idnits 2.17.1 draft-liu-lsr-p2poverlan-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (11 February 2022) is 802 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Liu 3 Internet-Draft J. Halpern 4 Intended status: Informational C. Zhang 5 Expires: 15 August 2022 Ericsson 6 11 February 2022 8 Interface Stack Table Definition and Example for Point-to-Point (P2P) 9 Interface over LAN 10 draft-liu-lsr-p2poverlan-07 12 Abstract 14 RFC 5309 defines the Point-to-Point (P2P) circuit type, one of the 15 two circuit types used in the link state routing protocols, and 16 highlights that it is important to identify the correct circuit type 17 when forming adjacencies, flooding link state database packets, and 18 monitoring the link state. 20 The P2P interface over LAN ifType value 303, has been assigned by 21 IANA Expert Review, and this document requests IANA to add this 22 document as a reference to ifType 303. This document provides advice 23 about the ifStack for the P2P interface over LAN ifType to facilitate 24 operational control, maintenance and statistics. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on 15 August 2022. 43 Copyright Notice 45 Copyright (c) 2022 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 50 license-info) in effect on the date of publication of this document. 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. Code Components 53 extracted from this document must include Revised BSD License text as 54 described in Section 4.e of the Trust Legal Provisions and are 55 provided without warranty as described in the Revised BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 61 3. Interface Stack Table for P2P Interface Type . . . . . . . . 3 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 6.1. Normative references . . . . . . . . . . . . . . . . . . 4 66 6.2. Informative References . . . . . . . . . . . . . . . . . 5 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 69 1. Introduction 71 [RFC5309] defines the P2P circuit type and highlights that it is 72 important to identify the correct circuit type when forming 73 adjacencies, flooding link state database packets, and monitoring the 74 link state. 76 The assignment of 303, as the value for p2pOverLan ifType was made by 77 Expert Review [Assignment]. This document requests IANA to add this 78 document as a reference to ifType 303. 80 To simplify configuration and operational control, it is helpful to 81 represent the fact that an interface is to be considered a P2P 82 interface over LAN type explicitly in the interface stack. This 83 enables, for example, routing protocols to automatically inherit the 84 correct operating mode from the interface stack without further 85 configuration (No need to explicitly configure the P2P interface in 86 routing protocols). 88 It is helpful to map the P2P interface over LAN type in the interface 89 management stack table. And if no entry specifies the P2P interface 90 lower layer, the management suffers loses the ability to get to the 91 lower layer specific management properties via many tools. 93 The purpose of this document is to suggest how to use 94 ifStackTable for the P2P interface over LAN type, and provide 95 examples. 97 2. Requirements Language 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in [RFC2119] [RFC8174]. 103 3. Interface Stack Table for P2P Interface Type 105 If a device implements the IF-MIB [RFC2863], each entry in the 106 "/interfaces/interface" list (in "Interface Management YANG") in the 107 operational state is typically mapped to one ifEntry as required in 108 [RFC8343], therefore the P2P interface over LAN type should also be 109 fully mapped to one ifEntry by defining the "ifStackTable" ("higher- 110 layer-if" and "lower-layer-if"). 112 The P2P interface higher layer SHOULD be network layer "ipForward" 113 (defined in IANA) to run routing protocol, the P2P interface lower 114 layer SHOULD be link data layer "ethernetCsmacd" (defined in IANA). 116 The P2P interface type ifStackTable can be defined along the lines of 117 following example which complies with [RFC8343] [RFC6991] [RFC8340]: 119 120 121 isis_int 122 ianaift:ipForward 123 125 126 eth1 127 ianaift:ethernetCsmacd 128 130 131 p2p 132 ianaift:p2pOverLan 133 isis_int 134 eth1 135 false 136 down 137 down 138 139 140 2021-04-01T03:00:00+00:00 141 142 143 144 145 147 Figure 1 149 4. Security Considerations 151 The interface stack table specified in this document is read-only. 152 Read operation to this table should not have a negative effect on 153 network operations. 155 5. IANA Considerations 157 In the Interface Types registry, IANA has assigned a value of 303 for 158 p2pOverLan [Assignment] with a reference of [RFC5309]. IANA is 159 requested to amend the reference for that code point to be to this 160 document and to make a similar amendment in the YANG iana-if-type 161 module (originally specified in [RFC7224]) which currently points to 162 [RFC8561], as this document explains how the ifType is to be used. 164 6. References 166 6.1. Normative references 168 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 169 Requirement Levels", BCP 14, RFC 2119, 170 DOI 10.17487/RFC2119, March 1997, 171 . 173 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 174 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 175 . 177 [RFC5309] Shen, N., Ed. and A. Zinin, Ed., "Point-to-Point Operation 178 over LAN in Link State Routing Protocols", RFC 5309, 179 DOI 10.17487/RFC5309, October 2008, 180 . 182 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 183 RFC 7224, DOI 10.17487/RFC7224, May 2014, 184 . 186 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 187 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 188 May 2017, . 190 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 191 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 192 . 194 [RFC8561] Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. 195 Vaupotic, "A YANG Data Model for Microwave Radio Link", 196 RFC 8561, DOI 10.17487/RFC8561, June 2019, 197 . 199 6.2. Informative References 201 [Assignment] 202 "Interface Types (ifType)", 203 . 206 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 207 RFC 6991, DOI 10.17487/RFC6991, July 2013, 208 . 210 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 211 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 212 . 214 Authors' Addresses 215 Daiying Liu 216 Ericsson 217 No.5 Lize East street 218 Beijing 219 100102 220 China 222 Email: harold.liu@ericsson.com 224 Joel Halpern 225 Ericsson 227 Email: joel.halpern@ericsson.com 229 Congjie Zhang 230 Ericsson 232 Email: congjie.zhang@ericsson.com