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



--On 2. februar 2006 23:12 -0500 "Bernie Volz (volz)" =20
wrote:

> Actually, I do now have a suggestion:
>
> Clients and servers SHOULD follow the character-set recommendations
> of RFC 1035 section 2.3.1. However, implementers SHOULD also
> be aware that some client software may use other character-sets.
> This specification does not require support for any other
> character-sets.
>
> If you don't like this, PLEASE SUGGEST ALTERNATIVE TEXT.


Bernie - are my messages not getting through to the DHCWG list?

I like this text, but you need to add the reference to RFC 1123 section 2.1 =

I mentioned earlier (the text that allows 3com) - and Mark Andrews seems to =

want to reference RFC 952 rather than RFC 1035.

My suggestion (slight modification) would be:

> Clients and servers SHOULD follow the character-set recommendations
> of RFC 1035 section 2.3.1, 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 any other
> character sets.


If referring to 952:

Clients and servers SHOULD follow the character-set rules of RFC 952,
fourth section, first 2 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 any other
character sets.

That's specific...

Harald


--==========5947F3AB260E64470B3A==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQFD4wV2OMj+2+WY0F4RAhTsAKDHkND0Z8wF4EaiYDFwBH 4YQ/p2mQCfYQ42
T2tUN+aCVfNDVB33LKs+Vhg=
=csid
-----END PGP SIGNATURE-----

--==========5947F3AB260E64470B3A==========--


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