Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00

Xuxiaohu <xuxiaohu@huawei.com> Thu, 05 June 2014 08:47 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA5B21A0102 for <isis-wg@ietfa.amsl.com>; Thu, 5 Jun 2014 01:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rIHYnGhcCq5 for <isis-wg@ietfa.amsl.com>; Thu, 5 Jun 2014 01:47:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E91551A0365 for <isis-wg@ietf.org>; Thu, 5 Jun 2014 01:47:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHW10560; Thu, 05 Jun 2014 08:46:54 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Jun 2014 09:45:57 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Jun 2014 09:46:47 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.62]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Thu, 5 Jun 2014 16:46:41 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Clarence Filsfils <cfilsfil@cisco.com>
Thread-Topic: Request for WG adoption of draft-xu-isis-mpls-elc-00
Thread-Index: Ac9z2gorbAmJYe4UTpeoTQ6gc4g+PgIyyZiAAKATQMAAGsmn0AALs7NwAAFqsOAACLdkoAAclDSQ///wAwD//3ROYA==
Date: Thu, 5 Jun 2014 08:46:41 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827E553@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827D488@NKGEML512-MBS.china.huawei.com> <9818_1401797825_538DBCC1_9818_12387_1_9E32478DFA9976438E7A22F69B08FF920133A5@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827DF1B@NKGEML512-MBS.china.huawei.com> <18316_1401864106_538EBFAA_18316_9423_1_9E32478DFA9976438E7A22F69B08FF92019077@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827E037@NKGEML512-MBS.china.huawei.com> <10697_1401881659_538F043B_10697_5233_1_9E32478DFA9976438E7A22F69B08FF9201B2F2@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827E408@NKGEML512-MBS.china.huawei.com> <53902588.7040803@cisco.com>
In-Reply-To: <53902588.7040803@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/afJ_8ylOVc6kShEJh1qe4QL8I4s
Cc: "isis-chairs@tools.ietf.org" <isis-chairs@tools.ietf.org>, "draft-xu-isis-mpls-elc@tools.ietf.org" <draft-xu-isis-mpls-elc@tools.ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 08:47:03 -0000

Hi Clarence,

> -----Original Message-----
> From: Clarence Filsfils [mailto:cfilsfil@cisco.com]
> Sent: Thursday, June 05, 2014 4:09 PM
> To: Xuxiaohu
> Cc: stephane.litkowski@orange.com; isis-chairs@tools.ietf.org;
> draft-xu-isis-mpls-elc@tools.ietf.org; isis-wg@ietf.org
> Subject: Re: Request for WG adoption of draft-xu-isis-mpls-elc-00
> 
> Xiaohu,
> 
> >> -----Original Message----- From: stephane.litkowski@orange.com
> >> [mailto:stephane.litkowski@orange.com] Sent: Wednesday, June 04,
> >> 2014 7:34 PM To: Xuxiaohu; isis-chairs@tools.ietf.org Cc:
> >> draft-xu-isis-mpls-elc@tools.ietf.org; isis-wg@ietf.org Subject:
> >> RE: Request for WG adoption of draft-xu-isis-mpls-elc-00
> >>
> >> Worst scenario (that I would not push for :) ) : What would you do
> >> with your capability if the conclusion is that EL insertion would not
> >> be supported for stacked tunnels because too complex ?
> >
> > I have to disagree with your assumption. At least for option 1 (i.e.,
> > inserting a single EL at the bottom of the LSP stack), do you believe
> > it's too complex? In addition, remember that one of the use cases of
> > SPRING is IGP-based MPLS Tunneling (see section 2 of
> > draft-filsfils-spring-segment-routing-use-cases-00).
> 
> What is the logical relationship?

Stephane had assumed the EL insertion for stacked tunnels (i.e., SPRING in this context) would be too complex. However, in the use case illustrated in section 2, the EL insertion for SPRING is no difference from that for today's LDP or RSVP-TE LSPs. 

Best regards,
Xiaohu  

> Cheers,
> Clarence