Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Fri, 29 July 2016 02:18 UTC

Return-Path: <jheitz@cisco.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 CE9C212D605 for <idr@ietfa.amsl.com>; Thu, 28 Jul 2016 19:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level:
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 izURVRnPGsaZ for <idr@ietfa.amsl.com>; Thu, 28 Jul 2016 19:18:18 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2AAD12D5B9 for <idr@ietf.org>; Thu, 28 Jul 2016 19:18:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8280; q=dns/txt; s=iport; t=1469758698; x=1470968298; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XgUmnT550slAZ6XAQFuRYwPOvMp5tJqL0XULBgHtzlw=; b=ctnMzJR35TuQvc1+MotNdzqFjaTi/JlDx9smTq+LrX5kRjC31H7A5N5X QrZ09CjIw6UdMjTGJjIJsHvN8Uk2GmMArjE81x36tM99zLJK6XMKIUcPH MmDKV4qrA0KEskQV2AG23URZ9A+eacw716ptOPeBhpi73zQasxdovHpBQ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DKAgD/u5pX/5NdJa1dgndOVnwGs3WFBYF9JoV3AhyBFjgUAQEBAQEBAV0nhF0BBSMKTBACAQg7BwICAjAlAgQBDQ2IKQ6uIY1vAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGKoRNgSKCeoMlgloFiQSKbIVCAY52j0aQJQEeNoJFgTVuAYZURX8BAQE
X-IronPort-AV: E=Sophos;i="5.28,437,1464652800"; d="scan'208,217";a="303895023"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jul 2016 02:18:17 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u6T2IHDR031475 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Jul 2016 02:18:17 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 28 Jul 2016 21:18:17 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Thu, 28 Jul 2016 21:18:17 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Robert Raszuk <robert@raszuk.net>, Tony Przygienda <tonysietf@gmail.com>
Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt
Thread-Index: AQHR4aVazIYBPV/cR0uGH7jm8G+9GqAgntcAgAABUACAAAdOAIAAAyuAgAF604CAABNLAIABJIAA//+uo+aAAFgkgIAABLuAgAEUfoCAA4DNAIAAdHiAgAADloCABkHiEA==
Date: Fri, 29 Jul 2016 02:18:17 +0000
Message-ID: <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com>
References: <CA+wi2hM+y_K+_50Q_QRS64VBdzgBWtx8hL-6iepsVqed+NtqTw@mail.gmail.com> <CA+b+ERm2AnRAYeJRDdsAh=hLX81aQUTVd7Pe5PYLpWmHNvbgtQ@mail.gmail.com> <CA+wi2hMsbVetW_D+HpsdXEHyh75yZkx+QTpj+FoX2hMTcqbrzw@mail.gmail.com> <CA+wi2hNk2+GLY0G800Uo8qgdZQWh=9AzFGhZTk+fWRd6isgriw@mail.gmail.com> <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <CA+b+ERnkkhYK7Cz5eG_8fuQ_cdeo3TSCK3sBQtA0SyfkGktwAg@mail.gmail.com> <D3B3F3D9.47283%keyupate@cisco.com> <CA+b+ERm+2HSu+QyU7pHsEXO9WKh9uavX2y4MtuSX=WADDYx_vg@mail.gmail.com> <D3B5343D.474BD%keyupate@cisco.com> <CA+b+ERn7Rb2=d7UFyxKC01dh7=JFpbnf+dd+_uL+UvAarnkE6w@mail.gmail.com> <CA+wi2hNjD+4Y3vfoDMXW2yzYiyv+9+Xhv=3ZTRumKkZcjY22Hg@mail.gmail.com> <CA+b+ER=_7P_Zg9GQYVT+RVMm9XB6H5o-r86axc0zyLnHf1f8fQ@mail.gmail.com> <CA+b+ERnr_9y9ta3VW99xbDbtRS=9jnNy9mtkk+h6MZ8r2Rj3AQ@mail.gmail.com> <CA+b+ERm39+UjahPJpQrGkAEGTguEQ_yQzNBoufR9wo7dOXDDbQ@mail.gmail.com> <CA+wi2hNMtzhkugis35ja_NbtvckaGSeb+QdFUyj1uMHq6oRWng@mail.gmail.com> <CA+b+ERkJwY8ucxR-FnWuoLMFE48CWE_5GbMwQRNX_3Und8jfsA@mail.gmail.com> <CA+wi2hOWCZjr78vic2O0crm_bSNww4HTJvdWjq0NfzdTpEEbpw@mail.gmail.com> <CA+b+ER=T-X0JYfvpGPcM4gs4y_HPRWwkLuktN9aO0jwUBybJFg@mail.gmail.com> <CA+wi2hPyhiGhMdnS3x_ZHFiy9dAFnx0mxCtRqr=rP6tu+aaePQ@mail.gmail.com> <CA+b+ERkT_zLQqd1B4295Z6Ezz0i+542SNouGBPXan=p15_PbRA@mail.gmail.com>
In-Reply-To: <CA+b+ERkT_zLQqd1B4295Z6Ezz0i+542SNouGBPXan=p15_PbRA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.69.18]
Content-Type: multipart/alternative; boundary="_000_5506bd9120c44493acb735085ead333aXCHALN014ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/i5qF8_aiTxdg_x8G0b_Ik6GEb0E>
Cc: "Keyur Patel (keyupate)" <keyupate@cisco.com>, idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 29 Jul 2016 02:18:21 -0000

Just reading some of this.
A limited refresh is NOT the same thing as "Apply the ORF then remove it".
Suppose you want to refresh a subset of the routes.
You send an ORF to permit only the subset.
You receive the subset.
Now you remove the ORF.
You receive the whole table.
NOT what you wanted.

Also, the use case is good.
The receiver dropped some routes due to policy.
The receiver changed the policy.
Now it wants a repeat of the previously dropped routes.
This is not a use case for ORF or RTC.
The thing is that ORF or RTC were already passing those routes, so changing them is nonsense.

Thanks,
Jakob.