Re: [Isis-wg] draft-ginsberg-isis-prefix-attributes & draft-ietf-isis-segment-routing-extensions

<stephane.litkowski@orange.com> Mon, 20 April 2015 15:15 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 C1A421B2EBF for <isis-wg@ietfa.amsl.com>; Mon, 20 Apr 2015 08:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 yXlHZrrjg_Mk for <isis-wg@ietfa.amsl.com>; Mon, 20 Apr 2015 08:15:11 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 911A41B2EBD for <isis-wg@ietf.org>; Mon, 20 Apr 2015 08:15:11 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 0B3BF2DC231; Mon, 20 Apr 2015 17:15:10 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id E0B7F27C071; Mon, 20 Apr 2015 17:15:09 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Mon, 20 Apr 2015 17:15:09 +0200
From: <stephane.litkowski@orange.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "isis-wg@ietf.org list (isis-wg@ietf.org)" <isis-wg@ietf.org>
Thread-Topic: draft-ginsberg-isis-prefix-attributes & draft-ietf-isis-segment-routing-extensions
Thread-Index: AdB7eZRWVBiAPkUSTViDyaxVyA+rAQAARjeAAAB+o4A=
Date: Mon, 20 Apr 2015 15:15:09 +0000
Message-ID: <13519_1429542909_553517FD_13519_19642_1_9E32478DFA9976438E7A22F69B08FF921663B516@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <30846_1429541884_553513FC_30846_16396_1_9E32478DFA9976438E7A22F69B08FF921663B4C0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F57466B29@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F57466B29@xmb-aln-x02.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.20.90620
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/uqnd3l0hc-PqYFInnorjTnlFbnk>
Subject: Re: [Isis-wg] draft-ginsberg-isis-prefix-attributes & draft-ietf-isis-segment-routing-extensions
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: Mon, 20 Apr 2015 15:15:13 -0000

> We have stated publicly that the plan is to deprecate the N flag in the prefix-SID sub-TLV

Great, I missed this ... .

Thanks for the info.

-----Original Message-----
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com] 
Sent: Monday, April 20, 2015 17:05
To: LITKOWSKI Stephane SCE/IBNF; isis-wg@ietf.org
Subject: RE: draft-ginsberg-isis-prefix-attributes & draft-ietf-isis-segment-routing-extensions

Stephane -

We have stated publicly that the plan is to deprecate the N flag in the prefix-SID sub-TLV. The only issue is timing as we have early deployments of SR. So we need to:

1)Get prefix-attributes as a WG document 2)Get early allocation of codepoints for prefix-attributes so folks can implement it 3)Allow a transition period for early SR deployments to add prefix-attributes support 4)Deprecate the redundant flag in SR

During the transition implementations will send both flags and accept either one.

We won't reuse the flag in SR until we are certain there are no legacy deployments. (A long time...)

   Les


> -----Original Message-----
> From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of 
> stephane.litkowski@orange.com
> Sent: Monday, April 20, 2015 7:58 AM
> To: isis-wg@ietf.org
> Subject: [Isis-wg] draft-ginsberg-isis-prefix-attributes & 
> draft-ietf-isis- segment-routing-extensions
> 
> Hi,
> 
> Introducing the IPv4/IPv6 extended reachability attribute flags, we 
> are introducing some redundancy with some informations contained in 
> Prefix- SID SubTLV, especially the N-Flag representing that the prefix 
> belongs to the node itself.
> 
> I'm not sure this is a good idea to keep both flags or if we do, we 
> need to define the relationship between them (are they independent or 
> not ...)
> 
> N-Flag was introduced in Prefix SID SubTLV because the information was 
> not existing at this time.
> Now we defined new attributes for the prefix containing this 
> information, so the PrefixSID information is redundant and not useful anymore.
> 
> For sure, we need to take care about backward compatibility as some SR 
> codes already used N-Flag in Prefix SID for FRR.
> 
> Thoughts ?
> 
> 
> Best Regards,
> 
> Stephane
> 
> 
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> 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.