< draft-acee-lsr-ospfv3-sr-yang-04.txt		draft-acee-lsr-ospfv3-sr-yang-05.txt >
	Internet A. Lindem		Internet A. Lindem
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Informational Y. Qu		Intended status: Informational Y. Qu
	Expires: October 31, 2021 Futurewei		Expires: April 21, 2022 Futurewei
	April 29, 2021		October 18, 2021
	YANG Data Model for OSPFv3 Segment Routing		YANG Data Model for OSPFv3 Segment Routing
	draft-acee-lsr-ospfv3-sr-yang-04		draft-acee-lsr-ospfv3-sr-yang-05
	Abstract		Abstract
	This document defines a YANG data module augmenting the IETF OSPF		This document defines a YANG data module augmenting the IETF OSPF
	Segment Routing (SR) YANG model to support OSPFv3 extensions for SR.		Segment Routing (SR) YANG model to support OSPFv3 extensions for SR.
	It can be used to configure and manage OSPFv3 Segment Routing in MPLS		It can be used to configure and manage OSPFv3 Segment Routing in MPLS
	data plane.		data plane.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on October 31, 2021.		This Internet-Draft will expire on April 21, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
	2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. OSPFv3 Extensions for Segment Routing . . . . . . . . . . . . 2		3. OSPFv3 Extensions for Segment Routing . . . . . . . . . . . . 3
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 17		4. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
	7.1. Normative References . . . . . . . . . . . . . . . . . . 18		7.1. Normative References . . . . . . . . . . . . . . . . . . 18
	7.2. Informative References . . . . . . . . . . . . . . . . . 19		7.2. Informative References . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
	1. Overview		1. Overview
	YANG [RFC6020] [RFC7950] is a data definition language used to define		YANG [RFC7950] is a data definition language used to define the
	the contents of a conceptual data store that allows networked devices		contents of a conceptual data store that allows networked devices to
	to be managed using NETCONF [RFC6241]. YANG is proving relevant		be managed using NETCONF [RFC6241]. YANG is proving relevant beyond
	beyond its initial confines, as bindings to other interfaces (e.g.,		its initial confines, as bindings to other interfaces (e.g., ReST)
	ReST) and encodings other than XML (e.g., JSON) are being defined.		and encodings other than XML (e.g., JSON) are being defined.
	Furthermore, YANG data models can be used as the basis for		Furthermore, YANG data models can be used as the basis for
	implementation of other interfaces, such as CLI and programmatic		implementation of other interfaces, such as CLI and programmatic
	APIs.		APIs.
	This document defines a YANG data module augmenting the IETF OSPF SR		This document defines a YANG data module augmenting the IETF OSPF SR
	YANG model [I-D.ietf-ospf-sr-yang], and can be used to configure and		YANG model [I-D.ietf-ospf-sr-yang], and can be used to configure and
	manage OSPFv3 extensions for Segment Routing [RFC8666].		manage OSPFv3 extensions for Segment Routing with the MPLS data
			plane. [RFC8666].
	The augmentation defined in this document requires support for both		The augmentation defined in this document requires support for both
	the OSPF SR model and the OSPF base model[I-D.ietf-ospf-yang].		the OSPF SR model and the OSPF base model[I-D.ietf-ospf-yang].
	1.1. Requirements Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Tree Diagrams		2. Tree Diagrams
	This document uses the graphical representation of data models		Tree diagrams used in this document follow the notation defined in
	defined in [RFC8340].		[RFC8340].
	3. OSPFv3 Extensions for Segment Routing		3. OSPFv3 Extensions for Segment Routing
	This document defines a YANG module for OSPFv3 extensions for Segment		This document defines a YANG module for OSPFv3 extensions for Segment
	Routing [RFC8666]. It is an augmentation of the OSPF SR base YANG		Routing [RFC8666]. It is an augmentation of the OSPF SR base YANG
	model. [RFC8022] and [RFC8349] are not referenced in the document		model. [RFC8022] and [RFC8349] are not referenced in the document
	text but within the YANG module itself.		text but within the YANG module itself.
	module: ietf-ospfv3-sr		module: ietf-ospfv3-sr
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	skipping to change at page 7, line 45 ¶		skipping to change at page 7, line 49 ¶
	| +--ro weight? uint8		| +--ro weight? uint8
	| +--ro sid? uint32		| +--ro sid? uint32
	+--ro lan-adj-sid-sub-tlvs		+--ro lan-adj-sid-sub-tlvs
	+--ro lan-adj-sid-sub-tlv* []		+--ro lan-adj-sid-sub-tlv* []
	+--ro lan-adj-sid-flags		+--ro lan-adj-sid-flags
	| +--ro bits* identityref		| +--ro bits* identityref
	+--ro weight? uint8		+--ro weight? uint8
	+--ro neighbor-router-id? yang:dotted-quad		+--ro neighbor-router-id? yang:dotted-quad
	+--ro sid? uint32		+--ro sid? uint32
	<CODE BEGINS> file "ietf-ospfv3-sr@2021-04-29.yang"		<CODE BEGINS> file "ietf-ospfv3-sr@2021-10-18.yang"
	module ietf-ospfv3-sr {		module ietf-ospfv3-sr {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr";		namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr";
	prefix ospfv3-sr;		prefix ospfv3-sr;
	import ietf-inet-types {		import ietf-inet-types {
	prefix "inet";		prefix "inet";
	}		}
	import ietf-yang-types {		import ietf-yang-types {
	prefix "yang";		prefix "yang";
	}		}
	import ietf-routing {		import ietf-routing {
	prefix "rt";		prefix "rt";
	skipping to change at page 8, line 49 ¶		skipping to change at page 9, line 6 ¶
	description		description
	"This YANG module defines the operational state for OSPFv3		"This YANG module defines the operational state for OSPFv3
	Segment Routing, which is common across all of the vendor		Segment Routing, which is common across all of the vendor
	implementations. It is intended that the module will be		implementations. It is intended that the module will be
	extended by vendors to define vendor-specific OSPFv3		extended by vendors to define vendor-specific OSPFv3
	Segment Routing configuration and operational parameters		Segment Routing configuration and operational parameters
	and policies.		and policies.
	This YANG model conforms to the Network Management		This YANG model conforms to the Network Management
	Datastore Architecture (NMDA) as described in RFC 8242.		Datastore Architecture (NMDA) as described in RFC 8342.
	Copyright (c) 2020 IETF Trust and the persons identified as		Copyright (c) 2021 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		authors of the code. All rights reserved.
	Redistribution and use in source and binary forms, with or		Redistribution and use in source and binary forms, with or
	without modification, is permitted pursuant to, and subject		without modification, is permitted pursuant to, and subject
	to the license terms contained in, the Simplified BSD License		to the license terms contained in, the Simplified BSD License
	set forth in Section 4.c of the IETF Trust's Legal Provisions		set forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX;		This version of this YANG module is part of RFC XXXX;
	see the RFC itself for full legal notices.		see the RFC itself for full legal notices.
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',		NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	'MAY', and 'OPTIONAL' in this document are to be interpreted as		'MAY', and 'OPTIONAL' in this document are to be interpreted as
	described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,		described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
	they appear in all capitals, as shown here.";		they appear in all capitals, as shown here.";
	reference "RFC XXXX";		reference "RFC XXXX";
	revision 2021-04-29 {		revision 2021-10-18 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPFv3 Segment Routing.";		"RFC XXXX: A YANG Data Model for OSPFv3 Segment Routing.";
	}		}
	/* groupings */		/* groupings */
	grouping ospfv3-prefix-sid-sub-tlvs {		grouping ospfv3-prefix-sid-sub-tlvs {
	description "Prefix Segment ID (SID) sub-TLVs.";		description "Prefix Segment ID (SID) sub-TLVs.";
	container perfix-sid-sub-tlvs{		container perfix-sid-sub-tlvs{
	skipping to change at page 10, line 4 ¶		skipping to change at page 10, line 8 ¶
	}		}
	description		description
	"Prefix SID Sub-TLV flag bits list.";		"Prefix SID Sub-TLV flag bits list.";
	}		}
	description "Segment Identifier (SID) Flags.";		description "Segment Identifier (SID) Flags.";
	}		}
	leaf algorithm {		leaf algorithm {
	type uint8;		type uint8;
	description		description
	"The algorithm associated with the prefix-SID.";		"The algorithm associated with the prefix-SID.";
	}		}
	leaf sid {		leaf sid {
	type uint32;		type uint32;
	description "An index or label.";		description "An index or label.";
	}		}
	}		}
	}		}
	}		}
	grouping ospfv3-extended-prefix-range-tlvs {		grouping ospfv3-extended-prefix-range-tlvs {
	description "Extended prefix range TLV grouping.";		description "Extended prefix range TLV grouping.";
	container ospfv3-extended-prefix-range-tlvs {		container ospfv3-extended-prefix-range-tlvs {
	description "The list of range of prefixes.";		description "The list of extended prefix range TLVs.";
	list extended-prefix-range-tlv { //type=2?		list extended-prefix-range-tlv {
	description "The range of prefixes.";		description "The range of prefixes.";
	leaf prefix-length {		leaf prefix-length {
	type uint8;		type uint8;
	description "Length of prefix in bits.";		description "Length of prefix in bits.";
	}		}
	leaf af {		leaf af {
	type uint8;		type uint8;
	description "Address family for the prefix.";		description "Address family for the prefix.";
	}		}
	leaf range-size {		leaf range-size {
	skipping to change at page 17, line 23 ¶		skipping to change at page 17, line 28 ¶
	<CODE ENDS>		<CODE ENDS>
	4. Security Considerations		4. Security Considerations
	The YANG modules specified in this document define a schema for data		The YANG modules specified in this document define a schema for data
	that is designed to be accessed via network management protocols such		that is designed to be accessed via network management protocols such
	as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer		as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
	is the secure transport layer, and the mandatory-to-implement secure		is the secure transport layer, and the mandatory-to-implement secure
	transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer		transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
	is HTTPS, and the mandatory-to-implement secure transport is TLS		is HTTPS, and the mandatory-to-implement secure transport is TLS
	[RFC5246].		[RFC8446].
	The NETCONF access control model [RFC6536] provides the means to		The Network Configuration Access Control Model (NACM) [[RFC8341]
	restrict access for particular NETCONF or RESTCONF users to a pre-		provides the means to restrict access for particular NETCONF or
	configured subset of all available NETCONF or RESTCONF protocol		RESTCONF users to a pre-configured subset of all available NETCONF or
	operations and content.		RESTCONF protocol operations and content.
	There are a number of data nodes defined in the modules that are		There are a number of data nodes defined in the modules that are
	writable/creatable/deletable (i.e., config true, which is the		writable/creatable/deletable (i.e., config true, which is the
	default). These data nodes may be considered sensitive or vulnerable		default). These data nodes may be considered sensitive or vulnerable
	in some network environments. Write operations (e.g., edit-config)		in some network environments. Write operations (e.g., edit-config)
	to these data nodes without proper protection can have a negative		to these data nodes without proper protection can have a negative
	effect on network operations.		effect on network operations.
	Some of the readable data nodes in the modules may be considered		Some of the readable data nodes in the modules may be considered
	sensitive or vulnerable in some network environments. It is thus		sensitive or vulnerable in some network environments. It is thus
	skipping to change at page 18, line 29 ¶		skipping to change at page 18, line 35 ¶
	This document was produced using Marshall Rose's xml2rfc tool.		This document was produced using Marshall Rose's xml2rfc tool.
	The YANG model was developed using the suite of YANG tools written		The YANG model was developed using the suite of YANG tools written
	and maintained by numerous authors.		and maintained by numerous authors.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[I-D.ietf-ospf-sr-yang]		[I-D.ietf-ospf-sr-yang]
	Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,		Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem,
	"YANG Data Model for OSPF SR (Segment Routing) Protocol",		"YANG Data Model for OSPF SR (Segment Routing) Protocol",
	draft-ietf-ospf-sr-yang-14 (work in progress), February		draft-ietf-ospf-sr-yang-15 (work in progress), July 2021.
	2021.
	[I-D.ietf-ospf-yang]		[I-D.ietf-ospf-yang]
	Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,		Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem,
	"YANG Data Model for OSPF Protocol", draft-ietf-ospf-		"YANG Data Model for OSPF Protocol", draft-ietf-ospf-
	yang-29 (work in progress), October 2019.		yang-29 (work in progress), October 2019.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004,		DOI 10.17487/RFC3688, January 2004,
	<https://www.rfc-editor.org/info/rfc3688>.		<https://www.rfc-editor.org/info/rfc3688>.
	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246,
	DOI 10.17487/RFC5246, August 2008,
	<https://www.rfc-editor.org/info/rfc5246>.
	[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	the Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	DOI 10.17487/RFC6020, October 2010,		DOI 10.17487/RFC6020, October 2010,
	<https://www.rfc-editor.org/info/rfc6020>.		<https://www.rfc-editor.org/info/rfc6020>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol		and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<https://www.rfc-editor.org/info/rfc6241>.		<https://www.rfc-editor.org/info/rfc6241>.
	[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure		[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
	Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,		Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
	<https://www.rfc-editor.org/info/rfc6242>.		<https://www.rfc-editor.org/info/rfc6242>.
	[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
	Protocol (NETCONF) Access Control Model", RFC 6536,
	DOI 10.17487/RFC6536, March 2012,
	<https://www.rfc-editor.org/info/rfc6536>.
	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",		[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
	RFC 7950, DOI 10.17487/RFC7950, August 2016,		RFC 7950, DOI 10.17487/RFC7950, August 2016,
	<https://www.rfc-editor.org/info/rfc7950>.		<https://www.rfc-editor.org/info/rfc7950>.
	[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing		[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
	Management", RFC 8022, DOI 10.17487/RFC8022, November		Management", RFC 8022, DOI 10.17487/RFC8022, November
	2016, <https://www.rfc-editor.org/info/rfc8022>.		2016, <https://www.rfc-editor.org/info/rfc8022>.
	[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF		[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
	Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,		Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
	<https://www.rfc-editor.org/info/rfc8040>.		<https://www.rfc-editor.org/info/rfc8040>.
			[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
			Access Control Model", STD 91, RFC 8341,
			DOI 10.17487/RFC8341, March 2018,
			<https://www.rfc-editor.org/info/rfc8341>.
	[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for		[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
	Routing Management (NMDA Version)", RFC 8349,		Routing Management (NMDA Version)", RFC 8349,
	DOI 10.17487/RFC8349, March 2018,		DOI 10.17487/RFC8349, March 2018,
	<https://www.rfc-editor.org/info/rfc8349>.		<https://www.rfc-editor.org/info/rfc8349>.
			[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
			Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
			<https://www.rfc-editor.org/info/rfc8446>.
	[RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions		[RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions
	for Segment Routing", RFC 8666, DOI 10.17487/RFC8666,		for Segment Routing", RFC 8666, DOI 10.17487/RFC8666,
	December 2019, <https://www.rfc-editor.org/info/rfc8666>.		December 2019, <https://www.rfc-editor.org/info/rfc8666>.
	7.2. Informative References		7.2. Informative References
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
End of changes. 25 change blocks.
	41 lines changed or deleted		40 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/