[Search] [txt|pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 rfc3049                                     
TN3270E Working Group                                      Jim Naugle
Internet Draft:                                Kathuri Kasthurirangan
<draft-ietf-tn3270e-service-loc-02.txt>                           IBM
Expiration Date: November 98                            Gregg Ledford
                                                   Zephyr Development
                                                              July 98


           TN3270E Service Location and Session Balancing
             draft-ietf-tn3270e-service-loc-02.txt

Status of This Memo

   This document is an Internet Draft.  Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its Areas,
   and its Working Groups.  Note that other groups may also distribute
   working documents as Internet Drafts.

   Internet Drafts are draft documents valid for a maximum of six
   months.  Internet Drafts may be updated, replaced, or obsoleted by
   other documents at any time.  It is not appropriate to use Internet
   Drafts as reference material or to cite them other than as a
   "working draft" or "work in progress."

   Please check the I-D abstract listing contained in each Internet
   Draft directory to learn the current status of this or any Internet
   Draft.  Distribution of this document is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Abstract

   This document discusses the implementation of Service Location
   Protocol and session balancing with a TN3270E emulator in a client
   server implementation with a TN3270E server.

   Application program developer's can locate TN3270E services and
   load balance among those services (3270 host sessions), by using
   this Service Location Protocol support.











Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 1]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

1. Table of Contents

Status of This Memo
Abstract
 1. Table of Contents
 2. Introduction and Terminology
     2.1 Terminology
 3. An Overview of RFC 2165
     3.1 SLP Agents
     3.2 Service Agents
     3.3 User Agents
 4. TN3270E Server Environment and Load
     4.1 TN3270E Server Load
 5. TN3270E Client Configuration
     5.1 SLP Scope
     5.2 DA-Discovery Time-Out
     5.3 SA-Discovery Time-Out
 6. TN3270E Client Implementation Information
     6.1 Overview
     6.2 How to Obtain List of TN3270E Servers Supporting SLP
     6.3 TN3270E Sample Client Flow
        6.3.1 Open the SLP connection
        6.3.2 Query the list of TN3270E servers
        6.3.3 Determine loading of each TN3270E server
     6.4 Recommendations
 7. Sample Trace Flow of SLP and Session Balancing
 8. Service Templates and Service Registration
     8.1 TN3270 Service Template
     8.2 Server Service Template
     8.3 Template Contact Information
     8.4 Security Considerations
     8.5 TN3270 Service Registration Message
     8.6 Server Service Registration Message
 9. References
10. Author's Addresses














Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 2]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

2. Introduction and Terminology

   This document will provide information on Service Location Protocol
   implementation to discover TN3270E servers in a network and session
   balance among those servers.  The implementation follows the
   standards track RFC 2165, Service Location Protocol [1].


2.1 Terminology

   Session Balance - refers to the ability of TN3270E client to use
   server load information to establish a TN3270E connection to the
   TN3270E server with the least load at that time. The purpose is to
   distribute the connection of TN3270E sessions among more than one
   TN3270E server, and one server will not be excessively loaded.
   The term "load balance" is a more general term, with respect to
   server load, and in this document we are trying to focus on the
   TN3270E session connections to least loaded servers.

3. An overview of RFC 2165

   RFC 2165, Service Location Protocol (SLP) [1], provides an automatic
   way for clients to discover services within an administrative
   domain.

   These services have various attributes associated with them from
   which a client can base a service selection. The basic design
   involves the use of three agent types.  These are: User Agents
   (UA's), Service Agents (SA's) and Directory Agents (DA's).

3.1 SLP Agents

   User Agents are used to query Service Agents or Directory Agents.
   They acquire/request service information based upon the desired
   attributes and service needed for the user application.

   Service Agents represent a specific service and advertise service
   information.

   Directory Agents act as a central collection point for service
   registration information by Service Agents which is later requested
   by "user agents" in "intranets".

3.2 Service Agents

   The service registers itself with the service agent so that the SA
   can start advertising this information over the network. The process
   of registration consists of the service giving the SA all relevant

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 3]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   configuration information and attributes. The format of this
   information is called the Service template. The service template for
   TN3270E is shown later, contains the URL which is the address of
   the server with the port, which should be used to connect to it. The
   URL also contains the service type which in this case is TN3270. The
   template also contains all the other attributes of the service like
   scope, load etc.

