RE: ASON reqts

["Ash, Gerald R (Jerry), ALABS" <gash@att.com>]

Vishal,
Kireeti,

> I should have clarified that I did not mean that the two pieces of
> work (routing and signaling) should be so tightly coupled that one
> cannot proceed independently of the other. What I did mean was that
> it would be better to initiate the routing work as well, so that 
> any impact that routing has on signaling is captured in the signaling
> work early on. This will be useful, as it'll prevent problems later.

Agreed.  We should progress the GMPLS-ASON routing requirements in a separate, parallel effort to the GMPLS-ASON signaling requirements.

> I believe the initial routing requirements are captured in ITU doc.
> G.7715. However, I am not sure whether, unlike signaling, the ITU has
> begun work on the protocol-specific instantiations of routing 
> requirements.

That is my understanding as well.  The GMPLS-ASON routing requirements should be based on the ITU-T G.7715 requirements.  

Hopefully the IETF will progress GMPLS-ASON routing extensions to meet the requirements, so that hopefully the ITU will not need to undertake protocol-specific extensions of GMPLS routing.  And hopefully this would then avoid another G.7713.2-like debacle.

I believe that ASON routing work is the subject of an ITU-T experts' meeting of Question 14/15, to be held in Chicago 9-13 June 2003.  The ITU-T has invited the IETF GMPLS routing experts to participate, as per Wesam's presentation documented in the IETF-56/CCAMP meeting minutes http://ietf.org/proceedings/03mar/minutes/ccamp.htm.

Jerry