nhrp-05 ????? - Destination Prefix Extension
gardo@vnet.ibm.com Sun, 05 November 1995 21:48 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11302;
5 Nov 95 16:48 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa11294;
5 Nov 95 16:48 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 QAA17260;
Sun, 5 Nov 1995 16:23:24 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
QAA17840 for rolc-out; Sun, 5 Nov 1995 16:27:58 -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 QAA17831;
Sun, 5 Nov 1995 16:27:55 -0500
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 QAA17248; Sun, 5 Nov 1995 16:14:26 -0500
Message-Id: <199511052114.QAA17248@guelah.nexen.com>
Received: from RALVM29 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 4877;
Sun, 05 Nov 95 16:21:45 EST
Date: Sun, 5 Nov 95 16:21:45 EST
To: asmith@baynetworks.com, luciani@nexen.com, bcole@cisco.com
cc: rolc@nexen.com, genecox@vnet.ibm.com
Subject: nhrp-05 ????? - 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/
Ref: Your note of Fri, 3 Nov 95 15:29:22 PST
On Wed, 25 Oct 1995 asmith@BayNetworks.COM wrote: >Date: Fri, 3 Nov 95 15:29:22 PST >From: asmith@BayNetworks.COM (Andrew Smith) >Message-Id: <9511032329.AA03000@milliways-le0.engwest> >To: gardo@VNET.IBM.COM >Subject: Re: nhrp-05 ????? - Destination Prefix Extension > >I think we should try to simplify the protocol by allowing fewer options. >I believe that the overall system complexity will be lower, even if >individual client complexity is higher (think globally, act locally :-)) >if we insist all clients behave the same in this regard. > >> Therefore, why not add another extension called the "purge mask >> extension" with the discretionary flag = 0. This way the destination >> prefix extension in the Reply can remain a discretionary extension. >> Maybe this proposal is acceptable? This proposal addresses the >> following problems: > >> 1) No flags in the dest prefix extension used in Reply packets >Good! > >> 2) Destination Prefix Extension remains discretionary >Is it a feature or a bug that it is discretionary? > >> 3) Only clients that support a purge with mask will receive this >> extension >> 4) The new extension is not discretionary, never ignored... >You've effectively moved the problem back to a once-off initialisation-time >negotiation. I'd rather have no negotiation at all: make it mandatory! I agree to make it mandatory; my preference is to make it mandatory (put it in the mandatory part), but there are objections to making it mandatory (see below). I am concerned that the mask will never get added anywhere if there is not a compromise. So, my second choice is: Put the mask in a non-discretionary extension. I believe this is an acceptable compromise. Does anyone disagree? On Wed, 25 Oct 1995 luciani@nexen.com wrote: >To: gardo@vnet.ibm.com >Subject: Re: clarification on the Purge format direction/status/positions >cc: rolc@nexen.com >Date: Fri, 03 Nov 1995 18:28:27 -0500 >From: James Luciani <luciani@nexen.com> > >Russell, > >Maybe you were not listening but I objected to making this MANDATORY >though I am in favor of its use on a discretionary basis. [...] >> It's not clear if there are objections to the above proposal: >> Are there any objections to putting the mask in the mandatory, >> protocol-specific part of the Purge packet? Therefore, why not add an extension called the "purge mask extension" with the discretionary flag = 0. This way the destination prefix extension in the Reply can remain a discretionary extension. Does anyone object, other than Andrew? :-) -- Russell
- Re: nhrp-05 ????? - Destination Prefix Extension gardo
- Re: nhrp-05 ????? - Destination Prefix Extension Bruce Cole
- nhrp-05 ????? - Destination Prefix Extension gardo
- Re: nhrp-05 ????? - Destination Prefix Extension Bruce Cole
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith
- Re: nhrp-05 ????? - Destination Prefix Extension debruin
- Re: nhrp-05 ????? - Destination Prefix Extension Bruce Cole
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith
- nhrp-05 ????? - Destination Prefix Extension gardo
- Re: nhrp-05 ????? - Destination Prefix Extension debruin
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith
- nhrp-05 ????? - Destination Prefix Extension gardo
- Re: nhrp-05 ????? - Destination Prefix Extension Andrew Smith