INTERNET ENGINEERING STEERING GROUP (IESG) Feubruary 11, 1999 Reported by: Steve Coya, IETF Executive Director ATTENDEES --------- Baker, Fred / Cisco Systems Bradner, Scott / Harvard Carpenter, Brian / IBM (IAB Liaison) Coya, Steve / CNRI Deering, Steve / Cisco (IAB Liaison) Faltstrom, Patrik / Swipnet Marine, April / Raytheon STX Moore, Keith / U of Tennessee Paxson, Vern / Lawrence Berkeley Laboratory Perkins, Charlie / Sun (IAB Liaison) Reynolds, Joyce K. / ISI (IANA Liaison) Schiller, Jeff / MIT Wijnen, Bert / IBM Regrets ------- Alvestrand, Harald / Maxware Burgan, Jeff / @home Coltun, Rob / Fore Systems Leech, Marcus / Nortel Narten, Thomas / IBM Minutes ------- 1. The minutes of the January 28, 1999 Teleconference were approved. Steve to place in public archives. 2. The IESG approved publication of Definitions of Managed Objects for the SONET/SDHInterface Type as a Proposed Standard. Steve to send announcement. 3. The IESG approved publication of A syntax for describing media feature sets as a Proposed Standard. Steve to send announcement. Steve will also send the Protocol Action announcements for the FAX document set approved 28-January-1999. 4. The IESG approved publication of Service Extension for Authentication as a Proposed Standard. Steve to send announcement. 5. The IESG approved publication of MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) as a Proposed Standard. Steve to send announcement. 6. The IESG approved reclassifying OSI Connectionless Transport Services on top of UDP - Version: 1 as Historic. The IESG also approved publication of OSI connectionless transport services on top of UDP Applicability Statement for Historic Status as an Informational RFC. Steve to end announcement. 7. The IESG approved publication of Terminology and Goals for Internet Fax as an Informational RFC. Steve to send announcement. 9. The IESG tentatively approved publication of the following as Experimental RFCs: Internet Printing Protocol/1.0: Encoding and Transport Internet Printing Protocol/1.0: Model and Semantics Design Goals for an Internet Printing Protocol Rationale for the Structure of the Model and Protocol for The Internet Printing Protocol Mapping between LPD and IPP Protocols Keith to convery IESG position to the authors, and will prepare an IESG note to be added. Once the note is received, Steve can send announcement. 10. The IESG agreed with Keith's comments and felt that Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3 should not be published as an Informational RFC. Should the RFC Editor decide to publish this document, an IESG note has been written. Steve to convey to the RFC Editor. 11. Tree Delete Control has been withdrawn by the author as he agreed to bring it to the IETF for possible consideration as as standards track document. Steve to notify RFC Editor. 12. The IESG consensus was that The SecurID(r) SASL Mechanism should not be published as it currently exists. Jeff Schiller will document the IESG's concerns in a message to the author. A revised document is anticipated. 13. The IESG recommends against publication of PNG (Portable Network Graphics) Specification, Version 1.1 as an Informational RFC at this time. Keith to invite the author to bring this to the IETF for possible consideration as as standards track document. 14. Yet another version of IMAP4 Implementation Recommendations is being written. This document will be withdrawn from the IESG's Reading list. Once the "really final I promise" version of the document is submitted, it will be added back to the Reading List. 15. Steve to request extensions from the RFC Editor for all remaining individual submissions not discussed due to a lack of time. 16. The IESG had no problem with the publication of the following indivudual submissions as Experimental Protocols: o The Photuris Session Key Management Protocol o Photuris Schemes and Privacy Protection [EXPERIMENTAL] o ICMP Security Failures Messages Steve to notify RFC Editor. 17. The IESG consensus was that Internet Security Transform Enhancements NOT be published as an Experimental Protocol as this document adds sequence numbers to the old and obsolete AH and ESP transforms. In the case of ESP, it does so in an incompatible way. Publication of these documents could easily confuse implementors of IPSEC. Steve to notify RFC Editor. 18. The IESG recommended against publication of the following two documents: o The ESP Triple DES Transform o IP Authentication using Keyed SHA1 with Data Padding as they add nothing to the documents already published as Proposed Standards from the IPSEC WG. Steve to notify RFC Editor. 19. The IESG consensus was that MTU discovery using TCP MSS and Discussion on MSS value in SYN reply should NOT be published as an RFC. Vern to document the rationale and Steve will convey to the RFC Editor.