[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00 01

Network Working Group                                      Igor Bryskin
Category: Informational                                      Consultant

Expires: April 2005                                       Adrian Farrel
                                                     Old Dog Consulting

                                                           January 2005

  A Lexicography for the Interpretation of Generalized Multiprotocol
    Label Switching (GMPLS) Terminology within The Context of the
  ITU-T's Automatically Switched Optical Network (ASON) Architecture

           draft-bryskin-ccamp-gmpls-ason-lexicography-00.txt

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   or will be disclosed, and any of which I become aware will be
   disclosed, in accordance with RFC 3668.

   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.

Abstract

   Generalized Multiprotocol Label Switching (GMPLS) has been developed
   by the IETF to facilitate the establishment of Label Switched Paths
   (LSPs) in a variety of physical technologies and across several
   architectural models. The ITU-T has specified an architecture for
   the management of Automatically Switched Optical Networks (ASON).

   This document provides a lexicography for the interpretation of GMPLS
   terminology within the context of the ASON architecture.

   It is important to note that GMPLS is applicable in a far wider set
   of contexts than just ASON. Thus the definitions presented in this
   document do not provide exclusive or complete interpretations of the
   GMPLS concepts. The intention of this document is simply to allow the
   GMPLS terms to be applied within the ASON context.

Bryskin and Farrel                                                Page 1

draft-bryskin-ccamp-gmpls-ason-lexicography-00.txt          January 2005

1. Introduction

   Generalized Multiprotocol Label Switching (GMPLS) has been developed
   by the IETF to facilitate the establishment of Label Switched Paths
   (LSPs) in a variety of physical technologies such as Packet Switching
   Capable (PSC), Layer Two Switching Capable (L2SC), Time Division
   Multiplexing (TDM), Lambda Switching Capable (LSC). and Fiber
   Switching Capable (FSC).

   GMPLS is deliberately specified to allow it to be applicable in
   several key architectures including the Integrated Model, the Overlay
   Model, and the Augmented Model. More information on these
   architectural models and on GMPLS can be found in [RFC3945].

   The ITU-T has specified an architecture for the management of
   Automatically Switched Optical Networks (ASON). This architecture
   forms the basis of many recommendations within the ITU-T.

   Because the GMPLS and ASON architectures were developed by different
   people in different standards bodies, and because the architectures
   have very different historic backgrounds (the Internet, and telephone
   and transport networks respectively), the terminology used is
   different. In order to demonstrate that GMPLS is a suitable
   technology to satisfy the requirements of the ASON architecture it is
   necessary to examine the terminology and provide a mapping between
   GMPLS and ASON terms.

   This document provides a lexicography for the interpretation of GMPLS
   terminology within the context of the ASON architecture. It does not
   provide wider definitions of the GMPLS terms which can already be
   found in existing RFCs. Thus the definitions presented in this
   document do not provide exclusive or complete interpretations of the
   GMPLS concepts. The intention of this document is simply to allow the
   GMPLS terms to be applied within the ASON context.

2. Terminology Sources

2.1. GMPLS Terminology Sources

   GMPLS Terminology is principally defined in [RFC3945]. Other
   documents provide further key definitions including [GMPLS-RTG],
   [BUNDLE], [LSP-HIER] and [LMP].

   The reader should be familiar with these other documents before
   attempting to use this document to provide a mapping to between GMPLS
   and ASON.

   For details of GMPLS signaling please refer to [RFC3471] and
   [RFC3473]. For details of GMPLS routing, please refer to [GMPLS-OSPF]
   and [GMPLS-ISIS].

Bryskin and Farrel                                                Page 2

draft-bryskin-ccamp-gmpls-ason-lexicography-00.txt          January 2005

2.2. ASON Terminology Sources

   The ASON architecture is specified in ITU-T Recommendation G.8080
   [G-8080]. This is developed from generic functional architectures and
   requirements specified in [G-805], [G-807] and [G-872].

   The reader must be familiar with these documents before attempting to
   apply the lexicography set out here.

2.3. Common Terminology Sources

   The work in this document builds on the shared view of ASON
   requirements and requirements expressed in [ASON-SIG], [ASON-RTG] and
   [TRANSPORT-LMP].

3. Lexicography






4. Guidance on the Application of this Lexicography


5. IANA Considerations

   This informational document defines no new code points and requires
   no action by IANA.

6. Management Considerations

   Both GMPLS and ASON networks require management. Both GMPLS and ASON
   specifications include considerable efforts to provide operator
   control and monitoring, as well as OAM functionality.

   These concepts are, however, out of scope of this document.

7. Security Considerations

   Security is also a significant requirement of both GMPLS and ASON
   architectures.

   Again, however, this informational document is intended only to
   provide a lexicography, and the security concerns are, therefore, out
   of scope.

8. Acknowledgements

   The authors would like to thank participants in the IETF's CCAMP
   working group and the ITU-T's Study Group 15 for their help in
   producing this document. In particular, all those who attended the
   Study Group 15 Question 14 Interim Meeting in Holmdel, New Jersey
   during January 2005.

9. Intellectual Property Consideration

   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
   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.

10. Normative References

   [RFC3945]        E. Mannie (Ed.). "Generalized Multi-Protocol Label
                    Switching (GMPLS) Architecture", RFC 3945, October
                    2004.

   [GMPLS-RTG]      Kompella, K. and Rekhter, Y., "Routing Extensions in
                    Support of Generalized Multi-Protocol Label
                    Switching", <draft-ietf-ccamp-gmpls-routing>, work
                    in progress.

   [BUNDLE]         Kompella, K., Rekhter, Y., and Berger, L., "Link
                    Bundling in MPLS Traffic Engineering",
                    <draft-ietf-mpls-bundle>, work in progress.

   [LSP-HIER]       Kompella, K. and Rekhter, Y., "LSP Hierarchy with
                    Generalized MPLS TE",
                    <draft-ietf-mpls-lsp-hierarchy>, work in progress.

   [LMP]            J. Lang (Ed.), "Link Management Protocol (LMP)",
                    <draft-ietf-ccamp-lmp>, work in progress.

11. Informational References

   [RFC3471]        L. Berger (Ed.), "Generalized Multi-Protocol Label
                    Switching (GMPLS) Signaling Functional Description",
                    RFC 3471, January 2003.

   [RFC3473]        L. Berger (Ed.), "Generalized Multi-Protocol Label
                    Switching (GMPLS) Signaling Resource ReserVation
                    Protocol-Traffic Engineering (RSVP-TE) Extensions",
                    RFC 3471, January 2003.

   [GMPLS-OSPF]     Kompella, K., and Rekhter, Y. (Ed.), "OSPF
                    Extensions in Support of Generalized MPLS",
                    <draft-ietf-ccamp-ospf-gmpls-extensions>, work in
                    progress.

   [GMPLS-ISIS]     Kompella, K., and Rekhter, Y. (Ed.), "IS-IS
                    Extensions in Support of Generalized MPLS",
                    <draft-ietf-isis-gmpls-extensions>, work in
                    progress.

   [ASON-SIG]       Papadimitriou, D., Drake, J., Ash, J., Farrel, A.,
                    and Ong, L., "Requirements for Generalized MPLS
                    (GMPLS) Signaling Usage and Extensions for
                    Automatically Switched Optical Network (ASON)",
                    <draft-ietf-ccamp-gmpls-ason-reqts>, work in
                    progress.

   [ASON-RTG]       D. Brungard (Ed.), "Requirements for Generalized
                    MPLS (GMPLS) Routing for Automatically Switched
                    Optical Network (ASON)",
                    <draft-ietf-ccamp-gmpls-ason-routing-reqts>, work in
                    progress.

   [TRANSPORT-LMP]  Fedyk, D., Aboul-Magd, O., Brungard, D., Lang, J.,
                    Papadimitriou, D., "A Transport Network View of LMP"
                    <draft-ietf-ccamp-transport-lmp>, work in progress.

   For information on the availability of the following documents,
   please see http://www.itu.int.

   [G-8080]         ITU-T Recommendation G.8080/Y.1304, Architecture for
                    the automatically switched optical network (ASON).

   [G-805]          ITU-T Recommendation G.805 (2000), Generic
                    functional architecture of transport networks.

   [G-807]          ITU-T Recommendation G.807/Y.1302 (2001),
                    Requirements for the automatic switched transport
                    network (ASTN).

   [G-872]          ITU-T Recommendation G.872 (2001), Architecture of
                    optical transport networks.

12. Authors' Addresses

   Igor Bryskin
   Independent Consultant
   Phone:
   EMail:  i_bryskin@yahoo.com

   Adrian Farrel
   Old Dog Consulting
   Phone:  +44 (0) 1978 860944
   EMail:  adrian@olddog.co.uk

13. 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.

14. Full Copyright Statement

   Copyright (C) The Internet Society (2005).  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.


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/