NOTE: This charter is a snapshot of the 39th IETF Meeting in Munich, Bavaria, Germany. It may now be out-of-date.
Chair(s):
Ed Bailey <bart@vnet.raleigh.ibm.com>
Michael Boe <mboe@cisco.com>
Applications Area Director(s):
Keith Moore <moore+iesg@cs.utk.edu>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Applications Area Advisor:
Keith Moore <moore+iesg@cs.utk.edu>
Technical Advisor(s):
Robert Moskowitz <rgm3@chrysler.com>
Mailing Lists:
General Discussion: tn3270e@list.nih.gov
To Subscribe: listserv@list.nih.gov
In Body: sub tn3270e <first_name> <last_name
Archive: listserv@list.nih.gov
Description of Working Group:
Present specifications for access to 3270 and 5250 based applications over TCP/IP require improvement to become more commercially viable. Security, Service Location, Response Time, and Session Balancing are improvement examples.
The WG will drive to update and extend the standards specifications proposed in rfc1647 and rfc1205 so that they fully support 3270 and 5250 style access to host (S/390 and AS/400) applications respectively in today's environments.
Consideration will be given to work already in progress on protocols for accessing 3270 and 5250 based applications over TCP/IP.
Three protocol documents will be produced.
Deliverables
1. A revised version of rfc1647 (tn3270e) including clarifications of the protocol, and security considerations. The revised rfc1647 will be submitted to the IESG for advancement of the tn3270e protocol to draft standard status. Currently it is a proposed standard.
2. A new standards track document defining options for the tn3270e protocol. Such options are: IPDS printing, response time monitoring, error reporting, session balancing, service location, and security.
3. A new standards track document defining enhancements to the tn5250 protocol. This new protocol will be called tn5250e. This is not Display Station Passthrubut printing, LU assignment, service location, and security.
Goals and Milestones:
Apr 97 |
|
Discuss scope of initial tn5250ec enhancements at IETF session. |
Apr 97 |
|
Goal 2 tn3270e new options Propose a list of initial enhancements on listsrv for review. |
Apr 97 |
|
Goal 1 revised tn3270e (rfc1647) Conduct interoperability testing. |
Apr 97 |
|
Discuss scope of initial tn3270e enhancements at IETF session. |
Apr 97 |
|
Propose a list of initial TN5250e enhancements on listsrv for review. |
May 97 |
|
Goal 1 revised tn3270e (rfc1647) Publish Internet-Draft and issue Working Group Last Call. |
Jun 97 |
|
Goal 1 revised tn3270e (rfc1647) Incorporate any revisions and publish Internet-Draft. |
Jun 97 |
|
Goal 1 revised tn3270e (rfc1647) Submit to IESG for consideration for Proposed Standard. |
Aug 97 |
|
Goal 3 tn5250e Resolve issues with initial enhancements using the listsrv. |
Aug 97 |
|
Goal 2 tn3270e new options Resolve issues with initial enhancements using the listsrv. |
Sep 97 |
|
Goal 2 tn3270e new options Issue initial draft of new proposed rfc to listsrv for review. |
Sep 97 |
|
Goal 3 tn5250e Issue initial draft of new proposed rfc to listsrv for review. |
Nov 97 |
|
Goal 3 tn5250e Incorporate comments and publish proposed rfc for implementation. |
Nov 97 |
|
Goal 2 tn3270e new options Incorporate comments and publish proposed rfc for implementation. |
Apr 98 |
|
Goal 2 tn3270e new options Conduct initial interoperability testing. |
Apr 98 |
|
Goal 3 tn5250e Conduct initial interoperability testing. |
Jun 98 |
|
Goal 2 tn3270e new options Gather operational experience from implementers. |
Jun 98 |
|
Goal 3 tn5250e Gather operational experience from implementers. |
Aug 98 |
|
Goal 3 tn5250e Publish Internet-Draft and issue Working Group Last Call. |
Aug 98 |
|
Goal 2 tn3270e new options Publish Internet-Draft and issue Working Group Last Call. |
Oct 98 |
|
Goal 3 tn5250e Submit to IESG for consideration for Proposed Standard. |
Oct 98 |
|
Goal 2 tn3270e new options Submit to IESG for consideration for Proposed Standard. |
Oct 98 |
|
Goal 3 tn5250e Incorporate any revisions and publish Internet-Draft. |
Oct 98 |
|
Goal 2 tn3270e new options Incorporate any revisions and publish Internet-Draft. |
Internet-Drafts:
· TN3270 Enhancements
· Base Definitions of Managed Objects for TN3270E Using SMIv2
· Definitions of Managed Objects for TN3270E Response Time Collection Using SMIv2
Request For Comments:
RFC |
Status |
Title |
RFC1576 |
TN3270 Current Practices | |
RFC1646 |
TN3270 Extensions for LUname and Printer Selection | |
RFC1647 |
PS |
TN3270 Enhancements |
Minutes of the Telnet TN3270E Enhancements (tn3270e) Working Group
Reported by Ed Bailey
I. Summary
The tn3270e Enhancements Working Group conducted two 1-hour sessions on Tuesday 8/12/97 at 3:45 p.m. and 5:00 p.m. with approximately 12 people in attendance. The 3:45pm session opened with a brief discussion of the charter, activity on the listsrv, and use of the IETF web pages. The results of the most recent interoperability testing held in May at Cisco Systems were reviewed along with WG plans for the next interoperability testing. The submission of the tn3270e Internet Draft to the IESG for Draft status was proposed with no objections. Then, discussion proceeded to the activities currently underway on the use of TLS and IPSEC for security for the remainder of the first session. The 5:00pm session was devoted to the review of the Internet drafts for tn3270e management and Response Time MIBs. A number of suggested changes were identified which will be added to the drafts and reposted as updates on the listsrv.
II. Detail (first hour session)
The charter will be updated to reflect the progress of the working group. In particular, the update will address the rewrite of rfc1647 into the tn3270e internet draft, its last call in the working group and submission to the IESG for draft status. Based upon the second inter- operability testing which included 11 organizations and representing an array of client and server implementations, the working group is confident that consistent interpretations are possible with the latest internet draft and is ready for draft status. The WG Chair will work with the Area Directors on the IESG submission.
The next interoperability testing is planned for October, 1997. The exact date and location will be posted on the list in the following weeks after Munich. More emphasis on printing and tn5250 is anticipated.
A number of enhancements are being discussed in the working group (see minutes of Memphis 97). In particular, security, and network management are at the forefront. Demand for tn3270 security is high. SSL3 has no reference spec yet TLS and IPSEC may not be ready soon enough for us. In light of current IETF activities on TLS and IPSEC, the working group will implement security negotiations based upon TLS with the ability to "fall back" to SSL3.0 that should suffice initially. Most new implementation will be on SSL3.1 (TLS). General deployment of SSL3.0 in corporate networks will pressure implementations to use it for tn3270 as well. The wg decided to separate the base telnet security need into a separate document. Michael Boe will be publishing this document. Some of the other comments and observations are as follows. There are existing challenge/response mechanisms in place for most of the tn3270/tn5250 applications. The use of encryption is used to protect passwords from flowing in the clear but is has too high overhead to encrypt all the traffic. More discussion on the list is needed to address the use of encryption and certificates.
III. Detail (second hour session)
Network management of tn3270 sessions requires certain instrumentation in the client and server to allow for setting and getting certain relevant performance and configuration information. The tn3270e base mib and the tn3270e rt mib are intended to specify the minimum instrumentation for managing tn3270e connections. Although fairly complete, review of these two draft documents led to a number of changes to enhance the implementation and understanding of the information. A revision will be made and posted on the list for review in the next 30 days following Munich. Most changes evolved the use of the ipaddr and port numbers for better granularity, additional information in base, and positioning with the application mib. The revised drafts will identify the individual changes. Some additional comments included ipv6 naming, use of timingmarks, and consistency with SNAMS response time management. An informational rfc will be produced to note the rationale for the mib variables and how they can be used.
None Received