INTERNET ENGINEERING STEERING GROUP (IESG) August 28, 1997 Reported by: Steve Coya, IETF Executive Director This report contains IESG meeting notes, positions and action items. These minutes were compiled by the IETF Secretariat which is supported in part by the National Science Foundation under Grant No. NCR-9528103 ATTENDEES --------- Alvestrand, Harald / Uninett Baker, Fred / cisco Bradner, Scott / Harvard Carpenter, Brian / IBM (IAB Liaison) Coya, Steve / CNRI Curran, John / BBN Planet Elz, Robert / U of Melbourne (IAB Liaison) Moore, Keith / U of Tennessee Narten, Thomas / IBM O'Dell, Mike / UUNET Reynolds, Joyce / ISI Romanow, Allyn / Sun Schiller, Jeff / MIT Regrets ------- Burgan, Jeff / @home Halpern, Joel / Newbridge Networks Minutes ------- 1. The minutes of the July 24 Teleconference were approved. Steve to place in public archives. 2. The IESG has approved SMTP Service Extension for Command Pipelining as a Draft Standard. This document will update RFC1854, currently a Proposed tandard. 3. The IESG came "close" to approving the following documents: o The Use of RSVP with IETF Integrated Services o Specification of the Controlled-Load Network Element Service o Specification of Guaranteed Quality of Service o Integrated Services Management Information Base o Integrated Services Management Information Base Guaranteed Service Extensions o General Characterization Parameters for Integrated Service Network Elements o Network Element Service Specification Template But there were not enough participants to complete. Steve to probe the remaining IESG members for their input. If consensus is reached, Steve will send the announcement and not wait for another meeting. 4. Scott Bradner was selected to serve as the IESG Liaison to the NOMCOMM. 5. The topic of a WG being established to work on S/MIME was discussed. They had been given a deadline (conveyed two months before) in which to submit a proposed charter, though no charter was received. The main concern was that this effort was based on encumbered technology, but there had been "statements" conveyed along the lines of ceeding change control to the IETF. Jeff will compose a note stating that before the IESG even considers such a WG, they would need to execute an agreement similar to the one received from SUN (RFC1790). Jeff was also to note that such an agreement was a pre- requisite, not a guarantee that a WG would be created. 6. The IESG had no problem with the publication of AT&T/Neda's Efficient Short Remote Operations (ESRO)Protocol Specification Version 1.2 as an Informational RFC, but wanted the following IESG Note: "This protocol has not had the benefit of IETF Working Group review, but a cursory examination reveals several issues which may be significant issues for scalability. A site considering deployment should conduct a careful analysis to ensure they understand the potential impacts." 7. Harald is in communication with the author of A Dictionary Server Protocol and a new draft is expected. Steve to convey to the RFC Editors. 8. The IESG (as well as the IAB liaison) felt that Guidelines for Writing RFC Text on Security Considerations was not ready for publication as an Informational RFC. This document is part of the report of the IAB secureity retreat Fini