| Internet-Draft | IfStackTable for P2poverLAN interface | June 2021 |
| Liu, et al. | Expires 1 January 2022 | [Page] |
In [RFC5309] defines the Point to Point (P2P) circuit type is one of the mainly used circuit types in link state routing protocol, and highlights it is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and monitor the link state.¶
Point to Point (P2P) Interface over LAN ifType value is assigned by IANA experts review. This document provides an example of the ifStack for Point to Point (P2P) Interface over LAN ifType to facilitate operational control, maintenance and statistics.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 3 December 2021.¶
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The assignment of a value (303, available at https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-5) to p2pOverLan ifType was made by expert review. To simplify configuration and operational control, it is helpful to represent the fact that an interface is to be considered a Point to Point (P2P) Interface over LAN type explicitly in the interface stack. This enables, for example, routing protocols to automatically inherit the correct operating mode from interface stack without further configuration(Not need to explicitly configure Point to Point Interface in routing protocols).¶
So it is helpful to map Point to Point (P2P) Interface over LAN type in interface management stack table. And if no entry specify Point to Point (P2P) Interface lower layer, the management will suffer since lose the ability to get to the lower layer specific management properties via many tools.¶
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 [RFC2119] [RFC8174].¶
If the device implements the IF-MIB [RFC2863], each entry in the "/interfaces/interface" list (in "Interface Management YANG") in the operational state is typically mapped to one ifEntry is required in [RFC8343], therefore Point to Point (P2P) Interface over LAN type should also fully map to one ifEntry by defining the "ifStackTable" ("higher-layer-if" and "lower-layer-if").¶
Point to Point (P2P) interface higher layer should be network layer "ipForward" (defined in IANA) to run routing protocol, Point to Point (P2P) interface lower layer is link data layer "ethernetCsmacd" (defined in IANA).¶
Point to Point (P2P) interface type ifStackTable can be defined along the lines of following example which complies with [RFC8343]:¶
<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>
The interface stack table specified in this document is read-only. Read operation to this table without complete protection shouldn't have a negative effect on network operations.¶
In the Interface Types registry, IANA has previously assigned a value of 303 for p2pOverLan with a reference of [RFC5309], as shown in following table (available at https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-5). IANA is requested to amend the reference to point to this document and to make a similar amendment in the YANG iana-if-type module [RFC7224] which currently points to [RFC8561], as this document explains how the ifType is to be used.¶
+=========+==================+==================+ | Decimal | Name | references | +=========+==================+==================+ | 303 | p2pOverLan | RFC5309 | +---------+------------------+------------------+