[Idr] 2 Week WG LC for draft-ietf-idr-rtc-no-rt-00 (5/22 to 6/5)
"Susan Hares" <shares@ndzh.com> Fri, 22 May 2015 11:41 UTC
Return-Path: <shares@ndzh.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 1A76E1ACD62 for <idr@ietfa.amsl.com>; Fri, 22 May 2015 04:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Level:
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=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 tteRN_EuvA5w for <idr@ietfa.amsl.com>; Fri, 22 May 2015 04:41:14 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 789B01ACD5C for <idr@ietf.org>; Fri, 22 May 2015 04:41:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.202.180;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Fri, 22 May 2015 07:41:14 -0400
Message-ID: <007c01d09484$35c8a440$a159ecc0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007D_01D09462.AEB88AE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCUg7a/QPVlrA1nQSKXO1p+bYtSYQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/TXkTKtgZ1loRhxFbLUJN8XqeFFs>
Subject: [Idr] 2 Week WG LC for draft-ietf-idr-rtc-no-rt-00 (5/22 to 6/5)
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: Fri, 22 May 2015 11:41:15 -0000
This is a 2 week WG LC for draft-ietf-idr-rtc-no-rt-00. You can find the draft at: http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-no-rt/ This draft looks to clarify the default setting of the RTC when the extended community does not carry an RT in the extended communities. A full description is: BGP routes sometimes carry an "Extended Communities" path attribute. An Extended Communities path attribute can contain one or more "Route Targets" (RTs). By means of a procedure known as "RT Constrained Distribution" (RTC), a BGP speaker can send BGP UPDATE messages that express its interest in a particular set of RTs. Generally, RTC has been applied only to address families whose routes always carry RTs. When RTC is applied to such an address family, a BGP speaker expressing its interest in a particular set of RTs is indicating that it wants to receive all and only the routes of that address family that have at least one of the RTs of interest. However, there are scenarios in which the originator of a route chooses not to include any RTs at all, assuming that the distribution of a route with no RTs at all will be unaffected by RTC. This has led to interoperability problems in the field, where the originator of a route assumes that RTC will not affect the distribution of the route, but intermediate BGP speakers refuse to distribute that route because it does not carry any RT of interest. The purpose of this document is to clarify the effect of the RTC mechanism on routes that do not have any RTs. Please comment if this clarification will aid your BGP Deployments, and if you think this draft is ready for WG LC. Sue Hares