Bernie Volz (volz) wrote:

> So, I think we want to drop or replace the LAST paragarph in section
> 3.3.1 of draft-ietf-dhc-fqdn-option-11.txt.


Sure.

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


We should also give reference to section 2.3.3.

We don't have to say anything about "character-sets".

So, the text could be:

> 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 the full binary octet
> capabilities in names" as described in section 2.3.3 of RFC1035.


Masataka Ohta



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