INTERNET ENGINEERING STEERING GROUP (IESG) September 5, 1996 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 by the National Science Foundation under Grant No. NCR-9528103 ATTENDEES --------- Alvestrand, Harald / Uninett Baker, Fred / cisco Bradner, Scott / Harvard Burgan, Jeff / Baynetworks Coya, Steve / CNRI Elz, Robert / U of Melbourne (IAB Liaison) Kastenholz, Frank / FTP Software Kostick, Deirdre / AT&T Bell Labs Mankin, Allison / Information Sciences Institute Moore, Keith / U of Tennessee O'Dell, Mike / UUNET Reynolds, Joyce / ISI Schiller, Jeff / MIT Regrets ------- Carpenter, Brian / CERN (IAB Liaison) Halpern, Joel / Newbridge Networks Romanow, Allyn / Sun Minutes: ------- 1. The IESG approved the minutes of the August 22 telechat. Steve to place in shadow directories. 2. The IESG approved publication of Internationalization of the HTML as a Proposed Standard. Steve to send announcement. 3. The IESG approved publication of RIPng for IPv6 as a Proposed Standard. Steve to send announcement. The IESG also approved publication of RIPng Protocol Applicability Statement as an Informational RFC. 4. The IESG approved publication of RIP-II Cryptographic Authentication as a Proposed Standard. Steve to send announcement. 5. The IESG approved publication of Generic Security Service Application Program Interface Version 2 as a Proposed Standard. Steve to send announcement. 6. The IESG approved publication of Requirements for Web Transaction Security as an Informational RFC, but ask that the title be changed to Considerations for Web Transaction Security. Steve to send announcement. 7. The IESG approved publication of Common Internet Message Headers as an Informational RFC. The IESG also requests that the IANA consider storing the HTML document (referenced via a URL) at the IANA. Steve to send announcement. 8. The IESG approved publication of How new BGP Attribute Types are defined as an Informational RFC. Steve to send announcement. 9. The IESG consensus on Political Disclosure Transmission Protocol (DISCLOSE) was that it was inappropriate for publication as an RFC and recommend it not be published. 10. The IESG had no problem with the publication of Applicability of Standards Track MIBs to Management of World Wide Web Servers as an Informational RFC. 11. The IESG deferred action on Mechanism for Self-Labeling of Content so that discussions with the author can continue. 12. The IESG had no problem with the publication of Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI as an Informational RFC. 13. The IESG had no problem with the publication of Group Key Management Protocol (GKMP) Specification or Group Key Management Protocol (GKMP) Architecture as Experimental Protocols. 14. The IESG had no problem with the publication ofThe RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms as an Informational RFC. 15. The IESG did not feel that Creation of and Registration in the ".NUM" Top Level Domain should be published until after the process for determining new TLDs is defined. 16. The IESG deferred action on the two WebNFS documents to provide more time for discussions with the author. It was noted that the IESG may consider issuing a Last Call on these documents to provide for more community review. This decision will not be made until after the discussions with the author take place. 17. The IESG recommends against publishing The PORT Resource Record as an Experimental Protocol. The subject matter duplicates work already done or currently underway in the IETF. 18. The IESG had no problem with the publication of Mobile Network Tracing as an Informational RFC. 19. Steve reported that things were closer WRT the Australian meeting. The tentative date is December 6-11, 1998. It was suggested that Spring would be better (dryer) than the fall. Steve to contact Simon and Mark in Adelaide to ascertatin the feasibility of a Spring 1999 meeting. 20. Steve will be sending out a Status Check message on all the age-old DISCUSS/PENDING actions.