[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
impending publication of the NETCONF BEEP mapping - one final concern
- To: netconf <netconf@ops.ietf.org>
- Subject: impending publication of the NETCONF BEEP mapping - one final concern
- From: Eliot Lear <lear@cisco.com>
- Date: Wed, 15 Nov 2006 11:32:45 +0100
- Authentication-results: sj-dkim-7; header.From=lear@cisco.com; dkim=pass (si g from cisco.com/sjdkim7002 verified; ); header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/oregon verified; );
- Cc: RFC Editor <rfc-editor@rfc-editor.org>, kkken <ken.crozier@gmail.com>, "Marshall T. Rose" <mrose@dbc.mtview.ca.us>
- Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1171; t=1163586769; x=1164450769; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20impending=20publication=20of=20the=20NETCONF=20BEEP=20mapping =20-=20one=20final=20concern |Sender:=20; bh=9SmRC/DGDpdsKZVT0bHOE8KTt0J4GjDMLU+keU2beig=; b=JZiIkXDZ1ueXW4B7eYtoya7NzWYr+0CwMr5CcpczbpE7gzDleuH1qm1djkBdEfrgO/P1qsrL cJrE5r28loeAsCVWDHoKhB4YXOQdjPcK3b3hfs1FScqA7BAIXBhg369/;
- Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1171; t=1163585945; x=1164449945; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20impending=20publication=20of=20the=20NETCONF=20BEEP=20mapping =20-=20one=20final=20concern |Sender:=20 |To:=20netconf=20<netconf@ops.ietf.org>; bh=9SmRC/DGDpdsKZVT0bHOE8KTt0J4GjDMLU+keU2beig=; b=mbhnbUieO7kNmMJmkOloWNek8HAHAdnZ1ILFE48ffyg5r+JEWqlaP6bNNFiMf3AriHOUZNJ5 ojftYnvsS25OT9Wzt1/8QPnIuW8Dhqndz5QBs2ifVCeG9YhCx3JP90wo;
- User-agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
Dear all,
After last call, a concern was raised regarding the NETCONF / BEEP
application mapping that is due to be released, relating to the lack of
<?xml version="1.0" encoding="UTF-8"?> in the <hello> message. I would
like to clarify why this is the case on the mailing list, and I will
clarify this in the netconf-beep mapping.
Section 6.4 of RFC 3080 registers the MIME subtype
application/beep+xml. That registration specifically specifies two
restrictions, relating to the XML:
First, no entity references other than the five predefined general
entities references ("&", "<", ">", "'", and
""") and numeric entity references may be present.
Second, neither the "XML" declaration (e.g., <?xml version="1.0"
?>) nor the "DOCTYPE" declaration (e.g., <!DOCTYPE ...>) may be
present. (Accordingly, if another character set other than UTF-8
is desired, then the "charset" parameter must be present.)
For this reason the example listed in draft-ietf-netconf-beep-10.txt
varies from that listed in draft-ietf-netconf-ssh-06.txt (amongst other
ways).
Regards,
Eliot
--
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/>