draft-ietf-lisp-rfc8113bis-02.txt   draft-ietf-lisp-rfc8113bis-03.txt 
LISP M. Boucadair LISP M. Boucadair
Internet-Draft C. Jacquenet Internet-Draft C. Jacquenet
Obsoletes: 8113 (if approved) Orange Obsoletes: 8113 (if approved) Orange
Intended status: Standards Track January 10, 2019 Intended status: Standards Track January 25, 2019
Expires: July 14, 2019 Expires: July 29, 2019
Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA
Registry for Packet Type Allocations Registry for Packet Type Allocations
draft-ietf-lisp-rfc8113bis-02 draft-ietf-lisp-rfc8113bis-03
Abstract Abstract
This document specifies a Locator/ID Separation Protocol (LISP) This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting shared message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each experiments without consuming a LISP packet type codepoint for each
extension. extension.
This document obsoletes RFC 8113. This document obsoletes RFC 8113.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 14, 2019. This Internet-Draft will expire on July 29, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 39 skipping to change at page 3, line 39
This document does not introduce any additional security issues other This document does not introduce any additional security issues other
than those discussed in [I-D.ietf-lisp-rfc6833bis]. than those discussed in [I-D.ietf-lisp-rfc6833bis].
5. IANA Considerations 5. IANA Considerations
5.1. LISP Packet Types 5.1. LISP Packet Types
IANA has created a protocol registry for LISP Packet Types, numbered IANA has created a protocol registry for LISP Packet Types, numbered
0-15. 0-15.
The values in the ranges 5-7 and 9-14 can be assigned via Standards Values can be assigned via Standards Action [RFC8126]. Documents
Action [RFC8126]. Documents that request for a new LISP packet type that request for a new LISP packet type may indicate a preferred
may indicate a preferred value in the corresponding IANA sections. value in the corresponding IANA sections.
IANA is requested to replace the reference to RFC8113 with the RFC IANA is requested to replace the reference to RFC8113 with the RFC
number to be assigned to this document. number to be assigned to this document.
Also, IANA is requested to update the table as follows: Also, IANA is requested to update the table as follows:
OLD: OLD:
Message Code Reference Message Code Reference
================================= ==== =============== ================================= ==== ===============
skipping to change at page 5, line 13 skipping to change at page 5, line 13
this document instead of RFC8113. this document instead of RFC8113.
7. Acknowledgments 7. Acknowledgments
This work is partly funded by ANR LISP-Lab project #ANR-13-INFR- This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-
009-X. 009-X.
Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for
the review. the review.
Thanks to Geoff Huston, Brian Carpenter, and Barry Leiba for the Thanks to Geoff Huston, Brian Carpenter, Barry Leiba, and Suresh
review. Krishnan for the review.
8. Normative References 8. Normative References
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Fuller, V., Farinacci, D., and A. Cabellos-Aparicio, Fuller, V., Farinacci, D., and A. Cabellos-Aparicio,
"Locator/ID Separation Protocol (LISP) Control-Plane", "Locator/ID Separation Protocol (LISP) Control-Plane",
draft-ietf-lisp-rfc6833bis-23 (work in progress), December draft-ietf-lisp-rfc6833bis-23 (work in progress), December
2018. 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 5 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/