draft-ietf-ccamp-flexible-grid-rsvp-te-ext-00.txt		draft-ietf-ccamp-flexible-grid-rsvp-te-ext-01.txt
	Network Working Group Fatai Zhang		Network Working Group Fatai Zhang
	Internet-Draft Xian Zhang		Internet-Draft Xian Zhang
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Adrian Farrel		Adrian Farrel
	Old Dog Consulting		Old Dog Consulting
	Oscar Gonzalez de Dios		Oscar Gonzalez de Dios
	Telefonica		Telefonica
	D. Ceccarelli		D. Ceccarelli
	Ericsson		Ericsson
	Expires: December 20, 2014 June 20, 2014		Expires: July 6, 2015 January 7, 2015
	RSVP-TE Signaling Extensions in support of Flexible Grid		RSVP-TE Signaling Extensions in support of Flexible Grid
	draft-ietf-ccamp-flexible-grid-rsvp-te-ext-00.txt		draft-ietf-ccamp-flexible-grid-rsvp-te-ext-01.txt
	Abstract		Abstract
	This memo describes the extensions to RSVP-TE signaling to support		This memo describes the extensions to the Resource reservation
	Label Switched Paths in a GMPLS-controlled network that includes		Protocol Traffic Engineering (RSVP-TE) signaling protocol to support
	devices using the flexible optical grid.		Label Switched Paths (LSPs) in a GMPLS-controlled network that
			includes devices using the flexible optical grid.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with		This Internet-Draft is submitted to IETF in full conformance with
	the provisions of BCP 78 and BCP 79.		the provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 45		skipping to change at page 1, line 46
	documents at any time. It is inappropriate to use Internet-Drafts		documents at any time. It is inappropriate to use Internet-Drafts
	as reference material or to cite them other than as "work in		as reference material or to cite them other than as "work in
	progress."		progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on December 20, 2014.		This Internet-Draft will expire on July 6, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with
	skipping to change at page 2, line 40		skipping to change at page 2, line 40
	5. IANA Considerations ......................................... 7		5. IANA Considerations ......................................... 7
	5.1. RSVP Objects Class Types................................ 7		5.1. RSVP Objects Class Types................................ 7
	6. Manageability Considerations................................. 8		6. Manageability Considerations................................. 8
	7. Implementation Status........................................ 8		7. Implementation Status........................................ 8
	7.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)8		7.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)8
	8. Acknowledgments ............................................ 10		8. Acknowledgments ............................................ 10
	9. Security Considerations..................................... 10		9. Security Considerations..................................... 10
	10. References ................................................ 10		10. References ................................................ 10
	10.1. Normative References.................................. 10		10.1. Normative References.................................. 10
	10.2. Informative References................................ 10		10.2. Informative References................................ 10
	11. Contributors' Address...................................... 11		11. Contributors' Addresses.................................... 11
	12. Authors' Addresses .........................................12		12. Authors' Addresses ......................................... 12
	1. Introduction		1. Introduction
	[G.694.1] defines the Dense Wavelength Division Multiplexing (DWDM)		[G.694.1] defines the Dense Wavelength Division Multiplexing (DWDM)
	frequency grids for Wavelength Division Multiplexing (WDM)		frequency grids for Wavelength Division Multiplexing (WDM)
	applications. A frequency grid is a reference set of frequencies		applications. A frequency grid is a reference set of frequencies
	used to denote allowed nominal central frequencies that may be used		used to denote allowed nominal central frequencies that may be used
	for defining applications that utilize WDM transmission. The channel		for defining applications that utilize WDM transmission. The channel
	spacing is the frequency spacing between two allowed nominal central		spacing is the frequency spacing between two allowed nominal central
	frequencies. All of the wavelengths on a fiber use different central		frequencies. All of the wavelengths on a fiber use different central
	skipping to change at page 3, line 48		skipping to change at page 3, line 48
	"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 RFC-2119 [RFC2119].		document are to be interpreted as described in RFC-2119 [RFC2119].
	3. Requirements for Flexible Grid Signaling		3. Requirements for Flexible Grid Signaling
	The architecture for establishing LSPs in a flexi-grid network is		The architecture for establishing LSPs in a flexi-grid network is
	described in [FLEX-FWK].		described in [FLEX-FWK].
	An optical spectrum LSP occupies a specific frequency slot, i.e., a		An optical spectrum LSP occupies a specific frequency slot, i.e., a
	range of frequencies. The process of computing a route and the		range of frequencies. The process of computing a route and the
	allocation of a frequency slot is referred to as RSA (Routing and		allocation of a frequency slot is referred to as Routing and
	Spectrum Assignment). [FLEX-FWK] describes three architectural		Spectrum Assignment (RSA). [FLEX-FWK] describes three architectural
	approaches to RSA: combined RSA, separated RSA, and distributed SA.		approaches to RSA: combined RSA, separated RSA, and distributed SA.
	The first two approaches are referred to as ''centralized SA'' because		The first two approaches are referred to as ''centralized SA'' because
	both routing and spectrum (frequency slot) assignment are performed		both routing and spectrum (frequency slot) assignment are performed
	by a centralized entity before the signaling procedure.		by a centralized entity before the signaling procedure.
	In the case of centralized SA the assigned frequency slot is		In the case of centralized SA, the assigned frequency slot is
	specified in the RSVP-TE Path message during LSP setup. In the case		specified in the RSVP-TE Path message during LSP setup. In the case
	of distributed SA, the slot width of the flexi-grid LSP is specified		of distributed SA, the slot width of the flexi-grid LSP is specified
	in the Path message, allowing the network elements to select the		in the Path message, allowing the network elements to select the
	frequency slot to be used when they process the RSVP-TE messages.		frequency slot to be used when they process the RSVP-TE messages.
	If the capability to switch or convert the whole optical spectrum		If the capability to switch or convert the whole optical spectrum
	allocated to an optical spectrum LSP is not available at some nodes		allocated to an optical spectrum LSP is not available at some nodes
	along the path of the LSP, the LSP is subject to the Optical		along the path of the LSP, the LSP is subject to the Optical
	''Spectrum Continuity Constraint'' as described in [FLEX-FWK].		''Spectrum Continuity Constraint'' as described in [FLEX-FWK].
	skipping to change at page 5, line 29		skipping to change at page 5, line 29
	193.1 + n * 0.00625		193.1 + n * 0.00625
	where n is zero or a positive or negative integer.		where n is zero or a positive or negative integer.
	The slot width (in GHz) is defined as:		The slot width (in GHz) is defined as:
	12.5 * m		12.5 * m
	where m is a positive integer.		where m is a positive integer.
	It is possible that implementing a subset of the possible slot		It is possible that an implementation supports only a subset of the
	widths and central frequencies are supported. For example, an		possible slot widths and central frequencies. For example, an
	implementation could built where the nominal central frequency		implementation could be built where the nominal central frequency
	granularity is 12.5 GHz (by only requiring values of n that are even)		granularity is 12.5 GHz (by only allowing values of n that are even)
	and that only supports slot widths as a multiple of 25 GHz (by only		and that only supports slot widths as a multiple of 25 GHz (by only
	allowing values of m that are even).		allowing values of m that are even).
	Further details can be found in [FLEX-FWK].		Further details can be found in [FLEX-FWK].
	4. Protocol Extensions		4. Protocol Extensions
	This section defines the extensions to RSVP-TE signaling for GMPLS		This section defines the extensions to RSVP-TE signaling for GMPLS
	[RFC3473] to support flexible grid networks.		[RFC3473] to support flexible grid networks.
	skipping to change at page 7, line 8		skipping to change at page 7, line 8
	4.2. Generalized Label		4.2. Generalized Label
	In the case of a flexible grid network, the labels that have been		In the case of a flexible grid network, the labels that have been
	requested or allocated as signaled in the RSVP-TE objects are		requested or allocated as signaled in the RSVP-TE objects are
	encoded as described in [FLEX-LBL]. This new label encoding can		encoded as described in [FLEX-LBL]. This new label encoding can
	appear in any RSVP-TE object or sub-object that can carry a label.		appear in any RSVP-TE object or sub-object that can carry a label.
	As noted in Section 4.2 of [FLEX-LBL], the m parameter forms part of		As noted in Section 4.2 of [FLEX-LBL], the m parameter forms part of
	the label as well as part of the traffic parameters.		the label as well as part of the traffic parameters.
			As described in Section 4.3 of [FLEX-LBL], a ''compound label'',
			constructed from a concatenation of the flexi-grid LABELs, is used
			when signaling an LSP that uses multiple flexi-grid slots.
	4.3. Signaling Procedures		4.3. Signaling Procedures
	There are no differences between the signaling procedure described		There are no differences between the signaling procedure described
	for LSP control in [FLEX-FWK] and those required for use in a fixed-		for LSP control in [FLEX-FWK] and those required for use in a fixed-
	grid network [WSON-SIG]. Obviously, the TSpec, FlowSpec, and label		grid network [WSON-SIG]. Obviously, the TSpec, FlowSpec, and label
	formats described in Section 3 are used. The signaling procedures		formats described in Sections 4.1 and 4.2 are used. The signaling
	for distributed SA and centralized SA can be applied.		procedures for distributed SA and centralized SA can be applied.
	5. IANA Considerations		5. IANA Considerations
	5.1. RSVP Objects Class Types		5.1. RSVP Objects Class Types
	This document introduces two new Class Types for existing RSVP		This document introduces two new Class Types for existing RSVP
	objects. IANA is requested to make allocations from the "Resource		objects. IANA is requested to make allocations from the "Resource
	ReSerVation Protocol (RSVP) Parameters" registry using the "Class		ReSerVation Protocol (RSVP) Parameters" registry using the "Class
	Names, Class Numbers, and Class Types" sub-registry.		Names, Class Numbers, and Class Types" sub-registry.
	Class Number Class Name Reference		Class Number Class Name Reference
	------------ ----------------------- ---------		------------ ----------------------- ---------
	9 FLOWSPEC [RFC2205]		9 FLOWSPEC [RFC2205]
	Class Type (C-Type):		Class Type (C-Type):
	(TBD2) SSON FLOWSPEC [This.I-D]		(TBD2) SSON FLOWSPEC [This.I-D]
	Class Number Class Name Reference		Class Number Class Name Reference
	------------ ----------------------- ---------		------------ ----------------------- ---------
	12 SENDER_TSPEC [RFC2205]		12 SENDER_TSPEC [RFC2205]
	Class Type (C-Type):		Class Type (C-Type):
	(TBD1) SSON SENDER_TSPEC [This.I-D]		(TBD1) SSON SENDER_TSPEC [This.I-D]
	IANA is requested to assign the same value for TBD1 and TBD2, and a		IANA is requested to assign the same value for TBD1 and TBD2, and a
	skipping to change at page 10, line 34		skipping to change at page 10, line 34
	[RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label		[RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label
	Switching (GMPLS) Signaling Resource ReserVation Protocol-		Switching (GMPLS) Signaling Resource ReserVation Protocol-
	Traffic Engineering (RSVP-TE) Extensions", RFC 3473,		Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
	January 2003.		January 2003.
	[G.694.1] ITU-T Recommendation G.694.1 (revision 2), ''Spectral grids		[G.694.1] ITU-T Recommendation G.694.1 (revision 2), ''Spectral grids
	for WDM applications: DWDM frequency grid'', February 2012.		for WDM applications: DWDM frequency grid'', February 2012.
	[FLEX-LBL]King, D., Farrel, A. and Y. Li, ''Generalized Labels for		[FLEX-LBL]King, D., Farrel, A. and Y. Li, ''Generalized Labels for
	the Flexi-Grid in Lambda Switched Capable (LSC) Label		the Flexi-Grid in Lambda Switched Capable (LSC) Label
	Switching Routers'', draft-farrkingel-ccamp-flexigrid-		Switching Routers'', draft-ietf-ccamp-flexigrid-lambda-
	lambda-label, work in progress.		label, work in progress.
	10.2. Informative References		10.2. Informative References
	[RFC2205] Braden, R., Zhang L., Berson, S., Herzog, S. and S. Jamin,		[RFC2205] Braden, R., Zhang L., Berson, S., Herzog, S. and S. Jamin,
	''Resource ReServation Protocol (RSVP) - - Version 1,		''Resource ReServation Protocol (RSVP) - - Version 1,
	Functional Specification', RFC2205, September 1997.		Functional Specification', RFC2205, September 1997.
	[RFC5920] L. Fang et al., "Security Framework for MPLS and GMPLS		[RFC5920] L. Fang et al., "Security Framework for MPLS and GMPLS
	Networks", RFC 5920, July 2010.		Networks", RFC 5920, July 2010.
	skipping to change at page 11, line 12		skipping to change at page 11, line 12
	and Path Computation Element (PCE) Control of Wavelength		and Path Computation Element (PCE) Control of Wavelength
	Switched Optical Networks (WSONs)", RFC 6163, April 2011.		Switched Optical Networks (WSONs)", RFC 6163, April 2011.
	[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running		[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
	Code: The Implementation Status Section", RFC 6982, July		Code: The Implementation Status Section", RFC 6982, July
	2013.		2013.
	[RFC Editor Note: This reference can be removed when Section 7 is		[RFC Editor Note: This reference can be removed when Section 7 is
	removed]		removed]
	[FLEX-FWK] Gonzalez de Dios, O,, Casellas R., Zhang, F., Fu, X.,		[FLEX-FWK] Gonzalez de Dios, O, Casellas R., Zhang, F., Fu, X.,
	Ceccarelli, D., and I. Hussain, ''Framework and		Ceccarelli, D., and I. Hussain, ''Framework and
	Requirements for GMPLS based control of Flexi-grid DWDM		Requirements for GMPLS based control of Flexi-grid DWDM
	networks', draft-ogrcetal-cammp-flexi-grid-fwk, work in		networks', draft-ietf-cammp-flexi-grid-fwk, work in
	progress.		progress.
	[WSON-SIG] G. Bernstein, Sugang Xu, Y. Lee, G. Martinelli and		[WSON-SIG] G. Bernstein, Sugang Xu, Y. Lee, G. Martinelli and
	Hiroaki Harai, "Signaling Extensions for Wavelength		Hiroaki Harai, "Signaling Extensions for Wavelength
	Switched Optical Networks", draft-ietf-ccamp-wson-		Switched Optical Networks", draft-ietf-ccamp-wson-
	signaling, work in progress.		signaling, work in progress.
	11. Contributors' Address		11. Contributors' Addresses
	Ramon Casellas		Ramon Casellas
	CTTC		CTTC
	Av. Carl Friedrich Gauss n7		Av. Carl Friedrich Gauss n7
	Castelldefels, Barcelona 08860		Castelldefels, Barcelona 08860
	Spain		Spain
	Email: ramon.casellas@cttc.es		Email: ramon.casellas@cttc.es
	Felipe Jimenez Arribas		Felipe Jimenez Arribas
End of changes. 15 change blocks.
	23 lines changed or deleted		28 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/