[lisp] Re: WG Last Call for Signal-Free Locator/ID Separation Protocol (LISP) Multicast draft-ietf-lisp-rfc8378bis

[Dino Farinacci <[e-mail]>]

Thanks Stig. Prasad, I can take care of these.

Dino

> On Jan 20, 2026, at 11:34 AM, Stig Venaas <[e-mail]> wrote:
> 
> Hi
> 
> I support publication of this document. It is in good shape, although
> I couldn't help spotting a few minor editorial issues. I'm sure the
> RFC Editor would fix them, but let me list what I found below.
> 
> In 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.
> 
> S/underlays/underlay
> 
> In abstract:
> "This document when approved obosletes RFC8378."
> Typo, and should have space after RFC.
> 
> In 5.2:
> "In the ASM case, for (*, G)". Should not have space after comma.
> 
> In 8:
> 
> When a Map_server uses "filtered-format', the Map-Reply it originates
> Note that the start and end quotes are different.
> 
> Thanks,
> Stig
> 
> On Mon, Jan 12, 2026 at 6:17 AM Luigi Iannone <[e-mail]> wrote:
>> 
>> 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]
> 
> _______________________________________________
> lisp mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]