INTERNET ENGINEERING STEERING GROUP (IESG) 8 September 1994 Reported by: John Stewart, 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 at . ATTENDEES --------- Bradner, Scott / Harvard Coya, Steve / CNRI Halpern, Joel / Newbridge Networks Huitema, Christian / INRIA (IAB Liaison) Klensin, John / MCI Knowles, Stev / FTP Software Mockapetris, Paul / ISI O'Dell, Mike / UUNET Reynolds, Joyce / ISI Rekhter, Yakov / IBM (IAB Liaison) Schiller, Jeff / MIT Stewart, John / CNRI Topolcic, Claudio / BBN Regrets ------- Huizer, Erik / SURFnet Mankin, Allison / NRL Rose, Marshall / DBC 1. The minutes of the 25 August IESG meeting were approved. 2. Protocol Actions o RIPv2 The following I-Ds were approved by the IESG for Draft Standard status: - "RIP Version 2 Carrying Additional Information" - "RIP Version 2 MIB Extension" - "RIP Version 2 Protocol Applicability Statement" In addition, the IESG recommends to the RFC Editor that: - "RIP Version 2 Protocol Analysis" be published as an Informational RFC. o IMAP4 The following I-Ds were approved by the IESG for Proposed Standard status: - "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4" - "IMAP4 Authentication mechanisms" In addition, the IESG recommends to the RFC Editor that: - "IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS" - "DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4" be published as an Informational RFCs. o The IESG approved "Post Office Protocol - Version 3" for the status of Draft Standard. o The IESG reclassified "Exterior Gateway Protocol formal specification" to Historic status. 3. RFC Editor Actions o The IESG had no objections to "DNS Encoding of Geographical Location" being published as an Experimental RFC. 4. Working Group Informational Documents o The IESG approved the following documents for publication as Informational RFCs: - "A Vision of an Integrated Internet Information Service" - "Resource Transponders" - "Using the Z39.50 Information Retrieval Protocol in the Internet Environment" 5. Encryption in IP6 The IESG agreed that the IP6 specification should require both privacy and authentication. To be clear, if an implementation is not able to send and receive IP6 datagrams with an encryption | header, then that implementation is not conformant. 6. IPng Candidate Working Groups The IESG agreed to move the CATNIP and TUBA Working Groups to the Internet Area now. The SIPP Working Group will conclude after the creation of the IPng Working-Group-to-be. **** The next IESG teleconference will be 22 September **** at 11:30 EDT.