draft-ietf-ccamp-rwa-info-02.txt   draft-ietf-ccamp-rwa-info-03.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: September 2009 Grotto Networking Expires: January 2010 Grotto Networking
D. Li D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
March 3, 2009 July 10, 2009
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-02.txt draft-ietf-ccamp-rwa-info-03.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 September 3, 2009. This Internet-Draft will expire on November 10, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This document provides a model of information needed by the routing This document provides a model of information needed by the routing
and wavelength assignment (RWA) process in wavelength switched and wavelength assignment (RWA) process in wavelength switched
optical networks (WSONs). The purpose of the information described optical networks (WSONs). The purpose of the information described
in this model is to facilitate constrained lightpath computation in in this model is to facilitate constrained lightpath computation in
WSONs, particularly in cases where there are no or a limited number WSONs, particularly in cases where there are no or a limited number
of wavelength converters available. This model does not include of wavelength converters available. This model does not include
optical impairments. optical impairments.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Revision History..........................................3 1.1. Revision History..........................................3
1.1.1. Changes from 01......................................3 1.1.1. Changes from 01......................................3
2. Terminology....................................................3 1.1.2. Changes from 02......................................3
2. Terminology....................................................4
3. Routing and Wavelength Assignment Information Model............4 3. Routing and Wavelength Assignment Information Model............4
3.1. Dynamic and Relatively Static Information.................4 3.1. Dynamic and Relatively Static Information.................5
3.2. Node Information..........................................5 3.2. Node Information..........................................5
3.2.1. Switched Connectivity Matrix.........................5 3.2.1. Connectivity Matrix..................................6
3.2.2. Fixed Connectivity Matrix............................6 3.2.2. Shared Risk Node Group...............................6
3.2.3. Shared Risk Node Group...............................6 3.2.3. Wavelength Converter Pool............................7
3.2.4. Wavelength Converter Pool............................6 3.2.4. OEO Wavelength Converter Info.......................10
3.2.4.1. OEO Wavelength Converter Info...................9 3.3. Link Information.........................................10
3.3. Link Information..........................................9 3.3.1. Link ID.............................................11
3.3.1. Link ID.............................................10 3.3.2. Administrative Group................................11
3.3.2. Administrative Group................................10 3.3.3. Interface Switching Capability Descriptor...........11
3.3.3. Interface Switching Capability Descriptor...........10 3.3.4. Link Protection Type (for this link)................11
3.3.4. Link Protection Type (for this link)................10 3.3.5. Shared Risk Link Group Information..................11
3.3.5. Shared Risk Link Group Information..................10 3.3.6. Traffic Engineering Metric..........................12
3.3.6. Traffic Engineering Metric..........................11 3.3.7. Port Wavelength (label) Restrictions................12
3.3.7. Maximum Bandwidth Per Channel.......................11 3.4. Dynamic Link Information.................................13
3.3.8. Switched and Fixed Port Wavelength Restrictions.....11 3.5. Dynamic Node Information.................................14
3.4. Dynamic Link Information.................................12 4. Security Considerations.......................................14
3.5. Dynamic Node Information.................................12 5. IANA Considerations...........................................15
4. Security Considerations.......................................13 6. Acknowledgments...............................................15
5. IANA Considerations...........................................13 7. References....................................................16
6. Acknowledgments...............................................13 7.1. Normative References.....................................16
7. References....................................................14 7.2. Informative References...................................16
7.1. Normative References.....................................14 8. Contributors..................................................17
7.2. Informative References...................................14 Author's Addresses...............................................18
8. Contributors..................................................15 Intellectual Property Statement..................................18
Author's Addresses...............................................16 Disclaimer of Validity...........................................19
Intellectual Property Statement..................................16
Disclaimer of Validity...........................................17
1. Introduction 1. Introduction
The purpose of the following information model for WSONs is to The purpose of the following information model for WSONs is to
facilitate constrained lightpath computation and as such is not a facilitate constrained lightpath computation and as such is not a
general purpose network management information model. In particular general purpose network management information model. In particular
this model has particular value in the cases where there are no or a this model has particular value in the cases where there are no or a
limited number of wavelength converters available in the WSON. This limited number of wavelength converters available in the WSON. This
constraint is frequently referred to as the "wavelength continuity" constraint is frequently referred to as the "wavelength continuity"
constraint, and the corresponding constrained lightpath computation constraint, and the corresponding constrained lightpath computation
skipping to change at page 3, line 42 skipping to change at page 3, line 40
Added text on the relationship between SRNG and SRLG and encoding Added text on the relationship between SRNG and SRLG and encoding
considerations. considerations.
Added clarifying text on the meaning and use of port/wavelength Added clarifying text on the meaning and use of port/wavelength
restrictions. restrictions.
Added clarifying text on wavelength availability information and how Added clarifying text on wavelength availability information and how
to derive wavelengths currently in use. to derive wavelengths currently in use.
1.1.2. Changes from 02
Integrated switched and fixed connectivity matrices into a single
"connectivity matrix" model. Added numbering of matrices to allow for
wavelength (time slot, label) dependence of the connectivity.
Discussed general use of this node parameter beyond WSON.
Integrated switched and fixed port wavelength restrictions into a
single port wavelength restriction of which there can be more than
one and added a reference to the corresponding connectivity matrix if
there is one. Also took into account port wavelength restrictions in
the case of symmetric switches, developed a uniform model and
specified how general label restrictions could be taken into account
with this model.
Removed the Shared Risk Node Group parameter from the node info, but
left explanation of how the same functionality can be achieved with
existing GMPLS SRLG constructs.
Removed Maximum bandwidth per channel parameter from link
information.
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 5, line 31 skipping to change at page 5, line 48
include properties of wavelength converters in the node if any are include properties of wavelength converters in the node if any are
present. In [Switch] it was shown that the wavelength connectivity present. In [Switch] it was shown that the wavelength connectivity
constraints for a large class of practical WSON devices can be constraints for a large class of practical WSON devices can be
modeled via switched and fixed connectivity matrices along with modeled via switched and fixed connectivity matrices along with
corresponding switched and fixed port constraints. We include these corresponding switched and fixed port constraints. We include these
connectivity matrices with our node information the switched and connectivity matrices with our node information the switched and
fixed port wavelength constraints with the link information. fixed port wavelength constraints with the link information.
Formally, Formally,
<Node_Information> ::= <Node_ID> [<SwitchedConnectivityMatrix>] <Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
[<FixedConnectivityMatrix>], [<SRNG>] [<WavelengthConverterPool>] [<WavelengthConverterPool>]
Where the Node_ID would be an appropriate identifier for the node Where the Node_ID would be an appropriate identifier for the node
within the WSON RWA context. within the WSON RWA context.
It is TBD whether multiple switched and fixed connectivity matrices Note that multiple connectivity matrices are allowed and hence can
should optionally be allowed to fully support the most general cases fully support the most general cases enumerated in [Switch].
enumerated in [Switch]. To support multiple matrices each of the
matrices below would need an identifier so that its particular
port/wavelength constraints can be associated.
3.2.1. Switched Connectivity Matrix 3.2.1. Connectivity Matrix
The switched connectivity matrix (SwitchConnectivityMatrix) The connectivity matrix (ConnectivityMatrix) represents either the
represents the potential connectivity matrix for asymmetric switches potential connectivity matrix for asymmetric switches (e.g. ROADMs
(e.g. ROADMs and such). Note that this matrix does not represent any and such) or fixed connectivity for an asymmetric device such as a
particular internal blocking behavior but indicates which ingress multiplexer. Note that this matrix does not represent any particular
ports and wavelengths could possibly be connected to a particular internal blocking behavior but indicates which ingress ports and
output port. Representing internal state dependent blocking for a wavelengths could possibly be connected to a particular output port.
switch or ROADM is beyond the scope of this document and due to its Representing internal state dependent blocking for a switch or ROADM
highly implementation dependent nature would not be subject to is beyond the scope of this document and due to it's highly
implementation dependent nature would not be subject to
standardization. This is a conceptual M by N matrix representing the standardization. This is a conceptual M by N matrix representing the
potential switched connectivity, where M represents the number of potential switched or fixed connectivity, where M represents the
ingress ports and N the number of egress ports. We say this is a number of ingress ports and N the number of egress ports. We say this
"conceptual" since this matrix tends to exhibit structure that allows is a "conceptual" since this matrix tends to exhibit structure that
for very compact representations that are useful for both allows for very compact representations that are useful for both
transmission and path computation [Encode]. transmission and path computation [Encode].
SwitchedConnectivityMatrix(i, j) = 0 or 1 depending on whether Note that the connectivity matrix concept can be useful in any
ingress port i can connect to egress port j for one or more context where asymmetric switches are utilized.
wavelengths.
3.2.2. Fixed Connectivity Matrix ConnectivityMatrix(i, j) ::= <MatrixID> <ConnType> <Matrix>
The fixed connectivity matrix (FixedConnectivityMatrix) represents Where
the connectivity for asymmetric fixed devices or the fixed part of a
"hybrid" device [Switch]. This is a conceptual M by N matrix, where M
represents the number of ingress ports and N the number of egress
ports. We say this is a "conceptual" since this matrix tends to
exhibit structure that allows for very compact representations.
FixedConnectivityMatrix(i, j) = 0 or 1 depending on whether ingress <MatrixID> is a unique identifier for the matrix. The MatrixID of 0
port i is connected to egress port j for one or more wavelengths. (zero) is reserved (see section 3.3.7.
3.2.3. Shared Risk Node Group <ConnType> can be either 0 or 1 depending upon whether the
connectivity is either fixed or potentially switched.
<Matrix> represents the fixed or switched connectivity in that
Matrix(i, j) = 0 or 1 depending on whether ingress port i can connect
to egress port j for one or more wavelengths.
3.2.2. Shared Risk Node Group
SRNG: Shared risk group for nodes. The concept of a shared risk link SRNG: Shared risk group for nodes. The concept of a shared risk link
group was defined in [RFC4202]. This can be used to achieve a desired group was defined in [RFC4202]. This can be used to achieve a desired
"amount" of link diversity. It is also desirable to have a similar "amount" of link diversity. It is also desirable to have a similar
capability to achieve various degrees of node diversity. This is capability to achieve various degrees of node diversity. This is
explained in [G.7715]. Typical risk groupings for nodes can include explained in [G.7715]. Typical risk groupings for nodes can include
those nodes in the same building, within the same city, or geographic those nodes in the same building, within the same city, or geographic
region. region.
Since the failure of a node implies the failure of all links Since the failure of a node implies the failure of all links
associated with that node a sufficiently general shared risk link associated with that node a sufficiently general shared risk link
group (SRLG) encoding, such as that used in GMPLS routing extensions group (SRLG) encoding, such as that used in GMPLS routing extensions
can explicitly incorporate SRNG information. can explicitly incorporate SRNG information.
3.2.4. Wavelength Converter Pool 3.2.3. Wavelength Converter Pool
A WSON node may include wavelength converters. These are usually A WSON node may include wavelength converters. These are usually
arranged into some type of pool to promote resource sharing. There arranged into some type of pool to promote resource sharing. There
are a number of different approaches used in the design of switches are a number of different approaches used in the design of switches
with converter pools. However, from the point of view of path with converter pools. However, from the point of view of path
computation we need to know the following: computation we need to know the following:
1. The nodes that support wavelength conversion. 1. The nodes that support wavelength conversion.
2. The accessibility and availability of a wavelength converter to 2. The accessibility and availability of a wavelength converter to
skipping to change at page 9, line 10 skipping to change at page 10, line 10
<WavelengthConverterPool> ::= <PoolIngressMatrix> <WavelengthConverterPool> ::= <PoolIngressMatrix>
<IngressPoolConstraints> [<WCPoolState>] <EgressPoolConstraints> <IngressPoolConstraints> [<WCPoolState>] <EgressPoolConstraints>
<PoolEgressMatrix> <PoolEgressMatrix>
Note that except for <WCPoolState> all the other components of Note that except for <WCPoolState> all the other components of
<WavelengthConverterPool> are relatively static. In addition <WavelengthConverterPool> are relatively static. In addition
<WCPoolState> is a relatively small structure compared potentially to <WCPoolState> is a relatively small structure compared potentially to
the others and hence in a future revision of this document maybe the others and hence in a future revision of this document maybe
moved to a new section on dynamic node information. moved to a new section on dynamic node information.
3.2.4.1. OEO Wavelength Converter Info 3.2.4. OEO Wavelength Converter Info
An OEO based wavelength converter can be characterized by an input An OEO based wavelength converter can be characterized by an input
wavelength set and an output wavelength set. In addition any wavelength set and an output wavelength set. In addition any
constraints on the signal formats and rates accommodated by the constraints on the signal formats and rates accommodated by the
converter must be described. Such a wavelength converter can be converter must be described. Such a wavelength converter can be
modeled by: modeled by:
<OEOWavelengthConverterInfo> ::= <RegeneratorType> [<BitRateRange>] <OEOWavelengthConverterInfo> ::= <RegeneratorType> [<BitRateRange>]
[<AcceptableSignals>] [<AcceptableSignals>]
skipping to change at page 10, line 12 skipping to change at page 11, line 12
additional link related constraints. These stem from WDM line system additional link related constraints. These stem from WDM line system
characterization, laser transmitter tuning restrictions, and characterization, laser transmitter tuning restrictions, and
switching subsystem port wavelength constraints, e.g., colored ROADM switching subsystem port wavelength constraints, e.g., colored ROADM
drop ports. drop ports.
In the following summarize both information from existing route In the following summarize both information from existing route
protocols and new information that maybe needed by the RWA process. protocols and new information that maybe needed by the RWA process.
<LinkInfo> ::= <LinkID> [<AdministrativeGroup>] [<InterfaceCapDesc>] <LinkInfo> ::= <LinkID> [<AdministrativeGroup>] [<InterfaceCapDesc>]
[<Protection>] [<SRLG>]... [<TrafficEngineeringMetric>] [<Protection>] [<SRLG>]... [<TrafficEngineeringMetric>]
[<MaximumBandwidthPerChannel>] <[SwitchedPortWavelengthRestriction>] [<PortWavelengthRestriction>]
[<FixedPortWavelengthRestriction>]
3.3.1. Link ID 3.3.1. Link ID
<LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID> <LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID>
<RemoteNodeID> <RemoteNodeID>
Here we can generally identify a link via a combination of local and Here we can generally identify a link via a combination of local and
remote node identifiers along with the corresponding local and remote remote node identifiers along with the corresponding local and remote
link identifiers per [RFC4202, RFC4203, RFC5307]. Note that reference link identifiers per [RFC4202, RFC4203, RFC5307]. Note that reference
[RFC3630] provides other ways to identify local and remote link ends [RFC3630] provides other ways to identify local and remote link ends
skipping to change at page 11, line 17 skipping to change at page 12, line 15
3.3.6. Traffic Engineering Metric 3.3.6. Traffic Engineering Metric
TrafficEngineeringMetric: Defined in [RFC3630]. This allows for the TrafficEngineeringMetric: Defined in [RFC3630]. This allows for the
definition of one additional link metric value for traffic definition of one additional link metric value for traffic
engineering separate from the IP link state routing protocols link engineering separate from the IP link state routing protocols link
metric. Note that multiple "link metric values" could find use in metric. Note that multiple "link metric values" could find use in
optical networks, however it would be more useful to the RWA process optical networks, however it would be more useful to the RWA process
to assign these specific meanings such as link mile metric, or to assign these specific meanings such as link mile metric, or
probability of failure metric, etc... probability of failure metric, etc...
3.3.7. Maximum Bandwidth Per Channel 3.3.7. Port Wavelength (label) Restrictions
TBD: Need to check if we still want this.
3.3.8. Switched and Fixed Port Wavelength Restrictions
Switch and fixed port wavelength restrictions Port wavelength (label) restrictions (PortWavelengthRestriction)
(SwitchedPortWavelengthRestriction, FixedPortWavelengthRestriction) model the wavelength (label) restrictions that the link and various
model the wavelength restrictions that various optical devices such optical devices such as OXCs, ROADMs, and waveband multiplexers may
as OXCs, ROADMs, and waveband multiplexers may impose on a port. impose on a port. These restrictions tell us what wavelength may or
These restrictions tell us what wavelength may or may not be used on may not be used on a link and are relatively static. This plays an
a link and are relatively static. This plays an important role in important role in fully characterizing a WSON switching device
fully characterizing a WSON switching device [Switch]. The [Switch]. Port wavelength restrictions are specified relative to the
SwitchedPortWavelengthRestriction is used with ports specified in the port in general or to a specific connectivity matrix (section 3.2.1.
SwitchedConnectivityMatrix while the FixedPortWavelengthRestriction
is used with ports specified in the FixedConnectivityMatrix.
Reference [Switch] gives an example where both switch and fixed Reference [Switch] gives an example where both switch and fixed
connectivity matrices are used and both types of constraints occur on connectivity matrices are used and both types of constraints occur on
the same port. the same port. Such restrictions could be applied generally to other
label types in GMPLS by adding new kinds of restrictions.
<SwitchedPortWavelengthRestriction> ::= <port wavelength restriction> <PortWavelengthRestriction> ::= [<GeneralPortRestrictions>...]
[<MatrixSpecificRestrictions>...]
<FixedPortWavelengthRestriction> ::= <port wavelength restriction> <GeneralPortRestrictions> ::= <RestrictionType>
[<RestrictionParameters>]
<port wavelength restriction> ::= <RestrictionKind> <MatrixSpecificRestriction> ::= <MatrixID> <RestrictionType>
<RestrictionParameters> <WavelengthSet> [<RestrictionParameters>]
<RestrictionParameters> ::= <MaxNumChannels> [<OthersTBD>]... <RestrictionParameters> ::= [<WavelengthSet>...] [<MaxNumChannels>]
[<MaxWaveBandWidth>]
Where WavelengthSet is a conceptual set of wavelengths, Where
MaxNumChannels is the number of channels permitted on the port, and
RestrictionKind can take the following values and meanings:
SIMPLE: Simple wavelength selective restriction. Max number of MatrixID is the ID of the corresponding connectivity matrix (section
channels indicates the number of wavelengths permitted on the port 3.2.1.
and the accompanying wavelength set indicates the permitted values.
The RestrictionType parameter is used to specify general port
restrictions and matrix specific restrictions. It can take the
following values and meanings:
SIMPLE_WAVELENGTH: Simple wavelength set restriction; The
wavelength set parameter is required.
CHANNEL_COUNT: The number of channels is restricted to be less than
or equal to the Max number of channels parameter (which is required).
WAVEBAND1: Waveband device with a tunable center frequency and WAVEBAND1: Waveband device with a tunable center frequency and
passband. In this case the maximum number of channels indicates the passband. This constraint is characterized by the MaxWaveBandWidth
maximum width of the waveband in terms of the channels spacing given parameters which indicates the maximum width of the waveband in terms
in the wavelength set. The corresponding wavelength set is used to of channels. Note that an additional wavelength set can be used to
indicate the overall tuning range. Specific center frequency tuning indicate the overall tuning range. Specific center frequency tuning
information can be obtained from dynamic channel in use information. information can be obtained from dynamic channel in use information.
It is assumed that both center frequency and bandwidth (Q) tuning can It is assumed that both center frequency and bandwidth (Q) tuning can
be done without causing faults in existing signals. be done without causing faults in existing signals.
For example, if the port is a "colored" drop port of a ROADM then the Restriction specific parameters are used with one or more of the
value of RestrictionKind = SIMPLE for a simple wavelength selective previously listed restriction types. The currently defined parameters
restriction, the MaxNumberOfChannels = 1, and the wavelength are:
restriction is just a wavelength set consisting of a single member
corresponding to the frequency of the permitted wavelength. See WavelengthSet is a conceptual set of wavelengths (labels).
[Switch] for a complete waveband example.
MaxNumChannels is the maximum number of channels that can be
simultaneously used (relative to either a port or a matrix).
MaxWaveBandWidth is the maximum width of a tunable waveband switching
device.
For example, if the port is a "colored" drop port of a ROADM then we
have two restrictions: (a) CHANNEL_COUNT, with MaxNumChannels = 1,
and (b) SIMPLE_WAVELENGTH, with the wavelength set consisting of a
single member corresponding to the frequency of the permitted
wavelength. See [Switch] for a complete waveband example.
This information model for port wavelength (label) restrictions is
fairly general in that it can be applied to ports that have label
restrictions only or to ports that are part of an asymmetric switch
and have label restrictions. In addition, the types of label
restrictions that can be supported is extensible.
3.4. Dynamic Link Information 3.4. Dynamic Link Information
By dynamic information we mean information that is subject to change By dynamic information we mean information that is subject to change
on a link with subsequent connection establishment or teardown. on a link with subsequent connection establishment or teardown.
Currently for WSON the only information we currently envision is Currently for WSON the only information we currently envision is
wavelength availability and wavelength in use for shared backup wavelength availability and wavelength in use for shared backup
purposes. purposes.
<DynamicLinkInfo> ::= <LinkID> <AvailableWavelengths> <DynamicLinkInfo> ::= <LinkID> <AvailableWavelengths>
[<SharedBackupWavelengths>] [<SharedBackupWavelengths>]
Where Where
<LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID> <LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID>
<RemoteNodeID> <RemoteNodeID>
AvailableWavelengths is a set of wavelengths currently available on AvailableWavelengths is a set of wavelengths (labels) currently
the link. Given this information and the port wavelength restrictions available on the link. Given this information and the port wavelength
we can also determine which wavelengths are currently in use. restrictions we can also determine which wavelengths are currently in
use. This parameter could potential be used with other technologies
that GMPLS currently covers or may cover in the future.
SharedBackupWavelengths is a set of wavelengths currently used for SharedBackupWavelengths is a set of wavelengths (labels)currently
shared backup protection on the link. An example usage of this used for shared backup protection on the link. An example usage of
information in a WSON setting is given in [Shared]. this information in a WSON setting is given in [Shared]. This
parameter could potential be used with other technologies that GMPLS
currently covers or may cover in the future.
3.5. Dynamic Node Information 3.5. Dynamic Node Information
Dynamic node information is used to hold information for a node that Dynamic node information is used to hold information for a node that
can change frequently. Currently only wavelength converter pool can change frequently. Currently only wavelength converter pool
information is included as a possible (but not required) information information is included as a possible (but not required) information
sub-element. sub-element.
<DynamicNodeInfo> ::= <NodeID> [<WavelengthConverterPoolStatus>] <DynamicNodeInfo> ::= <NodeID> [<WavelengthConverterPoolStatus>]
skipping to change at page 14, line 9 skipping to change at page 16, line 9
action. action.
6. Acknowledgments 6. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
7. References 7. References
7.1. Normative References 7.1. Normative References
[Encode] Reference the encoding draft here. [Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Encoding for Wavelength
Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-wson-encode.
[RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used in [RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used in
Various Protocol Specifications", work in progress: draft- Various Protocol Specifications", RFC 5511, April 2009.
farrel-rtg-common-bnf-08.txt.
[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, September (TE) Extensions to OSPF Version 2", RFC 3630, September
2003. 2003.
[RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions [RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, October 2005 (GMPLS)", RFC 4202, October 2005
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in
skipping to change at page 14, line 36 skipping to change at page 16, line 38
[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, October 2008. Engineering", RFC 5305, October 2008.
[RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions [RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, October 2008. (GMPLS)", RFC 5307, October 2008.
[WSON-Frame] G. Bernstein, Y. Lee, W. Imajuku, "Framework for GMPLS [WSON-Frame] G. Bernstein, Y. Lee, W. Imajuku, "Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks", and PCE Control of Wavelength Switched Optical Networks",
work in progress: draft-ietf-ccamp-wavelength-switched- work in progress: draft-ietf-ccamp-rwa-wson-framework.
framework-01.txt, October 2008.
7.2. Informative References 7.2. Informative References
[Shared] G. Bernstein, Y. Lee, "Shared Backup Mesh Protection in PCE- [Shared] G. Bernstein, Y. Lee, "Shared Backup Mesh Protection in PCE-
based WSON Networks", iPOP 2008, http://www.grotto- based WSON Networks", iPOP 2008, http://www.grotto-
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 Automated Path WDM Wavelength Switching Systems for Use in GMPLS and Automated
Computation", http://www.grotto- Path Computation", Journal of Optical Communications and
networking.com/wson/ModelingWSONswitchesV2a.pdf , June, 2008 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 [WC-Pool] G. Bernstein, Y. Lee, "Modeling WDM Switching Systems
including Wavelength Converters" to appear www.grotto- including Wavelength Converters" to appear www.grotto-
networking.com, 2008. networking.com, 2008.
8. Contributors 8. Contributors
Diego Caviglia Diego Caviglia
 End of changes. 39 change blocks. 
125 lines changed or deleted 170 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/