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

"Shahram Davari" <davari@broadcom.com> Wed, 24 March 2010 16:20 UTC

Return-Path: <davari@broadcom.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 A86A63A68C4; Wed, 24 Mar 2010 09:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level:
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 GVSDpjP1KEQM; Wed, 24 Mar 2010 09:20:35 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id EE5463A6847; Wed, 24 Mar 2010 09:20:33 -0700 (PDT)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 24 Mar 2010 09:20:46 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Wed, 24 Mar 2010 09:20:46 -0700
From: Shahram Davari <davari@broadcom.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Wed, 24 Mar 2010 09:20:44 -0700
Thread-Topic: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrBczT1LsEVDiSwTX2v9QSMrvpjyAAA7NaQAn1wnhA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD68171AE66FD@SJEXCHCCR02.corp.ad.broadcom.com>
References: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu> <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67B4E45720S68308113-01-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Wed, 24 Mar 2010 16:20:36 -0000

Hi

In addition to the previous comments that I have raised I like to also raise the following comments:

7) I think it is too early for this draft (just with 1 version) to become RFC. This draft affects many IETF WGs and drafts and is really putting stakes on the ground before the requirements are finalized for other drafts. 

8) I am concerned about not having a commonly agreed identifier for objects in this draft and in most cases defining an IETF identifier and an ITU identifier. That would make the interoperability a nightmare.

Thanks,
Shahram

  

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Shahram Davari
Sent: Thursday, March 11, 2010 4:28 PM
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,

Couple of comments:

1) Why the Interface_ID is 32-bit while the Tunnel_ID is 16-bit? Do we need to support more interfaces than tunnels? 
2) The draft defines the Global_Tunnel_ID as:
      Src-Global_ID::Src-Node_ID::Src-Tunnel_Num:: Dst-Global_ID::Dst-Node_ID::Dst-Tunnel_Num

This seems to define a bidirectional tunnel. Is that the intent? If so please clarify. If not then why Dst-Global_ID::Dst-Node_ID::Dst-Tunnel_Num is needed?

3) Is section 5.2 talking about unidirectional LSP or bidirectional LSP?
4) Section 7.1.2.1 says:
	Since a MEG pertains to a single MPLS-TP Tunnel, IP compatible MEG_IDs for MPLS-TP Tunnels are simply the corresponding Tunnel_IDs

Assuming the Tunnel_ID is a unidirectional ID, then this statement implies that for the reverse direction a different MEG_ID is required. Is that the intent? If so why?

5) Why are drafts part of the normative references?

6) Will section 8 (open issues) be removed before publishing? This section implies that the MEP and MIP definition is not yet aligned with framework?

Regards,
Shahram



-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Thursday, March 11, 2010 3:33 PM
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