revised draft of BGP-4
Yakov Rekhter <yakov@cisco.com> Thu, 15 June 1995 02:50 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12614;
14 Jun 95 22:50 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12610;
14 Jun 95 22:50 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa23675;
14 Jun 95 22:50 EDT
Received: by interlock.ans.net id AA38148
(InterLock SMTP Gateway 3.0 for iwg-out@ans.net);
Wed, 14 Jun 1995 22:43:45 -0400
Message-Id: <199506150243.AA38148@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2);
Wed, 14 Jun 1995 22:43:45 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1);
Wed, 14 Jun 1995 22:43:45 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.com>
To: bgp@ans.net
Subject: revised draft of BGP-4
Date: Wed, 14 Jun 95 19:43:38 PDT
Folks, Today I sent to CNRI a revised version of BGP-4 spec. The only difference between this version and the current protocol spec (other than changing dates and my affiliation) are the following two paragraphs: First paragraph: If the OPEN message carries any other Optional Parameter (other than Authentication Information), and the local system doesn't recognize the Parameter, the Parameter shall be ignored. Second paragraph: The information carried by the AS_PATH attribute is checked for AS loops. AS loop detection is done by scanning the full AS path (as specified in the AS_PATH attribute), and checking that the autonomous system number of the local system does not appear in the AS path. If the autonomous system number appears in the AS path the route may be stored in the Adj-RIB-In, but unless the router is configured to accept routes with its own autonomous system in the AS path, the route shall not be passed to the BGP Decision Process. Operations of a router that is configured to accept routes with its own autonomous system number in the AS path are outside the scope of this document. Please comment on this document as soon as possible, since we are planning to advance the document to a Full Standard at the Stockholm IETF. Thanks. Yakov Rekhter (yakov@cisco.com)
- revised draft of BGP-4 Yakov Rekhter
- Re: revised draft of BGP-4 Vadim Antonov
- Re: revised draft of BGP-4 Paul Traina
- Re: revised draft of BGP-4 Michael F. Nittmann
- Re: revised draft of BGP-4 Paul Traina
- Re: revised draft of BGP-4 Curtis Villamizar
- Re: revised draft of BGP-4 Michael F. Nittmann
- Re: revised draft of BGP-4 Paul Traina
- Re: revised draft of BGP-4 Dennis Ferguson