< draft-ietf-pce-pcep-yang-14.txt		draft-ietf-pce-pcep-yang-15.txt >
	PCE Working Group D. Dhody, Ed.		PCE Working Group D. Dhody, Ed.
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track J. Hardwick		Intended status: Standards Track J. Hardwick
	Expires: January 9, 2021 Metaswitch		Expires: May 4, 2021 Metaswitch
	V. Beeram		V. Beeram
	Juniper Networks		Juniper Networks
	J. Tantsura		J. Tantsura
	Apstra, Inc.		Apstra, Inc.
	July 8, 2020		October 31, 2020
	A YANG Data Model for Path Computation Element Communications Protocol		A YANG Data Model for Path Computation Element Communications Protocol
	(PCEP)		(PCEP)
	draft-ietf-pce-pcep-yang-14		draft-ietf-pce-pcep-yang-15
	Abstract		Abstract
	This document defines a YANG data model for the management of Path		This document defines a YANG data model for the management of Path
	Computation Element communications Protocol (PCEP) for communications		Computation Element communications Protocol (PCEP) for communications
	between a Path Computation Client (PCC) and a Path Computation		between a Path Computation Client (PCC) and a Path Computation
	Element (PCE), or between two PCEs. The data model includes		Element (PCE), or between two PCEs. The data model includes
	configuration and state data.		configuration and state data.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 January 9, 2021.		This Internet-Draft will expire on May 4, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 33 ¶		skipping to change at page 2, line 33 ¶
	5.3. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 13		5.3. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 13
	5.4. The Session Lists . . . . . . . . . . . . . . . . . . . . 15		5.4. The Session Lists . . . . . . . . . . . . . . . . . . . . 15
	5.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 17		5.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 17
	5.6. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 17		5.6. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	5.7. The Full PCEP Data Model . . . . . . . . . . . . . . . . 18		5.7. The Full PCEP Data Model . . . . . . . . . . . . . . . . 18
	6. The Design of PCEP Statistics Data Model . . . . . . . . . . 24		6. The Design of PCEP Statistics Data Model . . . . . . . . . . 24
	7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 27		7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 27
	7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 27		7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 27
	8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 28		8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 28
	8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 28		8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 28
			8.2. LSP-ID . . . . . . . . . . . . . . . . . . . . . . . . . 28
	9. Other Considerations . . . . . . . . . . . . . . . . . . . . 28		9. Other Considerations . . . . . . . . . . . . . . . . . . . . 28
	9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 28		9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 28
	10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 28		10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 28
	10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 28		10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 28
	10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 83		10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 83
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 101		11. Security Considerations . . . . . . . . . . . . . . . . . . . 101
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 102		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 102
	13. Implementation Status . . . . . . . . . . . . . . . . . . . . 103		13. Implementation Status . . . . . . . . . . . . . . . . . . . . 103
	14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 103		14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 104
	15. References . . . . . . . . . . . . . . . . . . . . . . . . . 104		15. References . . . . . . . . . . . . . . . . . . . . . . . . . 104
	15.1. Normative References . . . . . . . . . . . . . . . . . . 104		15.1. Normative References . . . . . . . . . . . . . . . . . . 104
	15.2. Informative References . . . . . . . . . . . . . . . . . 107		15.2. Informative References . . . . . . . . . . . . . . . . . 108
	Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 109		Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 109
	Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 112		Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 112
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 113		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 113
	1. Introduction		1. Introduction
	The Path Computation Element (PCE) defined in [RFC4655] is an entity		The Path Computation Element (PCE) defined in [RFC4655] is an entity
	that is capable of computing a network path or route based on a		that is capable of computing a network path or route based on a
	network graph, and applying computational constraints. A Path		network graph, and applying computational constraints. A Path
	Computation Client (PCC) may make requests to a PCE for paths to be		Computation Client (PCC) may make requests to a PCE for paths to be
	skipping to change at page 5, line 25 ¶		skipping to change at page 5, line 25 ¶
	context in which YANG module each name is defined. Otherwise, names		context in which YANG module each name is defined. Otherwise, names
	are prefixed using the standard prefix associated with the		are prefixed using the standard prefix associated with the
	corresponding YANG module, as shown in Table 1.		corresponding YANG module, as shown in Table 1.
	+----------+------------------+-------------------------------------+		+----------+------------------+-------------------------------------+
	| Prefix | YANG module | Reference |		| Prefix | YANG module | Reference |
	+----------+------------------+-------------------------------------+		+----------+------------------+-------------------------------------+
	| yang | ietf-yang-types | [RFC6991] |		| yang | ietf-yang-types | [RFC6991] |
	| inet | ietf-inet-types | [RFC6991] |		| inet | ietf-inet-types | [RFC6991] |
	| te | ietf-te | [I-D.ietf-teas-yang-te] |		| te | ietf-te | [I-D.ietf-teas-yang-te] |
	| te-types | ietf-te-types | [I-D.ietf-teas-yang-te] |		| te-types | ietf-te-types | [RFC8776] |
	| key- | ietf-key-chain | [RFC8177] |		| key- | ietf-key-chain | [RFC8177] |
	| chain | | |		| chain | | |
	| nacm | ietf-netconf-acm | [RFC8341] |		| nacm | ietf-netconf-acm | [RFC8341] |
	| tlss | ietf-tls-server | [I-D.ietf-netconf-tls-client-server |		| tlss | ietf-tls-server | [I-D.ietf-netconf-tls-client-server |
	| | | ] |		| | | ] |
	| tlsc | ietf-tls-client | [I-D.ietf-netconf-tls-client-server |		| tlsc | ietf-tls-client | [I-D.ietf-netconf-tls-client-server |
	| | | ] |		| | | ] |
	| ospf | ietf-ospf | [I-D.ietf-ospf-yang] |		| ospf | ietf-ospf | [I-D.ietf-ospf-yang] |
	| isis | ietf-isis | [I-D.ietf-isis-yang-isis-cfg] |		| isis | ietf-isis | [I-D.ietf-isis-yang-isis-cfg] |
	+----------+------------------+-------------------------------------+		+----------+------------------+-------------------------------------+
	skipping to change at page 7, line 26 ¶		skipping to change at page 7, line 26 ¶
	| Clients and TLS Servers | |		| Clients and TLS Servers | |
	| PCEP Extensions for | [RFC8664] |		| PCEP Extensions for | [RFC8664] |
	| Segment Routing | |		| Segment Routing | |
	| PCEP Extensions for | [RFC8697] |		| PCEP Extensions for | [RFC8697] |
	| Establishing Relationships | |		| Establishing Relationships | |
	| Between Sets of LSPs | |		| Between Sets of LSPs | |
	| YANG Data Model for OSPF | [I-D.ietf-ospf-yang] |		| YANG Data Model for OSPF | [I-D.ietf-ospf-yang] |
	| Protocol | |		| Protocol | |
	| YANG Data Model for IS-IS | [I-D.ietf-isis-yang-isis-cfg] |		| YANG Data Model for IS-IS | [I-D.ietf-isis-yang-isis-cfg] |
	| Protocol | |		| Protocol | |
	| PCEP extensions for GMPLS | [I-D.ietf-pce-gmpls-pcep-extensions] |		| PCEP extensions for GMPLS | [RFC8779] |
	+----------------------------+--------------------------------------+		+----------------------------+--------------------------------------+
	Table 2: Refrences in the YANG modules		Table 2: Refrences in the YANG modules
	4. Objectives		4. Objectives
	This section describes some of the design objectives for the model:		This section describes some of the design objectives for the model:
	o In case of existing implementations, it needs to map the data		o In case of existing implementations, it needs to map the data
	model defined in this document to their proprietary native data		model defined in this document to their proprietary native data
	skipping to change at page 11, line 42 ¶		skipping to change at page 11, line 42 ¶
	| | +--ro global-source uint32		| | +--ro global-source uint32
	| | +--ro extended-id string		| | +--ro extended-id string
	| | +--ro lsp* [plsp-id pcc-id lsp-id]		| | +--ro lsp* [plsp-id pcc-id lsp-id]
	| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id		| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id
	| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id		| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id
	| | +--ro lsp-id -> /pcep/entity/lsp-db/lsp/lsp-id		| | +--ro lsp-id -> /pcep/entity/lsp-db/lsp/lsp-id
	| +--ro lsp* [plsp-id pcc-id lsp-id]		| +--ro lsp* [plsp-id pcc-id lsp-id]
	| +--ro plsp-id uint32		| +--ro plsp-id uint32
	| +--ro pcc-id inet:ip-address		| +--ro pcc-id inet:ip-address
	| +--ro source?		| +--ro source?
	| | -> /te:te/lsps-state/lsp/source		| | -> /te:te/lsps/lsp/source
	| +--ro destination?		| +--ro destination?
	| | -> /te:te/lsps-state/lsp/destination		| | -> /te:te/lsps/lsp/destination
	| +--ro tunnel-id?		| +--ro tunnel-id?
	| | -> /te:te/lsps-state/lsp/tunnel-id		| | -> /te:te/lsps/lsp/tunnel-id
	| +--ro lsp-id		| +--ro lsp-id
	| | -> /te:te/lsps-state/lsp/lsp-id		| | -> /te:te/lsps/lsp/lsp-id
	| +--ro extended-tunnel-id?		| +--ro extended-tunnel-id?
	| | -> /te:te/lsps-state/lsp/extended-tunnel-id		| | -> /te:te/lsps/lsp/extended-tunnel-id
	| +--ro admin-state? boolean		| +--ro admin-state? boolean
	| +--ro operational-state? operational-state		| +--ro operational-state? operational-state
	| +--ro delegated		| +--ro delegated
	| | +--ro enabled? boolean		| | +--ro enabled? boolean
	| | +--ro peer? -> /pcep/entity/peers/peer/addr		| | +--ro peer? -> /pcep/entity/peers/peer/addr
	| | +--ro srp-id? uint32		| | +--ro srp-id? uint32
	| +--ro initiation {pce-initiated}?		| +--ro initiation {pce-initiated}?
	| | +--ro enabled? boolean		| | +--ro enabled? boolean
	| | +--ro peer? -> /pcep/entity/peers/peer/addr		| | +--ro peer? -> /pcep/entity/peers/peer/addr
	| +--ro symbolic-path-name? string		| +--ro symbolic-path-name? string
	skipping to change at page 18, line 28 ¶		skipping to change at page 18, line 28 ¶
	+--rw admin-status? boolean		+--rw admin-status? boolean
	+--ro index? uint32		+--ro index? uint32
	+--ro oper-status? pcep-oper-status		+--ro oper-status? pcep-oper-status
	+--rw domain		+--rw domain
	| +--rw domain* [domain-type domain]		| +--rw domain* [domain-type domain]
	| +--rw domain-type domain-type		| +--rw domain-type domain-type
	| +--rw domain domain		| +--rw domain domain
	+--rw capability		+--rw capability
	| +--rw capability? bits		| +--rw capability? bits
	| +--rw pce-initiated? boolean {pce-initiated}?		| +--rw pce-initiated? boolean {pce-initiated}?
	| +--rw include-db-ver? boolean		| +--rw include-db-ver? boolean {stateful,sync-opt}?
	| | {stateful,sync-opt}?		| +--rw trigger-resync? boolean {stateful,sync-opt}?
	| +--rw trigger-resync? boolean		| +--rw trigger-initial-sync? boolean {stateful,sync-opt}?
	| | {stateful,sync-opt}?		| +--rw incremental-sync? boolean {stateful,sync-opt}?
	| +--rw trigger-initial-sync? boolean
	| | {stateful,sync-opt}?
	| +--rw incremental-sync? boolean
	| | {stateful,sync-opt}?
	| +--rw sr {sr}?		| +--rw sr {sr}?
	| +--rw enabled? boolean		| +--rw enabled? boolean
	| +--rw msd-limit? boolean		| +--rw msd-limit? boolean
	| +--rw nai? boolean		| +--rw nai? boolean
	+--rw msd? uint8 {sr}?		+--rw msd? uint8 {sr}?
	+--rw pce-info		+--rw pce-info
	| +--rw scope		| +--rw scope
	| | +--rw path-scope? bits		| | +--rw path-scope? bits
	| | +--rw intra-area-pref? uint8		| | +--rw intra-area-pref? uint8
	| | +--rw inter-area-pref? uint8		| | +--rw inter-area-pref? uint8
	skipping to change at page 19, line 51 ¶		skipping to change at page 19, line 47 ¶
	| | +--ro source inet:ip-address		| | +--ro source inet:ip-address
	| | +--ro global-source uint32		| | +--ro global-source uint32
	| | +--ro extended-id string		| | +--ro extended-id string
	| | +--ro lsp* [plsp-id pcc-id lsp-id]		| | +--ro lsp* [plsp-id pcc-id lsp-id]
	| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id		| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id
	| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id		| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id
	| | +--ro lsp-id -> /pcep/entity/lsp-db/lsp/lsp-id		| | +--ro lsp-id -> /pcep/entity/lsp-db/lsp/lsp-id
	| +--ro lsp* [plsp-id pcc-id lsp-id]		| +--ro lsp* [plsp-id pcc-id lsp-id]
	| +--ro plsp-id uint32		| +--ro plsp-id uint32
	| +--ro pcc-id inet:ip-address		| +--ro pcc-id inet:ip-address
	| +--ro source?		| +--ro source? -> /te:te/lsps/lsp/source
	| | -> /te:te/lsps-state/lsp/source
	| +--ro destination?		| +--ro destination?
	| | -> /te:te/lsps-state/lsp/destination		| | -> /te:te/lsps/lsp/destination
	| +--ro tunnel-id?		| +--ro tunnel-id?
	| | -> /te:te/lsps-state/lsp/tunnel-id		| | -> /te:te/lsps/lsp/tunnel-id
	| +--ro lsp-id		| +--ro lsp-id -> /te:te/lsps/lsp/lsp-id
	| | -> /te:te/lsps-state/lsp/lsp-id
	| +--ro extended-tunnel-id?		| +--ro extended-tunnel-id?
	| | -> /te:te/lsps-state/lsp/extended-tunnel-id		| | -> /te:te/lsps/lsp/extended-tunnel-id
	| +--ro admin-state? boolean		| +--ro admin-state? boolean
	| +--ro operational-state? operational-state		| +--ro operational-state? operational-state
	| +--ro delegated		| +--ro delegated
	| | +--ro enabled? boolean		| | +--ro enabled? boolean
	| | +--ro peer? -> /pcep/entity/peers/peer/addr		| | +--ro peer? -> /pcep/entity/peers/peer/addr
	| | +--ro srp-id? uint32		| | +--ro srp-id? uint32
	| +--ro initiation {pce-initiated}?		| +--ro initiation {pce-initiated}?
	| | +--ro enabled? boolean		| | +--ro enabled? boolean
	| | +--ro peer? -> /pcep/entity/peers/peer/addr		| | +--ro peer? -> /pcep/entity/peers/peer/addr
	| +--ro symbolic-path-name? string		| +--ro symbolic-path-name? string
	skipping to change at page 28, line 17 ¶		skipping to change at page 28, line 17 ¶
	This section is added so that open issues can be tracked. This		This section is added so that open issues can be tracked. This
	section would be removed when the document is ready for publication.		section would be removed when the document is ready for publication.
	8.1. The PCE-Initiated LSP		8.1. The PCE-Initiated LSP
	The TE Model at [I-D.ietf-teas-yang-te] should support creating of		The TE Model at [I-D.ietf-teas-yang-te] should support creating of
	tunnels at the controller (PCE) and marking them as PCE-Initiated.		tunnels at the controller (PCE) and marking them as PCE-Initiated.
	The LSP-DB in the PCEP Yang (/pcep/entity/lsp-db/lsp/initiation) also		The LSP-DB in the PCEP Yang (/pcep/entity/lsp-db/lsp/initiation) also
	marks the LSPs which are PCE-initiated.		marks the LSPs which are PCE-initiated.
			8.2. LSP-ID
			Use of lsp-id as a key in the LSPDB could be an issue for a non-RSVP-
			TE path setup type. The lsp-id filed is currently a leafref to the
			TE model [I-D.ietf-teas-yang-te]. Need to a confirm if this is
			problematic.
	9. Other Considerations		9. Other Considerations
	9.1. PCEP over TLS (PCEPS)		9.1. PCEP over TLS (PCEPS)
	[RFC8253] describe the use of TLS in PCEP. The peer acting as the		[RFC8253] describe the use of TLS in PCEP. The peer acting as the
	PCEP client MUST act as the TLS client. The TLS client actively		PCEP client must act as the TLS client. The TLS client actively
	opens the TLS connection and the TLS server passively listens for the		opens the TLS connection and the TLS server passively listens for the
	incoming TLS connections. The well-known TCP port number 4189 is		incoming TLS connections. The well-known TCP port number 4189 is
	used by PCEP servers to listen for TCP connections established by		used by PCEP servers to listen for TCP connections established by
	PCEP over TLS clients. The TLS client MUST send the TLS ClientHello		PCEP over TLS clients. The TLS client sends the TLS ClientHello
	message to begin the TLS handshake. The TLS server MUST send a		message to begin the TLS handshake. The TLS server sends a
	CertificateRequest in order to request a certificate from the TLS		CertificateRequest in order to request a certificate from the TLS
	client. Once the TLS handshake has finished, the client and the		client. Once the TLS handshake has finished, the client and the
	server MAY begin to exchange PCEP messages. Client and server		server begin to exchange PCEP messages. Client and server identity
	identity verification is done before the PCEP open message is sent.		verification is done before the PCEP open message is sent. This
	This means that the identity verification is completed before the		means that the identity verification is completed before the PCEP
	PCEP session is started..		session is started.
	10. PCEP YANG Modules		10. PCEP YANG Modules
	10.1. ietf-pcep module		10.1. ietf-pcep module
	RFC Ed.: In this section, replace all occurrences of 'XXXX' with the		RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
	actual RFC number and all occurrences of the revision date below with		actual RFC number and all occurrences of the revision date below with
	the date of RFC publication (and remove this note).		the date of RFC publication (and remove this note).
	<CODE BEGINS> file "ietf-pcep@2020-07-08.yang"		<CODE BEGINS> file "ietf-pcep@2020-10-31.yang"
	module ietf-pcep {		module ietf-pcep {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";		namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";
	prefix pcep;		prefix pcep;
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	reference		reference
	"RFC 6991: Common YANG Data Types";		"RFC 6991: Common YANG Data Types";
	}		}
	skipping to change at page 30, line 39 ¶		skipping to change at page 30, line 46 ¶
	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
	(https://trustee.ietf.org/license-info).		(https://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX; see the		This version of this YANG module is part of RFC XXXX; see the
	RFC itself for full legal notices.";		RFC itself for full legal notices.";
	revision 2020-07-08 {		revision 2020-10-31 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: A YANG Data Model for Path Computation		"RFC XXXX: A YANG Data Model for Path Computation
	Element Communications Protocol (PCEP)";		Element Communications Protocol (PCEP)";
	}		}
	/*		/*
	* Typedefs		* Typedefs
	*/		*/
	typedef pcep-role {		typedef pcep-role {
	type enumeration {		type enumeration {
	enum unknown {		enum unknown {
	value 0;		value 0;
	skipping to change at page 36, line 43 ¶		skipping to change at page 36, line 49 ¶
	"Support synchronized path computation.";		"Support synchronized path computation.";
	reference		reference
	"RFC 5440: Path Computation Element (PCE) Communication		"RFC 5440: Path Computation Element (PCE) Communication
	Protocol (PCEP)";		Protocol (PCEP)";
	}		}
	feature gmpls {		feature gmpls {
	description		description
	"Support GMPLS.";		"Support GMPLS.";
	reference		reference
	"I-D.ietf-pce-gmpls-pcep-extensions: PCEP extensions for		"RFC 8779: PCEP extensions for GMPLS";
	GMPLS";
	}		}
	feature objective-function {		feature objective-function {
	description		description
	"Support OF as per RFC 5541.";		"Support OF as per RFC 5541.";
	reference		reference
	"RFC 5541: Encoding of Objective Functions in the Path		"RFC 5541: Encoding of Objective Functions in the Path
	Computation Element Communication Protocol (PCEP)";		Computation Element Communication Protocol (PCEP)";
	}		}
	feature global-concurrent {		feature global-concurrent {
	description		description
	skipping to change at page 61, line 19 ¶		skipping to change at page 61, line 24 ¶
	reserved";		reserved";
	}		}
	leaf pcc-id {		leaf pcc-id {
	type inet:ip-address;		type inet:ip-address;
	description		description
	"The local internet address of the PCC, that		"The local internet address of the PCC, that
	generated the PLSP-ID.";		generated the PLSP-ID.";
	}		}
	leaf source {		leaf source {
	type leafref {		type leafref {
	path "/te:te/te:lsps-state/te:lsp/te:source";		path "/te:te/te:lsps/te:lsp/te:source";
	}		}
	description		description
	"Tunnel sender address extracted from		"Tunnel sender address extracted from
	SENDER_TEMPLATE object";		SENDER_TEMPLATE object";
	reference		reference
	"RFC 3209: RSVP-TE: Extensions to RSVP for		"RFC 3209: RSVP-TE: Extensions to RSVP for
	LSP Tunnels";		LSP Tunnels";
	}		}
	leaf destination {		leaf destination {
	type leafref {		type leafref {
	path "/te:te/te:lsps-state/te:lsp/te:"		path "/te:te/te:lsps/te:lsp/te:"
	+ "destination";		+ "destination";
	}		}
	description		description
	"Tunnel endpoint address extracted from		"Tunnel endpoint address extracted from
	SESSION object";		SESSION object";
	reference		reference
	"RFC 3209: RSVP-TE: Extensions to RSVP for		"RFC 3209: RSVP-TE: Extensions to RSVP for
	LSP Tunnels";		LSP Tunnels";
	}		}
	leaf tunnel-id {		leaf tunnel-id {
	type leafref {		type leafref {
	path "/te:te/te:lsps-state/te:lsp/te:tunnel-id";		path "/te:te/te:lsps/te:lsp/te:tunnel-id";
	}		}
	description		description
	"Tunnel identifier used in the SESSION		"Tunnel identifier used in the SESSION
	that remains constant over the life		that remains constant over the life
	of the tunnel.";		of the tunnel.";
	reference		reference
	"RFC 3209: RSVP-TE: Extensions to RSVP for		"RFC 3209: RSVP-TE: Extensions to RSVP for
	LSP Tunnels";		LSP Tunnels";
	}		}
	leaf lsp-id {		leaf lsp-id {
	type leafref {		type leafref {
	path "/te:te/te:lsps-state/te:lsp/te:lsp-id";		path "/te:te/te:lsps/te:lsp/te:lsp-id";
	}		}
	description		description
	"Identifier used in the SENDER_TEMPLATE		"Identifier used in the SENDER_TEMPLATE
	and the FILTER_SPEC that can be changed		and the FILTER_SPEC that can be changed
	to allow a sender to share resources with		to allow a sender to share resources with
	itself.";		itself.";
	reference		reference
	"RFC 3209: RSVP-TE: Extensions to RSVP for		"RFC 3209: RSVP-TE: Extensions to RSVP for
	LSP Tunnels";		LSP Tunnels";
	}		}
	leaf extended-tunnel-id {		leaf extended-tunnel-id {
	type leafref {		type leafref {
	path "/te:te/te:lsps-state/te:lsp/te:"		path "/te:te/te:lsps/te:lsp/te:"
	+ "extended-tunnel-id";		+ "extended-tunnel-id";
	}		}
	description		description
	"Extended Tunnel ID of the LSP.";		"Extended Tunnel ID of the LSP.";
	reference		reference
	"RFC 3209: RSVP-TE: Extensions to RSVP for		"RFC 3209: RSVP-TE: Extensions to RSVP for
	LSP Tunnels";		LSP Tunnels";
	}		}
	leaf admin-state {		leaf admin-state {
	type boolean;		type boolean;
	skipping to change at page 83, line 4 ¶		skipping to change at page 83, line 9 ¶
	if-feature "sync-opt";		if-feature "sync-opt";
	description		description
	"Trigger the resyncrinization at the PCE";		"Trigger the resyncrinization at the PCE";
	reference		reference
	"RFC 8232: Optimizations of Label Switched Path State		"RFC 8232: Optimizations of Label Switched Path State
	Synchronization Procedures for a Stateful PCE";		Synchronization Procedures for a Stateful PCE";
	input {		input {
	leaf pcc {		leaf pcc {
	type leafref {		type leafref {
	path "/pcep/entity/peers/peer/addr";		path "/pcep/entity/peers/peer/addr";
	}		}
	description		description
	"The IP address to identify the PCC. The state		"The IP address to identify the PCC. The state
	syncronization is re-triggered for all LSPs from		syncronization is re-triggered for all LSPs from
	the PCC. The rpc on the PCC will be ignored.";		the PCC. The rpc on the PCC will be ignored.";
	}		}
	}		}
	//input		//input
	}		}
	//rpc		//rpc
	}		}
	<CODE ENDS>		<CODE ENDS>
	10.2. ietf-pcep-stats module		10.2. ietf-pcep-stats module
	<CODE BEGINS> file "ietf-pcep-stats@2020-07-08.yang"		<CODE BEGINS> file "ietf-pcep-stats@2020-10-31.yang"
	module ietf-pcep-stats {		module ietf-pcep-stats {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-stats";		namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-stats";
	prefix pcep-stats;		prefix pcep-stats;
	import ietf-pcep {		import ietf-pcep {
	prefix pcep;		prefix pcep;
	reference		reference
	"RFC XXXX: A YANG Data Model for Path Computation		"RFC XXXX: A YANG Data Model for Path Computation
	Element Communications Protocol (PCEP)";		Element Communications Protocol (PCEP)";
	skipping to change at page 83, line 47 ¶		skipping to change at page 84, line 4 ¶
	"RFC 6991: Common YANG Data Types";		"RFC 6991: Common YANG Data Types";
	}		}
	organization		organization
	"IETF PCE (Path Computation Element) Working Group";		"IETF PCE (Path Computation Element) Working Group";
	contact		contact
	"WG Web: <https://tools.ietf.org/wg/pce/>		"WG Web: <https://tools.ietf.org/wg/pce/>
	WG List: <mailto:pce@ietf.org>		WG List: <mailto:pce@ietf.org>
	Editor: Dhruv Dhody		Editor: Dhruv Dhody
	<mailto:dhruv.ietf@gmail.com>";		<mailto:dhruv.ietf@gmail.com>";
	description		description
	"The YANG module augments the PCEP yang operational		"The YANG module augments the PCEP yang operational
	model with statistics, counters and telemetry data.		model with statistics, counters and telemetry data.
	Copyright (c) 2020 IETF Trust and the persons identified as		Copyright (c) 2020 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
	(https://trustee.ietf.org/license-info).		(https://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX; see the		This version of this YANG module is part of RFC XXXX; see the
	RFC itself for full legal notices.";		RFC itself for full legal notices.";
	revision 2020-07-08 {		revision 2020-10-31 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: A YANG Data Model for Path Computation		"RFC XXXX: A YANG Data Model for Path Computation
	Element Communications Protocol (PCEP)";		Element Communications Protocol (PCEP)";
	}		}
	/*		/*
	* Groupings		* Groupings
	*/		*/
	skipping to change at page 104, line 15 ¶		skipping to change at page 104, line 28 ¶
	15. References		15. References
	15.1. Normative References		15.1. Normative References
	[I-D.ietf-isis-yang-isis-cfg]		[I-D.ietf-isis-yang-isis-cfg]
	Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.		Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
	Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf-		Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf-
	isis-yang-isis-cfg-42 (work in progress), October 2019.		isis-yang-isis-cfg-42 (work in progress), October 2019.
	[I-D.ietf-netconf-tls-client-server]		[I-D.ietf-netconf-tls-client-server]
	Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and		Watsen, K., "YANG Groupings for TLS Clients and TLS
	TLS Servers", draft-ietf-netconf-tls-client-server-19		Servers", draft-ietf-netconf-tls-client-server-22 (work in
	(work in progress), May 2020.		progress), August 2020.
	[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, Z., 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.
	[I-D.ietf-pce-gmpls-pcep-extensions]
	Margaria, C., Dios, O., and F. Zhang, "PCEP extensions for
	GMPLS", draft-ietf-pce-gmpls-pcep-extensions-16 (work in
	progress), December 2019.
	[I-D.ietf-teas-yang-te]		[I-D.ietf-teas-yang-te]
	Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,		Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
	"A YANG Data Model for Traffic Engineering Tunnels and		"A YANG Data Model for Traffic Engineering Tunnels, Label
	Interfaces", draft-ietf-teas-yang-te-23 (work in		Switched Paths and Interfaces", draft-ietf-teas-yang-te-25
	progress), March 2020.		(work in progress), July 2020.
	[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>.
	[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,		[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
	and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP		and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
	Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,		Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
	<https://www.rfc-editor.org/info/rfc3209>.		<https://www.rfc-editor.org/info/rfc3209>.
	skipping to change at page 107, line 41 ¶		skipping to change at page 107, line 48 ¶
	Communication Protocol (PCEP) Extensions for Establishing		Communication Protocol (PCEP) Extensions for Establishing
	Relationships between Sets of Label Switched Paths		Relationships between Sets of Label Switched Paths
	(LSPs)", RFC 8697, DOI 10.17487/RFC8697, January 2020,		(LSPs)", RFC 8697, DOI 10.17487/RFC8697, January 2020,
	<https://www.rfc-editor.org/info/rfc8697>.		<https://www.rfc-editor.org/info/rfc8697>.
	[RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,		[RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
	"Common YANG Data Types for Traffic Engineering",		"Common YANG Data Types for Traffic Engineering",
	RFC 8776, DOI 10.17487/RFC8776, June 2020,		RFC 8776, DOI 10.17487/RFC8776, June 2020,
	<https://www.rfc-editor.org/info/rfc8776>.		<https://www.rfc-editor.org/info/rfc8776>.
			[RFC8779] Margaria, C., Ed., Gonzalez de Dios, O., Ed., and F.
			Zhang, Ed., "Path Computation Element Communication
			Protocol (PCEP) Extensions for GMPLS", RFC 8779,
			DOI 10.17487/RFC8779, July 2020,
			<https://www.rfc-editor.org/info/rfc8779>.
	15.2. Informative References		15.2. Informative References
	[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation		[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
	Element (PCE)-Based Architecture", RFC 4655,		Element (PCE)-Based Architecture", RFC 4655,
	DOI 10.17487/RFC4655, August 2006,		DOI 10.17487/RFC4655, August 2006,
	<https://www.rfc-editor.org/info/rfc4655>.		<https://www.rfc-editor.org/info/rfc4655>.
	[RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J.		[RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J.
	Hardwick, "Path Computation Element Communication Protocol		Hardwick, "Path Computation Element Communication Protocol
	(PCEP) Management Information Base (MIB) Module",		(PCEP) Management Information Base (MIB) Module",
	skipping to change at page 112, line 35 ¶		skipping to change at page 112, line 35 ¶
	Canada		Canada
	EMail: zali@cisco.com		EMail: zali@cisco.com
	Xufeng Liu		Xufeng Liu
	Volta Networks		Volta Networks
	EMail: xufeng.liu.ietf@gmail.com		EMail: xufeng.liu.ietf@gmail.com
	Young Lee		Young Lee
	Futurewei		Samsung
	5340 Legacy Drive, Building 3
	Plano, TX 75023
	USA
	EMail: younglee.tx@gmail.com		EMail: younglee.tx@gmail.com
	Udayasree Palle		Udayasree Palle
	EMail: udayasreereddy@gmail.com		EMail: udayasreereddy@gmail.com
	Xian Zhang		Xian Zhang
	Huawei Technologies		Huawei Technologies
	Bantian, Longgang District		Bantian, Longgang District
	skipping to change at page 113, line 46 ¶		skipping to change at page 113, line 44 ¶
	Vishnu Pavan Beeram		Vishnu Pavan Beeram
	Juniper Networks		Juniper Networks
	USA		USA
	EMail: vbeeram@juniper.net		EMail: vbeeram@juniper.net
	Jeff Tantsura		Jeff Tantsura
	Apstra, Inc.		Apstra, Inc.
	USA		USA
	EMail: jefftant@gmail.com		EMail: jefftant.ietf@gmail.com
End of changes. 43 change blocks.
	63 lines changed or deleted		62 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/