[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PWE3] [mpls] proposed charter update for the MPLS TP work
Adrian Farrel wrote:
Include extensions to the [MPLS, PWE3, CCAMP] protocols
Include modifications and extensions to the [MPLS, PWE3, CCAMP]
protocols and procedures
my take on this that we are talking about "extensions" relative the
the existing specification, it is quite possible for an extension to
leave "components of the MPLS architecture unused", that is in
fact the case with most of our documents.
Consequently I agree with Stewart, and would oppose words like,
reduce and modify, since that implies that we intend to *change*
the MPLS architecture, while one of the foundations of the
agreement to create an MPLS TP was that it should fit into the
----- Original Message ----- From: "Stewart Bryant" <email@example.com>
To: "Shahram Davari" <firstname.lastname@example.org>
Cc: "'ccamp'" <email@example.com>; <firstname.lastname@example.org>; "'pwe3'"
Sent: Friday, May 09, 2008 9:52 PM
Subject: Re: [PWE3] [mpls] proposed charter update for the MPLS TP work
I think it was fine as it was. We are not going to do and unnecessary
extensions, and we are not going to remove any functionality that is
already in there because we need it for other applications.
We could perhaps say:
"Include necessary extensions ...." to make it completely clear.
Shahram Davari wrote:
Just a clarification. The term reduction means components of the MPLS
architecture left unused.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of
Sent: May-09-08 2:52 PM
To: 'Loa Andersson'; 'ccamp'; email@example.com; 'pwe3'
Subject: Re: [mpls] proposed charter update for the MPLS TP work
The term "extension" is not very appropriate. It doesn't cover the
case of MPLS TP requiring a reduction in MPLS functionality?
How about changing that to "extensions and reductions"
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf
Sent: May-09-08 6:57 AM
To: ccamp; firstname.lastname@example.org; pwe3
Subject: [mpls] proposed charter update for the MPLS TP work
MPLS, CCAMP and PWE3 working groups,
The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.
The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:
"- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
on the MPLS TP needs to be coordinated between the three working
groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.
Adrian, Deborah, Danny, Stewart, George and Loa
pwe3 mailing list
Principal Networking Architect
Acreo AB phone: +46 8 632 77 14
Isafjordsgatan 22 mobile: +46 739 81 21 64
Kista, Sweden email: email@example.com