RE: Proposed Resolution to Issue 198: Attribute Concatenation/Splitting

["Bernard Aboba" <bernard_aboba@hotmail.com>]

OK.  Suggest changing this to:

"A robust implementation SHOULD support the field as undistinguished 
octets."



> From: <Pasi.Eronen@nokia.com>
> To: <bernard_aboba@hotmail.com>, <radiusext@ops.ietf.org>
> Subject: RE: Proposed Resolution to Issue 198: Attribute 
> Concatenation/Splitting
> Date: Fri, 29 Sep 2006 12:50:04 +0300
>
> Bernard Aboba wrote:
>
> > The text of Issue 198 is enclosed below.  The proposed
> > resolution is as follows:
>
> Works for me (as would many of the other alternatives).
>
> One minor nit:
>
> > The String field is one or more octets.  It contains filter rules in
> > the IPFilterRule syntax defined in [RFC3588] Section 4.3.  [RFC3629]
> > UTF-8 encoded 10646 characters are RECOMMENDED, but a robust
> > implementation SHOULD support the field as undistinguished octets.
>
> If it follows the IPFilterRule syntax, it never contains any characters
> not part of US-ASCII, so mentioning UTF-8 is sort of redundant...
>
> Best regards,
> Pasi



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