IETF STEERING GROUP (IESG) REPORT FROM THE IETF MEETING April 29th, 1993 Reported by: Greg Vaudreuil, IESG Secretary This report contains IESG meeting notes, positions and action items. These minutes were compiled by the IETF Secretariat which is supported by the National Science Foundation under Grant No. NCR 8820945. For more information please contact the IESG Secretary. iesg-secretary@cnri.reston.va.us. ATTENDEES --------- Bradner, Scott / Harvard Coya, Steve / CNRI Crocker, Steve / TIS Gross, Philip / ANS Hinden, Robert / SUN Huizer, Erik / SURFnet Knowles, Stev / FTP Software Mankin, Allison / Locus Piscitello, Dave/ Bellcore Rose, Marshall / DBC Vaudreuil, Greg / CNRI IAB Liaison Christian Huitema / INRIA Regrets Chapin, Lyman / BBN Crocker, Dave / SGI Kahle, Brewster / WAIS Reynolds, Joyce / ISI Stockman, Bernhard / SUNET/NORDUnet AGENDA ------ 1. Administrivia o Roll Call o Bash the Agenda o Approval of minutes - April 15th 2. Protocol Actions o X.400 Routing Coordination (experimental) o Distributed Authentication Security Service (Experimental) o RPC & NFS (Historic) o Echo function for ISO 8473 (Draft Standard) o Multiprotocol over X.25 MIB (Proposed Standard) 3. Working Group Actions o Frame Relay Service MIB o Telnet tn3270 Enhancements Working Group o IMAP o Mail and Directory Management (madman) o SNA DLC MIB 4. Tasked Items o RIP A/S o Revised IPLPDN Working Group Charter 5. Management Issues o Alignment of the Working Groups o Compressing TCP/IP Headers o Dynamic Host Configuration o Multiplexing TCP WG/BOF 6. ON HOLD/Waiting o IP Security Charter o Authorization and Access Control Charter o Interdomain Multicast Routing o Virtual Circuit Routing 7. WAITING FOR AD ACTION prior to Last Call o Specification of TNFS Extensions o IP Multicast on Token Ring o Network News Transfer Protocol o The Finger User Information Protocol o Telnet Linemode Option o Transmitting IP Traffic over ARCNET Networks o WAR with RIP o CIDR Applicability Statement 8. RFC Editor Actions o Physical Link Security TOS o Internet Relay Chat o IP Version 7 o Routing Access Protocol MINUTES ------- 1) Administrivia o Approval of the Minutes Approval of the minutes of the April 15th Teleconference was deferred. o Next Meeting The IESG scheduled a meeting for May 13th from 11:30-1:30 ET. 2) Protocol Actions o X.400 Routing Coordination The IESG approved the Internet Draft as an Experimental Protocol. ACTION: Vaudreuil -- Send a document action announcement for the X.400 Routing Coordingation to Experimental to the RFC Editor and IETF mailing list. o Distribute Authentication Security Service There is no objection to the publication of this document as experimental once a new version of the document is posted with clarifying text on the intellectual property claims of DEC. o NFS and RPC A second last call was sent to move these protocols to historic. This action was taken with the belief that the current RFCs (NFS RFC1094 and RPC RFC1057) do not represent the versions of the protocols that are in use. Response from the last call indicates that this was incorrect and the Service Applications Area director has requested another last call suggesting they be moved to Informational. RFC 1050, the original RPC document will be recored as Historic. ACTION: Vaudreuil -- With text from Dave Crocker, send a revised last call for NFS and RPC to Informational status. The NFS and RPC protocols are currently being revised and a new version is expected to be released by an industry consortium. It is not clear if the IETF will be able to secure change control over these specifications. It would be good to get these protocols posted as Informational documents, and maybe form a Working Group to standardize a follow-on proposal. o Echo Function for CLNP (ISO 8473) The IESG approved the Echo function for CLNP for Draft Standard provided the title is changes to reflect that this option is for CLNP. This version of the specification eliminates the short term option in favor of support of the single long-term solution. This effort benefited by a positive reaction with ANSI and ISO. This proposal will be part of the CLNP specification. ACTION: Vaudreuil -- Send a protocol action to the RFC Editor and IETF announcing the elevation of the CLNP Echo Function to Draft Standard. o Multiprotocol Interconnect over X.25 MIB The IESG approved the Multiprotocol Interconnect over X.25 as a Proposed Standard. ACTION: Vaudreuil -- Send a protocol action to the RFC Editor and the IETF announcing approval of the Multiprotocol over X.25 MIB as a Proposed Standard. 3) Working Group Actions o Frame Relay Service MIB The IESG approved the charter of the Frame Relay Service MIB. ACTION: Vaudreuil -- Announce the formation of the Frame Relay Service MIB Working Group to the IETF. o Telnet TN3270 Enhancements Working Group The IESG approved the formation of the tn3270e Working Group. ACTION: Vaudreuil -- Announce the formation of the Telnet TN3270 Working Group. o Interactive Mail Access Protocol (IMAP) The IESG reviewed the IMAP Working Group proposal. It appears that this protocol is targeted as a remote mail store access protocol with extensions to subsume some of the functionality of PCmail. It is not clear to what extent disconnected operation will be supported and whether the effort will support re-synchronization after dis-connected operation. ACTION: Huizer -- Work with the proposed chairman of the IMAP group to refine the charter to better describe the scope of the effort. o Mail and Directory Management (madman) The IESG approved the formation of the Mail and Directory Management Working Group. ACTION: Vaudreuil -- Announce the formation of the Mail and Directory Management Working Group to the IETF. o SNA DLC MIB This proposed Working Group is chartered do define managed objects for SNA networks. The charter needs to be clarified to note that this is not defining MIBs for APPN or APPI. 4) Tasked Items o Routing Information Protocol Applicability Statement No progress to Report o Revised IPLPDN Charter No progress to report 5) Management Issues o IESG Ballots The IESG briefly discussed the meaning of the various ballot options. There was a wide variation in the interpretation of the various action. The options and agreed meanings are: Yes: I have read the protocol and am in favor of the ballot proposition. No Objection: I am familiar with the protocol and agree with the ballot. The Area Director analysis may be adequate background for such a vote. Discuss: I have an objection to the proposal and need to discuss possible changes to the proposal or clarifications. Abstain: I am not familiar with the proposal, am conflicted, or otherwise do not feel I can vote on the proposal. ACTION: Vaudreuil -- Add clarification text to the ballot on the meaning of the various voting options. o Alignment of the Working Groups The IESG has agreed to the current assignment of the Working Groups to Areas. The Internet Area wants the Dynamic Host Configuration Working Group moved once the current set of Client <=> Server Protocol documents are finished. o Compression of TCP/IP Headers Mankin has the list of changes needed in the Header Compression document. The IESG has change control of the documents and agreed that she should make the changes to the ASCII document to correct the bugs. ACTION: Mankin -- Edit the ascii version of the header compression document and post it as an Internet Draft. o Dynamic Host Configuration The final set of documents are expected by the end of this week. o Multiplexing TCP Connections BOF/WG There continues to be interest in multiplexing multiple host-pair telnet streams into a single stream to reduce the number of packets to emulate the performance gains of DEC LAT. The IETF has been presented with a proposal that needs examination. At this time there are several proposals and a Working Group may be pre-mature given the nature of some significant architectural questions. The IESG agreed that the Transport Area Director should convene a BOF at the next meeting to explore the issues and find a framework to pursue this work in this area. ACTION: Mankin -- Explore the architectural issues with multiplexing TCP connections and plan a BOF for the next IETF meeting to discuss these issues. 6) Waiting for AD ACTION o IP Multicast on Token Ring Networks No progress to report 7) Waiting for AD Action prior to the Last Call The following outstanding protocol action requests were briefly reviewed. o Specification of TNFS Extensions This protocol was in the Applications Area. It has been moved to the Service Applications Area and the new AD getting up to speed. o Transmitting IP Traffic over ARCNET Networks The IP over ARCNET specification has exceeded the 2 years in grade. The IESG has little knowledge of current use or implementation. ACTION: Vaudreuil -- Query author for implementation and operational experience with the RFC 1201 IP over ARCnet specification. If there is no response, send a last call for historic. o WAR with RIP The author of the Wide Area Routing with RIP would like this specification to become a Proposed Standard. The IESG discussed the request and agreed that the specification could be published as an Informational or Experimental protocol. Advancement in the standards track will require the formation of a Working Group. ACTION: Hinden -- Notify the author of the Wide Area Routing with RIP document that a Working Group will need to be formed to advance this to Proposed Standard. o CIDR Applicability Statement An update of the CIDR Applicability Statement is expected soon. The document is still pending the submission of BGP-4 into the standard track. 8) RFC Editor Actions The RFC Editor actions have not been assigned to a specific area director in the past. The Secretariat was asked to assign the review to a specific area director when the documents are submitted for review. o Physical Link Security Type of Service The author of this proposal has made changes to this proposal to address concerns and comments raised by the IESG. There was no objection to the publication of this proposal as an Experimental Protocol. ACTION: Vaudreuil -- Notify the RFC Editor that the IESG has no objection to the publication of the Physical Layer TOS document as an experimental protocol. o Internet Relay Chat No IESG objections were raised to the publication of this protocol as Experimental. ACTION: Vaudreuil -- Notify the RFC Editor that the IESG has no objection to the publication of the Internet Relay Chat protocol as an Experimental Protocol. o Ulmann's IP Version 7 o Routing Access Protocol Choice of title for this specification is confusing given the connection of "IP Version 7" in the public mind with the IAB recommendation on the next generation IP work. The IESG is in continuing discussion with Ulmann about the formation of an IETF working group to pursue standardization of these proposals. ACTION: Knowles -- Discuss the naming of Robert Ulmann's proposals with the RFC Editor. ACTION: Vaudreuil -- Notify Postel that the IESG has no objection to the publication of Robert Ulmann's IP routing packet format proposals provided the title is changed to something less confusing. Appendix -- Summary of Action Items -------- ACTION: Vaudreuil -- Send a document action announcement for the X.400 Routing Coordingation to Experimental to the RFC Editor and IETF mailing list. ACTION: Vaudreuil -- With text from Dave Crocker, send a revised last call for NFS and RPC to Informational status. ACTION: Vaudreuil -- Send a protocol action to the RFC Editor and IETF announcing the elevation of the CLNP Echo Function to Draft Standard. ACTION: Vaudreuil -- Send a protocol action to the RFC Editor and the IETF announcing approval of the Multiprotocol over X.25 MIB as a Proposed Standard. ACTION: Vaudreuil -- Announce the formation of the Frame Relay Service MIB Working Group to the IETF. ACTION: Vaudreuil -- Announce the formation of the Telnet TN3270 Working Group. ACTION: Huizer -- Work with the proposed chairman of the IMAP group to refine the charter to better describe the scope of the effort. ACTION: Vaudreuil -- Announce the formation of the Mail and Directory Management Working Group to the IETF. ACTION: Vaudreuil -- Add clarification text to the ballot on the meaning of the various voting options. ACTION: Mankin -- Edit the ascii version of the header compression document and post it as an Internet Draft. ACTION: Mankin -- Explore the architectural issues with multiplexing TCP connections and plan a BOF for the next IETF meeting to discuss these issues. ACTION: Vaudreuil -- Query author for implementation and operational experience with the RFC 1201 IP over ARCnet specification. If there is no response, send a last call for historic. ACTION: Hinden -- Notify the author of the Wide Area Routing with RIP document that a Working Group will need to be formed to advance this to Proposed Standard. ACTION: Vaudreuil -- Notify the RFC Editor that the IESG has no objection to the publication of the Physical Layer TOS document as an experimental protocol. ACTION: Vaudreuil -- Notify the RFC Editor that the IESG has no objection to the publication of the Internet Relay Chat protocol as an Experimental Protocol. ACTION: Knowles -- Discuss the naming of Robert Ulmann's proposals with the RFC Editor. ACTION: Vaudreuil -- Notify Postel that the IESG has no objection to the publication of Robert Ulmann's IP routing packet format proposals provided the title is changed to something less confusing.