INTERNET ENGINEERING STEERING GROUP (IESG) September 9, 1999 Reported by: Steve Coya, IETF Executive Director ATTENDEES --------- Bradner, Scott / Harvard Bush, Randy / Verio Coltun, Rob / Siara Systems Coya, Steve / IETF Faltstrom, Patrik / Swipnet Freed, Ned / Innosoft (IAB Liaison) Leech, Marcus / Nortel Marine, April / Internet Engines Moore, Keith / U of Tennessee Narten, Thomas / IBM Nordmark, Erik / Sun Oran, Dave / Cisco Paxson, Vern / ACIRI/ICSI Reynolds, Joyce K. / ISI (IANA Liaison) Schiller, Jeff / MIT Wijnen, Bert / IBM Regrets ------- Baker, Fred / Cisco Systems Carpenter, Brian / IBM (IAB Liaison) Minutes ------- 1. The minutes of the August 26 Teleconference were approved. Steve to place in public archives. 2. The IESG approved publication of Addition of Kerberos Cipher Suites to Transport Layer Security (TLS) as a Proposed Standard. Steve to send announcement with the following text as an IESG Note: The 40-bit ciphersuites defined in this memo are included only for the purpose of documenting the fact that those ciphersuite codes have already been assigned. 40-bit ciphersuites were designed to comply with US-centric, and now obsolete, export restrictions. They were never secure, and nowadays are inadequate even for casual applications. Implementation and use of the 40-bit ciphersuites defined in this document, and elsewhere, is strongly discouraged. 3. The IESG tentatively approved publication of Routing Policy System Security as a Proposed Standard, pending input from Fred. If Fred has no objection, Steve to send announcement. Otherwise, Fred will convey his issues with the document to Randy, who will in turn pass it on to the WG. 4. The IESG approved creation of the Zero Configuration Management (zeroconf) Working Group. Steve to send announcment. 5. Steve to send WG review message for Common Name Resolution Protocol (cnrp) Working Group to the IETF Announcement list and the new-work list. After one week, send out WG Action message announcing creation of the WG. 6. Steve to send WG review message for Web Versioning and Configuration Management (deltav) Working Group to the IETF Announcement list and the new-work list. 7. The IESG approved publication of Interoperability Rules for Multicast Routing Protocols as an Informational RFC. Steve to send announcement. 8. The IESG approved publication of PPP EAP TLS Authentication Protocol as an RFC. Thomas to check with WG as to publication status (Experimental vs. Informational). Steve to send announcement once the intended status is determined. 9. The IESG approved publication of Framework Architecture for Signaling Transport as an Informational RFC. Steve to send announcement. 10. The IESG approved publication of PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing as an Experimental RFC. Steve to hold off sending announcement until Scott touches base with the ITU folks to assign SONET/SDH Path Signal Label (PSL) values. 11. The IESG had no problem with the publication of Definition of the inetOrgPerson LDAP Object Class as an Informational RFC. Steve to notify RFC Editor. 12. The IESG had no problem with the publication of Schema for Representing CORBA Object References in an LDAP Directory as an Informational RFC. Steve to notify RFC Editor. 13. The IESG had no problem with the publication of Schema for Representing Java(tm) Objects in an LDAP Directory as an Informational RFC with the following changes: Section 3.4: OLD: This attribute's syntax is 'Binary'. NEW: This attribute's syntax is 'Octet String'. ^^^^^^^^^^^^ OLD: SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 NEW: SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 ^^ Section 10, definition of javaClassName: OLD: SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 NEW: SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE [START of message text] Steve to notify RFC Editor. 14. Vern said he will ask the NSFv4 WG to review Security Negotiation for WebNFS . Steve to notify RFC Editor. 15. The topic of the standard ISOC copyright text and the IPR statement (Please visit the IPR page, IESG makes no claims, etc) was discussed along the lines of whether or not that text should appear in Internet-Drafts, or if the current practice of the RFC Editor adding it was acceptable. Initial consensus was that any Internet-Draft that was being submitted with an intent of being published as a standards track item should contain the two text sections, especially as they are called for in RFC2026. Scott thought that having the text available to authors in a file suitable for copying and appending to their document would be useful in addition to updating the Web page on Internet-Drafts.