idnits 2.17.1 draft-fox-lsr-ospf-terminology-01.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 (Using the creation date from RFC2328, updated by this document, for RFC5378 checks: 1997-11-05) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (3 March 2022) is 778 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Link State Routing M. Fox 3 Internet-Draft IBM 4 Updates: 2328 5340 (if approved) A. Lindem 5 Intended status: Standards Track Cisco Systems 6 Expires: 4 September 2022 A. Retana 7 Futurewei Technologies, Inc. 8 3 March 2022 10 Update to OSPF Terminology 11 draft-fox-lsr-ospf-terminology-01 13 Abstract 15 This document updates some OSPF terminology to be in line with 16 inclusive language used in the industry. 18 This document updates RFC2328 and RFC5340. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on 4 September 2022. 37 Copyright Notice 39 Copyright (c) 2022 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 44 license-info) in effect on the date of publication of this document. 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. Code Components 47 extracted from this document must include Revised BSD License text as 48 described in Section 4.e of the Trust Legal Provisions and are 49 provided without warranty as described in the Revised BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Update to RFC2328 . . . . . . . . . . . . . . . . . . . . . . 2 55 3. Update to RFC5340 . . . . . . . . . . . . . . . . . . . . . . 3 56 4. Other RFCs With References . . . . . . . . . . . . . . . . . 3 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 8.2. Informative References . . . . . . . . . . . . . . . . . 4 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 This document updates some OSPF terminology to be in line with 68 inclusive language used in the industry. 70 This document updates [RFC2328] and [RFC5340]. 72 2. Update to RFC2328 74 The base OSPFv2 specification [RFC2328] defines the synchronization 75 of databases as two routers froming a "master/slave relationship". 76 All instances of these terms are replaced by leader/follower, 77 respectively. 79 The Master (MS) bit in the database description packet is renamed the 80 Leader (L) bit. 82 The operation of OSPFv2 is not modified. The Leader/Follower 83 terminology and Leader (L) Bit definition changes impact the 84 following sections: 7.2 "The Synchronization of Databases", 10 "The 85 Neighbor Data Structures", 10.1 "Neighbor states", 10.2 "Events 86 causing neighbor state changes", 10.6 "Receiving Database Description 87 Packets", 10.8 "Sending Database Description Packets", 10.10 "An 88 Example", and A.3.3 "The Database Description packet". 90 3. Update to RFC5340 92 The base OSPFv3 specification [RFC5340] defines the database 93 description process between two routers as one being "designated to 94 be the master and the other is the slave". All instances of these 95 terms are replaced by leader/follower, respectively. 97 The Master/Slave (MS) bit in the database description packet is 98 renamed the Leader (L) bit. 100 The operation of OSPFv3 is not modified. The Leader/Follower 101 terminology and Leader (L) Bit definition changes impact section 102 A.3.3 "The Database Description packet". 104 4. Other RFCs With References 106 The following OSPF RFCs also have references to the legacy 107 terminology. 109 * RFC 4222 - Prioritized Treatment of Specific OSPF Version 2 110 Packets and Congestion Avoidance (BCP) [RFC4222] 112 * RFC 5243 - OSPF Database Exchange Summary List Optimization 113 (Informational) [RFC5243] 115 * RFC 4811 - OSPF Out-of-Band Link State Database (LSDB) 116 Resynchronization (Experimental) [RFC4811] 118 * RFC 5243 - OSPF Database Exchange Summary List Optimization 119 (Informational) [RFC5243] 121 * RFC 5614 - Mobile Ad Hoc Network (MANET) Extension of OSPF Using 122 Connected Dominating Set (CDS) Flooding (Experimental) [RFC5614] 124 * RFC 5838 - Support of Address Families in OSPFv3 (Standards Track) 125 [RFC5838] 127 Some of these will be updated by this document. The final set is 128 TBD. 130 5. Acknowledgements 132 TDB 134 6. IANA Considerations 136 IANA is requested to rename bit 0x01 in the "Database Description 137 (DD) Packet Flags" registry to "Leader (L-bit)" and to add a 138 reference to this document. 140 7. Security Considerations 142 This document updates the terminology used in OSPFv2 [RFC2328] and 143 OSPFv3 [RFC5340] without any modification to the specification of the 144 protocol. As such, the security characteristics of OSPF do not 145 change. 147 8. References 149 8.1. Normative References 151 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, 152 DOI 10.17487/RFC2328, April 1998, 153 . 155 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 156 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 157 . 159 8.2. Informative References 161 [RFC4222] Choudhury, G., Ed., "Prioritized Treatment of Specific 162 OSPF Version 2 Packets and Congestion Avoidance", BCP 112, 163 RFC 4222, DOI 10.17487/RFC4222, October 2005, 164 . 166 [RFC4811] Nguyen, L., Roy, A., and A. Zinin, "OSPF Out-of-Band Link 167 State Database (LSDB) Resynchronization", RFC 4811, 168 DOI 10.17487/RFC4811, March 2007, 169 . 171 [RFC5243] Ogier, R., "OSPF Database Exchange Summary List 172 Optimization", RFC 5243, DOI 10.17487/RFC5243, May 2008, 173 . 175 [RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET) 176 Extension of OSPF Using Connected Dominating Set (CDS) 177 Flooding", RFC 5614, DOI 10.17487/RFC5614, August 2009, 178 . 180 [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and 181 R. Aggarwal, "Support of Address Families in OSPFv3", 182 RFC 5838, DOI 10.17487/RFC5838, April 2010, 183 . 185 Authors' Addresses 187 Mike Fox 188 IBM 189 3039 E Cornwallis Rd 190 Research Triangle Park, NC 27709 191 United States of America 192 Email: mjfox@us.ibm.com 194 Acee Lindem 195 Cisco Systems 196 301 Midenhall Way 197 Cary, NC 27513 198 United States of America 199 Email: acee@cisco.com 201 Alvaro Retana 202 Futurewei Technologies, Inc. 203 2330 Central Expressway 204 Santa Clara, CA 95050 205 United States of America 206 Email: aretana@futurewei.com