[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Additional comments on draft-ietf-radext-management-authorization-03.txt

To: <radiusext@ops.ietf.org>
Subject: RE: Additional comments on draft-ietf-radext-management-authorization-03.txt
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Tue, 8 Jul 2008 13:22:22 -0400
Cc: "'Bernard Aboba'" <bernard_aboba@hotmail.com>
In-reply-to: <BLU137-W102AA273611F540968B18293940@phx.gbl>
Organization: Elbrys Networks, Inc.
References: <Pine.LNX.4.64.0806240735140.18995@internaut.com> <69C61DEE097F4E5AB1582222AB04AFBC@xpsuperdvd2> <BLU137-W102AA273611F540968B18293940@phx.gbl>

Bernard Aboba writes...

> > > "MAY use these hint attributes" -> "may use these attributes
> > > as a hint" 
> > OK, but why "MAY" --> "may"?
> 
> Hints are inherently optional.

Well, quoting RFC 2119:

   MAY   This word, or the adjective "OPTIONAL", mean that an
   item is truly optional.

Since MAY means "truly optional", which I can't distinguish from "inherently
optional", I'm proposing to leave the text as is.  :-)



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- Additional comments on draft-ietf-radext-management-authorization-03.txt
  - From: Bernard Aboba <aboba@internaut.com>
- RE: Additional comments on draft-ietf-radext-management-authorization-03.txt
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>

Prev by Date: Re: REMINDER: RADEXT WG Last Call on Design Guidelines Document
Next by Date: RE: REMINDER: RADEXT WG Last Call on Design Guidelines Document
Previous by thread: RE: Additional comments on draft-ietf-radext-management-authorization-03.txt
Next by thread: RE: Additional comments on draft-ietf-radext-management-authorization-03.txt
Index(es):
- Date
- Thread