NHRP Version Location
Tim Salo <salo@msc.edu> Tue, 26 December 1995 23:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12416;
26 Dec 95 18:29 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa12412;
26 Dec 95 18:29 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id RAA03149;
Tue, 26 Dec 1995 17:49:25 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
RAA18519 for rolc-out; Tue, 26 Dec 1995 17:52:02 -0500
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id RAA18510 for
<rolc@nexen.com>; Tue, 26 Dec 1995 17:51:59 -0500
Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by guelah.nexen.com
(8.6.12/8.6.12) with SMTP id RAA03117 for <rolc@nexen.com>;
Tue, 26 Dec 1995 17:36:31 -0500
Received: from uh.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324))
id AA18891; Tue, 26 Dec 95 16:52:17 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Salo <salo@msc.edu>
Received: (salo@localhost) by uh.msc.edu (8.7.1/8.6.6) id QAA11944;
Tue, 26 Dec 1995 16:52:16 -0600 (CST)
Date: Tue, 26 Dec 1995 16:52:16 -0600 (CST)
Message-Id: <199512262252.QAA11944@uh.msc.edu>
To: rolc@nexen.com
Subject: NHRP Version Location
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/
I noticed that the NHRP version number (ar$op.version) is the 17th byte of the NHRP Fixed Header. Asuming that future versions of NHRP will be developed, it might be nice if the NHRP version number was earlier in the packet, perhaps the first byte. It would seem that leaving the NHRP version number in the 17th packet would cause future versions to work around this (hopefully fixed) location. [For example, future protocol designers might determine that the number of protocols will grow less rapidly than the number of IPv6 end nodes, and that a smaller protocol ID address space could be used for NHRP...] [[While I am whining, why don't we call the NHRP version field something like nhr$version...]] -tjs
- NHRP Version Location Tim Salo