The 'news' and 'nntp' URI Schemes
RFC 5538

 
Document Type RFC - Proposed Standard (April 2010; No errata)
Was draft-ellermann-news-nntp-uri (individual in gen area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 5538 (Proposed Standard)
Telechat date
Responsible AD Peter Saint-Andre
Send notices to hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com, draft-ellermann-news-nntp-uri@ietf.org

Email authors IPR References Referenced by Nits Search lists

Internet Engineering Task Force (IETF)                      F. Ellermann
Request for Comments: 5538                                         xyzzy
Category: Standards Track                                     April 2010
ISSN: 2070-1721

                   The 'news' and 'nntp' URI Schemes

Abstract

   This memo specifies the 'news' and 'nntp' Uniform Resource Identifier
   (URI) schemes that were originally defined in RFC 1738.  The purpose
   of this document is to allow RFC 1738 to be made obsolete while
   keeping the information about these schemes on the Standards Track.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/5538.

Copyright Notice

   Copyright (c) 2010 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
   (http://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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow

Ellermann                    Standards Track                    [Page 1]
RFC 5538                 'news' and 'nntp' URIs               April 2010

   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Background . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  'nntp' URIs  . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  'news' URIs  . . . . . . . . . . . . . . . . . . . . . . .  4
     2.3.  Query Parts, Fragments, and Normalization  . . . . . . . .  5
   3.  Syntax of 'nntp' URIs  . . . . . . . . . . . . . . . . . . . .  5
   4.  Syntax of 'news' URIs  . . . . . . . . . . . . . . . . . . . .  6
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Internationalization Considerations  . . . . . . . . . . . . .  8
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
     8.1.  'snews' URIs . . . . . . . . . . . . . . . . . . . . . . .  9
     8.2.  'news-message-ID' Access Type  . . . . . . . . . . . . . . 10
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Appendix A.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 13
   Appendix B.  Detailed Example  . . . . . . . . . . . . . . . . . . 13

Ellermann                    Standards Track                    [Page 2]
RFC 5538                 'news' and 'nntp' URIs               April 2010

1.  Introduction

   The first definition for many URI schemes appears in [RFC1738].  This
   memo extracts the 'news' and 'nntp' URI schemes from it to allow that
   material to remain on the Standards Track if [RFC1738] is moved to
   "historic" status.  It belongs to a series of similar documents like
   [RFC4156], [RFC4157], [RFC4248], and [RFC4266], which are discussed
   on the <mailto:uri@w3.org> list.

   The definitions for the 'news' and 'nntp' URI schemes given here are
Show full document text