Editor's Note:  These minutes have not been edited.


TN3270E ENHANCEMENTS WG
       MINUTES OF MEETING   4/9/10

SUMMARY:

THE TN3270E ENHANCEMENTS WORKING GROUP CONDUCTED TWO 1-HOUR SESSION ON
WEDNESDAY 4/9/97 AT 345PM & 5PM WITH APPROXIMATELY 20 PEOPLE IN
ATTENDANCE. DERIC VILLANUEVA (CO-CHAIR) LED THE SESSIONS WHILE MINUTES
WERE TAKEN BY ED BAILEY (CO-CHAIR). THE AGENDA INCLUDED ANNOUNCING THE
FORMAL ESTABLISHMENT OF THE WORKING GROUP AND IETF ACCEPTANCE OF THE
CHARTER; ANNOUNCMENT OF THE NEXT TN3270E INTEROPERABILITY EVENT
SCHEDULED FOR MAY 19, 1997; DISCUSSION OF THE DISPOSITION OF LU6.2
OVER TCP/IP; DETAILED REVIEW OF SCOPE, OBJECTIVES, MILESTONES, AND
COMMITMENTS; AND DETAILED DISCUSSION OF DELIVERABLES. THERE WERE NO
OBJECTIONS OR CHANGES RAISED. REFER TO THE FOLLOWING FOR DETAILS.

DETAIL (FIRST HOUR SESSION):

MANY THANKS GOES TO HARALD ALVERSTRAND AND KEITH MOORE (APP AREA
DIRECTORS) AND BOB MOSKOWITZ (ISG) FOR THEIR GUIDANCE AND ASSISTANCE
WITH THE PROPOSED CHARTER AND ESTABLISHING THE TN3270E ENHANCEMENTS
WORKING GROUP. WE HAVE A DEFINITE FOCUS AND SET OF OBJECTIVES AHEAD OF
US. THE CHARTER WAS POSTED TO THE LISTSRV ON 3/12/97.

MICHAEL BOE (CISCO) RECAPED THE FIRST TN3270E INTEROPERABILITY EVENT
LAST 10/97 WITH 7 CLIENT/SERVER VENDORS. THE ISSUES IDENTIFIED AT THE
EVENT ARE ADRESSED IN THE NEXT RFC 1647 DRAFT THAT IS TO BE POSTED FOR
REVIEW IN MAY. CISCO WILL AGAIN HOST THE NEXT INTEROPERABILITY EVENT
THIS SPRING (MAY 19, 1997) TO AFFORD VENDORS ANOTHER CHANCE TO VERIFY
THEIR RFC 1647 IMPLEMENTATIONS AS THE DRAFT MOVES TO PROPOSED STANDARD
THIS SUMMER. A POSTING OF THE EVENT WILL BE MADE ON THE LISTSRV IN THE
NEXT TEN DAYS FOR THOSE WHO WISH TO ATTEND.

THE BOF HELD AT THE LAST IETF MEETING IN SAN JOSE PRODUCED A CANDIDATE
LIST OF ITEMS TO CONSIDER IN THE CHARTER. ONE SUCH ITEM WAS LU6.2 OVER
TCP/IP. THIS ITEM WILL NOT BE A PART OF THIS WORKING GROUP AT THIS TIME.
LEE RAFALOW (IBM) PRESENTED AN OPTION TO THE WG THAT RECOMMENDS AN
INFORMATIONAL RFC BE PRODUCED AS A FIRST STEP. ADDITIONAL WORK COULD BE
CHARTERED FOLLOWING THE INFORMATIONAL RFC BASED UPON INTEREST AND NEED.
THE WG ACCEPTED THE RECOMMENDATION. THE INFORMATIONAL RFC WOULD IDENTIFY
APPROPRIATE SUBSET OF X-OPEN MPTN DOCUMENT. SHOULD THE INFORMATIONAL RFC
BE SUBMITED FOR A STANDARD TRACK, CHANGE CONTROL WOULD HAVE TO BE GIVEN
TO THE IETF, THE WG CHAIRS WILL REVIEW THE DOCUMENT AND DECIDE IF IT
SHOULD BE PLACED ON A STANDARD TRACK.

THE COMMITMENTS MADE BY THE WG MEMBERS FOR EDITING THE NEW DOCUMENTS WAS
RE-CONFIRMED.


DETAIL (SECOND HOUR SESSION):

THE SECOND WG SESSION WAS FOCUSED ON IDENTIFYING THE SET OF ENHANCEMENTS
FOR TN3270E AND TN5250 TO BE ADDRESSED BY THIS WORK GROUP. THE FOLLOWING
IS A LIST OF CANDIDATES SUGGESTED AT THE SESSION. THESE ITEMS WILL BE
DISCUSSED ON THE LISTSRV AND PRIORITIZED.

TN3270E ENHANCEMENTS SUGGESTED ARE:
 SECURITY
 RESPONSE TIME MONITORING
 NETWORK MANAGEMENT
 SERVICE LOCATION
 KEYBOARD RESTORE
 BID/IMPLICIT BID
 FMH
 FIREWALLS
 BIND/UNBIND
 SENSE CODES
 OIA DATA
 SESSION BALANCING
 LENGTH INDICATOR

TN5250 ENHANCEMENTS SUGGESTED ARE ITEMS IN RFC 1647 PLUS:
 PIP DATA
 PRINTING
 ASSOCIATE
 "NAILED" LU
 CONNECT TO DEVICE
 TERMINAL TYPES
 SECURITY

FOR RFC 1647, ADDING A STATEMENT ON SECURITY RISK WAS SUGGESTED BY BOB
MOSKOWITZ (CHRYSLER).

ROGER FAJMAN (NIH) NOTED THAT TN DEVICE TYPE MUST BE REGISTERED IN THE
IANA.

DANIEL MCINTYRE (BOEING) CLARIFIED THE NEED FOR SEQUENCE NUMBERS BETWEEN
THE CLIENT AND SERVER.

IT WAS MENTIONED THAT IF YOU PREFER A DIFFERENT WORDING IN THE DRAFT ON
A TOPIC, THEN PROVIDING ALTERNATIVE WORDING IS APPRECIATED.

BOB MOORE (IBM) PRESENTED INFORMATION ON MEASURING RESPONSE TIME USED BY
PREVIOUS METHODS IN SNA/MS AND NPM. BOB WILL LOOK AT THE NEW RTFM RFC TO
SEE IF THERE IS SOME WAY TO USE IT FOR RESPONSE TIME MEASURING PURPOSES.

BOB MOSKOWITZ (CHRYSLER) HIGHLIGHTED THE SECURITY OPTIONS AS FOLLOWS...
 KERBEROS
 SSL
 SSH
 IPSEC
 SASL
ENCRYPTION IS BROKEN IN KERBEROS, IT IS NOT A CHOICE. SSL IS MOVING TO
TLS - HAS PROBLEMS WITH FIREWALLS. SSH IS NEW BUT ADDRESSES THE ISSUES
MOST LIKE TN. SASL LACKS ENCRYPTION AND HAS NO FOLLOWING AS YET. IPSEC
IS LONG TERM BUT REQUIRES KERNEL CHANGES.THE PRIORITY IS SSH, SSL, IPSEC
RESPECTIVELY.

THERE WAS DISCUSSION ON THE NEXT IETF MEETING IN MUNICH AND IF THERE
WILL BE ANY SESSIONS.  ALSO INTERIM MEETINGS WAS DISCUSSED AS AN OPTION.

THE MEETING WAS ADJOURNED.