The Director's Message

The 35th meeting of the IETF, held in Los Angeles, California from March 4-8,1996, was the second largest meeting of the IETF in our seven year history with over 1038 registered attendees, four more than the number attending the Dallas IETF. Fortunately, the OMNI Hotel was large enough to accommodate this unexpected attendance level, as was the hotel's staff. Some IETFers even arrived early to take part in the LA Marathon, held the day before the IETF meeting commenced. This is the third time attendance has passed the 1000 mark, and I wonder if this is an indication of things to come.

First timers (308 in LA) continue to make up a third of our attendance at each meeting, and while many attend only one meeting, a significant number continues to attend IETF meetings.


I would like to thank Softbank Expos Interop for providing the terminal room facilities in LA. I would especially like to recognize the efforts of Jim Martin who organized and managed the entire effort. Some may recall that Jim showed up at the Dallas meeting to "observe" an IETF terminal room in action, and ended up providing technical assistance throughout the week. Of course, I thank the other folks from Interop as well as the volunteers from just about everywhere who worked to support the attendees around the clock and 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 many organizations and vendors for their contributions and assistance. Internet connectivity has become increasingly important to the IETF attendees, and Softbank Expos Interop and the other vendors and suppliers fulfilled that need admirably.

New Faces

As this was the first IETF meeting of the year, the terms of some Area Directors and IAB members concluded. The IETF/IAB Nominations Committee, working almost non-stop the prior three months, announced the new slate of IESG and IAB members who assumed their duties during the Thursday IESG Open Plenary session.

The current members of the IESG are:

The current members of the IAB are:

With gratitude and appreciation

I would like to take this opportunity to acknowledge and thank Paul Mockapetris, Sue Thomson, and John Klensin for their service to the IETF community as members of the IESG. Thanks and appreciation also go to Christian Huitema, Steve Crocker, Phill Gross, and Lixia Zhang for their service as members of the IAB.

Poised95's Final Approach

As had become customary, one of the topics discussed during the IESG Open Plenary touched on the Poised95 Working Group. The documents have been discussed and revised, and it appears that the effort in close to completion. In fact, it was announced that final working group review of the documents was to be initiated, and it was believed that these documents would be submitted to the IESG within a few weeks. Now is the time for all good IETFers to view the documents which define our processes.

The Poised95 Working Group has four Internet-Drafts: one documents the IETF Standards Process, one documents the Nominations Committee process, one identifies the various "I" organizations with whom the IETF has a relationship, and a new one documenting the relationship of the IETF to the Internet Society. I encourage everyone to read the Internet-Drafts, especially when the Last Call is issued. These documents will describe what the IETF is, what is does, and how it does it. This is one set of documents that concern all of the IETF.

Future Meetings

At the next IETF gathering, we will be meeting in parallel with INET '96 in Montreal, Quebec, Canada. This meeting will be held 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.

We are returning to San Jose, California from December 9-13, 1996 for our final meeting of the year. This meeting will be hosted by cisco systems.

The 1997 spring meeting will be held in Memphis, Tennessee the week of April 7-11. Our local host is Federal Express. For the summer meeting, scheduled for August instead of July, the IETF will meet in Munich, Germany.

Information on future IETF meetings can be found in the file 0mtg-sites.txt which is located on the IETF Shadow Directories. Alternatively, you can check the IETF Home Page on the WEB. Our URL is:


The IESG and IETF have been quit active since the Dallas IETF Meeting last July: 161 Internet-Drafts, 34 Protocol Actions, and 45 RFCs

Between the IETF meetings in Dallas and Los Angeles, there were three working groups created:

1. Remote Authentication Dial-In User Service (radius)

2. Procedures for Internet/Enterprise Renumbering (pier)

3. Realtime Traffic Flow Measurement (rtfm)

and four working groups concluded:

1. IP Over AppleTalk (appleip)

2. Trusted Network File Systems (tnfs)

3. Privacy-Enhanced Electronic Mail (pem)

4. Whois and Network Information Lookup Service (wnils)

Additionally, 45 RFC's have been published since the Dallas IETF meeting in December, 1995.

RFC Status Title

RFC1865 I EDI Meets the Internet: Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet

RFC1872 E The MIME Multipart/Related Content-type

RFC1873 E Message/External-Body Content-ID Access Type

RFC1874 E SGML Media Types

RFC1875 I UNINETT PCA Policy Statements

RFC1876 E A Means for Expressing Location Information in the Domain Name System

RFC1877 I PPP Internet Protocol Control Protocol Extensions for Name Server Addresses

RFC1878 I Variable Length Subnet Table For IPv4

RFC1879 I Class A Subnet Experiment Results and Recommendations

RFC1881 I IPv6 Address Allocation Management

RFC1882 I The 12-Days of Technology Before Christmas

RFC1883 PS Internet Protocol, Version 6 (IPv6) Specification

RFC1884 PS IP Version 6 Addressing Architecture

RFC1885 PS Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)

RFC1886 PS DNS Extensions to support IP version 6

RFC1887 I An Architecture for IPv6 Unicast Address Allocation

RFC1889 PS RTP: A Transport Protocol for Real-Time Applications

RFC1890 PS RTP Profile for Audio and Video Conferences with Minimal Control

RFC1891 PS SMTP Service Extension for Delivery Status Notifications

RFC1892 PS The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages

RFC1893 PS Enhanced Mail System Status Codes

RFC1894 PS An Extensible Message Format for Delivery Status Notifications

RFC1895 I The Application/CALS-1840 Content-type

RFC1896 I The text/enriched MIME Content-type

RFC1897 E IPv6 Testing Address Allocation

RFC1898 I CyberCash Credit Card Protocol Version 0.8

RFC1900 I Renumbering Needs Work

RFC1901 E Introduction to Community-based SNMPv2

RFC1902 DS Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1903 DS Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1904 DS Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1905 DS Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1906 DS Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1907 DS Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC1908 DS Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework

RFC1909 E An Administrative Infrastructure for SNMPv2

RFC1910 E User-based Security Model for SNMPv2

RFC1911 E Voice Profile for Internet Mail

RFC1912 I DNS Operational and Configuration Errors

RFC1913 PS Architecture of the Whois++ Index Service

RFC1914 PS How to interact with a Whois++ mesh

RFC1915 B Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol

RFC1916 I Enterprise Renumbering: Experience and Information Solicitation

RFC1917 B An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA

RFC1918 B Address Allocation for Private Internets