|
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 Watsen Software Architect Juniper Networks |