INTERNET ENGINEERING STEERING GROUP (IESG) August 12, 1999 Reported by: Steve Coya, IETF Executive Director ATTENDEES --------- Bradner, Scott / Harvard Bush, Randy / Verio Carpenter, Brian / IBM (IAB Liaison) Coltun, Rob / Fore Systems Coya, Steve / CNRI Faltstrom, Patrik / Swipnet Freed, Ned / Innosoft (IAB Liaison) Leech, Marcus / Nortel Marine, April / Internet Engines Moore, Keith / U of Tennessee Narten, Thomas / IBM Paxson, Vern / ACIRI/ICSI Schiller, Jeff / MIT Wijnen, Bert / IBM Regrets ------- Baker, Fred / Cisco Systems Nordmark, Erik / Sun Oran, Dave / Cisco Reynolds, Joyce K. / ISI (IANA Liaison) Minutes ------- 1. The minutes of the July 1, 1999 Teleconference were approved pending Steve's removal of the two RFCED documents that were mistakenly reported as approved. Once done, Steve to place in public archives, and to add the two documents back to the IESG Reading List. 2. The IESG approved publication of the following as Proposed Standards: o Multiprotocol Encapsulation over ATM Adaptation Layer 5 o Virtual Private Networks Identifier 3. The IESG approved publication of the following documents as Proposed Standards: o The Multi-Class Extension to Multi-Link PPP PPP in a real-time oriented HDLC-like framing Integrated Services Mappings for Low Speed Networks The IESG also approved publication of Providing integrated services over low-bitrate links as an Informational RFC. Steve to send announcement. 4. The IESG approved publication of the following documents as Informational RFCs: o A Memorandum of Understanding for an ICANN Protocol Support Organization o A Proposal for an MOU-Based ICANN Protocol Support Organization Steve to send announcement. 5. The IESG approved publication of Protocol-independent content negotiation framework as an Informational RFC. Steve to send announcemment. 6. The IESG approved publication of SPKI Certificate Theory as an Experimental RFC. Steve to send announcemment. 7. The IESG approved publication of SPKI Requirements as an Experimental RFC. Steve to send announcemment. 8. The IESG approved publication of Authentication Mechanisms for ONC RPC as an Informational RFC. Steve to send announcemment. 9. The IESG did NOT approve publication of Web Proxy Auto-Discovery Protocol as an Informational RFC. Keith to convey the reasons to the document authors. 10. Pending a conversation between Rob and the authors, the IESG tentatively approved publication of Requirements for Traffic Engineering Over MPLS as an Informational RFC. Once Rob conveys the outcome of the conversation (either a go-ahead or text for an Note to RFC Editor)to Steve, he will send announcemment. 11. As the MPLS WG review produced no issues, the IESG had no problem with the publication of Performance Issues in VC-Merge Capable ATM LSRs as an Informational RFC. Steve to notify RFC Editor. 12. The Applications ADs decided that the LDAP team needs to review Schema for Representing CORBA Object References in an LDAP Directory and Schema for Representing Java(tm) Objects in an LDAP Directory before a decision on publication is reached. Steve to notify RFC Editor and document authors. 13. The IESG deferred action on ECML v1: Field Names for E-Commerce until Patrik's review for international character set issues. 14. The IESG had no problem with the publication of Media Gateway Control Protocol (MGCP) as an Informational RFC, but requested that the following text be included as an IESG Note: This document is being published for the information of the community. It describes a protocol that is currently being deployed in a number of products. Implementers should keep aware of developments in the IETF Megaco Working Group and ITU-T SG16 who are currently working on a potential successor to this protocol. Steve to notify RFC Editor. 15. The IESG consensus was that Password-Based Cryptography Specification PKCS #5 v2.0 should not be published as an Informational RFC at this time. Marcus to contact author with comments; Steve to notify RFC Editor. 16. The IESG agreed that Comparison of the Addressing Schemes of the Internet and OSI should NOT be published as an Informational RFC. If the RFC Editor decides to publish, the IESG requests the opportunity to prepate an IESG note Steve to notify RFC Editor. 17. The IESG had no problem with the publication of IMAP4 Implementation Recommendations as an Informational RFC. Steve to notify RFC Editor. 18. The IESG had no problem with the publication of The KeyNote Trust- Management System as an Informational RFC. Steve to notify RFC Editor. 19. The IESG discussed the issues of non-standard boilerplate text and/or the inclusion of contradictory statements in Internet-Drafts. The consensus of the IESG was that a clear message needed to be sent by Fred on behalf of the IESG outlining that such documents were subject to immediate expirations. Steve to prepare text (extracted from last week's collection) and send to the IESG for final wordsmithing while waiting in anticipation for Fred to return from the wilds of California. 20. Steve was volunteered to act as the initial PSO Secretary. Steve accepted, but noted that this might prevent him from becoming a member of the ASO. 21. The IESG tentatively approved creating the Zero Configuration Networking (zeroconf) Working Group in the Internet Area. Thomas to incorporate text changes to address concerns raised during the telechat and send them to Steve. Steve is to send a WG Review message to the IETF-Announce and new-work lists. After one week, the WG will be created 22. The IESG approved creating the Secure Network Time Protocol (stime) Working Group in the Security Area. Steve to send announcement. 23. Steve was informed that the "no proplem with publication message" for URLs for Telephone Calls