<!-- Complete set of Processing Instructions with default values -->

<!-- ***** File Inclusion ***** -->
<!-- The parameter value is the name of the file to be included which can also be a URI. 
     In the case of local files the XML_LIBRARY environment variable provides a search
     path of directories in which the file may be located. See section 4.1.2 of README -->
<?rfc include="n/a" ?>

<!-- ***** Rigor Control ***** -->
<!-- Try to enforce the ID-nits conventions and DTD validity -->
<?rfc strict="no" ?>

<!-- ***** Rendering Control ***** -->
<!-- Put the famous header block on the first page -->
<?rfc topblock="yes" ?>
<!-- Include boilerplate from Section 10.4(d) of [1] (Bradner, S., "The Internet Standards 
     Process -- Revision 3," October 1996.) -->
<?rfc iprnotified="no" ?>

<!-- Use anchors as symbolic tags rather than numbers for references -->
<?rfc symrefs="no" ?>
<!-- Sort references according to symbolic tags - irrelevant if symrefs="no" -->
<?rfc sortrefs="no" ?>

<!-- Items useful for reviewing document -->
<!-- Render <cref> information -->
<?rfc comments="no" ?>
<!-- If comments is "yes", then render comments inline; otherwise render them in an 
     "Editorial Comments" section" -->
<?rfc inline="no" ?>
<!-- Insert editing marks for ease of discussing draft versions.
     Editing marks are strings such as <29> printed at the beginning of the blank line before
     each paragrpah of text. -->
<?rfc editing="no" ?>

<!-- Items useful when using xml2rfc to produce technical documents other than RFCs and I-Ds -->
<!-- Produce a private memo rather than an RFC or Internet-Draft.
     The value of the PI is used as the title of the document.
     Omits the topblock and standard boiler plate when . -->
<?rfc private="" ?>
<!-- Override the center footer string -->
<?rfc footer="" ?>
<!-- Override the leftmost header string -->
<?rfc header="" ?>

<!-- New items in v1.31 of xml2rfc - Not available in v1.30 and earlier -->
<!-- Attempt to closely follow finer details from the latest observable RFC-Editor style so as
     to minimize the probability of being sent back for corrections after submission as an RFC;
     this directive is a kludge whose exact behavior is likely to change on a regular basis to
     match the current flavor of the month; presently, it will capitalize the adjective "This"
     in automatically generated headings, use the variant "acknowledgement" spelling instead
     of Merriam Webster's main "acknowledgment" dictionary entry, use the "eMail" spelling
     instead of Knuth's more modern "email" spelling, only put one blank line instead of two
     before top sections, omit "Intellectual Property and Copyright Statements" and
     "Author's Address" from the table of content, and not limit the indentation to a maximum
     tag length in <references> sections." if the value is yes. -->
<?rfc rfcedstyle="no" ?>
<!-- If there already is an automatically generated Acknowledg(e)ment section, pluralize 
     its title and add a short sentence acknowledging that xml2rfc was used in the document's 
     production to process an input XML source file in RFC-2629 format. -->
<?rfc rfcprocack="no" ?>

<!-- ***** Table of Contents Control ***** -->
<!-- Generate a table-of-contents -->
<?rfc toc="no" ?>
<!-- Control whether the word "Appendix" appears in the table of contents. -->
<?rfc tocappendix="yes" ?>
<!-- If toc is "yes", then this determines the depth of the table of contents. -->
<?rfc tocdepth="3" ?>
<!-- If toc is "yes", then setting this to "yes" will indent subsections in 
     the table-of-contents. -->
<?rfc tocindent="yes" ?>
<!-- If toc is "yes", then setting this to "no" will make it a little less compact. -->
<?rfc tocompact="yes" ?>
<!-- Affects horizontal spacing in the table-of-content. -->
<?rfc tocnarrow="yes" ?>

<!-- ***** Format Control ***** -->
<!-- Automatically force page breaks to avoid widows and orphans (not perfect). -->
<?rfc autobreaks="yes" ?>
<!-- Put two spaces instead of one after each colon (":") in txt or nroff files. -->
<?rfc colonspace="no" ?>
<!-- When producing a txt/nroff file, try to conserve vertical whitespace 
    (the default value was "no" up to v1.30; from v1.31 the default is the current value 
    of the rfcedstyle PI).
    Will default to (rfcedstyle) in future. -->
<?rfc compact="no" ?>
<!-- If compact is "yes", then you can make things a little less compact by setting this 
     to "no" (the default value is the current value of the compact PI). -->
<?rfc subcompact="no" ?>
<!-- An integer hint indicating how many contiguous lines are needed at this point in 
     the output.
     Can appear as many times as necessary in the source. -->
<?rfc needLines="0" ?>

<!-- ***** HTML Specials ***** -->
<!-- When producing a html file, use the image in this file.  -->
<?rfc background="" ?>
<!-- Automatically replaces input sequences such as |*text| by,
     e.g., <strong>text</strong> in html output. -->
<?rfc emoticonic="no" ?>
<!-- Generate mailto: URL, as appropriate. -->
<?rfc linkmailto="yes" ?>
<!-- When producing a html file, produce multiple files for a slide show. -->
<?rfc slides="no" ?>
<!-- When producing a html file, use the <object> html element with inner replacement content 
     instead of the <img> html element, when a source xml element includes an src attribute. -->
<?rfc useobject="no" ?>

<!-- ***** Debugging ***** -->
<!-- Value is a string like "35:file.xml" or just "35" (file name then defaults to the 
     containing file's real name or to the latest linefile specification that changed it) that 
     will be used to override xml2rfc's reckoning of the current input position 
     (right after this PI) for warning and error reporting purposes 
     (line numbers are 1-based)" -->
<?rfc linefile="n/a" ?>
<!-- During processing pass 2, print the value to standard output at that point 
     in processing" -->
<?rfc typeout="n/a" ?>

