[mpls] Comments on draft-ravisingh-mpls-el-for-seamless-mpls

"Nobo Akiya (nobo)" <nobo@cisco.com> Thu, 07 November 2013 08:23 UTC

Return-Path: <nobo@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B383321E80D1 for <mpls@ietfa.amsl.com>; Thu, 7 Nov 2013 00:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VBNJpFvxOtD7 for <mpls@ietfa.amsl.com>; Thu, 7 Nov 2013 00:23:00 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 2350D21E80B8 for <mpls@ietf.org>; Thu, 7 Nov 2013 00:23:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=864; q=dns/txt; s=iport; t=1383812580; x=1385022180; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=fNVungvaM+yzqfT5CROWpPiqZpUzUPqBAjAOMPwz5Xo=; b=OI4xdYa15ZUEvZEEU4l7PWGeeXvKVeiESD2VmBtQYULk/TMPfqcfrHoz KweqcgXrDqcaWe83cYax1hJ91lpYMY76SZYVxUeyijcqJKHbGPx+jzrBC 4Oo34OAfYAM2ALrzGKhD141koCnMKQ4nZKWaVmY/fA4i38gHkq7+KymEM E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsUGAHxNe1KtJXG8/2dsb2JhbABZgmYhgQu/DYEjFm0HgiUBAQEDATo/BQ0BKhRCJgEEDg2HcwYBvXmPKDGDJ4EQA6oWgyaCKg
X-IronPort-AV: E=Sophos;i="4.93,650,1378857600"; d="scan'208";a="281776934"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 07 Nov 2013 08:22:59 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA78Mx0E019002 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 08:22:59 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 02:22:59 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "draft-ravisingh-mpls-el-for-seamless-mpls@tools.ietf.org" <draft-ravisingh-mpls-el-for-seamless-mpls@tools.ietf.org>
Thread-Topic: Comments on draft-ravisingh-mpls-el-for-seamless-mpls
Thread-Index: Ac7bkJ2xL0omkkvnRZ2jAuXiLdjyFQ==
Date: Thu, 07 Nov 2013 08:22:58 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941DEDE3E0@xmb-aln-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.115.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] Comments on draft-ravisingh-mpls-el-for-seamless-mpls
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 07 Nov 2013 08:23:05 -0000

Hi Ravi, Yimin,

I have couple of comments.

1. Stitched LSP - Proposed really offers optimization in stitched scenario.

a. Allows EL usage for even wider than just EL capable segments.
b. Potentially speeds data traversal over stitched LSP as number of times ELI/EL popped/pushed are reduced.

Document sort of eludes to this, but I think it'll be beneficial to state that things will work as is (RFC6790), but proposal can be used as optimization.

2. Hierarchical LSP

>   B. Preventing multiple (ELI+EL) pairs underneath a given forwarding
>       label in the stack:

I highly support above statement. Having multiple ELs in the stack will, yet again, cause more changes required in LSP traceroute wrt multipath information handling, and requires even more complex computation by initiator to traverse ECMP paths.

-Nobo