INTERNET ENGINEERING STEERING GROUP (IESG) February 12, 1998 Reported by: Steve Coya, IETF Executive Director ATTENDEES --------- Alvestrand, Harald / Maxware Baker, Fred / cisco Bradner, Scott / Harvard Burgan, Jeff / @home Carpenter, Brian / IBM (IAB Liaison) Coya, Steve / CNRI Elz, Robert / U of Melbourne (IAB Liaison) Halpern, Joel / Newbridge Networks Moore, Keith / U of Tennessee Narten, Thomas / IBM O'Dell, Mike / UUNET Reynolds, Joyce / ISI Romanow, Allyn / MCI Schiller, Jeff / MIT Regrets ------- Curran, John / GTE Internetworking Minutes ------- 1. The minutes of the January 29 Teleconference were approved. Steve to place in public archives. 2. The IESG approved publication of Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing as a Proposed Standard. Steve to send announcement. 3. The IESG approved publication of Classless IN-ADDR.ARPA delegation as a BCP. Steve to send announcement. 4. The IESG approved publication of Transmission of IPv6 Packets over Token Ring Networks as a Proposed Standard. However, the announcement will not be sent until other IPV6 documents are approved. Jeff Burgan to provide Steve with a list of "linked" documents. 5. The IESG approved publication of Definitions of System-Level Managed Objects for Applications as a Proposed Standard. Steve to send announcement. 6. The IESG approved publication of Management Information Base for IP Version 6: Textual Conventions and General Group as a Proposed Standard. In the same action, the IESG approved publication on Management Information Base for IP Version 6: ICMPv6 Group as a Proposed Standard. 7. The IESG approved publication of Negative Caching of DNS Queries (DNS NCACHE) as a Proposed Standard. Steve to send announcement. 8. The IESG approved creation of the Content Negotiation (conneg) Working Group in the Applications Area. Steve to send announcement. 9. The IESG approved publication of Using Existing Bibliographic Identifiers as Uniform Resource Names as an Informational RFC. Steve to send announcement. 10. The IESG approved publication of IPv6 Testing Address Allocation as an Experimental RFC, but with a RFC Editor note (text to be provided by Thomas). When received, Steve to send announcement. 11. The IESG approved publication of IPv6 Multicast Address Assignments as an Informational RFC. However, the announcement will not be sent until other IPV6 documents are approved. Jeff Burgan to provide Steve with a list of "linked" documents. 12. The IESG had no problem with the publication of the following: o S/MIME Version 2 Message Specification as an Informational RFC. o S/MIME Version 2 Certificate Handling as an Informational RFC. o The SRP Authentication and Key Exchange System as an Informational RFC. o An Approach for Using LDAP as a Network Information Service as an Experimental RFC. Steve to notify RFC Editor. 13. Action on The SRP Authentication and Key Exchange System was deferred as a new version of the document is now on-line and folks need time to review. 14. With respect to Proposal for the object-oriented, cross- platform filesystem (OFS) , the range of comments were from: "This document is stupid". "This document is pointless". "It is not just pointless, it is stupid". to Tell the RFC editor not to publish, needs review (and considerable fixing) by people who are not part of the IETF. Drop this doc in the nearest sewer... Steve to rephrase :-) 14. The IESG recommends that Proposal for the object-oriented, cross- platform filesystem (OFS) NOT be published as an Informational RFC as it is not a complete, updates are anticipated, and it needs review by folks who are not part of the IETF. Steve to convey to RFC Editor. 15. The FAX document set was deferred again as updates (and updates to updates) are still arriving at Internet-Drafts. Steve to send note to Dave Crocker and Claudio Allocchio to ascertain if the current set (just submitted by Claudio) are the documents to be considered in the package (or if additional updates are anticipated). 16. There was a brief discussion on the IESG's policy pertaining to interoperability testing at IETF Meetings (policy does not prohibit, but discourages). Steve gave a brief (HA) history of the policy, focusing on the issues and concerns that were originally raised. Consensus was that all requests needed to go through the AD, and requires coordination with the Secretariat prior to approval. If accommodations can be easily provided by the Secretariat, they will be. However, this is not an IETF event, and the organizer may be required to make own arrangements and be responsible for all costs). Next teleconference will be February 26, 1998