RE: [Pppext] Re: Last Call: 'Accommodating an MTU/MRU greater than1492in PPPoE' to Informational RFC

Pekka Savola <[email protected]> Thu, 23 Feb 2006 08:26:21 +0200 (EET)

Newsgroups	gmane.ietf.general,gmane.ietf.pppext
Message-ID	<[email protected]>

On Tue, 21 Feb 2006, Peter Arberg wrote:
> It will without a doubt make the solution more robust if the echo test
> was performed upon setup, and we could change the recommendation to not
> specific say this capability SHOULD be disabled, so changing it from
> ---
>   This capability SHOULD be disabled by default, and SHOULD only be
>   available for debug, test purpose.
> ---
>
> to something like this:
>
> ---
>   This capability MAY be disabled by default, but SHOULD be
>   available for debug, test purpose.
> ---
> if you think that will make it a little better.

Couldn't we say even more than that, simply like:

     This capability SHOULD be used by default.

or:

     This capability SHOULD be used by default to verify that the
     negotiated MTU/MRU actually works.

That would allow anyone to disable it (or not implement it) and still 
be compliant with the spec.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
Ietf mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf