<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-lsp-ping-registry" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-lsp-ping-registry-03">
   <front>
      <title>IANA Registries for LSP Ping Code Points</title>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         <organization>Orange</organization>
      </author>
      <author initials="N." surname="Akiya" fullname="Nobo Akiya">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="C." surname="Pignataro" fullname="Carlos Pignataro">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="L." surname="Andersson" fullname="Loa Andersson">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="S." surname="Aldrin" fullname="Sam Aldrin">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="March" day="6" year="2015" />
      <abstract>
	 <t>RFCs 4379 and 6424 created name spaces for Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP) Ping. However, those RFCs did not create the corresponding IANA registries for Downstream Mapping object Flags (DS Flags), Multipath Types, Pad TLVs, and Interface and Label Stack Address Types.

 There is now a need to make further code point allocations from these name spaces. This document updates RFCs 4379 and 6424 in that it creates IANA registries for that purpose.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-lsp-ping-registry-03" />
   
</reference>
