[Idr] Sub-Type of 4-octet AS specific extended community
Tomohiko Kurahashi <kura@iij.ad.jp> Fri, 14 March 2008 01:54 UTC
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D52A3A6930; Thu, 13 Mar 2008 18:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.42
X-Spam-Level:
X-Spam-Status: No, score=-100.42 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 iOTBUS5ZEZvV; Thu, 13 Mar 2008 18:54:22 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24BE23A680B; Thu, 13 Mar 2008 18:54:22 -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 CD58C3A680B for <idr@core3.amsl.com>; Thu, 13 Mar 2008 18:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 wwBw9+qrwzSm for <idr@core3.amsl.com>; Thu, 13 Mar 2008 18:54:20 -0700 (PDT)
Received: from otm-mgo01.iij.ad.jp (otm-mgo01.iij.ad.jp [210.138.20.175]) by core3.amsl.com (Postfix) with ESMTP id 385C63A67FA for <idr@ietf.org>; Thu, 13 Mar 2008 18:54:17 -0700 (PDT)
DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=From:To: Subject:Mime-Version:Content-Type:Message-Id:Date; i=kura@iij.ad.jp; s=omgo0; t= 1205459518; x=1206669118; bh=oXs8ejnfTFoBGfVB5It31QQO03DF5LibsVSzxGBBQb8=; b=L4h tpgltJFe3xM1U/I5T2tjFtHjfIIRGFTPp3djaE81OOtXNudvNPgKi6PFHPNtNVwtLz2/mi+1QoQ+W cCRW1gSW67R5at3HBLelvtuCzRM+VSb/nI2svQfM78G3w1Nh4qiXPH9NIV9ylQ3hWqXkAE3F23uC5 lEkhZwxv9MRlHA=;
Received: OTM-MO(otm-mgo01) id m2E1pwXA009908; Fri, 14 Mar 2008 10:51:58 +0900 (JST)
Received: OTM-MIX(otm-mix00) id m2E1pv4F065465; Fri, 14 Mar 2008 10:51:58 +0900 (JST)
Received: from melchior.iij.ad.jp (melchior.iij.ad.jp [192.168.168.33]) by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id m2E1pvKg045627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <idr@ietf.org>; Fri, 14 Mar 2008 10:51:57 +0900 (JST)
Received: by melchior.iij.ad.jp (Postfix) id 90B1F2346C; Fri, 14 Mar 2008 10:51:57 +0900 (JST)
From: Tomohiko Kurahashi <kura@iij.ad.jp>
To: idr@ietf.org
Mime-Version: 1.0
X-Mailer: mnews [version 1.22PL7] 2003-09/29(Mon)
Message-Id: <20080314015157.90B1F2346C@melchior.iij.ad.jp>
Date: Fri, 14 Mar 2008 10:51:57 +0900
Subject: [Idr] Sub-Type of 4-octet AS specific extended community
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
Hello list,
This post is duplicated since I found the previous mail isn't archived
correctly and hasn't been delivered to myself yet. I apologize first if
you receive my mail twice.
Well, I want a clarification with regard to (Sub-)Type Field value of
4-octet AS specific extended community. From section 5 of RFC4893
"BGP Support for Four-octet AS Number Space",
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.
[AS-EXT-COM] is pointing draft-rekhter-as4octet-ext-community, and in
the draft no types other than the followings are described.
Name Type Value
---- ----------
four-octet AS specific Route Target 0x0202
four-octet AS specific Route Origin 0x0203
Both types above are for BGP-MPLS VPN. Now, what (Sub-)Type value should
be used in other networks, e.g. in The Internet?
Best regards,
--
Tomohiko Kurahashi <kura@iij.ad.jp>
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr
- [Idr] Sub-Type of 4-octet AS specific extended co… kura
- [Idr] Sub-Type of 4-octet AS specific extended co… Tomohiko Kurahashi