doc/rfc-ja/rfc2629-ja.html

<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html>
<head profile="http://suika.fam.cx/~wakaba/lang/rfc/translation/html-profile">
<meta http-equiv="Content-Style-Type" content="text/css"/>
<title>
      RFC 2629: 
    XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B (Writing I-Ds and RFCs using XML)
    </title>
<link rel="stylesheet" href="http://suika.fam.cx/~wakaba/lang/rfc/translation/rfc-ja-style.css" type="text/css"/>
<meta name="ietf-area" content="General"/>
<meta name="keyword" xml:lang="en" content="RFC, Request for Comments, I-D, Internet-Draft, XML, Extensible Markup Language, "/>
<meta name="keyword" content="$B3HD%%^!<%/IU$18@8l(B, "/>
</head>
<body>
<div id="rfc--table">
<ul id="rfc--table-left">
<li>Network Working Group</li>
<li>Request for Comments: 2629</li>
<li>
<span class="t-pair">
<span xml:lang="en" class="t-l-en">Category: Informational</span>
</span>
</li>
<li>
<span class="t-pair">
<span xml:lang="ja" class="t-l-ja">$BJ,N`(B: $B;29M(B</span>
</span>
</li>
</ul>
<ul id="rfc--table-right">
<li title="Marshall T. Rose">M.T. Rose</li>
<li>Invisible Worlds, Inc.</li>
<li>
<span class="t-pair">
<span xml:lang="en" class="t-l-en"> June 1999</span>
</span>
</li>
<li>
<span class="t-pair">
<span xml:lang="ja" class="t-l-ja">1999$BG/(B6$B7n(B</span>
</span>
</li>
</ul>
</div>
<div class="t-pair t-heading" id="rfc-title">
<h1 class="rfc-title t-l-en" xml:lang="en">Writing I-Ds and RFCs using XML</h1>
<h1 class="rfc-title t-l-ja" xml:lang="ja">XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B</h1>
</div>
<div id="rfc-status" class="rfc-section">
<div class="t-pair">
<h1 xml:lang="en" class="t-l-en">Status of this Memo</h1>
<h1 xml:lang="ja" class="t-l-ja">$B$3$N%a%b$N0LCVIU$1(B</h1>
</div>
<div class="rfc-t">
<div class="t-pair">
<p class="t-l-en" xml:lang="en">
          This memo provides information for the Internet community.
          It does not specify an Internet standard of any kind.
          Distribution of this memo is unlimited.
        </p>
<p class="t-l-ja" xml:lang="ja">
          $B$3$N%a%b$O!"(B Internet $B<R2q$K>pJs$rDs6!$7$^$9!#$$$+$J$k<oN`$N(B
          Internet $BI8=`$r5,Dj$9$k$b$N$G$b$"$j$^$;$s!#$3$N%a%b$NG[I[$O@)8B$7$^$;$s!#(B
        </p>
</div>
</div>
</div>
<div id="rfc-copyright-notice" class="rfc-section">
<div class="t-pair">
<h1 xml:lang="en" class="t-l-en">Copyright Notice</h1>
<h1 xml:lang="ja" class="t-l-ja">$BCx:n8"I=<((B</h1>
</div>
<div class="t-pair t-hide-no">
<p class="t-l-en" xml:lang="en">Copyright &#x00A9; 
        <a href="http://www.isoc.org/">The Internet Society</a> 
        (1999). 
        All Rights Reserved.</p>
<p class="t-l-ja" xml:lang="ja">$BCx:n8"(B &#x00A9; 
        <a href="http://www.isoc.org/">The Internet Society</a> 
        (1999)$B!#A48"J]N1!#(B</p>
</div>
</div>
<div class="rfc-section" id="rfc.abstract">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en">Abstract</h1>
<h1 xml:lang="ja" class="t-l-ja">$B35MW(B</h1>
</div>
  <div class="rfc-t" xmlns="http://www.w3.org/1999/xhtml">
    <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
      This memo presents a technique for using XML
      (Extensible Markup Language)
      as a source format for documents in the Internet-Drafts (I-Ds) 
      and Request for Comments (RFC) series.
    </p>
<p xml:lang="ja" class="t-l-ja">
      $B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B Internet-Draft (I-D)
      $B$d(B Request for Comments (RFC) $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B
    </p>
</div>
  </div>
</div>

<div class="rfc-section" id="rfc.section.1">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">1. Introduction</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">1. 
          $B$O$8$a$K(B</h1>
</div>
<div class="rfc-t" id="rfc.section.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    This memo describes how to write a document for the I-D and 
    RFC series using <span class="rfc-xref">
<a href="#XML" title="Extensible Markup Language (XML) 1.0">the Extensible Markup 
    Language
          &#x00A0;<sup>[1]</sup>
</a>
</span> (XML). This memo has three goals:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$N%a%b$O!"(B I-D $B$*$h$S(B RFC 
    $B7ONs$NJ8=q$r(B<a href="#XML" title="$B3HD%2DG=%^!<%/IU$18@8l(B (XML) 1.0">$B3HD%%^!<%/IU$18@8l(B
          &#x00A0;<sup>[1]</sup>
</a> (XML)
    $B$r;H$C$F=q$/J}K!$r@bL@$7$^$9!#$3$N%a%b$K$O!";0$D$NL\E*$,$"$j$^$9!#(B
  </p>
</div>
  
<ol class="rfc-list-numbers text" xmlns="">
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    To describe a simple XML Document Type Definition (DTD) that is
powerful enough to handle the simple formatting requirements of RFC-like
documents whilst allowing for meaningful markup of descriptive
qualities.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B0UL#%^!<%/IU$1$N5-=RIJ<A$,2DG=$J(B RFC
    $B7?J8=q$NC1=c$J=q<0$E$1MW7o$r<h$j07$&$N$K==J,6/NO$G$"$k(B XML 
    $BJ8=q7?Dj5A(B (DTD) $B$N@bL@(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    To describe software that processes XML source files,
including a tool that produces documents
conforming to <span class="rfc-xref">
<a href="#refs.RFC2223" title="Instructions to RFC Authors">RFC 2223
          &#x00A0;<sup>[2]</sup>
</a>
</span>,
HTML format, and so on.
  </p>
<p xml:lang="ja" class="t-l-ja">
    <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">RFC 2223
          &#x00A0;<sup>[2]</sup>
</a> $B$KE,9g$9$kJ8=q(B,
    HTML $B7A<0(B, $B$=$NB>$r@8@.$9$kF;6q$r4^$`!"(B
    XML $B8;%U%!%$%k$r=hM}$9$k%=%U%H%&%'%"$N@bL@(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    To provide the proof-of-concept for the first two goals
