[lisp] Re: WG Last Call for The Locator/ID Separation Protocol (LISP) for Multicast Environments - draft-ietf-lisp-rfc6831bis

[Dino Farinacci <[e-mail]>]

Ditto for me. 

Dino

> 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] <[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]
> To unsubscribe send an email to [e-mail]