Re: [AVTCORE] WG last call on draft-ietf-avtcore-6222bis-01

["Ali C. Begen (abegen)" <[e-mail]>]

Thanks for the review. 

On Mar 25, 2013, at 5:07 PM, "Magnus Westerlund" <[e-mail]> wrote:

> WG & Authors,
> 
> I have reviewed this document as an individual and have the following
> comments:
> 
> 1. Section 4.2, second bullet:
> 
>      To produce a short-term persistent RTCP CNAME, an RTP endpoint
>      MUST either (a) use the numeric representation of the layer-2
>      (Media Access Control (MAC)) address of the interface that is used
>      to initiate the RTP session as the "host" part of its RTCP CNAME
>      or
> 
> Is using the MAC really that unique? In these days of MAC cloning is
> this good enough to use as long term persistent CNAME identifier? I also

The probability of clash is pretty small but we can make a note of this. 

> wonder of its persistence behavior as it says to use the MAC of the
> Interface that ones initiate the communication over. With multiple
> interfaces, I can in the context of an application use all of these
> interfaces over a set of calls. Thus it doesn't have particular good
> long term stability either.

I think it is meant to say the interface over which the initial connection was made not all other possible interfaces that could be used during the rtp session. 
> 
> Should this option simply be removed? Or at least some discussion of
> these deficiencies?
> 
> 2. Section 6.1:
> 
> Secure RTP (SRTP) [RFC3711] keeps unauthorized entities out of an RTP
>   session, but it does not aim to prevent impersonation attacks from
>   unauthorized entities.
> 
> Shouldn't the last "unauthorized" be "authorized". Unauthorized packets
> will never be processed where the impersonation matters.

Yup. 
> 
> 
> Otherwise this looks good.

Thanks. 
> 
> Cheers
> 
> Magnus
> 
> 
> On 2013-03-12 20:04, Magnus Westerlund wrote:
>> WG,
>> 
>> This is to announce the start of a WG last call on:
>> 
>> Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
>> (CNAMEs) to be published as a proposed standard.
>> 
>> Document can be retrieved here:
>> https://datatracker.ietf.org/doc/draft-ietf-avtcore-6222bis/
>> 
>> Please provide any feedback by the 31st of March.
>> 
>> Regards
>> 
>> Magnus Westerlund
>> WG chair
>> 
>> 
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  [phone]
>> Färögatan 6                | Mobile [phone]
>> SE-164 80 Stockholm, Sweden| mailto: [e-mail]
>> ----------------------------------------------------------------------
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
> -- 
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  [phone]
> Färögatan 6                | Mobile [phone]
> SE-164 80 Stockholm, Sweden| mailto: [e-mail]
> ----------------------------------------------------------------------
>