[Idr] [Fwd: I-D Action:draft-chen-rfc4893bis-00.txt]

[Enke Chen <enkechen at cisco.com>]

Hi, folks:

The changes from RFC 4893 are summarized in the Appendix of the draft:

     This document clarifies the handling of the confederation path
     segments in the AS4_PATH attribute, and also specifies the error
     handling for the new attributes.

The following are the specific additions:

-----------------------
3. Protocol Extensions

A NEW BGP speaker SHOULD NOT send these path segment
types in the AS4_PATH attribute of an UPDATE message.  A NEW BGP
speaker that receives these path segment types in the AS4_PATH
attribute of an UPDATE message MUST discard these path segments,
adjust the relevant attribute fields accordingly, and continue
processing the UPDATE message.

6. Error Handling

When a NEW BGP speaker encounters an error (other than the invalid
confederation path segment types described previously) in parsing the
AS4_PATH attribute or the AS4_AGGREGATOR attribute of an UPDATE
message, the speaker MUST discard the attribute in error, and
continue processing the UPDATE message. The error SHOULD be logged
locally for analysis.

9. Security Considerations

It is a misconfiguration to assign a non-mappable 4-octet AS number
as the "Member AS Number" in a BGP confederation before all the BGP
speakers within the confederation have transitioned to support 4-
octet AS numbers. Such a misconfiguration would weaken the AS path
loop detection within a confederation.
-----------------------------

Your comments are welcome and appreciated.

Thanks.  -- Enke

--- Begin Message ---

• To: i-d-announce at ietf.org
• Subject: I-D Action:draft-chen-rfc4893bis-00.txt
• From: Internet-Drafts at ietf.org
• Date: Sat, 24 Jan 2009 13:00:01 -0800 (PST)
• Authentication-results: sj-dkim-1; header.From=Internet-Drafts at ietf.org; dkim=neutral
• Delivered-to: i-d-announce at core3.amsl.com
• List-archive: <http://www.ietf.org/pipermail/i-d-announce>
• List-help: <mailto:i-d-announce-request@ietf.org?subject=help>
• List-id: Internet Draft Announcements only <i-d-announce.ietf.org>
• List-post: <mailto:i-d-announce@ietf.org>
• List-subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
• List-unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
• Reply-to: internet-drafts at ietf.org
• Sender: i-d-announce-bounces at ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : BGP Support for Four-octet AS Number Space
	Author(s)       : Q. Vohra, E. Chen
	Filename        : draft-chen-rfc4893bis-00.txt
	Pages           : 10
	Date            : 2009-01-24

Currently the Autonomous System (AS) number is encoded as a two-octet
entity in BGP. This document describes extensions to BGP to carry the
Autonomous System number as a four-octet entity.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chen-rfc4893bis-00.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

<ftp://ftp.ietf.org/internet-drafts/draft-chen-rfc4893bis-00.txt>

_______________________________________________
I-D-Announce mailing list
I-D-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--- End Message ---

_______________________________________________
Idr mailing list
Idr at ietf.org
https://www.ietf.org/mailman/listinfo/idr