Re: [mpls] [PWE3] proposed charter update for the MPLS TP work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mpls] [PWE3] proposed charter update for the MPLS TP work
Loa/Adrian/Stewart,
I think it would be really useful if someone could summarise what
specific proposals/options are being considered for MPLS-TP. In
particular, given:
- most operators would regard an OOB CP as an essential component
of a transport network (and this is a forced requirement in the co-cs
mode anyway);
- GMPLS already uses an OOB CP and there is a long-standing CCAMPs
charter item to unify the GMPLS/MPLS CPs;
- I believe re-using common CP techniques would also be of
interest to many operators;
then it would appear that the MPLS-TP initiative provides a very good
opportunity to address this.
Any comments?
regards, Neil
> -----Original Message-----
> From: owner-ccamp at ops.ietf.org
> [mailto:owner-ccamp at ops.ietf.org] On Behalf Of Loa Andersson
> Sent: 12 May 2008 08:34
> To: Adrian Farrel
> Cc: stbryant at cisco.com; Shahram Davari; 'ccamp'; mpls at ietf.org; 'pwe3'
> Subject: Re: [PWE3] [mpls] proposed charter update for the
> MPLS TP work
>
>
> All,
>
>
>
> Adrian Farrel wrote:
> > Hi,
> >
> > Perhaps...
> > OLD
> > Include extensions to the [MPLS, PWE3, CCAMP] protocols
> > NEW
> > 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", thaFrom mpls-bounces at ietf.org Mon May 12 04:57:54 2008
Return-Path: <mpls-bounces at ietf.org>
X-Original-To: mpls-archive at megatron.ietf.org
Delivered-To: ietfarch-mpls-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 6134628C22A;
Mon, 12 May 2008 04:57:54 -0700 (PDT)
X-Original-To: mpls at core3.amsl.com
Delivered-To: mpls at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id DD0C03A6906;
Mon, 12 May 2008 04:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id WkEVTuev5g27; Mon, 12 May 2008 04:57:50 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
by core3.amsl.com (Postfix) with ESMTP id 6A9D33A6863;
Mon, 12 May 2008 04:57:50 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.109]) by
smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 12 May 2008 12:56:49 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 May 2008 12:55:50 +0100
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C02653B26 at E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <4827F2D3.7030609 at pi.nu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] [mpls] proposed charter update for the MPLS TP work
Thread-Index: Aci0AvvVV4jxuwRrSG6pvaXj9JFLbwAI4tuQ
From: <neil.2.harrison at bt.com>
To: <loa at pi.nu>,
<adrian at olddog.co.uk>,
<stbryant at cisco.com>
X-OriginalArrivalTime: 12 May 2008 11:56:49.0284 (UTC)
FILETIME=[4285AC40:01C8B427]
Cc: davari at ieee.org, ccamp at ops.ietf.org, pwe3 at ietf.org, mpls at ietf.org
Subject: Re: [mpls] [PWE3] proposed charter update for the MPLS TP work
X-BeenThere: mpls at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
<mailto:mpls-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls at ietf.org>
List-Help: <mailto:mpls-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
<mailto:mpls-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces at ietf.org
Errors-To: mpls-bounces at ietf.org
Loa/Adrian/Stewart,
I think it would be really useful if someone could summarise what
specific proposals/options are being considered for MPLS-TP. In
particular, given:
- most operators would regard an OOB CP as an essential component
of a transport network (and this is a forced requirement in the co-cs
mode anyway);
- GMPLS already uses an OOB CP and there is a long-standing CCAMPs
charter item to unify the GMPLS/MPLS CPs;
- I believe re-using common CP techniques would also be of
interest to many operators;
then it would appear that the MPLS-TP initiative provides a very good
opportunity to address this.
Any comments?
regards, Neil
> -----Original Message-----
> From: owner-ccamp at ops.ietf.org
> [mailto:owner-ccamp at ops.ietf.org] On Behalf Of Loa Andersson
> Sent: 12 May 2008 08:34
> To: Adrian Farrel
> Cc: stbryant at cisco.com; Shahram Davari; 'ccamp'; mpls at ietf.org; 'pwe3'
> Subject: Re: [PWE3] [mpls] proposed charter update for the
> MPLS TP work
>
>
> All,
>
>
>
> Adrian Farrel wrote:
> > Hi,
> >
> > Perhaps...
> > OLD
> > Include extensions to the [MPLS, PWE3, CCAMP] protocols
> > NEW
> > 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 t 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 MPLS architecture.
>
> /Loa
> >
> > Adrian
> >
> > ----- Original Message ----- From: "Stewart Bryant"
> > <stbryant at cisco.com>
> > To: "Shahram Davari" <davari at ieee.org>
> > Cc: "'ccamp'" <ccamp at ops.ietf.org>; <mpls at ietf.org>; "'pwe3'"
> > <pwe3 at ietf.org>
> > 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.
> >>
> >> Stewart
> >>
> >> Shahram Davari wrote:
> >>> Hi Loa,
> >>>
> >>> Just a clarification. The term reduction means components of the
> >>> MPLS architecture left unused.
> >>>
> >>> Regards,
> >>> Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces at ietf.org
> [mailto:mpls-bounces at ietf.org] On Behalf
> >>> Of Shahram Davari
> >>> Sent: May-09-08 2:52 PM
> >>> To: 'Loa Andersson'; 'ccamp'; mpls at ietf.org; 'pwe3'
> >>> Subject: Re: [mpls] proposed charter update for the MPLS TP work
> >>>
> >>> Hi Loa,
> >>>
> >>> The term "extension" is not very appropriate. It doesn't cover the
> >>> possible
> >>> case of MPLS TP requiring a reduction in MPLS functionality?
> >>>
> >>> How about changing that to "extensions and reductions"
> >>>
> >>> Regards,
> >>> -Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces at ietf.org
> [mailto:mpls-bounces at ietf.org] On Behalf
> >>> Of Loa
> >>> Andersson
> >>> Sent: May-09-08 6:57 AM
> >>> To: ccamp; mpls at ietf.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
> >>> work."
> >>>
> >>> 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
> >> pwe3 at ietf.org
> >> https://www.ietf.org/mailman/listinfo/pwe3
> >>
> >
> >
> >
>
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB phone: +46 8 632 77 14
> Isafjordsgatan 22 mobile: +46 739 81 21 64
> Kista, Sweden email: loa.andersson at acreo.se
> loa at pi.nu
>
>
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls
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 MPLS architecture.
>
> /Loa
> >
> > Adrian
> >
> > ----- Original Message ----- From: "Stewart Bryant"
> > <stbryant at cisco.com>
> > To: "Shahram Davari" <davari at ieee.org>
> > Cc: "'ccamp'" <ccamp at ops.ietf.org>; <mpls at ietf.org>; "'pwe3'"
> > <pwe3 at ietf.org>
> > 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.
> >>
> >> Stewart
> >>
> >> Shahram Davari wrote:
> >>> Hi Loa,
> >>>
> >>> Just a clarification. The term reduction means components of the
> >>> MPLS architecture left unused.
> >>>
> >>> Regards,
> >>> Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces at ietf.org
> [mailto:mpls-bounces at ietf.org] On Behalf
> >>> Of Shahram Davari
> >>> Sent: May-09-08 2:52 PM
> >>> To: 'Loa Andersson'; 'ccamp'; mpls at ietf.org; 'pwe3'
> >>> Subject: Re: [mpls] proposed charter update for the MPLS TP work
> >>>
> >>> Hi Loa,
> >>>
> >>> The term "extension" is not very appropriate. It doesn't cover the
> >>> possible
> >>> case of MPLS TP requiring a reduction in MPLS functionality?
> >>>
> >>> How about changing that to "extensions and reductions"
> >>>
> >>> Regards,
> >>> -Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces at ietf.org
> [mailto:mpls-bounces at ietf.org] On Behalf
> >>> Of Loa
> >>> Andersson
> >>> Sent: May-09-08 6:57 AM
> >>> To: ccamp; mpls at ietf.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
> >>> work."
> >>>
> >>> 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
> >> pwe3 at ietf.org
> >> https://www.ietf.org/mailman/listinfo/pwe3
> >>
> >
> >
> >
>
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB phone: +46 8 632 77 14
> Isafjordsgatan 22 mobile: +46 739 81 21 64
> Kista, Sweden email: loa.andersson at acreo.se
> loa at pi.nu
>
>
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.
