<?xml version='1.0'?>encoding='utf-8'?> <!DOCTYPE rfcSYSTEM "rfc2629.dtd"[ <!ENTITYRFC2119 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">nbsp " "> <!ENTITYRFC2863 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2863.xml">zwsp "​"> <!ENTITYRFC5309 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5309.xml">nbhy "‑"> <!ENTITYRFC7224 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7224.xml"> <!ENTITY RFC8174 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <!ENTITY RFC8343 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"> <!ENTITY RFC8561 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8561.xml"> <!ENTITY RFC6991 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml">wj "⁠"> ]><?rfc toc="yes"?> <?rfc symrefs="yes"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-liu-lsr-p2poverlan-12" number="9296" ipr="trust200902"category="info">category="info" obsoletes="" updates="" submissionType="independent" xml:lang="en" tocInclude="true" symRefs="true" version="3" sortRefs="true"> <front> <titleabbrev='IfStackTableabbrev="IfStackTable for P2poverLANinterface'>Interface Stack Table Definition and Exampleinterface">ifStackTable for the Point-to-Point (P2P) Interface overLAN</title>a LAN Type: Definition and Examples</title> <seriesInfo name="RFC" value="9296"/> <author initials="D." surname="Liu" fullname="Daiying Liu"> <organization>Ericsson</organization> <address> <postal> <street>No.5 Lize Eaststreet</street>Street</street> <code>100102</code> <city>Beijing</city> <country>China</country> </postal> <email>harold.liu@ericsson.com</email> </address> </author> <author initials="J." surname="Halpern" fullname="Joel Halpern"> <organization>Ericsson</organization> <address> <email>joel.halpern@ericsson.com</email> </address> </author> <author initials="C." surname="Zhang" fullname="Congjie Zhang"> <organization>Ericsson</organization> <address> <email>congjie.zhang@ericsson.com</email> </address> </author> <date year="2022"month="May" day="24"/> <area>General</area> <keyword>RFC</keyword> <keyword>Internet-Draft</keyword> <keyword>XML</keyword> <keyword>Extensible Markup Language</keyword>month="August"/> <abstract> <t>RFC 5309 defines the Point-to-Point (P2P) circuit type, one of the two circuit types used in thelink statelink-state routing protocols, and highlights that it is important to identify the correct circuit type when forming adjacencies, floodinglink statelink-state database packets, and monitoring the link state. </t> <t> This document provides advice about the ifStack for the P2P interface over a LANifTypeType to facilitate operational control,maintenancemaintenance, and statistics. </t> </abstract> </front> <middle> <sectiontitle="Introduction">numbered="true" toc="default"> <name>Introduction</name> <t><xreftarget="RFC5309"/>target="RFC5309" format="default"/> defines theP2PPoint-to-Point (P2P) circuit type and highlights that it is important to identify the correct circuit type when forming adjacencies, floodinglink statelink-state database packets, and monitoring the link state. </t> <t> To simplify configuration and operational control, it is helpful to represent the fact that an interface is to be considered a P2P interface over a LAN type explicitly in the interface stack. This enables, for example, routing protocols to automatically inherit the correct operating mode from the interface stack without further configuration(No(i.e., there is no need to explicitly configure the P2P interface in routing protocols). </t> <t>It is helpful to map the P2P interface over a LAN type in the interface management stack table. If no entry specifies theP2P interfacelowerlayer,layer of the P2P interface, then management tools lose the ability to retrieve and measure properties specific to lower layers. </t><t>The<t>In standard network management protocols that make use of ifStackTables, the P2P interface over a LAN type is intended to be used solely as a means to signalin standard network management protocols that make use of ifStackTablesthat theupper layerupper-layer interface of link-data layer is a P2Pinterface, and thusinterface. Thus, the upper and lower layers of P2P over a LAN typewill beare expected to apply appropriatesemantics:semantics. In general, the higher layer of a P2P over a LAN typehigher layer SHOULD always<bcp14>SHOULD</bcp14> be "ipForward"(Value 142,(value 142 in <xreftarget="Assignment"/>),target="Assignment" format="default"/>), and the lower layer of P2P over a LAN typelower layer SHOULD<bcp14>SHOULD</bcp14> be any appropriatelink datalink-data layer of "ipForward". </t> <t>The assignment of303,303 as the value for the p2pOverLan ifType was made by Expert Review (see <xreftarget="Assignment"/>. So thetarget="Assignment" format="default"/> and <xref target="RFC8126" format="default"/>). The purpose of this document is torequest IANA to add this documentserve as a referencetofor ifType303, as well as suggest303 by suggesting howto usethe ifStackTable for the P2P interface over a LANtype,type is to be used andprovideproviding examples. </t> <t>It should be noted that this document reflects the operating model used on some routers. Other routers that use different models may not represent a P2P as a separate interface. </t> </section> <sectiontitle="Requirements Language"> <t>Thenumbered="true" toc="default"> <name>Requirements Language</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xreftarget="RFC8174"/>.target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t> </section> <section anchor="sec3"title="Interfacenumbered="true" toc="default"> <name>Interface Stack Table for P2P InterfaceType">Type</name> <section anchor="sec3_1"title="P2P Interfacenumbered="true" toc="default"> <name>P2P Interface: higher-layer-if andlower-layer-if">lower-layer-if</name> <t>If a device implements the IF-MIB <xreftarget="RFC2863"/>,target="RFC2863" format="default"/>, then each entry in the "/interfaces/interface" list(in "Interface Management YANG")(see "A YANG Data Model for Interface Management" <xref target="RFC8343" format="default"/>) in the operational state is typically mapped to one ifEntry as required in <xreftarget="RFC8343"/>. Thereforetarget="RFC8343" format="default"/>. Therefore, the P2P interface over a LAN type should also be fully mapped to one ifEntry by defining the "ifStackTable" ("higher-layer-if" and "lower-layer-if", defined in <xreftarget="RFC8343"/>).target="RFC8343" format="default"/>). </t> <t>InifStackTablethe ifStackTable, the higher layer of the P2P interface over a LAN typehigher layer SHALL<bcp14>SHALL</bcp14> be network layer "ipForward" to enable IP routing, and the lower layer of the P2P interface over a LAN typelower layer SHOULD<bcp14>SHOULD</bcp14> be anylink datalink-data layer that can be bound to"ipForward""ipForward", including "ethernetCsmacd", "ieee8023adLag", "l2vlan", and so on (defined inIANA).the iana-if-type YANG module <xref target="IANA-ifTYPE" format="default"/>). </t> <t>The P2P interface over the LAN type ifStackTable can be defined along the lines of the followingexample (Inexample, which complies with <xref target="RFC8343" format="default"/> and <xref target="RFC6991" format="default"/>. In the example, "lower-layer-if" takes"ethernetCsmacd" but"ethernetCsmacd", but, in fact, "lower-layer-if" can be any other availablelink datalink-data layer. See <xreftarget="sec7"/>target="sec7" format="default"/> for moreexamples) which complies with <xref target="RFC8343"/> <xref target="RFC6991"/>:examples. </t> <figurealign="center"anchor="xml_happy_1"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>isis_int</name> <type>ianaift:ipForward</type> </interface> <interface> <name>eth1</name> <type>ianaift:ethernetCsmacd</type> </interface> <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1</lower-layer-if> <enabled>false</enabled> <admin-status>down</admin-status> <oper-status>down</oper-status> <statistics> <discontinuity-time> 2021-04-01T03:00:00+00:00 </discontinuity-time> <!-- counters now shown here --> </statistics> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure> </section> <section anchor="sec3_2"title="P2Pnumbered="true" toc="default"> <name>P2P InterfaceStatistics">Statistics</name> <t>Because multiple IP interfaces can be bound to one physical port, the statistics on the physical portSHOULD<bcp14>SHOULD</bcp14> be a complete setwhichthat includes statistics of allupper layerupper-layer interfaces. Therefore, eachp2pP2P interface collects and displays traffic that has been sent to it via higher layers or received from it via lower layers. </t> </section> <section anchor="sec3_3"title="P2Pnumbered="true" toc="default"> <name>P2P Interface AdministrativeState">State</name> <t>The P2P interface can beshutdownshut down independently of the underlying interface. </t> <t>If the P2P interface is administratively up, then the"oper-status", defined"oper-status" (defined in <xreftarget="RFC8343"/>,target="RFC8343" format="default"/>) of that interfaceSHALL<bcp14>SHALL</bcp14> fully reflect the state of the underlying interface; if the P2P interface is administratively down, then the "oper-status" of that interfaceSHALL<bcp14>SHALL</bcp14> be down. Examples can be found in <xreftarget="sec7"/>.target="sec7" format="default"/>. </t> </section> </section> <sectiontitle="Security Considerations">numbered="true" toc="default"> <name>Security Considerations</name> <t>Thewriteablewritable attribute "admin-status" of the p2povervlan ifType is inherited from <xreftarget="RFC8343"/>.target="RFC8343" format="default"/>. Other objects associated with the p2povervlan ifType are read-only. With this in mind, the considerations discussedSection 7 of [RFC8343]in <xref target="RFC8343" sectionFormat="of" section="7"/> otherwise apply to the p2povervlan ifType. </t> </section> <sectiontitle="IANA Considerations">numbered="true" toc="default"> <name>IANA Considerations</name> <t>In theInterface"Interface Types (ifType)" registry,IANA has assigned avalueof303foris assigned to p2pOverLan <xreftarget="Assignment"/> with a reference of <xref target="RFC5309"/>. IANAtarget="Assignment" format="default"/>. As this document explains how the p2pOverLan (303) ifType isrequestedtoamendbe used, IANA has amended the reference forthat code pointp2pOverLan (303) tobepoint to this document (instead of <xref target="RFC5309" format="default"/>) andto makemade a similar amendment in the YANG iana-if-type module <xref target="IANA-ifTYPE" format="default"/> (originally specified in <xreftarget="RFC7224"/>) which currently points to <xref target="RFC8561"/>, as this document explains how the ifType is to be used.target="RFC7224" format="default"/>). </t> </section><section anchor="sec8" title="Acknowledgements"> <t>The authors would like to thank Rob Wilton for his reviews and valuable comments and suggestions.</t> </section></middle> <back><references title="Normative references"> &RFC2119; &RFC2863; &RFC5309; &RFC7224; &RFC8174; &RFC8343; &RFC8561;<references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2863.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5309.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7224.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"/> <!-- <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8561.xml"/>--> </references><references title="Informative References"><references> <name>Informative References</name> <reference anchor="Assignment"target="https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-5">target="https://www.iana.org/assignments/smi-numbers"> <front> <title>Interface Types(ifType)</title><author/><date/></front>(ifType)</title> <author><organization>IANA</organization></author> </front> </reference> <reference anchor="IANA-ifTYPE" target=" https://www.iana.org/assignments/yang-parameters"> <front> <title>YANG Module Names</title> <author><organization>IANA</organization></author> </front> </reference>&RFC6991;<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> </references> </references> <section anchor="sec7"title="Examples"> <t>Innumbered="true" toc="default"> <name>Examples</name> <t>If thecase ofunderlying interface is a VLAN sub-interface, the ifStackTable should be defined as: </t> <figurealign="center"anchor="xml_happy_2"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>isis_int</name> <type>ianaift:ipForward</type> </interface> <interface> <name>eth1_valn1</name> <type>ianaift:l2vlan</type> </interface> <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1_valn1</lower-layer-if> <enabled>false</enabled> <admin-status>down</admin-status> <oper-status>down</oper-status> <statistics> <discontinuity-time> 2021-04-01T03:00:00+00:00 </discontinuity-time> <!-- counters now shown here --> </statistics> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure><t>In<t>If thecase ofunderlying interface isLAG,Link Aggregation Group (LAG), the ifStackTable should be defined as: </t> <figurealign="center"anchor="xml_happy_3"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>isis_int</name> <type>ianaift:ipForward</type> </interface> <interface> <name>eth1_lag1</name> <type>ianaift:ieee8023adLag</type> </interface> <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1_lag1</lower-layer-if> <enabled>false</enabled> <admin-status>down</admin-status> <oper-status>down</oper-status> <statistics> <discontinuity-time> 2021-04-01T03:00:00+00:00 </discontinuity-time> <!-- counters now shown here --> </statistics> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure><t>In<t>If thecase ofP2P interface and underlying interface are both administrativelyup,up and the underlying interface operational status is up: </t> <figurealign="center"anchor="xml_happy_4"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1</lower-layer-if> <admin-status>up</admin-status> <oper-status>up</oper-status> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure><t>In<t>If thecase ofP2P interface and underlying interface are administrativelyup,up but the underlying interface operational status is down: </t> <figurealign="center"anchor="xml_happy_5"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1</lower-layer-if> <admin-status>up</admin-status> <oper-status>down</oper-status> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure><t>In<t>If thecase ofP2P interface is administratively down: </t> <figurealign="center"anchor="xml_happy_6"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1</lower-layer-if> <admin-status>down</admin-status> <oper-status>down</oper-status> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure><t>In<t>If thecase ofP2P interface is administratively up but the underlying interface is administratively down: </t> <figurealign="center"anchor="xml_happy_7"><artwork align="center"><![CDATA[ <CODE BEGINS><sourcecode name="" type="" markers="true"><![CDATA[ <interface> <name>p2p</name> <type>ianaift:p2pOverLan</type> <higher-layer-if>isis_int</higher-layer-if> <lower-layer-if>eth1</lower-layer-if> <admin-status>up</admin-status> <oper-status>down</oper-status> </interface><CODE ENDS> ]]></artwork>]]></sourcecode> </figure> </section> <section anchor="sec8" numbered="false" toc="default"> <name>Acknowledgements</name> <t>The authors would like to thank <contact fullname="Rob Wilton"/> for his reviews and valuable comments and suggestions.</t> </section> </back> </rfc>