I support WG Last call for draft-ietf-lisp-rfc6831bis Thanks Balaji
From: [email protected] <[email protected]> Date: Monday, January 19, 2026 at 3:45 AM To: [email protected] <[email protected]> Subject: lisp Digest, Vol 206, Issue 6 Send lisp mailing list submissions to [email protected] To subscribe or unsubscribe via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of lisp digest..." Today's Topics: 1. Re: WG Last Call for The Locator/ID Separation Protocol (LISP) for Multicast Environments - draft-ietf-lisp-rfc6831bis (Vengada Prasad Govindan (venggovi)) 2. Re: WG Last Call for Signal-Free Locator/ID Separation Protocol (LISP) Multicast draft-ietf-lisp-rfc8378bis (Vengada Prasad Govindan (venggovi)) ---------------------------------------------------------------------- Message: 1 Date: Mon, 19 Jan 2026 11:44:07 +0000 From: "Vengada Prasad Govindan (venggovi)" <[email protected]> Subject: [lisp] Re: WG Last Call for The Locator/ID Separation Protocol (LISP) for Multicast Environments - draft-ietf-lisp-rfc6831bis To: Luigi Iannone <[email protected]>, LISP mailing list list <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <[email protected] prd11.prod.outlook.com> Content-Type: multipart/alternative; boundary="_000_DM8PR11MB5622F8 FF6B8CF50AB290A760CD88ADM8PR11MB5622namp_" As an implementor and author, support WGLC for this document. Am not aware of any undisclosed IPR. Thanks Prasad ________________________________ From: Luigi Iannone <[email protected]> Sent: Monday, January 12, 2026 7:46 PM To: LISP mailing list list <[email protected]> Cc: [email protected] <[email protected]> Subject: [lisp] WG Last Call for The Locator/ID Separation Protocol (LISP) for Multicast Environments - draft-ietf-lisp-rfc6831bis Dear WG As requested by the authors, this message starts a two-week WG Last Call for ending on January 26th 2026. https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6831bis/ Title: The Locator/ID Separation Protocol (LISP) for Multicast Environments Abstract: This document describes the design for inter-domain multicast overlays using the Locator/ID Separation Protocol (LISP) architecture and protocols. The document specifies how LISP multicast overlays operate over multicast and unicast underlays. The mechanisms in this specification indicate how a signal-based approach using the PIM protocol can be used to program LISP encapsulators with a replication list in a locator-set, where the replication list can be a mix of multicast and unicast locators. This document when approved obsoletes RFC6831 Please review this WG document and let the WG know if you agree that it is ready to be handed over to the AD. If you have objections, please state your reasons why, and explain what it would take to address your concerns. Note: silence IS NOT consensus. Thanks Padma and Luigi -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 4152 bytes Desc: not available ------------------------------ Message: 2 Date: Mon, 19 Jan 2026 11:44:46 +0000 From: "Vengada Prasad Govindan (venggovi)" <[email protected]> Subject: [lisp] Re: WG Last Call for Signal-Free Locator/ID Separation Protocol (LISP) Multicast draft-ietf-lisp-rfc8378bis To: Luigi Iannone <[email protected]>, LISP mailing list list <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <[email protected] prd11.prod.outlook.com> Content-Type: multipart/alternative; boundary="_000_DM8PR11MB5622E0 1E59CF5493D3494382CD88ADM8PR11MB5622namp_" As implementor and co-author support WGLC. Not aware of any undisclosed IPR Thanks Prasad ________________________________ From: Luigi Iannone <[email protected]> Sent: Monday, January 12, 2026 7:46 PM To: LISP mailing list list <[email protected]> Cc: [email protected] <[email protected]> Subject: [lisp] WG Last Call for Signal-Free Locator/ID Separation Protocol (LISP) Multicast draft-ietf-lisp-rfc8378bis Dear WG As requested by the authors, this message starts a two-week WG Last Call for ending on January 26th 2026. https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc8378bis/ Title: Signal-Free Locator/ID Separation Protocol (LISP) Multicast Abstract: This document describes the design for inter-domain multicast overlays using the Locator/ID Separation Protocol (LISP). The document specifies how LISP multicast overlays operate over a unicast underlays. When multicast sources and receivers are active at Locator/ID Separation Protocol (LISP) sites, the core network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not available to connect the multicast sites together, a signal-free mechanism can be used to allow traffic to flow between sites. The mechanism within here uses unicast replication and encapsulation over the core network for the data plane and uses the LISP mapping database system so encapsulators at the source LISP multicast site can find decapsulators at the receiver LISP multicast sites. This document when approved obosletes RFC8378. Please review this WG document and let the WG know if you agree that it is ready to be handed over to the AD. If you have objections, please state your reasons why, and explain what it would take to address your concerns. Note: silence IS NOT consensus. Thanks Padma and Luigi -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 4296 bytes Desc: not available ------------------------------ Subject: Digest Footer _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected] ------------------------------ End of lisp Digest, Vol 206, Issue 6 ************************************
_______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
