Internet-Draft IfStackTable for P2P interface June 2021
Liu, et al. Expires 19 December 2021 [Page]
Network Working Group
Intended Status:
D. Liu
J. Halpern
C. Zhang

Interface Stack Table Definition for Point to Point (P2P) Interface over LAN


The point-to-point circuit type is one of the mainly used circuit types in link state routing protocol. It is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and monitor the link state. This document defines point-to-point interface type and relevant stack tables to provide benefit for operation, maintenance and statistics.

Status of This Memo

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

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.

Table of Contents

1. Introduction

Point-to-point is the predominant circuit type used by link state routing protocols such as IS-IS [RFC1195] and OSPF [RFC2328] [RFC5340]. Compare with broadcast interface, point-to-point interface is used differently when establish neighbor adjacencies, flood link state information, representing the topology, etc.

To simplify configuration and operation, it is helpful To represent the fact that an interface is to be considered a point-to-point interface explicitly in the interface stack. This enables, for example, routing protocols to automatically use the correct operating mode without further configuration.

So it is necessary to abstract P2P as special sub-type type and define relevant interface stack table. And if no entry saying p2pOverLan layer over ethernet, the management will suffer since lose the ability to get to the Ethernet-specific management properties (Ethernet MIB or YANG model) via many tools.

2. Requirements Language

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].

3. Relationship to the IF-MIB and Interfaces YANG Module

As defined in [RFC8343], if the device implements the IF-MIB [RFC2863], each entry in the "/interfaces/interface" list in the operational state is typically mapped to one ifEntry.

So P2P as sub-interface type should also fully map to one ifEntry, meanwhile define the "higher-layer-if" and "lower-layer-if" in the YANG corresponding to "ifStackTable" in IF-MIB to setup a complete interface stack table, then the P2P interface type can borrow all existing items in interfaces YANG and IF-MIB to take the full advantages from operation, statistic, etc.

The "higher-layer-if" should be a network layer interface type, and the lower-layer-if should be a data link layer interface type.

   | YANG data node in                    | IF-MIB object              |
   | /interfaces/interface                |                            |
   | name                                 | ifName                     |
   | type                                 | ifType                     |
   | description                          | ifAlias                    |
   | admin-status                         | ifAdminStatus              |
   | oper-status                          | ifOperStatus               |
   | last-change                          | ifLastChange               |
   | if-index                             | ifIndex                    |
   | link-up-down-trap-enable             | ifLinkUpDownTrapEnable     |
   | phys-address                         | ifPhysAddress              |
   | higher-layer-if and lower-layer-if   | ifStackTable               |
   | speed                                | ifSpeed and ifHighSpeed    |
   | discontinuity-time                   | ifCounterDiscontinuityTime |
   | in-octets                            | ifHCInOctets               |
   | in-unicast-pkts                      | ifHCInUcastPkts            |
   | in-broadcast-pkts                    | ifHCInBroadcastPkts        |
   | in-multicast-pkts                    | ifHCInMulticastPkts        |
   | in-discards                          | ifInDiscards               |
   | in-errors                            | ifInErrors                 |
   | in-unknown-protos                    | ifInUnknownProtos          |
   | out-octets                           | ifHCOutOctets              |
   | out-unicast-pkts                     | ifHCOutUcastPkts           |
   | out-broadcast-pkts                   | ifHCOutBroadcastPkts       |
   | out-multicast-pkts                   | ifHCOutMulticastPkts       |
   | out-discards                         | ifOutDiscards              |
   | out-errors                           | ifOutErrors                |
Figure 1

YANG Data Nodes and Related IF-MIB Objects

4. Interface Stack Table for P2P Interface Type

P2P interface type is a kind of point-to-point circuit type. P2P interface higher layer should be network layer "ipForward" (defined in IANA) to run routing protocol, P2P interface lower layer is link data layer "ethernetCsmacd" (defined in IANA).

P2P interface type ifStackTable should be defined as the following example:



              <!-- counters now shown here -->
Figure 2

5. Security Considerations

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.

The interface stack table defines to be accessed via network management protocols such as NETCONF [RFC6241], RESTCONF [RFC8040]. The NETCONF is over on layer secure transport, and the mandatory secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446].

6. IANA Considerations

IANA need to update the "Interface Types(ifType)" registry (available at with the following status types:

| Decimal |    Name          |             Description               |
|  303    |  p2pOverLan      |    Point to Point over LAN interface  |
Figure 3

IANA need to update the "IANAifType-MIB" registry (available at with the following status types:

|  Value  |    Name          |               Description             |
|  303    |  p2pOverLan      |  Point to Point over LAN interface    |
Figure 4

IANA need to update the "iana-if-type YANG Module" registry (available at with the following status types:

                identity p2pOverLan {
                  base iana-interface-type;
                    "Point to Point over LAN interface.";
Figure 5

7. References

7.1. Normative references

Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <>.
McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, DOI 10.17487/RFC2863, , <>.
Zinin, A. and N. Shen, "Point-to-Point Operation over LAN in Link State Routing Protocols", RFC 5309, DOI 10.17487/RFC5309, , <>.
Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", , <>.
Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, , <>.
Moy, J., "OSPF Version 2", STD 54, RFC 6242, DOI 10.17487/RFC2328, , <>.
Schoenwaelder, J., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, , <>.
Bjorklund, M., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, , <>.
Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, DOI 10.17487/RFC5340, , <>.
Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, , <>.

7.2. Informative References

Bjorklund, M., "IANA Interface Type YANG Module", RFC 7224, DOI 10.17487/RFC7224, , <>.
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, , <>.

Authors' Addresses

Daiying Liu
No.5 Lize East street
Joel Halpern
Congjie Zhang