Re: Character encoding for Netconf messages?

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

Hi -

If we specify a mandatory-to-implement encoding, I'd strongly suggest
that it be UTF-8.

Randy

----- Original Message ----- 
From: "Kent Watsen" <kwatsen@juniper.net>
To: <netconf@ops.ietf.org>
Sent: Tuesday, July 25, 2006 7:46 PM
Subject: Character encoding for Netconf messages?




The Netconf spec does not require XML declarations (i.e. <?xml
version="1.0" encoding="UTF-8" ?>).  However, both the SSH and SOAP
mapping specs show the use of XML declarations; though the BEEP mapping
spec does not...  

 

Should NetConf specify a mandatory encoding (e.g. USASCII) or leave it
up to implementations to decide?   If it is up to the implementations to
decide, then would that require the client to defer sending its <hello>
until after receiving the server's <hello> in order to determine the
encoding to use?

 

Would it make sense for the <hello> to be USASCII and to list all
supported encodings as capabilities? - this seems flexible but then the
NetConf spec would need to require an XML declaration on every message

 

Thanks!

Kent

 

--

Kent Watsen

Software Architect

Juniper Networks

 




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