<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" number="9759" ipr="trust200902" docName="draft-kkuhns-twp-00" category="info" submissionType="independent" xml:lang="en" sortRefs="true" symRefs="true" tocInclude="true" prepTime="2025-04-01T09:29:54" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-kkuhns-twp-00" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9759" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Unified Time Scaling">Unified Time Scaling for Temporal Coordination Frameworks</title>
    <seriesInfo name="RFC" value="9759" stream="independent"/>
    <author initials="K." surname="Kuhns" fullname="Kevin Kuhns">
      <organization showOnFrontPage="true">Yahoo Inc.</organization>
      <address>
        <email>kkevin@yahooinc.com</email>
      </address>
    </author>
    <date month="04" year="2025" day="01"/>
    <keyword>two weeks</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">Estimating time requirements for tasks, both critical and mundane, remains
a challenge in engineering, business, and everyday communication. Existing
models fail due to inherent unpredictability and inconsistencies in human
estimation. This document introduces the Two-Week Principle (TWP), a novel,
universally adaptable time scale that seeks to standardize all temporal
references to a singular, uniform duration. TWP ensures clarity,
predictability, and synchronization across all sectors that rely on time-based
scheduling.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This is a contribution to the RFC Series, independently of any
            other RFC stream.  The RFC Editor has chosen to publish this
            document at its discretion and makes no statement about its value
            for implementation or deployment.  Documents approved for
            publication by the RFC Editor are not candidates for any level of
            Internet Standard; see Section 2 of RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9759" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2025 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology">Terminology</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conversion-guidelines">Conversion Guidelines</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-implementation-consideratio">Implementation Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-post-quantum-effects">Post-Quantum Effects</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conclusion">Conclusion</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.9.2">
              <li pn="section-toc.1-1.9.2.1">
                <t indent="0" pn="section-toc.1-1.9.2.1.1"><xref derivedContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.2">
                <t indent="0" pn="section-toc.1-1.9.2.2.1"><xref derivedContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The problem of time estimation is well-documented. Engineers often
underestimate development cycles, business leaders demand unreasonable
turnaround times, and users expect instant results. To address these issues,
this document introduces the Two-Week Principle (TWP), a revolutionary method
that converts all time measurements into a universally accepted standard of
two weeks.</t>
    </section>
    <section anchor="terminology" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-terminology">Terminology</name>
      <dl newline="false" indent="3" spacing="normal" pn="section-2-1">
        <dt pn="section-2-1.1">Two-Week Principle (TWP):</dt>
        <dd pn="section-2-1.2">This rule states that any given time
duration, regardless of original or intended value, must be converted to two
weeks.</dd>
      </dl>
      <t indent="0" pn="section-2-2">
    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" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> 
    when, and only when, they appear in all capitals, as shown here.
      </t>
    </section>
    <section anchor="conversion-guidelines" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-conversion-guidelines">Conversion Guidelines</name>
      <t indent="0" pn="section-3-1">In TWP, all time-related units are mapped as follows:</t>
      <table anchor="mapping" align="center" pn="table-1">
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Original Time Estimate</th>
            <th align="left" colspan="1" rowspan="1">Standardized TWP Duration</th>
            <th align="left" colspan="1" rowspan="1">Binary Representation</th>
            <th align="left" colspan="1" rowspan="1">Hexadecimal Representation</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">1 second</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">5 minutes</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">24 hours</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">3-5 business days</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">6 months</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">2 years</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">ASAP</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">"It'll be done when it's done"</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">Any value of time not listed above</td>
            <td align="left" colspan="1" rowspan="1">Two weeks</td>
            <td align="left" colspan="1" rowspan="1">100111011000000</td>
            <td align="left" colspan="1" rowspan="1">0x4ec0</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="implementation-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-implementation-consideratio">Implementation Considerations</name>
      <dl newline="true" indent="3" spacing="normal" pn="section-4-1">
        <dt pn="section-4-1.1">Software Compliance:</dt>
        <dd pn="section-4-1.2">
          <t indent="0" pn="section-4-1.2.1">All software displaying time-based data should update their interfaces to replace time values with "two weeks."</t>
        </dd>
        <dt pn="section-4-1.3">Project Management:</dt>
        <dd pn="section-4-1.4">
          <t indent="0" pn="section-4-1.4.1">Tools such as Jira and ServiceNow should enforce a two-week estimate for all task durations.</t>
        </dd>
        <dt pn="section-4-1.5">Business Communications:</dt>
        <dd pn="section-4-1.6">
          <t indent="0" pn="section-4-1.6.1">Organizations must train employees to reflexively respond to all time-related questions with "two weeks."</t>
        </dd>
        <dt pn="section-4-1.7">iCalendar Format Updates:</dt>
        <dd pn="section-4-1.8">
          <t indent="0" pn="section-4-1.8.1">The iCalendar format <bcp14>MUST</bcp14> be updated to support TWP. All
