draft-ietf-lisp-rfc8113bis-00.txt   draft-ietf-lisp-rfc8113bis-01.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
Updates: rfc6833bis (if approved) September 27, 2018 Updates: rfc6833bis (if approved) November 5, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: March 31, 2019 Expires: May 9, 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-00 draft-ietf-lisp-rfc8113bis-01
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 40 skipping to change at page 1, line 40
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 March 31, 2019. This Internet-Draft will expire on May 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. LISP Shared Extension Message Type . . . . . . . . . . . . . 3 3. LISP Shared Extension Message Type . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 3 5.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 3
5.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4 5.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 6. Changes from RFC 8113 . . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The Locator/ID Separation Protocol (LISP) base specification, The Locator/ID Separation Protocol (LISP) base specification,
[I-D.ietf-lisp-rfc6833bis], defines a set of primitives that are [I-D.ietf-lisp-rfc6833bis], defines a set of primitives that are
identified with a packet type code. Several extensions have been identified with a packet type code. Several extensions have been
proposed to add more LISP functionalities. It is expected that proposed to add more LISP functionalities. It is expected that
additional LISP extensions will be proposed in the future. additional LISP extensions will be proposed in the future.
skipping to change at page 4, line 33 skipping to change at page 4, line 33
The values in the range 0-1023 are assigned via Standards Action. The values in the range 0-1023 are assigned via Standards Action.
This range is provisioned to anticipate, in particular, the This range is provisioned to anticipate, in particular, the
exhaustion of the LISP Packet types. exhaustion of the LISP Packet types.
The values in the range 1024-4095 are assigned on a First Come, First The values in the range 1024-4095 are assigned on a First Come, First
Served (FCFS) basis. The registration procedure should provide IANA Served (FCFS) basis. The registration procedure should provide IANA
with the desired codepoint and a point of contact; providing a short with the desired codepoint and a point of contact; providing a short
description (together with an acronym, if relevant) of the foreseen description (together with an acronym, if relevant) of the foreseen
usage of the extension message is also encouraged. usage of the extension message is also encouraged.
6. Acknowledgments 6. Changes from RFC 8113
The following changes were made from RFC 8113:
o Change the status from Experimental to Standard track.
o Indicate explicitly that the shared extension is used for two
purposes: extend the type space and conduct experiments to assess
new LISP extensions. Therefore, this document updates
[I-D.ietf-lisp-rfc6833bis].
o Delete pointers to some examples illustrating how the shared
extension message is used to extend the LISP protocol.
o Request IANA to update the "IANA LISP Packet Types" and ""LISP
Shared Extension Message Type Sub-types" registries to point to
this document instead of RFC8113.
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 for the RtgDir directorate review. Thanks to Geoff Huston for the RtgDir directorate review.
7. 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-15 (work in progress), draft-ietf-lisp-rfc6833bis-19 (work in progress), October
September 2018. 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
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>.
 End of changes. 8 change blocks. 
10 lines changed or deleted 29 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/