rfc9454.original.xml		rfc9454.xml
	<?xml version='1.0' encoding='utf-8'?>		<?xml version="1.0" encoding="UTF-8"?>
	<!-- This template is for creating an Internet Draft using xml2rfc,
	which is available here: http://xml.resource.org. -->
	<!-- For a complete list and description of processing instructions (PIs),
	please see http://xml.resource.org/authoring/README.html. -->
	<rfc
	xmlns:xi="http://www.w3.org/2001/XInclude"
	category="std"
	docName="draft-ietf-lsr-ospf-terminology-09"
	ipr="trust200902"
	obsoletes=""
	updates="2328 5340 4222 4811 5243 5614 5838"
	submissionType="IETF"
	xml:lang="en"
	tocInclude="true"
	tocDepth="4"
	symRefs="true"
	sortRefs="true"
	consensus="true"
	version="3">
	<!-- xml2rfc v2v3 conversion 2.38.1 -->
	<!-- category values: std, bcp, info, exp, and historic
	ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902
	,
	or pre5378Trust200902
	you can add the attributes updates="NNNN" and obsoletes="NNNN"
	they will automatically be output with "(if approved)" -->
	<!-- ***** FRONT MATTER ***** -->		<!DOCTYPE rfc [
			<!ENTITY nbsp "&#160;">
			<!ENTITY zwsp "&#8203;">
			<!ENTITY nbhy "&#8209;">
			<!ENTITY wj "&#8288;">
			]>
			<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category=
			"std"
			consensus="true" docName="draft-ietf-lsr-ospf-terminology-09" number="9454" ipr=
			"trust200902" obsoletes="" updates="2328 4222 4811 5243 5340 5614 5838" xml:lang
			="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" version="3">
	<front>		<front>
	<!-- The abbreviated title is used in the page header - it is only necessary
	if the
	full title is longer than 39 characters -->
	<title abbrev="OSPF Terminology">Update to OSPF Terminology</title>		<title abbrev="OSPF Terminology">Update to OSPF Terminology</title>
	<seriesInfo name="Internet-Draft" value="draft-ietf-lsr-ospf-terminology-09"		<seriesInfo name="RFC" value="9454"/>
	/>
	<!-- add 'role="editor"' below for the editors if appropriate -->
	<!-- Another author who claims to be an editor -->
	<author initials="M" surname="Fox" fullname="Mike Fox">		<author initials="M" surname="Fox" fullname="Mike Fox">
	<organization>IBM</organization>		<organization>IBM</organization>
	<address>		<address>
	<postal>		<postal>
	<street>3039 E Cornwallis Rd</street>		<street>3039 E Cornwallis Rd.</street>
	<city>Research Triangle Park</city>		<city>Research Triangle Park</city>
	<region>NC</region>		<region>NC</region>
	<code>27709</code>		<code>27709</code>
	<country>USA</country>		<country>United States of America</country>
	</postal>		</postal>
	<email>mjfox@us.ibm.com</email>		<email>mjfox@us.ibm.com</email>
	</address>		</address>
	</author>		</author>
	<author initials="A" surname="Lindem" fullname="Acee Lindem">		<author initials="A" surname="Lindem" fullname="Acee Lindem">
	<organization>LabN Consulting LLC</organization>		<organization>LabN Consulting, L.L.C.</organization>
	<address>		<address>
	<postal>		<postal>
	<street>301 Midenhall Way</street>		<street>301 Midenhall Way</street>
	<city>Cary</city>		<city>Cary</city>
	<region>NC</region>		<region>NC</region>
	<code>27513</code>		<code>27513</code>
	<country>USA</country>		<country>United States of America</country>
	</postal>		</postal>
	<email>acee.ietf@gmail.com</email>		<email>acee.ietf@gmail.com</email>
	</address>		</address>
	</author>		</author>
	<author initials="A" surname="Retana" fullname="Alvaro Retana">		<author initials="A" surname="Retana" fullname="Alvaro Retana">
	<organization>Futurewei Technologies, Inc.</organization>		<organization>Futurewei Technologies, Inc.</organization>
	<address>		<address>
	<postal>		<postal>
	<street>2330 Central Expressway</street>		<street>2330 Central Expressway</street>
	<city>Santa Clara</city>		<city>Santa Clara</city>
	<region>CA</region>		<region>CA</region>
	<code>95050</code>		<code>95050</code>
	<country>USA</country>		<country>United States of America</country>
	</postal>		</postal>
	<email>aretana@futurewei.com</email>		<email>aretana@futurewei.com</email>
	</address>		</address>
	</author>		</author>
	<date year="2023"/>		<date year="2023" month="August" />
	<!-- If the month and year are both specified and are the current ones, xml2
	rfc will fill
	in the current day for you. If only the current year is specified, xml2r
	fc will fill
	in the current day and month for you. If the year is not the current one
	, it is
	necessary to specify at least a month (xml2rfc assumes day="1" if not sp
	ecified for the
	purpose of calculating the expiry date). With drafts it is normally suf
	ficient to
	specify just the year. -->
	<!-- Meta-data Declarations -->
	<area>Routing</area>		<area>rtg</area>
	<workgroup>Link State Routing</workgroup>		<workgroup>lsr</workgroup>
	<!-- WG name at the upperleft corner of the doc,
	IETF is fine for individual submissions.
	If this element is not present, the default is "Network Working Group",
	which is used by the RFC Editor as a nod to the history of the IETF. -->
	<keyword>OSPF terminology</keyword>		<keyword>OSPF terminology</keyword>
	<!-- Keywords will be incorporated into HTML output
	files in a meta tag but they have no effect on text or nroff
	output. If you submit your draft to the RFC Editor, the
	keywords will be used for the search engine. -->
	<abstract>		<abstract>
	<t>		<t>
	This document updates some OSPF terminology to be in line with inclusive language used in the industry.		This document updates some OSPF terminology to be in line with inclusive language used in the industry.
	The IETF has designated US National Institute of Standards and Technolog		The IETF has designated "Guidance for NIST Staff on Using
	y (NIST) "Guidance for NIST Staff on Using		Inclusive Language in Documentary Standards" by the US National Institut
	Inclusive Language in Documentary Standards" for its inclusive language		e of Standards and Technology (NIST)
	guidelines. It is intended that all		for its inclusive language guidelines. It is intended that all
	future OSPF documents use this revised terminology even when they refere nce the RFCs updated by this		future OSPF documents use this revised terminology even when they refere nce the RFCs updated by this
	document.		document.
	</t>		</t>
	<t>		<t>
	This document updates RFC2328, RFC5340, RFC4222, RFC4811, RFC5243, RFC56 14, and RFC5838.		This document updates RFCs 2328, 4222, 4811, 5243, 5340, 5614, and 5838.
	</t>		</t>
	</abstract>		</abstract>
	</front>		</front>
	<middle>		<middle>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>Introduction</name>		<name>Introduction</name>
	<t>		<t>
	This document updates some OSPF terminology to be in line with inclusive language used in the industry.		This document updates some OSPF terminology to be in line with inclusive language used in the industry.
	The IETF has designated US National Institute of Standards and Technolog		The IETF has designated "Guidance for NIST Staff on Using
	y (NIST) "Guidance for NIST Staff on Using		Inclusive Language in Documentary Standards" by the US National Institut
	Inclusive Language in Documentary Standards" <xref target="NISTIR8366"/>		e of Standards and Technology (NIST) <xref target="NISTIR8366"/> for its inclusi
	for its inclusive language guidelines.		ve language guidelines.
	It is intended that all future OSPF documents use this revised terminolo gy even when they reference the RFCs		It is intended that all future OSPF documents use this revised terminolo gy even when they reference the RFCs
	updated by this document.		updated by this document.
	</t>		</t>
	<t>		<t>
	This document updates <xref target="RFC2328"/>, <xref target="RFC5340"/>		This document updates <xref target="RFC2328"/>, <xref target="RFC4222"/>
	, <xref target="RFC4222"/>,		,
	<xref target="RFC4811"/>, <xref target="RFC5243"/>, <xref target="RFC561		<xref target="RFC4811"/>, <xref target="RFC5243"/>, <xref target="RFC534
	4"/>,		0"/>, <xref target="RFC5614"/>,
	and <xref target="RFC5838"/>.		and <xref target="RFC5838"/>.
	</t>		</t>
	</section>		</section>
			<!--[rfced] May we reorder the sections so that they appear in ascending
			order of the RFCs being updated, or do you prefer keeping the same order
			so that the base specifications are presented first?
			Current:
			2. Update to RFC 2328
			3. Update to RFC 5340
			4. Update to RFC 4222
			5. Update to RFC 4811
			6. Update to RFC 5243
			7. Update to RFC 5614
			8. Update to RFC 5838
			Perhaps:
			2. Update to RFC 2328
			3. Update to RFC 4222
			4. Update to RFC 4811
			5. Update to RFC 5243
			6. Update to RFC 5340
			7. Update to RFC 5614
			8. Update to RFC 5838
			If you would like to change the order, we will also update the following text th
			at appears similarly in the Abstract and Introduction.
			Original:
			This document updates RFC2328, RFC5340, RFC4222, RFC4811, RFC5243,
			RFC5614, and RFC5838.
			Perhaps:
			This document updates RFCs 2328, 4222, 4811, 5243, 5340, 5614, and 5838.
			-->
	<section anchor="update" numbered="true" toc="default">		<section anchor="update" numbered="true" toc="default">
	<name>Update to RFC2328</name>		<name>Update to RFC 2328</name>
	<t>		<t>
	The base OSPFv2 specification <xref target="RFC2328"/> defines the synch		The base OSPFv2 specification "OSPF Version 2" <xref target="RFC2328"/>
	ronization of		defines the synchronization of
	databases as two routers forming a "master/slave relationship". All ins		databases as two routers forming a "master/slave" relationship. All ins
	tances of these terms		tances of these terms
	are replaced by Leader/Follower, respectively.		are replaced by "Leader/Follower", respectively.
	</t>		</t>
	<t>		<t>
	The Master (MS) bit in the database description packet is renamed the Lea der (L) bit.		In the Database Description packet, the "master (MS) bit" is renamed the "Leader (L) bit".
	</t>		</t>
	<t>		<t>
	The operation of OSPFv2 is not modified. The Leader/Follower terminology		The operation of OSPFv2 is not modified. The Leader/Follower terminology
	and Leader (L) Bit definition		and Leader (L) bit definition
	changes impact the following sections: 7.2 "The Synchronization of Data		changes impact the following sections: "The Synchronization of Databases
	bases", 10 "The Neighbor Data Structures",		" (Section <xref target="RFC2328" section="7.2"
	10.1 "Neighbor states", 10.2 "Events causing neighbor state changes", 10		sectionFormat="bare"/>), "The Neighbor Data Structure" (Section <xref target="RF
	.3 "The Neighbor state machine",		C2328" section="10"
	10.6 "Receiving Database Description Packets",		sectionFormat="bare"/>), "Neighbor states" (Section <xref target="RFC2328" secti
	10.8 "Sending Database Description Packets", 10.10 "An Example", and A.3		on="10.1"
	.3 "The Database Description packet".		sectionFormat="bare"/>), "Events causing neighbor state changes" (Section <xref
			target="RFC2328" section="10.2"
			sectionFormat="bare"/>), "The Neighbor state machine" (Section <xref target="RFC
			2328" section="10.3"
			sectionFormat="bare"/>), "Receiving Database Description Packets" (Section <xref
			target="RFC2328" section="10.6"
			sectionFormat="bare"/>), "Sending Database Description Packets" (Section <xref t
			arget="RFC2328" section="10.8"
			sectionFormat="bare"/>), "An Example" (Section <xref target="RFC2328" section="1
			0.10"
			sectionFormat="bare"/>), and "The Database Description packet" (Appendix <xref t
			arget="RFC2328" section="A.3.3"
			sectionFormat="bare"/>).
	</t>		</t>
	</section>		</section>
	<section anchor="updatev6" numbered="true" toc="default">
	<name>Update to RFC5340</name>
	<t>
	The base OSPFv3 specification <xref target="RFC5340"/> defines the datab
	ase description process
	between two routers as one being "designated to be the master and the ot
	her is the slave". All instances of these
	terms are replaced by Leader/Follower, respectively.
	</t>
	<t>
	The Master/Slave (MS) bit in the database description packet is renamed t
	he Leader (L) bit.
	</t>
	<t>
	The operation of OSPFv3 is not modified. The Leader/Follower terminology
	and Leader (L) Bit definition
	changes impact section A.3.3 "The Database Description packet".
	</t>
	</section>
	<section anchor="update4222" numbered="true" toc="default">		<section anchor="update4222" numbered="true" toc="default">
	<name>Update to RFC4222</name>		<name>Update to RFC 4222</name>
	<t>		<t>
	This Best Current Practice (BCP) document describes "Prioritized Treatme		"Prioritized Treatment of Specific OSPF Version 2 Packets and
	nt of Specific OSPF Version 2 Packets and		Congestion Avoidance" <xref target="RFC4222"/> is a Best Current Practic
	Congestion Avoidance" <xref target="RFC4222"/>. There is an example OSFP		e (BCP) document. In Appendix <xref target="RFC4222" section="C" sectionFormat=
	v2 packet sequence in Appendix C, (2),		"bare"/>, Item (2), there is an example OSFPv2 packet sequence that refers to th
	that refers to the "slave" in a database exchange. This reference will b		e "slave" in a database exchange; this reference is renamed to "Follower".
	e renamed to "Follower".
	</t>		</t>
	</section>		</section>
	<section anchor="update4811" numbered="true" toc="default">		<section anchor="update4811" numbered="true" toc="default">
	<name>Update to RFC4811</name>		<name>Update to RFC 4811</name>
	<t>		<t>
	This Experimental document specifies "OSPF Out-of-Band Link State Databa		"OSPF Out-of-Band Link State Database (LSDB) Resynchronization" <xref ta
	se (LSDB) Resynchronization"		rget="RFC4811"/> is an Informational document.
	<xref target="RFC4811"/>.		Section <xref target="RFC4811" section="2.4" sectionFormat="bare"/> incl
	Section 2.4 includes a Database Description packet (Figure 2) and a desc		udes a Database Description packet (Figure 2) and a description of the attendant
	ription of the attendant encoding		encoding
	changes for Out-of-Band Resynchronization. In the figure and the descrip		changes for Out-of-Band Resynchronization. In the figure and the descrip
	tion, all instances of MS when		tion, all instances of "MS" (when
	referring to the Database Description packet bit are renamed to "L". The		referring to the Database Description packet bit) are renamed to "L". Th
	re is also a reference to "Master" in		ere is also a reference to "Master" in
	this section that is renamed to "Leader".		this section that is renamed to "Leader".
	</t>		</t>
	</section>		</section>
	<section anchor="update5243" numbered="true" toc="default">		<section anchor="update5243" numbered="true" toc="default">
	<name>Update to RFC5243</name>		<name>Update to RFC 5243</name>
	<t>		<t>
	This Informational document describes an "OSPF Database Exchange Summary		"OSPF Database Exchange Summary List Optimization" <xref target="RFC524
	List Optimization" <xref target="RFC5243"/>.		3"/> is an Informational document.
	The Introduction, Section 1, references "Master or Slave". This will be		The Introduction (Section <xref target="RFC5243" section="1" sectionForm
	replaced by "Leader or Follower".		at="bare"/>) references "Master or Slave"; this is replaced by "Leader or Follow
	Section 3.0 includes an example of the optimized database exchange. In t		er".
	his example, all instances of		Section <xref target="RFC5243" section="3" sectionFormat="bare"/> includ
	"Master" will be renamed to "Leader" and all instances of "Slave" will b		es an example of the optimized database exchange. In this example, all instances
	e renamed to "Follower".		of
			"Master" and "Slave" are renamed to "Leader" and "Follower", respectivel
			y.
			</t>
			</section>
			<section anchor="updatev6" numbered="true" toc="default">
			<name>Update to RFC 5340</name>
			<t>
			The base OSPFv3 specification "OSPF for IPv6" <xref target="RFC5340"/> d
			efines the Database Description process
			between two routers as one being "designated to be the master and the ot
			her is the slave". All instances of these
			terms are replaced by "Leader/Follower", respectively.
			</t>
			<t>
			In the Database Description packet, the "Master/Slave (MS) bit" is rename
			d the "Leader (L) bit".
			</t>
			<t>
			The operation of OSPFv3 is not modified. The Leader/Follower terminology
			and Leader (L) bit definition
			changes impact "The Database Description Packet" (Appendix <xref target=
			"RFC5340" section="A.3.3" sectionFormat="bare"/>).
	</t>		</t>
	</section>		</section>
	<section anchor="update5614" numbered="true" toc="default">		<section anchor="update5614" numbered="true" toc="default">
	<name>Update to RFC5614</name>		<name>Update to RFC 5614</name>
	<t>		<t>
	This Experimental document specifies the "Mobile Ad Hoc Network (MANET)		"Mobile Ad Hoc Network (MANET) Extension of OSPF
	Extension of OSPF		Using Connected Dominating Set (CDS) Flooding" <xref target="RFC5614"/>
	Using Connected Dominating Set (CDS) Flooding" <xref target="RFC5614"/>.		is an Experimental document.
	"Changes to the Neighbor State Machine", Section 7.2 contains modificati		"Changes to the Neighbor State Machine" (Section <xref target="RFC5614"
	ons to the neighbor		section="7.1"
	state machine updated from <xref target="RFC2328"/>. In this transition		sectionFormat="bare"/>) contains modifications to the neighbor
	to "2-way" state, all		state machine that were updated from <xref target="RFC2328"/>. In the ne
	instances of "Master" are renamed to "Leader" and all instances of "Slav		ighbor state machine modifications, all
	e" are renamed to		instances of "Master" and "Slave" are renamed to "Leader" and "Follower"
	"Follower". Additionally, instances of "MS" in reference to the Database		, respectively.
	Description packet		Additionally, all instances of "MS" (when referring to the Database Desc
	bit are renamed to "L". Additionally, in "Receiving Database Description		ription packet
	Packets, Section 7.5,		bit) are renamed to "L". And in "Receiving Database Description Packets"
	the parenthentical "master or slave" is replaced by "Leader or Follower"		(Section <xref target="RFC5614" section="7.5" sectionFormat="bare"/>), "master
	.		or slave" is replaced by "Leader or Follower" in the parenthetical.
	</t>		</t>
	</section>		</section>
	<section anchor="update5838" numbered="true" toc="default">		<section anchor="update5838" numbered="true" toc="default">
	<name>Update to RFC5838</name>		<name>Update to RFC 5838</name>
	<t>		<t>
	This Standards Track document specifies the "Support of Address Families		"Support of Address Families in OSPFv3" <xref target="RFC5838"/> is a S
	in OSPFv3"		tandards Track document.
	<xref target="RFC5838"/>. "Database Description Maximum Transmission Uni		"Database Description Maximum Transmission Unit (MTU)
	t (MTU)		Specification for Non-IPv6 AFs" (Section <xref target="RFC5838" section=
	Specification for Non-IPv6 AFs", Section 2.7 contains a Database Descrip		"2.7" sectionFormat="bare"/>) contains a Database Description
	tion		packet change figure that includes the MS bit. In this figure, the "MS"
	packet change figure which include the "MS" bit. In this figure, the "MS		field is
	" field will		renamed the "L" field.
	be renamed to "L" field.
	</t>		</t>
	<t>		<t>
	Additionally, in Section 2.4.,first paragraph, "Changes to the Hello Pac ket Processing",		Additionally, in the first paragraph of "Changes to the Hello Packet Pro cessing" (Section <xref target="RFC5838" section="2.4" sectionFormat="bare"/>),
	the text is updated to remove the non-inclusive terms pertaining to		the text is updated to remove the non-inclusive terms pertaining to
	unreachability handling as follows:		unreachability handling as follows:
	</t>		</t>
	<artwork>		<blockquote>
	When an OSPFv3 router does not support this specification and an		When an OSPFv3 router does not support this specification and an
	interface is configured with the Instance ID corresponding to a		interface is configured with the Instance ID corresponding to an
	IPv4 AF, packets could be routed toward this interface and		IPv4 AF, packets could be routed toward this interface and
	dropped. This could happen due to misconfiguration or a router		dropped. This could happen due to misconfiguration or a router
	software downgrade. Packet reception and dropping on an interface		software downgrade. For example, an IPv4 packet
	not configured with the packet AF. For example, an IPv4 packet
	could be received on an interface not supporting IPv4 since		could be received on an interface not supporting IPv4 since
	a router that doesn't support this specification can still		a router that doesn't support this specification can still
	include the interface in an SPF-calculated path as long as it		include the interface in an SPF-calculated path as long as it
	establishes adjacencies using the Instance ID corresponding		establishes adjacencies using the Instance ID corresponding
	to the IPv4 AF. Note that OSPPFv3 Router-LSAs and Network-LSAs are		to the IPv4 AF. Note that OSPFv3 Router-LSAs and Network-LSAs are
	AF-agnostic.		AF-agnostic.
	</artwork>		</blockquote>
	</section>
	<section anchor="Acknowledgements" numbered="true" toc="default">
	<name>Acknowledgements</name>
	<t>Thanks to Dhruv Dhody, Adrian Farrel, Barry Leiba, and Erik Kline for r
	eview and comments.</t>
	</section>		</section>
	<!-- Possibly a 'Contributors' section ... -->
	<section anchor="IANA" numbered="true" toc="default">		<section anchor="IANA" numbered="true" toc="default">
	<name>IANA Considerations</name>		<name>IANA Considerations</name>
	<t>IANA is requested to rename bit 0x01 in the "Database Description (DD)		<t>In the "Database Description (DD) Packet Flags"
	Packet Flags"		registry, IANA has updated the description for value 0x01 to "Leader (L-bi
	registry to "Leader (L-bit)" and to add a reference to this document.</t>		t)" and has added this document as a reference, as shown below.</t>
	</section>
			<dl spacing="compact">
			<dt>Value:</dt><dd>0x01</dd>
			<dt>Description:</dt><dd>Leader (L-bit)</dd>
			<dt>Reference:</dt><dd><xref target="RFC2328"/> [RFC9454]</dd>
			</dl>
			</section>
	<section anchor="Security" numbered="true" toc="default">		<section anchor="Security" numbered="true" toc="default">
	<name>Security Considerations</name>		<name>Security Considerations</name>
	<t>		<t>
	This document updates the terminology used in OSPF RFCs without any modi fication to the specifications of the protocol.		This document updates the terminology used in OSPF RFCs without any modi fication to the specifications of the protocol.
	As such, the security characteristics of OSPF do not change.		As such, the security characteristics of OSPF do not change.
	</t>		</t>
	</section>		</section>
	</middle>		</middle>
	<!-- *****BACK MATTER ***** -->
	<back>		<back>
	<!-- References split into informative and normative -->
	<!-- There are 2 ways to insert reference entries from the citation libraries
	:
	1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (
	as shown)
	2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml
	"?> here
	(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.x
	ml")
	Both are cited textually in the same manner: by using xref elements.
	If you use the PI option, xml2rfc will, by default, try to find included fil
	es in the same
	directory as the including file. You can also define the XML_LIBRARY environ
	ment variable
	with a value containing a set of directories to search. These can be either
	in the local
	filing system or remote ones accessed by http (http://domain/dir/... ).-->
	<references>		<references>
	<name>References</name>		<name>References</name>
	<references>		<references>
	<name>Normative References</name>		<name>Normative References</name>
	<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RF C.2119.xml"?-->
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2 328.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2 328.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 340.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 340.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4 222.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4 222.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4 811.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4 811.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 243.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 243.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 614.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 614.xml"/>
	<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 838.xml"/>		<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5 838.xml"/>
	</references>		</references>
	<references>		<references>
	<name>Informative References</name>		<name>Informative References</name>
	<reference anchor="NISTIR8366" target="https://doi.org/10.6028/NIST.IR.8 366">		<reference anchor="NISTIR8366" target="https://doi.org/10.6028/NIST.IR.8 366">
	<front>		<front>
	<title>Guidance for NIST Staff on Using Inclusive Language in Docume		<title>Guidance for NIST Staff on Using Inclusive Language in Docume
	ntary Standards,		ntary Standards</title>
	National Institute of Standards and Technology (NIST) Interagency or		<author><organization>National Institute of Standards and Technology
	Internal Report 8366</title>		(NIST)</organization></author>
	<author surname="NIST"/>
	<date year="2021" month="April"/>		<date year="2021" month="April"/>
	</front>		</front>
	<seriesInfo name="NISTIR" value="8366"/>		<seriesInfo name="NIST Interagency/Internal Report (NISTIR)" value="83 66"/>
	</reference>		</reference>
	</references>		</references>
			</references>
	</references>		<section anchor="Acknowledgements" numbered="false" toc="default">
			<name>Acknowledgements</name>
			<t>Thanks to <contact fullname="Dhruv Dhody"/>, <contact fullname="Adrian
			Farrel"/>, <contact fullname="Erik Kline"/>, and <contact fullname="Barry Leiba
			"/> for their reviews and comments.</t>
			</section>
	</back>		</back>
	</rfc>		</rfc>
End of changes. 51 change blocks.
	216 lines changed or deleted		198 lines changed or added
This html diff was produced by rfcdiff 1.48.