Rename documents to match I-D naming conventions

Author: DanielOaks

build-client.sh

@@ -1,13 +1,13 @@
 #!/usr/bin/env sh
 
 # make xml
-kramdown-rfc2629 id-oakley-irc-client-latest.mkd > dist/id-oakley-irc-client-latest.xml
+kramdown-rfc2629 draft-oakley-irc-client-latest.mkd > dist/draft-oakley-irc-client-latest.xml
 
 # make txt
-xml2rfc dist/id-oakley-irc-client-latest.xml -o dist/id-oakley-irc-client-latest.txt --text
+xml2rfc dist/draft-oakley-irc-client-latest.xml -o dist/draft-oakley-irc-client-latest.txt --text
 
 # make html
-xml2rfc dist/id-oakley-irc-client-latest.xml -o dist/draft-tmp.html --html
+xml2rfc dist/draft-oakley-irc-client-latest.xml -o dist/draft-tmp.html --html
 
-cat dist/draft-tmp.html | sed -f lib/addstyle.sed > dist/id-oakley-irc-client-latest.html
+cat dist/draft-tmp.html | sed -f lib/addstyle.sed > dist/draft-oakley-irc-client-latest.html
 rm dist/draft-tmp.html

build-ctcp.sh

@@ -1,13 +1,13 @@
 #!/usr/bin/env sh
 
 # make xml
-kramdown-rfc2629 id-oakley-irc-ctcp-latest.mkd > dist/id-oakley-irc-ctcp-latest.xml
+kramdown-rfc2629 draft-oakley-irc-ctcp-latest.mkd > dist/draft-oakley-irc-ctcp-latest.xml
 
 # make txt
-xml2rfc dist/id-oakley-irc-ctcp-latest.xml -o dist/id-oakley-irc-ctcp-latest.txt --text
+xml2rfc dist/draft-oakley-irc-ctcp-latest.xml -o dist/draft-oakley-irc-ctcp-latest.txt --text
 
 # make html
-xml2rfc dist/id-oakley-irc-ctcp-latest.xml -o dist/draft-tmp.html --html
+xml2rfc dist/draft-oakley-irc-ctcp-latest.xml -o dist/draft-tmp.html --html
 
-cat dist/draft-tmp.html | sed -f lib/addstyle.sed > dist/id-oakley-irc-ctcp-latest.html
+cat dist/draft-tmp.html | sed -f lib/addstyle.sed > dist/draft-oakley-irc-ctcp-latest.html
 rm dist/draft-tmp.html

dist/id-oakley-irc-client-latest.html renamed to dist/draft-oakley-irc-client-latest.html

@@ -291,7 +291,7 @@
 
   <meta name="dct.creator" content="Oakley, D., Ed. and J. Allnutt" />
   <meta name="dct.identifier" content="urn:ietf:id:draft-oakley-irc-client-latest" />
-  <meta name="dct.issued" scheme="ISO8601" content="2017-4-20" />
+  <meta name="dct.issued" scheme="ISO8601" content="2017-5-28" />
   <meta name="dct.abstract" content="The Internet Relay Chat (IRC) protocol has been designed over a number of years, with multitudes of implementations and use cases appearing. This document describes the IRC Client-Server protocol." />
   <meta name="description" content="The Internet Relay Chat (IRC) protocol has been designed over a number of years, with multitudes of implementations and use cases appearing. This document describes the IRC Client-Server protocol." />
 
@@ -320,10 +320,10 @@
 </tr>
 <tr>
   <td class="left">Intended status: Informational</td>
-  <td class="right">April 20, 2017</td>
+  <td class="right">May 28, 2017</td>
 </tr>
 <tr>
-  <td class="left">Expires: October 22, 2017</td>
+  <td class="left">Expires: November 29, 2017</td>
   <td class="right"></td>
 </tr>
 
@@ -345,7 +345,7 @@ <h1 id="rfc.status">
 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).  Note that other groups may also distribute working documents as Internet-Drafts.  The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
 <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time.  It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
-<p>This Internet-Draft will expire on October 22, 2017.</p>
+<p>This Internet-Draft will expire on November 29, 2017.</p>
 <h1 id="rfc.copyrightnotice">
   <a href="#rfc.copyrightnotice">Copyright Notice</a>
 </h1>

dist/id-oakley-irc-client-latest.txt renamed to dist/draft-oakley-irc-client-latest.txt

@@ -6,8 +6,8 @@ Network Working Group                                     D. Oakley, Ed.
 Internet-Draft                                                   ircdocs
 Obsoletes: 1459, 2810, 2811, 2812 (if                         J. Allnutt
            approved)                                            Kiwi IRC
-Intended status: Informational                            April 20, 2017
-Expires: October 22, 2017
+Intended status: Informational                              May 28, 2017
+Expires: November 29, 2017
 
 
                   Internet Relay Chat Client Protocol
@@ -41,7 +41,7 @@ Status of This Memo
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on October 22, 2017.
+   This Internet-Draft will expire on November 29, 2017.
 
 Copyright Notice
 
@@ -53,9 +53,9 @@ Copyright Notice
 
 
 
-Oakley & Allnutt        Expires October 22, 2017                [Page 1]
+Oakley & Allnutt        Expires November 29, 2017               [Page 1]
 
