[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ASON reqts
Jerry, Vishal, and all,
Ash, Gerald R (Jerry), ALABS wrote:
Vishal,
Kireeti,
<snip>
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.
The conclusion drawn from some initial discussions on specific
routing protocols was to step back for a moment and develop a
so-called mid-level requirements recommendation for a link state
routing protocol which still should be protocol neutral. This
requirements recommendation will then be used for the assessment
of existing link state routing protocols to be applied in ASON.
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.
I fully share your view - the idea was indeed to invite IETF GMPLS
routing experts in order to have a closer and much better cooperation
on routing compared to what happened with signaling.
Furthermore, I would like to add that I have read this document
and it is ready to be a CCAMP WG doc (being aware that some
issues need further discussion or clarification which shouldn't
preclude that this document becomes a WG doc)
Dieter