Request-ID and Destination Prefix Extension
gardo@vnet.ibm.com Wed, 27 September 1995 21:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18099;
27 Sep 95 17:29 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa18095;
27 Sep 95 17:29 EDT
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 RAA09735;
Wed, 27 Sep 1995 17:08:26 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
RAA09931 for rolc-out; Wed, 27 Sep 1995 17:04:02 -0400
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 RAA09921;
Wed, 27 Sep 1995 17:03:58 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: gardo@vnet.ibm.com
Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by guelah.nexen.com
(8.6.12/8.6.12) with SMTP id QAA09651; Wed, 27 Sep 1995 16:57:01 -0400
Message-Id: <199509272057.QAA09651@guelah.nexen.com>
Received: from RALVM29 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 8683;
Wed, 27 Sep 95 16:59:21 EDT
Date: Wed, 27 Sep 95 16:15:26 EDT
To: rolc@nexen.com
cc: CDEBRUIN@vnet.ibm.com, genecox@vnet.ibm.com, malis@nexen.com
Subject: Request-ID and Destination Prefix Extension
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/
I understand why the request-id is included in the PURGE packet. But, I don't understand why the destination prefix is an optional extension. I would prefer the destination prefix be included in the "Mandatory Part" of the Reply and Purge. I'm just not very excited about having to purge with a request-id. In fact, I'm not very fond of the request-id in any of the NHRP packets. :-) Have a nice day! -- Russell