draft-ietf-ccamp-rwa-info-01.txt   draft-ietf-ccamp-rwa-info-02.txt 
Network Working Group G. Bernstein Network Working Group Y. Lee
Internet Draft Grotto Networking Internet Draft Huawei
Intended status: Informational Y. Lee Intended status: Informational G. Bernstein
Expires: May 2009 D. Li Expires: September 2009 Grotto Networking
D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
November 3, 2008 March 3, 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-01.txt draft-ietf-ccamp-rwa-info-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that This Internet-Draft is submitted to IETF in full conformance with the
any applicable patent or other IPR claims of which he or she is provisions of BCP 78 and BCP 79.
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
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
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 May 3, 2007. This Internet-Draft will expire on September 3, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
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 currently does not of wavelength converters available. This model does not include
include optical impairments. optical impairments.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Revision History..........................................3
1.1.1. Changes from 01......................................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..........................................5
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............................6
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...................9 3.2.4.1. OEO Wavelength Converter Info...................9
3.3. Link Information..........................................9 3.3. Link Information..........................................9
3.3.1. Link ID.............................................10 3.3.1. Link ID.............................................10
3.3.2. Administrative Group................................10 3.3.2. Administrative Group................................10
3.3.3. Interface Switching Capability Descriptor...........10 3.3.3. Interface Switching Capability Descriptor...........10
3.3.4. Link Protection Type (for this link)................10 3.3.4. Link Protection Type (for this link)................10
3.3.5. Shared Risk Link Group Information..................10 3.3.5. Shared Risk Link Group Information..................10
3.3.6. Traffic Engineering Metric..........................11 3.3.6. Traffic Engineering Metric..........................11
skipping to change at page 3, line 22 skipping to change at page 3, line 27
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
can be accommodated by the general framework presented here. can be accommodated by the general framework presented here.
1.1. Revision History
1.1.1. Changes from 01
Added text on multiple fixed and switched connectivity matrices.
Added text on the relationship between SRNG and SRLG and encoding
considerations.
Added clarifying text on the meaning and use of port/wavelength
restrictions.
Added clarifying text on wavelength availability information and how
to derive wavelengths currently in use.
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 19 skipping to change at page 5, line 37
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.
It is TBD whether multiple switched and fixed connectivity matrices
should optionally be allowed to fully support the most general cases
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. 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). Note that this matrix does not represent any (e.g. ROADMs and such). Note that this matrix does not represent any
particular internal blocking behavior but indicates which ingress particular internal blocking behavior but indicates which ingress
ports and wavelengths could possibly be connected to a particular ports and wavelengths could possibly be connected to a particular
output port. Representing internal state dependent blocking for a output port. Representing internal state dependent blocking for a
switch or ROADM is beyond the scope of this document and due to its switch or ROADM is beyond the scope of this document and due to its
highly implementation dependent nature would not be subject to highly implementation dependent nature would not be subject to
skipping to change at page 6, line 15 skipping to change at page 6, line 38
3.2.3. Shared Risk Node Group 3.2.3. 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
associated with that node a sufficiently general shared risk link
group (SRLG) encoding, such as that used in GMPLS routing extensions
can explicitly incorporate SRNG information.
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.
skipping to change at page 8, line 35 skipping to change at page 8, line 37
| | | |
Ingress wavelength Egress wavelength Ingress wavelength Egress wavelength
constraints for constraints for constraints for constraints for
each converter each converter each converter each converter
Figure 1 Schematic diagram of wavelength converter pool model. Figure 1 Schematic diagram of wavelength converter pool model.
Formally we can specify the model as: Formally we can specify the model as:
<WavelengthConverterPool> ::= <IngressPoolMatrix> <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.1. OEO Wavelength Converter Info
skipping to change at page 11, line 26 skipping to change at page 11, line 26
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 restrictions Switch and fixed port wavelength restrictions
(SwitchedPortWavelengthRestriction, FixedPortWavelengthRestriction) (SwitchedPortWavelengthRestriction, FixedPortWavelengthRestriction)
model the wavelength restrictions that various optical devices such model the wavelength restrictions that various optical devices such
as OXCs, ROADMs, and waveband mulitplexers may impose on a port. This as OXCs, ROADMs, and waveband multiplexers may impose on a port.
plays an important role in fully characterizing a WSON switching These restrictions tell us what wavelength may or may not be used on
device [Switch]. The SwitchedPortWavelengthRestriction is used with a link and are relatively static. This plays an important role in
ports specified in the SwitchedConnectivityMatrix while the fully characterizing a WSON switching device [Switch]. The
FixedPortWavelengthRestriction is used with ports specified in the SwitchedPortWavelengthRestriction is used with ports specified in the
FixedConnectivityMatrix. Reference [Switch] gives an example where SwitchedConnectivityMatrix while the FixedPortWavelengthRestriction
both switch and fixed connectivity matrices are used and both types is used with ports specified in the FixedConnectivityMatrix.
of constraints occur on the same port. Reference [Switch] gives an example where both switch and fixed
connectivity matrices are used and both types of constraints occur on
the same port.
<SwitchedPortWavelengthRestriction> ::= <port wavelength restriction> <SwitchedPortWavelengthRestriction> ::= <port wavelength restriction>
<FixedPortWavelengthRestriction> ::= <port wavelength restriction> <FixedPortWavelengthRestriction> ::= <port wavelength restriction>
<port wavelength restriction> ::= <RestrictionKind> <port wavelength restriction> ::= <RestrictionKind>
<RestrictionParameters> <WavelengthSet> <RestrictionParameters> <WavelengthSet>
<RestrictionParameters> ::= <MaxNumChannels> [<OthersTBD>]... <RestrictionParameters> ::= <MaxNumChannels> [<OthersTBD>]...
skipping to change at page 12, line 37 skipping to change at page 12, line 41
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 available on the link. AvailableWavelengths is a set of wavelengths currently available on
the link. Given this information and the port wavelength restrictions
we can also determine which wavelengths are currently in use.
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
skipping to change at page 14, line 13 skipping to change at page 14, line 13
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 [RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used in
Various Protocol Specifications", work in progress: draft- Various Protocol Specifications", work in progress: draft-
farrel-rtg-common-bnf-07.txt, October 2008. 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 16, line 42 skipping to change at page 16, line 42
Wataru Imajuku Wataru Imajuku
NTT Network Innovation Labs NTT Network Innovation Labs
1-1 Hikari-no-oka, Yokosuka, Kanagawa 1-1 Hikari-no-oka, Yokosuka, Kanagawa
Japan Japan
Phone: +81-(46) 859-4315 Phone: +81-(46) 859-4315
Email: imajuku.wataru@lab.ntt.co.jp Email: imajuku.wataru@lab.ntt.co.jp
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF Trust takes no position regarding the validity or scope of
Intellectual Property Rights or other rights that might be claimed to any Intellectual Property Rights or other rights that might be
pertain to the implementation or use of the technology described in claimed to pertain to the implementation or use of the technology
this document or the extent to which any license under such rights described in any IETF Document or the extent to which any license
might or might not be available; nor does it represent that it has under such rights might or might not be available; nor does it
made any independent effort to identify any such rights. Information represent that it has made any independent effort to identify any
on the procedures with respect to rights in RFC documents can be such rights.
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of Intellectual Property disclosures made to the IETF
assurances of licenses to be made available, or the result of an Secretariat and any assurances of licenses to be made available, or
attempt made to obtain a general license or permission for the use of the result of an attempt made to obtain a general license or
such proprietary rights by implementers or users of this permission for the use of such proprietary rights by implementers or
specification can be obtained from the IETF on-line IPR repository at users of this specification can be obtained from the IETF on-line IPR
http://www.ietf.org/ipr. repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at any standard or specification contained in an IETF Document. Please
ietf-ipr@ietf.org. address the information to the IETF at ietf-ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on an All IETF Documents and the information contained therein are provided
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 21 change blocks. 
59 lines changed or deleted 89 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/