Re: Karl Fox's suggestion of rejecting MRRU

Karl Fox <karl@morningstar.com> Thu, 15 February 1996 22:10 UTC

Resent-Date: Thu, 15 Feb 1996 16:49:37 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Karl Fox <karl@morningstar.com>
Date: Thu, 15 Feb 1996 16:46:18 -0500
Message-Id: <9602152146.AA04543@gefilte.MorningStar.Com>
To: Tom Coradetti <70761.1664@compuserve.com>
Cc: "INTERNET:ietf-ppp@MERIT.EDU" <ietf-ppp@merit.edu>
Subject: Re: Karl Fox's suggestion of rejecting MRRU
In-Reply-To: <960215173720_70761.1664_EHM47-6@CompuServe.COM>
References: <960215173720_70761.1664_EHM47-6@CompuServe.COM>
Reply-To: Karl Fox <karl@morningstar.com>
Organization: Morning Star Technologies, Inc.
Resent-Message-ID: <"AKiMf2.0.AY.ifw8n"@merit.edu>
Resent-From: ietf-ppp@merit.edu
Precedence: list
Resent-Sender: ietf-ppp-request@merit.edu

Tom Coradetti writes:
> Reacting to a problem discovered during ED processing by involving
> the MRRU can't be a good way to resolve the problem.

I responded too quickly; of course you are right.

> I continue to recommend that ED should never be config-nak'd.

This *MUST* be true.  After all, the configuration option says who I
am.  Is someone else going to know that better than I?

> (1) If you don't have capacity to add a new bundle, then clearly the
> MUST in the original text can not be complied with. The text has to
> change for that reason.

True.  However, as has been pointed out, we won't even have all the
information until after Authentication Phase.  Please, let's allow LCP
and NCP negotiation to simply negotiate.  Policy decisions can easily
be done afterwards, in this case by sending a Terminate-Request.
-- 
Karl Fox, servant of God, employee of Morning Star Technologies
3518 Riverside Drive, Suite 101, Columbus, Ohio 43221    +1 614 451 1883

Re: Karl Fox's suggestion of rejecting MRRU Karl Fox
Re: Karl Fox's suggestion of rejecting MRRU Dana Blair