Return-Path: 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 7FD6A1B2E2A for ; Mon, 20 Apr 2015 07:58:07 -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 ADt0MJy69kjb for ; Mon, 20 Apr 2015 07:58:06 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22BAC1B2E26 for ; Mon, 20 Apr 2015 07:58:06 -0700 (PDT) Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id F2EF5C0216 for ; Mon, 20 Apr 2015 16:58:04 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.72]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id D6E71C8081 for ; Mon, 20 Apr 2015 16:58:04 +0200 (CEST) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541%19]) with mapi id 14.03.0224.002; Mon, 20 Apr 2015 16:58:04 +0200 From: To: "isis-wg@ietf.org" Thread-Topic: draft-ginsberg-isis-prefix-attributes & draft-ietf-isis-segment-routing-extensions Thread-Index: AdB7eZRWVBiAPkUSTViDyaxVyA+rAQ== Date: Mon, 20 Apr 2015 14:58:03 +0000 Message-ID: <30846_1429541884_553513FC_30846_16396_1_9E32478DFA9976438E7A22F69B08FF921663B4C0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> 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.142418 Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 14:58:07 -0000 Hi, Introducing the IPv4/IPv6 extended reachability attribute flags, we are int= roducing some redundancy with some informations contained in Prefix-SID Sub= TLV, 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.=20 Now we defined new attributes for the prefix containing this information, s= o the PrefixSID information is redundant and not useful anymore. For sure, we need to take care about backward compatibility as some SR code= s already used N-Flag in Prefix SID for FRR. Thoughts ? Best Regards, Stephane ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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.