idnits 2.17.1 draft-ietf-svrloc-wpyp-01.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-25) 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 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 3 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 16 characters in excess of 72. 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 (October 1997) is 9689 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Obsolete normative reference: RFC 1959 (ref. '3') (Obsoleted by RFC 2255) -- Possible downref: Non-RFC (?) normative reference: ref. '4' == Outdated reference: A later version (-09) exists of draft-fielding-url-syntax-05 -- Possible downref: Normative reference to a draft: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 10 errors (**), 0 flaws (~~), 4 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Ryan Moats 3 draft-ietf-svrloc-wpyp-01.txt AT&T 4 Expires in six months October 1997 6 The 'wp:' and 'yp:' Abstract Service Types 7 Filename: draft-ietf-svrloc-wpyp-01.txt 9 Status of This Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as ``work 20 in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net 25 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Abstract 30 This document presents definitions for the 'wp:' (white pages) and 31 'yp:' (yellow pages) abstract services. 33 1. Introduction 35 In "Advertising Services" [1], several abstract services are 36 proposed. As specified in [2], the "wp:" (white pages) and "yp:" 37 yellow pages abstract services are documented here. 39 2. The "wp" Abstract Service 41 The "wp" abstract service is for locating people via directory or 42 "white pages" services. Version 0.0 of this service specifies four 43 protocols for accessing such services: LDAP, WHOIS++, CCSO/Ph and 44 HTTP. 46 type = wp 48 version = 0.0 50 language = EN 52 description = 53 The WP Abstract Service is for locating people via "white pages" services. 55 url-syntax = 56 url-path = ldapurl / whoisppurl / phurl / httpurl 57 ldapurl = url as defined in [3] 58 whoisppurl = url as defined in [4] 59 httpurl = url as defined in [5] 60 phurl = "ph://" hostport 61 hostport = host [ ":" port ] 62 host = hostname / hostnumber 63 hostname = *( domainlavel "." ) toplabel 64 domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum 65 toplabel = alpha / alpha * [alphanum / "-"] alphanum 66 hostnumber = ipv4-number / ipv6-number 67 ipv4-number = 1*3digit 3*3("." 1*3digit) 68 ipv6-number = 32*hex 69 3digit = digit digit digit 70 port = 1*digit 71 ; A port number must be included if the 72 ; protocol field does not have an IANA 73 ; assigned port number. 74 alphanum = alpha / digit 75 alpha = "a" / "b" / "c" / "d" / "e" / "f" / "g" / 76 "h" / "i" / "j" / "k" / "l" / "m" / "n" / 77 "o" / "p" / "q" / "r" / "s" / "t" / "u" / 78 "v" / "w" / "x" / "y" / "z" / 79 "A" / "B" / "C" / "D" / "E" / "F" / "G" / 80 "H" / "I" / "J" / "K" / "L" / "M" / "N" / 81 "O" / "P" / "Q" / "R" / "S" / "T" / "U" / 82 "V" / "W" / "X" / "Y" / "Z" 83 digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / 84 "7" / "8" / "9" 86 3. The "yp" Abstract Service 88 To locate resource on the Internet, a client would use the "Yellow 89 Pages" service and version 0.0 of the "yp" abstract service specifies 90 two protocols for accessing such services: Z39.50 and HTTP. 92 type = yp 93 version = 0.0 95 language = EN 97 description = 98 The yp Abstract Service is for locating resource via "yellow pages" services. 100 url-syntax = 101 url-path = z3950url / httpurl 102 z3950url = url as defined in [6] 103 httpurl = url as defined in [5] 105 4. Security Considerations 107 The templates presented here are subject to the same implications as 108 other service templates specified according to [2] and [7]. 110 5. Acknowledgments 112 This work described in this document is partially supported by the 113 National Science Foundation, Cooperative Agreement NCR-9218179. 115 6. References 117 Request For Comments (RFC) and Internet Drafts documents are 118 available from and numerous mirror sites 120 [1] R. Moats, M. Hamilton, "Advertising Services," 121 Internet Draft (work in progress), February 1997. 123 [2] E. Guttman, "The service: URL Scheme," Internet 124 Draft (work in progress), 20 November 1996. 126 [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, 127 June 1996. 129 [4] M. Hamilton, "WHOIS++ URL Specification," Internet 130 Draft (work in progress), May 1997. 132 [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni- 133 form Resource Locators (URL): Generic Syntax and 134 Semantics," RFC1738 as amended by RFC1808 and 135 updated by draft-fielding-url-syntax-05.txt, May 136 1997. (work in progress). 138 [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource 139 Locators for Z39.50," RFC 2056, November 1996. 141 [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, 142 "Service Location Protocol," Internet Draft (work 143 in progress), 8 January 1997. 145 7. Author's addresses 147 Ryan Moats 148 AT&T 149 15621 Drexel Circle 150 Omaha, NE 68135-2358 151 USA 153 Phone: +1 402 894-9456 154 EMail: jayhawk@att.com