1. Igor Bryskin - i_bryskin@yahoo.com Adrian Farrel - adrian@olddog.co.uk
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-01.txt
Igor Bryskin - Adrian Farrel -
62nd IETF Minneapolis March 2005

2. 62nd IETF Minneapolis March 2005
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
62nd IETF Minneapolis March 2005

3. 62nd IETF Minneapolis March 2005
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
62nd IETF Minneapolis March 2005

4. 62nd IETF Minneapolis March 2005
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
62nd IETF Minneapolis March 2005

5. 62nd IETF Minneapolis March 2005
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.
62nd IETF Minneapolis March 2005