Director's Message The 33rd meeting of the IETF, held in Stockholm, Sweden (our second meeting in Europe), turned out to be quite an enjoyable experience. The Hall of Mirrors served as a pleasant gathering place for the attendees during the meeting breaks, and working groups were scheduled into appropriately named venues (e.g., the Weapons Room). Additionally, the Wintergarden Ballroom proved to be an excellent setting for the multicast team to show off what they could do, and the result was impressive. While the number of attendees did not reach the level we have been experiencing in the U.S. and Canada, the Stockholm meeting was well attended by over 600 participants, exceeding our first European meeting by over 100---and that is not counting the members of the press! Just over 50% of the attendees were from the United States, about the same as our previous European meeting in Amsterdam. Not counting the scores of volunteers from KTH, our host group, 12% of the attendees were from Sweden. Acknowledgments Paul Mockapetris, Chair of the IETF, noted that the network connections supporting the terminal room and multicast effort was an excellent example of ``plug and play on a global level.'' This became apparent as the network topology was described during the opening session on Monday. Except for those who have hosted IETF meetings, very few of the attendees understand all that happens in the background in order to provide Internet connectivity. Fortunately for the IETF, the folks from KTH were up to the task, especially Peter Lothberg who was instrumental in making sure the connectivity and bandwidth desired by the attendees was available. Much of the credit for the setup goes to Bernhard Stockman for managing all the technical arrangements and serving as the primary local host contact, and to Mats Erixson and Christian Wettergren for the MBone/multicast effort. There were, of course, many folks who provided exceptional support to the attendees (and the Secretariat) throughout the week, but to list them would double the size of the proceedings. I also want to thank the many volunteers for the time and energy they put into providing Internet connectivity to the IETF meeting attendees. Thanks also to Randy Bush, who stopped off from his world tour to provide technical assistance throughout the week. 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 the following organizations for their contributions and assistance: NORDUnet Network connectivity and financial support UPNET Routers and Hubs Sun Microsystems Workstations and financial support Digital Equipment Printers, the Info-Kiosk, and financial support TELIA Terminal room and network connectivity TELE2/SWIPNET Connectivity to the U.S. KTH Workstations, printers, video equipment, financial support, and personnel A special thanks goes to the City of Stockholm for sponsoring the dinner portion of the social event. A Great Week What was suspected is now confirmed; there is no difference in the level of activity or the variety of spirited discussions at European IETF meetings than those held in North America. There was a great deal of activity during the Stockholm meeting and some intense and often frank conversations were held throughout the week on both old and new topics. The POISED95 effort, following up on the discussions from the Danvers IETF meeting in April, made progress as editors and writers stepped up to the task of volunteering, and a number of specific writing assignments were made with a delivery target of the Dallas IETF in December. The Internet Secure Payments Protocol BOF (ISPP), after first meeting in a medium sized room, had to be moved to one of the larger rooms for its second meeting, and culminated in a last-minute organized plenary presentation Friday morning. Follow-up discussions are still taking place even as I write this, a few weeks after the meeting concluded. Another new topic, the Read the Label BOF (RTL), was moved to the large plenary room to accommodate a strong demand for multicasting to remote participants and in anticipation of a large on-site audience. Future Meetings As we move towards the final meeting of 1995, we are already seeing indications that it might be quite a large IETF meeting, with a number of lively discussions taking place and a number of efforts expected to reach fruition by the end of the week. The meeting will be hosted by MCI in Dallas, Texas during the first week of December (December 4-8, 1995). Following the Dallas meeting, the 1996 meetings will start earlier than normal as the first is scheduled for March 4-8, 1996 in Los Angeles, California. This meeting will be setting a new first as it will be a hostless meeting. Interop will be providing the terminal room and we will be contracting out for multicast support. In another first for the IETF, we will be meeting in conjunction with INET '96 in Montreal, Quebec, Canada during the week of June 24-28, 1996. This is not a joint meeting per se, but both groups will be in the conference center. Additionally, INET will be providing a terminal room to be shared by both IETF and INET meeting attendees. This is only the beginning of a new phase in the organization of IETF meetings. The Secretariat has been exploring the possibilities of hostless meetings for quite some time and, beginning with the Dallas meeting, we are implementing parts of this plan on a step-by-step basis. Of course, there is no real substitute for having a local host, but the need to plan further and further out and to focus on a set number of meeting sites will reinforce this need to move towards local host independence. Of course, the Secretariat will always be open to offers from meeting hosts, and this is by no means an either/or situation. Although ``the times, they are a changing''---and so will the IETF---it is never too late to volunteer to host a meeting! :-) Information on future IETF meetings can always be found in the file 0mtg-sites.txt which is located on 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 Danvers IETF meeting last April; 209 Internet-Drafts, 21 Protocol Actions, and 27 RFCs were produced. Between the IETF meetings in Danvers and Stockholm, there were 14 working groups created: 1. Internet User Glossary (USERGLOS) 2. IEEE 802.3 Hub MIB (HUBMIB) 3. DS1/DS3 MIB (TRUNKMIB) 4. Interfaces MIB (IFMIB) 5. ISDN MIB (ISDNMIB) 6. MIME - X.400 Gateway (MIXER) 7. Routing Policy System (RPS) 8. 100VG-AnyLAN MIB (VGMIB) 9. MessageWay (MSGWAY) 10. Process for Organization of Internet Standards 95 (POISED95) 11. Web Transaction Security (WTS) 12. Detailed Revision/Update of Message Standards (DRUMS) 13. Humanities and Arts (HARTS) 14. One Time Password Authentication (OTP) Eight working groups concluded: 1. Router Requirements (RREQ) 2. TCP/UDP Over CLNP-Addressed Networks (TUBA) 3. Integration of Internet Information Resources (IIIR) 4. Internet Message Access Protocol (IMAP) 5. Common Architecture for Next Generation IP (CATNIP) 6. Electronic Data Interchange (EDI) 7. Internet White Pages Requirements (WHIP) 8. Quality Information Services (QUIS) Additionally, 27 RFCs have been published since the Danvers IETF meeting in April, 1995: RFC Status Title RFC1787 I Routing in a Multi-provider Internet RFC1788 E ICMP Domain Name Messages RFC1789 I INETPhone: Telephone Services and Servers on Internet RFC1790 I An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols RFC1791 E TCP And UDP Over IPX Networks With Fixed Path MTU RFC1792 E TCP/IPX Connection Mib Specification RFC1793 PS Extending OSPF to Support Demand Circuits RFC1794 I DNS Support for Load Balancing RFC1795 I Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1.0 RFC1796 I Not All RFCs are Standards RFC1797 E Class A Subnet Experiment RFC1798 PS Connection-less Lightweight Directory Access Protocol RFC1800 S INTERNET OFFICIAL PROTOCOL STANDARDS RFC1801 E MHS use of the X.500 Directory to support MHS Routing RFC1802 I Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing RFC1803 I Recommendations for an X.500 Production Directory Service RFC1804 E Schema Publishing in X.500 Directory RFC1805 I Location-Independent Data/Software Integrity Protocol RFC1806 E Communicating Presentation Information in Internet Messages: The Content-Disposition Header RFC1807 I A Format for Bibliographic Records RFC1808 PS Relative Uniform Resource Locators RFC1809 I Using the Flow Label Field in IPv6 RFC1810 I Report on MD5 Performance RFC1811 I U.S. Government Internet Domain Names RFC1812 PS Requirements for IP Version 4 Routers RFC1813 I NFS Version 3 Protocol Specification RFC1814 I Unique Addresses are Good