Andy> I012)
Wes> 7.3 example shows the use of ftp. Can we use something more secure in
Wes> the example please?
Andy> ** CLOSED **
Andy> No change; no suggested replacement text provided
Suggested new text:
Example:
<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<copy-config>
<source>
<url>https://user@example.com:passphrase/configs/testbed-dec10.txt</url>
</source>
<target>
<running/>
</target>
</copy-config>
</rpc>
--------------------
Andy> I013)
Andy> I014)
Andy> I015)
Wes> 7.4: #url allows a url to appear as a delete. doing remote file
Wes> management using netconf is questionable at best. From a security
Wes> point of view, it makes me cringe.
...
Andy> ** CLOSED **
Andy> No change; no suggested replacement text provided
Suggested text: Add to 8.8.5.1:
If this parameter contains a URL, then it should identify a local
configuration file.
(this text exists for delete-config already)
----------------------
New text for the beginning of appendix B:
The following XML schema is for informational purposes. It has
reviewed but there is no guarantee that the schema exactly matches the
definitions defined in the protocol description above.
Implementations MUST NOT assume that an incoming message is free from
malicious intent because it has been successfully verified against
this schema.
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
--
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/>