Re: [MMUSIC] I-D Action: draft-ietf-mmusic-rtsp-nat-12.txt

Hi Magnus

I have taken a look at the document and, the only real technical 
comments I have at this point are:

- Section 6.3 (Non-Supporting Proxies), last paragraph says that:
<quote>
This variance in results is the reason
    we don't recommend the usage of the Proxy-Require header. Instead we
    recommend the usage of the Supported header to force proxies to
    include the feature tags they support in the proxy-supported which
    will provide a positive indication when all proxies in the chain
    between the client and server support the functionality.  Even if not
    explicitly indicating support, any SETUP response including a
    transport specification with "D-ICE" will be implicit indication that
    the proxy chain supports at least passthrough of this media.
</quote>

I didn't follow the inferred logic in the last sentence (how does the 
response convey support for the entire chain). Can you elaborate on that 
part ?

- Section 8 (Fallback)
Section title and overall description is a bit confusing (it seems to be 
about about backwards compatibility with non-ICE supporting RTSP entities).
Also, the section recommends use of defunct (obsolete) behavior defined 
in RFC 3489 to try and determine the NAT type. Why is that (shouldn't we 
be based on RFC 5389) ?

I have some editorial/minor comments as well that I will send to the 
authors directly.

Also, we could really use another set of eyes on it (preferably by 
somebody that has both ICE and RTSP expertise)

Thanks

-- Flemming

On 5/7/12 4:39 AM, Magnus Westerlund wrote:
> WG,
>
> This version of the RTSP NAT specification contains some actual changes.
>
> - Specifies how one may Optionally use RFC 6544 TCP based candidates
> with RTSP.
>
> - Found a syntax bug related to ICE password and ufrag. They may
> contain characters that aren't allowed outside of double quote in RTSP
> transport parameters. Thus the syntax has been changed to put the
> password and ufrag values inside double quotes.
>
> - Updated IANA section to better meet the respective registries rules.
>
> - A number of editorial changes.
>
> Diff from the previous version.
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rtsp-nat-12
>
> I would appreciate a review of this to confirm that this document is in
> fact ready for WG last call.
>
> Thanks
>
> Magnus Westerlund
>
>
> On 2012-05-07 09:55, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.
>>
>> 	Title           : A Network Address Translator (NAT) Traversal mechanism for media controlled by Real-Time Streaming Protocol (RTSP)
>> 	Author(s)       : Jeff Goldberg
>>                            Magnus Westerlund
>>                            Thomas Zeng
>> 	Filename        : draft-ietf-mmusic-rtsp-nat-12.txt
>> 	Pages           : 30
>> 	Date            : 2012-05-07
>>
>>     This document defines a solution for Network Address Translation
>>     (NAT) traversal for datagram based media streams setup and controlled
>>     with Real-time Streaming Protocol version 2 (RTSP 2.0).  It uses
>>     Interactive Connectivity Establishment (ICE) adapted to use RTSP as a
>>     signalling channel, defining the necessary extra RTSP extensions and
>>     procedures.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-nat-12.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-nat-12.txt
>>
>> The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-rtsp-nat/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>