Re: WGLC of draft-ietf-mmusic-sdp-cs-11.txt

Hi

I have reviewed the above draft and have some comments (as chair) that 
will need to be addressed before we can move this one forward:

Technical Comments
=============

1) The document defines the "E164" 'addrtype' type as well as the "-" 
'addrtype' to be used in the "c=" line and wants to register these with 
IANA. As it turns out, RFC 3108 also defined these, however they never 
got registered with IANA. While the '-' seems to be defined similarly, 
the syntax for the "164" differs between the two, which is obviously a 
problem, not least considering RFC 3108 is Standards Track. Also, for 
some reason the cs-draft lists RFC 3108 as a normative reference, but it 
does not provide any normative text for its use.

2) The "cs-correlation" attribute includes an extension mechanism, 
however there is no description of how to use it, or any offer/answer 
procedures associated with it. For example, what do cs-draft 
implementations do if they encounter one or more unknown extensions.

- Section 5.2.1
OLD:
Note that <addrtype> and/or <connection-address> should not be
NEW:
Note that <addrtype> and/or <connection-address> MUST NOT be

- Section 5.2.3.1
Can there be at most one cs-correlation attribute per media description