<?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.39 (Ruby 3.4.9) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-todo-kevinmcm-tutorial-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.0 -->
  <front>
    <title abbrev="TODO - GHTUTRL">kevinmcm - Github tutorial</title>
    <seriesInfo name="Internet-Draft" value="draft-todo-kevinmcm-tutorial-00"/>
    <author fullname="Kevin McMenamy">
      <organization>Cisco</organization>
      <address>
        <email>kevinmcm@cisco.com</email>
      </address>
    </author>
    <date year="2026" month="July" day="19"/>
    <keyword>next generation</keyword>
    <keyword>unicorn</keyword>
    <keyword>AI-native</keyword>
    <abstract>
      <?line 38?>

<t>This is where the abstract should be written</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://kevinmcm-github.github.io/github-tutorial/draft-todo-kevinmcm-tutorial.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-todo-kevinmcm-tutorial/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/kevinmcm-github/github-tutorial"/>.</t>
    </note>
  </front>
  <middle>
    <?line 43?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>This is where the introduction should be written</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 83?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA31U227bOBB951dMlbeisuttgLZCb6rtJMbaces4KIrFPlDk
2CIskQJJxfUG+Zd+y37ZDiXZiZNgAcPinJk5wzkzUhzHzCtfYALRBm+ULkUJ
MZwrn9cZ+Nobq3gRMZ5lFm8oaDkfzUPAxfJ6uZhGTHCPa2N3CSi9MoxJIzQv
iU5avvKxN9LEe+J4zxe/fs1cnZXKOWW031UUPxkvzwBOgBfOUB2lJVZIf9pH
ryBCqbqrkDFJv9LDWDotlmcR03WZoU2YpLskTBjtULvaJeBtjYxu/YYRr0We
QLoYp2Rsjd2sramrBH6cww+ylF7DeUDYBnfklgmjNjX+8rBGjZZ7ummAaq2E
sc0xncSa8Buqgbqm0icAB9ZgtJ0d0xNcclWEkC/4i5dVgT1hyoBzK/IEcu8r
l/T7D5x9oiPqZigPBhW3SL99xPfTAihICucpds/2KKfXPZR5nN3/v8H1cl8S
P+O1z40NElEtgFVdFO3U/wwZMBMzJHvXOI1dc63+aQRMYKicMA2OrQz7Gl9E
8DRSMG1s2QibMBbW6t7q9XqMxXEMPHPecuEZW+bKAf22OVoEn+PBBy43dSEh
Q9ha5T1q1iaXSsoCGWk+0d4aWYtmus9QqQf+Z+lOYGg0jT8EOOBawghXSqvG
DoxIHe7CwkkH0ez6ahk2ODzhct6cF+Pv15PFeBTOVxfpdHo4sC7i6mJ+PR3d
n+4zh/PZbHw5apMJhSOIRbP0J3nCraL5t+VkfplOI+qJWqMu6VWtS7p5eDXA
m9AXtYu2suhRAndMohNWZWRQztfht39/D07h9vbF4mz4x2Dw/u6uM94N3p6S
QbLptprRxa4zScUd41WF3AYWXhQgeKU8vecU64KoWw1BcJrsy7+CMn8n8CET
1eD0UweEho/AvWZHYKPZU+RJciviM9AzZQ5qHuGPlD6+b/rzyN7r/gD88LlQ
GiEevPv8iTU7dIWippXahWVySnafm7A/4XO79zahk/QyfRp2NM+cZNWmjeTN
6rpet/kZF5vAkoqNNtsC5TpkOHabtB9RlB+jFY0Go7uuOD9E0oD+Az1L6bAv
BgAA

-->

</rfc>
