Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Mon, 18 November 2019 10:23 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: art@ietf.org, draft-nottingham-rfc7320bis@ietf.org, adam@nostrum.com, mt@lowentropy.net, mt@mozilla.com
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <157407262004.13995.17002547023445908822.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2019 02:23:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ooDOyEvo-XxRW2Pa41SeAQJR4TQ>

The IESG has received a request from an individual submitter to consider the
following document: - 'URI Design and Ownership'
  <draft-nottingham-rfc7320bis-02.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2019-12-16. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
   extensible naming system wherein each scheme's specification may
   further restrict the syntax and semantics of identifiers using that
   scheme."  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of substructure in URIs is often
   problematic.

   This document provides guidance on the specification of URI
   substructure in standards.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-nottingham-rfc7320bis-02.txt> (… The IESG