r2r nhrp and destination prefix length extension

Rajesh Varadarajan <rvaradar@fore.com> Wed, 15 May 1996 19:21 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27032; 15 May 96 15:21 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa27027; 15 May 96 15:21 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 PAA19696; Wed, 15 May 1996 15:10:32 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id PAA28691 for rolc-out; Wed, 15 May 1996 15:07:04 -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 PAA28678 for <rolc@nexen.com>; Wed, 15 May 1996 15:07:00 -0400 (EDT)
Received: from fore.com (mailhub.fore.com [192.88.243.4]) by nexen.nexen.com (8.7.3/8.7.3) with ESMTP id PAA09070 for <rolc@nexen.com>; Wed, 15 May 1996 15:06:59 -0400 (EDT)
Received: from dolphin.fore.com ([192.88.243.27]) by fore.com (8.7.3/8.6.11) with ESMTP id PAA09157; Wed, 15 May 1996 15:03:45 -0400 (EDT)
Received: from dcdolphin.dc.fore.com ([198.29.27.59]) by dolphin.fore.com (8.7.3/3.4W4) with ESMTP id PAA19506; Wed, 15 May 1996 15:06:54 -0400 (EDT)
Message-Id: <199605151906.PAA19506@dolphin.fore.com>
To: luciani@lobster.baynetworks.com
cc: rolc@nexen.com
Subject: r2r nhrp and destination prefix length extension
Date: Wed, 15 May 1996 15:11:12 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rajesh Varadarajan <rvaradar@fore.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/

jim,
	I had sent out mail to the rolc list a few days back regarding this subject.

Here a cut-and-paste of the contents....

> The r2r nhrp document assumes that the destination prefix length in
> a NHRP request could be other than 0xffffffff. However, the NHRP draft explicitly
> states that the destination prefix length has to be 0xffffffff in a NHRP request.
> 
        > It would therefore clarify things if the r2r nhrp document (or the NHRP draft)
> explictly redefine the semantics of the destination prefix extension to allow
> NHRP requests to have the destination prefix extension field have a value other
> that 0xffffffff.
> 
> Thanks,
> rajesh
> rajv@fore.com


Will the next version of NHRP allow for NHRP requests to have values other
that 0xffffffff in the dest-prefix extension. Could you clarify?

Thanks,
rajesh