The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Feb> msg00033



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

I-D ACTION:draft-andersson-mpls-g-chng-proc-00.txt

  • From: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>
  • Date: Fri, 14 Feb 2003 16:05:57 -0500
  • Cc: mpls@UU.NET, ccamp@ops.ietf.org, pwe3@ietf.org
  • X-OriginalArrivalTime: 14 Feb 2003 21:19:48.0576 (UTC) FILETIME=[CDE71600:01C2D46E]

Loa,

I assume that the mpls and ccamp lists are the appropriate places for 
discussion of this draft.  I also included the pwe3 list, since this also 
affects the work in that WG.  I apologize for the crossposts to those of 
you on more than one of these lists (including myself).  Perhaps once the 
discussion has started, we can pick just one place to continue it.

My initial reaction on reading your draft was that I didn't see any 
discussion of the pwe3 WG, which as you know is specifying extensions to 
RFC 3036.  For the purposes of your draft, would pwe3 be classified as a 
"protocol specifying working group"?  And is it your intention that the 
current work in the pwe3 WG be approved by the "requirement evaluating 
working group" prior to its documents being published as RFCs?  Or would 
this be grandfathered in as already having been chartered by the IESG?

Thanks,
Andy

-------

At 2/14/2003 06:43 AM -0500, Internet-Drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : MPLS and GMPLS Change Process
>         Author(s)       : L. Andersson
>         Filename        : draft-andersson-mpls-g-chng-proc-00.txt
>         Pages           : 11
>         Date            : 2003-2-13
>
>This memo describes the process through which individuals, working
>groups and external standards bodies can influence the development of
>MPLS and GMPLS standards.  With respect to standardization, this
>process means that (G)MPLS extensions and changes can be done through
>the IETF only, the body that created the (G)MPLS technology.  The
>IETF will not publish a (G)MPLS technology extension RFC outside of
>the processes described here.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-andersson-mpls-g-chng-proc-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-andersson-mpls-g-chng-proc-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-andersson-mpls-g-chng-proc-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2003-2-13152703.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-andersson-mpls-g-chng-proc-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-andersson-mpls-g-chng-proc-00.txt>