[Idr] New method for format of ExtCommunity then ExtCommunity can carry TOS of IP header and keep the ability for classifing route information
zhangzhifeng <zhangzhifeng@huawei.com> Thu, 10 November 2005 02:39 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ea2LC-0002js-Fs; Wed, 09 Nov 2005 21:39:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ea2LB-0002jj-9a for idr@megatron.ietf.org; Wed, 09 Nov 2005 21:39:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28736 for <idr@ietf.org>; Wed, 9 Nov 2005 21:38:37 -0500 (EST)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ea2bB-0002O8-JN for idr@ietf.org; Wed, 09 Nov 2005 21:55:45 -0500
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IPP0005ZWYVBC@szxga01-in.huawei.com> for idr@ietf.org; Thu, 10 Nov 2005 10:44:55 +0800 (CST)
Received: from szxml01-in ([172.24.1.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IPP00H1AWYU83@szxga01-in.huawei.com> for idr@ietf.org; Thu, 10 Nov 2005 10:44:55 +0800 (CST)
Received: from z37310 ([10.110.156.163]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IPP002BKX7AXU@szxml01-in.huawei.com> for idr@ietf.org; Thu, 10 Nov 2005 10:49:59 +0800 (CST)
Date: Thu, 10 Nov 2005 10:37:09 +0800
From: zhangzhifeng <zhangzhifeng@huawei.com>
To: idr@ietf.org
Message-id: <004901c5e59f$a61434b0$a39c6e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 96d3a783a4707f1ab458eb15058bb2d7
Subject: [Idr] New method for format of ExtCommunity then ExtCommunity can carry TOS of IP header and keep the ability for classifing route information
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>
Content-Type: multipart/mixed; boundary="===============1058795102=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
Dear all:
If BGP Extended Community can map TOS value of IP header at the same time and keep the ability for classifing route
information,the QoS policy based on BGP will be simple.
The format of ExtCommunity is as following:
Format of BGP ExtCommunity
The BGP Extended Community is encoded as an eight octet quantity.
We define the Format of the BGP Extended Community
as follows:
- Type Field : 1 octets
- TOS Value Field : 1 octets
- Value Field : Remaining octets
Type Field - the value mark the IANA regist information of BGP
Extended Community and the format of the Value Field
TOS Value Field - the value mark the TOS value that will be carried
by the stream matched correlation networking
information
Value Field - the value mark the classified route imformatin
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type Field |TOS Value Field| Value Field |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value Field |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Type Field
The size of Type Field for Regular types is 1 octet，as shown below：
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|I|T| spare |V|
+-+-+-+-+-+-+-+-+
I - IANA authority bit
T - TOS bit
Value 0: The TOS Value Field mark the default value 0
value 1: The TOS Value Field mark the value which would
be remarked the IP packet
V - The value of this bit which can identify the format of
the Value Field
Value 0: The high-order two octets of the Value Field is
administrator Field, the remaining octets is
sub-administrator Field
Value 1: The high-order four octets of the Value Field
is administrator Field, the remaining octets is
sub-administrator Field
TOS Value Field
The default value of TOS Value Field is 0. When the route information
be imported into BGP, we can define the TOS Field value that the route
informatin should carried.
According to defined DSCP value, we will define such BGP Extended
Community:
ExtCommunity name the high-order DSCP classes DSCP values
six bits of TOS
Value Field
ExtCom-EF 101110 EF 101110
ExtCom-AF41 100010 AF41 100010
ExtCom-AF42 100100 AF42 100100
ExtCom-AF43 100110 AF43 100110
ExtCom-AF31 011010 AF31 011010
ExtCom-AF32 011100 AF32 011100
ExtCom-AF33 011110 AF33 011110
ExtCom-AF21 010010 AF21 010010
ExtCom-AF22 010100 AF22 010100
ExtCom-AF23 010110 AF23 010110
ExtCom-AF11 001010 AF11 001010
ExtCom-AF12 001100 AF12 001100
ExtCom-AF13 001110 AF13 001110
ExtCom-BF 000000 BF 000000
The remaining bits of TOS Value Field use 0 as value.
Value Field
The Value Field used for identifing the route infomation which belong
to different community.
We can set and change the value of the Value Field, and can't impact
the other Field.
If you have any advice or suggestion, please contact me directly.
Thanks a lot!
zhangzhifeng
_______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] New method for format of ExtCommunity then … zhangzhifeng
- [Idr] New method for format of ExtCommunity then … zhangzhifeng