Re: [MMUSIC] I-D Action: draft-ietf-mmusic-latching-06.txt

Sure. Fixed.

On 01.06.14, 01:41, Parthasarathi R wrote:
> Hi all,
>
> The minor text comment in the introduction for the below text:
>
> "It is however worth pointing out that the current
>     deployment levels of HNT and NATs themselves make an exclusive
>     adoption of ICE highly unlikely in the foreseeable future."
>
> I agree with you that the above text is correct when the initial draft is
> written on June 2012
> (http://tools.ietf.org/html/draft-ivov-mmusic-latching-00). Because WebRTC
> mandated ICE, the above scenario is changed drastically now and lot of
> SBC/intermediates supports ICE as one of the NAT traversal mechanism today.
> In case you revise this draft once more, Please consider for updating the
> text or remove this line to reflect the current status.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Thursday, May 29, 2014 10:11 PM
>> To: i-d-announce@ietf.org
>> Cc: mmusic@ietf.org
>> Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-latching-06.txt
>>
>>
>> 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           : Latching: Hosted NAT Traversal (HNT) for
>> Media in Real-Time Communication
>>          Authors         : Emil Ivov
>>                            Hadriel Kaplan
>>                            Dan Wing
>> 	Filename        : draft-ietf-mmusic-latching-06.txt
>> 	Pages           : 16
>> 	Date            : 2014-05-29
>>
>> Abstract:
>>     This document describes behavior of signalling intermediaries in
>>     Real-Time Communication (RTC) deployments, sometimes referred to as
>>     Session Border Controllers (SBCs), when performing Hosted NAT
>>     Traversal (HNT).  HNT is a set of mechanisms, such as media relaying
>>     and latching, that such intermediaries use to enable other RTC
>>     devices behind NATs to communicate with each other.
>>
>>     This document is non-normative, and is only written to explain HNT
>> in
>>     order to provide a reference to the IETF community, as well as an
>>     informative description to manufacturers, and users.
>>
>>     Latching, which is one of the components of the HNT components, has
>> a
>>     number of security issues covered here.  Because of those, and
>> unless
>>     all security considerations explained here are taken into account
>> and
>>     solved, the IETF advises against use of latching mechanism over the
>>     Internet and recommends other solutions such as the Interactive
>>     Connectivity Establishment (ICE) protocol.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-latching/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-mmusic-latching-06
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-latching-06
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>

-- 
https://jitsi.org