rfc9160xml2.original.xml   rfc9160.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="1"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-ietf-opsawg-ipfix-mpls-sr-label-type-11"
ipr="trust200902">
<front>
<title
abbrev="IPFIX MPLS Segment Routing Information">Export&nbsp;of&nbsp;MPLS&nbs
p;Segment&nbsp;Routing&nbsp;Label&nbsp;Type&nbsp;Information&nbsp;in
IP&nbsp;Flow&nbsp;Information&nbsp;Export&nbsp;(IPFIX)</title>
<!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-opsawg-ipfix
-mpls-sr-label-type-11" number="9160" ipr="trust200902" obsoletes="" updates=""
submissionType="IETF" category="info" consensus="true" xml:lang="en" tocInclude=
"true" tocDepth="1" symRefs="true" sortRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.10.0 -->
<front>
<title abbrev="IPFIX MPLS Segment Routing Information">Export of MPLS Segmen
t Routing Label Type Information in IP Flow Information Export (IPFIX)</title>
<seriesInfo name="RFC" value="9160"/>
<author fullname="Thomas Graf" initials="T. " surname="Graf"> <author fullname="Thomas Graf" initials="T. " surname="Graf">
<organization>Swisscom</organization> <organization>Swisscom</organization>
<address> <address>
<postal> <postal>
<street>Binzring 17</street> <street>Binzring 17</street>
<city>Zürich</city>
<city>Zurich</city>
<code>8045</code> <code>8045</code>
<country>Switzerland</country> <country>Switzerland</country>
</postal> </postal>
<email>thomas.graf@swisscom.com</email> <email>thomas.graf@swisscom.com</email>
</address> </address>
</author> </author>
<date month="December" year="2021"/>
<date day="18" month="September" year="2021"/> <keyword>control plane migration</keyword>
<keyword>traffic monitoring</keyword>
<keyword>traffic accounting</keyword>
<keyword>OSPF</keyword>
<keyword>IS-IS</keyword>
<keyword>BGP Prefix-SID</keyword>
<keyword>PCE</keyword>
<keyword>PCEP SR</keyword>
<abstract> <abstract>
<t>This document introduces new IP Flow Information Export (IPFIX) code <t>This document introduces new IP Flow Information Export (IPFIX) code
points to identify which traffic is being forwarded based on which MPLS points to identify which traffic is being forwarded based on which MPLS
control plane protocol used within a Segment Routing domain. In control plane protocol is used within a Segment Routing domain. In
particular, this document defines five code points for the IPFIX particular, this document defines five code points for the IPFIX
mplsTopLabelType Information Element for PCE, IS-IS, OSPFv2, OSPFv3, and mplsTopLabelType Information Element for Path Computation Element (PCE), I
BGP MPLS Segment Routing extensions.</t> S-IS, OSPFv2, OSPFv3, and
BGP MPLS Segment Routing extensions.
</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="Introduction" title="Introduction"> <section anchor="Introduction" numbered="true" toc="default">
<t>Four routing protocol extensions, <xref target="RFC8665">OSPFv2 <name>Introduction</name>
Extensions</xref>, <xref target="RFC8666">OSPFv3 Extensions</xref>, <t>Four routing protocol extensions -- <xref target="RFC8665" format="defa
<xref target="RFC8667">IS-IS Extensions</xref>, <xref ult">OSPFv2
target="RFC8669">BGP Prefix Segment Identifiers (Prefix-SIDs)</xref> and Extensions</xref>, <xref target="RFC8666" format="default">OSPFv3 Extensio
one <xref target="RFC8664">Path Computation Element Communication ns</xref>,
<xref target="RFC8667" format="default">IS-IS Extensions</xref>, and <xref
target="RFC8669" format="default">BGP Prefix Segment Identifiers (Prefix-SIDs)<
/xref> -- and
one <xref target="RFC8664" format="default">Path Computation Element Commu
nication
Protocol (PCEP) Extension</xref> have been defined to be able to Protocol (PCEP) Extension</xref> have been defined to be able to
propagate Segment Routing (SR) labels for the MPLS data plane <xref propagate Segment Routing (SR) labels for the MPLS data plane <xref target
target="RFC8660"/>.</t> ="RFC8660" format="default"/>.</t>
<t>Also, <xref target="SR-Traffic-Accounting"/> describes
<t>Also, <xref target="I-D.ali-spring-sr-traffic-accounting"/> describes how IP Flow Information Export (IPFIX) <xref target="RFC7012" format="defa
how IP Flow Information Export <xref target="RFC7012"/> can be leveraged ult"/> can be leveraged
in dimensional data modelling to account traffic to MPLS SR label in dimensional data modeling to account for traffic to MPLS SR label
dimensions within a Segment Routing domain.</t> dimensions within a Segment Routing domain.</t>
<t>In <xref target="RFC7012" format="default"/>, the Information Element (
<t>In <xref target="RFC7012"/>, the Information Element (IE) IE)
mplsTopLabelType(46) identifies which MPLS control plane protocol mplsTopLabelType(46) identifies which MPLS control plane protocol
allocated the top-of-stack label in the MPLS label stack. Section 7.2 of allocated the top-of-stack label in the MPLS label stack.
<xref target="RFC7012"/> creates the <xref target="IANA-IPFIX">"IPFIX Per <xref target="RFC7012" sectionFormat="of" section="7.2"/>, the <xref target
MPLS label type (Value 46)" subregistry</xref> where MPLS label type ="IANA-IPFIX" format="default">"IPFIX
MPLS label type (Value 46)" subregistry</xref> was created, where new MPLS
label type entries
should be added. This document defines new code points to address should be added. This document defines new code points to address
typical use cases that are discussed in Section 2.</t> typical use cases that are discussed in <xref target="MPLS-SR"/>.</t>
</section> </section>
<section anchor="MPLS-SR" numbered="true" toc="default">
<section anchor="MPLS-SR" title="MPLS Segment Routing Top Label Type"> <name>MPLS Segment Routing Top Label Type</name>
<t>By introducing five new code points to the IPFIX IE <t>By introducing five new code points to the IPFIX IE
mplsTopLabelType(46) for PCE, IS-IS, OSPFv2, OSPFv3 and BGP Prefix-SID, mplsTopLabelType(46) for Path Computation Element (PCE), IS-IS, OSPFv2, OS PFv3, and BGP Prefix-SIDs,
it is possible to identify which traffic is being forwarded based upon it is possible to identify which traffic is being forwarded based upon
which MPLS SR control plane protocol is in use.</t> which MPLS SR control plane protocol is in use.</t>
<t>A typical use case is to monitor MPLS control plane migrations from <t>A typical use case is to monitor MPLS control plane migrations from
LDP to IS-IS or OSPF Segment Routing. Such a migration can be done node LDP to IS-IS or OSPF Segment Routing. Such a migration can be done node
by node as described in Appendix A of <xref target="RFC8661"/>.</t> by node as described in <xref target="RFC8661" sectionFormat="of" section=
"A"/>.</t>
<t>Another use case is to monitor MPLS control plane migrations from <t>Another use case is to monitor MPLS control plane migrations from
dynamic BGP labels <xref target="RFC8277"/> to BGP Prefix-SIDs <xref dynamic BGP labels <xref target="RFC8277" format="default"/> to BGP Prefix
target="RFC8669"/>. For example, the motivation and benefits for such a -SIDs <xref target="RFC8669" format="default"/>. For example, the motivation for
migration in large-scale data centers are described in <xref , and benefits of, such a
target="RFC8670"/>.</t> migration in large-scale data centers are described in <xref target="RFC86
70" format="default"/>.</t>
<t>Both use cases can be verified by using mplsTopLabelType(46), <t>Both use cases can be verified by using mplsTopLabelType(46),
mplsTopLabelIPv4Address(47), mplsTopLabelIPv6Address(140), mplsTopLabelIPv4Address(47), mplsTopLabelIPv6Address(140),
mplsTopLabelStackSection(70) and forwardingStatus(89) IEs to infer</t> mplsTopLabelStackSection(70), and forwardingStatus(89) IEs to infer</t>
<ul spacing="normal">
<t><list style="symbols"> <li>how many packets are forwarded or dropped</li>
<t>how many packets are forwarded or dropped</t> <li>if packets are dropped, for which reasons, and</li>
<li>the MPLS provider edge loopback address and label protocol</li>
<t>if dropped, for which reasons, and</t> </ul>
<t>By looking at the MPLS label value itself, it is not always clear
<t>the MPLS provider edge loopback address and label protocol</t>
</list></t>
<t>By looking at the MPLS label value itself, it is not always clear as
to which label protocol it belongs. This is because they may share the to which label protocol it belongs. This is because they may share the
same label allocation range. This is, for example, the case for same label allocation range. This is, for example, the case for
IGP-Adjacency SIDs, LDP and dynamic BGP labels.</t> IGP-Adjacency SIDs, LDP, and dynamic BGP labels.</t>
</section> </section>
<section anchor="IANA" numbered="true" toc="default">
<name>IANA Considerations</name>
<t>IANA has allocated the following code points in
the "IPFIX MPLS label type (Value 46)" subregistry within the
"IPFIX Information Elements" registry <xref target="RFC7012" format="defau
lt"/>. See
<xref target="IANA-IPFIX" format="default"/>.</t>
<section anchor="IANA" title="IANA Considerations"> <table anchor="ipfix-reg-updates">
<t>This document requests IANA to allocate the following code points in <name>Updates to "IPFIX MPLS label type (Value 46)" Subregistry</name>
the existing subregistry "IPFIX MPLS label type (Value 46)" under the <thead>
"IPFIX Information Elements" registry <xref target="RFC7012"/> available <tr>
at <xref target="IANA-IPFIX"/>.</t> <th>Value</th>
<th>Description</th>
<t><figure> <th>Reference</th>
<artwork align="center"><![CDATA[ </tr>
</thead>
+-------+--------------------------------+----------------------+ <tbody>
| Value | Description | Reference | <tr>
+-------+--------------------------------+----------------------+ <td>6</td>
| TBD1 | Path Computation Element | [RFC-to-be], RFC8664 | <td>Path Computation Element</td>
+-------+--------------------------------+----------------------+ <td>RFC 9160, RFC 8664</td>
| TBD2 | OSPFv2 Segment Routing | [RFC-to-be], RFC8665 | </tr>
+-------+--------------------------------+----------------------+ <tr>
| TBD3 | OSPFv3 Segment Routing | [RFC-to-be], RFC8666 | <td>7</td>
+-------+--------------------------------+----------------------+ <td>OSPFv2 Segment Routing</td>
| TBD4 | IS-IS Segment Routing | [RFC-to-be], RFC8667 | <td>RFC 9160, RFC 8665</td>
+-------+--------------------------------+----------------------+ </tr>
| TBD5 | BGP Segment Routing Prefix-SID | [RFC-to-be], RFC8669 | <tr>
+-------+--------------------------------+----------------------+ <td>8</td>
<td>OSPFv3 Segment Routing</td>
Table 1: Updates to "IPFIX MPLS label type (Value 46)" subregistry <td>RFC 9160, RFC 8666</td>
]]></artwork> </tr>
</figure></t> <tr>
<td>9</td>
<t>Note to the RFC-Editor:</t> <td>IS-IS Segment Routing</td>
<td>RFC 9160, RFC 8667</td>
<t><list style="symbols"> </tr>
<t>Please replace TBD1 - TBD5 with the values allocated by IANA</t> <tr>
<td>10</td>
<t>Please replace the [RFC-to-be] with the RFC number assigned to <td>BGP Segment Routing Prefix-SID</td>
this document</t> <td>RFC 9160, RFC 8669</td>
</list></t> </tr>
</tbody>
<t>Note IANA:</t> </table>
<t><list style="symbols"> <t>References to RFCs 4364, 4271, and 5036 have been added to the
<t>Suggest to move the existing RFC references in the additional "Reference" column in the "IPFIX MPLS label type (Value 46)" subregistry
information column of IE mplsTopLabelType(46) to reference column [IANA-IPFIX] for code points 3, 4, and 5, respectively. Previously, these
for codepoint 3, 4 and 5.</t> references appeared in the "Additional Information" column for mplsTopLabelTyp
</list></t> e(46)
in the "IPFIX Information Elements" registry <xref target="IANA-IPFIX"/>.</t>
</section> </section>
<section anchor="Operational" numbered="true" toc="default">
<name>Operational Considerations</name>
<section anchor="Operational" title="Operational Considerations"> <t>In the IE mplsTopLabelType(46), BGP code point 4 refers to the
<t>In the IE mplsTopLabelType(46), the BGP code point 4 refers to the label value in the MP_REACH_NLRI path attribute described in <xref target=
label value in MP_REACH_NLRI path attribute described in Section 2 of "RFC8277" sectionFormat="of" section="2"/>, while BGP Segment Routing Prefix-SID
<xref target="RFC8277"/>, while the BGP Segment Routing Prefix-SID code code
point TBD5 corresponds to the label index value in the Label-Index TLV point 10 corresponds to the label index value in the Label-Index TLV
described in Section 3.1 of <xref target="RFC8669"/>. These values are described in <xref target="RFC8669" sectionFormat="of" section="3.1"/>. Th
ese values are
thus used for those distinct purposes.</t> thus used for those distinct purposes.</t>
</section> </section>
<section anchor="Security" numbered="true" toc="default">
<section anchor="Security" title="Security Considerations"> <name>Security Considerations</name>
<t>There exists no significant extra security considerations regarding <t>There exist no significant extra security considerations regarding
the allocation of these new IPFIX IEs compared to <xref the allocation of these new IPFIX IEs as compared to <xref target="RFC7012
target="RFC7012"/>.</t> " format="default"/>.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>I would like to thank the IE doctors, Paul Aitken and Andrew Feren,
as well Benoit Claise, Loa Andersson, Tianran Zhou, Pierre Francois,
Bruno Decreane, Paolo Lucente, Hannes Gredler, Ketan Talaulikar, Sabrina
Tanamal, Erik Auerswald, Sergey Fomin, Mohamed Boucadair, Tom Petch, Qin
Wu and Matthias Arnold for their review and valuable comments. Many
thanks also to Robert Wilton for the AD review. Thanks to Alvaro Retana,
Eric Vyncke and Benjamin Kaduk for the IESG review.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References">
<?rfc include='reference.RFC.7012'?>
</references>
<references title="Informative References">
<?rfc include='reference.I-D.ali-spring-sr-traffic-accounting'?>
<?rfc include='reference.RFC.8277'?>
<?rfc include='reference.RFC.8660'?>
<?rfc include='reference.RFC.8661'?>
<?rfc include='reference.RFC.8664'?>
<?rfc include='reference.RFC.8665'?>
<?rfc include='reference.RFC.8666'?>
<?rfc include='reference.RFC.8667'?> <references>
<name>References</name>
<?rfc include='reference.RFC.8669'?> <references>
<name>Normative References</name>
<?rfc include='reference.RFC.8670'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.7012.xml"/>
</references>
<references>
<name>Informative References</name>
<reference anchor="IANA-IPFIX" <!-- draft-ali-spring-sr-traffic-accounting (I-D Exists) -->
target="https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfi <reference anchor="SR-Traffic-Accounting">
x-mpls-label-type"> <front>
<front> <title>Traffic Accounting in Segment Routing Networks</title>
<title>IANA, IPFIX MPLS label type (Value 46)</title> <author initials='Z' surname='Ali' fullname='Zafar Ali'>
<organization/></author>
<author initials='C' surname='Filsfils' fullname='Clarence Filsfils'>
<organization/></author>
<author initials='K' surname='Talaulikar' fullname='Ketan Talaulikar'>
<organization/></author>
<author initials='S' surname='Sivabalan' fullname='Siva Sivabalan'>
<organization/></author>
<author initials='M' surname='Horneffer' fullname='Martin Horneffer'>
<organization/></author>
<author initials='R' surname='Raszuk' fullname='Robert Raszuk'>
<organization/></author>
<author initials='S' surname='Litkowski' fullname='Stephane Litkowski'>
<organization/></author>
<author initials='D' surname='Voyer' fullname='Dan Voyer'>
<organization/></author>
<author initials='R' surname='Morton' fullname='Rick Morton'>
<organization/></author>
<author initials='G' surname='Dawra' fullname='Gaurav Dawra'>
<organization/></author>
<date year='2021' month='November' day='13' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ali-spring-sr-traffic-accounting-
06'/>
</reference>
<author/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8277.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8660.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8661.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8664.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8665.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8666.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8667.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8669.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8670.xml"/>
<date/> <reference anchor="IANA-IPFIX" target="https://www.iana.org/assignments/
</front> ipfix/">
</reference> <front>
<title>IPFIX MPLS label type (Value 46)</title>
<author><organization>IANA</organization></author>
<date/>
</front>
</reference>
</references>
</references> </references>
<section anchor="Acknowledgements" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>I would like to thank the IE doctors, <contact fullname="Paul Aitken"/>
and <contact fullname="Andrew Feren"/>,
as well as <contact fullname="Benoît Claise"/>, <contact fullname="Loa And
ersson"/>, <contact fullname="Tianran Zhou"/>, <contact fullname="Pierre Françoi
s"/>,
<contact fullname="Bruno Decraene"/>, <contact fullname="Paolo Lucente"/>,
<contact fullname="Hannes Gredler"/>, <contact fullname="Ketan Talaulikar"/>, <
contact fullname="Sabrina Tanamal"/>, <contact fullname="Erik Auerswald"/>, <con
tact fullname="Sergey Fomin"/>, <contact fullname="Mohamed Boucadair"/>, <contac
t fullname="Tom Petch"/>, <contact fullname="Qin Wu"/>, and <contact fullname="M
atthias Arnold"/> for their review and valuable comments. Many
thanks also to <contact fullname="Robert Wilton"/> for the AD review. Than
ks to <contact fullname="Alvaro Retana"/>,
<contact fullname="Éric Vyncke"/>, and <contact fullname="Benjamin Kaduk"/
> for the IESG review.</t>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 36 change blocks. 
167 lines changed or deleted 223 lines changed or added

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