Re: [mpls] [Idr] Working Group adoption call for draft-decraene-idr-next-hop-capability-03

<bruno.decraene@orange.com> Mon, 12 June 2017 10:04 UTC

Return-Path: <bruno.decraene@orange.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 ACFBA126CD8; Mon, 12 Jun 2017 03:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 WoenlpLVcFC0; Mon, 12 Jun 2017 03:04:05 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFC791294F7; Mon, 12 Jun 2017 03:04:03 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id EB0BC18033F; Mon, 12 Jun 2017 12:04:01 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id BC12E1A0059; Mon, 12 Jun 2017 12:04:01 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%18]) with mapi id 14.03.0339.000; Mon, 12 Jun 2017 12:04:01 +0200
From: <bruno.decraene@orange.com>
To: Keyur Patel <keyur@arrcus.com>, idr wg <idr@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "draft-decraene-idr-next-hop-capability@ietf.org" <draft-decraene-idr-next-hop-capability@ietf.org>, John G.Scudder <jgs@juniper.net>
Thread-Topic: [Idr] Working Group adoption call for draft-decraene-idr-next-hop-capability-03
Thread-Index: AQHS0QIJYQaYgmju5kW1w24bFzBjqKIhBZaw
Date: Mon, 12 Jun 2017 10:04:01 +0000
Message-ID: <13271_1497261841_593E6711_13271_395_1_53C29892C857584299CBF5D05346208A4777B42F@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <921E0107-5131-42CC-9EFC-E9A914D9C2FB@arrcus.com>
In-Reply-To: <921E0107-5131-42CC-9EFC-E9A914D9C2FB@arrcus.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/w4l0-LoE3F5_d430gDvzfhcy9ZM>
Subject: Re: [mpls] [Idr] Working Group adoption call for draft-decraene-idr-next-hop-capability-03
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 12 Jun 2017 10:04:08 -0000

Hi Keyur,

 > From: Keyur Patel [mailto:keyur@arrcus.com]  > Sent: Saturday, May 20, 2017 2:43 AM
> 
 > Support. However, It would be great if the attribute format adopts new attribute definition
 > of : https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-attribute-announcement/
 > 
 > This will help scope the attribute announcements.

Thanks for the support.

TL;DR: Interesting comment regarding draft-ietf-idr-bgp-attribute-announcement. But I feel that the comment is more related to draft-ietf-idr-bgp-attribute-announcement, and how we(IDR) can make it real.


A priori, to enforce the use of draft-ietf-idr-bgp-attribute-announcement for future BGP attributes, we need an RFC. But to get that RFC, IDR requests 2 implementations. Hence there is a need to implement it on a first attribute. 3 options:

a) pick a draft / attribute more or less randomly.
Pro: easy path for  -bgp-attribute-announcement
Con: typical reaction for the choose draft may be "why me?", "not in my backyard"

As a matter of fact ;-) I don't feel that draft-decraene-idr-next-hop-capability is the best choice given that the next-hop attribute is removed when the next-hop is changed, so typically will already not leave an AS/administrative domain. So there is less need for filtering capability on AS border. Plus bgp-attribute-announcement provides filtering capability on an attribute basis, why -next-hop-capability would better benefit from filtering on a capability basis.

May be the iOTC attribute would be a better fit, especially since it already needs to implement filtering on AS boundaries and may benefit from enhanced filtering capabilities. 

b) pick a dedicated attribute code, just to implement the general behavior.
Could even be a deprecated code point given that it won't be used in deployment.
Con: difficult to fund the implementation since the benefit is null in the short term.

c) split bgp-attribute-announcement into 2 drafts/phases:
- phase 1: define the new Extended Path Attribute Flags field (i.e. 4 null octets). With no flag  defined
- phase 2: defines the new flags.

Pro:
Phase 1 is very easy to implement for any new attribute. Hence high chance to get implementation --> RFC --> mandate this new format. Speaking for myself, I'm open to add this phase 1 in next-hop-capability (once this phase1 document is written, accepted as WG doc, preferably WGLC)
Phase 2 has more incentive to get implemented since the flags would be applicable to multiple attributes i.e. the benefit would be multiplied by N.

Best regards,
-- Bruno

 
 > Regards,
 > Keyur
 > 
 > On 5/19/17, 7:35 AM, "Idr on behalf of bruno.decraene@orange.com"; <idr-
 > bounces@ietf.org on behalf of bruno.decraene@orange.com>; wrote:
 > 
 >     Support as coauthor
 > 
 >      > -----Original Message-----
 >      > From: John G.Scudder [mailto:jgs@juniper.net]
 >      > Sent: Thursday, May 18, 2017 6:35 PM
 >      > To: idr wg
 >      > Cc: draft-decraene-idr-next-hop-capability@ietf.org; mpls@ietf.org
 >      > Subject: Working Group adoption call for draft-decraene-idr-next-hop-capability-03
 >      >
 >      > [resending, correcting draft@ietf address]
 >      >
 >      > Hi All,
 >      >
 >      > IDR working group adoption has been requested for draft-decraene-idr-next-hop-
 >      > capability-03. Please send your comments to the IDR mailing list before June 2, 2017.
 > Please
 >      > remember that we need affirmative support in order to adopt the draft, so don't be
 > shy.
 >      >
 >      > draft datatracker page: https://datatracker.ietf.org/doc/draft-decraene-idr-next-hop-
 >      > capability/
 >      > slides from IETF-98: https://www.ietf.org/proceedings/98/slides/slides-98-idr-08-bgp-
 > next-
 >      > hop-dependent-capabilities-00.pdf
 >      >
 >      > Since in part this draft specifies a replacement for the Entropy Label Capability
 > Attribute
 >      > (ELCA) that was defined by the MPLS WG in RFC 6790 and deprecated by RFC 7447, I
 > have
 >      > cc'd the MPLS WG mailing list. Since the proposed new attribute is a generic container
 > with
 >      > the ELCA replacement just the first application, the current draft is targeted to IDR and
 > not
 >      > MPLS (this was discussed during IETF-93).
 >      >
 >      > Thanks,
 >      >
 >      > --John
 > 
 > 
 > ______________________________________________________________________
 > ___________________________________________________
 > 
 >     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.
 > 
 >     _______________________________________________
 >     Idr mailing list
 >     Idr@ietf.org
 >     https://www.ietf.org/mailman/listinfo/idr
 > 


_________________________________________________________________________________________________________________________

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.