Re: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

"Diego Caviglia" <diego.caviglia@ericsson.com> Fri, 02 April 2010 06:58 UTC

Return-Path: <diego.caviglia@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B64B43A692E; Thu, 1 Apr 2010 23:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level:
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=3.177, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4]
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 bm8kszJm9Wo6; Thu, 1 Apr 2010 23:58:32 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 027A43A68DD; Thu, 1 Apr 2010 23:58:30 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-2b-4bb595b6f965
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 96.D3.23532.6B595BB4; Fri, 2 Apr 2010 08:59:02 +0200 (CEST)
Received: from esealmw110.eemea.ericsson.se ([153.88.200.78]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Apr 2010 08:58:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Apr 2010 08:58:01 +0200
Message-ID: <E0EB0F89D33F0B46A0C9A5B4293395F701FCCDA8@esealmw110.eemea.ericsson.se>
In-Reply-To: <79F41BA1E9BF3C489375521EF8DDE23C12B1B1A5BB@ESESSCMS0355.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrBczLI0hRemNw6QIizlAldPNT1mwQvaaOAAAAvpBA=
References: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu> <79F41BA1E9BF3C489375521EF8DDE23C12B1B1A5BB@ESESSCMS0355.eemea.ericsson.se>
From: Diego Caviglia <diego.caviglia@ericsson.com>
To: Attila Takacs <Attila.Takacs@ericsson.com>, Loa Andersson <loa@pi.nu>, mpls@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org, ccamp@ietf.org
X-OriginalArrivalTime: 02 Apr 2010 06:58:02.0837 (UTC) FILETIME=[D68E7050:01CAD231]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: mpls@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2010 06:58:32 -0000

Hi,
   Some more comments from me more ore less on the same route as Attila.

·         Section 1.1

o        PSC is also used as Packet Switching Capable for OSPF-TE 

·         Section 2

o        Tunnel I think that here a reference to the actual identifier of the quoted entity could help I mean a reference to Section 5

·         Section 4 

o        would be good to have a short explanation why numbered interfaces are not in the scope of MPLS-TP 

·         Section 5

o        Even if section 2 points to 3209 than the Tunnel Identifier chosen is different from what is defined in 3209, Extended Tunnel ID field is missing while there are two different Tunnel Num that is not clear how they works.  I think here the same convention used in 3209 and in GMPLS signaling would be good to avoid to have two or more Tunnel identifiers for MPLS-TP networks using GMPLS. 

o        Why MPLS-TP tunnels must be associated to a LIH?  Why MPLS-TP tunnels need to be configured as FA? Does that imply that in case OSPF-TE is used it must advertise MPLS-TP tunnels as FA each time a new tunnel is created?

·         Section 5.2 I think that sentence "The format of a Tunnel_ID is:" should be "The format of a LSP_ID is:" same for the globally unique case.

·         Section 5.3 addresses some of my above concern about usage of tunnel and lsp identifiers even if is not a 1:1 mapping given that the Dst-Tunnel_Num is not mapped in GMPLS Tunnel ID

·         Remaining of the docs is still WP
        

BR

Diego


 line



DIEGO CAVIGLIA 
Strategic Product Manager 


Ericsson Italy
Product Line PAIB
Via A. Negrone 1/A
Genoa, Italy
Phone +390106003736
Mobile +393357181762
diego.caviglia@ericsson.com
www.ericsson.com 



 Ericsson






This Communication is Confidential. We only send and receive email on the basis of the term set out at www.ericsson.com/email_disclaimer 


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Attila Takacs
Sent: venerdì 2 aprile 2010 8.54
To: Loa Andersson; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
Subject: Re: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

Hi Matthew and George,

Please find some comments/questions below.

-In Section 5.1 you have:

Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num

What is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_Num? 
Is it there to support associated unidirectional Tunnels/LSPs? If so it should be called out in the text. 

Same applies to the globally unique case.

-In Section 5.2 you simply append one LSP_Num to the above. This is a bit confusing to me, if there are Src/Dst Tunnel_Nums then two LSP_Nums would be needed too, wouldn't it?

-In Section 5.3 Mapping to GMPLS signaling does not use the Dst-Tunnel_Num. So this means that we may have two different tunnels identified with Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num. Is this intentional, e.g., the associated unidirectional case? This should be clarified.


Hmm, maybe the Dst-Tunnel_Num should be omitted altogether.


-Section 7 has a note saying to be aligned with the OAM fwk, is this still to be done?

-In section 7.1.2.1 there is a discussion on Tunnel MEG IDs.
How would Tunnel and LSP MEGs be used? What OAM would run at the Tunnel level and not at the LSP level?
Do we need Tunnel MEG_IDs as defined in 7.1.2.1?

-Section 7.1.2.2, the Dst-Tunnel_Num question applies here too.

-Section 8 talks about open issues? When will these be addressed?

Thanks,
Attila 

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: Friday, March 12, 2010 12:33 AM
> To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
> Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
> 
> All,
> 
> this is to start an MPLS working group last call on
> draft-ietf-mpls-tp-identifiers-01
> 
> There is a discussion on the OAM model for MS-PWs where we 
> haven't been able to come to conclusion. Once we reach 
> agreement the document will be updated. Comments in this area 
> are welcome during the working group last call.
> 
> 
> Please send your comments to the mpls-tp@ietf.org mailing list.
> 
> The working group last ends eob April 2nd.
> 
> /Loa
> 
> --
> 
> Loa Andersson
> 
> Sr Strategy and Standards Manager
> Ericsson ///
>    phone:  +46 10 717 52 13
>            +46 767 72 92 13
> 
>    email:  loa.andersson@ericsson.com
>            loa@pi.nu
> 
> 
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls