Re: Character encoding for Netconf messages?

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Kent Watsen" <kwatsen@juniper.net>
> Cc: "McDonald, Ira" <imcdonald@sharplabs.com>; "Randy Presuhn" <randy_presuhn@mindspring.com>; <netconf@ops.ietf.org>
> Sent: Wednesday, August 09, 2006 3:56 PM
> Subject: Re: Character encoding for Netconf messages?
...
> Why does the NETCONF protocol have to specify the XML encoding scheme?
...

BCP 18 (RFC 2277) clause 3.1:

| 3.1.  What charset to use
|
|   All protocols MUST identify, for all character data, which charset is
|   in use.

Seems rather clear.  Are you proposing that we ask the IESG for
an exception?

BCP 18 continues:

|   Protocols MUST be able to use the UTF-8 charset, which consists of
|   the ISO 10646 coded character set combined with the UTF-8 character
|   encoding scheme, as defined in [10646] Annex R (published in
|   Amendment 2), for all text.

This also seems rather clear.

What's the rationale for not addressing these requirements?

Randy


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