meeting and event timestamps shall be normalized to "two weeks." Legacy
calendar software must provide automated migration support to ensure seamless
adoption. Use of the binary or hexadecimal values in <xref target="mapping" format="default" sectionFormat="of" derivedContent="Table 1"/> may be used but should
not deviate from representations outlined in this document.</t>
        </dd>
      </dl>
    </section>
    <section anchor="post-quantum-effects" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-post-quantum-effects">Post-Quantum Effects</name>
      <t indent="0" pn="section-5-1">TWP introduces significant implications for quantum
      computing and quantum cryptography. Given that quantum uncertainty
      affects temporal precision, a uniform two-week scale may serve as a
      stabilization factor in quantum timekeeping mechanisms, reducing the
      need for complex error correction in time-dependent quantum
      operations. Further research is required to determine whether quantum
      entanglement can reliably synchronize multiple two-week cycles across
      distant computing nodes. However, quantum computing implementations must
      not employ multiple instances of TWP within a scaling variable, as this
      may introduce temporal feedback instabilities and lead to accidental
      spontaneous wormhole creation, an outcome that is outside the
      scope of this document.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">This document has no IANA actions.</t>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-7-1">There are no security concerns associated with this RFC. Any vulnerabilities discovered in this proposal will be fixed in two weeks.</t>
    </section>
    <section anchor="conclusion" numbered="true" removeInRFC="false" toc="include" pn="section-8">
      <name slugifiedName="name-conclusion">Conclusion</name>
      <t indent="0" pn="section-8-1">By adopting TWP, the world will finally standardize time estimation, eliminating stress, miscommunication, and disappointment. This RFC strongly recommends immediate implementation.</t>
    </section>
  </middle>
  <back>
    <references pn="section-9">
      <name slugifiedName="name-references">References</name>
      <references pn="section-9.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="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 indent="0">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" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="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 indent="0">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>
      <references pn="section-9.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="Adams" quoteTitle="true" derivedAnchor="Adams">
          <front>
            <title>The Hitchhiker's Guide to the Galaxy</title>
            <author initials="D." surname="Adams" fullname="">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1979"/>
          </front>
          <refcontent>Pan Books</refcontent>
        </reference>
        <reference anchor="Parkinson" quoteTitle="true" derivedAnchor="Parkinson">
          <front>
            <title>Parkinson's Law</title>
            <author initials="C." surname="Parkinson" fullname="">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1955"/>
          </front>
          <refcontent>The Economist</refcontent>
        </reference>
      </references>
    </references>
    <section anchor="ack" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">The author would like to acknowledge "The Hitchhiker's Guide to the
      Galaxy" <xref target="Adams" format="default" sectionFormat="of" derivedContent="Adams"/> for its timeless reminder that deadlines,
      like the best kind of improbability drives, are often more conceptual
      than practical. The author would also like to acknowledge Cyril
      Northcote Parkinson, whose observation that "work expands to fill the
      time allotted" <xref target="Parkinson" format="default" sectionFormat="of" derivedContent="Parkinson"/> remains as much a cornerstone
      of project planning as it does the flurry of feverish activity that
      often accompanies sprints of last-minute productivity. Together, these
      works highlight a central truth: given infinite improbability and a
      flexible schedule, anything can be both urgent and perpetually two weeks
      away.
      </t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="K." surname="Kuhns" fullname="Kevin Kuhns">
        <organization showOnFrontPage="true">Yahoo Inc.</organization>
        <address>
          <email>kkevin@yahooinc.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
