Director's Message The 32nd meeting of the IETF was held in Danvers, Massachusetts from 3-7 April, 1995. The number of attendees was not as high as the last meeting, but close. There were 893 registered attendees, down 17% from the record set in San Jose, but still the second largest IETF meeting in its seven year history. However, it does appear that the price of orange juice exceeded the previous record! Of the 448 first-time attendees at the San Jose meeting, 152 (34%) returned for their second meeting, joining with 283 folks who were attending their first IETF meeting. Acknowledgments I would like to thank FTP Software and NEARNET for hosting this meeting of the IETF, and for providing the terminal room facilities, manning the AVT multicast, and setting up a social event that will be remembered for quite some time. I would especially like to recognize the efforts of Stev Knowles and John Curran, and their teams (who did most of the work :-) who worked around the clock to support the attendees. Oh, and a special thanks to Scott Bradner for loaning us his printer! The configuration of the terminal room facilities depends a great deal on the generosity of equipment vendors and service providers, and I want to thank them all for the time, equipment, and energy they put into providing Internet connectivity to the IETF meeting attendees. As this was the first IETF meeting of the year, the terms of some Area Directors and IAB members concluded. Since this section is for acknowledging contributions to the IETF, I would like to take this opportunity to recognize Erik Huizer, Stev Knowles, Marshall Rose, and Claudio Topolcic and thank them, on behalf of the IETF, for the time, effort, and energy they contributed to the community as members of the IESG. I would also like to thank Jun Murai, John Romkey, Dave Sincoskie, and Mike St. Johns for serving as members of the IAB. POISED Effort Revived A number of efforts were underway in 1992 to describe and document the procedures and practices of the IETF. During the San Diego IETF (March, 1992), the IAB and IESG were working on the details that would eventually be documented as the Internet Standards Process and published as RFC 1310. The document was revised and published again as RFC 1602 following a Last Call in March of 1994. At the Washington DC meeting (November, 1992) the POISED effort redefined the roles and responsibilities of the IAB and IESG, and implemented a new procedure where IAB and IESG members are now selected by a nominating committee of volunteers from the IETF to serve two year terms. Since that time, the IETF has gained experience operating under the ``New World Order'' and, in the process, items have been identified which require clarification, some which need enhancements, and others which require change. Following a period of dormancy, there were three POISED95 sessions held during the week, each focusing on a specific topic. The first session was for general purposes, primarily to identify subjects which need to be addressed. The second session focused on the Nominating Committee process, which touched on the powers of the committee chair, possible restrictions on who may serve as members of the committee, and general procedures and practices. The third POISED95 session was devoted to Intellectual Property Rights (IPR), focusing on the perceived problems with Section 5 of RFC 1602. Over the past few years, the subject of Intellectual Property Rights, particularly copyrights and patents, licensing, and a concern over liability, has received a considerable amount of attention and discussion. I encourage everyone to review the notes from the POISED95 BOF, and be prepared to participate once the working group(s) are created. Future Meetings The next IETF meeting will be in Stockholm, Sweden on 17-21 July, 1995 (our second time in Europe). MCI will host the final meeting of 1995 in Dallas, Texas on 4-8 December, 1995. Note that information on future IETF meetings can always be found in the file 0mtg-sites.txt which is located in the IETF Shadow Directories. Or, you can check the IETF Home Page on the Web. Our URL is: http://www.ietf.cnri.reston.va.us/home.html Stephen J. Coya Executive Director, IETF IETF Progress Report The IESG and IETF have been very active since the San Jose IETF meeting last December; over 193 Internet-Drafts, 30 Protocol Actions, and 64 RFCs were produced. Between the IETF meetings in San Jose, California and Danvers, Massachusetts, there were nine working groups created: 1. AToM MIB (ATOMMIB) 2. Guidelines and Recommendations for Security Incident Processing (GRIP) 3. New Generation Transition (NGTRANS) 4. HyperText Transfer Protocol (HTTP) 5. Data Link Switching MIB (DLSWMIB) 6. MIME Content-Type for SGML Documents (MIMESGML) 7. RWhois Operational Development (RWHOIS) 8. IPv6 MIB (IPV6MIB) 9. Routing Information Protocol (RIP) and ten working groups were concluded: 1. Inter-Domain Policy Routing (IDPR) 2. Commercial Internet Protocol Security Option (CIPSO) 3. RIP Version II (RIPV2) 4. MHS-DS (MHSDS) 5. Network Access Server Requirements (NASREQ) 6. Authorization and Access Control (AAC) 7. Interfaces MIB (IFMIB) 8. Address Lifetime Expectations (ALE) 9. Printer MIB (PRINTMIB) 10. TFTP Extensions (TFTPEXTS) Additionally, 64 RFCs have been published since the San Jose IETF meeting in December, 1994: RFC Status Title RFC 1440 E SIFT/UFT: Sender-Initiated/Unsolicited File Transfer RFC 1709 I K-12 Internetworking Guidelines RFC 1714 I Referral Whois Protocol (RWhois) RFC 1719 I A Direction for IPng RFC 1726 I Technical Criteria for Choosing IP:The Next Generation (IPng) RFC 1727 I A Vision of an Integrated Internet Information Service RFC 1728 I Resource Transponders RFC 1729 I Using the Z39.50 Information Retrieval Protocol in the Internet Environment RFC 1730 PS INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4 RFC 1731 PS IMAP4 Authentication mechanisms RFC 1732 I IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS RFC 1733 I DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4 RFC 1734 PS POP3 AUTHentication command RFC 1735 E NBMA Address Resolution Protocol (NARP) RFC 1736 I Functional Requirements for Internet Resource Locators RFC 1737 I Functional Requirements for Uniform Resource Names RFC 1738 PS Uniform Resource Locators (URL) RFC 1739 I A Primer On Internet and TCP/IP Tools RFC 1740 PS MIME Encapsulation of Macintosh files - MacMIME RFC 1741 I MIME Content Type for BinHex Encoded Files RFC 1742 PS AppleTalk Management Information Base II RFC 1743 DS IEEE 802.5 MIB using SMIv2 RFC 1744 I Observations on the Management of the Internet Address Space RFC 1745 PS BGP4/IDRP for IP---OSPF Interaction RFC 1746 I Ways to Define User Expectations RFC 1747 PS Definitions of Managed Objects for SNA Data Link Control: SDLC RFC 1748 DS IEEE 802.5 MIB using SMIv2 RFC 1749 PS IEEE 802.5 Station Source Routing MIB using SMIv2 RFC 1750 I Randomness Recommendations for Security RFC 1751 I A Convention for Human-Readable 128-bit Keys RFC 1752 PS The Recommendation for the IP Next Generation Protocol RFC 1753 I IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture RFC 1754 I IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1 RFC 1755 PS ATM Signaling Support for IP over ATM RFC 1756 E REMOTE WRITE PROTOCOL - VERSION 1.0 RFC 1757 DS Remote Network Monitoring Management Information Base RFC 1758 I NADF Standing Documents: A Brief Overview RFC 1759 PS Printer MIB RFC 1760 I The S/KEY One-Time Password System RFC 1761 I Snoop Version 2 Packet Capture File Format RFC 1762 DS The PPP DECnet Phase IV Control Protocol (DNCP) RFC 1763 PS The PPP Banyan Vines Control Protocol (BVCP) RFC 1764 PS The PPP XNS IDP Control Protocol (XNSCP) RFC 1765 E OSPF Database Overflow RFC 1766 PS Tags for the Identification of Languages RFC 1767 PS MIME Encapsulation of EDI Objects RFC 1768 E Host Group Extensions for CLNP Multicasting RFC 1769 I Simple Network Time Protocol (SNTP) RFC 1770 I IPv4 Option for Sender Directed Multi-Destination Delivery RFC 1771 DS A Border Gateway Protocol 4 (BGP-4) RFC 1772 DS Application of the Border Gateway Protocol in the Internet RFC 1773 I Experience with the BGP-4 protocol RFC 1774 I BGP-4 Protocol Analysis RFC 1775 I To Be ``On'' the Internet RFC 1776 I The Address is the Message RFC 1777 DS Lightweight Directory Access Protocol RFC 1778 DS The String Representation of Standard Attribute Syntaxes RFC 1779 DS A String Representation of Distinguished Names RFC 1780 S INTERNET OFFICIAL PROTOCOL STANDARDS RFC 1781 PS Using the OSI Directory to Achieve User Friendly Naming RFC 1782 PS TFTP Option Extension RFC 1783 PS TFTP Blocksize Option RFC 1784 PS TFTP Timeout Interval and Transfer Size Options RFC 1785 I TFTP Option Negotiation Analysis RFC 1786 I Representation of IP Routing Policies in a Routing Registry (RIPE-81++)