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

<stephane.litkowski@orange.com> Fri, 06 June 2014 07:38 UTC

Return-Path: <stephane.litkowski@orange.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 410001A03D8; Fri, 6 Jun 2014 00:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 vOueRuispIt5; Fri, 6 Jun 2014 00:38:13 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C34B11A0376; Fri, 6 Jun 2014 00:38:12 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id B54961903A1; Fri, 6 Jun 2014 09:38:04 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 92B7EC8056; Fri, 6 Jun 2014 09:38:04 +0200 (CEST)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.19]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0181.006; Fri, 6 Jun 2014 09:38:04 +0200
From: <stephane.litkowski@orange.com>
To: Hannes Gredler <hannes@juniper.net>
Thread-Topic: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00
Thread-Index: Ac9z2gorbAmJYe4UTpeoTQ6gc4g+PgIyyZiAAKATQMAAWzLIgAAxLZrTAACtKBA=
Date: Fri, 6 Jun 2014 07:38:04 +0000
Message-ID: <1356_1402040284_53916FDC_1356_5092_1_9E32478DFA9976438E7A22F69B08FF9201DFAF@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0827D488@NKGEML512-MBS.china.huawei.com> <9818_1401797825_538DBCC1_9818_12387_1_9E32478DFA9976438E7A22F69B08FF920133A5@OPEXCLILM34.corporate.adroot.infra.ftgroup> <CD0A9624-12C3-4413-AFD5-C0CF25071FF4@juniper.net> <21360_1401975245_539071CD_21360_4036_1_9E32478DFA9976438E7A22F69B08FF9201DD93@OPEXCLILM34.corporate.adroot.infra.ftgroup> <EDEF5D14-B78D-4F31-BE01-D3336D1E39A0@juniper.net>
In-Reply-To: <EDEF5D14-B78D-4F31-BE01-D3336D1E39A0@juniper.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.6.5.221820
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/UKWWWDZixCBdzdiLxVupQUFRpko
Cc: "<spring@ietf.org>" <spring@ietf.org>, "draft-xu-isis-mpls-elc@tools.ietf.org" <draft-xu-isis-mpls-elc@tools.ietf.org>, "isis-chairs@tools.ietf.org" <isis-chairs@tools.ietf.org>, "isis-wg@ietf.org list" <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: Fri, 06 Jun 2014 07:38:15 -0000

You are right, I think EL processing in SPRING is mainly an implementor discussion about what is possible to do, what's the impact on legacy HWs ...

Some HW may also never be able to look at EL if it's 7 or 8 labels after the top one ... and FAT PW solution (FAT label at bottom of stack) may not work anymore. 


-----Original Message-----
From: Hannes Gredler [mailto:hannes@juniper.net] 
Sent: Friday, June 06, 2014 09:15
To: LITKOWSKI Stephane SCE/IBNF
Cc: Xuxiaohu; isis-chairs@tools.ietf.org; draft-xu-isis-mpls-elc@tools.ietf.org; isis-wg@ietf.org list; <spring@ietf.org>
Subject: Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00

valid point - i am not terribly happy with the EL behind the top label as it may require new data plane capabilities (you need to retain the EL label while the SR stack gets POPed off). - not sure if all existing MPLS HW does support that.

/hannes 

On Jun 5, 2014, at 3:34 PM, <stephane.litkowski@orange.com> wrote:

> Hi Hannes,
> 
> I agree with you but if draft-kini-mpls-spring-entropy-label evolve to the option where entropy label is always behind top label, there is no need to encode such granularity.
> That's why I think it's too early to progress the capability document.
> 
> Thoughts ?
> 
> Stephane
> 
> -----Original Message-----
> From: Hannes Gredler [mailto:hannes@juniper.net]
> Sent: Thursday, June 05, 2014 11:47
> To: Xuxiaohu
> Cc: isis-chairs@tools.ietf.org; draft-xu-isis-mpls-elc@tools.ietf.org; 
> isis-wg@ietf.org list; LITKOWSKI Stephane SCE/IBNF; <spring@ietf.org>
> Subject: Re: [Isis-wg] Request for WG adoption of 
> draft-xu-isis-mpls-elc-00
> 
> <IS-IS WG chair hat off>
> 
> i'm discomfortable with the *granularity* of the cap-advertisement:
> 
> rather than saying:
> 
> "i can crawl as deep as you like on any of my interfaces"
> 
>  i'd like to announce:
> 
> "i can crawl for EL <N> up to labels deep on interface XYZ"
> 
> 
> /hannes
> 
> On Jun 3, 2014, at 2:17 PM, <stephane.litkowski@orange.com> <stephane.litkowski@orange.com> wrote:
> 
>> Hi,
>> 
>> IMHO, before defining the capability, I would be more interrested on seeing some progress on a solution for EL over SPRING. A draft exists with multiple options, maybe we should wait for one option to have consensus before worrying about ELC encoding (quite easy part of the EL for SPRING).
>> 
>> 
>> Stephane
>> 
>> -----Message d'origine-----
>> De : Isis-wg [mailto:isis-wg-bounces@ietf.org] De la part de Xuxiaohu 
>> Envoyé : samedi 31 mai 2014 10:05 À : isis-chairs@tools.ietf.org Cc :
>> draft-xu-isis-mpls-elc@tools.ietf.org; isis-wg@ietf.org Objet : 
>> [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00
>> 
>> Hi WG co-chairs,
>> 
>> This draft (http://tools.ietf.org/html/draft-xu-isis-mpls-elc-00) describes how to advertise the MPLS Entropy Label Capability (ELC) using IS-IS in SPRING networks. Since (http://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-00) has been adopted as a WG draft, as co-authors of draft-xu-isis-mpls-elc-00, we hope you could consider the WG adoption for this draft as well.
>> 
>> Best regards,
>> Xiaohu (on behalf of all-authors)
>> 
>> _______________________________________________
>> Isis-wg mailing list
>> Isis-wg@ietf.org
>> https://www.ietf.org/mailman/listinfo/isis-wg
>> 
>> _____________________________________________________________________
>> _ ___________________________________________________
>> 
>> Ce message et ses pieces jointes peuvent contenir des informations 
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
>> exploites ou copies sans autorisation. Si vous avez recu ce message 
>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>> 
>> This message and its attachments may contain confidential or 
>> privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>> 
>> _______________________________________________
>> Isis-wg mailing list
>> Isis-wg@ietf.org
>> https://www.ietf.org/mailman/listinfo/isis-wg
> 
> 
> ______________________________________________________________________
> ___________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
> exploites ou copies sans autorisation. Si vous avez recu ce message 
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.