Re: [AVT] FW: New Version Notification for draft-begen-avt-rtp-cnames-01

[Roni Even <[e-mail]>]

Hi,

> 
> * Question: Are there any ideas on the table for generating a unique
> identifier that wouldn't be useful for traffic analysis?  That is, a
> unique
> identifier that is generated on each call?  For example, a BASE64-
> encoded
> SHA1-HMAC of one of the three pieces of information currently suggested
> in the
> memo (IPv6 address, unique FQDN, UUID), where the 'secret' is changed
> for
> every new RTP session?  This seems it could eliminate traffic analysis
> concerns.
> 

RFC 3550 says that one of the usage of RTCP is for monitoring and "To
facilitate third-party monitoring, the CNAME SHOULD be suitable for either a
program or a person to locate the source." 


Other comments

1. For the UUID I assume the proposal is to use the string representation of
the UUID maybe as a URN. 

2. As for the structure of CNAME, section 6.5.1 of RFC 3550 has the cname
composed of user and domain name. it also says that
"The user name SHOULD be in a form that a program such as "finger" or "talk"
could use, i.e., it typically is the login name rather than the personal
name.  The host name is not necessarily identical to the one in the
participant's electronic mail address. "
Maybe this document should recommend how to create a unique host part of the
CNAME and not the whole CNAME.

Regards
Roni Even