Internet DRAFT - draft-miyazaki-ccamp-lsp-hierachy-in-otn
draft-miyazaki-ccamp-lsp-hierachy-in-otn
CCAMP Working Group K.Miyazaki
Internet Draft Fujitsu
Expires: September 2006 March 30, 2006
LSP Hierarchy in the Optical Transport Network
draft-miyazaki-ccamp-lsp-hierachy-in-otn-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
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
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
This document may only be posted in an Internet-Draft.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 30, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006). All Rights Reserved.
Abstract
For the Optical Transport Network(OTN), ITU-T defined the digital and
optical layers in [ITU-T G.872] to manage and control the OTN. Base
Miyazaki Expires September 30, 2006 [Page 1]
Internet-Draft LSP Hierarchy in OTN March 2006
on this Recommendation, several hierarchical LSPs are needed to setup
an end-to-end client signal and LSP hierarchy becomes very complex.
However, this document describes the example of networks and shows
the LSP hierarchy in OTN.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119.
Table of Contents
1. Introduction................................................2
2. Network examples...............................................3
3. LSP hierarchy in OTN.........................................7
4. Security Considerations......................................8
5. References..................................................8
5.1. Normative References....................................8
Author's Addresses.............................................8
Intellectual Property Statement.................................8
Disclaimer of Validity.........................................9
Copyright Statement............................................9
Acknowledgment.................................................9
1. Introduction
As described in [ITU-T G.872], ITU-T defined the digital layers and
the optical layers in the OTN(Optical Transport Network) to supervise
and control the optical paths. In the digital OTN, OPUk(Optical
Channel Payload Unit), ODUk(Optical Channel Data Unit) and OUT.
(optical Channel Transport Unit) are defined. In these layers, the
optical stream is terminated and the Digital Wrapper Overhead is
managed. In the optical OTN, Optical Channel, Optical Multiplex
Section and Optical Transmission Section are defined. And there is no
electric process in these layers. Otherwise there is client other
than the digital OTN (pre-OTN).
This document presents the LSP hierarchy in the OTN.
Miyazaki Expires September 30, 2006 [Page 2]
Internet-Draft LSP Hierarchy in OTN March 2006
+---------------------------------------------------------+
| |
| +------+ |
| |Client| |
| +------+ ------------- |
| | OPUk | Optical Channel Payload Unit ^ |
| +------+ | |
| | ODUk | Optical Channel Data Unit Digital Layer |
| +------+ | |
| | OTUk | Optical Channel Transport Unit v |
| +------+ ------------- |
| | OCh | Optical Channel ^ |
| +------+ | |
| | OMS | Optical Multiplex Section Optical Layer |
| +------+ | |
| | OTS | Optical Transmission Section v |
| +------+ ------------- |
| |
| |
+---------------------------------------------------------+
Figure 1 Layer structure in the OTN.
2. Network examples
Based on the [ITU-T G.872], there are some structures shown from
Figure 2 to Figure 8.
In Figure 2, OXCs does not handle the Digital Wrapper and the ingress
OXC converts the specific wavelength to transmit the client signal to
the egress OXC. And the encoding between OXCs is lambda. Based on the
G.872, there is one lambda LSP between ingress and egress OXC.
Miyazaki Expires September 30, 2006 [Page 3]
Internet-Draft LSP Hierarchy in OTN March 2006
+-------------------------------------------+
| |
| +---+ +---+ |
|--|Clt| |Clt|--|
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |OCh|X|OCh|---|OCh|X|OCh|---|OCh|X|OCh| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 OXC2 OXC3 |
| |
| X:Cross Connect or Connection function |
+-------------------------------------------+
Figure 2 OXC without Digital Wrapper
In Figure 3 and 4, some OXCs deal with the Digital Wrapper, and some
transit OXCs do not deal with the Digital Wrapper. And the encoding
between OXC1 and OXC2 in Figure 4 is the digital wrapper. In these
Figures, there are one digital wrapper LSP and one lambda LSPs.
+-------------------------------------------+
| |
| +---+ +---+ |
|--|Clt| |Clt|--|
| +---+ +---+ |
| |ODU| |ODU| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |OCh|X|OCh|---|OCh|X|OCh|---|OCh|X|OCh| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 OXC2 OXC3 |
| |
+-------------------------------------------+
Figure 3 OXCs at Ingress/Egress terminate Digital Wrapper
Miyazaki Expires September 30, 2006 [Page 4]
Internet-Draft LSP Hierarchy in OTN March 2006
+-------------------------------------------+
| |
| +---+ +---+ |
|--|Clt| |Clt|--|
| +---+ +---+ +---+ +---+ |
| |ODU| |ODU| |ODU| |ODU| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |OCh|X|OCh|---|OCh|X|OCh|---|OCh|X|OCh| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 OXC2 OXC3 |
| |
+-------------------------------------------+
Figure 4 OXCs at Ingress/Egress/some Transit terminate Digital
Wrapper
In Figure 5, all OXCs terminate the Digital Wrapper. i.e. the
encoding between OXCs is the digital wrapper. Therefore there are one
digital wrapper LSP and two lambda LSPs.
+-------------------------------------------+
| |
| +---+ +---+ |
|--|Clt| |Clt|--|
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |ODU| |ODU| |ODU| |ODU| |ODU| |ODU| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |OCh|X|OCh|---|OCh|X|OCh|---|OCh|X|OCh| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 OXC2 OXC3 |
| |
+-------------------------------------------+
Figure 5 OXC at Ingress/Egress/Transit terminates Digital Wrapper
Miyazaki Expires September 30, 2006 [Page 5]
Internet-Draft LSP Hierarchy in OTN March 2006
In Figure 6, transit OXCs terminate the client signal. The encoding
between OXC2 and OXC3 is encoding of client signal such as SDH/SONET.
Therefore there is one client LSP and two digital wrapper LSPs and
two lambda LSPs.
+---------------------------------------------------------+
| |
| +---+ +---+ +---+ +---+ |
|--|Clt| |Clt|---|Clt| |Clt|--|
| +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ |
| |ODU| |ODU| |ODU| |ODU| |ODU| |ODU| |ODU| |ODU| |
| +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ |
| |OCh|X|OCh|---|OCh|X|OCh| |OCh|X|OCh|---|OCh|X|OCh| |
| +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 OXC2 OXC3 OXC4 |
| |
+---------------------------------------------------------+
Figure 6 Transit's OXC terminates Client signal
In Figure 7, there are ODU multiplexers from the ODU1(2.5Gbps) to
ODU2(10Gbps). In this network, we must setup digital wrapper LSP with
ODU2 between OXC1 and OXC2, and between OXC3 and OXC4 respectively.
And the digital wrapper LSP with ODU1 between OXC1 and OXC4 must be
setup.
+-------------------------------------------------------------+
| |
| +----+ +----+ |
|--|Clt | |Clt |--|
| +----+ +----+ +----+ +----+ |
| |ODU1| |ODU1|---|ODU1| |ODU1| |
| +----+ +----+ +----+ +----+ |
| |ODU2| |ODU2| |ODU2| |ODU2| |
| +----+ +---+ +---+ +----+ +----+ +---+ +---+ +----+ |
| |OCh |X|OCh|---|OCh|X|OCh | |OCh |X|OCh|---|OCh|X|OCh | |
| +----+ +---+ +---+ +----+ +----+ +---+ +---+ +----+ |
| OXC1 OXC2 OXC3 OXC4 |
| |
+-------------------------------------------------------------+
Figure 7 OXCs have ODU multiplexer
Miyazaki Expires September 30, 2006 [Page 6]
Internet-Draft LSP Hierarchy in OTN March 2006
Otherwise, in the long haul network, there may be some regenerators
with OEO. In this network the encoding between OXCs is the digital
wrapper.
+---------------------------------------------+
| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
| |ODU| |ODU| |ODU|X|ODU| |ODU| |ODU| |
| +---+ +---+ +---+ +---+ +---+ +---+ |
|---|OCh|X|OCh|---|OCh| |OCh|---|OCh|X|OCh|---|
| +---+ +---+ +---+ +---+ +---+ +---+ |
| OXC1 REG with OEO OXC2 |
| |
+---------------------------------------------+
Figure 8 Regenerator terminates Digital Wrapper
3. LSP hierarchy in OTN
Based on the G.872, we must setup several LSPs to setup an end-to-end
LSP shown in section 2.
When we setup a LSP with the lambda encoding, TE link with the
digital wrapper or the SONET/SDH encoding can not be used. But a LSP
with the digital wrapper can use the TE link with the lambda encoding.
When the LSP with lambda encoding is required, figure 2 network may
be available for that requirement. When the LSP with the digital
wrapper encoding is required, figure 3, 4, 5, 7 and 8 networks may be
available. In these network, some hierarchical LSPs such as
lambda(OCh) and the digital wrapper(ODU2) are exist. When the LSP
with the client encoding is required, all figure network may be
available if the transponder can accommodate the client signal.
And, when the ODU multiplexer between ODU1(2.5Gbps), ODU2(10Gbps) and
ODU3(40Gbps) exists, the LSPs in each ODUk layer must be created.
Otherwise from the view point of the network management, the operator
should monitor the LSPs to guarantee the QoS. In the digital OTN, the
Tandem Connection Monitoring may be used for fault localization or
Miyazaki Expires September 30, 2006 [Page 7]
Internet-Draft LSP Hierarchy in OTN March 2006
verification of delivered quality of service. In the optical OTN,
optical monitoring such as OSNR may be used. In the pre-OTN, some
client mechanism may be used. Otherwise, the alarm notification
mechanism is different each other.
Therefore, the LSPs in each digital OTN should be separated. And when the
LSP in digital OTN is required, the LSPs in the optical OTN should not be created.
4. Security Considerations
This document introduces no new security considerations.
5. References
5.1. Normative References
[ITU-T G.872] ITU-T Recommendation G.872, "Architecture of optical
transport network", November 2001.
[ITU-T G.709] ITU-T Recommendation G.709, "Interfaces for the
Optical Transport Network(OTN)", March 2003.
Author's Addresses
Keiji Miyazaki
Fujitsu
4-1-1, Kamikodanaka, Nakahara-ku, Kawasaki, Japan
Phone: +81-44-754-2765
Email: miyazaki.keiji@jp.fujitsu.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
Miyazaki Expires September 30, 2006 [Page 8]
Internet-Draft LSP Hierarchy in OTN March 2006
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006).
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
Funding for the RFC Editor function is currently provided by the
Internet Society.
Miyazaki Expires September 30, 2006 [Page 9]
