Ordering of NHRP extensions
David Horton <horton@citr.com.au> Fri, 03 May 1996 03:24 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00734; 2 May 96 23:24 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa00730; 2 May 96 23:24 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id XAA15845; Thu, 2 May 1996 23:16:28 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id XAA11689 for rolc-out; Thu, 2 May 1996 23:15:54 -0400 (EDT)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id XAA11659 for <rolc@nexen.com>; Thu, 2 May 1996 23:15:48 -0400 (EDT)
Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id XAA05358 for <rolc@nexen.com>; Thu, 2 May 1996 23:15:29 -0400 (EDT)
Received: from citrus.citr.uq.oz.au by bunyip.cc.uq.oz.au with SMTP (PP); Fri, 3 May 1996 13:14:52 +1000
Received: from citron.citr.uq.oz.au by citrus.citr.uq.oz.au (8.7.3/CiTR-External-Gateway) ; id <NAA12454@citrus.citr.uq.oz.au>; Fri, 3 May 1996 13:14:12 +1000 (EST)
Received: from joppa.citr.uq.oz.au by citron.citr.uq.oz.au (8.7.3/CiTR-Main) ; id <NAA10117@citron.citr.uq.oz.au>; Fri, 3 May 1996 13:14:49 +1000 (EST)
Received: from cumquat by joppa.citr.uq.oz.au (8.6.11/CiTR-Client) ; id <NAA10385@joppa.citr.uq.oz.au>; Fri, 3 May 1996 13:14:48 +1000
Received: from localhost by cumquat (5.65c/CiTR-Client) ; id <AA05161@cumquat>; Fri, 3 May 1996 13:13:53 -0500
Message-Id: <5161.199605031813@cumquat>
To: rolc@nexen.com
Subject: Ordering of NHRP extensions
Date: Fri, 03 May 1996 13:13:52 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: David Horton <horton@citr.com.au>
X-Mts: smtp
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: [Un]Subscribe to rolc-request@nexen.com, submissions to rolc@nexen.com
X-Info: Email archive at ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
X-Info: Hypermail archive at http://cell-relay.indiana.edu/mail/archives/rolc/
X-Info: FTP archive at ftp://ftp.nexen.com/pub/rolc/
Is there any implied ordering of extensions in an NHRP packet? Is there any requirement for the extensions to be kept in the same order when forwarded? I can envisage an implementation where an NHS would always send out extensions in some particular fixed order, e.g. have some code that looks like :- if (input_packet.destination_prefix_present) add_destination_prefix_extension(out_packet) if (input_packet.NBMA_subnetwork_extension_present) add_NBMA_subnetwork_extension(out_packet) etc Could the next draft of NHRP add a positive statement on the subject one way or the other? Cheers, David David Horton Centre for Information Technology Research Level 2 South Tower, 339 Coronation Drive, Milton, Australia 4064 Email: d.horton@citr.uq.oz.au Phone +61 7 32592222 Fax +61 7 32592259
- Ordering of NHRP extensions David Horton
- Re: Ordering of NHRP extensions James V. Luciani
- Re: Ordering of NHRP extensions David C. Barnhart
- Re: Ordering of NHRP extensions Paul_Koning/US/3Com%3COM
- Re: Ordering of NHRP extensions Grenville Armitage
- Re: Ordering of NHRP extensions Eric W. Gray