I support for WGLC.

Thanks
Balaji

From: [email protected] <[email protected]>
Date: Monday, January 19, 2026 at 10:54 AM
To: [email protected] <[email protected]>
Subject: lisp Digest, Vol 206, Issue 7

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
      (Dino Farinacci)
   2. Re: WG Last Call for Signal-Free Locator/ID Separation Protocol (LISP) 
Multicast draft-ietf-lisp-rfc8378bis
      (Dino Farinacci)
   3. Re: WG Last Call for The Locator/ID Separation Protocol (LISP) for 
Multicast Environments - draft-ietf-lisp-rfc6831bis
      (David Meyer)


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

Message: 1
Date: Mon, 19 Jan 2026 10:40:56 -0800
From: Dino Farinacci <[email protected]>
Subject: [lisp] Re: WG Last Call for The Locator/ID Separation
        Protocol (LISP) for Multicast Environments -
        draft-ietf-lisp-rfc6831bis
To: Vengada Prasad Govindan <[email protected]>
Cc: LISP mailing list list <[email protected]>, [email protected]
Message-ID: <[email protected]>
Content-Type: multipart/alternative;
        boundary=Apple-Mail-75D93D49-A660-4CB0-A307-9366B5DAF3C0

Ditto for me.

Dino

> On Jan 19, 2026, at 3:44 AM, Vengada Prasad Govindan (venggovi) 
> <[email protected]> wrote:
>
> 
> 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
> _______________________________________________
> lisp mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 4720 bytes
Desc: not available

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

Message: 2
Date: Mon, 19 Jan 2026 10:41:17 -0800
From: Dino Farinacci <[email protected]>
Subject: [lisp] Re: WG Last Call for Signal-Free Locator/ID Separation
        Protocol (LISP) Multicast draft-ietf-lisp-rfc8378bis
To: Vengada Prasad Govindan <[email protected]>
Cc: LISP mailing list list <[email protected]>, [email protected]
Message-ID: <[email protected]>
Content-Type: multipart/alternative;
        boundary=Apple-Mail-F0904400-853A-45BC-AC80-0D8404FD1F13

Ditto as well for me.

Dino

> On Jan 19, 2026, at 3:45 AM, Vengada Prasad Govindan (venggovi) 
> <[email protected]> wrote:
>
> 
> 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
> _______________________________________________
> lisp mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
-------------- 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 <[email protected]>
Subject: [lisp] Re: WG Last Call for The Locator/ID Separation
        Protocol (LISP) for Multicast Environments -
        draft-ietf-lisp-rfc6831bis
To: [email protected]
Message-ID: <[email protected]>
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) 
> <[email protected]> wrote:
>
> 
> 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] <mailto:[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] <mailto:[email protected]>
> To unsubscribe send an email to [email protected] 
> <mailto:[email protected]>-------------- 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 -- [email protected]
To unsubscribe send an email to [email protected]


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

End of lisp Digest, Vol 206, Issue 7
************************************
_______________________________________________
lisp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
  • [lisp] Re: lisp Digest, Vol 206,... Balaji Pitta Venkatachalapathy (bvenkata)

Reply via email to