idnits 2.17.1 draft-guttman-svrloc-sa-scheme-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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? == 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 64 lines 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 an Authors' Addresses Section. ** There are 8 instances of too long lines in the document, the longest one being 3 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 copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (11 October 1999) is 8963 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 99 looks like a reference -- Missing reference section? '2' on line 102 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Service Location Working Group Erik Guttman 2 INTERNET DRAFT Sun Microsystems, Inc 3 11 October 1999 5 The Service Agent Service Type 6 draft-guttman-svrloc-sa-scheme-00.txt 8 Status of This Memo 10 This document is a submission by the Service Location Working Group 11 of the Internet Engineering Task Force (IETF). Comments should be 12 submitted to the srvloc@corp.home.net mailing list. 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC 2026 [1]. 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at 24 any time. It is inappropriate to use Internet- Drafts as reference 25 material or to cite them other than as ``work in progress.'' 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 To view the entire list of current Internet-Drafts, please check 34 the ``1id-abstracts.txt'' listing contained in the Internet-Drafts 35 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 36 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 37 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 39 Distribution of this memo is unlimited. 41 Abstract 43 This document describes the Service Agent service type. Service 44 Agents are one of three types of agents used in the Service Location 45 Protocol, Version 2 [1]. The Service Agent advertises all services 46 on a given host which have been enabled to use SLPv2. 48 1. Introduction 50 This document provides a Service Template for Service Agents. 51 Service templates are defined in [2]. 53 SLPv2 may be used to discover Service Agents. This template defines 54 the attributes which SLP User Agents may use to select the 55 appropriate service agent for its needs. 57 Guttman Expires 11 April 2000 [Page 1] 58 2. The "service agent" Service Type 60 Name of Submitter = "Erik Guttman" 61 Language of Template = en 62 Security Considerations = See section 3, below. 63 Template Text: 64 -------------------------template begins here----------------------- 65 template-type=service-agent 67 template-version=0.1 69 lang=en 71 template-description= 72 This defines the service-agent service type. This service is 73 used by SLPv2 User Agents to do service discovery in the absense 74 of SLPv2 Directory Agents. By discovering all SLPv2 Service 75 Agents, the User Agents know both their locations (so they may 76 send unicast requests to them) and the scopes they support. 77 Service Agent discovery and the use of service:service-agent 78 URLs is defined in [1]. 80 template-url-syntax= 81 url-path= ; The URL of the service agent. Defined in [1]. 83 service-type=string M L 84 ; The service types advertised by the Service Agent 86 --------------------------template ends here------------------------ 88 3. Security Considerations 90 Authentication of Service Agent URLs is possible within the context 91 of SLPv2 [1]. Service Agent URLs may be used by SLPv2 UAs. The 92 use of the service information included in this template allows UAs 93 to select a subset of all SLPv2 SAs. If SLPv2 security mechanisms 94 are not used, the UAs will have no guarantee these services actually 95 conform to the selected subset. 97 References: 99 [1] E. Guttman, C. Perkins, J. Veizades, M. Day. Service Location 100 Protocol. RFC 2608, June 1999. 102 [2] E. Guttman, C. Perkins, J. Kempf, Service Templates and service: 103 URLs. RFC 2609, June 1999. 105 Guttman Expires 21 December 1998 [Page 2] 106 Author Contact Information: 108 Erik Guttman 109 Sun Microsystems 110 Eichhoelzelstr. 7 111 74915 Waibstadt Germany 113 Erik.Guttman@sun.com 114 +49 7263 911 701 116 Full Copyright Statement 118 Copyright (C) The Internet Society (1999). All Rights Reserved. 120 This document and translations of it may be copied and furnished to 121 others, and derivative works that comment on or otherwise explain it 122 or assist in its implementation may be prepared, copied, published 123 and distributed, in whole or in part, without restriction of any 124 kind, provided that the above copyright notice and this paragraph are 125 included on all such copies and derivative works. However, this 126 document itself may not be modified in any way, such as by removing 127 the copyright notice or references to the Internet Society or other 128 Internet organizations, except as needed for the purpose of 129 developing Internet standards in which case the procedures for 130 copyrights defined in the Internet Standards process must be 131 followed, or as required to translate it into languages other than 132 English. 134 The limited permissions granted above are perpetual and will not be 135 revoked by the Internet Society or its successors or assigns. 137 This document and the information contained herein is provided on an 138 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 139 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 140 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 141 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 142 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 144 Guttman Expires 11 April 1998 [Page 3]