You are here

IETF Journal October 2012

   The IETF Journal      IETF Logo

The IETF Journal is an Internet Society publication produced in cooperation with the Internet Engineering Task Force.

Spanish Translation: IETF Journal April 2016 (PDF, 1.8MB)

Russian Translation: IETF Journal April 2016 (PDF, 2.1MB)


Registered attendees: 1174

Newcomers: 195

Number of countries: 52

IETF Activity since IETF 83 (March–July 2012)

New WGs: 6

WGs closed: 4

WG currently chartered: 117

New or revised Internet-Drafts: 1607

IETF Last Calls: 102

Internet-Drafts approved for publication: 106

RFCs published: 140

- 81 Standards Track and 4 BCP

- 41 Informational and 11 Experimental

IANA Activity since IETF 82 (March–July 2012)

Processed 1366 IETF-related requests, including:

Getting new work started in the IETF usually requires a birds-of-a-feather (BoF) meeting to discuss goals for the work, to assess the suitability of the IETF as a venue for pursuing the work, and to identify the level of interest in and support for the work. In this article, we’ll review the BoFs that took place during IETF 84, including their intentions and outcomes. If you’re inspired to arrange a BoF meeting, please be sure to read RFC 5434: Considerations for Having a Successful Birds-of-a-Feather (BoF) Session.

It was a surprise when I learned that the man who was sitting beside me was a very well-known researcher in my field. I’d read lots of his papers—to suddenly find this man sitting beside me was very exciting! — Shabbir Ahmed, IETF 84 Internet Society Fellow

After the success of ISOC’s Pilot Fellowship Programme for Regulators (IETF 83 Paris, France), the Internet Society formally launched the programme in Vancouver at IETF 84 by inviting another five public policy guests to the meeting. In addition to attending IETF Working Group sessions, the Fellows spoke with experts within the IETF community on topics such as IP routing, security, and management of key Internet resources.

During IETF 84 in Vancouver, Canada, two chartered Internet Research Task Force (IRTF) research groups (RGs) held meetings:

In IETF protocol activities in which a data serialization format is not natural to the problem domain, chances are discussion will be raised about using JavaScript Object Notation (JSON). And chances are that discussion will compare JSON with the Extensible Markup Language (XML). Today, in the IETF, where XML was once the preferred text-based data format, JSON is being used more and more.

Internet censorship was the focus of an initiative proposed in Vancouver at an informal bar birds-of-a-feather (BoF) meeting. In this article Johan Pouwelse discusses his motivations for organizing the meeting. An initial draft discussion document is available.1

Demonstrations at the Bits-N-Bites session of the IETF 84 meeting in Vancouver, Canada, featured the framework of a software-defined networking (SDN) solution suitable for the telco environment, as well as new proposals such as an SDN northbound interface for the coexistence of SDN with application-layer traffic optimization (ALTO) and the application of ALTO in an east-west interface interconnecting SDN controllers.

During IETF 84 in Vancouver, Canada, the Internet Protocol for Smart Objects (IPSO) Alliance conducted an interoperability event that primarily focussed on the IPSO Application Framework, but also included testing of 6lowpan, Routing Protocol for Lossy Networks (RPL), and Constrained Application Protocol (CoAP)—all IETF developing standards. This was not the first Interop held in conjunction with the IETF; the Alliance organized a successful test of RPL at IETF 77 in Anaheim, California.

Funding for IETF activities primarily comes from three sources: participant registration fees, corporate sponsorships, and an annual contribution from the Internet Society. The IETF leadership believes that the IETF must diversify its revenue sources in order to preserve the important work of the IETF. The Open Internet Endowment (OIE) is being established as one way to provide funds for the IETF as long as the purpose exists.

Software-defined Networking (SDN) could radically change how networks are designed and operated, according to panelists at the Internet Architecture Board’s Technical Plenary discussion in Vancouver, Canada, which considered whether the IETF should develop protocols to support the emerging network architecture.

The Internet Society is deeply saddened at the passing of Wendy Rickard after an extended battle with cancer.

IETF 84 was a well-attended, successful meeting. Approximately 1,175 people from 52 countries came to Vancouver and actively engaged in developing the future of the Internet. It was exciting to see so many people collaborating.

Google was the meeting host, the hotel facilities were very comfortable, and the social on Tuesday evening was both fun and educational. Hyatt Regency Vancouver, Telus, and Verisign were meeting sponsors, and they assisted Google in ensuring the event was successful. Thanks to all for your support.

The World IPv6 Launch on 6 June 2012 saw leading web sites, Internet service providers (ISPs), and home-router equipment manufacturers turn on IPv6 by default. At IETF 84 the Internet Society (ISOC) brought together content providers, access providers, and Internet measurement experts to discuss the launch, and to share their findings.

Amongst fireworks and nude bicyclists of coincident festivals, the 84th meeting of the IETF took place in downtown Vancouver, Canada, earlier this year. In this issue of the IETF Journal you’ll find a roundup of some of the discussions and people that helped make it such a great meeting.