Ack. Dino
> On Nov 21, 2019, at 10:27 AM, Luigi Iannone <[email protected]> wrote: > > may be we can drop that and keep only LISP-GPE. > > L. > > > >> On 21 Nov 2019, at 10:26, Luigi Iannone <[email protected]> wrote: >> >> the shim headers. >> >> L. >> >>> On 21 Nov 2019, at 10:25, Dino Farinacci <[email protected]> wrote: >>> >>> What are “related features”. >>> >>> Dino >>> >>>> On Nov 21, 2019, at 10:17 AM, Luigi Iannone <[email protected]> wrote: >>>> >>>> Hi Fabio, >>>> >>>> I would suggest that you change the text in section 5.1 as follows: >>>> >>>> OLD: >>>> >>>> The detection of ETR capabilities to support multiple data plane >>>> encapsulations and shim headers is out of the scope of this document. >>>> Given that the applicability domain of LISP-GPE is a traffic-managed >>>> controlled environment, ITR/ETR (xTR) configuration mechanisms >>>> may be used for this purpose. >>>> >>>> NEW: >>>> >>>> The discovery of xTR capabilities to support LISP-GPE and related >>>> features >>>> is out of the scope of this document. >>>> Given that the applicability domain of LISP-GPE is a traffic-managed >>>> controlled environment, ITR/ETR (xTR) configuration mechanisms >>>> may be used for this purpose. >>>> >>>> >>>> Other than that, the document looks good to me. >>>> >>>> Ciao >>>> >>>> L. >>>> >>>> >>>> >>>>> On 19 Nov 2019, at 16:00, Fabio Maino (fmaino) <[email protected]> wrote: >>>>> >>>>> _______________________________________________ >>>> >>>> _______________________________________________ >>>> lisp mailing list >>>> [email protected] >>>> https://www.ietf.org/mailman/listinfo/lisp >>> >> > _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