3.3 User Agents
   The User Agent working on the TN3270E client's behalf retrieves
   service information from the Service Agent(s) or a Directory Agent.
   Based on the gathered information and required attributes the
   TN3270E client or user can decide whether or not to connect with a
   particular server. Based on the service advertisements from various
   TN3270E servers, the client looks at the load attribute and can
   decide to connect to the least loaded server. If by the time it
   connects to that particular TN3270E server, the server becomes
   unavailable it can try connecting to the next server in its list
   (ie: the second least loaded server whose advertisement was
   retrieved by the client/user agent).

4. TN3270E Server Environment and Load

   TN3270E Servers are pervasive in today's networked environment. SLP
   provides emulator clients with a way to discover TN3270E servers in
   the network and session balance among the servers.  The TN3270E
   servers could be distributed across different SNA gateways with
   different connection methods to hosts.  The use of LU pools provides
   an easy way for administrators to provide users access to hosts.
   Administrators can add users to LU pools that have pre-configured
   LU's with specific attributes, like LU types and model types.

   These LU pools would typically have LUs from several different
   gateways assigned, and as members of the LU pool make TN3270E
   session connections, they would be making connections to different
   TN3270E servers, with different load factors, so that session
   balancing could be accomplished. The use of LU pools is not a
   requirement for SLP and session balancing.  A TN3270E client could
   obtain a session by using SLP and session balancing to locate the
   least loaded server in the network.  On a service request a wild
   card "*" could be used when asking for LUPOOL if the emulator
   doesn't care which device types are supported in given pools or if
   it can assume given pools support only certain device types.
   (LUPOOL=xyz\t*)

4.1 TN3270E Server Load

   TN3270E servers providing load information, typically will include

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 4]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   number of sessions available, not in current use,  as part of the
   calculation in determining load for that server. There can be other
   factors that might have an effect on server load.  An example would
   be if a server is not dedicated to only SNA traffic, and is handling
   other processes, like file services and print services, etc.  It is
   beyond the scope of this document to try to standardize the method
   individual server load calculations should be determined. Different
   vendors server's may calculate load information based upon factors
   they consider important, and methods for calculating load may change
   over time.

   If the TN3270E server coexists in a network with other TN server
   implementations using SLP for session balancing, TN3270E server load
   could be adjusted to compensate for differences in load
   calculations.

   One way to allow TN3270E server administrators to compensate for
   differences in implementations of calculating server load
   measurement is to provide the ability to modify the load calculation
   on the TN3270E server.  An element of control can be provided by
   allowing the administrator to modify the load measurement, by using
   an integral number between 0 and 100 (100 being the highest) to
   change the load. This load measurement acts as an additional factor
   on the server's actual load calculation, so that the administrator
   could bias up or down, the likelihood of that server being selected
   by a TN3270E client.

   Load is defined as one of the attributes for the TN3270E server.
   A Load attribute should be provided at the server so clients can
   determine which server to make a connection. If a UA provides only
   a Service Type, in an Attribute Request,  then the reply includes
   all attributes and all values for that Service

   Type, and Load would be included.  Attribute Requests can include a
   select clause, so you could be returned information on just load.
   For more information on Attribute Requests refer to Service Location
   Protocol Internet draft [1].

   An application could issue a  SL_GetService request to locate a
   TN3270E server. Then an application designed to perform least-load
   location of  a TN3270E service, could issue a series of SL_GetAttrs
   calls to obtain the load measurement of each server specified with
   a URL. It would specify a select clause similar to the one
   below to receive only load information.

   URL = service:tn3270://9.37.51.254:23
   Attribute filter = LOAD

   The attribute LOAD would be returned along with its value.  The
   application could then issue other SL_GetAttrs calls for each
   URL.

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 5]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   The application would then select the least loaded server as a
   connection target.  If it tries to connect to a server and that
   connection fails, it could then try to connect to the next
   least-loaded server.

