[Idr] Prefix-list ORF sequence number question
"Vivian Lu" <vlu@nortel.com> Wed, 09 February 2005 14:27 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 JAA05231; Wed, 9 Feb 2005 09:27:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyt81-0008S1-Oh; Wed, 09 Feb 2005 09:47:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyshm-0003y3-0f; Wed, 09 Feb 2005 09:20:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cysa5-0001yS-R3 for idr@megatron.ietf.org; Wed, 09 Feb 2005 09:12:38 -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 JAA04313 for <idr@ietf.org>; Wed, 9 Feb 2005 09:12:36 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cystu-0008Ag-Nk for idr@ietf.org; Wed, 09 Feb 2005 09:33:07 -0500
Received: from zbl6c004.us.nortel.com (zbl6c004.corpeast.baynetworks.com [132.245.205.54]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j19EC3V24037; Wed, 9 Feb 2005 09:12:03 -0500 (EST)
Received: by zbl6c004.corpeast.baynetworks.com with Internet Mail Service (5.5.2653.19) id <1JMBWFMD>; Wed, 9 Feb 2005 09:12:03 -0500
Message-ID: <6204FDDE129D364D8040A98BCCB290EF0FCD1003@zbl6c004.corpeast.baynetworks.com>
From: Vivian Lu <vlu@nortel.com>
To: Vivian Lu <vlu@nortel.com>, "'enke@cisco.com'" <enke@cisco.com>, "'rsrihari@cisco.com'" <rsrihari@cisco.com>
Date: Wed, 09 Feb 2005 09:12:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: "'idr@ietf.org'" <idr@ietf.org>
Subject: [Idr] Prefix-list ORF sequence number question
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="===============0594236792=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
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? 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. Thanks. Vivian.
_______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] Prefix-list ORF sequence number question Vivian Lu
- [Idr] RE: Prefix-list ORF sequence number question Enke Chen (enkechen)
- [Idr] RE: Prefix-list ORF sequence number question Vivian Lu