Re: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 07 January 2015 07:20 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5671A8971 for <idr@ietfa.amsl.com>; Tue, 6 Jan 2015 23:20:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gNKx7yYqtnoH for <idr@ietfa.amsl.com>; Tue, 6 Jan 2015 23:20:20 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24FE11A1A3D for <idr@ietf.org>; Tue, 6 Jan 2015 23:20:19 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNQ96350; Wed, 07 Jan 2015 07:20:17 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 Jan 2015 07:18:56 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.128]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 7 Jan 2015 15:18:49 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Thread-Topic: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02
Thread-Index: AdAbkULeZViW4uCIRLy+k1dsWqlgXgOLv8UQ//+aqAD//pCdUA==
Date: Wed, 7 Jan 2015 07:18:48 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927337F4503@nkgeml512-mbx.china.huawei.com>
References: <01c401d01b91$feca19d0$fc5e4d70$@ndzh.com> <2403_1420562329_54AC0F99_2403_19702_1_53C29892C857584299CBF5D05346208A0EAEDDFB@PEXCVZYM11.corporate.adroot.infra.ftgroup> <01c901d029d0$a53fc2a0$efbf47e0$@ndzh.com>
In-Reply-To: <01c901d029d0$a53fc2a0$efbf47e0$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.96.76]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927337F4503nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/SSouMsdupU8dMpjgzWn_ZM0sw8U
Cc: "idr@ietf.org" <idr@ietf.org>, "robert@raszuk.net" <robert@raszuk.net>
Subject: Re: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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, 07 Jan 2015 07:20:26 -0000

Hi Bruno, Sue,

Thanks for the discussion on this draft. Since now it is a WG document, we expect to have more discussions on this list about the choice of a suitable solution, and this is a good start:)

Personally, I'd also prefer the "best external" one, as it does not rely on the "add-path" capability, also does not add complexity in provisioning. The cost is to define new propagation rules for RTC AFI/SAFI. Note that the current propagation rule of RTC is already a little bit different from the BGP default rules.

As for the "add-path" solution, IMO this depends on the requirement of operators. If some of them plan to use add-path and RTC together, this can be one solution for them. "add-path all" can definitely meet the requirement, while we also want to check the possibility of advertising a subset of paths to solve this problem, for example, the "advertise N paths" mode in draft-ietf-idr-add-paths-guidelines.

Regarding the "standard track", we didn't expect protocol extensions with the "add-path" solution, but since the solution space is still open, it is likely that this document will include some protocol extensions.

Thanks again and we'd appreciate more discussions on this list.

Best regards,
Jie

From: Susan Hares [mailto:shares@ndzh.com]
Sent: Wednesday, January 07, 2015 12:49 AM
To: bruno.decraene@orange.com
Cc: robert@raszuk.net; idr@ietf.org; Dongjie (Jimmy)
Subject: RE: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02

Bruno:

The document has been accepted as a WG document.   I hope that people will engage you in debating the primary solution version the second solution.   I expect this evening Jie will respond to this email during his working hours (this evening).

I agree with many of your points regarding Add-path versus RTC approach.   One question should we allow two solutions - one for people already taking the heavy weight of add-path and another for the RTC.

AddPath grouping has entered the standard process, but I did not hold it for this work.  We can append a standard to the AddPath standard if operators need this feature.

Sue

From: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:bruno.decraene@orange.com]
Sent: Tuesday, January 06, 2015 11:39 AM
To: Susan Hares
Cc: robert@raszuk.net<mailto:robert@raszuk.net>; idr@ietf.org<mailto:idr@ietf.org>; Dongjie (Jimmy)
Subject: RE: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02

Hi Sue, John, all

I support WG adoption.

AFAIK, I don't have a use case for this (so personally I could live without) but the RTC  RFC has an issue and therefore, from and STD standpoint, IMO this at least needs to be documented.

Regarding the solution, I would a priori prefer the alternate solution (from Appendix A in v01 / the original solution proposed in v00; ala "Best External") rather than the solution currently proposed in v02 (ala "Add Path") for the following reasons:
- "Add Path" heavily depend on configuration to be done by the Service Provider. This add complexity to the provisioning system which would need to look at the iBGP client's configuration to see if it itself have an iBGP client session
- It looks to me that even the "Add Path" solution requires protocol extension (not crystal clear but the draft asks for STD track) and implementation change. So no specific advantage for "Add Path" on this point.
-The "Best External" solution is IMO more inlined with the current RTC spec/point of view which is to limit BGP states/path at the cost of a specific iBGP propagation rule. Looks more coherent to me and easier from an operational point to have all sessions within the AS behaving along  the same principles.

Specific comment:
- In §3.1 (add path solution)
"The number of RT-Constrain routes to be advertised is a local decision of operators. »
IMO "add path all" is needed, unless you define a new Add Path mode that you would need to specify.


Thanks,
Regards,
Bruno

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, December 19, 2014 2:45 PM
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: robert@raszuk.net<mailto:robert@raszuk.net>
Subject: [Idr] 1 Week Final Call for adoption of draft-dong-idr-rtc-hierarchical-rr-02


The IDR Chairs intend to adopt the draft-dong-idr-rtc-hierarchical-rr-02 as a WG draft.  This is a 1 week final call for comments on the adoption of this draft as WG draft.  The draft can be found at:

http://datatracker.ietf.org/doc/draft-dong-idr-rtc-hierarchical-rr/


Sue Hares and John Scudder



_________________________________________________________________________________________________________________________



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.