(this memo was written using this DTD and produced using that
software).
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BA0=R$N(B2$B$D$NL\E*$N35G0$N>ZL@$NDs6!(B ($B$3$N%a%b$O$=$N(B DTD 
    $B$r;H$C$F<9I.$5$l!"$=$&$7$?%=%U%H%&%'%"$r;H$C$F@8@.$5$l$^$7$?!#(B)
  </p>
</div>
</li>
</ol>
</div>
<div class="rfc-t" id="rfc.section.1.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    It is beyond the scope of this memo to discuss the political
ramifications of using XML as a source format for RFC-like documents.
Rather,
it is simply noted that adding minimal markup to plain text:
  </p>
<p xml:lang="ja" class="t-l-ja">
    RFC $BE*J8=q$N8;7A<0$H$7$F(B XML $B$r;H$&$3$H$N@/<#E*5DO@$O$3$N%a%b$NE,MQHO0O30$G$9!#$=$l$h$j$b!"J?J8(B (plain text) $B$K:G>.$N%^!<%/IU$1$r2C$($k$3$H$G!"(B
  </p>
</div>
  
<ul class="rfc-list-symbols text" xmlns="">
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    allows the traditional production of textual RFC-like documents using
familiar editors;
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$h$/CN$i$l$F$$$k%(%G%#%?!<$r;H$C$FJ8;z$J(B RFC $BE*J8=q$NEAE}E*@8@.$,2DG=$K$J$k(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    requires some, albeit minimal, additions to existing software
environments; and,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B4v$D$+!":GDc$G$b!"4{B8$N%=%U%H%&%'%"4D6-$KDI2C$,I,MW$G$"$k(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    permits information to be organized, searched, and retrieved
using both unstructured and structured mechanisms.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BHs9=B$2=!&9=B$2=$NN>5!9=$r;H$C$F>pJs$rAH?%2=$7$?$j8!:w$7$?$j<h$j=P$7$?$j=PMh$k(B
  </p>
</div>
</li>
</ul>

  <div class="t-pair" xmlns="">
<p xml:lang="ja" class="t-l-ja">
    $B$H$$$&$3$H$rC1$K5-$9$b$N$G$9!#(B
  </p>
</div>
</div>
</div>

<div class="rfc-section" id="rfc.section.2">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2. Using the DTD to Write I-Ds and RFCs</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2. 
          I-D $B$d(B RFC $B$r=q$/$N$K(B DTD $B$r;H$&(B</h1>
</div>
<div class="rfc-t" id="rfc.section.2.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    We do not provide a formal or comprehensive description of XML.
Rather,
this section discusses just enough XML to use a Document Type
Declaration (DTD) to write RFC-like documents.
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B$K$D$$$F$N@5<0$J!"$"$k$$$OJq3gE*$J@bL@$O$7$^$;$s!#(B
    $B$3$N@a$G$O!"(B RFC $BE*J8=q$r=q$/$?$a$NJ8=q7?@k8@(B (DTD) 
    $B$r;H$&$N$KI,MW$J$@$1$NOC$r$7$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    If you're already familiar with XML,
skip to <span class="rfc-xref">
<a href="#rfc.dtd" title="The RFC DTD">
        section 2</a>
</span> to look at the DTD.
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B$K$D$$$F4{$K$h$/J,$+$C$F$$$k$J$i!"(B<a href="#rfc.dtd" title="The RFC DTD">
      $BImB0=q(BB</a>$B$KHt$s$G!"(B DTD $B$r8fMw2<$5$$!#(B
  </p>
</div>
</div>

<div class="rfc-section" id="rfc.section.2.1">
<div class="t-pair t-heading" id="xml_basics">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.1. XML basics</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.1. 
          XML $B$N4pAC(B</h2>
</div>
<div class="rfc-t" id="rfc.section.2.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    There are very few rules when writing in XML,
as the syntax is simple.
There are five terms you'll need to know:
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B$O9=J8$,4JC1$J$N$G!"=q$/;~$KI,MW$J$N$O$[$s$N>/$7$N5,B'$@$1$G$9!#CN$C$F$*$/$Y$-$3$H$O(B5$B$D$"$j$^$9!#(B
  </p>
</div>

<ol class="rfc-list-numbers text" xmlns="">
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    An $B!H(Belement$B!I(B usually refers to a start tag, an end tag, and all the
characters in between,
e.g.,
"&lt;example&gt;text and/or nested elements&lt;/example&gt;"
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!VMWAG!W$ODL>o3+;O%?%0$H=*N;%?%0!"$=$l$K4V$NA4$F$NJ8;z!"Nc$($P(B
    <samp>$B!V(B&lt;$BNc(B&gt;$BJ8;z$H$+F~$l;R$NMWAG(B&lt;/$BNc(B&gt;$B!W(B</samp>
    $B$r;X$7$^$9!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    An "empty element" combines the start tag and the end tag,
e.g.,
"&lt;empty/&gt;".
You don't find these in HTML.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!V6uMWAG!W$O3+;O%?%0$H=*N;%?%0$,$/$C$D$$$F!"(B 
    <samp>$B!V(B&lt;$B6u(B/&gt;$B!W(B</samp> $B$N$h$&$K$J$j$^$9!#(B 
    HTML $B$K$O$3$l$O$"$j$^$;$s!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    An "attribute" is part of an element.
If present, they occur in the start tag, e.g.,
"&lt;example name='value'&gt;".
Of course,
they can also appear in empty elements, e.g.,
"&lt;empty name='value'/&gt;".
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!VB0@-!W$OMWAG$N0lIt$G$9!#B8:_$9$k>l9g!"3+;O%?%0Cf$K!"(B
    <samp>$B!V(B&lt;$BNc(B $BL>A0(B='$BCM(B'&gt;$B!W(B</samp> 
    $B$NMM$K8=$l$^$9!#$b$A$m$s!"6uMWAGCf$G$b(B
    <samp>$B!V(B&lt;$B6u(B $BL>A0(B='$BCM(B'/&gt;$B!W(B</samp> $B$NMM$K;H$($^$9!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    An "entity" is a textual macro that starts with "&amp;".
Don't worry about these,
you'll only use them whenever you want to put a "&amp;" or a "&lt;" in
your text.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!V<BBN!W$OJ8;z%^%/%m$G!"!V(B&amp;$B!W$G;O$^$j$^$9!#(B
    $B$J!A$K?4G[$7$J$5$s$J!"!V(B&amp;$B!W$d!V(B&lt;$B!W$rJ8Cf$KF~$l$?$$;~$K$@$1$$$D$G$b;H$&$3$H$,=PMh$^$9!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    A "token" is a string of characters.
The first character is either a letter or an underscore ("_").
Any characters that follow are either letters, numbers, an
underscore, or a period (".").
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!V;z6g(B (token)$B!W(B $B$OJ8;z$NNs$G$9!#:G=i$NJ8;z$OJ8;z$+2<@~(B ($B!V(B_$B!W(B)
    $B$G$9!#$=$N8e$NJ8;z$OJ8;z!"?t;z!"2<@~!"6gE@(B ($B!V(B.$B!W(B) $B$G$9!#(B
    <ins class="t-note t-l-ja" xml:lang="ja">
    (<span class="t-note-title">$BLuCm(B:</span>$B$3$3$GJ8;z$H$O!"(B26$B!_(B2$B<oN`$N4pK\%i%F%s;zJl$N$3$H$G$9!#(B)
  </ins>
  </p>
</div>
</li>
</ol>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.1">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    First,
start your source file with an XML declaration,
a reference to the DTD,
and the "rfc" element:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G=i$K!"8;%U%!%$%k$O(B XML $B@k8@(B, DTD $B$X$N;2>H(B, $B!V(Brfc$B!WMWAG$G;O$a$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;?xml version="1.0"?&gt;
    &lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd"&gt;
    &lt;rfc&gt;
        ...
    &lt;/rfc&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Ignore the first two lines
$B!=!=(B the declaration and the reference $B!=!=(B
and simply treat them as opaque strings.
Nothing else should be present after the "&lt;/rfc&gt;" tag.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G=i$N(B2$B9T(B ($B@k8@$H;2>H(B) $B$OL5;k$7!"C1$K<vJ8$@$H;W$C$F2<$5$$!#(B
    $B!V(B&lt;/rfc&gt;$B!W%?%0$N8e$K$O2?$b8=$l$k$Y$-$G$O$"$j$^$;$s!#(B
    <ins class="t-note t-l-ja" xml:lang="ja">
    (<span class="t-note-title">$BLuCm(B:</span>rfc $BMWAG$K$D$$$F$O!"(B <a href="#rfc" title="rfc $BMWAG(B">
      $BImB0=q(BA</a> $B$K@bL@$,$"$j$^$9!#(B)
  </ins>
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.1.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Second,
make sure that all elements are properly matched and nested.
A properly matched element that starts with
"&lt;example&gt;" is eventually followed with "&lt;/example&gt;".
(Empty elements are always matched.)
Elements are properly nested when they don't overlap.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BFsHVL\$K!"A4$F$NMWAG$,E,@Z$KBP1~!&F~$l;R$K$J$C$F$$$k$+3N$+$a$F2<$5$$!#(B
    <samp>$B!V(B&lt;$BNc(B&gt;$B!W(B</samp> $B$G;O$^$kE,@Z$KBP1~$9$kMWAG$O!":G=*E*$K$O(B
    <samp>$B!V(B&lt;/$BNc(B&gt;$B!W(B</samp> $B$,B3$/$3$H$K$J$j$^$9!#(B
    ($B6uMWAG$O>o$KBP1~$7$F$$$^$9!#(B) 
    $B3FMWAG$O=EJ#$7$F$$$J$$;~$GE,@Z$KF~$l;R$K$J$C$F$$$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.2">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    For example,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BNc$($P!"(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;outer&gt;
        ...
        &lt;inner&gt;
            ...
        &lt;/inner&gt;
        ...
    &lt;/outer&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    is properly nested.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$OE,@Z$KF~$jAH$s$G$$$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.3">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    However,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$7$+$7!"(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;outer&gt;
        ...
        &lt;inner&gt;
            ...
        &lt;/outer&gt;
        ...
    &lt;/inner&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    overlaps, so the elements aren't properly nested.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$O=E$J$C$F$$$k$N$G!"MWAG$O@5$7$/F~$l;R$K$J$C$F$$$^$;$s!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.1.p.6" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Third,
never use "&lt;" or "&amp;" in your text.
Instead, use either "&amp;lt;" or "&amp;amp;", respectively.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B;0HVL\$K!"!V(B&lt;$B!W$d!V(B&amp;$B!W$rJ8Cf$K;H$C$F$O$$$1$^$;$s!#Be$o$j$K!"$=$l$>$l!V(B&amp;lt;$B!W$H!V(B&amp;amp;$B!W$r;H$$$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.1.p.7" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Fourth,
there are two quoting characters in XML, 'apostrophe' and "quotation".
Make sure that all attributes values are quoted,
e.g., "&lt;example name='value'&gt;",
If the value contains one of the quoting characters,
then use the other to quote the value,
e.g., "&lt;example name='"'&gt;",
If the value contains both quoting characters,
then use one of them to quote the value,
and replace occurrances of that character in the attribute value with
either '&amp;apos;' (apostrophe) or "&amp;quot;" (quotation),
e.g., "&lt;example name='"&amp;apos;"'&gt;".
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B;MHVL\$K!"(B XML $B$G$O(B '$B%"%]%9%H%m%U%#(B' $B$H(B "$B0zMQ(B" 
    $B$NFs<oN`$N0zMQJ8;z$,$"$j$^$9!#A4$F$NB0@-CM$r!"(B
    <samp>$B!V(B6lt;$BNc(B $BL>A0(B='$BCM(B'&gt;$B!W(B</samp> $B$NMM$K0zMQId$G0O$`$3$H$r3NG'$7$F2<$5$$!#CM$K0zMQJ8;z$N0lJ}$,;H$o$l$F$$$k;~$O!"(B
    <samp>$B!V(B&lt;$BNc(B $BL>A0(B='"'&gt;$B!W(B</samp> $B$NMM$KB>J}$rCM$r0O$`$N$K;H$$$^$9!#(B
    $BCM$,0zMQJ8;z$NN>J}$r4^$s$G$$$k>l9g!"$I$A$i$+$rCM$r0O$`$N$K;H$$!"B0@-CM$K;H$o$l$F$$$kJ8;z$r(B '&amp;apos;' ($B%"%]%9%H%m%U%#(B) $B$^$?$O(B "&amp;quot;"
    ($B0zMQ(B) $B$KCV$-49$($F!"(B <samp>$B!V(B&lt;$BNc(B $BL>A0(B='"&amp;apos;"'&gt;"$B!W(B</samp>
    $B$N$h$&$K$7$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.4">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    If you want to put a comment in your source file,
here's the syntax:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B8;%U%!%$%k$KCm<a$rF~$l$?$$;~$O!"<!$N9=J8$NMM$K$7$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
        &lt;!-- comments can be multiline,
         if you wish --&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
        &lt;!-- $BCm<a9T$O!"I,MW$J$i(B
         $BJ#?t9T$K=PMh$^$9!#(B --&gt;
</pre>
    <div class="rfc-postamble">
      <ins class="t-note t-l-ja" xml:lang="ja">
    (<span class="t-note-title">$BLuCm(B:</span>$B$^$?!"Cm<aCf$K!V(B--$B!W$r;H$C$F$O$$$1$^$;$s!#(B)
  </ins>
    </div>
  </p>
</div>

</div>
<div class="rfc-t" id="rfc.section.2.1.p.9" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Finally,
XML is case sensitive.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B8^HVL\$K!"(B XML $B$OBgJ8;z$H>.J8;z$r6hJL$7$^$9!#(B
  </p>
</div>
</div>
</div>

<div class="rfc-section" id="rfc.section.2.2">
<div id="front_matter">
<h2 xmlns="http://www.w3.org/1999/xhtml">2.2. Front matter</h2>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.5">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Immediately following the "&lt;rfc&gt;" tag is the "front"
element:
  </p>
<p xml:lang="ja" class="t-l-ja">
    "&lt;rfc&gt;" $B%?%0$ND>$08e$KB3$/$N$O(B "front" $BMWAG$G$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;?xml version="1.0"?&gt;
    &lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd"&gt;
    &lt;rfc&gt;
        &lt;front&gt;
            &lt;title ...&gt;
            &lt;author ...&gt;
            &lt;author ...&gt;
            &lt;date ...&gt;
            &lt;area ...&gt;
            &lt;workgroup ...&gt;
            &lt;keyword ...&gt;
            &lt;keyword ...&gt;
            &lt;abstract ...&gt;
            &lt;note ...&gt;
        &lt;/front&gt;
        ...
    &lt;/rfc&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    (Note that in all examples,
indentation is used only for expository purposes.)
  </p>
<p xml:lang="ja" class="t-l-ja">
    ($BA4$F$NNc$G!";z2<$2$O@bL@$N$?$a$@$1$K;H$C$F$$$k$3$H$KCm0U$7$F2<$5$$!#(B)
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.2.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "front" element consists of a "title" element,
one or more "author" elements,
a "date" element,
one or more optional "area" elements,
one or more optional "workgroup" elements,
one or more optional "keyword" elements,
an optional "abstract" element.
and,
one or more optional "note" elements.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "front" $BMWAG$O(B "title" $BMWAG(B, 1$B$D0J>e$N(B "author" $BMWAG(B, "date" $BMWAG(B,
    1$B$D0J>e$N>JN,2DG=$J(B "area" $BMWAG(B,
    1$B$D0J>e$N>JN,2DG=$J(B "workgroup" $BMWAG(B,
    1$B$D0J>e$N>JN,2DG=$J(B "keyword" $BMWAG(B,
    $B>JN,2DG=$J(B "abstract" $BMWAG(B,
    1$B$D0J>e$N>JN,2DG=$J(B "note" $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.1">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.1. The title Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.1. 
          title $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.6">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "title" element identifies the title of the document.
Because the title will be used in the headers of the document when formatted
according to <span class="rfc-xref">
<a href="#refs.RFC2223" title="Instructions to RFC Authors">[2]</a>
</span>,
if the title is more than 42 characters,
then an abbreviation should also be provided,
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "title" $BMWAG$O!"J8=q$NBj$r<1JL$7$^$9!#Bj$O(B 
    <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">[2]</a> $B$K=>$C$F@07A$9$k;~$KJ8=q$NF,$K;H$o$l$k$N$G!"Bj$O(B42$BJ8;z0J>e$N;~$O!">JN,7A$bM?$($k$Y$-$G$9!#Nc$($P!"<!$N$h$&$K$7$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;title abbrev="Much Ado about Nothing"&gt;
    The IETF's Discussion on "Source Format of RFC Documents"
    &lt;/title&gt;
</pre>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.2">
<div class="t-pair t-heading" id="author">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.2. The author Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.2. 
          author $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.7">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Each "author" element identifies a document author.
Since a document may have more than one author,
more than one "author" element may be present.
If the author is a person,
then three attributes must be present in the "&lt;author&gt;" tag,
"initials", "surname", and "fullname",
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B3F(B "author" $BMWAG$O!"J8=q$NMWAG$r<1JL$7$^$9!#J8=q$K$OJ#?t?M$NCx<T$,$$F@$^$9$N$G!"J#?t$N(B 
    "author" $BMWAG$r;H$&$3$H$,=PMh$^$9!#Cx<T$,?MJ*$G$"$k;~$O!"(B
    "initials" ($BF,J8;z(B), "surname" ($B@+(B), "fullname" ($BA4L>(B) $B$N(B3$B$D$NB0@-$,(B
    "author" $B%?%0$K$J$1$l$P$J$j$^$;$s!#Nc$($P!"<!$NMM$K$7$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;author initials="M.T." surname="Rose"
            fullname="Marshall T. Rose"&gt;
</pre>
</div>
<div class="rfc-t" id="rfc.section.2.2.2.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "author" element itself consists of an "organization" element,
and,
an optional "address" element.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "author" $BMWAG<+?H$O(B "organization" $BMWAG$H!">JN,2DG=$J(B "address"
    $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.8">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "organization" element is similar to the "title"
element,
in that an abbreviation may be paired with a long organization name
using the "abbrev" attribute, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "organization" $BMWAG$O(B "title" $BMWAG$HF1$8MM$K!"D9$$AH?%L>$K(B
    "abbrev" $BB0@-$r;H$C$F<!$NNc$NMM$K>JN,L>$r;XDj$9$k$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;organization abbrev="ISI"&gt;
        USC/Information Sciences Institute
    &lt;/organization&gt;
</pre>
</div>
<div class="rfc-t" id="rfc.section.2.2.2.p.4" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "address" element consists of an optional "postal" element,
an optional "phone" element,
an optional "facsimile" element,
an optional "email" element,
and,
an optional "uri" element.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "address" $BMWAG$O>JN,2DG=$J(B "postal" $BMWAG(B,
$B>JN,2DG=$J(B "phone" $BMWAG(B,
$B>JN,2DG=$J(B "facsimile" $BMWAG(B,
$B>JN,2DG=$J(B "email" $BMWAG(B,
$B>JN,2DG=$J(B "uri" $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.9">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "postal" element contains one or more "street" elements,
followed by any combination of "city", "region" (state or province),
"code" (zipcode or postal code), and "country" elements, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "postal" $BMWAG$O<!$NNc$NMM$K!"(B1$B$D0J>e$N(B "street" $BMWAG(B, $B$=$l$KB3$/(B
    "city", "region" ($B=#$dCOJ}(B), "code" ($BM9JXHV9f(B), "country" 
    $B3FMWAG$N<+M3$JAH9g$;$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;postal&gt;
        &lt;street&gt;660 York Street&lt;/street&gt;
        &lt;street&gt;M/S 40&lt;/street&gt;
        &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
        &lt;code&gt;94110&lt;/code&gt;
        &lt;country&gt;US&lt;/country&gt;
    &lt;/postal&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    This flexibility is provided to allow for different national
formats for postal addresses.
Note however,
that although the order of the "city", "region", "code", and "country"
elements isn't specified,
at most one of each may be present.
Regardless,
these elements must not be re-ordered during processing by an XML
application
(e.g., display applications must preserve the ordering of the
information contained in these elements).
Finally,
the value of the "country" element should be a two-letter
code from ISO 3166.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$N=@Fp$5$K$h$j!"0[$J$C$?9q2HM9JX=;=j7A<0$,;H$($^$9!#(B
    $B$7$+$7!"(B "city", "region", "code", "country" 
    $B3FMWAG$N=g=x$O5,Dj$7$F$$$^$;$s$,!"$3$NFb$N$;$$$<$$(B1$B$D$O=P8=$9$k$+$b$7$l$J$$$3$H$KCm0U$7$F2<$5$$!#$H$K$+$/!"$3$l$i$NMWAG$O(B 
    XML $B1~MQ$N=hM}$N2aDx$G=g=x$rF~$lBX$($F$O$J$j$^$;$s!#(B 
    ($BNc$($P!"I=<(1~MQ$O$3$l$i$NMWAG$K4^$^$l$k>pJs$N=g=x$rJ]$?$J$1$l$P$J$j$^$;$s!#(B)
    $B:G8e$K!"(B "country" $BMWAG$NCM$O(B ISO 3166 $B$N(B2$BJ8;zId9f$H$9$k$Y$-$G$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.10">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "phone", "facsimile", "email", and "uri" elements are
simple, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "phone", "facsimile", "email", "uri" $B3FMWAG$O4JC1$G!"<!$NMM$J46$8$G$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
    &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
    &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
</pre>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.3">
<div class="t-pair t-heading" id="date">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.3. The date Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.3. 
          date $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.11">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "date" element identifies the publication date of the
document.
It consists of a month and a year, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "date" $BMWAG$OJ8=q$N=PHG$NF|IU$r<($7$^$9!#<!$N$h$&$K7n$HG/$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;date month="February" year="1999" /&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "date" element also has an optional day attribute.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "date" $BMWAG$K$O>JN,2DG=$J(B day $BB0@-$b$"$j$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.4">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.4. Meta Data Elements</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.4. 
          $B%a%?!&%G!<%?MWAG(B</h3>
</div>
<div class="rfc-t" id="rfc.section.2.2.4.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "front" element may contain meta data $B!=!=(B
the content of these elements does not appear in printed versions of
the document.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "front" $BMWAG$O%a%?!&%G!<%?(B ($BFbMF$OJ8=q$N0u:~HG$K$O=P8=$7$J$$$b$N(B) $B$b4^$`$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.12">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    A document has one or more optional "area",
"workgroup" and "keyword" elements, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$O(B1$B$D0J>e$N>JN,2DG=$J(B "area", "workgroup", "keyword"
    $B3FMWAG$r<!$NNc$NMM$K;}$A$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;area&gt;General&lt;/area&gt;
    &lt;workgroup&gt;RFC Beautification Working Group&lt;/workgroup&gt;
    &lt;keyword&gt;RFC&lt;/keyword&gt;
    &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
    &lt;keyword&gt;I-D&lt;/keyword&gt;
    &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
    &lt;keyword&gt;XML&lt;/keyword&gt;
    &lt;keyword&gt;Extensible Markup Language&lt;/keyword&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "area" elements identify a general category for the
document
(e.g., one of "Applications", "General", "Internet", "Management",
"Operations", "Routing", "Security", "Transport", or "User"),
while the "workgroup" elements identify the IETF working groups that
produced the document,
and the "keyword" elements identify useful search terms.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "area" $BMWAG$OJ8=q$N0lHLJ,N`(B ("Applications" ($B1~MQ(B), 
    "General" ($B0lHL(B), "Internet", "Management" ($B7P1D(B),
    "Operations" ($B:n6H(B), "Routing" ($B7PO)(B), "Security" ($BJ]0B(B), 
    "Transport" ($BM"Aw(B), "User" ($BMxMQ<T(B)) $B$r<($7!"(B
    "workgroup" $BMWAG$OJ8=q$r=P$7$?(B IETF $B:n6HIt2q$r<($7!"(B
    "keyword" $BMWAG$OM-MQ$J8!:w8l$r<($7$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.5">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.5. The abstract Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.5. 
          abstract $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.13">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    A document may have an "abstract" element,
which contains one or more <span class="rfc-xref">
<a href="#t" title="">"t" elements</a>
</span>.
In general,
only a single "t" element is present,
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$K$O(B "abstract" $BMWAG$r;H$&$3$H$,=PMh$F!"(B
    $B$=$l$K$O(B1$B$D0J>e$N(B <a href="#t" title="">"t" $BMWAG(B</a>$B$,4^$a$i$l$^$9!#DL>o!"<!$NNc$NMM$K!"(B "t" $BMWAG$r(B1$B$D$@$1;H$$$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;abstract&gt;
        &lt;t&gt;This memo presents a technique for using XML
        (Extensible Markup Language) as a source format
        for documents in the Internet-Drafts (I-Ds) and
        Request for Comments (RFC) series.&lt;/t&gt;
    &lt;/abstract&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;abstract&gt;
        &lt;t&gt;$B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B 
        Internet-Draft (I-D) $B$d(B Request for Comments (RFC) 
        $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B&lt;/t&gt;
    &lt;/abstract&gt;
</pre>
  </p>
</div>

</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.6">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.6. The note Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.6. 
          note $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.14">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    A document may have one or more "note" elements,
each of which contains one or more <span class="rfc-xref">
<a href="#t" title="">"t" elements</a>
</span>.
There is a mandatory "title" attribute.
In general,
the "note" element contains text from the IESG, 
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$K$O(B1$B$D0J>e$N(B "note" $BMWAG$r;H$&$3$H$,=PMh$F!"(B
    $B$=$l$>$l(B1$B$D0J>e$N(B <a href="#t" title="">"t" $BMWAG(B</a>$B$,4^$a$i$l$^$9!#I,?\$N(B
    "title" $BB0@-$,$"$j$^$9!#DL>o!"(B "note" $BMWAG$O(B IESG 
    $B$+$i$NJ8$r<!$NNc$NMM$KF~$l$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;note title="IESG Note"&gt;
        &lt;t&gt;The IESG has something to say.&lt;/t&gt;
    &lt;/note&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;note title="IESG $BCm5-(B"&gt;
        &lt;t&gt;IESG $B$OFC$K8@$&$3$H$O$"$j$^$;$s!#(B&lt;/t&gt;
    &lt;/note&gt;
</pre>
  </p>
</div>

</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.7">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.7. Status, Copyright Notice, Table of Contents</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.7. 
          $B0LCVIU$1(B, $BCx:n8"I=<((B, $BL\<!(B</h3>
</div>
<div class="rfc-t" id="rfc.section.2.2.7.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Note that text relating to the memo's status, copyright notice, or
table of contents is not included in the document's markup $B!=!=(B this is
automatically inserted by an XML application when it produces either
a text or HTML version of the document.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B%a%b$N0LCVIU$1$r@bL@$9$kJ8>O(B, $BCx:n8"I=<((B, 
    $BL\<!$OJ8=q$N%^!<%/IU$1$K$O4^$a$^$;$s!#$3$l$O(B XML 
    $B1~MQ$,J8=q$N(B text $BHG$d(B HTML $BHG$r@8@.$9$k;~$K<+F0E*$KA^F~$5$l$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.7.1">
<div class="t-pair t-heading" id="ipr">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.7.1. Conformance with RFC 2026</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.7.1. 
          RFC 2026 $B$X$NE,9g@-(B</h4>
</div>
<div class="rfc-t" id="rfc.section.2.2.7.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    If an Internet-Draft is being produced,
then the "ipr" attribute should be present in the "&lt;rfc&gt;"
tag at the beginning of the file.
The value of the attribute should be one of:
  </p>
<p xml:lang="ja" class="t-l-ja">
    Internet-Draft $B$,@8@.$5$l$k>l9g$K!"(B "ipr" $BB0@-$,%U%!%$%k$N$O$8$a$N(B
    "&lt;rfc&gt;"$B%?%0$K8=$l$k$Y$-$G$9!#$3$NB0@-$NCM$O<!$N$$$:$l$+$G$"$k$Y$-$G$9!#(B
  </p>
</div>

<dl class="rfc-list-hanging" xmlns="">
<dt>full2026:</dt>
<dd>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    indicating that the document is in full conformance with all
the provisions of Section 10 of RFC 2026;
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$,(B <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a> 
    $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
    $B$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B
  </p>
</div>
</dd>
<dt>noDerivativeWorks2026:</dt>
<dd>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    indicating that the document is in full
conformance with all the provisions of Section 10 of RFC 2026 except that the
right to produce derivative works is not granted; or,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$,!"GI@8E*:n6H$N@8@.$,G'$a$i$l$F$$$J$$$3$H$r=|$$$F!"(B
    <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a> 
    $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
    $B$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B
  </p>
</div>
</dd>
<dt>none:</dt>
<dd>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    indicating that the document is NOT offered in accordance with
Section 10 of RFC 2026, and the author does not provide the IETF with any rights
other than to publish as an Internet-Draft.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$,(B
    <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a> 
    $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
    $B$K=>$C$F(B<strong xmlns="http://www.w3.org/1999/xhtml">$B$*$i$:(B</strong>$B!"Cx<T$O(B IETF $B$K(B Internet-Draft
    $B$H$7$FH/9T$9$k0J30$N$$$+$J$k8"Mx$r$bDs6!$7$J$$$3$H$r<($7$^$9(B
  </p>
</div>
</dd>
</dl>

  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    In the latter case,
a copyright notice will not be automatically inserted during
processing by an XML application.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B8e<T$N>l9g$G$O!"Cx:n8"I=<($O(B XML $B1~MQ$K$h$j<+F0E*$K$OA^F~$5$l$^$;$s!#(B
    <ins class="t-note t-l-ja" xml:lang="ja">
    (<span class="t-note-title">$BLuCm(B:</span>$B8e<T(B (the latter case) $B$H$O:G8e$N>l9g$N$_(B?
    rfc2629.xslt $B$G$O$I$N>l9g$G$bA^F~$5$l$k$h$&$G$9$,(B...)
  </ins>
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.2.7.1.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Consult <span class="rfc-xref">
<a href="#refs.RFC2026" title="The Internet Standards Process $B!=!=(B Revision 3">[3]</a>
</span> for further details.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B>\$7$/$O(B <a href="#refs.RFC2026" title="Internet $BI8=`2=2aDx(B $B!=!=(B $B2~D{(B3$BHG(B">[3]</a> $B$rD4$Y$F2<$5$$!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.15">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Finally,
if the Internet-Draft is being submitted to an automated process,
then the "docName" attribute should be present in the "&lt;rfc&gt;"
tag at the beginning of the file.
The value of this attribute contains the document (not file) name
associated with this Internet-Draft, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G8e$K!"(B Internet-Draft $B$,<+F0=hM}$K2s$5$l$?;~$O!"(B "docName"
    $BB0@-$,%U%!%$%k$N$O$8$a$N(B "&lt;rfc&gt;" $B%?%0Cf$K=P8=$9$k$Y$-$G$9!#(B
    $B$3$NB0@-$NCM$O(B Internet-Draft $B$K$D$1$i$l$?J8=q(B ($B%U%!%$%k$G$J$7$K(B) 
    $B$NL>A0$G!"<!$NMM$K$J$j$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;rfc ipr="full" docName="draft-mrose-writing-rfcs-01"&gt;
        ...
    &lt;/rfc&gt;
</pre>

<div class="rfc-postamble"/>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.2.8">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.2.8. Everything in the Front</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.2.8. 
          Front $BA4BN(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.16">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    So,
putting it all together, we have, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B0J>e$r$^$H$a$k$H<!$NMM$K$J$j$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
<pre class="rfc-artwork" xml:space="preserve">
    &lt;front&gt;
        &lt;title&gt;Writing I-Ds and RFCs using XML&lt;/title&gt;
    
        &lt;author initials="M.T." surname="Rose"
                fullname="Marshall T. Rose"&gt;
            &lt;organization&gt;Invisible Worlds, Inc.&lt;/organization&gt;
    
            &lt;address&gt;
                &lt;postal&gt;
                    &lt;street&gt;660 York Street&lt;/street&gt;
                    &lt;street&gt;M/S 40&lt;/street&gt;
                    &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
                    &lt;code&gt;94110&lt;/code&gt;
                    &lt;country&gt;US&lt;/country&gt;
                &lt;/postal&gt;
    
                &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
                &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
                &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
            &lt;/address&gt;
        &lt;/author&gt;
    
        &lt;date month="February" year="1999" /&gt;
    
        &lt;area&gt;General&lt;/area&gt;
        &lt;workgroup&gt;RFC Beautification Working Group&lt;/workgroup&gt;
        &lt;keyword&gt;RFC&lt;/keyword&gt;
        &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
        &lt;keyword&gt;I-D&lt;/keyword&gt;
        &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
        &lt;keyword&gt;XML&lt;/keyword&gt;
        &lt;keyword&gt;Extensible Markup Language&lt;/keyword&gt;
        &lt;abstract&gt;
            &lt;t&gt;This memo presents a technique for using XML
            (Extensible Markup Language) as a source format
            for documents in the Internet-Drafts (I-Ds) and
            Request for Comments (RFC) series.&lt;/t&gt;
        &lt;/abstract&gt;
    &lt;/front&gt;
</pre>
</p>
<p xml:lang="ja" class="t-l-ja">
<pre class="rfc-artwork" xml:space="preserve">
    &lt;front&gt;
        &lt;title&gt;XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B&lt;/title&gt;
    
        &lt;author initials="M.T." surname="Rose"
                fullname="Marshall T. Rose"&gt;
            &lt;organization&gt;Invisible Worlds, Inc.&lt;/organization&gt;
    
            &lt;address&gt;
                &lt;postal&gt;
                    &lt;street&gt;660 York Street&lt;/street&gt;
                    &lt;street&gt;M/S 40&lt;/street&gt;
                    &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
                    &lt;code&gt;94110&lt;/code&gt;
                    &lt;country&gt;US&lt;/country&gt;
                &lt;/postal&gt;
    
                &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
                &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
                &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
            &lt;/address&gt;
        &lt;/author&gt;
    
        &lt;date month="February" year="1999" /&gt;
    
        &lt;area&gt;General&lt;/area&gt;
        &lt;workgroup&gt;RFC $BH~2=:n6HIt2q(B&lt;/workgroup&gt;
        &lt;keyword&gt;RFC&lt;/keyword&gt;
        &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
        &lt;keyword&gt;I-D&lt;/keyword&gt;
        &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
        &lt;keyword&gt;XML&lt;/keyword&gt;
        &lt;keyword&gt;$B3HD%%^!<%/IU$18@8l(B&lt;/keyword&gt;
        &lt;abstract&gt;
            &lt;t&gt;$B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B 
            Internet-Draft (I-D) $B$d(B Request for Comments (RFC) 
            $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B&lt;/t&gt;
        &lt;/abstract&gt;
    &lt;/front&gt;
</pre>
</p>
</div>

</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3">
<div>
<h2 xmlns="http://www.w3.org/1999/xhtml">2.3. The Middle</h2>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.17">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "middle" element contains all the sections of the document
except for the bibliography and appendices:
  </p>
<p xml:lang="ja" class="t-l-ja">
    "middle" $BMWAG$O;29MJ88%$HImB0=q$r=|$/J8=q$NA4$F$N@a$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    ...
    &lt;/front&gt;
    &lt;middle&gt;
        &lt;section ...&gt;
        &lt;section ...&gt;
        &lt;section ...&gt;
    &lt;/middle&gt;
    &lt;back&gt;
    ...
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "middle" element consists of one or more "section"
elements.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "middle" $BMWAG$O(B1$B$D0J>e$N(B "section" $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1">
<div class="t-pair t-heading" id="section">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1. The section Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1. 
          section $BMWAG(B</h3>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.18">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Each "section" element contains a section of the document.
There is a mandatory attribute,
"title",
that identifies the title of the section.
There is also an optional attribute,
"anchor",
that is used for cross-referencing with
<span class="rfc-xref">
<a href="#xref" title="">the "xref" element</a>
</span>,
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B3F(B "section" $BMWAG$OJ8=q$N@a$+$i@.$j$^$9!#I,?\$NB0@-(B "title"
    $B$O@a$NBj$rI=$7$^$9!#>JN,2DG=$NB0@-(B "anchor" $B$O(B
    <a href="#xref" title="">"xref" $BMWAG(B</a>$B$K$h$k8r:9;2>H$K;H$$$^$9!#(B
    $B<!$NNc$r8fMw2<$5$$!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;section anchor="intro" title="Introduction"&gt;
        ...
    &lt;/section&gt;
</pre>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.19">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "section" element is recursive $B!=!=(B
each contains any number and combination of "t", "figure", and "section"
elements, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "section" $BMWAG$O:F5"E*$G!"3F!9G$0U$N?t!&AH9g$;$G(B "t",
    "figure", "section" $B3FMWAG$r<!$NNc$NG!$/;H$$$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;section title="The Middle"&gt;
        ...
        &lt;section title="The section Element"&gt;
            ...
            &lt;section title="The t Element"&gt;...&lt;/section&gt;
            &lt;section title="The list Element"&gt;...&lt;/section&gt;
            &lt;section title="The figure Element"&gt;...&lt;/section&gt;
            &lt;section title="The xref Element"&gt;...&lt;/section&gt;
            &lt;section title="The eref Element"&gt;...&lt;/section&gt;
            &lt;section title="The iref Element"&gt;...&lt;/section&gt;
        &lt;/section&gt;
    &lt;/section&gt;
</pre>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.1">
<div class="t-pair t-heading" id="t">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.1. The t Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.1. 
          t $BMWAG(B</h4>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "t" element contains any number and combination of
paragraphs, lists, and figures.
If a cross-reference is needed to a section, figure, or reference,
<span class="rfc-xref">
<a href="#xref" title="">the "xref" element</a>
</span> is used;
similarly,
if an external-reference is needed,
<span class="rfc-xref">
<a href="#eref" title="">the "eref" element</a>
</span> is used.
Indexing of text is provided by the
<span class="rfc-xref">
<a href="#iref" title="">the "iref" element</a>
</span>.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "t" $BMWAG$OG$0U$N?t!&AH9g$;$NCJMn!&0lMw!&?^$+$i@.$j$^$9!#@a!&?^!&;29MJ88%$X$N8r:9;2>H$,I,MW$J$i!"(B <a href="#xref" title="">"xref" $BMWAG(B</a>
    $B$r;H$$$^$9!#F1MM$K30It;2>H$,I,MW$J$i!"(B <a href="#eref" title="">"eref" 
    $BMWAG(B</a>$B$r;H$$$^$9!#J8>O$N:w0zIU$1$K$O(B <a href="#iref" title="">"iref" 
    $BMWAG(B</a>$B$r;H$$$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.2">
<div class="t-pair t-heading">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.2. The list Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.2. 
          list $BMWAG(B</h4>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.20">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "list" element contains one or more items.
Each item is a "t" element,
allowing for recursion, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "list" $BMWAG$O(B1$B$D0J>e$N9`L\$+$i@.$j$^$9!#3F9`L\$O(B
    "t" $BMWAG$G!"7+$jJV$72DG=$G$9!#Nc$r8fMw$"$l(B:
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="numbers"&gt;
        &lt;t&gt;The first item.&lt;/t&gt;
        &lt;t&gt;The second item, which contains two bulleted sub-items:
            &lt;list style="symbols"&gt;
                &lt;t&gt;The first sub-item.&lt;/t&gt;
                &lt;t&gt;The second sub-item.&lt;/t&gt;
            &lt;/list&gt;
        &lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="numbers"&gt;
        &lt;t&gt;$B:G=i$N9`L\!#(B&lt;/t&gt;
        &lt;t&gt;2$B$D$N>.9`L\$,$"$kFsHVL\$N9`L\(B
            &lt;list style="symbols"&gt;
                &lt;t&gt;$B:G=i$N>.9`L\(B&lt;/t&gt;
                &lt;t&gt;$BFsHVL\$N>.9`L\(B&lt;/t&gt;
            &lt;/list&gt;
        &lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
</div>

<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "list" element has an optional attribute,
"style",
having the value "numbers" (for numeric lists),
"symbols" (for bulleted lists),
"hanging" (for hanging lists),
or,
"empty" (for indented text).
If a "list" element is nested,
the default value is taken from its closest parent;
otherwise,
the default value is "empty".

  </p>
<p xml:lang="ja" class="t-l-ja">
    "list" $BMWAG$O>JN,2DG=$J(B "style" $BB0@-$,$"$C$F!"(B "numbers"
    ($BHV9f$D$-0lMw(B), "symbols" ($B5-9f$D$-0lMw(B), "hanging" ($B$V$i2<$,$j0lMw(B),
    "empty" ($B;z2<$2J8(B) $B$N$$$:$l$+$NCM$r<h$k$3$H$,=PMh$^$9!#(B
    "list" $BMWAG$,F~$l;R$K$J$C$F$$$k;~!"4{DjCM$O0lHV6a$$?F$+$i<h$i$l$^$9!#$=$&$G$J$$;~$O!"4{DjCM$O(B "empty" $B$G$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.21">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    When nested within a "hanging list" element,
the "t" element has an optional attribute,
"hangText" that specifies the text to be inserted, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B!V$V$i2<$,$j0lMw!W(B $BMWAGCf$GF~$l;R$K$J$C$F$$$k;~!"(B
    "t" $BMWAG$O>JN,2DG=$JB0@-(B "hangText" $B$r;}$A!"A^F~$5$l$kJ8;zNs$r;XDj$7$^$9!#<!$NNc$r;2>H$7$F2<$5$$!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="hanging"&gt;
        &lt;t hangText="full2026:"&gt;indicating that the document is in
        full conformance with all the provisions of Section 10 of
        RFC 2026;&lt;/t&gt;

        &lt;t hangText="noDerivativeWorks2026:"&gt;indicating that the
        document is in full conformance with all the provisions of
        Section 10 of RFC 2026 except that the right to produce
        derivative works is not granted; or,&lt;/t&gt;

        &lt;t hangText="none:"&gt;indicating that the document is NOT
        offered in accordance with Section 10 of RFC 2026, and
        the author does not provide the IETF with any rights other
        than to publish as an Internet-Draft.&lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="hanging"&gt;
        &lt;t hangText="full2026:"&gt;$BJ8=q$,(B RFC 2026 
        $B$NBh(B10$B>O$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B&lt;/t&gt;

        &lt;t hangText="noDerivativeWorks2026:"&gt;
        $BJ8=q$,!"GI@8E*:n6H$N@8@.$,G'$a$i$l$F$$$J$$$3$H$r=|$$$F!"(B
        RFC 2026 $B$NBh(B10$B>O$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r(B
        $B<($7$^$9(B&lt;/t&gt;

        &lt;t hangText="none:"&gt;$BJ8=q$,(B RFC 2026 $B$NBh(B10$B>O$K=>$C$F(B
        *$B$*$i$:(B*$B!"Cx<T$O(B IETF $B$K(B Internet-Draft
        $B$H$7$FH/9T$9$k0J30$N$$$+$J$k8"Mx$r$bDs6!$7$J$$$3$H$r(B
        $B<($7$^$9(B&lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
</div>

</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.3">
<div class="t-pair t-heading" id="figure">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.3. The figure Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.3. 
          figure $BMWAG(B</h4>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.3.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "figure" element groups an optional "preamble" element,
an "artwork" element,
and an optional "postamble" element together.
The "figure" element also has an optional "anchor" attribute that is
used for cross-referencing with
<span class="rfc-xref">
<a href="#xref" title="">the "xref" element</a>
</span>.
There is also an optional "title" attribute that identifies the title
of the figure.

  </p>
<p xml:lang="ja" class="t-l-ja">
    "figure" $BMWAG$O>JN,2DG=$J(B "preamble" $BMWAG(B,
    "artwork" $BMWAG(B, $B>JN,2DG=$J(B "postable" $BMWAG$r$R$H$^$H$a$K$7$^$9!#(B
    "figure" $BMWAG$O>JN,2DG=$J(B "anchor" $BB0@-$b;}$C$F$$$F!"(B
    <a href="#xref" title="">"xref" $BMWAG(B</a>$B$K$h$k8r:9;2>H$K;H$&$3$H$,=PMh$^$9!#(B
    $B>JN,2DG=$J(B "title" $BB0@-$H$$$&$N$b$"$C$F!"?^$NBj$r<($7$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.3.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "preamble" and "postamble" elements,
if present,
are simply text.
If a cross-reference is needed to a section, figure, or reference,
<span class="rfc-xref">
<a href="#xref" title="">the "xref" element</a>
</span> is used;
similarly,
if an external-reference is needed,
<span class="rfc-xref">
<a href="#eref" title="">the "eref" element</a>
</span> is used.
Indexing of text is provided by the
<span class="rfc-xref">
<a href="#iref" title="">the "iref" element</a>
</span>.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "preamble" $B!&(B "postamble" $BN>MWAG$O!"B8:_$9$k>l9g!"C1=c$JJ8;zNs$G$9!#(B
    $B@a!&?^!&;29MJ88%$X$N8r:9;2>H$,I,MW$J>l9g$O!"(B
    <a href="#xref" title="">"xref" 
    $BMWAG(B</a>$B$r;H$$$^$9!#F1MM$K!"30It;2>H$,I,MW$J$i!"(B 
    <a href="#eref" title="">"eref" $BMWAG(B</a>$B$r;H$$$^$9!#J8>O$N:w0zIU$1$K$O(B 
    <a href="#iref" title="">"iref" $BMWAG(B</a>$B$r;H$$$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.3.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "artwork" element,
which must be present,
contains "ASCII artwork".
Unlike text contained in the "t", "preamble", or "postamble" elements,
both horizontal and vertical whitespace is significant in the "artwork"
element.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "artwork" $BMWAG$O!"I,$:B8:_$7$J$1$l$P$J$i$:!"!V(BASCII $B3(!W$+$i@.$j$^$9!#(B
    "t", "preamble", "postamble" $B3FMWAGCf$NJ8;zNs$H$O0c$C$F!"?eJ?!&?bD>$I$A$i$N6uGr4V3V$b(B 
    "artwork" $BMWAGCf$G$O0UL#$r;}$A$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.22">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    So,
putting it all together, we have, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$H$$$&$3$H$G!"A4$F$^$H$a$k$H!"<!$NNc$NMM$K$J$j$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;figure anchor="figure_example"&gt;
        &lt;preamble&gt;So,
        putting it all together, we have, e.g.,&lt;/preamble&gt;
        &lt;artwork&gt;
            ascii artwork goes here...
    
            be sure to use "&amp;lt;" or "&amp;amp;" instead of "&lt;" and "&amp;",
            respectively!
        &lt;/artwork&gt;
        &lt;postamble&gt;which is a very simple example.&lt;/postamble&gt;
    &lt;/figure&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;figure anchor="figure_example"&gt;
        &lt;preamble&gt;$B$H$$$&$3$H$G!"A4$F$^$H$a$k$H!"(B
        $B<!$NNc$NMM$K$J$j$^$9!#(B&lt;/preamble&gt;
        &lt;artwork&gt;
            ascii $B3($,$3$3$KF~$j$^$9(B...
    
            "&amp;lt;" $B$H$+(B "&amp;amp;" $B$r$=$l$>$l(B "&lt;" $B$H(B "&amp;"
            $B$NBe$o$j$K;H$&$s$@$h(B!
        &lt;/artwork&gt;
        &lt;postamble&gt;$BHs>o$KC1=c$JNc$G$7$?!#(B&lt;/postamble&gt;
    &lt;/figure&gt;
</pre>
  </p>
</div>

<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    which is a very simple example.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BHs>o$KC1=c$JNc$G$7$?!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.23">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    If you have artwork with a lot of "&lt;" characters,
then there's an XML trick you can use:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BBt;3$N(B "&lt;" $BJ8;z$,3($NCf$K$"$k>l9g$O!"$3$N$h$&$J(B
    XML $BKbK!$r;H$&$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;figure&gt;
        &lt;preamble&gt;If you have artwork with a lot of "&amp;lt;"
        characters, then there's an XML trick you can
        use:&lt;/preamble&gt;
        &lt;artwork&gt;&lt;![CDATA[
            ascii artwork goes here...
    
            just don't use "]]" in your artwork!
        ]]&gt;&lt;/artwork&gt;
        &lt;postamble&gt;The "&amp;lt;![CDATA[ ... ]]&gt;" construct is called
        a CDATA block -- everything between the innermost brackets
        is left alone by the XML application.&lt;/postamble&gt;
    &lt;/figure&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;figure&gt;
        &lt;preamble&gt;$BBt;3$N(B "&amp;lt;" $BJ8;z$,3($NCf$K$"$k>l9g$O!"(B
        $B$3$N$h$&$J(B XML $BKbK!$r;H$&$3$H$,=PMh$^$9!#(B&lt;/preamble&gt;
        &lt;artwork&gt;&lt;![CDATA[
            ascii $B$,$3$3$KMh$^$9(B...
    
            $BC1$K(B "]]" $B$r3($NCf$G;H$o$J$$$@$1$G$9(B!
        ]]&gt;&lt;/artwork&gt;
        &lt;postamble&gt;"&amp;lt;![CDATA[ ... ]]&gt;" $B9=B$$O(B CDATA
        $B2t$H8F$P$l$^$9!#0lHVFbB&$N3g8L$N4V$N$b$N$OA4$F(B XML 
        $B1~MQ$K43>D$5$l$^$;$s!#(B&lt;/postamble&gt;
    &lt;/figure&gt;
</pre>
  </p>
</div>

<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "&lt;![CDATA[ ... ]]&gt;" construct is called a CDATA
block $B!=!=(B everything between the innermost brackets is left alone by
the XML application.
  </p>
<p xml:lang="ja" class="t-l-ja">
    <samp>$B!V(B&lt;![CDATA[ ... ]]&gt;$B!W(B</samp> $B9=B$$O(B CDATA
    $B2t$H8F$P$l$^$9!#0lHVFbB&$N3g8L$N4V$N$b$N$OA4$F(B XML $B1~MQ$K43>D$5$l$^$;$s!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.3.p.6" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Because the "figure" element represents a logical grouping of text
and artwork,
an XML application producing a text version of the document should
attempt to keep these elements on the same page.
Because <span class="rfc-xref">
<a href="#refs.RFC2223" title="Instructions to RFC Authors">RFC 2223
          &#x00A0;<sup>[2]</sup>
</a>
</span> allows no more than 69
characters by 49 lines of content on each page,
XML applications should be prepared to prematurely introduce page
breaks to allow for better visual grouping.
  </p>
<p xml:lang="ja" class="t-l-ja">
      "figure" $BMWAG$OJ8=q$H3($NO@M}E*$J=89g$rI=8=$9$k$N$G!"J8=q$N(B 
      text $BHG$r@8@.$9$k(B XML $B1~MQ$O3FMWAG$rF10lJGCf$KF~$l$k$h$&$K:v$9$k$Y$-$G$9!#(B
      <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">RFC 2223
          &#x00A0;<sup>[2]</sup>
</a> 
      $B$,3FJG(B49$B9T$NFbMF$G(B, 69$BJ8;z$rD6$($k$N$rG'$a$F$$$J$$$N$G!"(B
      XML $B1~MQ$O$h$jNI$$;k3PE*=89g2=$r9T$&$?$a$KM=$a2~JG$9$k=`Hw$r$7$F$*$/$Y$-$G$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.3.p.7" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Finally,
the "artwork" element has two optional attributes:
"name" and "type".
The former is used to suggest a filename to use when storing the
content of the "artwork" element,
whilst the latter contains a suggestive data-typing for the content.
  </p>
<p xml:lang="ja" class="t-l-ja">
      $B:G8e$K!"(B "artwork" $BMWAG$O(B2$B$D$N>JN,2DG=$JB0@-(B "name", "type"
      $B$r;}$A$^$9!#A0<T$O(B "artwork" $BMWAG$NFbMF$rJ]4I$9$k;~$K;H$&%U%!%$%kL>$N0F$r?d$9$N$K;H$$$^$9!#8e<T$OFbMF$N%G!<%?7?$r<($9$N$K;H$$$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.4">
<div class="t-pair t-heading" id="xref">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.4. The xref Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.4. 
          xref $BMWAG(B</h4>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.4.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "xref" element is used to cross-reference sections, figures, and
references.
The mandatory "target" attribute is used to link back to the "anchor"
attribute of the "section", "figure", and "reference" elements.
The value of the "anchor" and "target" attributes should be formatted
according to the token syntax in <span class="rfc-xref">
<a href="#xml_basics" title="XML basics">
        section 2.1</a>
</span>.
  </p>
<p xml:lang="ja" class="t-l-ja">
      "xref" $BMWAG$O@a!&?^!&;29MJ88%$N8r:9;2>H$K;H$$$^$9!#I,?\$N(B
      "target" $BB0@-$O(B "section", "figure", "reference" $BMWAG$N(B
      "anchor" $BB0@-$K5U@\B3$9$k$N$K;H$$$^$9!#(B
      "anchor" $B$*$h$S(B "target" $BN>B0@-$NCM$O(B <a href="#xml_basics" title="XML $B$N4pAC(B">2.1$B@a(B</a>
      $B$N;z6g(B (token) $B9=J8$K=>$$=q<02=$5$l$k$Y$-$G$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.24">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    If used as an empty element,
e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
      $B6uMWAG$H$7$F;H$&;~$O(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    according to the token syntax in &lt;xref target="xml_basics" /&gt;.
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
      <pre class="rfc-artwork" xml:space="preserve">
    &lt;xref target="xml_basics" /&gt; $B$N;z6g(B (token) $B9=J8$K=>$$(B
</pre>
  </p>
</div>

<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    then the XML application inserts an appropriate phrase
during processing,
such as "Section 2.1" or
"&lt;a href="#xml_basics"&gt;XML Basics&lt;/a&gt;".
  </p>
<p xml:lang="ja" class="t-l-ja">
      $B$NMM$K$J$j!"(B XML $B1~MQ$O(B <samp>$B!V(B2.1 $B@a!W(B</samp> $B$d(B
      <samp>$B!V(B&lt;a href="#xml_basics"&gt;XML $B$N4pAC(B&lt;/a&gt;$B!W(B</samp>
      $B$N$h$&$KE,@Z$JJ8;zNs$r=hM}$K$h$jA^F~$7$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.25">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    If used with content, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
      $BFbMF$"$j$G;H$&;~$O(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    conforming to &lt;xref target="refs.RFC2223"&gt;RFC 2223&lt;/xref&gt;.
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;xref target="refs.RFC2223"&gt;RFC 2223&lt;/xref&gt; $B$KE,9g$9$k(B
</pre>
  </p>
</div>

<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    then the XML application inserts an appropriate
designation during processing,
such as "RFC 2223[2]" or
"&lt;a href="#refs.RFC2223"&gt;RFC 2223&lt;/a&gt;".
Although the XML application decides what "an appropriate designation"
might be,
its choice is consistent throughout the processing of the document.
  </p>
<p xml:lang="ja" class="t-l-ja">
      $B$NMM$K$J$j!"(B XML $B1~MQ$O(B <samp>$B!V(BRFC 2223[2]$B!W(B</samp> $B$d(B
      <samp>$B!V(B&lt;a href="#refs.RFC2223"&gt;RFC 2223&lt;/a&gt;$B!W(B</samp>
      $B$N$h$&$KE,@Z$J;X<($r=hM}$K$h$jA^F~$7$^$9!#!VE,@Z$J;X<(!W$NFbMF$O(B
      XML $B1~MQ$,7h$a$^$9$,!"A*Br$OEv3:J8=q$N=hM}$rDL$8$F8GDj$G$9!#(B
  </p>
</div>
</div>
</div>
</div>

<div class="rfc-section" id="rfc.section.2.3.1.5">
<div class="t-pair t-heading" id="eref">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.5. The eref Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.5. 
          eref $BMWAG(B</h4>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.26">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "eref" element is used to reference external documents.
The mandatory "target" attribute is a
<span class="rfc-xref">
<a href="#URI" title="Uniform Resource Identifiers (URI): Generic Syntax">URI
          &#x00A0;<sup>[4]</sup>
</a>
</span>, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "eref" $BMWAG$O!"30ItJ8=q$r;2>H$9$k$N$K;H$$$^$9!#I,?\$N(B
    "target" $BB0@-$O(B <a href="#URI" title="$BE}0l;q8;<1JL;R(B (URI): $B0lHL9=J8(B">URI
          &#x00A0;<sup>[4]</sup>
</a>
    $B$G!"<!$NMM$K;H$$$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;eref target="http://metalab.unc.edu/xml/"&gt;Cafe con Leche&lt;/eref&gt;
</pre>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.27">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Note that while the "target" attribute is always present,
the "eref" element may be empty, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "target" $BB0@-$O>o$KI,MW$G$"$j!"(B "eref" $BMWAG$O6u$G$"$jF@$k$3$H$KCm0U$7$F2<$5$$!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;eref target="http://invisible.net/" /&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
and the XML application inserts an appropriate designation during
processing such as "[9]" or
"&lt;a href="http://invisible.net/"&gt;http://invisible.net/&lt;/a&gt;".
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B1~MQ$O(B <samp>$B!V(B[9]$B!W(B</samp> $B$d(B 
    <samp>$B!V(B&lt;a href="http://invisible.net/"&gt;http://invisible.net/&lt;/a&gt;$B!W(B</samp> 
    $B$NMM$KE,@Z$J;X<($r=hM}$N2aDx$GA^F~$7$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.6">
<div class="t-pair t-heading" id="iref">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.6. The iref Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.6. 
          iref $BMWAG(B</h4>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.28">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
<span class="rfc-iref" id="rfc.iref.1">&#x00A0;</span>The "iref" element
is used to add information to an index.
The mandatory "item" attribute is the primary key the information is stored
under,
whilst the optional "subitem" attribute is the secondary key, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    <span class="rfc-iref" id="rfc.iref.2">&#x00A0;</span>"iref" 
    $BMWAG$O:w0z$K>pJs$rDI2C$9$k$N$K;H$$$^$9!#I,?\$NB0@-(B "item"
    $B$O>pJs$,J]4I$5$l$k<g80$G!">JN,2DG=$J(B "subitem" $BB0@-$OI{80$G$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
<pre class="rfc-artwork" xml:space="preserve">
    &lt;iref item="indexing" subitem="how to" /&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;iref item="$B:w0zIU$1(B" subitem="$BJ}K!(B" /&gt;
</pre>
  </p>
</div>

</div>
<div class="rfc-t" id="rfc.section.2.3.1.6.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
Finally, note that the "iref" element is always empty $B!=!=(B it never
contains any text.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G8e$K!"(B "iref" 
    $BMWAG$O>o$K6u$G$"$k!=!=$I$s$JJ8;zNs$b4^$^$J$$$H$$$&$3$H$KCm0U$7$F2<$5$$!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.3.1.7">
<div class="t-pair t-heading">
<h4 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.3.1.7. The vspace Element</h4>
<h4 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.3.1.7. 
          vspace $BMWAG(B</h4>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.7.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "vspace" element,
which may occur only inside the "t" element,
is used by the author to provide formatting guidance to the XML
application.
There is an attribute,
"blankLines",
that indicates the number of blank lines that should be inserted.
A physical linebreak is specified by using the default value, "0".
  </p>
<p xml:lang="ja" class="t-l-ja">
    "vspace" $BMWAG$O!"(B "t" $BMWAG$NCf$K$N$_8=$l$k$3$H$,=PMh$F!"Cx<T$,(B
    XML $B1~MQ$K@07A$N<j0z$-$rM?$($k$N$K;H$$$^$9!#(B "blankLines"
    $BB0@-$,$"$j!"A^F~$5$l$k$Y$-6uGr9T$N?t$r<($7$^$9!#J*M}2~9T$O4{DjCM$G$"$k(B
    "0" $B$r;H$C$FI=$7$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.29">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    In addition,
the "vspace" element can be used to force a new physical paragraph
within a list item, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B2C$($F!"(B "vspace" $BMWAG$O<!$KNc<($9$k$h$&$K!"?7$7$$7A<0CJMn$r0lMw9`L\Cf$K:n$j=P$9$N$K;H$&$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="numbers"&gt;
        &lt;t&gt;This is list item.
           &lt;vspace blankLines="1" /&gt;
           This is part of the same list item,
           although when displayed, it appears
           as a separate physical paragraph.&lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;list style="numbers"&gt;
        &lt;t&gt;$B$3$l$O0lMw$N9`L\$G$9!#(B
           &lt;vspace blankLines="1" /&gt;
           $B$3$l$OF1$80lMw9`L\$G$9!#(B
           $B$7$+$7I=<($N:]$K$OJL$N7A<0CJMn$K8+$($^$9!#(B&lt;/t&gt;
    &lt;/list&gt;
</pre>
  </p>
</div>

</div>
<div class="rfc-t" id="rfc.section.2.3.1.7.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    An XML application producing a text version of the document should
exercise care when encountering a value for "blankLines" that causes a
pagebreak $B!=!=(B
in particular,
if a "vspace" element causes a pagebreak,
then no further blank lines should be inserted.
This allows authors to "force" a pagebreak by using an arbitrarily
large value, e.g., "blankLines='100'".
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$N(B text $BHG$r@8@.$9$k(B XML $B1~MQ$O!"2~JG$r5/$3$9$h$&$J(B
    "breakLines" $B$NCM$G$"$C$?;~$KCm0U$9$k$Y$-$G$9!#(B
    "vspace" $BMWAG$,2~JG$r5/$3$9;~$O!"$=$l0J>e6uGr9T$rA^F~$9$k$Y$-$G$O$"$j$^$;$s!#$3$l$K$h$j!"Cx<T$OG$0U$NBg$-$JCM!"Nc$($P(B
    <samp>$B!V(BblankLines='100'$B!W(B</samp> $B$G!V6/@)!W2~JG$5$;$k$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.3.1.7.p.4" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Finally, note that the "vspace" element is always empty $B!=!=(B it never
contains any text.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G8e$K!"(B "vspace" $BMWAG$O>o$K6u$G$"$k!=!=J8;zNs$r4^$^$J$$$H$$$&$3$H$KCm0U$7$F2<$5$$!#(B
  </p>
</div>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.4">
<div id="back_matter">
<h2 xmlns="http://www.w3.org/1999/xhtml">2.4. Back matter</h2>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.30">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    Finally,
the "back" element is used for references and
appendices:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G8e$K!"(B "back" $BMWAG$O;29MJ88%$HImB0=q$K;H$$$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
        ...
        &lt;/middle&gt;
        &lt;back&gt;
            &lt;references&gt;
                &lt;reference ...&gt;
                &lt;reference ...&gt;
            &lt;/references&gt;
            &lt;section ...&gt;
            &lt;section ...&gt;
        &lt;/back&gt;
    &lt;/rfc&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "back" element consists of an optional "references" element,
and,
one or more optional "section" elements.
The "back" element itself is optional,
if your document doesn't have any references or appendices,
you don't have to include it.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "back" $BMWAG$O>JN,2DG=$J(B "references" $BMWAG$H!"(B1$B$D0J>e$N>JN,2DG=$J(B
    "section" $BMWAG$+$i@.$j$^$9!#(B "back" $BMWAG<+BN$O>JN,2DG=$G!"J8=q$K;29MJ88%$bImB0=q$b$J$$>l9g$O!"4^$a$kI,MW$O$"$j$^$;$s!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.4.1">
<div class="t-pair t-heading" id="references">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.4.1. The references Element</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.4.1. 
          references $BMWAG(B</h3>
</div>
<div class="rfc-t" id="rfc.section.2.4.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "references" element contains the document's bibliography.
It contains one or more "reference" elements.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "references" $BMWAG$OJ8=q$N;29MJ88%$+$i@.$j$^$9!#(B1$B$D0J>e$N(B
    "reference" $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.4.1.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Each "reference" element contains a "front" element and one or more
optional "seriesInfo" elements.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B3F(B "references" $BMWAG$O(B "front" $BMWAG$H(B1$B$D0J>e$N>JN,2DG=$J(B
    "seriesInfo" $BMWAG$+$i@.$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.4.1.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    We've already discussed the "front" element back in
<span class="rfc-xref">
<a href="#front_matter" title="Front matter">
        section 2.2</a>
</span>.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "front" $BMWAG$K$D$$$F$O(B <a href="#front_matter" title="">2.2$B@a(B</a>
    $B$G4{$KOC$7$^$7$?!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.2.4.1.p.4" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "seriesInfo" element has two attributes,
"name" and "value" that identify the document series and series entry,
respectively.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "seriesInfo" $BMWAG$O(B "name", "value" $B$N(B2$B$D$NB0@-$r;}$A!"$=$l$>$lJ8=q7ONs$H7ONs9`L\$rFCDj$7$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.31">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "reference" element has an optional "anchor"
attribute that is used for cross-referencing with
<span class="rfc-xref">
<a href="#xref" title="">the "xref" element</a>
</span>, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    "reference" $BMWAG$O>JN,2DG=$J(B "anchor" $BB0@-$r;}$A!"(B
    $B<!$NMM$K;H$$!"(B <a href="#xref" title="">"xref" $BMWAG(B</a>$B$G8r:9;2>H$K;H$&$3$H$,=PMh$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;reference anchor="refs.RFC2200"&gt;
        &lt;front&gt;
            &lt;title&gt;Internet Official Protocol Standards&lt;/title&gt;
            &lt;author initials="J." surname="Postel"
                    fullname="Jon Postel"&gt;
                &lt;organization abbrev="ISI"&gt;
                USC/Information Sciences Institute
                &lt;/organization&gt;
            &lt;/author&gt;
    
            &lt;date month="June" year="1997" /&gt;
        &lt;/front&gt;
        &lt;seriesInfo name="RFC" value="2200" /&gt;
        &lt;seriesInfo name="STD" value="1" /&gt;
    &lt;/reference&gt;
</pre>
</div>
<div class="rfc-t" id="rfc.section.2.4.1.p.6" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The "reference" element also has an optional "target"
attribute that is used for external references
(c.f., <span class="rfc-xref">
<a href="#eref" title="The eref Element">
        section 2.3.1.5</a>
</span>).
The XML application,
if producing an HTML version of the document will use the "target"
attribute accordingly;
however, if the "name" attribute of the "seriesInfo" element has the value
"RFC",
then the XML application should automatically provide an appropriate
default for the "target" attribute
(e.g., "http://example.com/rfcs/rfc2200.txt").
  </p>
<p xml:lang="ja" class="t-l-ja">
    "reference" $BMWAG$K$O>JN,2DG=$J(B "target" $BB0@-$,$"$j!"30It;2>H$K;H$$$^$9!#(B
    (cf. <a href="#eref" title="eref $BMWAG(B">2.3.1.5$B@a(B</a>) XML $B1~MQ$OJ8=q$N(B HTML $BHG$r@8@.$9$k;~$K(B
    "target" $BB0@-$r;H$$$^$9!#$7$+$7!"(B "seriseInfo" $BMWAG$N(B "name"
    $BB0@-$,CM(B "RFC" $B$r;}$D>l9g!"(B XML $B1~MQ$O<+F0E*$KE,@Z$J(B "target"
    $BB0@-$N4{DjCM$rMQ0U$9$k$Y$-$G$9!#(B ($BNc$($P(B 
    <samp>$B!V(Bhttp://example.com/rfcs/rfc2200.txt$B!W(B</samp>)
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.4.2">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.4.2. Appendices</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.4.2. 
          $BImB0=q(B</h3>
</div>
<div class="rfc-t" id="rfc.section.2.4.2.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    To include appendices after the bibliography,
simply add more "section" elements.
(For an example,
look at the example at the beginning of <span class="rfc-xref">
<a href="#back_matter" title="Back matter">
        section 2.4</a>
</span>.)
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B;29MJ88%$N8e$KImB0=q$r4^$a$k$K$O!"C1$K(B "section" 
    $BMWAG$rDI2C$9$k$@$1$G$9!#(B ($BNc$H$7$F!"(B <a href="#back_matter" title="">2.4$B@a(B</a>
    $B$N$O$8$a$NNc$r8fMw2<$5$$!#(B)
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.2.4.3">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">2.4.3. Copyright Status</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">2.4.3. 
          $BCx:n8">uBV(B</h3>
</div>
<div class="rfc-t" id="rfc.section.2.4.3.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The copyright status for the document is not included in the
document's markup $B!=!=(B this is automatically inserted by an XML
application that produces either a text or HTML version of the document.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BJ8=q$NCx:n8">uBV$OJ8=q$N%^!<%/IU$1$K$O4^$a$^$;$s!#(B
    $B$3$l$OJ8=q$N(B text $BHG$+(B HTML $BHG$r@8@.$9$k(B XML 
    $B1~MQ$K$h$j<+F0E*$KA^F~$5$l$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.3">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3. Processing the XML Source File</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3. 
          XML $B8;%U%!%$%k$N=hM}(B</h1>
</div>
<div class="rfc-t" id="rfc.section.3.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    This section concerns itself with applications that operate on
an XML source file.
A lot of XML tools are available,
as are many lists of XML resources,
e.g.,
<a href="http://metalab.unc.edu/xml/" title="URI: &lt;http://metalab.unc.edu/xml/>">Cafe con Leche</a>.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$N@a$O(B XML $B8;%U%!%$%k$r=hM}$9$k1~MQ$K$D$$$F$G$9!#Bt;3$N(B
    XML $B9)6q$,MxMQ2DG=$G$9$7!"Bt;3$N(B XML $B;q8;$N0lMw$b!"Nc$($P(B
    <a href="http://metalab.unc.edu/xml/" title="URI: &lt;http://metalab.unc.edu/xml/>">Cafe con Leche</a>
    $B$K$"$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.3.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    There are two kinds of XML tools: validating and non-validating.
Both check that the source file conforms to the rules given in
<span class="rfc-xref">
<a href="#xml_basics" title="XML basics">
        section 2.1</a>
</span>.
However,
in addition to making sure that the source file is well-formed,
a validating tool also reads the DTD referenced by the source file
to make sure that they match.
There are a number of both validating and non-validating tools available.
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B9)6q$K$O(B2$B<oN`$"$j$^$9(B: $B8!>Z$9$k$b$N$H8!>Z$7$J$$$b$N$G$9!#N><T6&$K!"8;%U%!%$%k$,(B 
    <a href="#xml_basics" title="XML $B$N4pAC(B">2.1$B@a(B</a> $B$K5s$2$?5,B'$KE,9g$9$k$+$O3NG'$7$^$9!#$7$+$7!"2C$($F8;%U%!%$%k$,@07A<0$G$"$k$+$r3NG'$9$k$?$a!"8!>Z9)6q$O8=%U%!%$%k$,;2>H$7$F$$$k(B
    DTD $B$bFI$s$G0lCW$7$F$$$k$+3NG'$7$^$9!#8!>Z!&Hs8!>Z9)6q6&$KB??tF~<j=PMh$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-section" id="rfc.section.3.1">
<div class="t-pair t-heading">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.1. Editing</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.1. 
          $BJT=8(B</h2>
</div>
<div class="rfc-t" id="rfc.section.3.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    There are several XML editors available.
Ideally,
you want an editor that validates.
This has two advantages:
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B%(%G%#%?!<$O4v$D$+F~<j2DG=$G$9!#M}A[E*$K$O!"8!>Z=PMh$k%(%G%#%?!<$,NI$$$G$7$g$&!#$3$l$K$O(B2$B$D$NMxE@$,$"$j$^$9!#(B
  </p>
</div>

<ul class="rfc-list-symbols text" xmlns="">
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    the editor provides guidance in fleshing-out the document structure;
and,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B%(%G%#%?!<$,J8=q9=B$$KFyIU$1$9$k<j0z$-$r<($9(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    the editor validates that the source file matches the rules in the DTD.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B%(%G%#%?!<$,8;%U%!%$%k$,(B DTD $B$N5,B'$H0lCW$7$F$$$k$+8!>Z$9$k(B
  </p>
</div>
</li>
</ul>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.32">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    There are two major modes in Emacs that support XML:
<a href="http://www.mulberrytech.com/tdtd/" title="URI: &lt;http://www.mulberrytech.com/tdtd/>">tdtd</a> and
<a href="http://www.inria.fr/koala/plh/sxml.html" title="URI: &lt;http://www.inria.fr/koala/plh/sxml.html>">psgml</a>.
The latter mode allows you to validate the source file
(by calling an external program).
If you visit the source file in Emacs and the major mode isn't
"SGML" or "XML", 
then usually all it takes is adding these lines to your ".emacs"
file:
  </p>
<p xml:lang="ja" class="t-l-ja">
    Emacs $B$G$O(B XML $B$KBP1~$7$?(B2$B$D$NBg%b!<%I!"(B
    <a href="http://www.mulberrytech.com/tdtd/" title="URI: &lt;http://www.mulberrytech.com/tdtd/>">tdtd</a> $B$H(B
    <a href="http://www.inria.fr/koala/plh/sxml.html" title="URI: &lt;http://www.inria.fr/koala/plh/sxml.html>">psgml</a>
    $B$,$"$j$^$9!#8e<T$N%b!<%I$G$O8;%U%!%$%k$r(B 
    ($B30It%W%m%0%i%`$r8F$S=P$9$3$H$K$h$j(B) $B8!>Z$9$k$3$H$,=PMh$^$9!#8;%U%!%$%k$r(B
    Emacs $B$G$_$F!"Bg%b!<%I$,(B $B!V(BSGML$B!W(B $B$+(B $B!V(BXML$B!W(B 
    $B$K$J$i$J$$>l9g!"DL>o$O(B ".emacs" $B%U%!%$%k$K<!$N9T(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    (setq auto-mode-alist
          (cons (cons "\\.xml$" 'sgml-mode) auto-mode-alist))
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    and then restarting Emacs.
If this doesn't work,
try one of the sources above.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$r2C$($F!"(B Emacs $B$r:F5/F0$7$^$9!#$3$l$G>e<j$/$$$+$J$1$l$P!">e5-$N>pJs8;$N$$$:$l$+$r;n$7$F$_$F2<$5$$!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.3.1.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The author uses both sgml-mode in Emacs,
and a commercial validating editor,
<a href="http://www.t2000-usa.com/" title="URI: &lt;http://www.t2000-usa.com/>">Clip! version 1.5</a>,
when editing source
files.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BCx<T$ON>(B sgml-mode $B$r(B Emacs $B$G;H$C$F$$$F!">&MQ8!>Z%(%G%#%?!<(B
    <a href="http://www.t2000-usa.com/" title="URI: &lt;http://www.t2000-usa.com/>">Clip! version 1.5</a>
    $B$r8;%U%!%$%k$rJT=8$9$k$N$K;H$C$F$$$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-section" id="rfc.section.3.1.1">
<div class="t-pair t-heading">
<h3 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.1.1. Checking</h3>
<h3 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.1.1. 
          $B3NG'(B</h3>
</div>
<div class="rfc-t" id="rfc.section.3.1.1.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    If your editor doesn't validate,
then you should run a program to validate the source file.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$*;H$$$N%(%G%#%?!<$,8!>Z$7$J$$$J$i!"8;%U%!%$%k$r8!>Z$9$k$N$K%W%m%0%i%`$rF0$+$9I,MW$,$"$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.3.1.1.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The author uses
<a href="http://www.alphaworks.ibm.com/formula/xml/" title="URI: &lt;http://www.alphaworks.ibm.com/formula/xml/>">the
AlphaWorks XML parser</a> for this purpose.
It requires that your system have a Java virtual machine.
In addition to Java,
there are validating parsers written in C, Perl, Python, and Tcl.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BCx<T$O(B 
    <a href="http://www.alphaworks.ibm.com/formula/xml/" title="URI: &lt;http://www.alphaworks.ibm.com/formula/xml/>">the
    AlphaWorks XML parser</a> $B$r$3$NL\E*$K;H$C$F$$$^$9!#$3$l$K$O$*;H$$$N7OE}$K(B
    Java $B2>A[5!3#$,I,MW$G$9!#(B Java $B$K2C$(!"(B C, Perl, Python, Tcl
    $B$G=q$+$l$?8!>Z2r@O4o$,$"$j$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.3.2">
<div class="t-pair t-heading" id="xml2rfc">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.2. Converting to Text Format</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.2. 
          text $B7A<0$KJQ49$9$k(B</h2>
</div>
<div class="rfc-t" id="rfc.section.3.2.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The author has written
<a href="http://memory.palace.org/authoring/" title="URI: &lt;http://memory.palace.org/authoring/>">the xml2rfc tool</a>,
which reads the source file and produces both a text and HTML version
of the document.
(This memo was produced using the xml2rfc tool.)
Note that xml2rfc isn't a validating tool,
so it's a good idea to use either a validating editor or run a stand-alone
validating parser prior to using the tool.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BCx<T$O8;%U%!%$%k$rFI$s$GJ8=q$N(B text $BHG$H(B HTML $BHG$NN><T$r@8@.$9$k(B
    <a href="http://memory.palace.org/authoring/" title="URI: &lt;http://memory.palace.org/authoring/>">xml2rfc 
    $B9)6q(B</a>$B$r=q$-$^$7$?!#(B ($B$3$N%a%b$O(B xml2rfc $B9)6q$r;H$C$F@8@.$7$^$7$?!#(B)
    $B$J$*!"(B xml2rfc $B$O8!>Z9)6q$G$O$J$$$N$G!"8!>Z%(%G%#%?!<$dC1FH8!>Z2r@O4o$r$3$N9)6q$NA0$K;H$&$N$,NI$$$G$7$g$&!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.3.3">
<div class="t-pair t-heading">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.3. Converting to HTML Format</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.3. 
          HTML $B7A<0$KJQ49$9$k(B</h2>
</div>
<div class="rfc-t" id="rfc.section.3.3.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The XML Style Language (XSL) is used to describe transformations
from the source file into some other structured file.
So,
ideally you should use an XSL-capable formatter to convert an XML source
file to HTML.
  </p>
<p xml:lang="ja" class="t-l-ja">
    XML $B%9%?%$%k8@8l(B (XSL) $B$r8;%U%!%$%k$+$iB>$N9=B$$N%U%!%$%k$KJQ7A$9$k$N$r5-=R$9$k$N$K;HMQ=PMh$^$9!#$G$9$+$i!"M}A[E*$K$O(B XSL $B$,;H$($k(B formatter
    $B$r;H$C$F(B XML $B8;%U%!%$%k$r(B HTML $B$KJQ49$9$k$Y$-$G$7$g$&!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.3.3.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    However,
as of this writing XSL is still in considerable flux.
(Hence,
no reference was included in this memo,
as by the time you read this section,
the reference would be outdated.)
So,
in the interim,
the author uses the xml2rfc tool for this purpose,
even though this tool doesn't provide much flexibility in its HTML layout.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$7$+$7$J$,$i!"$3$N(B XSL $B=q$-$O$^$@N.F0E*$H9M$($i$l$^$9!#(B
    ($B$=$l8N!"$3$N%a%b$K$O;2>H$O4^$a$^$;$s$G$7$?!#FI<T$,$3$N@a$rFI$`;~$K$O;2>H$O$b$&8E$$$b$N$K$J$C$F$$$k$G$7$g$&$+$i!#(B)
    $B$G$9$,!"$=$N4V!"Cx<T$O$3$NL\E*$K(B xml2rfc $B9)6q$r;H$$$^$9!#(B
    $B$3$N9)6q$O$=$l$[$I(B HTML $BG[CV$K=@Fp@-$r;}$C$F$$$J$$$N$G$9$,!#(B
  </p>
</div>
</div>
<ins class="t-note t-l-ja" xml:lang="ja">
<span class="t-note-title">$BLuCm(B:</span>
  <p class="rfc-t" id="rfc.section.3.3.p.1" xmlns="http://www.w3.org/1999/xhtml">rfc2629.xslt $B$O!"(B 
  <a href="http://xml.resource.org/authoring/" title="URI: &lt;http://xml.resource.org/authoring/>" xmlns="">xml2rfc 
  $B9)6q(B</a>$B$K4^$^$l$F$$$^$9!#$3$l$r;H$C$F9+$N(B XSLT formatter
  $B$G$b(B HTML $B$KJQ49=PMh$^$9!#(B</p>
</ins>
</div>
<div class="rfc-section" id="rfc.section.3.4">
<div class="t-pair t-heading">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.4. Viewing</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.4. 
          $BI=<((B</h2>
</div>
<div class="rfc-t" id="rfc.section.3.4.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Browsers that support either XSL or Cascading Style Sheets (CSS)
are able to view the source file directly.
  </p>
<p xml:lang="ja" class="t-l-ja">
    XSL $B$+(B Cascading Style Sheets (CSS) 
    $B$KBP1~$7$?1\Mw4o$r8;%U%!%$%k$rD>@\8+$k$N$K;HMQ=PMh$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-t" id="rfc.section.3.4.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    At present,
the author doesn't use any of these browsers,
instead converting source files to either text or HTML.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B8=;~E@$G!"Cx<T$O$=$NMM$J1\Mw4o$r;H$C$F$*$i$:!"Be$o$j$K8;%U%!%$%k$r(B
    text $B$+(B HTML $B$KJQ49$7$F$$$^$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.3.5">
<div class="t-pair t-heading">
<h2 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">3.5. Searching</h2>
<h2 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">3.5. 
          $B8!:w(B</h2>
</div>
<div class="rfc-t" id="rfc.section.3.5.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    As with text editors,
any text-oriented search tool (e.g., grep) can be used on the source file.
However,
there are search tools available that understand structured source.
  </p>
<p xml:lang="ja" class="t-l-ja">
    text $B%(%G%#%?!<$H6&$K!"$I$s$J(B text $B;X8~8!:w9)6q(B ($BNc(B grep)
    $B$r$b8;%U%!%$%k$KBP$7$F;H$&$3$H$,=PMh$^$9!#$7$+$7!"9=B$2=$5$l$?8;$rM}2r$9$k8!:wF;6q$b$"$j$^$9!#(B
  </p>
</div>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.33">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The author uses 
<a href="http://www.cs.helsinki.fi/~jjaakkol/sgrep.html" title="URI: &lt;http://www.cs.helsinki.fi/~jjaakkol/sgrep.html>">sgrep
version 1.9</a>
for this purpose,
e.g.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $BCx<T$O(B
    <a href="http://www.cs.helsinki.fi/~jjaakkol/sgrep.html" title="URI: &lt;http://www.cs.helsinki.fi/~jjaakkol/sgrep.html>">sgrep
    version 1.9</a> $B$r$3$NL\E*$G<!$NMM$K;H$C$F$$$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    sgrep -g xml 'ELEMENTS("title") not in ELEMENTS("back")' \
        writing-rfcs.xml
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    which extracts the title element from the source file.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$l$O(B title $BMWAG$r8;%U%!%$%k$+$i<h$j=P$7$^$9!#(B
  </p>
</div>
</div>
</div>
</div>
</div>
<div class="rfc-section" id="rfc.section.4">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">4. Security Considerations</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">4. 
          $B0BA4@-$K4X$7$F(B</h1>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.34">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    This memo raises no security issues;
however,
according to <span class="rfc-xref">
<a href="#refs.RFC2223" title="Instructions to RFC Authors">[2]</a>
</span>,
your document should contain a section near the end that discusses the
security considerations of the protocol or procedures that are the
main topic of your document, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$N%a%b$O0BA4@-LdBj$r5/$3$7$^$;$s!#$7$+$7!"(B <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">[2]</a>
    $B$K$h$k$H!"J8=q$O=*$o$j6a$/$K!"J8=q$N<gBj$G$"$k%W%m%H%3%k$d=hM}$N0BA4@-$K4X$7$F$N5DO@$N@a$r@_$1$k$Y$-$G$9!#Nc(B:
  </p>
</div>
</div>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;middle&gt;
        ...
        &lt;section title="Security Considerations"&gt;
            &lt;t&gt;This memo raises no security issues;
            however,
            according to &lt;xref target="refs.RFC2223" /&gt;,
            your document should contain a section near the end
            that discusses the security considerations of the
            protocol or procedures that are the main topic of your
            document.&lt;/t&gt;
        &lt;/section&gt;
    &lt;/middle&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
    &lt;middle&gt;
        ...
        &lt;section title="$B0BA4@-$K4X$7$F(B"&gt;
            &lt;t&gt;$B$3$N%a%b$O0BA4@-LdBj$r5/$3$7$^$;$s!#$7$+$7!"(B 
            &lt;xref target="refs.RFC2223" /&gt; $B$K$h$k$H!"(B
            $BJ8=q$O=*$o$j6a$/$K!"J8=q$N<gBj$G$"$k%W%m%H%3%k$d(B
            $B=hM}$N0BA4@-$K4X$7$F$N5DO@$N@a$r@_$1$k$Y$-$G$9!#(B&lt;/t&gt;
        &lt;/section&gt;
    &lt;/middle&gt;
</pre>
  </p>
</div>

</div>
</div>
<div class="rfc-section" id="rfc.references.References">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en">References</h1>
<h1 xml:lang="ja" class="t-l-ja">$B;29MJ88%(B</h1>
</div>
<dl>
<dt id="XML">[1]</dt>
<dd>$B!X(B<cite>
<a href="http://www.w3.org/TR/1998/REC-xml-19980210" title="URI: &lt;http://www.w3.org/TR/1998/REC-xml-19980210>">Extensible Markup Language (XML) 1.0</a>
</cite>$B!Y(B, W3C
        &#x00A0;XML
    
    , <span class="t-pair">
<span xml:lang="en" class="t-l-en">
      &#x00A0;February&#x00A0;
      1998.
    </span>, <span xml:lang="ja" class="t-l-ja">1998$BG/(B2$B7n!#(B
    </span>
</span>
</dd>
<dt id="refs.RFC2223">[2]</dt>
<dd>$B!X(B<cite>
<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2223" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2223>">Instructions to RFC Authors</a>
</cite>$B!Y(B, <span title="@fullname">Postel, J.</span>, <span title="@fullname">Reynolds, J.</span>, RFC
        &#x00A0;2223
    
    , <span class="t-pair">
<span xml:lang="en" class="t-l-en">
      &#x00A0;October&#x00A0;
      1997.
    </span>, <span xml:lang="ja" class="t-l-ja">1997$BG/(B10$B7n!#(B
    </span>
</span>
</dd>
<dt id="refs.RFC2026">[3]</dt>
<dd>$B!X(B<cite>
<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026>">The Internet Standards Process $B!=!=(B Revision 3</a>
</cite>$B!Y(B, <span title="@fullname">Bradner, S.O.</span>, RFC
        &#x00A0;2026, BCP
        &#x00A0;9
    
    , <span class="t-pair">
<span xml:lang="en" class="t-l-en">
      &#x00A0;October&#x00A0;
      1996.
    </span>, <span xml:lang="ja" class="t-l-ja">1996$BG/(B10$B7n!#(B
    </span>
</span>
</dd>
<dt id="URI">[4]</dt>
<dd>$B!X(B<cite>
<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2396" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2396>">Uniform Resource Identifiers (URI): Generic Syntax</a>
</cite>$B!Y(B, <span title="@fullname">Berners-Lee, T.</span>, <span title="@fullname">Fielding, R.T.</span>, <span title="@fullname">Masinter, L.</span>, RFC
        &#x00A0;2396
    
    , <span class="t-pair">
<span xml:lang="en" class="t-l-en">
      &#x00A0;August&#x00A0;
      1998.
    </span>, <span xml:lang="ja" class="t-l-ja">1998$BG/(B8$B7n!#(B
    </span>
</span>
</dd>
</dl>
</div>
<div id="rfc-authors" class="rfc-section">
<div id="rfc.authors" class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en">Author's Address</h1>
<h1 xml:lang="ja" class="t-l-ja">$BCx<T$NO"Mm@h(B</h1>
</div>
<ul class="rfc-author">
<li class="rfc-author-fullname">Marshall T. Rose</li>
<li class="rfc-organization">Invisible Worlds, Inc.</li>
<li class="rfc-street">660 York Street</li>
<li class="rfc-city">San Francisco</li>
<li class="rfc-region">CA</li>
<li class="rfc-code">94110</li>
<li class="rfc-country">US</li>
<li class="rfc-phone">$BEEOC(B: +1 415 695 3975</li>
<li class="rfc-email">$BEE;R%a%$%k(B: &lt;<a href="mailto:mrose@not.invisible.net">mrose@not.invisible.net</a>&gt;</li>
<li class="rfc-uri">URI: &lt;<a href="http://invisible.net/">http://invisible.net/</a>&gt;</li>
</ul>
</div>
<div class="rfc-section" id="rfc.section.A">
<div class="t-pair t-heading" id="rfc">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">A. The rfc Element</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">A. 
          rfc $BMWAG(B</h1>
</div>
<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.35">&#x00A0;</span>
<div class="rfc-preamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    The "&lt;rfc&gt;" tag at the beginning of the file,
with only <span class="rfc-xref">
<a href="#ipr" title="">an "ipr" attribute</a>
</span>,
produces an Internet-Draft.
However,
when other attributes are added to this tag by the RFC editor,
an RFC is produced, e.g.,
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B%U%!%$%k$N$O$8$a$N(B "&lt;rfc&gt;" $B%?%0$O!"(B
    <a href="#ipr" title="">"ipr" $BB0@-(B</a>$B$@$1$r;}$D$H!"(B Internet-Draft
    $B$r@8@.$7$^$9!#$7$+$7!"$3$N%?%0$K(B RFC $BJT=8<T$K$h$jB>$NB0@-$,(B
    $BIU2C$5$l$k$H!"(B RFC $B$,@8@.$5$l$^$9!#(B
  </p>
</div>
</div>
<pre class="rfc-artwork" xml:space="preserve">
    &lt;rfc number="2200"
         obsoletes="2000, 1920, 1880, 1800, ..."
         category="std"
         seriesNo="1"&gt;
</pre>
<div class="rfc-postamble">
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    At a minimum,
the "number" attribute should be present.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B>/$J$/$F$b!"(B "number" $BB0@-$,$"$k$Y$-$G$9!#(B
  </p>
</div>
</div>
</div>
<div class="rfc-t" id="rfc.section.A.p.2" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    The other attributes are:
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B$3$NB>$NB0@-$O!"(B
  </p>
</div>

<ul class="rfc-list-symbols text" xmlns="">
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    "obsoletes",
having a comma-separated list of RFC numbers,
that the document obsoletes;
  </p>
<p xml:lang="ja" class="t-l-ja">
    "obsoleted" $B$O!"$=$NJ8=q$,GQ;_$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    "updates",
having a comma-separated list of RFC numbers,
that the document updates;
  </p>
<p xml:lang="ja" class="t-l-ja">
    "updates" $B$O!"$=$NJ8=q$,99?7$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
  </p>
</div>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    "category",
having one of these values:
  </p>
<p xml:lang="ja" class="t-l-ja">
    "category" $B$O!"<!$NCM$N$$$:$l$+$r;}$A$^$9!#(B
  </p>
</div>

    <ol class="rfc-list-numbers text">
    <li>
      <div class="t-pair">
<p xml:lang="en" class="t-l-en">"std", for a Standards-Track document;</p>
<p xml:lang="ja" class="t-l-ja">"std" $B$OI8=`2=2aDxJ8=qMQ(B</p>
</div>
    </li>
    <li>
      <div class="t-pair">
<p xml:lang="en" class="t-l-en">"bcp", for a Best Current Practices document;</p>
<p xml:lang="ja" class="t-l-ja">"bcp" $B$O8=>u:GA11?MQJ8=qMQ(B</p>
</div>
    </li>
    <li>
      <div class="t-pair">
<p xml:lang="en" class="t-l-en">"exp", for an Experimental Protocol document;</p>
<p xml:lang="ja" class="t-l-ja">"exp" $B$O<B83%W%m%H%3%kJ8=qMQ(B</p>
</div>
    </li>
    <li>
      <div class="t-pair">
<p xml:lang="en" class="t-l-en">"historic", for a historic document; or,</p>
<p xml:lang="ja" class="t-l-ja">"exp" $B$ONr;KE*J8=qMQ(B</p>
</div>
    </li>
    <li>
      <div class="t-pair">
<p xml:lang="en" class="t-l-en">"info", the default, for an Informational document.</p>
<p xml:lang="ja" class="t-l-ja">"info" $B$O4{DjCM$G;29MJ8=qMQ(B</p>
</div>
    </li>
    </ol>
</li>
<li>
  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    "seriesNo",
having the corresponding number in the STD (std), BCP (bcp), or FYI (info)
series.
  </p>
<p xml:lang="ja" class="t-l-ja">
    "seriesNo" $B$O!"(B STD (std), BCP (bcp), FYI (info) $B3F7ONs$G$NBP1~HV9f$rCM$K;}$A$^$9!#(B
  </p>
</div>
</li>
</ul>
</div>
<div class="rfc-t" id="rfc.section.A.p.3" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">
    Finally,
a special entity, "&amp;rfc.number;", is available.
Authors preparing an RFC should use this entity whenever they want to 
reference the number of the RFC within the document itself.
In printed versions of the document,
the appropriate substitution (or "XXXX") will occur.
  </p>
<p xml:lang="ja" class="t-l-ja">
    $B:G8e$K!"FCJL$J<BBN(B "&amp;rfc.number;" $B$,;H$($^$9!#(B
    RFC $B$rMQ0U$9$kCx<T$O$3$N<BBN$rJ8=q<+?H$N(B 
    RFC $BHV9f$r;2>H$7$?$$;~$K;H$&$Y$-$G$9!#J8=q$N0u:~HG$G$O!"E,@Z$JBeBX(B 
    ($B$^$?$O(B "XXXX") $B$r;H$$$^$9!#(B
  </p>
</div>
  <ins class="t-note t-l-ja" xml:lang="ja" xmlns="">
    (<span class="t-note-title">$BLuCm(B:</span>
    <div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.36">&#x00A0;</span>
      <div class="rfc-preamble">$B<B:]$K;H$&;~$O!"(B</div>
      <pre class="rfc-artwork" xml:space="preserve">&lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd" [&lt;!ENTITY rfc.number "1234"&gt;]&gt;</pre>
      <div class="rfc-postamble">$B$N$h$&$K!"J8=q7?@k8@$GEv3:(B RFC 
      $BHV9f$r<($9$3$H$K$J$k$G$7$g$&!#(B</div>
    </div>
  )
  </ins>
</div>
</div>
<div class="rfc-section" id="rfc.section.B">
<div id="rfc.dtd">
<h1 xmlns="http://www.w3.org/1999/xhtml">B. The RFC DTD</h1>
</div>

<ins class="t-note t-l-ja" xml:lang="ja">
<span class="t-note-title">$BLuCm(B:</span>
  <p class="rfc-t" id="rfc.section.B.p.1" xmlns="http://www.w3.org/1999/xhtml">$B$3$N(B DTD $B$N%U%!%$%k(B rfc2629.dtd $B$O!"(B 
  <a href="http://xml.resource.org/authoring/" title="URI: &lt;http://xml.resource.org/authoring/>" xmlns="">xml2rfc 
  $B9)6q(B</a>$B$NCf$K$b4^$^$l$F$$$^$9!#(B</p>
</ins>

<div class="rfc-figure">
<span class="rfc-figure-id" id="rfc.figure.u.37">&#x00A0;</span>

  <div class="t-pair">
<p xml:lang="en" class="t-l-en">
    <pre class="rfc-artwork" xml:space="preserve">
&lt;!--
  DTD for the RFC document series, draft of 99-01-30
  --&gt;


&lt;!--
  Contents

    DTD data types

    The top-level

    Front matter

    The Body

    Back matter
  --&gt;


&lt;!--
  DTD data types:

        entity        description
        ======        ===============================================
        NUMBER        [0-9]+
        NUMBERS       a comma-separated list of NUMBER

        DAY           the day of the month, e.g., "1"
        MONTH         the month of the year, e.g., "January"
        YEAR          a four-digit year, e.g., "1999"

        URI           e.g., "http://invisible.net/"

        ATEXT/CTEXT   printable ASCII text (no line-terminators)

        TEXT          character data
  --&gt;


&lt;!ENTITY % NUMBER     "CDATA"&gt;
&lt;!ENTITY % NUMBERS    "CDATA"&gt;

&lt;!ENTITY % DAY        "CDATA"&gt;
&lt;!ENTITY % MONTH      "CDATA"&gt;
&lt;!ENTITY % YEAR       "CDATA"&gt;

&lt;!ENTITY % URI        "CDATA"&gt;

&lt;!ENTITY % ATEXT      "CDATA"&gt;
&lt;!ENTITY % CTEXT      "#PCDATA"&gt;

&lt;!ENTITY % TEXT       "#PCDATA"&gt;

&lt;!ENTITY   rfc.number "2629"&gt;


&lt;!--
  The top-level
  --&gt;


&lt;!--
  attributes for the "rfc" element are supplied by the RFC
  editor. when preparing drafts, authors should leave them blank.

  the "seriesNo" attribute is used if the category is, e.g., BCP.
  --&gt;
&lt;!ELEMENT rfc         (front,middle,back?)&gt;
&lt;!ATTLIST rfc
          number      %NUMBER;           #IMPLIED
          obsoletes   %NUMBERS;          ""
          updates     %NUMBERS;          ""
          category    (std|bcp|info|exp|historic)
                                         "info"
          seriesNo    %NUMBER;           #IMPLIED
          ipr         (full2026|noDerivativeWorks2026|none)
                                         #IMPLIED
          docName     %ATEXT;            #IMPLIED&gt; 

&lt;!--
  Front matter
  --&gt;


&lt;!ELEMENT front       (title,author+,date,area*,workgroup*,keyword*,
                       abstract?,note*)&gt;

&lt;!-- the "abbrev" attribute is used for headers, etc. --&gt;
&lt;!ELEMENT title       (%CTEXT;)&gt;
&lt;!ATTLIST title
          abbrev      %ATEXT;            #IMPLIED&gt; 

&lt;!ELEMENT author      (organization,address?)&gt;
&lt;!ATTLIST author
          initials    %ATEXT;            #IMPLIED
          surname     %ATEXT;            #IMPLIED
          fullname    %ATEXT;            #IMPLIED&gt;

&lt;!ELEMENT organization
                      (%CTEXT;)&gt;
&lt;!ATTLIST organization
          abbrev      %ATEXT;            #IMPLIED&gt; 
 
&lt;!ELEMENT address     (postal?,phone?,facsimile?,email?,uri?)&gt;

&lt;!-- at most one of each the city, region, code, and country
     elements may be present --&gt;
&lt;!ELEMENT postal      (street+,(city|region|code|country)*)&gt;
&lt;!ELEMENT street      (%CTEXT;)&gt;
&lt;!ELEMENT city        (%CTEXT;)&gt;
&lt;!ELEMENT region      (%CTEXT;)&gt;
&lt;!ELEMENT code        (%CTEXT;)&gt;
&lt;!ELEMENT country     (%CTEXT;)&gt;
&lt;!ELEMENT phone       (%CTEXT;)&gt;
&lt;!ELEMENT facsimile   (%CTEXT;)&gt;
&lt;!ELEMENT email       (%CTEXT;)&gt;
&lt;!ELEMENT uri         (%CTEXT;)&gt;

&lt;!ELEMENT date        EMPTY&gt;
&lt;!ATTLIST date
          day         %DAY;              #IMPLIED
          month       %MONTH;            #REQUIRED
          year        %YEAR;             #REQUIRED&gt;

&lt;!-- meta-data... --&gt;
&lt;!ELEMENT area        (%CTEXT;)&gt;
&lt;!ELEMENT workgroup   (%CTEXT;)&gt;
&lt;!ELEMENT keyword     (%CTEXT;)&gt;

&lt;!ELEMENT abstract    (t)+&gt;
&lt;!ELEMENT note        (t)+&gt;
&lt;!ATTLIST note
          title       %ATEXT;            #REQUIRED&gt;


&lt;!--
  The body
  --&gt;


&lt;!ELEMENT middle      (section)+&gt;

&lt;!ELEMENT section     (t|figure|section)*&gt;
&lt;!ATTLIST section
          anchor      ID                 #IMPLIED
          title       %ATEXT;            #REQUIRED&gt;

&lt;!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
&lt;!ATTLIST t
          hangText    %ATEXT;            #IMPLIED&gt;

&lt;!-- the value of the style attribute is inherited from the closest 
     parent --&gt;
&lt;!ELEMENT list        (t+)&gt;
&lt;!ATTLIST list
          style       (numbers|symbols|hanging|empty)
                                         "empty"&gt;

&lt;!ELEMENT xref        (%CTEXT;)&gt;
&lt;!ATTLIST xref
          target      IDREF              #REQUIRED
          pageno      (true|false)       "false"&gt;

&lt;!ELEMENT eref        (%CTEXT;)&gt;
&lt;!ATTLIST eref
          target      %URI;              #REQUIRED&gt;

&lt;!ELEMENT iref        EMPTY&gt;
&lt;!ATTLIST iref
          item        %ATEXT;            #REQUIRED
          subitem     %ATEXT;            ""&gt;

&lt;!ELEMENT vspace      EMPTY&gt;
&lt;!ATTLIST vspace
          blankLines  %NUMBER;           "0"&gt;

&lt;!ELEMENT figure      (preamble?,artwork,postamble?)&gt;
&lt;!ATTLIST figure
          anchor      ID                 #IMPLIED
          title       %ATEXT;            ""&gt;

&lt;!ELEMENT preamble    (%TEXT;|xref|eref|iref)*&gt;
&lt;!ELEMENT artwork     (%TEXT;)*&gt;
&lt;!ATTLIST artwork
          xml:space   (default|preserve) "preserve"&gt;
&lt;!ELEMENT postamble   (%TEXT;|xref|eref|iref)*&gt;


&lt;!--
  Back matter
  --&gt;


&lt;!-- sections, if present, are appendices --&gt;
&lt;!ELEMENT back        (references?,section*)&gt;

&lt;!ELEMENT references  (reference+)&gt;
&lt;!ELEMENT reference   (front,seriesInfo*)&gt;
&lt;!ATTLIST reference
          anchor      ID                 #IMPLIED
          target      %URI;              #IMPLIED&gt;
&lt;!ELEMENT seriesInfo  EMPTY&gt;
&lt;!ATTLIST seriesInfo
          name        %ATEXT;            #REQUIRED
          value       %ATEXT;            #REQUIRED&gt;
</pre>
  </p>
<p xml:lang="ja" class="t-l-ja">
    <pre class="rfc-artwork" xml:space="preserve">
&lt;!--
  RFC $BJ8=q7ONsMQ(B DTD, 99-01-30 $B$N860F(B ($B$NCm<aItJ,OBLu(B)
  --&gt;


&lt;!--
  $BFbMF(B

    DTD $B%G!<%?7?(B

    $B:G>e0L(B

    Front matter

    The Body

    Back matter
  --&gt;


&lt;!--
  DTD $B%G!<%?7?(B:

        $B<BBN(B          $B@bL@(B
        ======        ===============================================
        NUMBER        [0-9]+
        NUMBERS       $BFIE@(B(comma)$B6h@Z$j$N(B NUMBER

        DAY           $B7nCf$NF|!"Nc$($P(B "1"
        MONTH         $BG/Cf$N7n!"Nc$($P(B "January" (1$B7n(B)
        YEAR          4$B7eG/9f!"Nc$($P(B "1999"

        URI           $BNc(B "http://invisible.net/"

        ATEXT/CTEXT   $B0u;z2DG=(B ASCII $BJ8;zNs(B ($B9T=*C<L5$7(B)

        TEXT          $BJ8;z%G!<%?(B
  --&gt;


&lt;!ENTITY % NUMBER     "CDATA"&gt;
&lt;!ENTITY % NUMBERS    "CDATA"&gt;

&lt;!ENTITY % DAY        "CDATA"&gt;
&lt;!ENTITY % MONTH      "CDATA"&gt;
&lt;!ENTITY % YEAR       "CDATA"&gt;

&lt;!ENTITY % URI        "CDATA"&gt;

&lt;!ENTITY % ATEXT      "CDATA"&gt;
&lt;!ENTITY % CTEXT      "#PCDATA"&gt;

&lt;!ENTITY % TEXT       "#PCDATA"&gt;

&lt;!ENTITY   rfc.number "2629"&gt;


&lt;!--
  $B:G>e0L(B
  --&gt;


&lt;!--
  "rfc" $BMWAG$NB0@-$O(B RFC $BJT=8<T$K$h$jKd$a$i$l$^$9!#(B
  $B860F$rMQ0U$9$k:]$K$O!"Cx<T$O6uMs$K$7$F$*$/$Y$-$G$9!#(B

  "seriesNo" $BB0@-$OJ,N`$,Nc$($P(B BCP $B$N;~$K;H$$$^$9!#(B
  --&gt;
&lt;!ELEMENT rfc         (front,middle,back?)&gt;
&lt;!ATTLIST rfc
          number      %NUMBER;           #IMPLIED
          obsoletes   %NUMBERS;          ""
          updates     %NUMBERS;          ""
          category    (std|bcp|info|exp|historic)
                                         "info"
          seriesNo    %NUMBER;           #IMPLIED
          ipr         (full2026|noDerivativeWorks2026|none)
                                         #IMPLIED
          docName     %ATEXT;            #IMPLIED&gt; 

&lt;!--
  Front matter
  --&gt;


&lt;!ELEMENT front       (title,author+,date,area*,workgroup*,keyword*,
                       abstract?,note*)&gt;

&lt;!-- "abbrev" $BB0@-$OF,$H$+$K;H$$$^$9!#(B --&gt;
&lt;!ELEMENT title       (%CTEXT;)&gt;
&lt;!ATTLIST title
          abbrev      %ATEXT;            #IMPLIED&gt; 

&lt;!ELEMENT author      (organization,address?)&gt;
&lt;!ATTLIST author
          initials    %ATEXT;            #IMPLIED
          surname     %ATEXT;            #IMPLIED
          fullname    %ATEXT;            #IMPLIED&gt;

&lt;!ELEMENT organization
                      (%CTEXT;)&gt;
&lt;!ATTLIST organization
          abbrev      %ATEXT;            #IMPLIED&gt; 
 
&lt;!ELEMENT address     (postal?,phone?,facsimile?,email?,uri?)&gt;

&lt;!-- city, region, code, country $B3FMWAG$,$;$$$<$$(B1$B2s=P8=2DG=(B --&gt;
&lt;!ELEMENT postal      (street+,(city|region|code|country)*)&gt;
&lt;!ELEMENT street      (%CTEXT;)&gt;
&lt;!ELEMENT city        (%CTEXT;)&gt;
&lt;!ELEMENT region      (%CTEXT;)&gt;
&lt;!ELEMENT code        (%CTEXT;)&gt;
&lt;!ELEMENT country     (%CTEXT;)&gt;
&lt;!ELEMENT phone       (%CTEXT;)&gt;
&lt;!ELEMENT facsimile   (%CTEXT;)&gt;
&lt;!ELEMENT email       (%CTEXT;)&gt;
&lt;!ELEMENT uri         (%CTEXT;)&gt;

&lt;!ELEMENT date        EMPTY&gt;
&lt;!ATTLIST date
          day         %DAY;              #IMPLIED
          month       %MONTH;            #REQUIRED
          year        %YEAR;             #REQUIRED&gt;

&lt;!-- $B%a%?!&%G!<%?!&!&!&(B --&gt;
&lt;!ELEMENT area        (%CTEXT;)&gt;
&lt;!ELEMENT workgroup   (%CTEXT;)&gt;
&lt;!ELEMENT keyword     (%CTEXT;)&gt;

&lt;!ELEMENT abstract    (t)+&gt;
&lt;!ELEMENT note        (t)+&gt;
&lt;!ATTLIST note
          title       %ATEXT;            #REQUIRED&gt;


&lt;!--
  $BK\BN(B
  --&gt;


&lt;!ELEMENT middle      (section)+&gt;

&lt;!ELEMENT section     (t|figure|section)*&gt;
&lt;!ATTLIST section
          anchor      ID                 #IMPLIED
          title       %ATEXT;            #REQUIRED&gt;

&lt;!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
&lt;!ATTLIST t
          hangText    %ATEXT;            #IMPLIED&gt;

&lt;!-- style $BB0@-$NCM$OD>6a$N?F$+$i7Q>5$9$k(B --&gt;
&lt;!ELEMENT list        (t+)&gt;
&lt;!ATTLIST list
          style       (numbers|symbols|hanging|empty)
                                         "empty"&gt;

&lt;!ELEMENT xref        (%CTEXT;)&gt;
&lt;!ATTLIST xref
          target      IDREF              #REQUIRED
          pageno      (true|false)       "false"&gt;

&lt;!ELEMENT eref        (%CTEXT;)&gt;
&lt;!ATTLIST eref
          target      %URI;              #REQUIRED&gt;

&lt;!ELEMENT iref        EMPTY&gt;
&lt;!ATTLIST iref
          item        %ATEXT;            #REQUIRED
          subitem     %ATEXT;            ""&gt;

&lt;!ELEMENT vspace      EMPTY&gt;
&lt;!ATTLIST vspace
          blankLines  %NUMBER;           "0"&gt;

&lt;!ELEMENT figure      (preamble?,artwork,postamble?)&gt;
&lt;!ATTLIST figure
          anchor      ID                 #IMPLIED
          title       %ATEXT;            ""&gt;

&lt;!ELEMENT preamble    (%TEXT;|xref|eref|iref)*&gt;
&lt;!ELEMENT artwork     (%TEXT;)*&gt;
&lt;!ATTLIST artwork
          xml:space   (default|preserve) "preserve"&gt;
&lt;!ELEMENT postamble   (%TEXT;|xref|eref|iref)*&gt;


&lt;!--
  Back matter
  --&gt;


&lt;!-- sections $B$,$"$k>l9g!"$=$l$OImB0=q(B --&gt;
&lt;!ELEMENT back        (references?,section*)&gt;

&lt;!ELEMENT references  (reference+)&gt;
&lt;!ELEMENT reference   (front,seriesInfo*)&gt;
&lt;!ATTLIST reference
          anchor      ID                 #IMPLIED
          target      %URI;              #IMPLIED&gt;
&lt;!ELEMENT seriesInfo  EMPTY&gt;
&lt;!ATTLIST seriesInfo
          name        %ATEXT;            #REQUIRED
          value       %ATEXT;            #REQUIRED&gt;
</pre>
  </p>
</div>

</div>
</div>
<div class="rfc-section" id="rfc.section.C">
<div class="t-pair t-heading">
<h1 xml:lang="en" class="t-l-en" xmlns="http://www.w3.org/1999/xhtml">C. Acknowledgements</h1>
<h1 xml:lang="ja" class="t-l-ja" xmlns="http://www.w3.org/1999/xhtml">C. 
          $B<U<-(B</h1>
</div>
<div class="rfc-t" id="rfc.section.C.p.1" xmlns="http://www.w3.org/1999/xhtml">
  <div class="t-pair" xmlns="">
<p xml:lang="en" class="t-l-en">The author gratefully acknowledges the contributions of:
Alan Barrett,
Brad Burdick,
Brian Carpenter,
Steve Deering,
Patrik Faltstrom,
Jim Gettys,
Carl Malamud,
Chris Newman,
Kurt Starsinic,
and,
Frank Strauss.</p>
<p xml:lang="ja" class="t-l-ja">$BCx<T$O<!$NJ}!9$N9W8%$K<U0U$rI=$7$^$9(B:
Alan Barrett,
Brad Burdick,
Brian Carpenter,
Steve Deering,
Patrik Faltstrom,
Jim Gettys,
Carl Malamud,
Chris Newman,
Kurt Starsinic,
Frank Strauss$B!#(B</p>
</div>
</div>
</div>
<div id="rfc-copyright" class="rfc-section">
<div class="t-pair" id="rfc.copyright">
<h1 xml:lang="en" class="t-l-en">Full Copyright Statement</h1>
<h1 xml:lang="ja" class="t-l-ja">$B40A4$JCx:n8"@<L@(B</h1>
</div>
<div class="t-pair t-hide-no">
<p class="t-l-en" xml:lang="en">
          Copyright &#x00A9; 
          <a href="http://www.isoc.org/">The Internet Society</a> 
          (1999). 
          All Rights Reserved.
        </p>
<p class="t-l-ja" xml:lang="ja">
          $BCx:n8"(B &#x00A9; 
          <a href="http://www.isoc.org/">The Internet Society</a> 
          (1999)$B!#A48"N1J]!#(B
        </p>
</div>
<div class="rfc-t">
<div class="t-pair t-hide-no">
<p class="t-l-en" xml:lang="en">
            This document and translations of it may be copied 
            and furnished
            to others, and derivative works that comment on or otherwise 
            explain it or assist in its implementation may be prepared, 
            copied, published and distributed, in whole or in part, 
            without restriction of any kind, provided that the 
            above copyright notice 
            and this paragraph are included on all such copies and 
            derivative works. However, this document itself may 
            not be modified in any way, such as by removing the 
            copyright notice or references to the Internet Society 
            or other Internet organizations, except as 
            needed for the purpose of developing Internet standards 
            in which case the procedures for copyrights defined in 
            the Internet Standards process must be followed, or as 
            required to translate it into languages other than English.
          </p>
<p class="t-l-ja" xml:lang="ja">
            $B$3$NJ8=q$H$=$NK]Lu$OJ#<L$7B><T$KDs6!$7$F$bNI$/!"$^$?$3$l$K$D$$$FCm<a$r2C$($k$+$b$7$/$O@bL@$9$k!"$"$k$$$O$=$N<BAu$r=u$1$kGI@8E*:n6H$O!"$=$NA4It$^$?$O0lIt$r!">e5-$NCx:n8"I=<(5Z$S$3$N@a$rA4$F$NJ#<LJ*5Z$SGI@8E*:n6H$K4^$`8B$j$K$*$$$F!"0l@Z$N@)8BL5$7$K!"MQ0U!&J#<L!&=PHG!&G[I[$7$FNI$$!#$7$+$7!"$3$NJ8=q<+BN$O!"Cx:n8"I=<($"$k$$$O(B 
            Internet Society $BKt$OB>$N(B Internet 
            $BAH?%$X$N8@5Z$r<h$j=|$/$J$I!"$$$+$J$kJ}K!$K$;$hJQ99$7$F$O$J$i$J$$!#C"$7!"(B 
            Internet $BI8=`2=2aDx$GDj5A$5$l$?Cx:n8"$N$?$a$N<jB3$-$K=>$$(B 
            Internet $BI8=`$r3+H/$9$kL\E*$KI,MW$J>l9g!"$"$k$$$O1Q8l0J30$N8@8l$KK]Lu$9$k$N$KI,MW$J>l9g$r=|$/!#(B
          </p>
</div>
</div>
<div class="rfc-t">
<div class="t-pair t-hide-no">
<p class="t-l-en" xml:lang="en">
            The limited permissions granted above are perpetual and will 
            not be revoked by the Internet Society or its successors or 
            assigns.
          </p>
<p class="t-l-ja" xml:lang="ja">
            $B>e5-$GG'$a$?$3$N@)8BIU$-5vBz$O915WE*$J$b$N$G$"$j!"(B
            Internet Society $B$b$7$/$O$=$N8e7Q<T$b$7$/$O$=$N>yEO<T$K$h$jGK4~$5$l$k$3$H$O$J$$!#(B
          </p>
</div>
</div>
<div class="rfc-t">
<div class="t-pair t-hide-no">
<p class="t-l-en" xml:lang="en">
            This document and the information contained herein is provided 
            on an $B!H(B<strong>AS IS</strong>$B!I(B basis and 
            <strong>THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
            TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 
            INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 
            THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 
            IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR 
            A PARTICULAR PURPOSE</strong>.
          </p>
<p class="t-l-ja" xml:lang="ja">
            $B$3$NJ8=q5Z$S$3$3$K4^$^$l$k>pJs$O!V(B<strong>$B8=>uM-;Q(B</strong>$B!W$GDs6!$5$l!"(B
            <strong>Internet Society $B$*$h$S(B
            Internet Engineering Task Force (Internet $B5;=QFCJLD4::0Q0w2q(B)
            $B$O$3$3$K4^$^$l$k>pJs$N;HMQ$,$$$+$J$k8"Mx$r$b?/32$7$J$$$H$$$&J]>Z$^$?$O;T>l@-$"$k$$$OFCDjL\E*$X$NE,Ev@-$K$D$$$F$N0EL[E*J]>Z$r4^$a$F$3$l$K8BDj$5$l$J$$!"L@<($"$k$$$O0E<($K$h$k!"0l@Z$NJ]>Z$rH]G'$9$k(B</strong>$B!#(B
          </p>
</div>
</div>
<ins class="t-note t-l-ja" xml:lang="ja">
<p class="rfc-t">
          (<span class="t-note-title">$BLuCm(B:</span>
          $B@5<0$JCx:n8"@<L@$O1Q8l$N86J8$N$_$G$"$j!"Lu<T$O0l@Z$NJ]>Z(B
          ($BK]LuJ8$,86J8$H87L)$K0lCW$7$F$$$k$+$r4^$`$,!"$3$l$K8BDj$5$l$J$$!#(B)
          $B$r$7$J$$!#(B<a href="#rfc-t-copyright">$BLuJ8$K$D$$$F$NCx:n8"@<L@(B</a>$B$b;2>H$;$h!#(B)
        </p>
</ins>
</div>
<div id="rfc-acknowledgement-editor" class="rfc-section">
<div class="t-heading t-pair">
<h1 xml:lang="en" class="t-l-en">Acknowledgement</h1>
<h1 xml:lang="ja" class="t-l-ja">$B<U<-(B</h1>
</div>
<div class="rfc-t">
<div class="t-pair">
<p class="t-l-en" xml:lang="en">
          Funding for the 
          <a href="http://www.rfceditor.org/">RFC editor</a> 
          function is currently provided by the
          <a href="http://www.isoc.org/">Internet Society</a>.
        </p>
<p class="t-l-ja" xml:lang="ja">
<a href="http://www.rfceditor.org/" xml:lang="en">RFC 
          $BJT=8<T(B</a>$B6HL3$N;q6b1g=u$O8=:_(B
          <a href="http://www.isoc.org/">Internet Society</a>
          $B$K$h$j9T$o$l$F$$$^$9!#(B
        </p>
</div>
</div>
</div>
<ins id="rfc-translators-note" class="t-note t-l-ja" xml:lang="ja">
<div class="rfc-section">
<div id="ja.note.mydtd">
<h1 xmlns="http://www.w3.org/1999/xhtml">$B$3$NK]LuJ8$N7A<0$K$D$$$F(B</h1>
</div>
    <p class="rfc-t" id="rfc.section.1.p.1" xmlns="http://www.w3.org/1999/xhtml">$B$3$NJ8=q(B ($B$N86K\(B) $B$O!"(B RFC 2629 
    $B$GDj5A$5$l$?7A<0$K!"K]LuJ8MQ$NMWAG$r(B XML 
    $BL>A06u4V$r;H$C$FDI2C$7$FMQ$$$F$$$^$9!#>\$7$/$O!"(B 
    
  &lt;<a href="http://suika.fam.cx/~wakaba/lang/rfc/translation/" xmlns="">http://suika.fam.cx/~wakaba/lang/rfc/translation/</a>&gt;

    $B$r8fMw2<$5$$!#(B</p>
  </div>
<div class="rfc-section" id="t-change">
<h1>$BK]Lu$NJQ99MzNr(B</h1>
<dl>
<dt>2002-04-30 <a href="mailto:w@suika.fam.cx" title="$BEE;R%a%$%k(B: &lt;w@suika.fam.cx>">$B$o$+$P(B</a>
</dt>
<dd>
<ul>
<li>$BK]Lu40N;!#(B</li>
</ul>
</dd>
<dt>2002-05-03 <a href="mailto:w@suika.fam.cx" title="$BEE;R%a%$%k(B: &lt;w@suika.fam.cx>">$B$o$+$P(B</a>
</dt>
<dd>
<ul>
<li>$BLuCm$r4v$D$+DI2C!#K]LuJQ99MzNr$N>O$r?7@_!#(B</li>
</ul>
</dd>
</dl>
</div>
<div class="rfc-section" id="rfc-t-copyright">
<h1>$BLuJ8$K$D$$$F$NCx:n8"@<L@(B</h1>
<ul>
<li>Copyright &#x00A9; $B$o$+$P(B (2002)$B!#A48"J]N1!#(B</li>
</ul>
<p>
<a href="#rfc-copyright">$B86J8$NCx:n8"@<L@(B</a>$B$,!"LuJ8$K$D$$$F$bF1MM$KE,MQ$5$l$^$9!#(B</p>
<p>$B$^$?!"2~Lu$=$NB>$N86J8$NCx:n8"@<L@$KH?$7$J$$HO0O$K$*$1$k2~JQ$O!"0l@Z$N5v2DL5$/9T$C$F9=$$$^$;$s!#(B</p>
</div>
</ins>
</body>
</html>