5. TN3270E Client Configuration

5.1 SLP Scope

   Scope is a parameter used to control and manage access by clients to
   servers in a network. It is the same as the Service Location
   Protocol scope defined in RFC 2165 [1]. The control scope provides
   is necessary for two reasons:

   As your network, the number of clients, and the number of servers
   grow, it becomes necessary to partition access to those servers by
   the growing number of clients in order to reduce overall traffic on
   the network. It allows administrators to organize users and servers
   into administrative groups.

   The meaning of the values of scope is defined by the administrator
   of the network. These values can represent any entity. Commonly,
   they fall along either departmental, geographical, or organizational
   lines.

   Each TN3270E server can be assigned to a scope or scopes. TN3270E
   clients using these servers can be configured for a single specific
   scope or be unscoped.  Different scopes can be assigned for
   different services provided on the server if desired.

   SLP Service Agents and Directory Agents (DA) need to reside in the
   network that support the TN3270E server with configured scopes. If
   you plan to allow clients to locate TN3270E server services based on
   scopes, keep in mind how scope relates to the network as a whole. If
   there are unscoped services in a network where scopes are also used,
   then these services are eligible to satisfy any scoped requests,
   which can potentially put a burden on those service agents and
   directory agents that support the unscoped services. For this
   reason, we recommend that every reachable server either have a
   scope, or no server has a scope defined. If directory agents are to
   be used in the site network (for upward scaling), then they should
   be configured to handle the same scopes as is set for the TN3270E
   servers. In addition, if unscoped services are to be used in
   networks with directory agents, at least one unscoped directory
   agent should be set up.

   Attribute information for Service Types pertaining to a specific
   scope can be obtained from Directory Agents (DA).  The DA will not

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 6]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   return a result unless the requested scope matches.

   For more information on SLP scope refer to Service Location Protocol
   Internet draft [1].

5.2 DA-Discovery time-out

   The DA Discovery time-out value, is used to control how long the SLP
   API must wait to discover Directory Agents (DAs) in the network. The
   discovery request is a multicast, and the amount of time required to
   gather all DA responses might vary depending on many factors. If
   there are no DAs in the network, this time-out value can be set to
   zero to indicate that no DA discovery is to be done. The time-out is
   expressed in milliseconds.

5.3 SA Multicast time-out

   The SA Multicast time-out value, is used to control how long the SLP
   API must wait to discover services, attributes, or service types in
   a network without at least one DA that supports the scope of the
   request. In this situation, these requests are multicast and the
   User Agent waits the time-out value to gather the multiple responses
   that are returned. The time-out is expressed in milliseconds.

6. TN3270E Client Implementation Information

6.1 Overview

   A TN3270E client that implements TN3270E SLP session balancing does
   not need to configure an IP Host Address for the TN3270E server it
   desires to connect to. Instead, the IP Host Address of the least
   loaded TN3270E server is discovered by using the SLP session
   balancing described in this document.

   The discovery of the least loaded TN3270E server is done entirely
   outside of and before the TN3270E telnet negotiation. Once the IP
   Host address of the least loaded TN3270E server is discovered, the
   TN3270E client can then start normal TN3270E telnet negotiation.

   The TN3270E client should allow for configuration of the
   following parameters:

   Enable SLP Session Balancing

   This configuration parameter indicates whether or not SLP session
   balancing is enabled. If it is enabled the following three
   configuration parameters must also be configured. If this
   parameter is disabled, SLP session balancing is not supported and

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 7]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   normal TN3270E telnet negotiation is performed.

   Scope Name
   The scope name is a text string that specifies a group of TN3270E
   servers. The scope name can be used to identify groups of TN3270E
   servers in a departmental or geographic setting. For example, if the
   scope name is Building-D, then the SLP session balancing would
   search all TN3270E servers in the Building-D scope to find the least
   loaded TN3270E server.

   If the scope name is blank, then the scope name is not used. This is
   referred to as unscoped. In this case all TN3270E servers, with or
   without scope names, can be used to satisfy the request for least
   loaded TN3270E servers. In order to cut down on network overhead, it
   is recommended that either all servers be scoped or no servers be
   scoped. Refer back to section 5.1 for more discussion of scope.

   DA Discovery Time Out Value

   This value is specified in milliseconds and is fully described
   in section 5.2 of this document.

   SA Multicast Time Out Value

   This value is specified in milliseconds and is fully described
   in section 5.3 of this document.

