draft-ietf-ccamp-rwa-info-09.txt		draft-ietf-ccamp-rwa-info-10.txt
	Network Working Group Y. Lee		Network Working Group Y. Lee
	Internet Draft Huawei		Internet Draft Huawei
	Intended status: Informational G. Bernstein		Intended status: Informational G. Bernstein
	Expires: March 2011 Grotto Networking		Expires: August 2011 Grotto Networking
	D. Li		D. Li
	Huawei		Huawei
	W. Imajuku		W. Imajuku
	NTT		NTT
	September 3, 2010		February 28, 2011
	Routing and Wavelength Assignment Information Model for Wavelength		Routing and Wavelength Assignment Information Model for Wavelength
	Switched Optical Networks		Switched Optical Networks
	draft-ietf-ccamp-rwa-info-09.txt		draft-ietf-ccamp-rwa-info-10.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		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 39		skipping to change at page 1, line 39
	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."
	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 March 3, 2011.		This Internet-Draft will expire on August 28, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2011 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 respect		carefully, as they describe your rights and restrictions with respect
	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
	skipping to change at page 2, line 39		skipping to change at page 2, line 39
	1. Introduction...................................................3		1. Introduction...................................................3
	1.1. Revision History..........................................4		1.1. Revision History..........................................4
	1.1.1. Changes from 01......................................4		1.1.1. Changes from 01......................................4
	1.1.2. Changes from 02......................................4		1.1.2. Changes from 02......................................4
	1.1.3. Changes from 03......................................4		1.1.3. Changes from 03......................................4
	1.1.4. Changes from 04......................................5		1.1.4. Changes from 04......................................5
	1.1.5. Changes from 05......................................5		1.1.5. Changes from 05......................................5
	1.1.6. Changes from 06......................................5		1.1.6. Changes from 06......................................5
	1.1.7. Changes from 07......................................5		1.1.7. Changes from 07......................................5
	1.1.8. Changes from 08......................................5		1.1.8. Changes from 08......................................5
	2. Terminology....................................................5		1.1.9. Changes from 09......................................5
			2. Terminology....................................................6
	3. Routing and Wavelength Assignment Information Model............6		3. Routing and Wavelength Assignment Information Model............6
	3.1. Dynamic and Relatively Static Information.................6		3.1. Dynamic and Relatively Static Information.................7
	4. Node Information (General).....................................7		4. Node Information (General).....................................7
	4.1. Connectivity Matrix.......................................7		4.1. Connectivity Matrix.......................................7
	4.2. Shared Risk Node Group....................................8		4.2. Shared Risk Node Group....................................8
	5. Node Information (WSON specific)...............................8		5. Node Information (WSON specific)...............................9
	5.1. Resource Accessibility/Availability.......................9		5.1. Resource Accessibility/Availability......................10
	5.2. Resource Signal Constraints and Processing Capabilities..13		5.2. Resource Signal Constraints and Processing Capabilities..13
	5.3. Compatibility and Capability Details.....................14		5.3. Compatibility and Capability Details.....................14
	5.3.1. Shared Ingress or Egress Indication.................14		5.3.1. Shared Ingress or Egress Indication.................14
	5.3.2. Modulation Type List................................14		5.3.2. Modulation Type List................................14
	5.3.3. FEC Type List.......................................14		5.3.3. FEC Type List.......................................14
	5.3.4. Bit Rate Range List.................................14		5.3.4. Bit Rate Range List.................................14
	5.3.5. Acceptable Client Signal List.......................15		5.3.5. Acceptable Client Signal List.......................15
	5.3.6. Processing Capability List..........................15		5.3.6. Processing Capability List..........................15
	6. Link Information (General)....................................15		6. Link Information (General)....................................15
	6.1. Administrative Group.....................................16		6.1. Administrative Group.....................................16
	skipping to change at page 5, line 39		skipping to change at page 5, line 39
	Added shared fiber connectivity to resource pool modeling. This		Added shared fiber connectivity to resource pool modeling. This
	includes information for determining wavelength collision on an		includes information for determining wavelength collision on an
	internal fiber providing access to resource blocks.		internal fiber providing access to resource blocks.
	1.1.8. Changes from 08		1.1.8. Changes from 08
	Added PORT_WAVELENGTH_EXCLUSIVITY in the RestrictionType parameter.		Added PORT_WAVELENGTH_EXCLUSIVITY in the RestrictionType parameter.
	Added section 6.6.1 that has an example of the port wavelength		Added section 6.6.1 that has an example of the port wavelength
	exclusivity constraint.		exclusivity constraint.
			1.1.9. Changes from 09
			Section 5: clarified the way that the resource pool is modeled from
			blocks of identical resources.
			Section 5.1: grammar fixes. Removed reference to "academic" modeling
			pre-print. Clarified RBNF resource pool model details.
			Section 5.2: Formatting fixes.
	2. Terminology		2. Terminology
	CWDM: Coarse Wavelength Division Multiplexing.		CWDM: Coarse Wavelength Division Multiplexing.
	DWDM: Dense Wavelength Division Multiplexing.		DWDM: Dense Wavelength Division Multiplexing.
	FOADM: Fixed Optical Add/Drop Multiplexer.		FOADM: Fixed Optical Add/Drop Multiplexer.
	ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port		ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
	count wavelength selective switching element featuring ingress and		count wavelength selective switching element featuring ingress and
	skipping to change at page 9, line 20		skipping to change at page 9, line 34
	2. The accessibility and availability of a wavelength converter to		2. The accessibility and availability of a wavelength converter to
	convert from a given ingress wavelength on a particular ingress		convert from a given ingress wavelength on a particular ingress
	port to a desired egress wavelength on a particular egress port.		port to a desired egress wavelength on a particular egress port.
	3. Limitations on the types of signals that can be converted and the		3. Limitations on the types of signals that can be converted and the
	conversions that can be performed.		conversions that can be performed.
	For modeling purposes and encoding efficiency we group identical		For modeling purposes and encoding efficiency we group identical
	processing resources such as regenerators or wavelength converters		processing resources such as regenerators or wavelength converters
	into "blocks". The accessibility to and from any resource within a		with identical accessibility properties into "blocks". The resource
	block must be the same. The resource pool is composed of one or more		pool model is composed of one or more resource blocks where the
	blocks.		accessibility to and from any resource within a block is the same.
	This leads to the following formal high level model:		This leads to the following formal high level model:
	<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]		<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
	[<ResourcePool>]		[<ResourcePool>]
	Where		Where
	<ResourcePool> ::= <ResourceBlockInfo>...		<ResourcePool> ::= <ResourceBlockInfo>...
	[<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...]		[<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...]
	skipping to change at page 10, line 5		skipping to change at page 10, line 18
	be used to model regenerator/converter accessibility. This technique		be used to model regenerator/converter accessibility. This technique
	was generally discussed in [WSON-Frame] and consisted of a matrix to		was generally discussed in [WSON-Frame] and consisted of a matrix to
	indicate possible connectivity along with wavelength constraints for		indicate possible connectivity along with wavelength constraints for
	links/ports. Since regenerators or wavelength converters may be		links/ports. Since regenerators or wavelength converters may be
	considered a scarce resource we will also want to our model to		considered a scarce resource we will also want to our model to
	include as a minimum the usage state (availability) of individual		include as a minimum the usage state (availability) of individual
	regenerators or converters in the pool. Models that incorporate more		regenerators or converters in the pool. Models that incorporate more
	state to further reveal blocking conditions on ingress or egress to		state to further reveal blocking conditions on ingress or egress to
	particular converters are for further study and not included here.		particular converters are for further study and not included here.
	The three stage model as shown schematically in Figure 1 and Figure		The three stage model is shown schematically in Figure 1 and Figure
	2.The difference between the two figures is that in Figure 1 we		2. The difference between the two figures is that in Figure 1 we
	assume that each signal that can get to a resource block may do so,		assume that each signal that can get to a resource block may do so,
	while in Figure 2 the access to the resource blocks is via a shared		while in Figure 2 the access to the resource blocks is via a shared
	fiber which imposes its own wavelength collision constraint. In the		fiber which imposes its own wavelength collision constraint. In the
	representation of Figure 1 we can have more than one ingress to each		representation of Figure 1 we can have more than one ingress to each
	resource block since each ingress represents a single wavelength		resource block since each ingress represents a single wavelength
	signal, while in Figure 2 we show a single multiplexed WDM ingress,		signal, while in Figure 2 we show a single multiplexed WDM ingress,
	e.g., a fiber, to each block.		e.g., a fiber, to each block.
	In this model we assume N ingress ports (fibers), P resource blocks		In this model we assume N ingress ports (fibers), P resource blocks
	containing one or more identical resources (e.g. wavelength		containing one or more identical resources (e.g. wavelength
	skipping to change at page 10, line 48		skipping to change at page 11, line 12
	After that, we have a set of static resource egress wavelength		After that, we have a set of static resource egress wavelength
	constraints and possibly dynamic shared egress fiber constraints. The		constraints and possibly dynamic shared egress fiber constraints. The
	static constraints indicate what wavelengths a particular resource		static constraints indicate what wavelengths a particular resource
	block can generate or are restricted to generating e.g., a fixed		block can generate or are restricted to generating e.g., a fixed
	regenerator would be limited to a single lambda. The dynamic		regenerator would be limited to a single lambda. The dynamic
	constraints would be used in the case where a single shared fiber is		constraints would be used in the case where a single shared fiber is
	used to egress the resource block (Figure 2).		used to egress the resource block (Figure 2).
	Finally, we have a resource pool egress matrix RE(p,k) = {0,1}		Finally, we have a resource pool egress matrix RE(p,k) = {0,1}
	depending on whether the output from resource block p can reach		depending on whether the output from resource block p can reach
	egress port k. Examples of this method being used to model wavelength		egress port k.
	converter pools for several switch architectures from the literature
	are given in reference [WC-Pool].
	I1 +-------------+ +-------------+ E1		I1 +-------------+ +-------------+ E1
	----->| | +--------+ | |----->		----->| | +--------+ | |----->
	I2 | +------+ Rb #1 +-------+ | E2		I2 | +------+ Rb #1 +-------+ | E2
	----->| | +--------+ | |----->		----->| | +--------+ | |----->
	| | | |		| | | |
	| Resource | +--------+ | Resource |		| Resource | +--------+ | Resource |
	| Pool +------+ +-------+ Pool |		| Pool +------+ +-------+ Pool |
	| | + Rb #2 + | |		| | + Rb #2 + | |
	| Ingress +------+ +-------| Egress |		| Ingress +------+ +-------| Egress |
	skipping to change at page 12, line 11		skipping to change at page 12, line 11
	each resource each resource		each resource each resource
	Figure 1 Schematic diagram of resource pool model.		Figure 1 Schematic diagram of resource pool model.
	I1 +-------------+ +-------------+ E1		I1 +-------------+ +-------------+ E1
	----->| | +--------+ | |----->		----->| | +--------+ | |----->
	I2 | +======+ Rb #1 +=======+ | E2		I2 | +======+ Rb #1 +=======+ | E2
	----->| | +--------+ | |----->		----->| | +--------+ | |----->
	| | | |		| | | |
	| Resource | +--------+ | Resource |		| Resource | +--------+ | Resource |
	| Pool | | Pool | | |		| Pool | | | | Pool |
	| |======+ Rb #2 +=======+ |		| |======+ Rb #2 +=======+ |
	| Ingress | + | | Egress |		| Ingress | + | | Egress |
	| Connection | +--------+ | Connection |		| Connection | +--------+ | Connection |
	| Matrix | . | Matrix |		| Matrix | . | Matrix |
	| | . | |		| | . | |
	| | . | |		| | . | |
	IN | | +--------+ | | EM		IN | | +--------+ | | EM
	----->| +======+ Rb #P +=======+ |----->		----->| +======+ Rb #P +=======+ |----->
	| | +--------+ | |		| | +--------+ | |
	+-------------+ ^ ^ +-------------+		+-------------+ ^ ^ +-------------+
	skipping to change at page 12, line 34		skipping to change at page 12, line 34
	| |		| |
	Single (shared) fibers for block ingress and egress		Single (shared) fibers for block ingress and egress
	Ingress wavelength Egress wavelength		Ingress wavelength Egress wavelength
	availability for availability for		availability for availability for
	each block ingress fiber each block egress fiber		each block ingress fiber each block egress fiber
	Figure 2 Schematic diagram of resource pool model with shared block		Figure 2 Schematic diagram of resource pool model with shared block
	accessibility.		accessibility.
	Formally we can specify the model as:		Formally we complete the specification of the model with:
	<ResourceBlockAccessibility ::= <PoolIngressMatrix>		<ResourceBlockAccessibility ::= <PoolIngressMatrix>
	<PoolEgressMatrix>		<PoolEgressMatrix>
	[<ResourceWaveConstraints> ::= <IngressWaveConstraints>		[<ResourceWaveConstraints> ::= <IngressWaveConstraints>
	<EgressWaveConstraints>		<EgressWaveConstraints>
	<ResourcePoolState>		<RBPoolState>
	::=(<ResourceBlockID><NumResourcesInUse><InAvailableWavelengths><OutA		::=(<ResourceBlockID><NumResourcesInUse><InAvailableWavelengths><OutA
	vailableWavelengths>)...		vailableWavelengths>)...
	Note that except for <ResourcePoolState> all the other components of		Note that except for <ResourcePoolState> all the other components of
	<ResourcePool> are relatively static. Also the		<ResourcePool> are relatively static. Also the
	<InAvailableWavelengths> and <OutAvailableWavelengths> are only used		<InAvailableWavelengths> and <OutAvailableWavelengths> are only used
	in the cases of shared ingress or egress access to the particular		in the cases of shared ingress or egress access to the particular
	block. See the resource block information in the next section to see		block. See the resource block information in the next section to see
	how this is specified.		how this is specified.
	5.2. Resource Signal Constraints and Processing Capabilities		5.2. Resource Signal Constraints and Processing Capabilities
	The wavelength conversion abilities of a resource (e.g. regenerator,		The wavelength conversion abilities of a resource (e.g. regenerator,
	wavelength converter) were modeled in the <EgressWaveConstraints>		wavelength converter) were modeled in the <EgressWaveConstraints>
	previously discussed. As discussed in [WSON-Frame] we can model the		previously discussed. As discussed in [WSON-Frame] we can model the
	constraints on an electro-optical resource in terms of input		constraints on an electro-optical resource in terms of input
	constraints, processing capabilities, and output constraints:		constraints, processing capabilities, and output constraints:
	<ResourceBlockInfo> ::=		<ResourceBlockInfo> ::= ([<ResourceSet>] <InputConstraints>
	([<ResourceSet>]<InputConstraints><ProcessingCapabilities><OutputCons		<ProcessingCapabilities> <OutputConstraints>)*
	traints>)*
	Where <ResourceSet> is a list of resource block identifiers with the		Where <ResourceSet> is a list of resource block identifiers with the
	same characteristics. If this set is missing the constraints are		same characteristics. If this set is missing the constraints are
	applied to the entire network element.		applied to the entire network element.
	The <InputConstraints> are signal compatibility based constraints		The <InputConstraints> are signal compatibility based constraints
	and/or shared access constraint indication. The details of these		and/or shared access constraint indication. The details of these
	constraints are defined in section 5.3.		constraints are defined in section 5.3.
	<InputConstraints> ::= <SharedIngress><ModulationTypeList>		<InputConstraints> ::= <SharedIngress> <ModulationTypeList>
	<FECTypeList> <BitRateRange> <ClientSignalList>		<FECTypeList> <BitRateRange> <ClientSignalList>
	The <ProcessingCapabilities> are important operations that the		The <ProcessingCapabilities> are important operations that the
	resource (or network element) can perform on the signal. The details		resource (or network element) can perform on the signal. The details
	of these capabilities are defined in section 5.3.		of these capabilities are defined in section 5.3.
	<ProcessingCapabilities> ::= <NumResources>		<ProcessingCapabilities> ::= <NumResources>
	<RegenerationCapabilities> <FaultPerfMon> <VendorSpecific>		<RegenerationCapabilities> <FaultPerfMon> <VendorSpecific>
	The <OutputConstraints> are either restrictions on the properties of		The <OutputConstraints> are either restrictions on the properties of
	the signal leaving the block, options concerning the signal		the signal leaving the block, options concerning the signal
	properties when leaving the resource or shared fiber egress		properties when leaving the resource or shared fiber egress
	constraint indication.		constraint indication.
	<OutputConstraints> :=		<OutputConstraints> := <SharedEgress> <ModulationTypeList>
	<SharedEgress><ModulationTypeList><FECTypeList>		<FECTypeList>
	5.3. Compatibility and Capability Details		5.3. Compatibility and Capability Details
	5.3.1. Shared Ingress or Egress Indication		5.3.1. Shared Ingress or Egress Indication
	As discussed in the previous section and shown in Figure 2 the		As discussed in the previous section and shown in Figure 2 the
	ingress or egress access to a resource block may be via a shared		ingress or egress access to a resource block may be via a shared
	fiber. The <SharedIngress> and <SharedEgress> elements are indicators		fiber. The <SharedIngress> and <SharedEgress> elements are indicators
	for this condition with respect to the block being described.		for this condition with respect to the block being described.
	5.3.2. Modulation Type List		5.3.2. Modulation Type List
	skipping to change at page 20, line 20		skipping to change at page 20, line 20
	<DynamicLinkInfo> ::= <LinkID> <AvailableLabels>		<DynamicLinkInfo> ::= <LinkID> <AvailableLabels>
	[<SharedBackupLabels>]		[<SharedBackupLabels>]
	AvailableLabels is a set of labels (wavelengths) currently available		AvailableLabels is a set of labels (wavelengths) currently available
	on the link. Given this information and the port wavelength		on the link. Given this information and the port wavelength
	restrictions we can also determine which wavelengths are currently in		restrictions we can also determine which wavelengths are currently in
	use. This parameter could potential be used with other technologies		use. This parameter could potential be used with other technologies
	that GMPLS currently covers or may cover in the future.		that GMPLS currently covers or may cover in the future.
	SharedBackupLabels is a set of labels (wavelengths)currently used for		SharedBackupLabels is a set of labels (wavelengths) currently used
	shared backup protection on the link. An example usage of this		for shared backup protection on the link. An example usage of this
	information in a WSON setting is given in [Shared]. This parameter		information in a WSON setting is given in [Shared]. This parameter
	could potential be used with other technologies that GMPLS currently		could potential be used with other technologies that GMPLS currently
	covers or may cover in the future.		covers or may cover in the future.
	7.2. Dynamic Node Information (WSON Specific)		7.2. Dynamic Node Information (WSON Specific)
	Currently the only node information that can be considered dynamic is		Currently the only node information that can be considered dynamic is
	the resource pool state and can be isolated into a dynamic node		the resource pool state and can be isolated into a dynamic node
	information element as follows:		information element as follows:
	skipping to change at page 23, line 32		skipping to change at page 24, line 5
	networking.com/wson/iPOP2008_WSON-shared-mesh-poster.pdf .		networking.com/wson/iPOP2008_WSON-shared-mesh-poster.pdf .
	[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, " Modeling		[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, " Modeling
	WDM Wavelength Switching Systems for Use in GMPLS and Automated		WDM Wavelength Switching Systems for Use in GMPLS and Automated
	Path Computation", Journal of Optical Communications and		Path Computation", Journal of Optical Communications and
	Networking, vol. 1, June, 2009, pp. 187-195.		Networking, vol. 1, June, 2009, pp. 187-195.
	[G.Sup39] ITU-T Series G Supplement 39, Optical system design and		[G.Sup39] ITU-T Series G Supplement 39, Optical system design and
	engineering considerations, February 2006.		engineering considerations, February 2006.
	[WC-Pool] G. Bernstein, Y. Lee, "Modeling WDM Switching Systems
	including Wavelength Converters" to appear www.grotto-
	networking.com, 2008.
	12. Contributors		12. Contributors
	Diego Caviglia		Diego Caviglia
	Ericsson		Ericsson
	Via A. Negrone 1/A 16153		Via A. Negrone 1/A 16153
	Genoa Italy		Genoa Italy
	Phone: +39 010 600 3736		Phone: +39 010 600 3736
	Email: diego.caviglia@(marconi.com, ericsson.com)		Email: diego.caviglia@(marconi.com, ericsson.com)
End of changes. 20 change blocks.
	32 lines changed or deleted		36 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/