[Idr] draft-chakrabarti-idr-as4-route-cap-01 submitted

"Samita Chakrabarti" <samitac@ipinfusion.com> Tue, 08 July 2008 19:40 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9251328C2DA; Tue, 8 Jul 2008 12:40:21 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 132E228C2DD for <idr@core3.amsl.com>; Tue, 8 Jul 2008 12:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2b9wduMt6010 for <idr@core3.amsl.com>; Tue, 8 Jul 2008 12:40:20 -0700 (PDT)
Received: from nlpi087.prodigy.net (nlpi087.prodigy.net [207.115.36.103]) by core3.amsl.com (Postfix) with ESMTP id 98C0128C2DA for <idr@ietf.org>; Tue, 8 Jul 2008 12:40:18 -0700 (PDT)
X-ORBL: [71.141.112.45]
Received: from samitacD600 (adsl-71-141-112-45.dsl.snfc21.pacbell.net [71.141.112.45]) by nlpi087.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id m68JeMpa021042 for <idr@ietf.org>; Tue, 8 Jul 2008 14:40:28 -0500
From: "Samita Chakrabarti" <samitac@ipinfusion.com>
To: <idr@ietf.org>
Date: Tue, 8 Jul 2008 12:40:19 -0700
Message-ID: <011c01c8e132$7600d6c0$53000a0a@samitacD600>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: AcjgkeUuIdP5ABoJSuCs8PRMVsZgGQAAGUygACgC4DA=
Subject: [Idr] draft-chakrabarti-idr-as4-route-cap-01 submitted
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org




The new draft is available at :

http://www.ietf.org/internet-drafts/draft-chakrabarti-idr-as4-route-cap-01.t
xt


Comments and suggestions are welcome.

Thanks,
-Samita

----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Monday, July 07, 2008 5:32 PM
To: samitac@ipinfusion.com
Subject: New Version Notification for draft-chakrabarti-idr-as4-route-cap-01



A new version of I-D, draft-chakrabarti-idr-as4-route-cap-01.txt has been
successfuly submitted by Samita Chakrabarti and posted to the IETF
repository.

Filename:	 draft-chakrabarti-idr-as4-route-cap
Revision:	 01
Title:		 AS4-specific RD/RT/SOO Capability exchange
Creation_date:	 2008-07-07
WG ID:		 Independent Submission
Number_of_pages: 7

Abstract:
RFC 4893 defines BGP support for four-octet AS number space for
handling AS_PATH attributes and "My ASN" value in BGP OPEN messages.
Foue-Octet AS specific Extended Community attribute formats are
defined in draft-rekhter-as4octet-ext-community-03.txt.  However, an
implementation compliant to RFC 4893 does not necessarily provide
support for 4-Octet Route-distinguisher, Route-target or Site-of-
origin in the BGP-MPLS-VPN.  Thus BGP capability exchange for
extended AS number attribute does not cover the BGP-MPLS-VPN AS4-
specific route-attributes and route-distinguishers.  This document
proposes an optional BGP capability exchange between the Provider
Edge (PE) routers in order to communicate the intention of handling
4-Octet or 2-Octet exteneded AS-specific Route-targets or Site-of-
Origins or being able to handle and inteprete the 4-Octet route-
distinguishers correctly.  This capability parameter will be part of
OPEN message during the BGP session initiation.
 



The IETF Secretariat.






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