6.2 How to obtain the list of TN3270E servers supporting SLP

   A TN3270E client that implements SLP session balancing uses API
   calls to obtain the list of TN3270E servers supporting SLP session
   balancing.

   The following minimum API calls, can be used with TN3270E SLP
   session balancing.

   SL_Open
   SL_GetService
   SL_GetAttrs
   SL_FreeResult
   SL_Close

6.3 TN3270E Sample Client Flow

6.3.1 Open the SLP connection

   The TN3270E client must first open a handle with the SLP User
   Agent using the SL_Open API call. The SA multicast time out and

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 8]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   DA discovery time out values are passed as parameters to the SL_OPEN
   API call.

6.3.2 Query the list of TN3270E servers

   The TN3270E client then queries for the list of TN3270E servers
   supporting SLP. This is done by using the SL_GetService API call.

   The request string contains information that determines which type
   of TN3270E servers that this client desires to connect to. The
   request string can contain the scope name, pool name, session type
   and 3270 screen size.

   The string has the following format:

   TN3270/<scope name>/LUPOOL == <pool name><TAB><device type>

   The <scope name> is the name of the scope that is configured
   for the TN3270E client. If the scope is blank or null (unscoped
   request), then the scope is not inserted into the request string.

   The <pool name> is a 1 to 8 character upper case string that
   indicates the name of the pool to which the TN3270E client desires
   to connect. For SLP session balancing, the same pool name must
   be configured on different TN3270E servers.

   The <TAB> is the '/t' tab character which is hexadecimal 0x09.
   the <TAB> is a literal and will be used as a separator.

   The <device type> can be any of the following:

    3270DSC for TN3270E device type IBM-3287-1
    3270002 for TN3270E device types IBM-3278-2 and IBM-3278-2-E
    3270003 for TN3270E device types IBM-3278-3 and IBM-3278-3-E
    3270004 for TN3270E device types IBM-3278-4 and IBM-3278-4-E
    3270005 for TN3270E device types IBM-3278-5 and IBM-3278-5-E
    * for TN3270E device type IBM-DYNAMIC

   Example:

   For a TN3270E client searching for TN3270E servers in the
   ENGINEERING scope for a model 2 screen size and LUPOOL name pool2,
   the following request string would be constructed:

   "TN3270/ENGINEERING/LUPOOL == POOL2<TAB>3270002"

   Note: The " characters before and after the string are not
   part of the request string.

Naugle, Kasthurirangan, Ledford      Expires  November 1998   [Page 9]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

6.3.3 Determine loading of each TN3270E server

   An attribute request for "service:tn3270e" specifying the
   attribute LOAD can be made and you will get back all the available
   loads. Say these are 35,88,78.  You can then issue a service request
   for all tn3270e servers with "LOAD<40" for instance.  Even if the
   load changes between the time you get the attribute reply and when
   you issue the request, you will still get the best the network has
   to offer.

   The TN3270E client then uses the TN3270E server's IP Host address to
   start normal Telnet TN3270E negotiation.

