latest NHRP I-D
Yakov Rekhter <yakov@cisco.com> Tue, 21 November 1995 16:08 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15504;
21 Nov 95 11:08 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15492;
21 Nov 95 11:08 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id KAA13467;
Tue, 21 Nov 1995 10:42:59 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
KAA22352 for rolc-out; Tue, 21 Nov 1995 10:54:41 -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 KAA22343 for
<rolc@nexen.com>; Tue, 21 Nov 1995 10:54:38 -0500
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id KAA13459 for <rolc@nexen.com>;
Tue, 21 Nov 1995 10:41:08 -0500
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by
hubbub.cisco.com (8.6.12/CISCO.GATE.1.1) with SMTP id HAA05650 for
rolc@nexen.com; Tue, 21 Nov 1995 07:51:34 -0800
Message-Id: <199511211551.HAA05650@hubbub.cisco.com>
To: rolc@nexen.com
Subject: latest NHRP I-D
Date: Tue, 21 Nov 95 07:51:33 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
Folks,
If we want to re-use the Destination Prefix Extension for the R2R
case, where the originator of a Request wants to acquire shortcut
information for an address prefix, then the current text in 5.3.1 is
a bit restrictive.
Specifically, it requires the initiator to put 255.255.255.255 in the
Destination Mask. So, if the initiator is a router and it wants
to get the shortcut information for 192.9.200/24, then it would
not be able to specify 255.255.255.0 in the Destination Mask.
So, let me suggest to replace the last paragraph in this section with
the following text:
For example, in the case of IPv4, if an initiator would like to
receive the equivalence information for a group of addresses
covered by an address prefix, it SHALL add this extension
to the NHRP Request with a value that specifies the address prefix.
The responder SHALL copy the extension to the NHRP Reply and modify
the mask appropriately.
Yakov.
- latest NHRP I-D Yakov Rekhter
- Re: latest NHRP I-D Yakov Rekhter
- latest NHRP I-D gardo
- Re: latest NHRP I-D James Luciani
- latest NHRP I-D gardo