rfc3049.txt

RFC 的详细文档！

   RC4_MD5_US,
   RC4_SHA_US,
   RC2_MD5_EXPORT,
   DES_SHA_EXPORT,
   TRIPLE_DES_SHA_US

   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 here -------------------------------







Naugle, et al.              Standards Track                    [Page 15]

RFC 3049              TN3270E Location & Balancing          January 2001


7.2 Server Service Type Template

   The 'service:commserver:' template defined below conforms to the
   grammar described in "Service Templates and service: Schemes".
   Please refer to [2] for detailed explanation of the syntax.

   Name of submitters: Jim Naugle <[e-mail]>
                       Gregg Ledford <[e-mail]>
                       K. Kasthurirangan <[e-mail]>
   Language of service template: en
   Security Considerations:
   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.

   Template text:

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

   template-type=commserver

   template-version=1.0

   template-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.

   template-url-syntax=
    # service:commserver://<hostname>:<port>
    # <hostname>
    # <port>

   platform=string X
    # This is the network operating system platform underlying the
    # advertising service.  The defined values are:
    #
    # IW          Server uses Novell 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



Naugle, et al.              Standards Track                    [Page 16]

RFC 3049              TN3270E Location & Balancing          January 2001


   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 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---------------------

7.3 Template Contact Information

   Jim Naugle <[e-mail]>
   Kasthuri Kasthurirangan <[e-mail]>
   Gregg Ledford <[e-mail]>

7.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.





Naugle, et al.              Standards Track                    [Page 17]

RFC 3049              TN3270E Location & Balancing          January 2001


   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.

7.5 Sample TN3270 Service Registration Message

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

   [(SCOPE=<string>),]

   (RELEASE=03.00.00),

   (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,

   RFC2355





Naugle, et al.              Standards Track                    [Page 18]

RFC 3049              TN3270E Location & Balancing          January 2001


7.6 Sample Server Service Registration Message

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

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

   (RELEASE=03.00.00),

   (PLATFORM=IW),

   (PROTOCOL=IP),

   (SERVERNAME=<string>)

8. References

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

   [2]  Guttman, E., Perkins, C. and J. Kempf, "Service Templates and
        service: Schemes", RFC 2609, June 1999.

   [3]  Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC
        2246, January 1999.

   [4]  Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service
        Location Protocol Version 2", RFC 2608, June 1999.

   [5]  Kempf, J. and E. Guttman, "An API for Service Location", RFC
        2614, June 1999.

   [6]  Bradner, S., "Key Words for Use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.


















Naugle, et al.              Standards Track                    [Page 19]

RFC 3049              TN3270E Location & Balancing          January 2001


9. Authors' Addresses

   Jim Naugle
   IBM
   P.O. Box 12195
   Research Triangle Park, N.C. 27709-2195
   USA

   Phone:  [phone]
   EMail:  [e-mail]


   Kasthuri Kasthurirangan
   IBM
   P.O. Box 12195
   Research Triangle Park, N.C. 27709-2195
   USA

   Phone: [phone]
   EMail: [e-mail]


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

   Phone: [phone]
   EMail:  [e-mail]





















Naugle, et al.              Standards Track                    [Page 20]

RFC 3049              TN3270E Location & Balancing          January 2001


10.  Full Copyright Statement

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Naugle, et al.              Standards Track                    [Page 21]