6.4 Recommendations

   It is recommended that the TN3270E client display the IP host
   address that is being used for the TN3270E connection. This gives
   the user knowledge of which TN3270E server the session is connected
   to. For example, the IP host address could be displayed in the
   Windows status bar.

   It is also recommended that the TN3270E client display the resource
   name that is returned by the TN3270E server after connection and
   TN3270E negotiation is completed. This gives the user knowledge of
   which LU resource name in the LUPOOL the session is connected to.
   For example, the resource name could be displayed in the Windows
   status bar, or even in the 3270 OIA line.

   In the event that after the TN3270E client has determined the least
   loaded server and the connection to that server fails for some
   reason, the connection should be closed and an attempt made to
   connect to other TN3270E servers in the list of least loaded
   servers.

   For example, a TN3270E server may reject a connection to a specific
   pool if the pool is full, or if the device type does not match what
   is available in the pool. If this occurs, then an attempt to other
   least loaded TN3270E servers should be performed.

7. Sample Trace Flow of SLP and Session Balancing

   This sample trace flow is provided for informational purposes only.

   SLP: SL_GetService Request: TN3270//LUPOOL == POOL2 3270002/

   SLP: SL_GetService Reply: service:tn3270://206.109.45.139:23

   SLP: SL_GetService Reply: service:tn3270://206.109.45.140:23

Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 10]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   Connecting to 206.109.45.139...

   TerminalType=NVT

   Connection established

   Recv <- DO TN3270E

   Send -> WILL TN3270E

   TerminalType=TN3270E

   Recv <- SEND DEVICE_TYPE

   Send -> DEVICE_TYPE REQUEST IBM-3278-2-E CONNECT POOL2

   Recv <- DEVICE_TYPE IS IBM-3278-2-E CONNECT TN8003

   Send -> FUNCTIONS REQUEST BIND_IMAGE SYSREQ

   Recv <- FUNCTIONS IS BIND_IMAGE SYSREQ

8. Service Templates and Service Registration

   The Service Location Protocol uses the ''service:'' URL scheme name
   to define URLs called ''service: URLs''. These schemes provide a
   way for clients to obtain configuration information that is needed
   to establish a 3270 session through the Telnet server.  The Service
   Location Protocol provides for service: URLs to be registered and
   discovered.

   Service Registration
   These service registrations contain a service: URL, and possible
   attributes associated with that service.  The service registration
   information are shown below for the server.

   Service Templates
   Service templates are documents defining in a formal way the
   attributes associated with that service that a client may want to
   use. For more information on service templates please refer to,
   Service Templates and service:  Schemes. [2]. The server service
   template and TN3270 service templates are shown below.







Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 11]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

