draft-ietf-ccamp-rwa-info-00.txt   draft-ietf-ccamp-rwa-info-01.txt 
Network Working Group G. Bernstein Network Working Group G. Bernstein
Internet Draft Grotto Networking Internet Draft Grotto Networking
Intended status: Informational Y. Lee Intended status: Informational Y. Lee
Expires: February 2009 D. Li Expires: May 2009 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
August 29, 2008 November 3, 2008
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-00.txt draft-ietf-ccamp-rwa-info-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 January 29, 2007. This Internet-Draft will expire on May 3, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document provides an information model of information needed by This document provides a model of information needed by the routing
the routing and wavelength assignment (RWA) process in wavelength and wavelength assignment (RWA) process in wavelength switched
switched optical networks (WSONs). The purpose of information optical networks (WSONs). The purpose of the information described
described in this model is to facilitate constrained lightpath in this model is to facilitate constrained lightpath computation in
computation in WSONs. In particular in cases where there are no or a WSONs, particularly in cases where there are no or a limited number
limited number of wavelength converters available in the WSON. This of wavelength converters available. This model currently does not
model currently does not include optical impairments. include optical impairments.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Terminology....................................................3 2. Terminology....................................................3
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.................4
3.2. Node Information..........................................4 3.2. Node Information..........................................4
3.2.1. Switched Connectivity Matrix.........................5 3.2.1. Switched Connectivity Matrix.........................5
3.2.2. Fixed Connectivity Matrix............................5 3.2.2. Fixed Connectivity Matrix............................5
3.2.3. Shared Risk Node Group...............................6 3.2.3. Shared Risk Node Group...............................6
3.2.4. Wavelength Converter Pool............................6 3.2.4. Wavelength Converter Pool............................6
3.2.4.1. OEO Wavelength Converter Info...................6 3.2.4.1. OEO Wavelength Converter Info...................9
3.3. Link Information..........................................7 3.3. Link Information..........................................9
3.3.1. Link ID..............................................7 3.3.1. Link ID.............................................10
3.3.2. Administrative Group.................................8 3.3.2. Administrative Group................................10
3.3.3. Interface Switching Capability Descriptor............8 3.3.3. Interface Switching Capability Descriptor...........10
3.3.4. Link Protection Type (for this link).................8 3.3.4. Link Protection Type (for this link)................10
3.3.5. Shared Risk Link Group Information...................8 3.3.5. Shared Risk Link Group Information..................10
3.3.6. Traffic Engineering Metric...........................8 3.3.6. Traffic Engineering Metric..........................11
3.3.7. Maximum Bandwidth Per Channel........................8 3.3.7. Maximum Bandwidth Per Channel.......................11
3.3.8. Switched and Fixed Port Wavelength Restrictions......9 3.3.8. Switched and Fixed Port Wavelength Restrictions.....11
3.4. Dynamic Link Information.................................10 3.4. Dynamic Link Information.................................12
3.5. Dynamic Node Information.................................10 3.5. Dynamic Node Information.................................12
4. Security Considerations.......................................10 4. Security Considerations.......................................13
5. IANA Considerations...........................................11 5. IANA Considerations...........................................13
6. Acknowledgments...............................................11 6. Acknowledgments...............................................13
7. References....................................................12 7. References....................................................14
7.1. Normative References.....................................12 7.1. Normative References.....................................14
7.2. Informative References...................................12 7.2. Informative References...................................14
8. Contributors..................................................13 8. Contributors..................................................15
Author's Addresses...............................................13 Author's Addresses...............................................16
Intellectual Property Statement..................................14 Intellectual Property Statement..................................16
Disclaimer of Validity...........................................15 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 this is not facilitate constrained lightpath computation and as such is not a
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
is known as the routing and wavelength assignment (RWA) problem. is known as the routing and wavelength assignment (RWA) problem.
Hence the information model must provide sufficient topology and Hence the information model must provide sufficient topology and
wavelength restriction and availability information to support this wavelength restriction and availability information to support this
computation. More details on the RWA process and WSON subsystems and computation. More details on the RWA process and WSON subsystems and
their properties can be found in [WSON-Frame]. The model defined here their properties can be found in [WSON-Frame]. The model defined here
does not currently include impairments however optical impairments does not currently include impairments however optical impairments
skipping to change at page 4, line 22 skipping to change at page 4, line 22
o Link Information o Link Information
o Dynamic Node Information o Dynamic Node Information
o Dynamic Link Information o Dynamic Link Information
Note that this is roughly the categorization used in [G.7715] section Note that this is roughly the categorization used in [G.7715] section
7. 7.
In the following we use a BNF/Regular expression like syntax where In the following we use where applicable the reduced Backus-Naur form
the symbol "|" indicates a choice between two or more elements; the (RBNF) syntax of [RBNF] to aid in defining the RWA information model.
symbol "*" indicates zero or more occurrences of an element; the
symbol "?" indicates zero or one occurrences; and the symbol "+"
indicates one or more occurrences.
3.1. Dynamic and Relatively Static Information 3.1. Dynamic and Relatively Static Information
All the RWA information of concern in a WSON network is subject to All the RWA information of concern in a WSON network is subject to
change over time. Equipment can be upgraded; links may be placed in change over time. Equipment can be upgraded; links may be placed in
or out of service and the like. However, from the point of view of or out of service and the like. However, from the point of view of
RWA computations there is a difference between information that can RWA computations there is a difference between information that can
change with each successive connection establishment in the network change with each successive connection establishment in the network
and that information that is relatively static on the time scales of and that information that is relatively static on the time scales of
connection establishment. A key example of the former is link connection establishment. A key example of the former is link
wavelength usage since this can change with connection setup/teardown wavelength usage since this can change with connection setup/teardown
and this information is a key input to the RWA process. Examples of and this information is a key input to the RWA process. Examples of
relatively static information are the internal connectivity of a WDM relatively static information are the potential port connectivity of
ROADM, and the channel spacing on a WDM link. a WDM ROADM, and the channel spacing on a WDM link.
In this document we will separate, where possible, dynamic and static In this document we will separate, where possible, dynamic and static
information so that these can be kept separate in possible encodings information so that these can be kept separate in possible encodings
and hence allowing for separate updates of these two types of and hence allowing for separate updates of these two types of
information thereby reducing processing and traffic load caused by information thereby reducing processing and traffic load caused by
the timely distribution of the more dynamic RWA WSON information. the timely distribution of the more dynamic RWA WSON information.
3.2. Node Information 3.2. Node Information
The node information described here contains the relatively static The node information described here contains the relatively static
skipping to change at page 5, line 16 skipping to change at page 5, line 13
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> [<SwitchedConnectivityMatrix>]
FixedConnectivityMatrix?, SRNG?, WavelengthConverterPool? [<FixedConnectivityMatrix>], [<SRNG>] [<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.
3.2.1. Switched Connectivity Matrix 3.2.1. Switched Connectivity Matrix
The switched connectivity matrix (SwitchConnectivityMatrix) The switched connectivity matrix (SwitchConnectivityMatrix)
represents the potential connectivity matrix for asymmetric switches represents the potential connectivity matrix for asymmetric switches
(e.g. ROADMs and such). This is a conceptual M by N matrix (e.g. ROADMs and such). Note that this matrix does not represent any
representing the switched connectivity, where M represents the number particular internal blocking behavior but indicates which ingress
of ingress ports and N the number of egress ports. We say this is a ports and wavelengths could possibly be connected to a particular
output port. Representing internal state dependent blocking for a
switch or ROADM is beyond the scope of this document and due to its
highly implementation dependent nature would not be subject to
standardization. This is a conceptual M by N matrix representing the
potential switched connectivity, 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 "conceptual" since this matrix tends to exhibit structure that allows
for very compact representations that are useful for both 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 SwitchedConnectivityMatrix(i, j) = 0 or 1 depending on whether
ingress port i can connect to egress port j for one or more ingress port i can connect to egress port j for one or more
wavelengths. wavelengths.
3.2.2. Fixed Connectivity Matrix 3.2.2. Fixed Connectivity Matrix
The fixed connectivity matrix (FixedConnectivityMatrix) represents The fixed connectivity matrix (FixedConnectivityMatrix) represents
the connectivity for asymmetric fixed devices or the fixed part of a 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 "hybrid" device [Switch]. This is a conceptual M by N matrix, where M
skipping to change at page 6, line 25 skipping to change at page 6, line 25
3.2.4. Wavelength Converter Pool 3.2.4. 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 of the wavelength converter pool from a 2. The accessibility and availability of a wavelength converter to
particular port and wavelength. convert from a given ingress wavelength on a particular ingress
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.
A general representation of the converter pool with respect to To model point 2 above we can use a similar technique as used to
resource availability from a particular port and wavelength is TBD model ROADMs and optical switches this technique was generally
and will be furnished in a subsequent revision of this draft. discussed in [WSON-Frame] and consisted of a matrix to indicate
Particular types of individual wavelength converters, such as those possible connectivity along with wavelength constraints for
based on an OEO approach can be characterized fairly completely as links/ports. Since wavelength converters are considered a scarce
specified below. resource we will also want to our model to include as a minimum the
usage state of individual wavelength converters in the pool. Models
that incorporate more state to further reveal blocking conditions on
ingress or egress to particular converters are for further study.
We utilize a three stage model as shown schematically in Figure 1. In
this model we assume N ingress ports (fibers), P wavelength
converters, and M egress ports (fibers). Since not all ingress ports
can necessarily reach the converter pool, the model starts with a
wavelength pool ingress matrix WI(i,p) = {0,1} whether ingress port i
can reach potentially reach wavelength converter p.
Since not all wavelength can necessarily reach all the converters or
the converters may have limited input wavelength range we have a set
of ingress port constraints for each wavelength converter. Currently
we assume that a wavelength converter can only take a single
wavelength on input. We can model each wavelength converter ingress
port constraint via a wavelength set mechanism.
Next we have a state vector WC(j) = {0,1} dependent upon whether
wavelength converter j in the pool is in use. This is the only state
kept in the converter pool model. This state is not necessary for
modeling "fixed" transponder system, i.e., systems where there is no
sharing. In addition, this state information may be encoded in a
much more compact form depending on the overall connectivity
structure [WC-Pool].
After that, we have a set of wavelength converter egress wavelength
constraints. These constraints indicate what wavelengths a particular
wavelength converter can generate or are restricted to generating due
to internal switch structure.
Finally, we have a wavelength pool egress matrix WE(p,k) = {0,1}
depending on whether the output from wavelength converter p can reach
egress port k. Examples of this method being used to model wavelength
converter pools for several switch architectures from the literature
are given in reference [WC-Pool].
I1 +-------------+ +-------------+ E1
----->| | +--------+ | |----->
I2 | +------+ WC #1 +-------+ | E2
----->| | +--------+ | |----->
| Wavelength | | Wavelength |
| Converter | +--------+ | Converter |
| Pool +------+ WC #2 +-------+ Pool |
| | +--------+ | |
| Ingress | | Egress |
| Connection | . | Connection |
| Matrix | . | Matrix |
| | . | |
| | | |
IN | | +--------+ | | EM
----->| +------+ WC #P +-------+ |----->
| | +--------+ | |
+-------------+ ^ ^ +-------------+
| |
| |
| |
| |
Ingress wavelength Egress wavelength
constraints for constraints for
each converter each converter
Figure 1 Schematic diagram of wavelength converter pool model.
Formally we can specify the model as:
<WavelengthConverterPool> ::= <IngressPoolMatrix>
<IngressPoolConstraints> [<WCPoolState>] <EgressPoolConstraints>
<PoolEgressMatrix>
Note that except for <WCPoolState> all the other components of
<WavelengthConverterPool> are relatively static. In addition
<WCPoolState> is a relatively small structure compared potentially to
the others and hence in a future revision of this document maybe
moved to a new section on dynamic node information.
3.2.4.1. OEO Wavelength Converter Info 3.2.4.1. 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, <OEOWavelengthConverterInfo> ::= <RegeneratorType> [<BitRateRange>]
IngressWavelengthRange, EgressWavelengthRange, BitRateRange?, [<AcceptableSignals>]
AcceptableSignals?
Where the RegeneratorType is used to model an OEO regenerator. Where the RegeneratorType is used to model an OEO regenerator.
Regenerators are usually classified into three types. Level 1 Regenerators are usually classified into three types [G.sup39]. Level
provides signal amplification, level 2 amplification and pulse 1 provides signal amplification, level 2 amplification and pulse
shaping, and level 3 amplification, pulse shaping and timing shaping, and level 3 amplification, pulse shaping and timing
regeneration. Level 2 regenerators can have a restricted bit rate regeneration. Level 2 regenerators can have a restricted bit rate
range, while level 3 regenerators can also be specialized to a range, while level 3 regenerators can also be specialized to a
particular signal type. particular signal type.
IngressWavelengthRange and EgressWavelengthRange are sets of
wavelengths that characterize the input wavelengths acceptable to the
wavelength converter and the outputs that can be generated by the
wavelength converter.
BitRateRange: indicates the range of bit rates that can be BitRateRange: indicates the range of bit rates that can be
accommodated by the wavelength converter. accommodated by the wavelength converter.
AcceptableSignals: is a list of signals that the wavelength converter AcceptableSignals: is a list of signals that the wavelength converter
can handle. This could be fairly general for Level 1 and Level 2 can handle. This could be fairly general for Level 1 and Level 2
regenerators, e.g., characterized by general signal properties such regenerators, e.g., characterized by general signal properties such
as modulation type and related parameters, or fairly specific signal as modulation type and related parameters, or fairly specific signal
types for Level 3 based regenerators. types for Level 3 based regenerators.
3.3. Link Information 3.3. Link Information
MPLS-TE routing protocol extensions for OSPF and IS-IS [RFC3630], MPLS-TE routing protocol extensions for OSPF and IS-IS [RFC3630],
[RFC3784] along with GMPLS routing protocol extensions for OSPF and [RFC5305] along with GMPLS routing protocol extensions for OSPF and
IS-IS [RFC4203, RFC4205] provide the bulk of the relatively static IS-IS [RFC4203, RFC5307] provide the bulk of the relatively static
link information needed by the RWA process. WSON networks bring in link information needed by the RWA process. WSON networks bring in
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?, [<MaximumBandwidthPerChannel>] <[SwitchedPortWavelengthRestriction>]
FixedPortWavelengthRestriction? [<FixedPortWavelengthRestriction>]
3.3.1. Link ID 3.3.1. Link ID
LinkID: LocalLinkID, LocalNodeID, RemoteLinkID, RemoteNodeID <LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID>
<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, RFC4205]. 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
in the case of numbered links. in the case of numbered links.
3.3.2. Administrative Group 3.3.2. Administrative Group
AdministrativeGroup: Defined in [RFC3630]. Each set bit corresponds AdministrativeGroup: Defined in [RFC3630]. Each set bit corresponds
to one administrative group assigned to the interface. A link may to one administrative group assigned to the interface. A link may
belong to multiple groups. This is a configured quantity and can be belong to multiple groups. This is a configured quantity and can be
used to influence routing decisions. used to influence routing decisions.
3.3.3. Interface Switching Capability Descriptor 3.3.3. Interface Switching Capability Descriptor
InterfaceSwCapDesc: Defined in [RFC4202], lets us know the different InterfaceSwCapDesc: Defined in [RFC4202], lets us know the different
switching capabilities on this GMPLS interface. In both [RFC4203] and switching capabilities on this GMPLS interface. In both [RFC4203] and
[RFC4205] this information gets combined with the maximum LSP [RFC5307] this information gets combined with the maximum LSP
bandwidth that can be used on this link at eight different priority bandwidth that can be used on this link at eight different priority
levels. levels.
3.3.4. Link Protection Type (for this link) 3.3.4. Link Protection Type (for this link)
Protection: Defined in [RFC4202] and implemented in [RFC4203, Protection: Defined in [RFC4202] and implemented in [RFC4203,
RFC4205]. Used to indicate what protection, if any, is guarding this RFC5307]. Used to indicate what protection, if any, is guarding this
link. link.
3.3.5. Shared Risk Link Group Information 3.3.5. Shared Risk Link Group Information
SRLG: Defined in [RFC4202] and implemented in [RFC4203, RFC4205]. SRLG: Defined in [RFC4202] and implemented in [RFC4203, RFC5307].
This allows for the grouping of links into shared risk groups, i.e., This allows for the grouping of links into shared risk groups, i.e.,
those links that are likely, for some reason, to fail at the same those links that are likely, for some reason, to fail at the same
time. time.
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. Maximum Bandwidth Per Channel
TBD: Need to check if we still want this. TBD: Need to check if we still want this.
3.3.8. Switched and Fixed Port Wavelength Restrictions 3.3.8. Switched and Fixed Port Wavelength Restrictions
Switch and fixed port wavelength Switch and fixed port wavelength restrictions
restrictions(SwitchedPortWavelengthRestriction, (SwitchedPortWavelengthRestriction, FixedPortWavelengthRestriction)
FixedPortWavelengthRestriction) model the wavelength restrictions model the wavelength restrictions that various optical devices such
that various optical devices such as OXCs, ROADMs, and waveband as OXCs, ROADMs, and waveband mulitplexers may impose on a port. This
mulitplexers may impose on a port. This plays an important role in plays an important role in fully characterizing a WSON switching
fully characterizing a WSON switching device[Switch]. The device [Switch]. The SwitchedPortWavelengthRestriction is used with
SwitchedPortWavelengthRestriction is used with ports specified in the ports specified in the SwitchedConnectivityMatrix while the
SwitchedConnectivityMatrix while the FixedPortWavelengthRestriction FixedPortWavelengthRestriction is used with ports specified in the
is used with ports specified in the FixedConnectivityMatrix. FixedConnectivityMatrix. Reference [Switch] gives an example where
Reference [Switch] gives an example where both switch and fixed both switch and fixed connectivity matrices are used and both types
connectivity matrices are used and both types of constraints are of constraints occur on the same port.
occur on the same port.
SwitchedPortWavelengthRestriction := PortWavelengthRestriction <SwitchedPortWavelengthRestriction> ::= <port wavelength restriction>
FixedPortWavelengthRestriction := PortWavelengthRestriction <FixedPortWavelengthRestriction> ::= <port wavelength restriction>
PortWavelengthRestriction := RestrictionKind, RestrictionParameters, <port wavelength restriction> ::= <RestrictionKind>
WavelengthSet <RestrictionParameters> <WavelengthSet>
RestrictionParameters := MaxNumChannels, OthersTBD? <RestrictionParameters> ::= <MaxNumChannels> [<OthersTBD>]...
Where WavelengthSet is a conceptual set of wavelengths, Where WavelengthSet is a conceptual set of wavelengths,
MaxNumChannels is the number of channels permitted on the port, and MaxNumChannels is the number of channels permitted on the port, and
RestrictionKind can take the following values and meanings: RestrictionKind can take the following values and meanings:
SIMPLE: Simple wavelength selective restriction. Max number of SIMPLE: Simple wavelength selective restriction. Max number of
channels indicates the number of wavelengths permitted on the port channels indicates the number of wavelengths permitted on the port
and the accompanying wavelength set indicates the permitted values. and the accompanying wavelength set indicates the permitted values.
WAVEBAND1: Waveband device with a tunable center frequency and WAVEBAND1: Waveband device with a tunable center frequency and
skipping to change at page 10, line 13 skipping to change at page 12, line 29
[Switch] for a complete waveband example. [Switch] for a complete waveband example.
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, RemoteNodeID <LinkID> ::= <LocalLinkID> <LocalNodeID> <RemoteLinkID>
<RemoteNodeID>
AvailableWavelengths is a set of wavelengths available on the link. AvailableWavelengths is a set of wavelengths available on the link.
SharedBackupWavelengths is a set of wavelengths currently used for SharedBackupWavelengths is a set of wavelengths currently used for
shared backup protection on the link. An example usage of this shared backup protection on the link. An example usage of this
information in a WSON setting is given in [Shared]. information in a WSON setting is given in [Shared].
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>]
Where NodeID is a node identifier and the exact form of the Where NodeID is a node identifier and the exact form of the
wavelength converter pool status information is TBD. wavelength converter pool status information is TBD.
4. Security Considerations 4. Security Considerations
This document discussed an information model for RWA computation in This document discussed an information model for RWA computation in
WSONs. Such a model is very similar from a security standpoint of the WSONs. Such a model is very similar from a security standpoint of the
information that can be currently conveyed via GMPLS routing information that can be currently conveyed via GMPLS routing
protocols. Such information includes network topology, link state protocols. Such information includes network topology, link state
and current utilization, and well as the capabilities of switches and and current utilization, and well as the capabilities of switches and
skipping to change at page 12, line 11 skipping to change at page 14, line 11
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] Reference the encoding draft here.
[RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used in
Various Protocol Specifications", work in progress: draft-
farrel-rtg-common-bnf-07.txt, October 2008.
[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.
[RFC3784] Smit, H. and T. Li, "Intermediate System to Intermediate
System (IS-IS) Extensions for Traffic Engineering (TE)",
RFC 3784, June 2004.
[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
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005. (GMPLS)", RFC 4203, October 2005.
[RFC4205] Kompella, K., Ed., and Y. Rekhter, Ed., "Intermediate [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
System to Intermediate System (IS-IS) Extensions in Support Engineering", RFC 5305, October 2008.
of Generalized Multi-Protocol Label Switching (GMPLS)", RFC
4205, October 2005. [RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
in Support of Generalized Multi-Protocol Label Switching
(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-wavelength-switched-
framework-00.txt, May 2008. 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 Automated Path
Computation", http://www.grotto- Computation", http://www.grotto-
networking.com/wson/ModelingWSONswitchesV2a.pdf , June, 2008 networking.com/wson/ModelingWSONswitchesV2a.pdf , June, 2008
[G.Sup39] ITU-T Series G Supplement 39, Optical system design and
engineering considerations, February 2006.
[WC-Pool] G. Bernstein, Y. Lee, "Modeling WDM Switching Systems
including Wavelength Converters" to appear www.grotto-
networking.com, 2008.
8. Contributors 8. 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)
skipping to change at page 13, line 43 skipping to change at page 16, line 7
Phone: +81 44 396 3287 Phone: +81 44 396 3287
Email: i-nishioka@cb.jp.nec.com Email: i-nishioka@cb.jp.nec.com
Lyndon Ong Lyndon Ong
Ciena Ciena
Email: lyong@ciena.com Email: lyong@ciena.com
Author's Addresses Author's Addresses
Greg Bernstein (ed.) Greg M. Bernstein (ed.)
Grotto Networking Grotto Networking
Fremont, CA, USA Fremont California, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Young Lee (ed.) Young Lee (ed.)
Huawei Technologies Huawei Technologies
1700 Alma Drive, Suite 100 1700 Alma Drive, Suite 100
Plano, TX 75075 Plano, TX 75075
USA USA
Phone: (972) 509-5599 (x2240) Phone: (972) 509-5599 (x2240)
Email: ylee@huawei.com Email: ylee@huawei.com
Dan Li Dan Li
 End of changes. 40 change blocks. 
110 lines changed or deleted 192 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/