INTERNET ENGINEERING STEERING GROUP (IESG) April 18, 2002 Reported by: Steve Coya, IETF Executive Director ATTENDEES --------- Alvestrand, Harald / Cisco Austein, Rob / IAB Liaison Bellovin, Steve / AT&T Labs Bradner, Scott / Harvard Coya, Steve / IETF Daigle, Leslie / Verisign (IAB) Faltstrom, Patrik / Cisco Fenner, Bill / AT&T Freed, Ned / Innosoft Hargest, Jacqueline / IETF Narten, Thomas / IBM Nordmark, Erik / Sun Reynolds, Joyce K. / ISI (RFC Editor) Cotton, Michelle / ICANN Schiller, Jeff / MIT Wijnen, Bert / Lucent Zinin, Alex / Nexsi Systems Regrets ------- Bush, Randy / AT&T Mankin, Allison / ISI Minutes ------- 1. The minutes of the April 4 Teleconference were approved, noting Thomas' comments are to be addressed first. Steve to place in public archives. 2. Subsequent to the April 4 teleconference, DHCP Option for SIP Servers' was approved as a Proposed Standard. The announcement was posted. 3. The IESG approved publication of Transient Prefix for Identifying Profiles under Development by the Working Groups of the IETF as a BCP. Steve to send announcement. 4. The IESG approved publication of Layer Two Tunneling Protocol 'L2TP' Management Information Base as a Proposed Standard. Steve to send announcement. 5. The IESG approved publication of IMAP4 Child Mailbox Extension as an Informational RFC. Steve to send announcement. 6. The IESG approved publication of Voice Messaging Client Behaviour as an Informational RFC. Steve to send announcement. 7. The IESG tentatively approved creation of the Operation of the IESG/IAB Nominating and Recall Committees (nomcom) Working Group. Scott to provide text for a "definition" milestone. Once provided and approved by Harald, Steve to add to charter and then send announcement. 8. The IESG approved the recharter of the Network File System Version 4 (nfsv4) Working Group. Steve to update WG record. 9. The IESG approved the recharter of the Public-Key Infrastructure (pkix) Working Group with the addition of the following text: Other deliverables may be agreed upon as extensions are proposed. New deliverables must be approved by the Security Area Directors before inclusion on the charter or IETF meeting agendas. 10. The IESG tentatively approved SIP-H.323 Interworking Requirements for publication as an Informational RFC, but wanted an explicit OK from Allison (who was unable to participate in the teleconference). Once received, Steve to announce. 11. Action on Differentiated Services Quality of Service Policy Information Base and Framework Policy Information Base was deferred as new versions of both documents are anticipated. As there was no IESG consensus for these documents being on the standard track, the IESG decided they would approve as Informational documents once the required IESG/PIB-doctor-review revisions are accepted by Scott and Bert. If acceptable, Scott and Bert to provide "clean" version of text for Document Action announcement. When announced, Steve to request Fast-Track RFC Number assignment 12. The following items were deferred: o Signalling Connection Control Part User Adaptation Layer (SUA) (Proposed) Note: Issues raised requiring discussion o Internet Printing Protocol (IPP): Printer Installation Extension (Proposed) Note: Issues raised requiring discussion o Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration (BCP) Note: Issues raised requiring discussion. May go through another Last Call o Reserved TLV Codepoints in ISIS (Informational) Note: Held over o Optional Checksums in ISIS (Informational) Note: OK, but held over along with draft-ietf-isis-wg-tlv-codepoints o Framework for IP Multicast in MPLS (Informational) Note: Being returned to WG New Action Items: o Allison to review draft-agrawal-sip-h323-interworking-reqs and send decision to IESG. If OK, Steve to announce. o Scott to provide milestone text for nomcom; Harald to approve,, Steve to announce. o Scott to create list of documents for IAB chair pertaining to Sigtran o Steve to explain to Ned how/why the REGBIS item consists of only one document => DONE o Harald to draft text explaining difference between Informational and Experimental status. o Scott and Bert to provide "clean" version of text for the "PIB" documents, which Steve will use in Document Action announcement. When announced, Steve to request Fast-Track RFC Number assignment