8.1 TN3270 Service Template

   ----------------------template begins below this line---------------

   type=tn3270e

   version=0.0

   language=en

   description=
    The tn3270 service provides 3270 gateway access to an SNA network
    via the TN3270 protocol. The attributes reflect the types of 3270
    devices, LU Pools, and load information available on the server.

   url-syntax=
   ; service:tn3270://<ipv4-number>:<port>
   ; <ipv4-number> =define by [draft-ietf-svrloc-service-scheme-10.txt]
   ; <port>        =define by [draft-ietf-svrloc-service-scheme-10.txt]

   load=integer X
   ; This is the load balancing quantity to use in determining the
   ; least loaded TN3270E server to attach to for the service. The
   ;range of valid values is an integral 0 to 100 with 0 indicating the
   ;lowest possible load and 100 the highest

   LU Pool=string X M
   ; This attribute takes on one or more values as defined below.
   ; The <TAB> char. 0x09 is literal and will be used as a separator.
   ;
   ;
   ;   <pool name> = <name> / <name> "<TAB>" <dev type>
   ;   <name>      = 1*ALPHANUM
   ;   <dev type>  = "3270002" / "3270003" / "3270004" / "3270005" /
   ;                 "3270DSC"
   ;
   ; Identifies the LU pool names of LU pools available for use on this
   ; service with the associated device types supported in each pool.
   ; Each value is a record where the first token is the pool name of
   ; the pool and the second token is a device type supported in that
   ; pool. A pool name without a device type indicates that LUs of
   ; unknown type are included in the pool. Records associated with a
   ; given pool name are repeated for each supported device type. A
   ; given pool is included in a registration request if any PU profile
   ; that contributes at least one LU to the pool is active on the
   ; server. The range of valid dev_types are:
   ;
   ; dev_type    Meaning

Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 12]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   ;
   ; 3270002     Lu Type 2 Model 2
   ;
   ; 3270003     Lu Type 2 Model 3
   ;
   ; 3270004     Lu Type 2 Model 4
   ;
   ; 3270005     Lu Type 2 Model 5
   ;
   ; 3270DSC     Printer LU
   ;

   BIND=keyword
   ; The server supports the SNA bind image TN3270e function.

   DATA=keyword
   ; The non-SNA 3270 data stream is supported by server.

   RESPONSES=keyword
   ; The server supports SNA response mode.

   SCS=keyword
   ; The server supports SNA 3270 SCS data stream.

   SYSREQ=keyword
   ; The SYSREQ keyboard key is supported on server.

   RFC1576=keyword
   ; RFC1576 options supported.

   RFC1646=keyword
   ; RFC1646 options supported.

   RFC1647=keyword
   ; RFC1647 options supported.

   security=string M
   ; This is the security technique supported on the server and the
   ; cipher specifications supported by this server.  The defined
   ; values are:
   NONE
   SSLV3

   Ciphersuites=string M
   NULL_NULL,
   NULL_MD5,
   NULL_SHA,
   RC4_MD5_EXPORT,

Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 13]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   RC4_MD5_US,
   RC4_SHA_US,
   RC2_MD5_EXPORT,
   DES_SHA_EXPORT,
   TRIPLE_DES_SHA_US
   ; Additional values will be defined in future templates.

   platform=string X
   ; This is the network operating system platform underlying the
   ; advertising service. The defined values are:
   ;
   ; IW          Server uses IntranetWare or NetWare operating system
   ;
   ; NT          Server uses the Microsoft NT operating system
   ;
   ; OS2         Server uses the OS2 operating system
   ;
   ; AIX         Server uses the AIX operating system
   ;
   IW,NT,OS2,AIX

   protocol=string X
   ;   This is the protocol(s) supported by the server providing this
   ;   service. The defined values are:
   ;
   ; IP          Server supports client connections over IP (TCP/IP or
   ;             UDP/IP)
   ;
   ; IPX         Server supports client connections over IPX (SPX/IPX)
   ;
   IP,IPX

   server name=string
   ; This is the name of the server that was configured during
   ; installation.

   release=string X
   ; This is the version and release level of the server advertising
   ; services. Its format is vv.rr.mm where "vv" is the major version
   ; number, "rr" is the minor version number, and "mm" is the
   ; modification level. All numbers are padded on the left with zeroes
   ; to two characters.
   ; Example: version 3, release 0, mod level 0 is "03.00.00"

---------------------template ends above this line---------------------



Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 14]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

8.2 Server Service Template

  Server Service Template

----------------------template begins below this line------------------

  type=commserver

  version=0.0

  language=en

  description=
   The server service type is registered whenever the communications
   software is loaded on the server. It describes generic attributes of
   the server.  These attributes are also repeated on the other service
   types provided.

  url-syntax=
   ; service:commserver://<ipv4-number>:<port>
   ; <ipv4-number> =def. by [draft-ietf-svrloc-service-scheme-09.txt]
   ; <port>        =def. by [draft-ietf-svrloc-service-scheme-09.txt]

  platform=string X
   ; This is the network operating system platform underlying the
   ; advertising service. The defined values are:
   ;
   ; IW          Server uses IntranetWare or NetWare operating system
   ;
   ; NT          Server uses the Microsoft NT operating system
   ;
   ; OS2         Server uses the OS2 operating system
   ;
   ; AIX         Server uses the AIX operating system
   ;
   IW,NT,OS2,AIX

  protocol=string X
   ;   This is the protocol(s) supported by the server providing this
   ;   service. The defined values are:
   ;
   ; IP          Server supports client connections over IP (TCP/IP or
   ;             UDP/IP)
   ;
   ; IPX         Server supports client connections over IPX (SPX/IPX)
   ;
   IP,IPX


Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 15]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

