Just because it's an ID doesn't mean anything... at all...
draft-wkumari-not-a-draft-08

Document Type Active Internet-Draft (individual)
Last updated 2020-02-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          W. Kumari
Internet-Draft                                          February 4, 2020
Intended status: Standards Track
Expires: August 7, 2020

       Just because it's an ID doesn't mean anything... at all...
                      draft-wkumari-not-a-draft-08

Abstract

   Anyone can publish an Internet Draft.  This doesn't mean that the
   "IETF thinks" or that "the IETF is planning..." or anything similar.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 https://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on August 7, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kumari                   Expires August 7, 2020                 [Page 1]
Internet-Draft           Anyone can write an ID            February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Feature Creep . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . .   6
   Appendix B.  new section  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   All too often one reads something in the press, or some ravings on a
   mailing list that reference some Internet Draft, that claim that "the
   IETF thinks that XXX" or that the ID is an IETF document, and so
   represents support by the IETF.

   Repeatedly pointing at the RFC Editor page, carefully explaining what
   an ID is (and isn't), describing how consensus is reached, detailing
   the Independent Stream, etc doesn't seems to accomplish much.

   So, here is an Internet Draft.  I wrote it.  It's full of nonsense.
   It doesn't represent the "IETF's views"; it doesn't mean that the
   IETF, the IESG, the RFC editor, any IETF participant, my auntie on my
   father's side twice removed, me, or anyone else believes any of the
   drivel in it.  [Editor note: Interestingly, after publishing version
   -00 of this ID I got some feedback saying that some participants *do*
   believe the below.  As I plan to actually get this published as a
   (probably AD sponsored) RFC, I guess someone will need to judge
   consensus at IETF LC ]

   Readers are expected to be familiar with Section 2.5 of [RFC2410] and
   [RFC2321]

1.1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Kumari                   Expires August 7, 2020                 [Page 2]
Internet-Draft           Anyone can write an ID            February 2020

2.  Background

   Pyramids are good for sharpening razor blades.  The ancient Egyptians
   has a major problem - wearing a big, bushy beard in the desert is
   uncomfortable.  Unfortunately the safely razor hadn't been invented
   yet, and so they all had to use straight razors.  Additionally, camel
   leather makes a very poor strop, hippopotamus leather was reserved
   for the pharaohs and crocodile leather, while suitable, had the
Show full document text