idnits 2.17.1 draft-stockwell-hnews-url-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-16) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: 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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 121 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 2 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 17, 1998) is 9435 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 94 looks like a reference -- Missing reference section? 'RFC-URI-SYNTAX' on line 102 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft Ted Stockwell 2 draft-stockwell-hnews-url-00.txt early morning software 3 June 17, 1998 4 Expires six months after above date 6 The hnews URL scheme 8 Status of This Memo 10 This document is an Internet-Draft. Internet-Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its 12 areas, and its working groups. Note that other groups may also 13 distribute working documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six 16 months and may be updated, replaced, or obsoleted by other 17 documents at any time. It is inappropriate to use Internet- 18 Drafts as reference material or to cite them other than as 19 "work in progress." 21 To view the entire list of current Internet-Drafts, please check 22 the "1id-abstracts.txt" listing contained in the Internet-Drafts 23 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 24 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 25 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 26 (US West Coast). 28 Abstract 30 HNEWS [1] is an HTTP-tunneling variant of the NNTP news protocol. 31 This document defines the format of Uniform Resource Locators(URLs) 32 identifying news messages and groups provided by HNEWS servers. 33 The syntax of 'hnews' URLs is designed to be compatible with the 34 current common usage of the 'news' URL scheme. Specifically, the 35 'hnews' URL scheme is designed according to recommendations made in 36 [NEWS_URL_SCHEME]. [NEWS_URL_SCHEME] is based on the general 37 specification of all URL schemes in "Uniform Resource Locators (URL): 38 Generic Syntax and Semantics" [RFC URI SYNTAX]. 40 1. The 'hnews' URL scheme 42 The hnews URL scheme is used to designate a message or a set of 43 messages available from an HNEWS server. The hnews URL scheme is 44 meant to designate the same kinds of objects as the 'news' URL 45 scheme except that 'hnews' objects are retrieved using the HNEWS 46 protocol instead of the USENET news protocol used to retrieve 47 'news' objects. 49 Therefore, the syntax of the 'hnews' URL scheme is hereby declared 50 to be EXACTLY the same as the 'news' URL scheme except that 'hnews' 51 URLs begin with the scheme designator "hnews" instead of the scheme 52 designator "news". 53 The semanatics of the 'hnews' URL scheme is hereby declared to be 54 EXACTLY the same as the 'news' URL scheme except that objects 55 referenced by 'hnews' URLs are retrieved with the HNEWS protocol 56 defined in [1] instead of the USENET news protocol used to retrieve 57 objects referenced by 'news' URLs. 58 The default port (in server) of 'hnews' URLs is 80. 60 See [NEWS_URL_SCHEME] for a description of the 'news' URL scheme. 61 If the syntax or semantics of the 'news' URL scheme should be changed 62 by future documents published by the IETF then those future documents 63 also change the syntax or semantics of the 'hnews' URL scheme. 65 2. Examples 67 An URL to read a newsgroup from anywhere (usually locally): 69 71 An URL to read a specific message from anywhere (usually locally): 73 75 An URL to read a specific message from a designated site, using port 76 8080 instead of the default port of 80: 78 80 An URL to read a newsgroup from a designated site: 82 84 An URL to read all the newsgroups from a designated site: 85 Notice that the server name has multiple slashes in it. 86 We know that no message number or message id is specified because the 87 URL ends with a slash. URLs that include a message number or ID will 88 never end with a slash. 90 92 3. References 94 [1] Ted Stockwell, "HNEWS: An HTTP-Tunneling News Protocol", 95 Internet-Draft, , 96 early morning software, July 1998 98 [NEWS_URL_SCHEME] Alfred S. Gilman, "The 'news' URL scheme", 99 Internet-Draft, , 100 Arlington VA, March, 1998 102 [RFC-URI-SYNTAX] Berners-Lee, T., Fielding, R., Masinter L., 103 "Uniform Resource Locators (URL): Generic Syntax and Semantics", 104 Work in Progress , MIT/LCS, 105 U.C. Irvine, Xerox Corporation, Mar 1998. 107 4. Author contact information: 109 Ted Stockwell 110 early morning software 111 2222 Preston Lakes Court 112 Plainfield, IL 60544 113 emorning@ix.netcom.com