draft-ietf-lisp-type-iana-02.txt   draft-ietf-lisp-type-iana-03.txt 
Network Working Group M. Boucadair Network Working Group M. Boucadair
Internet-Draft C. Jacquenet Internet-Draft C. Jacquenet
Intended status: Standards Track Orange Intended status: Standards Track Orange
Expires: April 1, 2017 September 28, 2016 Expires: April 23, 2017 October 20, 2016
LISP Experimental Message & IANA Registry for LISP Packet Type LISP Experimental Message & IANA Registry for LISP Packet Type
Allocations Allocations
draft-ietf-lisp-type-iana-02 draft-ietf-lisp-type-iana-03
Abstract Abstract
This document defines a registry for LISP Packet Type allocations. This document defines a registry for LISP Packet Type allocations.
It also specifies a shared LISP message type for experimentation It also specifies a shared LISP message type for experimentation
purposes. purposes.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 April 1, 2017. This Internet-Draft will expire on April 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 4, line 13 skipping to change at page 4, line 13
LISP Experimental Message 15 [This document] LISP Experimental Message 15 [This document]
The values in the ranges 5-7 and 9-14 can be assigned via Standards The values in the ranges 5-7 and 9-14 can be assigned via Standards
Action [RFC5226]. Documents that request for a new LISP packet type Action [RFC5226]. Documents that request for a new LISP packet type
may indicate a preferred value in the corresponding IANA sections. may indicate a preferred value in the corresponding IANA sections.
The value 15 is reserved for Experimental Use [RFC5226]. The value 15 is reserved for Experimental Use [RFC5226].
4.2. Sub-Types 4.2. Sub-Types
IANA is requested to create a "LISP Experimental Message Sub-types" IANA is requested to create a "LISP Experimental Message Sub-types"
registry. registry. No initial values are assigned at the creation of the
registry; (0-4095) are available for future assignments.
Entries are assigned on a FCFS basis. Entries are assigned on a FCFS basis.
The registration procedure should provide IANA with the desired The registration procedure should provide IANA with the desired
codepoint and a point of contact. Providing a short description codepoint and a point of contact. Providing a short description
(together with an acronym, if relevant) of the foreseen usage of the (together with an acronym, if relevant) of the foreseen usage of the
experimental message is also encouraged. experimental message is also encouraged.
5. Acknowledgments 5. Acknowledgments
 End of changes. 4 change blocks. 
4 lines changed or deleted 5 lines changed or added

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