Re: [lisp] Support draft-nexagon wg adoption
Thanks for the call Luigi. Just in case, let me formally restate that I support the adoption of the document. Thanks, Alberto From: lisp on behalf of Luigi Iannone Date: Tuesday, November 19, 2019 at 6:41 PM To: Sharon Barkai Cc: "lisp-cha...@ietf.org" , "lisp@ietf.org list" Subject: Re: [lisp] Support draft-nexagon wg adoption Hi, happy to see that there is already support for this document. This email formally opens the two weeks WG adoption call. Please have a look at the document and send an email on whether you agree or not to adopt it. (Silence is NOT consensus) Thanks Ciao L. On 19 Nov 2019, at 13:36, Sharon Barkai mailto:sharon.bar...@getnexar.com>> wrote: Hey, following very productive session today and as discussed would like to formally ask group for draft adoption. Cheers, Sharon --szb Cell: +972.53.2470068 WhatsApp: +1.650.492.0794 ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
Re: [lisp] I-D Action: draft-ietf-lisp-gpe-12.txt
Sounds good. Next version will reflect this change.. Fabio On 11/21/19, 10:29 AM, "Dino Farinacci" wrote: Ack. Dino > On Nov 21, 2019, at 10:27 AM, Luigi Iannone wrote: > > may be we can drop that and keep only LISP-GPE. > > L. > > > >> On 21 Nov 2019, at 10:26, Luigi Iannone wrote: >> >> the shim headers. >> >> L. >> >>> On 21 Nov 2019, at 10:25, Dino Farinacci wrote: >>> >>> What are “related features”. >>> >>> Dino >>> On Nov 21, 2019, at 10:17 AM, Luigi Iannone 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) wrote: > > ___ ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp >>> >> > ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
Re: [lisp] Support draft-nexagon wg adoption
Hi Luigi, as a co-author I support adoption of this document. It’s a very interesting use case that leverages LISP aspects such as signal free multicast and pub-sub that are some of the most interesting features of the LISP protocol stack. It’s also a very interesting example of how LISP can support applications that have very unique mobility requirements. Fabio From: lisp on behalf of Luigi Iannone Date: Wednesday, November 20, 2019 at 10:41 AM To: Sharon Barkai Cc: "lisp-cha...@ietf.org" , "lisp@ietf.org list" Subject: Re: [lisp] Support draft-nexagon wg adoption Hi, happy to see that there is already support for this document. This email formally opens the two weeks WG adoption call. Please have a look at the document and send an email on whether you agree or not to adopt it. (Silence is NOT consensus) Thanks Ciao L. On 19 Nov 2019, at 13:36, Sharon Barkai mailto:sharon.bar...@getnexar.com>> wrote: Hey, following very productive session today and as discussed would like to formally ask group for draft adoption. Cheers, Sharon --szb Cell: +972.53.2470068 WhatsApp: +1.650.492.0794 ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
Re: [lisp] Support draft-nexagon wg adoption
I also would like to support the adoption of the document by the WG On 11/22/19, 1:57 AM, "lisp on behalf of Victor Moreno (vimoreno)" wrote: This is a space where the LISP model can make a big difference and something the WG should be spending time on. I support the adoption of the document by the WG. -v > On Nov 20, 2019, at 7:16 PM, Sharon Barkai wrote: > > As co-auth also support draft for interoperable edge brokering of shared EID > geo-state. > > As “lisper” think mapped-overlay scales logically and/or algorithmically > addressable network-compute / multicast-channels. > > * ref also Dino mobile node mcast demo > > Combined believe this key to scale deployment per edge location for co-op > end-points for apps needing such termination / turn-around. > > --szb > Cell: +972.53.2470068 > WhatsApp: +1.650.492.0794 > >> On Nov 19, 2019, at 8:50 AM, Bruno Fernandez-Ruiz wrote: >> >> I believe the pub/sub + H3-server brokered model of communication fits >> naturally with LISP and addresses a hugely important networking requirement >> for continuously roaming mobility clients. >> >> As such, I endorse the draft to be published as an informational RFC. >> >> -b >> >>> On 19 Nov 2019, at 06:36, Sharon Barkai wrote: >>> >>> Hey, following very productive session today and as discussed would like to >>> formally ask group for draft adoption. >>> >>> Cheers, >>> Sharon >>> >>> --szb >>> Cell: +972.53.2470068 >>> WhatsApp: +1.650.492.0794 >>> ___ >>> lisp mailing list >>> lisp@ietf.org >>> https://www.ietf.org/mailman/listinfo/lisp >> > > ___ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
Re: [lisp] Support draft-nexagon wg adoption
This is a space where the LISP model can make a big difference and something the WG should be spending time on. I support the adoption of the document by the WG. -v > On Nov 20, 2019, at 7:16 PM, Sharon Barkai wrote: > > As co-auth also support draft for interoperable edge brokering of shared EID > geo-state. > > As “lisper” think mapped-overlay scales logically and/or algorithmically > addressable network-compute / multicast-channels. > > * ref also Dino mobile node mcast demo > > Combined believe this key to scale deployment per edge location for co-op > end-points for apps needing such termination / turn-around. > > --szb > Cell: +972.53.2470068 > WhatsApp: +1.650.492.0794 > >> On Nov 19, 2019, at 8:50 AM, Bruno Fernandez-Ruiz wrote: >> >> I believe the pub/sub + H3-server brokered model of communication fits >> naturally with LISP and addresses a hugely important networking requirement >> for continuously roaming mobility clients. >> >> As such, I endorse the draft to be published as an informational RFC. >> >> -b >> >>> On 19 Nov 2019, at 06:36, Sharon Barkai wrote: >>> >>> Hey, following very productive session today and as discussed would like to >>> formally ask group for draft adoption. >>> >>> Cheers, >>> Sharon >>> >>> --szb >>> Cell: +972.53.2470068 >>> WhatsApp: +1.650.492.0794 >>> ___ >>> lisp mailing list >>> lisp@ietf.org >>> https://www.ietf.org/mailman/listinfo/lisp >> > > ___ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp ___ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
