hi jonathan, in order to address the issue raised during this discussion, i would suggest to add the following sentences to the following paragraphs (in section 2.1):
"2. Support of inter-layer attributes (e.g., adaptation
relationships). Between a client and server layer, a general
mechanism for describing the layer relationship exists. For
example "4 client links of type X can be supported by this server
layer link". Another example is being able to identify when two
layers share a common server layer."-> "Attributes describing inter-layer relationships are not captured by the present document. Only single layer attributes are covered."
also, i would also suggest to replace the word "draft" by "document" in the following sentence: "From the factors presented above, development of layer specific GMPLS routing drafts should use the following principles for TE-link attributes."
thanks, - dimitri.
Hi Kireeti -
I was under the impression, given your email sent on 17 Jul 2003, that a new rev of draft-ietf-ccamp-gmpls-routing was going to be released with a statement added saying that the current doc is okay in a single layer network, but doesn't capture inter-layer relationships.
I thought I may have missed an announcement of the new doc on the CCAMP list, but cannot find it in the IETF I-D repository. Am I missing something?
Jonathan Sadler
Kireeti Kompella wrote:
Hi All,
On Thu, 17 Jul 2003, Kireeti Kompella wrote:
Betts, Brungard, Dotaro, Grammel, Kompella, Papadimitriou, Prattico, Sadler, Vigoureux and Zinin got together to iron out the last few issues in the document "Routing Extensions in Support of GMPLS".
In the interests of progressing this document in a timely fashion, we examined these issues from two points of view: a) is the current document set fundamentally broken, and if not, what caveats should be stated? b) how do we move forward and address these issues, whether in the current doc set or in the future?
The consensus we reached for (a) is that the current doc set is okay in a single layer network, but it doesn't capture inter-layer relationships. So, we will state that in draft-ietf-ccamp-gmpls-routing-06.txt, and then progress it.
As for (b), this will be one of the charter items for the ASON Routing Reqts DT. They will be chartered to state clearly what the requirements are, what relations should be captured in a technology/layer independent document, and what should be part of the layer-dependent documents. These will then be addressed in future documents.
Many thanks to all who took part for getting together on such short notice, and for the courteous and productive discussion!
No comments have been received on this subject. I would like to do a one week WG Last Call before sending this back to the IESG.
Since it's been a while, I will recap: a) Jonathan Sadler raised some important issues. mainly regarding layering, and some SDH-specific points. b) Stephen Shew sent a write-up on layering requirements. c) The group above met to make progress on these issues. d) A new version of the Routing document with most of Stephen's text incorporated was posted. (No changes were made to the OSPF doc.)
Please respond by 5pm PDT, Monday Sept 29, 2003 with comments on the changes (i.e., section 2.1); ideally, send specific text that you would like to see.
PS: A design team is being created to specificcaly address ASON routing requirements; the team members and charter will be announced once AD review is complete.
Thanks, Kireeti.
============================================================
The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
Thank you. Tellabs ============================================================
-- Papadimitriou Dimitri E-mail : dimitri.papadimitriou@alcatel.be Private: http://www.rc.bel.alcatel.be/~papadimd/index.html E-mail : dpapadimitriou@psg.com Public : http://psg.com/~dpapadimitriou/ Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium Phone : +32 3 240-8491