idnits 2.17.1 draft-ietf-svrloc-nrsm-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 the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard 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. ** 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: Normative reference to a draft: ref. '3' Summary: 8 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Service Location Working Group Mikael Pahmp 2 INTERNET DRAFT Axis Communications 3 23 June 1999 Erik Guttman 4 Sun Microsystems, Inc 5 Kent Lidstrom 6 Axis Communications 8 The Networked Removable Storage Media Abstract Service Type 9 draft-ietf-svrloc-nrsm-scheme-00.txt 11 Status of This Memo 13 This document is a submission by the Service Location Working Group 14 of the Internet Engineering Task Force (IETF). Comments should be 15 submitted to the srvloc@srvloc.org mailing list. 17 Distribution of this memo is unlimited. 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC2026. Internet-Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its areas, 22 and its working groups. Note that other groups may also distribute 23 working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at 27 any time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at: 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at: 36 http://www.ietf.org/shadow.html. 38 Abstract 40 This document describes the Abstract Service Type for removable 41 networked storage media. These include CD-ROMs, DVDs, DAT tapes, 42 optical disks and other media types. Through the use of this 43 template and the Service Location Procotocol [1] networked 44 removable storage devices can advertise the currently available 45 media and client systems can discover them. 47 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 1] 48 1. Introduction 50 It is increasingly common to find networked storage devices which 51 are available using a range of access protocols. One common class 52 of storage devices allow removable storage (such as CD-ROMs, tapes 53 and optical disks) to be made available to the network simply by 54 inserting the media to the networked storage device. 56 This presents a problem: How are clients to discover which media 57 is currently available, or becomes avaiLable over time? By using 58 SLP [1] and advertising the attributes of the removable storage 59 media, the data on the storage media becomes accessible without 60 any prior client configuration. 62 Abstract Service templates are defined in [2]. 64 2. Definitions 66 This document defines the Networked Removable Storage Media abstract 67 service type and two concrete types for the CIFS and NCP file sharing 68 protocols. 70 2.1. CIFS 72 The Common Internet File System (CIFS) protocol [3] is based on the 73 standard Server Message Block (SMB) protocol widely in use by 74 personal computers and workstations running a wide variety of 75 operating systems. 77 2.2. NCP 79 The NetWare Core Protocol (NCP) is one of the core protocols of the 80 NetWare (TM) operating system. No known public specification of this 81 protocol exists. Clients with access to a NCP client implementation 82 may still use the information available in a Networked Removable 83 Storage Media service: URL of the NCP concrete type to access the 84 media. 86 2.3. UNC 88 Networked Removable Storage Media service: URLs of the CIFS or NCP 89 concrete type uses a Uniform Naming Convention (UNC) [3] path string 90 as part of the url-path to describe the network path to the media. 91 Client implementations of the CIFS and NCP protocols usually accepts 92 UNC path strings for accessing shared network storage resources. 94 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 2] 95 3. Networked Removable Storage Media Service Template 97 Name of submitters: Mikael Pahmp 98 Erik Guttman 99 Kent Lidstrom 101 Language of service template: en 103 Security Considerations: 104 The attributes included in the template, especially those concerning 105 access control, are to be used to provide clients with configuration 106 information regarding server features, not security per se. 107 Authentication of and access control must be performed by the data 108 access protocols themselves. 110 Template Text: 111 -------------------------template begins here----------------------- 112 template-type = nrsm 114 template-version = 0.0 116 template-description = 117 This is an abstract service type defining Networked Removable 118 Storage Media. 120 template-url-syntax = 121 url-path = ; Depends on the concrete service type. 122 ; See these templates. 124 media-name = STRING 125 ; This is the human readable name for this media. The name may be 126 ; given by the media itself or user defined. 128 capacity = INTEGER 0 129 ; This is the memory capacity of the storage media, in units of 130 ; kilobyte. 132 writeable = BOOLEAN 133 ; If this is TRUE, then the media is read/write. If it is FALSE 134 ; the media is read-only. Note that stating that media is read/ 135 ; write does not indicate that *anyone* may write to it. Access 136 ; control may be in place preventing unauthorized writing to the 137 ; media. 139 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 3] 140 media-type = STRING L 141 ; This is the media type of the removable media. This can take 142 ; one of the following values: 143 ; 144 ; CDROM The removable media is a CD with data content. 145 ; DVD The media is a DVD. 146 ; JAZ The media is a JAZ diskette. 147 ; DAT The media is a DAT tape. 148 ; OPTICAL The media is an optical disk. 149 ; TAPE The media is a tape. 150 CDROM,DVD,JAZ,DAT,OPTICAL,TAPE 152 volume-description = STRING 153 ; This string describes the contents of the removable storage 154 ; media. This string will be supplied to users in user interfaces 155 ; to provide them with information to determine whether this 156 ; particular storage media is of interest. 158 access-control = BOOLEAN O 159 ; This indicates that access control is being used to limit the 160 ; availability of the storage media. No attempt is made to define 161 ; *what* access control is in place if the value of this attribute 162 ; is TRUE. 164 used-space=INTEGER O 165 ; The amount of used space of the storage media, 166 ; in units of kilobytes. 168 file-system = STRING O 169 ; The file system present on the networked storage media. For 170 ; example "ISO 9660 with Rock Ridge Extensions" 172 worm = BOOLEAN O 173 ; If this is TRUE, the media supports Write Once Read Many: Thus 174 ; data can be appended but not deleted or altered on the media. 176 contact-person = STRING O 177 ; The name of a contact person who is the operator of the removable 178 ; storage media device. This is the person to contact to 179 ; unload or load particular media if the storage device if is in a 180 ; remote location. It is suggested that this string include 181 ; information that would enable other humans to reach the contact 182 ; person, such as a phone number or an email address. 184 location = STRING O 185 ; The physical location of the removable storage media device. 186 ; This should be a descriptive human readable text. 188 --------------------------template ends here------------------------ 190 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 4] 191 3.1. Concrete 'nrsm' Service Template for CIFS 193 Name of submitters: Mikael Pahmp 194 Erik Guttman 195 Kent Lidstrom 197 Language of service template: en 199 Security Considerations: 200 See the security considerations of the nrsm template. 202 Template Text: 203 -------------------------template begins here----------------------- 204 template-type = nrsm:cifs 206 template-version = 0.0 208 template-description = 209 This is the concrete service template for CIFS access to Networked 210 Removable Storage Media. 212 template-url-syntax = 213 url-path = "/" unc-path 214 ; "unc-path" is a UNC path string as defined in [3] and escaped 215 ; according to the rules in [2]. 217 --------------------------template ends here------------------------ 219 3.2. Concrete 'nrsm' Service Template for NCP 221 Name of submitters: Mikael Pahmp 222 Erik Guttman 223 Kent Lidstrom 225 Language of service template: en 227 Security Considerations: 228 See the security considerations of the nrsm template. 230 Template Text: 231 -------------------------template begins here----------------------- 232 template-type = nrsm:ncp 234 template-version = 0.0 236 template-description = 237 This is the concrete service template for NCP access to Networked 238 Removable Storage Media. 240 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 5] 241 template-url-syntax = 242 url-path = "/" unc-path 243 ; "unc-path" is a UNC path string as defined in [3] escaped 244 ; according to the rules in [2]. 246 --------------------------template ends here------------------------ 248 4. Security Considerations 250 The attributes included in the nrsm service template, especially those 251 concerning access control, are to be used to provide clients with 252 configuration information regarding server features, not security per 253 se. Authentication of and access control must be performed by the 254 data access protocols themselves. 256 SLP [1] provides authentication features which allow clients to verify 257 the authenticity of URLs and service attributes. If the attributes 258 present in this service template are obtained in a different manner 259 (than SLP) they may be supplied by a malicious source attempting to 260 misdirect clients or hide available resources. 262 5. References 264 [1] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service 265 Location Protocol Version 2", RFC 2608, June 1999. 267 [2] Guttman, E., Perkins, C. and J. Kempf, "Service Templates and 268 service: Schemes", RFC 2609, June 1999. 270 [3] Leach, P. and D. Naik, "A Common Internet File System (CIFS/1.0) 271 Protocol", draft-leach-cifs-v1-spec-01.txt, 272 December 1997 (work in progress) 274 6. Authors' Addresses 276 Mikael Pahmp Erik Guttman 277 Axis Communications Sun Microsystems 278 Scheelev. 16 Bahnstr. 2 279 S-223 70 Lund, Sweden 74915 Waibstadt Germany 280 Mikael.Pahmp@axis.com Erik.Guttman@sun.com 281 +46 46 270 1881 +49 7263 911 701 283 Kent Lidstrom 284 Axis Communications 285 Scheelev. 16 286 S-223 70 Lund, Sweden 287 Kent.Lidstrom@axis.com 288 +46 46 270 1941 290 Pahmp,Guttman,Lidstrom Expires 23 December 1999 [Page 6]