Re: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt

The revised text in Section 2.3 LGTM.

I noticed the acknowledgements section (Section 23) refers to SSODA, but
this name doesn't appear elsewhere in the document. Perhaps it should say
"the ADDITIONAL-ADDRESS-FAMILY mechanism"?

On Sun, Jun 3, 2018 at 11:24 PM Konda, Tirumaleswar Reddy <
TirumaleswarReddy_Konda@mcafee.com> wrote:

> This revision addresses comments from Justin.
>
> -Tiru
>
> > -----Original Message-----
> > From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
> > drafts@ietf.org
> > Sent: Monday, June 4, 2018 11:51 AM
> > To: i-d-announce@ietf.org
> > Cc: tram@ietf.org
> > Subject: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt
> >
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the TURN Revised and Modernized WG of the
> IETF.
> >
> >         Title           : Traversal Using Relays around NAT (TURN):
> Relay Extensions
> > to Session Traversal Utilities for NAT (STUN)
> >         Authors         : Tirumaleswar Reddy
> >                           Alan Johnston
> >                           Philip Matthews
> >                           Jonathan Rosenberg
> >       Filename        : draft-ietf-tram-turnbis-19.txt
> >       Pages           : 84
> >       Date            : 2018-06-03
> >
> > Abstract:
> >    If a host is located behind a NAT, then in certain situations it can
> >    be impossible for that host to communicate directly with other hosts
> >    (peers).  In these situations, it is necessary for the host to use
> >    the services of an intermediate node that acts as a communication
> >    relay.  This specification defines a protocol, called TURN (Traversal
> >    Using Relays around NAT), that allows the host to control the
> >    operation of the relay and to exchange packets with its peers using
> >    the relay.  TURN differs from some other relay control protocols in
> >    that it allows a client to communicate with multiple peers using a
> >    single relay address.
> >
> >    The TURN protocol was designed to be used as part of the ICE
> >    (Interactive Connectivity Establishment) approach to NAT traversal,
> >    though it also can be used without ICE.
> >
> >    This document obsoletes RFC 5766 and RFC 6156.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-tram-turnbis-19
> > https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-19
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-19
> >
> >
> > 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/
> >
> > _______________________________________________
> > tram mailing list
> > tram@ietf.org
> > https://www.ietf.org/mailman/listinfo/tram
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>