<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.11 (Ruby 3.2.4) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-rankin-ccsv-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.21.0 -->
  <front>
    <title abbrev="CCSV">Control Character Separated Value Files</title>
    <seriesInfo name="Internet-Draft" value="draft-rankin-ccsv-00"/>
    <author fullname="Mike Rankin">
      <organization>Individual Contributor</organization>
      <address>
        <email>mrankin@oldgrognard.pub</email>
      </address>
    </author>
    <date year="2024" month="May" day="16"/>
    <keyword>next generation</keyword>
    <keyword>unicorn</keyword>
    <keyword>sparkling distributed ledger</keyword>
    <abstract>
      <?line 37?>

<t>TODO Abstract</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://oldgrognard.github.io/ccsv-id/draft-rankin-ccsv.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-rankin-ccsv/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/oldgrognard/ccsv-id"/>.</t>
    </note>
  </front>
  <middle>
    <?line 42?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>TODO Introduction</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>TODO Security</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
    <?line 82?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA21U227bOBB951fMqm/Fyq63AdoVelNtpzWQxK3ttCiKfaDE
sUWYIgVenLpB/mW/Zb9sh5LtRE1f7JkzVx4eKk1T5qVXmEEyNtpbo2BccctL
jxaW2JDpUcAXrgLCuVToEsaLwuIuVoyXXxJWUsbG2H0GUq8NY8KUmtfUUVi+
9qnleit1WpZulz57xlwoaumcpGH7hpJm09U5wBPgyhlqKbXABulH++RPSFBI
b6zkKjqz/D39GUvWYnWeMB3qAm3GBC2QsdJoh9oFl4G3ARkt+JxRX4s8g3wx
zcm5MXa7sSY0GXz9AF/Jk3oDHyLCtrinsMgYpKDxh4cNaqTT06YRClqWxram
I1a2KlYK6byVRYgUKRQbtGyHOtA2TwBOg6LTHbY/keCaSxVT3uEPXjcKB6Wp
I85tWWVQed+4bDh8EBxSO2otfRUKossoQWM2mlsxbBmWIqG4Ikacp/ixw4O8
QVc8kOZYMXx0UYPK1yphjAdfGRspoaYA66BUd7XJpdwiLNqKpI0Zu+Fa/mz5
ovhMC7mTInDSU9RVJMnYLhW7Uyd1N/Hdw+WaUNBcbWxNnXZEJIuiuvdYmqbA
C6KdJMrYaj6ZQ35y22gthVDIiMZZFLQIZXuHXW4fohzajq4sug64FjDBtdSy
9amkQiBdRN0IR4e+Xq6iEOM/XM1bezH9fD1bTCfRXn7MLy5OBjtkLD/Ory8m
99Z95Xh+eTm9mnTFhEIPYsll/o0icatk/mk1m1/lFwk9MvCVdEDPLNS0eVQ4
eAMFUohebWMxypE7JtCVRDw5VPN+/Om/f0dncHv7x+J8/Ndo9Pfd3cF5OXpx
Rs5NhbqbZrTaH1xf4Z7xpkFuYxeuFJS8kZ6eK+U6cJW50VChxQFjT79HZv7J
4FVRNqOzNwcgHrgHHjnrgS1nj5FHxR2Jv4F+M+bEZg//hen+vvm3nn/k/QH4
6i29fYR09PLtG9ZqaIllsNLvo5icFIevhjtI7hhtU2f5Vf44rXefFdGqTZfJ
W6G6wUHaBS+3sUtebrW5iV+cWOHYbdZ9C1G8TtZ0NZjcHYbzUyZd0P+Y/GvP
7gUAAA==

-->

</rfc>