server name=string
   ; This is the name of the server that was configured during
   ; installation.

  release=string X
   ; This is the version and release level of the commserver
   ; advertising services. Its format is vv.rr.mm where "vv" is the
   ; major version number, "rr" is the minor version number, and "mm"
   ; is the modification level. All numbers are padded on the left with
   ; zeroes to two characters.
   ;
   ; Example: version 3, release 0, mod level 0 is "03.00.00"

---------------------template ends above this line---------------------

8.3 Template Contact Information

   Jim Naugle <jnaugle@us.ibm.com>
   Kasthuri Kasthurirangan <kasthuri@us.ibm.com>

8.4 Security Considerations

   Service type templates provide information that is used to interpret
   information obtained by the Service Location Protocol.  If these
   templates are modified or if false templates are distributed,
   services may not correctly register themselves, or clients might not
   be able to interpret service information.

   The service: URLs themselves specify the service access point and
   protocol for a particular service type.  These service: URLs could
   be distributed and indicate the location of a service other than
   that normally wanted to used. SLP [1] provides an authentication
   mechanism that allows service: URLs of registered services to be
   signed and for the signatures to be verified by clients.

   Service Location Protocol can help clients discover security
   services supported by the TN3270E server.  If security services are
   important or required, using SLP authentication, and protected
   scopes [1] is recommended.

8.5 TN3270 Service Registration Message

   URL: service:tn3270://<addr-spec>:<port-number>
   Attributes:

   [(SCOPE=<string>),]

   (RELEASE=03.00.00),


Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 16]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

   (PLATFORM=IW),

   (PROTOCOL=IP),

   (SERVERNAME=<string>),

   (LOAD=<integer 0 to 100>),

   [(LUPOOL=pool-name0/tANY,

   pool-name1/tdevice_type1,

   pool-name2/tdevice-type2, ...

   pool-namen/tdevice-typen)]

   BIND,

   DATA,

   RESPONSES,

   SCS,

   SYSREQ,

   (SECURITY=NONE),

   RFC1576,

   RFC1646,

   RFC1647

8.6 Server Service Registration Message

   URL:service:commserver://<addr-spec>:<port-number>

   Attributes:
   [(SCOPE=<string>),]

   (RELEASE=03.00.00),

   (PLATFORM=IW),

   (PROTOCOL=IP),

   (SERVERNAME=<string>)

Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 17]


Internet Draft   TN3270E Service Location/Session Balancing  July 1998

9. References

   Request For Comments (RFC) and Internet Draft documents are
   available from <URL:ftp://ftp.internic.net> and numerous mirror
   sites.

   [1]  J. Veizades, E. Guttman, C. Perkins, and S. Kaplan. Service
        Location Protocol. RFC 2165, July 1997.

   [2]  E. Guttman, C. Perkins, J. Kempf. Service Templates and
        service:  Schemes. draft-ietf-svrloc-service-scheme-10.txt
        June 98 (work in progress)

10. Authors' Addresses

   Jim Naugle
   IBM
   P.O. Box 12195
   Research Triangle Park, N.C. 27709-2195
   USA
   Phone:  (919) 254-8789
   EMail:  jnaugle@us.ibm.com

   Kathuri Kasthurirangan
   IBM
   P.O. Box 12195
   Research Triangle Park, N.C. 27709-2195
   USA
   Phone: (919) 254-5721
   Email: kasthuri@us.ibm.com

   Gregg Ledford
   Zephyr Development Corporation
   8 Greenway Plaza Suite 1400
   Houston, Texas 77046
   USA

   Phone: (713) 623-0089
   Email:  gledford@zephyrcorp.com










Naugle, Kasthurirangan, Ledford      Expires  November 1998  [Page 18]