[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt



I also have no problem with Adrian editing the document,
especially since it is a framework document and does not
advocate any specific technique.  I understand the 
reservation, but it should be balanced against the
need to make progress in the group.

Cheers,

Lyndon

-----Original Message-----
From: Yakov Rekhter [mailto:yakov@juniper.net]
Sent: Thursday, May 13, 2004 4:25 PM
To: Tom Petch
Cc: Adrian Farrel; ccamp@ops.ietf.org
Subject: Re: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt



Tom,

> I always have a reservation when the WG chair and the I-D editor are or
> turn out to be the same individual.  I think that the IETF discourages this
> for good reason and so for this to be adopted, I would like someone other
> than the WG chair to take the role of (lead) editor.

There are plenty of precedence where a WG chair/co-chair is also
an editor of some of the WG documents, and so far we've yet to
see any significant problem(s) with this. So, I don't think Adrian
being an editor is a problem. Especially, since he is not the
only chair of the WG.

Yakov.

> 
> Tom Petch
> 
> -----Original Message-----
> From: Adrian Farrel <adrian@olddog.co.uk>
> To: ccamp@ops.ietf.org <ccamp@ops.ietf.org>
> Date: 06 May 2004 22:08
> Subject: Re: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt
> 
> 
> >Folks,
> >
> >This draft represents the first step in the much-discussed six point plan
> towards
> >inter-area/AS solutions.
> >
> >I would like three things to happen:
> >
> >a. This draft to become a WG draft
> >    Please send your opinions
> >b. The draft to be reinforced in areas that people consider necessary
> >    One such area MAY be diverse routing.
> >    Please send suggested text, but
> >    - recall that this is not a solutions draft
> >    - try to keep the length of the draft down below 100 pages
> >c. Move on with the next step in the plan.
> >    At the moment, this seems to require effort on points 2 and 4
> >    Viz, develop individual signaling solutions as required and
> >    state their applicability.
> >    We await input from those who have preferred solutions.
> >
> >Cheers,
> >Adrian
> >----- Original Message -----
> >From: <Internet-Drafts@ietf.org>
> >To: <i-d-announce@ietf.org>
> >Cc: <ccamp@ops.ietf.org>
> >Sent: Friday, April 30, 2004 8:44 PM
> >Subject: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt
> >
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>
> >> Title : A Framework for Inter-Domain MPLS Traffic Engineering
> >> Author(s) : A. Farrel, et al.
> >> Filename : draft-farrel-ccamp-inter-domain-framework-00.txt
> >> Pages : 14
> >> Date : 2004-4-30
> >>
> >> This document provides a framework for establishing and controlling
> >>    Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
> >>    Label Switched Paths (LSPs) in multi-domain networks.
> >>
> >>    For the purposes of this document, a domain is considered to be any
> >>    collection of network elements within a common sphere of address
> >>    management or path computational responsibility. Examples of such
> >>    domains include IGP areas and Autonomous Systems.
> >>
> >> A URL for this Internet-Draft is:
> >>
> http://www.ietf.org/internet-drafts/draft-farrel-ccamp-inter-domain-framewo
> rk-00.txt
> >>
> 
> 
>