Re: nhrp-05 ????? - Destination Prefix Extension

Andrew Smith <asmith@baynetworks.com> Mon, 06 November 1995 16:04 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13782; 6 Nov 95 11:04 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa13776; 6 Nov 95 11:04 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 KAA19461; Mon, 6 Nov 1995 10:31:59 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id KAA23147 for rolc-out; Mon, 6 Nov 1995 10:38:35 -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 KAA23138; Mon, 6 Nov 1995 10:38:32 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id KAA19360; Mon, 6 Nov 1995 10:25:00 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA05340; Mon, 6 Nov 95 07:32:13 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA11527; Mon, 6 Nov 95 07:33:37 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA04550; Mon, 6 Nov 95 07:33:35 PST
Date: Mon, 6 Nov 95 07:33:35 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511061533.AA04550@milliways-le0.engwest>
To: luciani@nexen.com, gardo@vnet.ibm.com
Subject: Re: nhrp-05 ????? - Destination Prefix Extension
Cc: rolc@nexen.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/

> From gardo@VNET.IBM.COM Sun Nov  5 13:21:59 1995
> Date: Sun, 5 Nov 95 16:21:45 EST
> From: gardo@VNET.IBM.COM
> To: asmith@BayNetworks.COM, luciani@nexen.com, bcole@cisco.com
> Cc: rolc@nexen.com, genecox@VNET.IBM.COM
> Subject: nhrp-05 ????? - Destination Prefix Extension

> 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?

I'd rather hear some more about Jim's objection to making it mandatory
first. Jim?


Andrew


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy Unit				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************


> 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
>