I-D ACTION:draft-white-pathconsiderations-08.txt
Internet-Drafts@ietf.org Wed, 16 August 2006 19:50 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDRP4-0004qF-Ni; Wed, 16 Aug 2006 15:50:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDROt-0004oL-25 for i-d-announce@ietf.org; Wed, 16 Aug 2006 15:50:03 -0400
Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDROs-0004f9-HW for i-d-announce@ietf.org; Wed, 16 Aug 2006 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 7BF9D3287E for <i-d-announce@ietf.org>; Wed, 16 Aug 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GDROs-0000sU-C3 for i-d-announce@ietf.org; Wed, 16 Aug 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc:
From: Internet-Drafts@ietf.org
Message-Id: <E1GDROs-0000sU-C3@stiedprstage1.ietf.org>
Date: Wed, 16 Aug 2006 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Subject: I-D ACTION:draft-white-pathconsiderations-08.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Considerations in Validating the Path in BGP Author(s) : R. White, et al. Filename : draft-white-pathconsiderations-08.txt Pages : 15 Date : 2006-8-16 A good deal of thought has gone into, and is currently being given to, validating the path to a destination advertised by BGP. The purpose of this work is to explain the issues in validating a BGP AS Path, in the expectation that it will help in the evaluation of schemes seeking to improve path validation. The first section defines at least some of the types of questions a BGP speaker receiving an update from a peer not in the local autonomous system (AS) could ask about the information within the routing update. The sections following examine the answers to these questions in consideration of specific deployments of BGP. The examples given in this draft are intended to distill deployments down to their most critical components, making the examples easier to understand and consider. In many situations, the specific path taken in the example may not be relevant, but that does not nullify the principles considered in each example. It has been suggested that these examples are "red herrings," because they do not illustrate actual problems with specific policies. On the contrary, these examples are powerful because they are simple. Any topology in which one of these example topologies is a subtopology will exhibit the characteristics explained in this draft. Rather than focusing on a specific topology, then dismissing that single topology as a "corner case," this draft shows the basic issues with assertions about the AS Path attribute within BGP. These generalized issues can then be applied to more specific cases. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-white-pathconsiderations-08.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-white-pathconsiderations-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-white-pathconsiderations-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
_______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce
- I-D ACTION:draft-white-pathconsiderations-08.txt Internet-Drafts