I am a bit lost here…. This: The xTR needs to receive traffic with the destination port equal to the translated port and the source port equal to the well-known port 4341.
Is not what the document says. The NAT state is such that the xTR behind it will receive LISP packets with destination port 4341 (as for the standard), your sentence seems to suggest the opposite. L. > On 18 Feb 2026, at 18:19, Dino Farinacci <[email protected]> wrote: > > Your text is misleading. Just use what I told you. > > And your last point isn’t true in a decentralized > NAT environment. But for this document’s scope, use RTR as the xTR term. > > Dino > >> On Feb 18, 2026, at 6:34 AM, Luigi Iannone <[email protected]> wrote: >> >> Hi Dino, >> >> DO you meqns the “Second … “ Sentence? >> >> What about: >> >> Second, LISP protocol requires an xTR >> to receive traffic on the specific UDP port 4341, hence, the random >> UDP port allocated by the NAT on its public side is not used by other >> xTRs to send LISP traffic. >> >> Better? >> >> L. >> >> >> >>> On 16 Feb 2026, at 19:06, Dino Farinacci <[email protected]> wrote: >>> >>> Luigi, to be more precise, this paragraph sound say: >>> >>> <Screenshot 2026-02-16 at 10.03.48 AM.png> >>>> >>>> >>> >>> The xTR needs to receive traffic with the destination port equal to the >>> translated port and the source port equal to the well-known port 4341. >>> >>> Dino >>> >>>>> On Feb 16, 2026, at 5:26 AM, [email protected] wrote: >>>> >>>> Internet-Draft draft-ietf-lisp-nat-traversal-01.txt is now available. It >>>> is a >>>> work item of the Locator/ID Separation Protocol (LISP) WG of the IETF. >>>> >>>> Title: NAT traversal for LISP >>>> Author: Luigi Iannone >>>> Name: draft-ietf-lisp-nat-traversal-01.txt >>>> Pages: 28 >>>> Dates: 2026-02-16 >>>> >>>> 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. >>>> >>>> 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-01 >>>> >>>> A diff from the previous version is available at: >>>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-nat-traversal-01 >>>> >>>> Internet-Drafts are also available by rsync at: >>>> rsync.ietf.org::internet-drafts >>>> >>>> >>>> _______________________________________________ >>>> 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]
