< draft-chen-pce-h-sdns-02.txt		draft-chen-pce-h-sdns-03.txt >
	PCE Working Group H. Chen		PCE Working Group H. Chen
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track M. Toy		Intended status: Standards Track M. Toy
	Expires: November 5, 2017 Verizon		Expires: May 3, 2018 Verizon
	L. Liu		L. Liu
	Fujitsu		Fujitsu
	V. Liu		V. Liu
	China Mobile		China Mobile
	May 4, 2017		October 30, 2017
	PCE Hierarchical SDNs		PCE Hierarchical SDNs
	draft-chen-pce-h-sdns-02		draft-chen-pce-h-sdns-03
	Abstract		Abstract
	This document presents extensions to the Path Computation Element		This document presents extensions to the Path Computation Element
	Communication Protocol (PCEP) for supporting a hierarchical SDN		Communication Protocol (PCEP) for supporting a hierarchical SDN
	control system, which comprises multiple SDN controllers controlling		control system, which comprises multiple SDN controllers controlling
	a network with a number of domains.		a network with a number of domains.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 November 5, 2017.		This Internet-Draft will expire on May 3, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 56, line 38 ¶		skipping to change at page 56, line 38 ¶
	The authors would like to thank people for their valuable comments on		The authors would like to thank people for their valuable comments on
	this draft.		this draft.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[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, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
	RFC2119, March 1997,		RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[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, DOI 10.17487/		Element (PCE)-Based Architecture", RFC 4655, DOI 10.17487/
	RFC4655, August 2006,		RFC4655, August 2006,
	<http://www.rfc-editor.org/info/rfc4655>.		<https://www.rfc-editor.org/info/rfc4655>.
	[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation		[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
	Element (PCE) Communication Protocol (PCEP)", RFC 5440,		Element (PCE) Communication Protocol (PCEP)", RFC 5440,
	DOI 10.17487/RFC5440, March 2009,		DOI 10.17487/RFC5440, March 2009,
	<http://www.rfc-editor.org/info/rfc5440>.		<https://www.rfc-editor.org/info/rfc5440>.
	[RFC5441] Vasseur, JP., Ed., Zhang, R., Bitar, N., and JL. Le Roux,		[RFC5441] Vasseur, JP., Ed., Zhang, R., Bitar, N., and JL. Le Roux,
	"A Backward-Recursive PCE-Based Computation (BRPC)		"A Backward-Recursive PCE-Based Computation (BRPC)
	Procedure to Compute Shortest Constrained Inter-Domain		Procedure to Compute Shortest Constrained Inter-Domain
	Traffic Engineering Label Switched Paths", RFC 5441,		Traffic Engineering Label Switched Paths", RFC 5441,
	DOI 10.17487/RFC5441, April 2009,		DOI 10.17487/RFC5441, April 2009,
	<http://www.rfc-editor.org/info/rfc5441>.		<https://www.rfc-editor.org/info/rfc5441>.
	[RFC5392] Chen, M., Zhang, R., and X. Duan, "OSPF Extensions in		[RFC5392] Chen, M., Zhang, R., and X. Duan, "OSPF Extensions in
	Support of Inter-Autonomous System (AS) MPLS and GMPLS		Support of Inter-Autonomous System (AS) MPLS and GMPLS
	Traffic Engineering", RFC 5392, DOI 10.17487/RFC5392,		Traffic Engineering", RFC 5392, DOI 10.17487/RFC5392,
	January 2009, <http://www.rfc-editor.org/info/rfc5392>.		January 2009, <https://www.rfc-editor.org/info/rfc5392>.
	[RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in		[RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in
	Support of Inter-Autonomous System (AS) MPLS and GMPLS		Support of Inter-Autonomous System (AS) MPLS and GMPLS
	Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316,		Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316,
	December 2008, <http://www.rfc-editor.org/info/rfc5316>.		December 2008, <https://www.rfc-editor.org/info/rfc5316>.
	[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic		[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
	Engineering", RFC 5305, DOI 10.17487/RFC5305,		Engineering", RFC 5305, DOI 10.17487/RFC5305,
	October 2008, <http://www.rfc-editor.org/info/rfc5305>.		October 2008, <https://www.rfc-editor.org/info/rfc5305>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003,
	<http://www.rfc-editor.org/info/rfc3630>.		<https://www.rfc-editor.org/info/rfc3630>.
	10.2. Informative References		10.2. Informative References
	[RFC1136] Hares, S. and D. Katz, "Administrative Domains and Routing		[RFC1136] Hares, S. and D. Katz, "Administrative Domains and Routing
	Domains: A model for routing in the Internet", RFC 1136,		Domains: A model for routing in the Internet", RFC 1136,
	DOI 10.17487/RFC1136, December 1989,		DOI 10.17487/RFC1136, December 1989,
	<http://www.rfc-editor.org/info/rfc1136>.		<https://www.rfc-editor.org/info/rfc1136>.
	[RFC4105] Le Roux, J., Ed., Vasseur, J., Ed., and J. Boyle, Ed.,		[RFC4105] Le Roux, J., Ed., Vasseur, J., Ed., and J. Boyle, Ed.,
	"Requirements for Inter-Area MPLS Traffic Engineering",		"Requirements for Inter-Area MPLS Traffic Engineering",
	RFC 4105, DOI 10.17487/RFC4105, June 2005,		RFC 4105, DOI 10.17487/RFC4105, June 2005,
	<http://www.rfc-editor.org/info/rfc4105>.		<https://www.rfc-editor.org/info/rfc4105>.
	[RFC4216] Zhang, R., Ed. and J. Vasseur, Ed., "MPLS Inter-Autonomous		[RFC4216] Zhang, R., Ed. and J. Vasseur, Ed., "MPLS Inter-Autonomous
	System (AS) Traffic Engineering (TE) Requirements",		System (AS) Traffic Engineering (TE) Requirements",
	RFC 4216, DOI 10.17487/RFC4216, November 2005,		RFC 4216, DOI 10.17487/RFC4216, November 2005,
	<http://www.rfc-editor.org/info/rfc4216>.		<https://www.rfc-editor.org/info/rfc4216>.
	[RFC6006] Zhao, Q., Ed., King, D., Ed., Verhaeghe, F., Takeda, T.,		[RFC6006] Zhao, Q., Ed., King, D., Ed., Verhaeghe, F., Takeda, T.,
	Ali, Z., and J. Meuric, "Extensions to the Path		Ali, Z., and J. Meuric, "Extensions to the Path
	Computation Element Communication Protocol (PCEP) for		Computation Element Communication Protocol (PCEP) for
	Point-to-Multipoint Traffic Engineering Label Switched		Point-to-Multipoint Traffic Engineering Label Switched
	Paths", RFC 6006, DOI 10.17487/RFC6006, September 2010,		Paths", RFC 6006, DOI 10.17487/RFC6006, September 2010,
	<http://www.rfc-editor.org/info/rfc6006>.		<https://www.rfc-editor.org/info/rfc6006>.
	[RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the		[RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the
	Path Computation Element Architecture to the Determination		Path Computation Element Architecture to the Determination
	of a Sequence of Domains in MPLS and GMPLS", RFC 6805,		of a Sequence of Domains in MPLS and GMPLS", RFC 6805,
	DOI 10.17487/RFC6805, November 2012,		DOI 10.17487/RFC6805, November 2012,
	<http://www.rfc-editor.org/info/rfc6805>.		<https://www.rfc-editor.org/info/rfc6805>.
	Appendix A. Details on Embedded Encoding of Messages		Appendix A. Details on Embedded Encoding of Messages
	A new options field of 3 bits is defined in the flags field of the RP		A new options field of 3 bits is defined in the flags field of the RP
	object to tell the receiver of the message that the request/reply is		object to tell the receiver of the message that the request/reply is
	for one of the five request/reply messages for supporting HSCS as		for one of the five request/reply messages for supporting HSCS as
	follows:		follows:
	Options Meaning		Options Meaning
	1 Path Segment Computation Request/Reply		1 Path Segment Computation Request/Reply
End of changes. 17 change blocks.
	17 lines changed or deleted		17 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/