Re: FW: Evaluation: draft-ietf-ccamp-gmpls-architecture - Generalized Multi-Protocol Label Switching Architecture to Proposed Standard

[Dimitri.Papadimitriou@alcatel.be]

bert, this is the intention (taking also into account the
previous set of ref's comment), here probably harald wanted to
see a single sentence where the following words are included:
GMPLS, control plane, protocol (suite), architecture, and
another sentence (first sentence of the introduction) should
be rephrased from "The architecture presented..." to "The
architecture described..." since it is an "architecture
descriptive" document; these together should address
his hesitation(s) now of course there was a trade-off here
between reproduce all the i-d's (this wasn't the ultimate
intention) and give a fair level of details (intention was
also to have a "structuring i-d"), thus here the reader is
pointed to the appropriate reference when the level of the
details wouldn't be suitable in the scope of this document
(anyway if the iesg thinks some pointers are still missing
well would you then just send them asap, and if the ccamp
community thinks additional editorial changes are needed to
address these comments input is welcome on this specific
point)

ps: i'd like to recap here also there was imho a very good
i-d ("Multi-Protocol Lambda Switching: Combining MPLS Traffic 
Engineering Control With Optical Crossconnects" draft-awduche-
mpls-te-optical-03.txt) which is the fundamental step between
this i-d (gmpls and related) and rfc2702 (mpls-te), rfc3031
(mpls) unfortunately it has not been further progressed since
april'01

thanks,
- dimitri.

Wijnen, Bert (Bert) wrote:
> Dimitri, if for any reason (possibly on based on other comments
> from IESG) you are going to do another rev, can you pls check
> the below comments and see if some additional editorial changes 
> make sense?
>
> By the way, you can see that Harald also noted the "many Work in Progress"
> documents that are listed as normative references.
>
> Thanks,
> Bert 
> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: zaterdag 26 april 2003 18:03
> To: IESG Secretary; Internet Engineering Steering Group
> Subject: Re: Evaluation: draft-ietf-ccamp-gmpls-architecture -
> Generalized Multi-Protocol Label Switching Architecture to Proposed
> Standard
>
> Harald Alvestrand has no Objection.
>
> note: this does not mean that I like it.....
>
> In particular, I don't like the fact that the document can't decide whether 
> it's an architecture, an introduction or a specification. It goes into lots 
> of details that are ALMOST specified, but then just says that these are 
> "finished elsewhere" - sometimes giving, sometimes not giving, the forward 
> pointers.
>
> It's just about right (although overly detailed, and lacking some pointers 
> to where the "real spec" is) for an introduction.
>
> It also *contains* an architecture description - the idea of a control 
> plane that is a fully connected IP network (with, apparently, manual link 
> configuration), a set of links that are not necessarily the control links, 
> and in many cases not even IP-capable links, and groupings of these that 
> can be manipulated and controlled in various ways, and a set of protocols 
> and ways to use those protocols that are defined in other documents.
>
> But the lenght and the level of detail means that it's very hard for me to 
> be sure I have grasped that architecture correctly and fully.
>
> And - note - I have said nothing about whether or not I *like* that 
> architecture.
>
> Note: It will be a while before this is published as an RFC. There are no 
> less than thirteen "works in progress" in its normative references.
>
>                      Harald

--
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