Director's Message The 30th meeting of the Internet Engineering Task Force was held in Toronto, Ontario, Canada from 24-29 July 1994. The meeting was hosted by the University of Toronto, and our thanks and appreciation go out to Norman Housley and Frank Pearce, and to all the others that helped with the terminal room and the social event. The Toronto meeting of the Internet Engineering Task Force was not the largest to date, but it did end up in second place overall with just over 700 attendees. One reason for the high rate of attendance was probably due to the anticipation of the opening session in which the IPng Area co-Directors, Allison Mankin and Scott Bradner, presented their recommendations to the IESG for the next version of IP. Though not included in the attendance numbers, there seemed to be an increase in the number of representatives from the press, evidenced by the many one-on-one interviews that were taking place in the hallways of the hotel! The number of first-time attendees rose to an all time high. There were over 204 first-time attendees at the Toronto meeting (approximately 29% of the total attendees). As has become the norm, the Newcomers' Orientation held Sunday afternoon was packed. An encouraging statistic is that of the 260 first-time attendees at the Seattle meeting, over 100 returned to attend the Toronto meeting. It is almost impossible to guess how many people are listening in during the IETF meetings. There were 645 hosts on the receiving end of the Toronto IETF multicast effort, a new all-time high. The number of countries ``listening in'' (in some instances, actually ``participating'') remained at 16. This technology is expanding the number of virtual attendees at these meetings, and it's not limited to the technical presentations and plenaries---some of the working group sessions themselves are broadcast over the Internet. Acknowledgments As many attendees know, the configuration and operation of the terminal room facilities depends a great deal on the generosity of equipment vendors and service providers. Certainly the past IETF meeting hosts are well aware of this dependency! I would like to take this opportunity to recognize the following organizations for their contributions in making the terminal room for the Toronto IETF meeting a reality: Sun Microsystems of Canada Rogers Network Services Cabletron Systems of Canada Ainsworth Electric Network Computing Devices IETF is on the Web In addition to preparing the printed proceedings from the IETF meeting in Seattle, Washington, electronic versions of the proceedings were made available on the WorldWide Web and via Gopher. Since that time, the IETF Secretariat has enhanced their WWW offering adding information on Internet-Drafts, RFCs, working groups, and other general IETF information. If you have not yet seen the IETF ``home page,'' I encourage you to do so. The URL for the Internet Engineering Task Force is: http://www.ietf.cnri.reston.va.us/home.html Future Meetings The next IETF meeting will be in San Jose, California from 5-9 December 1994. This meeting is being hosted by Sun Microsystems. The first IETF meeting of 1995 will be held in Danvers, Massachusetts (a suburb of Boston), and will be co-hosted by FTP Software and NEARNet. Then we go back to Europe! The summer IETF meeting will be held in Stockholm, Sweden from 17-21 July 1995, and will be hosted by NORDUnet. Note that information on future IETF meetings can be 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. Stephen J. Coya Executive Director, IETF IETF Progress Report The IESG and IETF have been very active since the Seattle IETF meeting last April; 156 Internet-Drafts, 28 Protocol Actions, and 57 RFCs were produced. Between the IETF meetings in Seattle, Washington, and Toronto, Ontario, there were seven new working groups created: 1. Network Status Reports (NETSTAT) 2. Integrated Services (INTSERV) 3. Access/Synchronization of the Internet Directories (ASID) 4. Electronic Data Interchange (EDI) 5. Internet White Pages Requirements (WHIP) 6. DNS IXFR, Notification, and Dynamic Update (DNSIND) 7. Mail Extensions (MAILEXT) Seven working groups were concluded: 1. Network Joint Management (NJM) 2. Character MIB (CHARMIB) 3. X.400 Operations (X400OPS) 4. Network OSI Operations (NOOP) 5. Internet Anonymous FTP Archives (IAFA) 6. Uninterruptible Power Supply (UPSMIB) 7. Telnet TN3270 Enhancements (TN3270E) Additionally, 57 RFCs have been published since the Seattle IETF meeting in April, 1994 (26 standards-track; 5 Experimental; 26 Informational): RFC Status Title RFC1605 I SONET to Sonnet Translation RFC1606 I A Historical Perspective On The Usage Of IP Version 9 RFC1607 I A VIEW FROM THE 21ST CENTURY RFC1610 S INTERNET OFFICIAL PROTOCOL STANDARDS RFC1611 PS DNS Server MIB Extensions RFC1612 PS DNS Resolver MIB Extensions RFC1613 I cisco Systems X.25 over TCP (XOT) RFC1614 I Network Access to Multimedia Information RFC1615 I Migrating from X.400(84) to X.400(88) RFC1616 I X.400(1988) for the Academic and Research Community in Europe RFC1617 I Naming and Structuring Guidelines for X.500 Directory Pilots RFC1618 PS PPP over ISDN RFC1619 PS PPP over SONET/SDH RFC1620 I Internet Architecture Extensions for Shared Media RFC1621 I Pip Near-term Architecture RFC1622 I Pip Header Processing RFC1623 S Definitions of Managed Objects for the Ethernet-like Interface Types RFC1624 I Computation of the Internet Checksum via Incremental Update RFC1625 I WAIS over Z39.50-1988 RFC1626 PS Default IP MTU for use over ATM AAL5 RFC1627 I Network 10 Considered Harmful (Some Practices Shouldn't be Codified) RFC1628 PS UPS Management Information Base RFC1629 DS Guidelines for OSI NSAP Allocation in the Internet RFC1630 I Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web RFC1631 I The IP Network Address Translator (Nat) RFC1632 I A Revised Catalog of Available X.500 Implementations RFC1633 I Integrated Services in the Internet Architecture: an Overview. RFC1634 I Novell IPX Over Various WAN Media (IPXWAN) RFC1635 I How to Use Anonymous FTP RFC1636 I Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994 RFC1637 E DNS NSAP Resource Records RFC1638 PS PPP Bridging Control Protocol (BCP) RFC1639 E FTP Operation Over Big Address Records (FOOBAR) RFC1640 I The Process for Organization of Internet Standards Working Group (POISED) RFC1641 E Using Unicode with MIME RFC1642 E UTF-7 - A Mail-Safe Transformation Format of Unicode RFC1643 S Definitions of Managed Objects for the Ethernet-like Interface Types RFC1644 E T/TCP -- TCP Extensions for Transactions Functional Specification RFC1645 I Simple Network Paging Protocol - Version 2 RFC1646 I TN3270 Extensions for LUname and Printer Selection RFC1647 PS TN3270 Enhancements RFC1648 PS Postmaster Convention for X.400 Operations RFC1649 I Operational Requirements for X.400 Management Domains in the GO-MHS Community RFC1651 DS SMTP Service Extensions RFC1652 DS SMTP Service Extension for 8bit-MIMEtransport RFC1653 DS SMTP Service Extension for Message Size Declaration RFC1654 PS A Border Gateway Protocol 4 (BGP-4) RFC1655 PS Application of the Border Gateway Protocol in the Internet RFC1656 I BGP-4 Protocol Document Roadmap and Implementation Experience RFC1657 PS Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 RFC1658 DS Definitions of Managed Objects for Character Stream Devices using SMIv2 RFC1659 DS Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2 RFC1660 DS Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2 RFC1661 S The Point-to-Point Protocol (PPP) RFC1662 S PPP in HDLC-like Framing RFC1663 PS PPP Reliable Transmission RFC1665 PS Definitions of Managed Objects for SNA NAUs using SMIv2