Proposed response to the Liaison Statement on ASON Routing

[Kireeti Kompella <kireeti@juniper.net>]

Hi All,

Here's a proposed response to the Liaison Statement from the ITU-T
Study Group 15, Q 12, 14/15 on ASON Routing Activities, dated January
31, 2003.

Please post any comments you have to the CCAMP list; we would like to
send this by COB Friday April 18.

Kireeti.
--------------------------------------------------------------------
Dear Mr. Lam,

> Q.14/15 would like to inform the IETF CCAMP Working Group and the Sub-IP
> Area Directors that Q.14/15 is beginning work in defining the connection
> routing protocols for use in ASON networks, and requests the benefit of
> the IETF's expertise in this area.

The IETF CCAMP WG would be glad to help.

> Q.12/15 has also developed an amendment to ITU-T Recommendation G.8080
> (Architecture for the Automatically Switched Optical Network) to provide
> clarification on naming and structure of the network for routing and
> signalling and add architectural support for discovery procedures and
> protection/restoration.
>
> A set of protocol-independent high level routing architecture and
> requirements has already been specified in ITU-T Recommendation G.7715
> (see below) and Q. 14/15 has initiated work on a new draft recommendation
> (numbered G.7715.1) describing the requirements for a link-state method
> routing protocol for ASON.
>
> Some of the following requirements have been identified:
>
> 1.       The routing protocol should support partitioning of transport
> networks that may be controlled by using multiple instances of different
> routing protocols at different levels.
>
> 2.       The routing protocol should support separation of control and
> data (i.e, transport) planes such that data and control entities are not
> required to be co-located, and the scope of the data plane resources seen
> by a routing function is not limited.
>
> 3.       The routing protocol should support distribution, abstraction and
> filtering of information within hierarchical and partitioning
> relationships.
>
> 4.      The routing protocol should support independence of inter-domain
> and intra-domain routing protocols.
>
> It should be noted that the scope of this work is limited to routing of
> transport connections within ASON networks.

We believe that the link-state routing paradigm that is being progressed
at the IETF in the CCAMP WG in conjunction with the OSPF and ISIS WGs,
does meet the above requirements.  Some of this has not been articulated
as well as it should be; we are addressing this.

> Q.12 and Q.14/15 wish to work cooperatively with IETF in order to reach a
> common understanding of respective terminology and available mechanisms.

That is an excellent goal.  We would be glad to work with you to achieve
this; similar work is already under way for signaling and protection &
restoration.

> An interim meeting of Q.14/15 will be held on 9-13 June 2003, located in
> Chicago .  The Rapporteur for Q.14/15 invites the participation of
> interested IETF members in discussions of ASON routing protocols at this
> meeting, and invites comments and input from IETF community to progress
> this work.  Those interested in attending the interim meeting should
> contact the Rapporteur for Q.14/15 (H. Kam Lam, hklam@lucent.com) by May
> 27, 2003.  Any contributions directed to the meeting must be submitted by
> June 2, 2003.

Thank you for the invitation.  Several interested participants from the
CCAMP WG are making arrangments to attend; if at all possible, the
chairs of the CCAMP WG will attend as well.  In particular, we plan to
make a presentation stating how the proposed link-state routing structure
in the IETF addresses the requirements for ASON networks.

> Approved Recommendation G.7715  and the consented amendment to
> Recommendation G.8080 may be obtained from the ccamp link at:
>
> ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/in
dex.html

Thank you for making this available.

Kireeti Kompella & Ron Bonica
CCAMP WG chairs