Re: no perpass /Secuirty Consideration in IETF docs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Could you please describe the need of perpass ?

I am talking complete security consideration removal. perpass is
needed for security reasons only.

Did you see the slide set and paper on my blog for Complete Multimedia

You do not even need complicated locks in the Complete Multimedia Recording/

Thanks
Samir

On Sat, Nov 21, 2015 at 12:33 PM, Yoav Nir <ynir.ietf@xxxxxxxxx> wrote:
> Hi, Samir
>
> The solution described in section 3.2 seems to be in line with what BCP 188 (RFC 7258) calls an attack.
>
> You should at least reference this and explain how this solution is either (1) not pervasive monitoring, or (2) a good thing, despite being “pervasive monitoring”
>
> Regards,
>
> Yoav
>
>> On 21 Nov 2015, at 6:34 PM, Samir Srivastava <samirs.lists@xxxxxxxxx> wrote:
>>
>> We donot need anywork being done in security consideration.
>>
>> Pl refer the draft
>>
>> https://tools.ietf.org/html/draft-srivastava-dispatch-avoidance-of-threats-00
>>
>> Thanks
>> Samir
>>
>





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]