[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Inter-Domain Routing List <idr at ietf.org>
Subject: [Idr] [Fwd: I-D Action:draft-chen-rfc4893bis-01.txt]
From: Enke Chen <enkechen at cisco.com>
Date: Mon, 02 Feb 2009 11:16:46 -0800
Authentication-results: sj-dkim-2; header.From=enkechen at cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: quaizar.vohra at gmail.com
Delivered-to: ietfarch-idr-archive at core3.amsl.com
Delivered-to: idr at core3.amsl.com
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=10141; t=1233602210; x=1234466210; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen at cisco.com; z=From:=20Enke=20Chen=20<enkechen at cisco.com> |Subject:=20[Fwd=3A=20I-D=20Action=3Adraft-chen-rfc4893bis- 01.txt] |Sender:=20; bh=pfqwY5vsbEyRX6pQ/E5Qucszz0Z9Li8dk3mQukavxB8=; b=TGgzGfIGZmM67qwBk8EaCcREb3rRKecq3OpXDaN4LhxIebLcCypRBeQ0eu iZOPhveeH+T9nZf3FREN2copVjlh570gd0dXr/GMw4YB6PKmhUMXe8gCHC80 Vs8tbvFg6G;
List-archive: <http://www.ietf.org/pipermail/idr>
List-help: <mailto:idr-request@ietf.org?subject=help>
List-id: Inter-Domain Routing <idr.ietf.org>
List-post: <mailto:idr@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
Sender: idr-bounces at ietf.org
User-agent: Thunderbird 2.0.0.19 (X11/20081209)

Hi, folks:

The revised version includes the following changes from the -00.txt version:

  o The Error Handling section has been enhanced, with the error conditions
     for the new attributes spelled out.

  o Several "SHOULD NOT" are changed to "MUST NOT".

The diff is attached.

Thanks.   -- Enke

-------- Original Message --------
Subject: 	I-D Action:draft-chen-rfc4893bis-01.txt
Date: 	Mon, 2 Feb 2009 11:00:01 -0800 (PST)
From: 	Internet-Drafts at ietf.org
Reply-To: 	internet-drafts at ietf.org
To: 	i-d-announce 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-01.txt
	Pages           : 11
	Date            : 2009-02-02

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-01.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.

<<< Message/External-body; name="draft-chen-rfc4893bis-01.txt": Unrecognized >>>

_______________________________________________
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

*** draft-chen-rfc4893bis-00.txt	Fri Jan 23 16:09:47 2009
--- draft-chen-rfc4893bis-01.txt	Mon Feb  2 09:34:53 2009
***************
*** 147,158 ****
     To prevent the possible propagation of confederation path segments
     outside of a confederation, the path segment types AS_CONFED_SEQUENCE
     and AS_CONFED_SET [RFC5065] are declared invalid for the AS4_PATH
!    attribute.  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.
  
     Similarly, this document defines a new aggregator attribute called
     AS4_AGGREGATOR, which is optional transitive.  The AS4_AGGREGATOR
--- 147,153 ----
     To prevent the possible propagation of confederation path segments
     outside of a confederation, the path segment types AS_CONFED_SEQUENCE
     and AS_CONFED_SET [RFC5065] are declared invalid for the AS4_PATH
!    attribute, and MUST NOT be carried in an UPDATE message.
  
     Similarly, this document defines a new aggregator attribute called
     AS4_AGGREGATOR, which is optional transitive.  The AS4_AGGREGATOR
***************
*** 198,208 ****
     peer, and MUST assume that these attributes in the updates received
     from the peer encode Autonomous System numbers as 4-octet entities.
  
!    The new attributes, AS4_PATH and AS4_AGGREGATOR SHOULD NOT be carried
!    in the UPDATE messages between NEW BGP peers.  A NEW BGP speaker that
!    receives the AS4_PATH and AS4_AGGREGATOR path attributes in an UPDATE
!    message from a NEW BGP speaker SHOULD discard these path attributes
!    and continue processing the UPDATE message.
  
  
  4.2. Interaction Between NEW and OLD BGP Speakers
--- 198,208 ----
     peer, and MUST assume that these attributes in the updates received
     from the peer encode Autonomous System numbers as 4-octet entities.
  
!    The new attributes, AS4_PATH and AS4_AGGREGATOR MUST NOT be carried
!    in an UPDATE message between NEW BGP speakers.  A NEW BGP speaker
!    that receives the AS4_PATH attribute or the AS4_AGGREGATOR attribute
!    in an UPDATE message from another NEW BGP speaker MUST discard the
!    path attribute and continue processing the UPDATE message.
  
  
  4.2. Interaction Between NEW and OLD BGP Speakers
***************
*** 225,231 ****
     AS numbers.  The NEW speaker MUST also send the AS path information
     in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
     for the case where the entire AS path information is composed of 2-
!    octet AS numbers only.  In this case, the NEW speaker SHOULD NOT send
     the AS4_PATH attribute.
  
     In the AS_PATH attribute encoded with 2-octet AS numbers, non-
--- 225,231 ----
     AS numbers.  The NEW speaker MUST also send the AS path information
     in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
     for the case where the entire AS path information is composed of 2-
!    octet AS numbers only.  In this case, the NEW speaker MUST NOT send
     the AS4_PATH attribute.
  
     In the AS_PATH attribute encoded with 2-octet AS numbers, non-
***************
*** 264,270 ****
     value of the AS4_AGGREGATOR attribute, and sets the AS number field
     in the existing AGGREGATOR attribute to the reserved AS number,
     AS_TRANS.  Note that if the AS number is 2-octets only, then the
!    AS4_AGGREGATOR attribute SHOULD NOT be sent.
  
  
  4.2.3. Processing Received Updates
--- 264,270 ----
     value of the AS4_AGGREGATOR attribute, and sets the AS number field
     in the existing AGGREGATOR attribute to the reserved AS number,
     AS_TRANS.  Note that if the AS number is 2-octets only, then the
!    AS4_AGGREGATOR attribute MUST NOT be sent.
  
  
  4.2.3. Processing Received Updates
***************
*** 372,390 ****
     As specified in [RFC1997], when the high-order two-octets of the
     community attribute is neither 0x0000 nor 0xffff, these two octets
     encode the Autonomous System number.  Quite clearly this would not
!    work for BGP speakers that use 4-octets Autonomous System numbers.
     Such BGP speakers should use the Four-octet AS Specific Extended
     Communities [AS-EXT-COM] instead.
  
  
  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.
  
  
  7. Transition
--- 369,441 ----
     As specified in [RFC1997], when the high-order two-octets of the
     community attribute is neither 0x0000 nor 0xffff, these two octets
     encode the Autonomous System number.  Quite clearly this would not
!    work for a NEW BGP speaker with a non-mappable 4-octet AS number.
     Such BGP speakers should use the Four-octet AS Specific Extended
     Communities [AS-EXT-COM] instead.
  
  
  6. Error Handling
  
!    The AS4_PATH attribute in an UPDATE message is considered malformed
!    under the following conditions:
! 
!       - the attribute type appears more than once in the UPDATE
!         message, or
! 
!       - the attribute is not marked "optional and transitive", or
! 
!       - the attribute length is inconsistent with the "Total Path
!         Attribute Length" in the UPDATE message, or
! 
!       - the path segment length in the attribute is either zero, or
!         is inconsistent with the attribute length, or
! 
!       - the path segment type in the attribute is not one of the
!         types defined: AS_SEQUENCE, AS_SET, AS_CONFED_SEQUENCE
!         and AS_CONFED_SET.
! 
!    A NEW BGP speaker that receives a malformed AS4_PATH attribute in an
!    UPDATE message from an OLD BGP speaker MUST discard the attribute,
!    and continue processing the UPDATE message.  The error SHOULD be
!    logged locally for analysis.
! 
!    In addition, the path segment types AS_CONFED_SEQUENCE and
!    AS_CONFED_SET [RFC5065] are declared invalid for the AS4_PATH
!    attribute, and MUST NOT be carried in an UPDATE message.  A NEW BGP
!    speaker that receives these path segment types in the AS4_PATH
!    attribute of an UPDATE message from an OLD BGP speaker MUST discard
!    these path segments, adjust the relevant attribute fields
!    accordingly, and continue processing the UPDATE message.
! 
!    The AS4_AGGREGATOR attribute in an UPDATE message is considered
!    malformed under the following conditions:
! 
!       - the attribute type appears more than once in the UPDATE
!         message, or
! 
!       - the attribute is not marked "optional and transitive", or
! 
!       - the attribute length is of a value other than 8, or
! 
!       - the AS number in the attribute is zero, or
! 
!       - the BGP Identifier in the attribute is zero.
! 
!    A NEW BGP speaker that receives a malformed AS4_AGGREGATOR attribute
!    in an UPDATE message from an OLD BGP speaker MUST discard the
!    attribute, and continue processing the UPDATE message.  The error
!    SHOULD be logged locally for analysis.
  
  
  7. Transition

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

Follow-Ups:
- Re: [Idr] [Fwd: I-D Action:draft-chen-rfc4893bis-01.txt]
  - From: Rob Shakir

Prev by Date: Your Payment Has Been Initiated
Next by Date: [Idr] Posting of IPR Disclosure
Previous by thread: Sales Receipt from Amazon
Next by thread: Re: [Idr] [Fwd: I-D Action:draft-chen-rfc4893bis-01.txt]
Index(es):
- Date
- Thread