Thanks, I have addressed this in -06 of the document by adding reference to RFC
3376 and RFC 3810.
- Prasad
________________________________
From: Stig Venaas <[email protected]>
Sent: Tuesday, January 20, 2026 10:36 PM
To: Marc Portoles Comeras (mportole) <[email protected]>
Cc: LISP mailing list list <[email protected]>; [email protected]
<[email protected]>
Subject: [lisp] Re: WG Last Call for The Locator/ID Separation Protocol (LISP)
for Multicast Environments - draft-ietf-lisp-rfc6831bis
As implementer and author I think this is ready for publication,
except for one minor issue. I'm not aware of any IPR.
In section 7 it says:
IGMPv1-v3, MLDv1-v2: These protocols [RFC4604] do not require any
changes for LISP-Multicast for two reasons. One is that they are
link-local and not used over site boundaries, and the second is
that they advertise group addresses that don't need translation.
RFC 4604 is about IGMPv3, MLDv2 and SSM. Hence the reference should be
updated. I'm not sure if there is a single common reference for all of
them.
Thanks,
Stig
On Tue, Jan 20, 2026 at 8:05 AM Marc Portoles Comeras (mportole)
<[email protected]> wrote:
>
> I support the WGLC for this document.
>
> Thanks,
> Marc
>
> From: Luigi Iannone <[email protected]>
> Date: Monday, January 12, 2026 at 6:16 AM
> 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
> _______________________________________________
> 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]
