Re: [Idr] 4-Byte ASN - subtype for extended community

Yakov Rekhter <yakov@juniper.net> Mon, 09 October 2006 13:48 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWvUm-0003Po-76; Mon, 09 Oct 2006 09:48:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWvUl-0003Pj-Cq for idr@ietf.org; Mon, 09 Oct 2006 09:48:39 -0400
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GWvUj-0004CL-2V for idr@ietf.org; Mon, 09 Oct 2006 09:48:39 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k99DmU1Z093154; Mon, 9 Oct 2006 06:48:30 -0700 (PDT) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k99DmUu61917; Mon, 9 Oct 2006 06:48:30 -0700 (PDT) (envelope-from yakov@juniper.net)
Message-Id: <200610091348.k99DmUu61917@merlot.juniper.net>
To: "Kavitha G - TLS ,Chennai" <KavithaG@hcl.in>
Subject: Re: [Idr] 4-Byte ASN - subtype for extended community
In-Reply-To: Your message of "Mon, 09 Oct 2006 17:39:04 +0530." <434F1CE611459F45BBC351FEB5A83F43021D9332@kavithai.ctd.hcltech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <94795.1160401710.1@juniper.net>
Date: Mon, 09 Oct 2006 06:48:30 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

Kavitha,

> For BGP 4-octet AS, what is the sub-type value to be used in extended
> communities?
>
> In the draft 4-octet AS specific Extended community, the subtype are
> given for Route Target and Route Origin.
> 
> When there is no support for BGP-MPLS-VPN, how this 4-octet AS specific 
> can be sent in the extended community attribute. [i.e., For general 
> 4-octet AS number in extended comm, which is used similar to community 
> attribute]

The IANA would need to create a registry (as specified in the
IANA Consideration section of draft-rekhter-as4octet-ext-community),
and then one would need to request an assignment from that registry.
  
Yakov.

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