A%20Lexicography%20for%20the%20Interpretation%20of%20Generalized%20Multiprotocol%20Label%20Switching%20(GMPLS)%20Terminology%20within%20The%20Context%20of%20the%20ITU-T's%20Automatically%20Switched%20Optical%20Network%20(ASON)%20Architecture%20draft-bryskin-ccamp-gmpls-ason-lexicography-01.txt

1
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)
Architecturedraft-bryskin-ccamp-gmpls-ason-lexic
ography-01.txt

• Igor Bryskin - i_bryskin_at_yahoo.comAdrian Farrel
  - adrian_at_olddog.co.uk

2
Objectives

• ASON is real!
• ASON is a useful architecture for certain
  deployment scenarios for transport networks
• ASON has a wide following among carriers
• GMPLS protocols provide good tools to implement
  the architecture
• GMPLS and ASON use significantly different
  terminology
• Lack of mutual understanding blocks the adoption
  of GMPLS in an ASON environment
• Several drafts to explain ASON to the IETF
• Provide a lexicography for the interpretation of
  GMPLS terminology within the context of the ASON
  architecture
• Objective is to allow people who understand ASON
  to be able to read GMPLS RFCs and apply the
  technology to their architecture

3
Non-Objectives

• Non-objectives are very important!
• This document is not
• An attempt to redefine any GMPLS terms
• A deprecation of any GMPLS definitions
• An exclusion of any GMPLS architectural models
• An expression of support for or opposition to ASON

4
Current Status

• ITU-T Study Group 15 Question 14 requested a
  joint meeting to discuss terminology
• Holmdel, Jan 2005
• Incoming contribution from Igor and Adrian
• Starting point for discussions
• Already discussed privately in CCAMP
• Meeting agreed lexicography
• Current draft reproduces this and wraps it with
  wise words

5
Proposed Actions

• Now need to be sure that CCAMP agrees
• Already had some full and frank private
  discussions
• Need discussion on the mailing list
• Please be aware of ASON architecture
• We cannot and do not want to change it!
• Please be aware of objectives
• There is a strict and limited purpose to the
  draft
• Therefore be aware of non-objectives, too.
• Authors believe this draft should be CCAMP work,
  but would be happy to continue to RFC as a
  personal draft.