Re: [lisp] I-D Action: draft-ietf-lisp-rfc6830bis-10.txt

> Hi all
> 
> This document should address all the comments except this one:
> 
> G.- Move sections 16 (Mobility Considerations), 17 (xTR Placement Considerations), 18 (Traceroute Consideration) to a new OAM document
> 
> The authors would like to have a better understanding of where this text will go.

Right, we concluded to not remove the valuable text. A lot of time and thought went into writing it and we didn’t want to lose it. There was no where that was agreed upon to put it.

So since we felt there was no concensus on Sections 16-18, we didn’t make any change.

Dino

> 
> If we adress this by today I can submit a new version (before the cut-off) taking this comment into account.
> 
> Thanks!
> 
> Albert
> 
> On Mon, Mar 5, 2018 at 10:44 AM, Luigi Iannone <ggx@gigix.net> wrote:
> Hi Albert, Dino,
> 
> this version of the document doesn’t not yet completely respect the discussions of the last months.
> 
> Do you plan another version before London?
> 
> Thanks
> 
> Luigi
> 
> 
> > On 5 Mar 2018, at 00:51, 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 Locator/ID Separation Protocol WG of the IETF.
> >
> >        Title           : The Locator/ID Separation Protocol (LISP)
> >        Authors         : Dino Farinacci
> >                          Vince Fuller
> >                          Dave Meyer
> >                          Darrel Lewis
> >                          Albert Cabellos
> >       Filename        : draft-ietf-lisp-rfc6830bis-10.txt
> >       Pages           : 50
> >       Date            : 2018-03-04
> >
> > Abstract:
> >   This document describes the data-plane protocol for the Locator/ID
> >   Separation Protocol (LISP).  LISP defines two namespaces, End-point
> >   Identifiers (EIDs) that identify end-hosts and Routing Locators
> >   (RLOCs) that identify network attachment points.  With this, LISP
> >   effectively separates control from data, and allows routers to create
> >   overlay networks.  LISP-capable routers exchange encapsulated packets
> >   according to EID-to-RLOC mappings stored in a local map-cache.
> >
> >   LISP requires no change to either host protocol stacks or to underlay
> >   routers and offers Traffic Engineering, multihoming and mobility,
> >   among other features.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-lisp-rfc6830bis-10
> > https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6830bis-10
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-rfc6830bis-10
> >
> >
> > 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/
> >
> > _______________________________________________
> > 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
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
> 