NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98
Chair(s):
Ed Bailey <elbailey@us.ibm.com>
Michael Boe <mboe@cisco.com>
Applications Area Director(s):
Keith Moore <moore@cs.utk.edu>
Patrik Faltstrom <paf@swip.net>
Applications Area Advisor:
Keith Moore <moore@cs.utk.edu>
Technical Advisor(s):
Robert Moskowitz <rgm@icsa.net>
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:
· Base Definitions of Managed Objects for TN3270E Using SMIv2
· TN3270E Service Location and Session Balancing
Request For Comments:
RFC |
Status |
Title |
RFC1576 |
TN3270 Current Practices | |
RFC1646 |
TN3270 Extensions for LUname and Printer Selection | |
RFC2355 |
DS |
TN3270 Enhancements |
Telnet TN3270 Enhancements WG Session Minutes - reported by Ed Bailey, WG Co-Chair
Summary
The work group has produced a number of Internet Drafts for enhancing tn3270 and tn5250 protocols. Focus of the work group is centered around completing last call for these drafts for submission to IESG. The remaining drafts awaiting completion of last call are TLS Security, and Tn3270e extensions. Currently in last call are tn5350e, MIBs, and Service Location. Experiences were presented for implementations of the new TLS and MIB drafts. The WG responded to the submission by the interested parties of the OHIO specification on how to proceed. Interest remains high to continue interoperability testing in 1999 of implementations of the new drafts.
Details
Agenda
Michael Boe - WG Co-Chair open the session with a review of the published agenda. No modifications were requested.
The topics of the agenda were:
Status of existing drafts (MIBs, Extensions, SLP, TLS)
TN5250E
TLS experience for Telnet
Misc (Ohio, Interoperability)
It was emphasized that the co-chairs were attempting to achieve closure on remaining items within the work group.
Status of existing drafts
MIBS
According to Keith Moore (Apps Area Director), the two internet drafts for MIBs have completed IESG last call. These drafts will be assigned Proposed Standard status and rfc numbers as soon as the director completes the writeup. Implementations by IBM and Cisco were noted for Response Time MIB. Implementation of the Config MIB is now available from IBM. Implementations of the MIBs thus far seem to be the minimal necessary to support service level agreements. Reporting applications are being developed to present data represented by the MIBs. MIB testing will be included in the future interoperability events.
TN3270 Extensions
Gene Pullen reported that three additional extensions have been requested. These were:
1.) an acknowledgment that the client has completed the processing of the Bind/Unbind;
2.) endbrackets be passed thru to the client by the server;
3.) add a code to indicate client inactive (PU Inactive). More discussion on the mailing list is required to understand these requests before they are accepted by the WG as extensions.
Service Location Protocol
This draft is in Work Group last call. No additional comments have been posted on the mailing list. A final request will be issued on the List to solicit approval for submission to IESG. There are server implementations for IBM and Novell. There are client implementations for Zephyr, WRQ, and IBM. The Internet draft conforms to version 2 of the Servloc specification and allows for version 1 compatibility. This draft is intended for locating tn servers. Optionally it can be used to balance multiple requests across multiple servers. However, there are other specifications such as rfc2250bis which can be used to balance requests across multiple servers.
TLS
The last revision was posted in sep 98. Implementations are being developed. The negotiation is intended to be consistent with other implementations such as ACAP and IMAP. Some clarifications were requested about negotiation failure and fall back to SSL V3. Also clarification of use of V3 certs and an example of the cert exchange was requested.
Jeff Altman from Columbia University, discussed his experience in implementing the TLS draft for telnet and kermit. Jeff has used DSS and SSLEAY 9.1.
TN5250E
Armando Fratezi reported that the authors will make the revisions to move the current draft to standards track from informational. A target date of 2/99 is intended for the new draft. TN5250E was noted as a high priority for future interoperability events.
Misc
Ohio
Tom Brawn co-author of the OHIO specification reviewed with the work group, the progress of the OHIO committee and the results of their two day meeting. Their original draft submitted 9/98 as informational defined a open set of objects for accessing host data. Since the submission, a considerable amount of discussion has occurred and a significant commitment by a number of interested parties has been expressed to pursue this specification as a standard.
The Work group and IETF response to the committee was for them to prepare a charter that establishes the goals, deliverable, and milestones for consideration in forming a new IETF work group. A new work group is necessary because the OHIO specification falls outside of the existing tn3270e work group charter. The committee accepted this request and will work with the Apps Area director to develop a charter for a proposed OHIO work group. The Apps area director will work with the IAB and IESG to determine the appropriateness of a OHIO work group and to reach a final decision.
Interoperaility
The work group will be discussing the details of the next interoperabilty event on the mailing list. Currently, the intent is to hold the next event sometime in April 99.
Session Adjourn
None received.