[lisp] Re: lisp Digest, Vol 206, Issue 7

["Balaji Pitta Venkatachalapathy (bvenkata)" <[e-mail]>]

I support WGLC for rfc8378bis

Thanks
Balaji

> From: Luigi Iannone <[e-mail]>
> Sent: Monday, January 12, 2026 7:46 PM
> To: LISP mailing list list <[e-mail]>
> Cc: [e-mail] <[e-mail]>
> 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
> _______________________________________________
> lisp mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 4872 bytes
Desc: not available

------------------------------

Message: 3
Date: Mon, 19 Jan 2026 10:51:37 -0800
From: David Meyer <[e-mail]>
Subject: [lisp] Re: WG Last Call for The Locator/ID Separation
        Protocol (LISP) for Multicast Environments -
        draft-ietf-lisp-rfc6831bis
To: [e-mail]
Message-ID: <[e-mail]>
Content-Type: multipart/alternative;
        boundary="Apple-Mail=_4A5AFE5E-295D-4842-AD55-A7D6FC8881CF"

Same here. David Meyer


> On Jan 19, 2026, at 3:44 AM, Vengada Prasad Govindan (venggovi) <venggovi=[e-mail]> wrote:
>
> 
> As an implementor and author, support WGLC for this document. Am not aware of any undisclosed IPR.
> Thanks
> Prasad
> From: Luigi Iannone <[e-mail]>
> Sent: Monday, January 12, 2026 7:46 PM
> To: LISP mailing list list <[e-mail]>
> Cc: [e-mail] <mailto:[e-mail]> <[e-mail]>
> 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 -- [e-mail] <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 3409 bytes
Desc: not available

------------------------------

Subject: Digest Footer

_______________________________________________
lisp mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]


------------------------------

End of lisp Digest, Vol 206, Issue 7
************************************