INTERNET ENGINEERING STEERING GROUP (IESG) October 12, 1995 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 Halpern, Joel / Newbridge Networks Kastenholz, Frank / FTP Software Klensin, John / MCI Kostick, Deirdre / AT&T Bell Labs Mankin, Allison / ISI Mockapetris, Paul / @home O'Dell, Mike / UUNET Reynolds, Joyce / ISI Rekhter, Yakov / cisco (IAB Liaison) Schiller, Jeff / MIT Regrets ------- Thomson, Susan / Bellcore Minutes ------- 1. The minutes from the September 28 teleconference were approved. Coya to place onto Shadow directories. 2. The IESG approved the publication of Guidelines for creation, selection, and registration of an Autonomous System (AS) as a BCP. Coya to send Protocol Action announcement. 3. The IESG approved the publication of "RTP: A Transport Protocol for Real-Time Applications" and "RTP Profile for Audio and Video Conferences with Minimal Control" as Proposed Standards, but the announcement is not to be made until the revised document (profile-06) is available as an Internet-Draft. 4. The IESG directed John to return the finger URL Specification to the authors, conveying the consensus that this specification did not have a constituency and was therefore not a candidate for standards track action. 5. The IESG consensus was that the Mailserver URL Specification was not acceptable. John is to return the specification to the authors. 6. The IESG decided to return the RIP-II Cryptographic Authentication specification to the working group to provide answers to questions raised by IESG members. 7. The IESG deferred action on "Transition Mechanisms for IPv6 Hosts and Routers" to provide more review time by IESG members. 8. The IESG approved the publication of the following Internet-Drafts as Historic RFCs: o IPv6 Security Architecture o Simple Internet Protocol Plus (SIPP) Specification (128-bit address version) o DNS Extensions to support Simple Internet Protocol Plus (SIPP) o The SIPP Interoperability and Transition Mechanism o ICMP and IGMP for the Simple Internet Protocol Plus (SIPP) o Simple Internet Protocol Plus (SIPP): DHCP Options and BOOTP Vendor Extensions o Simple Internet Protocol Plus (SIPP): Addressing Architecture o Simple Internet Protocol Plus (SIPP): Unicast Hierarchical Address Assignment o OSPF for SIPP As part of the Protocol Action announcement, a note to the RFC Editor includes text discussing the historic status that is to be incorporated into each RFC. Coya to send out the Protocol Action announcement. 9. The IESG consensus was that the ietf.org domain would be administered by the Chair of the IETF. Paul took the action to get things set up. 10. The following text was proposed for inclusion in the next version of the Variance Procedure Internet-Draft: Upon the recommendation of the responsible IETF Working Group (or, if no Working Group is constituted, upon the recommendation of the responsible ad hoc committee), the IESG may enter a particular specification into, or advance it within, the standards track even though some of the requirements of section 5 of RFC 1602 have not or will not be met. The IESG may approve such a variance, however, only if it first determines that the likely benefits to the Internet community from entering or advancing the specification on the standards track are likely to outweigh the costs to the Internet community that result from noncompliance with section 5. In exercising this discretion, the IESG shall consider (a) the technical merit of the specification, (b) the possibility of achieving the goals of the Internet standards process without granting a variance, (c) alternatives to the granting of a variance, (d) the collateral and precedential effects of granting a variance, and (e) the IESG's ability to craft a variance that is as narrow as possible. In determining whether to approve a variance, the IESG has discretion to limit the scope of the variance to particular parts of section 5 and to impose such additional restrictions or limitations as it determines appropriate to protect the internet community. If no problems or issues are raised by Monday, October 16, Coya to send formal request to Jon Postel, the document author/editor. 11. Steve briefed the IESG on the very tentative status of the Fall '96 IETF meeting. The probable site will be San Jose where two weeks are available. The IESG consensus was to meet the second week of December (December 9-13, 1996).