Alternatives to the RFC++ "Switch Labels" Proposal
draft-klensin-rfcplusplus-alternatives-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-01-15 (latest revision 2018-07-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-klensin-rfcplusplus-alternatives-00.txt

Abstract

A BoF, identified as RFC++ and focused on possible changes to the identification of a broad range of documents and sources with the term "RFC", has been scheduled for IETF 102 and extensively discussed on an associated mailing list. At least based on the BoF proposal, the BoF was expected to accept a particular problem description as both adequate and sufficiently important to justify changes and then to consider one particular proposal. Mailing list discussions have indicated that neither the problem statement nor the proposal are without controversy. An Internet Draft has been posted that describes that particular proposal in more detail. Without significant analysis of the problem statement, this draft mentions that proposal as a possible member of a family of similar proposals and then outlines some other families of proposals for the convenience of BoF participants and the community more generally.

Authors

John Klensin (john-ietf@jck.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)