Re: [Idr] Solicit feedbacks on draft-dong-idr-end-of-rib-use-extension

Jie Dong <jie.dong@huawei.com> Wed, 10 August 2011 06:45 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3409A21F84F6 for <idr@ietfa.amsl.com>; Tue, 9 Aug 2011 23:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level:
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8na5JhbB4Z28 for <idr@ietfa.amsl.com>; Tue, 9 Aug 2011 23:45:44 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7979821F84F3 for <idr@ietf.org>; Tue, 9 Aug 2011 23:45:44 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LPP0098X9EFP5@szxga05-in.huawei.com> for idr@ietf.org; Wed, 10 Aug 2011 14:44:40 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LPP0098A9EFOH@szxga05-in.huawei.com> for idr@ietf.org; Wed, 10 Aug 2011 14:44:39 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ADC19675; Wed, 10 Aug 2011 14:44:39 +0800 (CST)
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 10 Aug 2011 14:44:35 +0800
Received: from SZXEML509-MBS.china.huawei.com ([169.254.2.156]) by szxeml403-hub.china.huawei.com ([169.254.173.75]) with mapi id 14.01.0270.001; Wed, 10 Aug 2011 14:44:38 +0800
Date: Wed, 10 Aug 2011 06:44:37 +0000
From: Jie Dong <jie.dong@huawei.com>
In-reply-to: <4E422113.708@cisco.com>
X-Originating-IP: [10.110.98.148]
To: "raszuk@cisco.com" <raszuk@cisco.com>, "idr@ietf.org" <idr@ietf.org>
Message-id: <76CD132C3ADEF848BD84D028D243C9270B76B887@szxeml509-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: en-US, zh-CN
Thread-topic: [Idr] Solicit feedbacks on draft-dong-idr-end-of-rib-use-extension
Thread-index: AcxWaIOGlX/cLil9Quelmj6EiTtLxwAeMdOAABFwLdA=
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <76CD132C3ADEF848BD84D028D243C9270B76B48C@szxeml509-mbs.china.huawei.com> <4E422113.708@cisco.com>
Subject: Re: [Idr] Solicit feedbacks on draft-dong-idr-end-of-rib-use-extension
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 06:45:45 -0000

Hi Robert, 

> As we have discussed already offline I also do not see a need for new
> spec to define EoR capability as a separate document.

Got your opinion on this, thanks.

> Text clarification of re-spined RFC4724 (with possible addition of new
> flag) would be in my opinion sufficient to address any potential doubts
> one could have reg explicit helper behaviour signaling when sending GR
> capability with null set of AFI/SAFIs.

If you choose to re-spin RFC4724, adding new flags would definitely be needed, which is more than "text clarification". And remember this would be for negotiating features "outside" GR. Not sure if this sounds reasonable. 

> I am of the opinion that it is always much better to focus on one clear
> specification rather then define the same functionality in multiple and
> independent documents.

Correct if they are exactly the same functionality:) Please note that LDP End-of-LIB and LDP GR are not the same functionality and are defined in separate documents.

Best regards,
Jie

> 
> > Dear all,
> >
> > Internet-Draft draft-dong-idr-end-of-rib-use-extension was submitted
> > before Quebec IETF. The url is:
> > http://tools.ietf.org/html/draft-dong-idr-end-of-rib-use-extension-00
> >
> >  Since BGP End-of-Rib (EoR) would be useful for general BGP
> > convergence, this draft proposes to define a EoR capability to
> > negotiate the use of EoR between BGP peers. This makes EoR an
> > independent feature and could be used without supporting or enabling
> > GR capability. As according to BGP GR (RFC4724), BGP peers can only
> > negotiate the combination of EoR and GR capability.
> >
> > We've received some offline comments, one of which suggested an
> > alternative solution: respin GR specification and cover this
> > scenario: negotiate only EoR, no GR.
> >
> > Thus we would have two alternatives here: either we define a simple
> > and dedicated capability for EoR, or we respin BGP GR with some
> > further capability negotiation functionality to cover this case.
> >
> > We would like to solicit feedbacks and opinions on this draft and
> > also the alternatives.
> >
> > Many thanks, Jie
> _______________________________________________ Idr
> > mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
> >