[Idr] I-D Action: draft-ietf-idr-rtc-no-rt-07.txt

internet-drafts@ietf.org Mon, 08 May 2017 13:30 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 638DF127843; Mon, 8 May 2017 06:30:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: idr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149425022536.27632.12204873443849653826@ietfa.amsl.com>
Date: Mon, 08 May 2017 06:30:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/RQ-n77NAbk5HKhI1PgMJff7I6NU>
Subject: [Idr] I-D Action: draft-ietf-idr-rtc-no-rt-07.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 08 May 2017 13:30:25 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Route Target Constrained Distribution of Routes with no Route Targets
        Authors         : Eric C. Rosen
                          Keyur Patel
                          Jeffrey Haas
                          Robert Raszuk
	Filename        : draft-ietf-idr-rtc-no-rt-07.txt
	Pages           : 7
	Date            : 2017-05-08

Abstract:
   There are a variety of BGP-enabled services in which the originator
   of a BGP route may attach one or more "Route Targets" to the route.
   By means of a procedure known as "RT Constrained Distribution" (RTC),
   a given BGP speaker (call it "B") can announce the set of RTs in
   which it has interest.  The implication is that if a particular route
   (call it "R") carries any RTs at all, BGP speaker B wants to receive
   route R if and only if B has announced interest in one of the RTs
   carried by R.  However, if route R does not carry any RTs at all,
   prior specifications do not make it clear whether B's use of RTC
   implies that it does not want to receive route R.  This has caused
   interoperability problems in the field, as some implementations of
   RTC do not allow B to receive R, but some services presuppose that B
   will receive R.  This document updates RFC 4684 by clarifying the
   effect of the RTC mechanism on routes that do not have any RTs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-rtc-no-rt/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-rtc-no-rt-07
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rtc-no-rt-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rtc-no-rt-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/