Me too. I support. Dino
> On Oct 27, 2026, at 6:01 AM, Alberto Rodriguez-Natal (natal) > <[email protected]> wrote: > > Thanks Luigi for the editorial work. Kudos as well to the contributors that > shaped this document over the years. I support publication of the document. > > Thanks, > Alberto > > From: Padma Pillay-Esnault <[email protected]> > Date: Sunday, 25 October 2026 at 15:48 > To: [email protected] <[email protected]> > Cc: [email protected] <[email protected]> > Subject: EXTENSION Re: WG Last Call: draft-ietf-lisp-nat-traversal-03 (Now > Ends 2026-11-15) > > Dear WG > > The WGLC had only few responses. The chairs have decided to extend this call > for 2 more weeks ending 11/15/2026. > > Thanks > Padma and Luigi > > > On Oct 13, 2026, at 22:42, Prakash Jain > <[email protected]> wrote: > > I support too. > Thanks, > Prakash > > > On Mon, Oct 12, 2026, 11:54 AM Dino Farinacci <[email protected]> wrote: > I support publication as well. > > Dino > > > On Oct 12, 2026, at 5:30 AM, Luigi Iannone <[email protected]> wrote: > > > > As editor of the document I support publication. > > > > Ciao > > > > L. > > > >> On 6 Oct 2026, at 08:51, Padma Pillay-Esnault via Datatracker > >> <[email protected]> wrote: > >> > >> Dear LISP WG > >> > >> This message starts a WG Last Call for: > >> draft-ietf-lisp-nat-traversal-03 > >> > >> This Working Group Last Call ends on 2026-10-19 > >> > >> Abstract: > >> This document describes a mechanism for IPv4 NAT traversal for LISP > >> tunnel routers (xTR) and LISP Mobile Nodes (LISP-MN) behind a Network > >> Address Translator (NAT) device. A LISP device both detects the NAT > >> and initializes its state. Forwarding to the LISP device through a > >> NAT is enabled by the LISP Re-encapsulating Tunnel Router (RTR) > >> network element, which acts as an anchor point in the data plane, > >> forwarding traffic from unmodified LISP devices through the NAT. > >> > >> File can be retrieved from: > >> https://www.ietf.org/archive/id/draft-ietf-lisp-nat-traversal-03.txt > >> > >> Please review and indicate your support or objection to proceed with the > >> publication of this document by replying to this email keeping > >> [email protected] > >> in copy. Objections should be explained and suggestions to resolve them are > >> highly appreciated. > >> > >> Authors, and WG participants in general, are reminded of the Intellectual > >> Property Rights (IPR) disclosure obligations described in BCP 79 [1]. > >> Appropriate IPR disclosures required for full conformance with the > >> provisions > >> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > >> Sanctions available for application to violators of IETF IPR Policy can be > >> found at [3]. > >> > >> Thank you. > >> > >> [1] https://datatracker.ietf.org/doc/bcp78/ > >> [2] https://datatracker.ietf.org/doc/bcp79/ > >> [3] https://datatracker.ietf.org/doc/rfc6701/ > >> > >> The IETF datatracker status page for this Internet-Draft is: > >> https://datatracker.ietf.org/doc/draft-ietf-lisp-nat-traversal/ > >> > >> There is also an HTMLized version available at: > >> https://datatracker.ietf.org/doc/html/draft-ietf-lisp-nat-traversal-03 > >> > >> A diff from the previous version is available at: > >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-nat-traversal-03 > > > > _______________________________________________ > > lisp mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > _______________________________________________ > lisp mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ > lisp mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ > lisp mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
