Re: Ordering of NHRP extensions

"James V. Luciani" <luciani@baynetworks.com> Fri, 03 May 1996 15:01 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18405; 3 May 96 11:01 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa18401; 3 May 96 11:01 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 KAA18461; Fri, 3 May 1996 10:53:34 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id KAA22496 for rolc-out; Fri, 3 May 1996 10:50:09 -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 KAA22487 for <rolc@nexen.com>; Fri, 3 May 1996 10:50:05 -0400 (EDT)
Received: from lobster.wellfleet.com (lobster.corpeast.baynetworks.com [192.32.253.3]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id KAA16837 for <rolc@nexen.com>; Fri, 3 May 1996 10:50:04 -0400 (EDT)
Received: from lobster1.corpeast.Baynetworks.com by lobster.wellfleet.com (SMI-8.6/SMI-4.1) id KAA17256; Fri, 3 May 1996 10:51:15 -0400
Received: from exnex.engeast (cousteau) by lobster1.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA27551; Fri, 3 May 96 10:49:12 EDT
Received: by exnex.engeast (4.1/SMI-4.1) id AA02046; Fri, 3 May 96 10:50:00 EDT
Message-Id: <9605031450.AA02046@exnex.engeast>
To: David Horton <horton@citr.com.au>
Subject: Re: Ordering of NHRP extensions
In-Reply-To: Your message of "Fri, 03 May 1996 13:13:52 CDT." <5161.199605031813@cumquat>
Cc: rolc@nexen.com
Date: Fri, 03 May 1996 10:49:59 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "James V. Luciani" <luciani@baynetworks.com>
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/

David,
> Is there any implied ordering of extensions in an NHRP packet?
Good idea! :-)  I actually suggested this (via proxy of Andy Malis)
at the last European based IETF.  I explicitly asked for 2 things:
1) the extensions be placed in numerical order by type code
2) (slightly different topic) Next Hop Entries always be
   returned in order from highest to lowest preference with the highest
   in the mandatory part of the NHRP res reply.
Both of these sound eminantly reasonable to me and would make packet processing
faster on the receive side (on the other hand, I have argued many times
that NHRP is NOT fast path :-))

> 
> 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?

What do folks think about the above suggestions?