INTERNET ENGINEERING STEERING GROUP (IESG) February 8, 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 For more information please contact the IESG Secretary at . ATTENDEES --------- Alvestrand, Harald / Uninett Bradner, Scott / Harvard Carpenter, Brian / CERN (IAB Liaison) Coya, Steve / CNRI Kastenholz, Frank / FTP Software Klensin, John / MCI Kostick, Deirdre / AT&T Bell Labs Mankin, Allison / ISI Mockapetris, Paul / @home O'Dell, Mike / UUNET Schiller, Jeff / MIT Thomson, Susan / Bellcore Regrets ------- Halpern, Joel / Newbridge Networks Reynolds, Joyce / ISI Rekhter, Yakov / cisco (IAB Liaison) Minutes ------- 1. The minutes of the January 18 teleconference were approved. Coya to place in IESG Shadow directory. 2. The IESG approved Architecture of the Whois++ Index Service and How to interact with a Whois++ mesh as Proposed Standards. Coya to send announcement. 3. The IESG decided to return Introducing a Directory Service to the working group, noting that the requested status of BCP was inappropriate. The document was perceived to be long, not specific, and in some instances, not clear. There was also serious concerns that the document referenced specific vendors/implementations, a reference the IESG considered unacceptable. The IESG suggested that it could be resubmitted as an Informational RFC if the WG desires this. Harald was to convey this to the WG. 4. The IESG consensus was to return An IPv6 Provider-Based Unicast Address Format to the working group as there was insufficient support for the existing document. Allison is to convey this to the WG chair, suggesting that email exchanges might be beneficial in arriving at a specification acceptable both to the WG and the IESG. 5. The IESG approved the publication of Variance Request for The PPP Connection Control Protocol and The PPP Encryption Control Protocol as a BCP. Coya to send announcement. 6. The IESG approved the publication of An Appeal to the Internet Community to Return Unused IPNetworks (Prefixes) to the IANA as a BCP RFC. Coya to send announcement. 7. The IESG deferred action on Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) pending an editorial review, specifically to insure consistancy with the new SMI definitions as recently approved by the IESG. 8. The IESG approved the publication of RIPv2 Applicability Statement as an Informational RFC. This approval is to be included in the same message which announces that RIPv1 has been reclassified as Historic. 9. The IESG approved the publication of Building an X.500 Directory Service in the US as an Informational RFC. 10. The IESG approved the publication of Enterprise Renumbering: Experience and Information Solicitation as an Informational RFC. 11. The IESG approved the publication of Source Demand Routing: Packet Format and Forwarding Specification (Version 1) as an Informational RFC. 12. The IESG had no problem with the publication of Chinese Character Encoding for Internet Messages if the changes negotiated between the authors and the Application ADs with the RFC Editor are included. 13. The IESG had no problem with the publication of Scalable Multicast Key Distribution as an Experimental Protocol. 14. The IESG had no problem with the publication of Common DNS Operational and Configuration Errors as an Informational RFC. 15. The IESG had no problem with the publication of An Administrative Infrastructure for SNMPv2 as an Experimental Protocol. 16. The IESG had no problem with the publication of User-based Security Model for SNMPv2 as an Experimental Protocol. 17. The IESG had no problem with the publication of Defending Against Sequence Number Attacks as an Informational RFC. Frank noted that he had provided some input to the author, and this should be mentioned in the note to the RFC Editor. 18. The IESG had no problem with the publication of Classical versus transparent IP proxies as an Informational RFC.