IETF Logo Mail Archive

[Idr] RE: Prefix-list ORF sequence number question

"Enke Chen \(enkechen\)" <enkechen@cisco.com> Wed, 09 February 2005 18:44 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25768; Wed, 9 Feb 2005 13:44:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyx9K-0005zX-7Z; Wed, 09 Feb 2005 14:05:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CywlN-00007h-JG; Wed, 09 Feb 2005 13:40:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cywja-00086a-Uq for idr@megatron.ietf.org; Wed, 09 Feb 2005 13:38:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25364 for <idr@ietf.org>; Wed, 9 Feb 2005 13:38:40 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyx3R-0005r9-CL for idr@ietf.org; Wed, 09 Feb 2005 13:59:14 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 09 Feb 2005 10:48:37 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.88,190,1102320000"; d="scan'208"; a="613342807:sNHT447927426"
Received: from enkechenw2k (dhcp-128-107-134-98.cisco.com [128.107.134.98]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j19Ic6uC018758; Wed, 9 Feb 2005 10:38:07 -0800 (PST)
Message-Id: <200502091838.j19Ic6uC018758@sj-core-1.cisco.com>
From: "Enke Chen (enkechen)" <enkechen@cisco.com>
To: 'Vivian Lu' <vlu@nortel.com>
Date: Wed, 09 Feb 2005 10:38:06 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
Thread-Index: AcUOsWGjLS4KPseYQdujevTg40r16gAI5FvQ
In-Reply-To: <6204FDDE129D364D8040A98BCCB290EF0FCD1003@zbl6c004.corpeast.baynetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org, enkechen@cisco.com
Subject: [Idr] RE: Prefix-list ORF sequence number question
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: enkechen@cisco.com
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>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Hi, Vivian:

Please see my comments inlined.

> -----Original Message-----
> From: Vivian Lu [mailto:vlu@nortel.com] 
> Sent: Wednesday, February 09, 2005 6:12 AM
> To: Vivian Lu; 'enke@cisco.com'; 'rsrihari@cisco.com'
> Cc: 'idr@ietf.org'
> Subject: Prefix-list ORF sequence number question
> 
> Hi, 
> 
> I have a question regarding prefix-list ORF draft, 
> draft-ietf-idr-bgp-prefix-orf-00.txt. 
> 
> The "sequence" field as specified in the draft is the following, 
>         "The 'Sequence' field is a number that specifies the 
> relative ordering of the entry." 
> 
> What is the scope to which the statement is referring that 
> makes the ordering significant? 

The "Sequence" field is used in Sect 6. Address Prefix ORF Matching
when multiple ORF entries match a particular NLRI.

We can add some text to the definition in the next revision.

> 
> Is the scope 
> 
> 	*	per bgp peer session? 
> 
> 		-- That is, sequence number is continuously 
> incremented for each orf entry through out the peer session. 
> 		-- Sequence number gets reset when the peer 
> session is reset. 
> 	*	per ORF message? 
> 
> 		-- That is, sequence number is continuously 
> incremented for each orf entry within an ORF message. 
> 		-- Sequence number gets reset when a new ORF 
> message is created. 
> 	*	per ORF type block in the orf message ?
> 
> 		-- That is, sequence number is continuously 
> incremented for each orf entry within an ORF type block 
> inside an ORF message.
> 
> 		-- Sequence number gets reset when a new ORF 
> type block is written. 
> 
> We are wondering which one is what you intended and the 
> industry may agree with. 

Per the base ORF spec., ORFs are exchanged on a per peer
basis, and the life time of an ORF is the duration of the
session.

The scope of the sequence number is within the prefix-ORF
type exchanged over the session.  It is a local matter
(on the sender) how the sequenece number is assigned for
the intended semantics "relative ordering").

-- Enke

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

v2.23.0 | Report a Bug | By Email