<?xml version='1.0' ?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2863 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2863.xml">
<!ENTITY RFC5309 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5309.xml">
<!ENTITY RFC7224 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">
<!ENTITY RFC8340 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml">
]>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<rfc docName="draft-liu-lsr-p2poverlan-07" ipr="trust200902" category="info">
	<front>
		<title abbrev='IfStackTable for P2poverLAN interface'>Interface Stack Table Definition and Example for Point-to-Point (P2P) Interface over LAN</title>
		<author initials="D." surname="Liu" fullname="Daiying Liu">
			<organization>Ericsson</organization>
			<address>
				<postal>
					<street>No.5 Lize East 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="February" day="11"/>
		<area>General</area>
		<keyword>RFC</keyword>
		<keyword>Internet-Draft</keyword>
		<keyword>XML</keyword>
		<keyword>Extensible Markup Language</keyword>
		<abstract>
			<t>RFC 5309 defines the Point-to-Point (P2P) circuit type, one of the two circuit types used in the link state routing protocols,
				 and highlights that it is important to identify the correct circuit type when forming adjacencies, flooding 
         link state database packets, and monitoring the link state.
      </t>
      <t>
         The P2P interface over LAN ifType value 303, has been assigned by IANA Expert Review, and this document requests IANA to add this document as a reference to ifType 303.
         This document provides advice about the ifStack for the P2P interface over LAN ifType
         to facilitate operational control, maintenance and statistics. 
			</t>
		</abstract>
	</front>







	<middle>
		<section title="Introduction">
			<t><xref target="RFC5309"/> defines the P2P circuit type and highlights that it is important to identify the correct circuit type
				 when forming adjacencies, flooding link state database packets, and monitoring the link state.
      </t>
      <t>The assignment of 303, as the value for p2pOverLan ifType was made by Expert Review <xref target="Assignment"/>.
      	 This document requests IANA to add this document as a reference to ifType 303.
      </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 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 need to explicitly configure the P2P interface in routing protocols).
      </t>
      <t>It is helpful to map the P2P interface over LAN type in the interface management stack table. 
      	 And if no entry specifies the P2P interface lower layer, the management suffers 
      	 loses the ability to get to the lower layer specific management properties via many tools.
      </t>
      <t>The purpose of this document is to suggest how to use ifStackTable for the P2P interface over LAN type, and provide examples.
      </t>
    </section>





    <section title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
         "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
         document are to be interpreted as described in <xref target="RFC2119"/> <xref target="RFC8174"/>.
      </t>
    </section>





    <section title="Interface Stack Table for P2P Interface Type">
    	<t>If a device implements the IF-MIB <xref target="RFC2863"/>, each entry in the
         "/interfaces/interface" list (in "Interface Management YANG") in the operational state is typically
         mapped to one ifEntry as required in <xref target="RFC8343"/>, therefore the P2P interface over LAN type 
         should also be fully mapped to one ifEntry by defining the "ifStackTable" ("higher-layer-if" and "lower-layer-if").
    	</t>
    	<t>The P2P interface higher layer SHOULD be network layer "ipForward" 
    	   (defined in IANA) 
    	   to run routing protocol, 
    		 the P2P interface lower layer SHOULD be link data layer "ethernetCsmacd" (defined in IANA).
    	</t>
    	<t>The P2P interface type ifStackTable can be defined along the lines of following example which complies with <xref target="RFC8343"/>
    		 <xref target="RFC6991"/> <xref target="RFC8340"/>:
    	</t>
    	<figure align="center" anchor="xml_happy_2">
        <artwork align="center"><![CDATA[
          <CODE BEGINS>

          <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>
      </figure>
    </section>




    <section title="Security Considerations">
      <t>The interface stack table specified in this document is read-only.
      	 Read operation to this table should not have a negative
         effect on network operations.
      </t>
    </section>



    <section title="IANA Considerations">
    	<t>In the Interface Types registry, IANA has assigned a value of 303 
    		 for p2pOverLan <xref target="Assignment"/> with a reference of <xref target="RFC5309"/>.
    		 IANA is requested to amend the reference for that code point to be to this document 
    		 and to make a similar amendment in the YANG iana-if-type module (originally specified in 
    		 <xref target="RFC7224"/>) which currently points to <xref target="RFC8561"/>, 
    		 as this document explains how the ifType is to be used.
    	</t>
    </section>
	</middle>








	<back>
		<references title="Normative references">
      &RFC2119;
      &RFC2863;
      &RFC5309;
      &RFC7224;
      &RFC8174;
      &RFC8343;
      &RFC8561;
		</references>










		<references title="Informative References">
      <reference anchor="Assignment" target="https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-5">
				<front>
					<title>Interface Types (ifType)</title><author/><date/></front>
			</reference>
      &RFC6991;
      &RFC8340;
		</references>
	</back>
</rfc>