idnits 2.17.1 draft-ietf-svrloc-da-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-27) 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 62 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. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 48: '... MAY include in their DAAdverts....' RFC 2119 keyword, line 66: '... Directory Agent MAY include attribute...' RFC 2119 keyword, line 67: '...d Service Agents MAY also use attribut...' 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 (29 July 1998) is 9404 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 96 looks like a reference -- Missing reference section? '2' on line 100 looks like a reference Summary: 10 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 29 July 1998 5 The Directory Agent Service Type 6 draft-ietf-svrloc-da-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@srvloc.org 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 Directory Agent service type. Directory 35 Agents are one of three types of agents used in the Service Location 36 Protocol, Version 2 [1]. The Directory Agent caches services for a 37 set of Service Agents which have been enabled to use SLPv2. User 38 Agents issue requests of Directory Agents to discover services. 40 1. Introduction 42 This document provides a Service Template for SLPv2 Directory Agents. 43 Service templates are defined in [2]. 45 SLPv2 may be used to discover Directory Agents. Directory Agents 46 respond with DAAdvert messages which include attributes. This 47 document describes the standard attributes which Directory Agents 48 MAY include in their DAAdverts. 50 Guttman Expires 29 January 1999 [Page 1] 51 2. The Directory-Agent Service Type 53 -------------------------template begins here----------------------- 54 type=directory-agent 56 version=0.0 58 lang=en 60 description= 61 This defines the directory-agent service type. This service is 62 used by SLPv2 User Agents, who issue service discovery requests 63 and by SLPv2 Service Agents, who register their services with 64 the Directory Agent. The SLPv2 Directory Agent caches the service 65 information and provides scalability to the SLPv2 protocol. The 66 Directory Agent MAY include attribute information in its DAAdvert 67 messages. User Agents and Service Agents MAY also use attributes 68 to select Directory Agents, by issuing SLPv2 Directory Agent 69 discovery Service Requests messages which include a search filter. 71 url-syntax= 72 url-path= ; The URL of the service agent. Defined in [1]. 74 min-lifetime=string L O 75 ; The minimum lifetime the Directory Agent will accept in service 76 ; registrations. 78 max-lifetime=integer L O 79 ; The maximum lifetime the Directory Agent will accept in service 80 ; registrations. 82 --------------------------template ends here------------------------ 84 contacts = "Erik Guttman" 86 3. Security Considerations 88 Authentication of Directory Agent URLs is possible within the context 89 of SLPv2 [1]. Directory Agent URLs may be used by SLPv2 UAs and SAs. 90 If SLPv2 security mechanisms are not used, UAs and SAs will have no 91 guarantee these services actually conform to the selected subset. 93 Guttman Expires 29 January 1999 [Page 2] 94 References: 96 [1] E. Guttman, C. Perkins, J. Veizades, M. Day. Service Location 97 Protocol. draft-ietf-svrloc-protocol-v2-08.txt, July 1998 (work in 98 progress). 100 [2] E. Guttman, C. Perkins, J. Kempf, Service Templates and service: 101 Schemes. draft-ietf-svrloc-service-scheme-10.txt 102 March, 1998 (work in progress). 104 Author Contact Information: 106 Erik Guttman 107 Sun Microsystems 108 Bahnstr. 2 109 74915 Waibstadt Germany 110 Erik.Guttman@sun.com 111 +49 7263 911 701 113 Guttman Expires 29 January 1999 [Page 3]