Re: Ordering of NHRP extensions

Grenville Armitage <gja@bellcore.com> Fri, 03 May 1996 16:43 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20898; 3 May 96 12:43 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20894; 3 May 96 12:43 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 MAA19674; Fri, 3 May 1996 12:32:24 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id MAA24074 for rolc-out; Fri, 3 May 1996 12:31:23 -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 MAA24065 for <rolc@nexen.com>; Fri, 3 May 1996 12:31:20 -0400 (EDT)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id MAA18836 for <rolc@nexen.com>; Fri, 3 May 1996 12:31:15 -0400 (EDT)
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.12/8.6.11) with ESMTP id MAA26423; Fri, 3 May 1996 12:30:44 -0400
Message-Id: <199605031630.MAA26423@thumper.bellcore.com>
To: Paul_Koning/US/3Com%3COM@smtp1.isd.3com.com
cc: luciani@baynetworks.com, rolc@nexen.com, gja@thumper.bellcore.com
Subject: Re: Ordering of NHRP extensions
In-reply-to: Your message of 03 May 1996 11:56:19 -0400. <9605031855.AA5395@>
Date: Fri, 03 May 1996 12:30:31 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@bellcore.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/

>>>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
>>
>>I hope not.  This might in a few cases speed up receive processing
>>slightly, at the cost of a more substantial hit in time and complexity
>>at the transmit end.

Could you please justify this assertion. The 'hit' you get by forcing
programmers to structure their TX code cleanly is not a good reason.
Since the TX side knows what it wants, the set of options to be TXed
can be built pre-transmission to be in the most optimal order for RX
processing. Minimal per-packet TX side hit.

	[..]
>>This sort of idea has been floated in other places and generally
>>rejected.  I think it should be rejected here as well.

Not thinking of CIF recently, are we? :)  Perhaps if you could
explain why it was rejected in the past, the WG would be in a better
place to understand how the past lessons ought to be applied here.

I happen to think its a reasonable idea. RX processing may
be improved (and could hardly be made worse), and I dont see
where the hit is on TX processing.

cheers,
gja
_________________________________________________________________________
Grenville Armitage                               gja@thumper.bellcore.com
Bellcore, 445 South St.      http://gump.bellcore.com:8000/~gja/home.html
Morristown, NJ 07960 USA          (voice) +1 201 829 2635 {.. 2504 (fax)}