-Internet-Draft                 irc-client                     April 2017
+Internet-Draft                 irc-client                       May 2017
 
 
    (http://trustee.ietf.org/license-info) in effect on the date of
@@ -109,9 +109,9 @@ Table of Contents
 
 
 
-Oakley & Allnutt        Expires October 22, 2017                [Page 2]
+Oakley & Allnutt        Expires November 29, 2017               [Page 2]
 
-Internet-Draft                 irc-client                     April 2017
+Internet-Draft                 irc-client                       May 2017
 
 
 2.1.1.  Servers
@@ -165,9 +165,9 @@ Internet-Draft                 irc-client                     April 2017
 
 
 
-Oakley & Allnutt        Expires October 22, 2017                [Page 3]
+Oakley & Allnutt        Expires November 29, 2017               [Page 3]
 
-Internet-Draft                 irc-client                     April 2017
+Internet-Draft                 irc-client                       May 2017
 
 
    o  *Leaf*: A leaf is a server that is only connected to a single
@@ -221,9 +221,9 @@ Authors' Addresses
 
 
 
-Oakley & Allnutt        Expires October 22, 2017                [Page 4]
+Oakley & Allnutt        Expires November 29, 2017               [Page 4]
 
-Internet-Draft                 irc-client                     April 2017
+Internet-Draft                 irc-client                       May 2017
 
 
    Jack Allnutt
@@ -277,4 +277,4 @@ Internet-Draft                 irc-client                     April 2017
 
 
 
-Oakley & Allnutt        Expires October 22, 2017                [Page 5]
+Oakley & Allnutt        Expires November 29, 2017               [Page 5]

dist/id-oakley-irc-client-latest.xml renamed to dist/draft-oakley-irc-client-latest.xml

@@ -28,7 +28,7 @@
       </address>
     </author>
 
-    <date year="2017" month="April" day="20"/>
+    <date year="2017" month="May" day="28"/>
 
 
 
@@ -147,7 +147,7 @@
   </back>
 
 <!-- ##markdown-source:
-H4sIAIMQ+FgAA+1YXW8btxJ931/B6zw4MSS1dpI2MVCghpM27rXjXNtBcZEE
+H4sIAGO1K1kAA+1YXW8btxJ931/B6zw4MSS1dpI2MVCghpM27rXjXNtBcZEE
 LXeXklhTywXJtaKbj9/eM0NytbIdJ/e9AiytqOFw5szhfHg8HheVrXUz2xdd
 mI6fFEXQwah9cdQE5RoVxJkyciUO5zKIQ6NVE8QrZ4OtrClkWTp1tS+0q8YV
 /1bUtmrkAvtrJ6dhbOWlUavxWmBsZFA+FIXvyoX2XtvmYtVCXje1ahXeoKSC

dist/id-oakley-irc-ctcp-latest.html renamed to dist/draft-oakley-irc-ctcp-latest.html

@@ -287,7 +287,8 @@
 <link href="#rfc.section.4" rel="Chapter" title="4 Messages"/>
 <link href="#rfc.section.5" rel="Chapter" title="5 Acknowledgements"/>
 <link href="#rfc.section.6" rel="Chapter" title="6 Security Considerations"/>
-<link href="#rfc.references" rel="Chapter" title="7 Normative References"/>
+<link href="#rfc.section.7" rel="Chapter" title="7 IANA Considerations"/>
+<link href="#rfc.references" rel="Chapter" title="8 Normative References"/>
 <link href="#rfc.appendix.A" rel="Chapter" title="A Message List"/>
 <link href="#rfc.appendix.A.1" rel="Chapter" title="A.1 ACTION"/>
 <link href="#rfc.appendix.A.2" rel="Chapter" title="A.2 CLIENTINFO"/>
@@ -349,6 +350,7 @@ <h1 id="rfc.abstract">
   <a href="#rfc.abstract">Abstract</a>
 </h1>
 <p>This document describes the Client-to-Client Protocol (CTCP), which lets Internet Relay Chat (IRC) clients send each other messages that get displayed or responded to in special ways. CTCP has been widely implemented, with most clients supporting it natively. This document outlines how to implement CTCP and the most common messages used.</p>
+<p>It updates RFC 1459 and RFC 2812.</p>
 <h1 id="rfc.status">
   <a href="#rfc.status">Status of This Memo</a>
 </h1>
@@ -376,7 +378,8 @@ <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
 </ul><li>4.   <a href="#rfc.section.4">Messages</a></li>
 <li>5.   <a href="#rfc.section.5">Acknowledgements</a></li>
 <li>6.   <a href="#rfc.section.6">Security Considerations</a></li>
-<li>7.   <a href="#rfc.references">Normative References</a></li>
+<li>7.   <a href="#rfc.section.7">IANA Considerations</a></li>
+<li>8.   <a href="#rfc.references">Normative References</a></li>
 <li>Appendix A.   <a href="#rfc.appendix.A">Message List</a></li>
 <ul><li>A.1.   <a href="#rfc.appendix.A.1">ACTION</a></li>
 <li>A.2.   <a href="#rfc.appendix.A.2">CLIENTINFO</a></li>
@@ -462,7 +465,9 @@ <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#security-consid
 <p id="rfc.section.6.p.3">Older CTCP specifications describe including more than one CTCP message inside a single PRIVMSG or NOTICE command. Implementations SHOULD NOT implement this form of CTCP parsing as it is not widely-implemented and may result in an implementation that can be attacked or spammed more easily.</p>
 <p id="rfc.section.6.p.4">CTCP requests can be abused to flood clients off a server. Clients may ignore or throttle excessive incoming requests to protect against this.</p>
 <p id="rfc.section.6.p.5">Many servers implement optional filtering to prevent any CTCP messages apart from ACTION from being sent to channels. When this is done, it can typically be enabled or disabled by channel operators with a channel mode.</p>
-<h1 id="rfc.references"><a href="#rfc.references">7.</a> Normative References</h1>
+<h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a href="#iana-considerations" id="iana-considerations">IANA Considerations</a></h1>
+<p id="rfc.section.7.p.1">This document has no actions for IANA.</p>
+<h1 id="rfc.references"><a href="#rfc.references">8.</a> Normative References</h1>
 <table>
   <tbody>
     <tr>