idnits 2.17.1 draft-ietf-svrloc-sa-scheme-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-26) 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 1 longer page, the longest (page 1) being 60 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. ** 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 (21 June 1998) is 9441 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 88 looks like a reference -- Missing reference section? '2' on line 91 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 2 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 21 June 1998 5 The Service Agent Service Type 6 draft-ietf-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. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at 21 any time. It is inappropriate to use Internet- Drafts as reference 22 material or to cite them other than as ``work in progress.'' 24 To view the entire list of current Internet-Drafts, please check 25 the ``1id-abstracts.txt'' listing contained in the Internet-Drafts 26 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 27 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 28 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 30 Distribution of this memo is unlimited. 32 Abstract 34 This document describes the Service Agent service type. Service 35 Agents are one of three types of agents used in the Service Location 36 Protocol, Version 2 [1]. The Service Agent advertises all services 37 on a given host which have been enabled to use SLPv2. 39 1. Introduction 41 This document provides a Service Template for Service Agents. 42 Service templates are defined in [2]. 44 SLPv2 may be used to discover Service Agents. This template defines 45 the attributes which SLP User Agents may use to select the 46 appropriate service agent for its needs. 48 Guttman Expires 21 December 1998 [Page 1] 49 2. The "service agent" Service Type 51 -------------------------template begins here----------------------- 52 type=service-agent 54 version=0.0 56 lang=en 58 description= 59 This defines the service-agent service type. This service is 60 used by SLPv2 User Agents to do service discovery in the absense 61 of SLPv2 Directory Agents. By discovering all SLPv2 Service 62 Agents, the User Agents know both their locations (so they may 63 send unicast requests to them) and the scopes they support. 64 Service Agent discovery and the use of service:service-agent 65 URLs is defined in [1]. 67 url-syntax= 68 url-path= ; The URL of the service agent. Defined in [1]. 70 service-type=string M L 71 ; The service types advertised by the Service Agent 73 --------------------------template ends here------------------------ 75 contacts = "Erik Guttman" 77 3. Security Considerations 79 Authentication of Service Agent URLs is possible within the context 80 of SLPv2 [1]. Service Agent URLs may be used by SLPv2 UAs. The 81 use of the service information included in this template allows UAs 82 to select a subset of all SLPv2 SAs. If SLPv2 security mechanisms 83 are not used, the UAs will have no guarantee these services actually 84 conform to the selected subset. 86 References: 88 [1] E. Guttman, C. Perkins, M. Day. Service Location Protocol. 89 draft-ietf-svrloc-protocol-v2-06.txt, June 1998 (work in progress) 91 [2] E. Guttman, C. Perkins, J. Kempf, Service Templates and service: 92 Schemes. draft-ietf-svrloc-service-scheme-10.txt 93 March, 1998 (work in progress) 95 Guttman Expires 21 December 1998 [Page 2] 96 Author Contact Information: 98 Erik Guttman 99 Sun Microsystems 100 Bahnstr. 2 101 74915 Waibstadt Germany 102 Erik.Guttman@sun.com 103 +49 7263 911 701 105 Guttman Expires 21 December 1998 [Page 3]