draft-ietf-ccamp-rwa-info-19.txt   draft-ietf-ccamp-rwa-info-20.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: May 2014 Grotto Networking Expires: August 2014 Grotto Networking
D. Li D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
November 7, 2013 February 5, 2014
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-19.txt draft-ietf-ccamp-rwa-info-20.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 7, 2013. This Internet-Draft will expire on August 5, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 3, line 7 skipping to change at page 3, line 7
5.3.2. Optical Interface Class List........................12 5.3.2. Optical Interface Class List........................12
5.3.3. Acceptable Client Signal List.......................12 5.3.3. Acceptable Client Signal List.......................12
5.3.4. Processing Capability List..........................12 5.3.4. Processing Capability List..........................12
6. Link Information (General)....................................13 6. Link Information (General)....................................13
6.1. Administrative Group.....................................13 6.1. Administrative Group.....................................13
6.2. Interface Switching Capability Descriptor................14 6.2. Interface Switching Capability Descriptor................14
6.3. Link Protection Type (for this link).....................14 6.3. Link Protection Type (for this link).....................14
6.4. Shared Risk Link Group Information.......................14 6.4. Shared Risk Link Group Information.......................14
6.5. Traffic Engineering Metric...............................14 6.5. Traffic Engineering Metric...............................14
6.6. Port Label Restrictions..................................14 6.6. Port Label Restrictions..................................14
6.6.1. Port-Wavelength Exclusivity Example.................16 6.6.1. Port-Wavelength Exclusivity Example.................17
7. Dynamic Components of the Information Model...................17 7. Dynamic Components of the Information Model...................18
7.1. Dynamic Link Information (General).......................18 7.1. Dynamic Link Information (General).......................19
7.2. Dynamic Node Information (WSON Specific).................18 7.2. Dynamic Node Information (WSON Specific).................19
8. Security Considerations.......................................18 8. Security Considerations.......................................19
9. IANA Considerations...........................................19 9. IANA Considerations...........................................20
10. Acknowledgments..............................................19 10. Acknowledgments..............................................20
11. References...................................................20 11. References...................................................21
11.1. Normative References....................................20 11.1. Normative References....................................21
11.2. Informative References..................................21 11.2. Informative References..................................22
12. Contributors.................................................22 12. Contributors.................................................23
Author's Addresses...............................................23 Author's Addresses...............................................24
Intellectual Property Statement..................................23 Intellectual Property Statement..................................24
Disclaimer of Validity...........................................24 Disclaimer of Validity...........................................25
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. This general purpose network management information model. 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
skipping to change at page 5, line 47 skipping to change at page 5, line 47
conceptual M by N matrix representing the potential switched or conceptual M by N matrix representing the potential switched or
fixed connectivity, where M represents the number of input ports and fixed connectivity, where M represents the number of input ports and
N the number of output ports. This is a "conceptual" matrix since N the number of output ports. This is a "conceptual" matrix since
the matrix tends to exhibit structure that allows for very compact the matrix tends to exhibit structure that allows for very compact
representations that are useful for both transmission and path representations that are useful for both transmission and path
computation. computation.
Note that the connectivity matrix information element can be useful Note that the connectivity matrix information element can be useful
in any technology context where asymmetric switches are utilized. in any technology context where asymmetric switches are utilized.
ConnectivityMatrix ::= <MatrixID> <ConnType> <Matrix> <ConnectivityMatrix> ::= <MatrixID> <ConnType> <Matrix>
Where Where
<MatrixID> is a unique identifier for the matrix. <MatrixID> is a unique identifier for the matrix.
<ConnType> can be either 0 or 1 depending upon whether the <ConnType> can be either 0 or 1 depending upon whether the
connectivity is either fixed or switched. connectivity is either fixed or switched.
<Matrix> represents the fixed or switched connectivity in that <Matrix> represents the fixed or switched connectivity in that
Matrix(i, j) = 0 or 1 depending on whether input port i can connect Matrix(i, j) = 0 or 1 depending on whether input port i can connect
to output port j for one or more wavelengths. to output port j for one or more wavelengths.
skipping to change at page 6, line 45 skipping to change at page 6, line 45
to a desired output wavelength on a particular output port. to a desired output wavelength on a particular output 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.
Since resources tend to be packaged together in blocks of similar Since resources tend to be packaged together in blocks of similar
devices, e.g., on line cards or other types of modules, the devices, e.g., on line cards or other types of modules, the
fundamental unit of identifiable resource in this document is the fundamental unit of identifiable resource in this document is the
"resource block". A resource block may contain one or more "resource block". A resource block may contain one or more
resources. A resource is the smallest identifiable unit of resources. A resource is the smallest identifiable unit of
processing resource. One can group together resources into blocks if processing allocation. One can group together resources into blocks
they have similar characteristics relevant to the optical system if they have similar characteristics relevant to the optical system
being modeled, e.g., processing properties, accessibility, etc. being modeled, e.g., processing properties, accessibility, etc.
This leads to the following formal high level model: This leads to the following formal high level model:
<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...] <Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
[<ResourcePool>] [<ResourcePool>]
Where Where
<ResourcePool> ::= <ResourceBlockInfo>... <ResourcePool> ::= <ResourceBlockInfo>...
skipping to change at page 10, line 43 skipping to change at page 10, line 43
Figure 2 Schematic diagram of resource pool model with shared block Figure 2 Schematic diagram of resource pool model with shared block
accessibility. accessibility.
Formally the model can be specified as: Formally the model can be specified as:
<ResourceAccessibility ::= <PoolInputMatrix> <PoolOutputMatrix> <ResourceAccessibility ::= <PoolInputMatrix> <PoolOutputMatrix>
<ResourceWaveConstraints> ::= <InputWaveConstraints> <ResourceWaveConstraints> ::= <InputWaveConstraints>
<OutputOutputWaveConstraints> <OutputOutputWaveConstraints>
<RBPoolState> <RBPoolState> ::=<ResourceBlockID> <NumResourcesInUse>
::=(<ResourceBlockID><NumResourcesInUse><InAvailableWavelengths><Out [<InAvailableWavelengths>] [<OutAvailableWavelengths>]
AvailableWavelengths>)... [<RBPoolState>]
Note that except for <RBPoolState> all the other components of Note that except for <RBPoolState> all the other components of
<ResourcePool> are relatively static. Also the <ResourcePool> are relatively static. Also the
<InAvailableWavelengths> and <OutAvailableWavelengths> are only used <InAvailableWavelengths> and <OutAvailableWavelengths> are only used
in the cases of shared input or output access to the particular in the cases of shared input or output access to the particular
block. See the resource block information in the next section to see block. See the resource block information in the next section to see
how this is specified. how this is specified.
5.2. Resource Signal Constraints and Processing Capabilities 5.2. Resource Signal Constraints and Processing Capabilities
The wavelength conversion abilities of a resource (e.g. regenerator, The wavelength conversion abilities of a resource (e.g. regenerator,
wavelength converter) were modeled in the <OutputWaveConstraints> wavelength converter) were modeled in the <OutputWaveConstraints>
previously discussed. As discussed in [RFC6163] the constraints on previously discussed. As discussed in [RFC6163] the constraints on
an electro-optical resource can be modeled in terms of input an electro-optical resource can be modeled in terms of input
constraints, processing capabilities, and output constraints: constraints, processing capabilities, and output constraints:
<ResourceBlockInfo> ::= ([<ResourceSet>] <InputConstraints> <ResourceBlockInfo> ::= <ResourceBlockSet> [<InputConstraints>]
[<ProcessingCapabilities>] <OutputConstraints>)* [<ProcessingCapabilities>] [<OutputConstraints>]
Where <ResourceSet> is a list of resource block identifiers with Where <ResourceBlockSet> is a list of resource block identifiers
the same characteristics. If this set is missing the constraints are with the same characteristics. If this set is missing the
applied to the entire network element. constraints are applied to the entire network element.
The <InputConstraints> are signal compatibility based constraints The <InputConstraints> are signal compatibility based constraints
and/or shared access constraint indication. The details of these and/or shared access constraint indication. The details of these
constraints are defined in section 5.3. constraints are defined in section 5.3.
<InputConstraints> ::= <SharedInput> [<OpticalInterfaceClassList>] <InputConstraints> ::= <SharedInput> [<OpticalInterfaceClassList>]
[<ClientSignalList>] [<ClientSignalList>]
The <ProcessingCapabilities> are important operations that the The <ProcessingCapabilities> are important operations that the
resource (or network element) can perform on the signal. The details resource (or network element) can perform on the signal. The details
skipping to change at page 13, line 32 skipping to change at page 13, line 32
bring in additional link related constraints. These stem from WDM bring in additional link related constraints. These stem from WDM
line system characterization, laser transmitter tuning restrictions, line system characterization, laser transmitter tuning restrictions,
and switching subsystem port wavelength constraints, e.g., colored and switching subsystem port wavelength constraints, e.g., colored
ROADM drop ports. ROADM drop ports.
In the following summarize both information from existing GMPLS In the following summarize both information from existing GMPLS
route protocols and new information that maybe needed by the RWA route protocols and new information that maybe needed by the RWA
process. process.
<LinkInfo> ::= <LinkID> [<AdministrativeGroup>] <LinkInfo> ::= <LinkID> [<AdministrativeGroup>]
[<InterfaceCapDesc>] [<Protection>] [<SRLG>]... [<InterfaceCapDesc>] [<Protection>] [<SRLG>...]
[<TrafficEngineeringMetric>] [<PortLabelRestriction>] [<TrafficEngineeringMetric>] [<PortLabelRestriction>...]
Note that these additional link characteristics only applies to line Note that these additional link characteristics only applies to line
side ports of WDM system or add/drop ports pertaining to Resource side ports of WDM system or add/drop ports pertaining to Resource
Pool (e.g., Regenerator or Wavelength Converter Pool). The Pool (e.g., Regenerator or Wavelength Converter Pool). The
advertisement of input/output tributary ports is not intended here. advertisement of input/output tributary ports is not intended here.
6.1. Administrative Group 6.1. 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
skipping to change at page 15, line 9 skipping to change at page 15, line 9
impose on a port. These restrictions tell us what wavelength may or impose on a port. These restrictions tell us what wavelength may or
may not be used on a link and are relatively static. This plays an may not be used on a link and are relatively static. This plays an
important role in fully characterizing a WSON switching device important role in fully characterizing a WSON switching device
[Switch]. Port wavelength restrictions are specified relative to the [Switch]. Port wavelength restrictions are specified relative to the
port in general or to a specific connectivity matrix (section 4.1. port in general or to a specific connectivity matrix (section 4.1.
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 connectivity matrices are used and both types of constraints occur
on the same port. on the same port.
<PortLabelRestriction> ::= <GeneralPortRestrictions>... <PortLabelRestriction> ::= <MatrixID> <RestrictionType>
<MatrixSpecificRestrictions>... <Restriction parameters list>
<GeneralPortRestrictions> ::= <RestrictionType> <Restriction parameters list> ::=
<RestrictionParameters> <Simple label restriction parameters> |
<Channel count restriction parameters> |
<Label range restriction parameters> |
<Simple+channel restriction parameters> |
<Exclusive label restriction parameters>
<MatrixSpecificRestriction> ::= <MatrixID> <RestrictionType> <Simple label restriction parameters> ::= <LabelSet> ...
<RestrictionParameters>
<RestrictionParameters> ::= <LabelSet>... <MaxNumChannels> <Channel count restriction parameters> ::= <MaxNumChannels>
<MaxWaveBandWidth>
<Label range restriction parameters> ::=
<MaxLabelRange> (<LabelSet> ...)
<Simple+channel restriction parameters> ::=
<MaxNumChannels> (<LabelSet> ...)
<Exclusive label restriction parameters> ::= <LabelSet> ...
Where Where
MatrixID is the ID of the corresponding connectivity matrix (section MatrixID is the ID of the corresponding connectivity matrix (section
4.1. 4.1.
The RestrictionType parameter is used to specify general port The RestrictionType parameter is used to specify general port
restrictions and matrix specific restrictions. It can take the restrictions and matrix specific restrictions. It can take the
following values and meanings: following values and meanings:
SIMPLE_WAVELENGTH: Simple wavelength set restriction; The SIMPLE_LABEL: Simple label (wavelength) set restriction; The label
wavelength set parameter is required. set parameter is required.
CHANNEL_COUNT: The number of channels is restricted to be less than CHANNEL_COUNT: The number of channels is restricted to be less than
or equal to the Max number of channels parameter (which is or equal to the Max number of channels parameter (which is
required). required).
PORT_WAVELENGTH_EXCLUSIVITY: A wavelength can be used at most once LABEL_RANGE: Used to indicate a restriction on a range of labels
among a given set of ports. The set of ports is specified as a that can be switched. For example, a waveband device with a tunable
parameter to this constraint. center frequency and passband. This constraint is characterized by
the MaxLabelRange parameter which indicates the maximum range of the
labels, e.g., which may represent a waveband in terms of channels.
Note that an additional parameter can be used to indicate the
overall tuning range. Specific center frequency tuning information
can be obtained from dynamic channel in use information. It is
assumed that both center frequency and bandwidth (Q) tuning can be
done without causing faults in existing signals.
WAVEBAND1: Waveband device with a tunable center frequency and SIMPLE LABEL & CHANNEL COUNT: In this case, the accompanying label
passband. This constraint is characterized by the MaxWaveBandWidth set and MaxNumChannels indicate labels permitted on the port and the
parameters which indicates the maximum width of the waveband in maximum number of labels that can be simultaneously used on the
terms of channels. Note that an additional wavelength set can be port.
used to indicate the overall tuning range. Specific center frequency
tuning information can be obtained from dynamic channel in use LINK LABEL_EXCLUSIVITY: A label (wavelength) can be used at most
information. It is assumed that both center frequency and bandwidth once among a given set of ports. The set of ports is specified as a
(Q) tuning can be done without causing faults in existing signals. parameter to this constraint.
Restriction specific parameters are used with one or more of the Restriction specific parameters are used with one or more of the
previously listed restriction types. The currently defined previously listed restriction types. The currently defined
parameters are: parameters are:
LabelSet is a conceptual set of labels (wavelengths). LabelSet is a conceptual set of labels (wavelengths).
MaxNumChannels is the maximum number of channels that can be MaxNumChannels is the maximum number of channels that can be
simultaneously used (relative to either a port or a matrix). simultaneously used (relative to either a port or a matrix).
MaxWaveBandWidth is the maximum width of a tunable waveband LinkSet is a conceptual set of ports.
switching device.
PortSet is a conceptual set of ports. MaxLabelRange indicates the maximum range of the labels.
For example, if the port is a "colored" drop port of a ROADM then For example, if the port is a "colored" drop port of a ROADM then
there are two restrictions: (a) CHANNEL_COUNT, with MaxNumChannels = there are two restrictions: (a) CHANNEL_COUNT, with MaxNumChannels =
1, and (b) SIMPLE_WAVELENGTH, with the wavelength set consisting of 1, and (b) SIMPLE_WAVELENGTH, with the wavelength set consisting of
a single member corresponding to the frequency of the permitted a single member corresponding to the frequency of the permitted
wavelength. See [Switch] for a complete waveband example. wavelength. See [Switch] for a complete waveband example.
This information model for port wavelength (label) restrictions is This information model for port wavelength (label) restrictions is
fairly general in that it can be applied to ports that have label 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 restrictions only or to ports that are part of an asymmetric switch
skipping to change at page 18, line 41 skipping to change at page 19, line 41
extensions for details of placement of information elements. extensions for details of placement of information elements.
7.2. Dynamic Node Information (WSON Specific) 7.2. Dynamic Node Information (WSON Specific)
Currently the only node information that can be considered dynamic Currently the only node information that can be considered dynamic
is the resource pool state and can be isolated into a dynamic node is the resource pool state and can be isolated into a dynamic node
information element as follows: information element as follows:
<DynamicNodeInfo> ::= <NodeID> [<ResourcePool>] <DynamicNodeInfo> ::= <NodeID> [<ResourcePool>]
Where
<ResourcePool> ::= <ResourceBlockInfo>...[<RBPoolState>]
8. Security Considerations 8. 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 WSONs. Such a model is very similar from a security standpoint of
the information that can be currently conveyed via GMPLS routing the 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 current utilization, and well as the capabilities of switches
and routers within the network. As such this information should be and routers within the network. As such this information should be
protected from disclosure to unintended recipients. In addition, protected from disclosure to unintended recipients. In addition,
the intentional modification of this information can significantly the intentional modification of this information can significantly
skipping to change at page 20, line 9 skipping to change at page 21, line 9
action. action.
10. Acknowledgments 10. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
11. References 11. References
11.1. Normative References 11.1. Normative References
[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.
[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, "Modeling
WDM Wavelength Switching Systems for Use in GMPLS and
Automated Path Computation", Journal of Optical
Communications and Networking, vol. 1, June, 2009, pp.
187-195.
[G.707] ITU-T Recommendation G.707, Network node interface for the [G.707] ITU-T Recommendation G.707, Network node interface for the
synchronous digital hierarchy (SDH), January 2007. synchronous digital hierarchy (SDH), January 2007.
[G.709] ITU-T Recommendation G.709, Interfaces for the Optical [G.709] ITU-T Recommendation G.709, Interfaces for the Optical
Transport Network(OTN), March 2003. Transport Network(OTN), March 2003.
[G.975.1] ITU-T Recommendation G.975.1, Forward error correction for [G.975.1] ITU-T Recommendation G.975.1, Forward error correction for
high bit-rate DWDM submarine systems, February 2004. high bit-rate DWDM submarine systems, February 2004.
[RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used [RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used
skipping to change at page 21, line 26 skipping to change at page 22, line 15
11.2. Informative References 11.2. Informative References
[OFC08] P. Roorda and B. Collings, "Evolution to Colorless and [OFC08] P. Roorda and B. Collings, "Evolution to Colorless and
Directionless ROADM Architectures," Optical Fiber Directionless ROADM Architectures," Optical Fiber
communication/National Fiber Optic Engineers Conference, communication/National Fiber Optic Engineers Conference,
2008. OFC/NFOEC 2008. Conference on, 2008, pp. 1-3. 2008. OFC/NFOEC 2008. Conference on, 2008, pp. 1-3.
[Shared] G. Bernstein, Y. Lee, "Shared Backup Mesh Protection in [Shared] G. Bernstein, Y. Lee, "Shared Backup Mesh Protection in
PCE-based WSON Networks", iPOP 2008. PCE-based WSON Networks", iPOP 2008.
[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, "Modeling
WDM Wavelength Switching Systems for Use in GMPLS and
Automated Path Computation", Journal of Optical
Communications and 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.
[RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS [RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010. Networks", RFC 5920, July 2010.
[RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and
PCE Control of Wavelength Switched Optical Networks", RFC PCE Control of Wavelength Switched Optical Networks", RFC
6163, April 2011. 6163, April 2011.
12. Contributors 12. Contributors
Diego Caviglia Diego Caviglia
Ericsson Ericsson
Via A. Negrone 1/A 16153 Via A. Negrone 1/A 16153
skipping to change at page 23, line 4 skipping to change at page 23, line 40
NEC Corp. NEC Corp.
1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666 1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666
Japan Japan
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
Cyril Margaria Cyril Margaria
Email: cyril.margaria@googlemail.com Email: cyril.margaria@gmail.com
Author's Addresses Author's Addresses
Greg M. Bernstein (ed.) Greg M. Bernstein (ed.)
Grotto Networking Grotto Networking
Fremont California, USA Fremont California, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
 End of changes. 27 change blocks. 
74 lines changed or deleted 81 lines changed or added

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