I support the adaptation of this document, it is time to be updated.

Thanks
Hooman


-----Original Message-----
From: Matthew Bocci via Datatracker <[email protected]> 
Sent: Tuesday, November 25, 2025 11:56 AM
To: [email protected]; [email protected]; [email protected]
Subject: [bess] Call for adoption: draft-zzhang-bess-rfc6514bis-01 (Ends 
2025-12-09)


CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.



Subject: Call for adoption: draft-zzhang-bess-rfc6514bis-01  (Ends 2025-12-09)

This message starts a 2-week Call for Adoption for this document.

Abstract:
   RFC 6514 describes the BGP encodings and procedures for exchanging
   the information elements required by Multicast in MPLS/BGP IP VPNs,
   as specified in RFC 6513.

   This document updates and obsoletes RFC 6514.  The original authors
   of RFC 6514 are listed at the end of this document.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-zzhang-bess-rfc6514bis/

Please reply to this message keeping [email protected] in copy by indicating 
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual 
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions 
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be 
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/



_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to