--==========1399869266E8D596B77B==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline



--On 3. februar 2006 17:54 -0500 "Bernie Volz (volz)" =20
wrote:

> So, I'll change the text to what you suggested with one minor change:
>
> Clients and servers SHOULD follow the character-set rules of RFC 952,
> fourth section ("Assumptions"), first 5 sentences, as modified by RFC
> 1123 section 2.1. However, implementers SHOULD also be aware that
> some client software may send data intended to be in other character
> sets. This specification does not require support for other character
> sets.
>
> Note that I changed it to cover the 5 sentences because I believe the
> additional sentences are required (lower case and space rules)?


Agreed - my writing was sloppy; I wanted to avoid the "-gw" language, but=20
saying "character set rules" accomplishes that.
(Do omit the hyphen..... "character set" is much more common than=20
"character-set"...)

Harald


--==========1399869266E8D596B77B==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFD4+v5OMj+2+WY0F4RAm7ZAKDpJqCnQG+wLR6GLEJJd/ormIpeowCgqYBJ
j7mUJcVniX4nzio5FpecbY0=
=8bf6
-----END PGP SIGNATURE-----

--==========1399869266E8D596B77B==========--


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: