rfc9306v2.txt | rfc9306.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) A. Rodriguez-Natal | Internet Engineering Task Force (IETF) A. Rodriguez-Natal | |||
Request for Comments: 9306 Cisco | Request for Comments: 9306 Cisco | |||
Updates: 8060 V. Ermagan | Updates: 8060 V. Ermagan | |||
Category: Experimental Google | Category: Experimental Google, Inc. | |||
ISSN: 2070-1721 A. Smirnov | ISSN: 2070-1721 A. Smirnov | |||
V. Ashtaputre | V. Ashtaputre | |||
Cisco | Cisco | |||
D. Farinacci | D. Farinacci | |||
lispers.net | lispers.net | |||
September 2022 | October 2022 | |||
Vendor-Specific LISP Canonical Address Format (LCAF) | Vendor-Specific LISP Canonical Address Format (LCAF) | |||
Abstract | Abstract | |||
This document describes a new Locator/ID Separation Protocol (LISP) | This document describes a new Locator/ID Separation Protocol (LISP) | |||
Canonical Address Format (LCAF), the Vendor-Specific LCAF. This LCAF | Canonical Address Format (LCAF), the Vendor-Specific LCAF. This LCAF | |||
enables organizations to have implementation-specific encodings for | enables organizations to have implementation-specific encodings for | |||
LCAF addresses. This document updates RFC 8060. | LCAF addresses. This document updates RFC 8060. | |||
skipping to change at line 202 ¶ | skipping to change at line 202 ¶ | |||
Writing an IANA Considerations Section in RFCs", BCP 26, | Writing an IANA Considerations Section in RFCs", BCP 26, | |||
RFC 8126, DOI 10.17487/RFC8126, June 2017, | RFC 8126, DOI 10.17487/RFC8126, June 2017, | |||
<https://www.rfc-editor.org/info/rfc8126>. | <https://www.rfc-editor.org/info/rfc8126>. | |||
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
[RFC9300] Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. | [RFC9300] Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. | |||
Cabellos, Ed., "The Locator/ID Separation Protocol | Cabellos, Ed., "The Locator/ID Separation Protocol | |||
(LISP)", RFC 9300, DOI 10.17487/RFC9300, September 2022, | (LISP)", RFC 9300, DOI 10.17487/RFC9300, October 2022, | |||
<https://www.rfc-editor.org/info/rfc9300>. | <https://www.rfc-editor.org/info/rfc9300>. | |||
[RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos, | [RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos, | |||
Ed., "Locator/ID Separation Protocol (LISP) Control | Ed., "Locator/ID Separation Protocol (LISP) Control | |||
Plane", RFC 9301, DOI 10.17487/RFC9301, September 2022, | Plane", RFC 9301, DOI 10.17487/RFC9301, October 2022, | |||
<https://www.rfc-editor.org/info/rfc9301>. | <https://www.rfc-editor.org/info/rfc9301>. | |||
Acknowledgments | Acknowledgments | |||
The authors would like to thank Joel Halpern, Luigi Iannone, and | The authors would like to thank Joel Halpern, Luigi Iannone, and | |||
Alvaro Retana for their suggestions and guidance regarding this | Alvaro Retana for their suggestions and guidance regarding this | |||
document. | document. | |||
Authors' Addresses | Authors' Addresses | |||
Alberto Rodriguez-Natal | Alberto Rodriguez-Natal | |||
Cisco | Cisco | |||
Spain | Spain | |||
Email: natal@cisco.com | Email: natal@cisco.com | |||
Vina Ermagan | Vina Ermagan | |||
Google, Inc. | ||||
1600 Amphitheatre Parkway | ||||
Mountain View, CA 94043 | ||||
United States of America | United States of America | |||
Email: ermagan@gmail.com | Email: ermagan@gmail.com | |||
Anton Smirnov | Anton Smirnov | |||
Cisco | Cisco | |||
Diegem | Diegem | |||
Belgium | Belgium | |||
Email: asmirnov@cisco.com | Email: asmirnov@cisco.com | |||
Vrushali Ashtaputre | Vrushali Ashtaputre | |||
End of changes. 5 change blocks. | ||||
5 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |