idnits 2.17.1 draft-naugle-tn3270e-serv-loc-template-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. Found some kind of copyright notice around line 28 but it does not match any copyright boilerplate known by this tool. 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. ** 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. == It seems as if not all pages are separated by form feeds - found 0 form feeds but 5 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in 'Category: Individual Contribution', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 (May 1998) is 9478 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. '3' Summary: 10 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 Jim Naugle 2 Internet Draft Kasthuri Kasthurirangan 3 Category: Individual Contribution IBM 4 Expiration Date: November 98 May 1998 6 TN3270E Service Location and Session Balancing Templates 7 draft-naugle-tn3270e-serv-loc-template-00.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 Areas, 13 and its Working Groups. Note that other groups may also distribute 14 working documents as Internet Drafts. 16 Internet Drafts are draft documents valid for a maximum of six 17 months. Internet Drafts may be updated, replaced, or obsoleted by 18 other documents at any time. It is not appropriate to use Internet 19 Drafts as reference material or to cite them other than as a 20 "working draft" or "work in progress." 22 Please check the I-D abstract listing contained in each Internet 23 Draft directory to learn the current status of this or any Internet 24 Draft. Distribution of this document is unlimited. 26 Copyright Notice 28 Copyright (C) The Internet Society (1998). All Rights Reserved. 30 Abstract 32 These Service Location Protocol templates are to be used to provide 33 service attributes associated with TN3270E servers to client 34 software, or to end users. For more information refer to TN3270E 35 Service Location and Session Balancing Internet-Draft, 36 [1] work in progress. 38 1. Table of Contents 40 Status of This Memo 41 Abstract 42 1. Table of Contents 43 2. Communications Server Service Templates 44 3. TN3270 Service Template 45 4. Security Consideration 46 5. References 47 6. Author's Addresses 49 2. Communications Server Service Templates 51 Communications Server Service Template 53 ---------- template begins here ----------- 55 URL:service:commserver://: 57 The communications server service type is registered whenever the 58 communications software is loaded on the server. It describes generic 59 attributes of the communications server. These attributes are also 60 repeated on the other service types provided. 62 Release = 64 This is the version and release level of the commserver advertising 65 services. Its format is vv.rr.mm where "vv" is the major version 66 number, "rr" is the minor version number, and "mm" is the modification 67 level. All numbers are padded on the left with zeroes to two 68 characters. 69 Example: version 3, release 0, mod level 0 is "03.00.00" 71 Platform = 73 This is the network operating system platform underlying the 74 advertising service. The defined values are: 76 IW Server uses the IntranetWare network operating system 78 NT Server uses the Microsoft NT operating system 80 OS2 Server uses the OS2 operating system 82 AIX Server uses the AIX operating system 84 Protocol = 85 This is the protocol(s) supported by server providing this service. 87 The defined values are: 89 IP Server supports client connections over IP (TCP/IP or 90 UDP/IP) 92 IPX Server supports client connections over IPX (SPX/IPX) 94 Server name = 96 This is the name of the server that was configured during installation. 97 This value has meaning only for the IW platform. 99 ----------- template ends here ----------- 101 3. TN3270 Service Template 103 ---------- template begins here ---------- 105 URL: service:tn3270://: 107 The tn3270 service provides 3270 gateway access to an SNA network via 108 the TN3270 protocol. The attributes reflect the types of 3270 devices, 109 LU Pools, and load information available on the server. 111 Load = : 113 This is the load balancing quantity to use in determining the least 114 loaded comm server to attach to for the service. The range of valid 115 values is an integral 0 to 100 with 0 indicating the lowest possible 116 load and 100 the highest. 118 LU Pool = , 120 /t , 122 /t, ... 124 /t 126 Identifies the LU pool names of LU pools available for use on this 127 service with the associated device types supported in each pool. Each 128 value is a record where the first token is the pool name of the pool 129 and the second token is a device type supported in that pool. A pool 130 name without a device type indicates that LUs of unknown type are 131 included in the pool. Records associated with a given pool name are 132 repeated for each supported device type. A given pool is included in a 133 registration request if any PU profile that contributes at least one 134 LU to the pool is active on the server. The range of valid dev_types 135 are: 137 dev_type Meaning 139 3270002 Lu Type 2 Model 2 141 3270003 Lu Type 2 Model 3 143 3270004 Lu Type 2 Model 4 145 3270005 Lu Type 2 Model 5 147 3270DSC Printer LU 149 BIND, DATA, RESPONSES, SCS, SYSREQ 151 These keyword attributes describe the TN3270e functions supported by 152 this service. 154 BIND The server supports the SNA bind image function 156 DATA The non-SNA 3270 data stream is supported by server 158 RESPONSES The server supports SNA response mode 160 SCS The server supports SNA 3270 SCS data stream 162 SYSREQ The SYSREQ keyboard key is supported on server 164 They are present in the service advertisement if the functions they 165 describe are available. 167 Security = 169 This field will contain the security technique supported by the 170 server. The actual values are currently being defined in the Internet 171 standards body. 173 RFC1576, RFC1646, RFC1647 175 The RFC numbers that document features supported by the service. 176 Current RFC's for TN3270 include 1576, 1646, and 1647. 178 ----------- template ends here ---------- 180 4. Security Consideration 181 This information was taken from Service Templates and service: 182 Schemes Internet-Draft [3] work in progress. 184 Service type templates provide information that is used to interpret 185 information obtained by the Service Location Protocol. If these 186 templates are modified or if false templates are distributed, services 187 may not correctly register themselves, or clients might not be able to 188 interpret service information. 190 The service: URLs themselves specify the service access point and 191 protocol for a particular service type. These service URLs could be 192 distributed and indicate the location of a service other than that 193 normally wanted to used. The Service Location Protocol [2] 194 distributes service: URLs and has an authentication mechnism that 195 allows service: URLs of registered services to be signed and for the 196 signatures to be verified by clients. 198 5. References 200 [1] J. Naugle, K. Kasthurirangan, G. Ledford. TN3270E Service Location 201 and Session Balancing Internet-Draft, May 98. (work in progress) 203 [2] J. Veizades, E. Guttman, C. Perkins, and S. Kaplan. Service 204 Location Protocol. RFC 2165, July 1997. 206 [3] E. Guttman, C. Perkins, J. Kempf. Service Templates and service: 207 Schemes Internet-Draft, March 1998. (work in progress) 209 6. Author's Addresses 211 Jim Naugle 212 IBM 213 P.O. Box 12195 214 Research Triangle Park, N.C. 27709-2195 215 USA 217 Phone: (919) 254-8789 218 EMail: jnaugle@us.ibm.com 220 Kathuri Kasthurirangan 221 IBM 222 P.O. Box 12195 223 Research Triangle Park, N.C. 27709-2195 224 USA 226 Phone: (919) 254-5721 227 EMail: kasthuri@us.ibm.com