…used by the RFC Editor) around 2014. It obsoletes the original version ("v1") [ RFC2629 ], which contained the original language definition and which was subsequently extended. Many of the changes leading to version 2 have been described in "Writing I-Ds and RFCs using XML (revis…
…cument. This document was written using the xml2rfc tool described in RFC 2629 [RFC2629]. Extensive input was received from the other members of the NETCONF design team, including: Andy Bierman, Weijing Chen, Rob Enns, Wes Hardaker, David Harrington, Eliot Lear, Simon Leinen, Phi…
…ument. This document was written using the xml2rfc tool described in RFC 2629 [ RFC2629 ]. Extensive input was received from the other members of the NETCONF design team, including: Andy Bierman, Weijing Chen, Rob Enns, Wes Hardaker, David Harrington, Eliot Lear, Simon Leinen, Ph…
…arser-gfm-1.1.0 Kramdown parser for the GFM dialect of Markdown ruby33-kramdown-rfc2629-1.7.35 IETF RFC 2629 back end for kramdown ruby33-launchy-2.5.2 Ruby class for launching applications ruby33-lazy_priority_queue-0.1.1 Priority queue implemented using a lazy binomial heap rub…
…Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616 , June 1999. [ RFC2629 ] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629 , June 1999. [ RFC2703 ] Klyne, G., "Protocol-independent Content Negotiation Framework", RFC 2703 , September 1999. [ RFC2781 ] Hoffman…
…. Acknowledgments This document was written using the xml2rfc tool described in RFC2629 [ 4 ]. The authors wish to thank Chris Lonvick, Anton Okmianski, David Harrington, Tom Petch, and all other people who commented on various versions of this proposal. 11 . Notes to the RFC Edi…
…cations: ABNF", STD 68, RFC 5234 , January 2008. 7.2 . Informative References [ RFC2629 ] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629 , June 1999. [ RFC4395 ] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35 ,…
…cations: ABNF", STD 68, RFC 5234 , January 2008. 7.2 . Informative References [ RFC2629 ] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629 , June 1999. [ RFC4395 ] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35 ,…
…2001 Added Julian Reschke as author. Chapter about QSD re-added. Formatted into RFC2629-compliant XML document. Added first comments. ID version number kicked up to draft-dasl-protocol-03. October 17, 2001 Updated address information for Jim Davis. Added issue of datatype vocabul…
…ner, Fred Baker and others. This document was produced using the xml2rfc tool ( RFC2629 ). Author's Address Brian Carpenter (ed.), IESG Email: iesg@ietf.org
…xml version="1.0"?> <!DOCTYPE rfc [ <!-- allow later RFC 2629 reference using "&rfc2629;" --> <!-- the data will be fetched from xml2rfc.ietf.org --> <!ENTITY rfc2629 PUBLIC "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml"> ]> It should say: <?xml version="1.0"?…
…. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616 , June 1999. RFC2629 ] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629 June 1999. RFC2703 ] Klyne, G., "Protocol-independent Content Negotiation Framework", RFC 2703 , September 1999. RFC2781 ] Hoffman, P. a…
…xml version="1.0"?> <!DOCTYPE rfc [ <!-- allow later RFC 2629 reference using "&rfc2629;" --> <!-- the data will be fetched from xml2rfc.ietf.org --> <!ENTITY rfc2629 PUBLIC "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml"> ]> It should say: <?xml version="1.0"?…