RSS feed
Atom feedFull edition in PDF format
The full IETF Journal, Volume 2, issue 2 (Autumn 2006) is available here for download in PDF format (590KB).
This article was posted on 17 September 2006
Donate Now
IETF JournalTable of Contents - Volume 2, Issue 2 (Autumn 2006)
Full edition in PDF formatThe full IETF Journal, Volume 2, issue 2 (Autumn 2006) is available here for download in PDF format (590KB). This article was posted on 17 September 2006
EditorialBy Mirjam Kühne, Editor, IETF Journal Welcome to the Autumn 2006 edition of the IETF Journal. In this issue we’re pleased to present highlights from last July’s IETF meeting in Montreal. While it is not intended as a full report, we believe it provides a fairly comprehensive overview of developments and outcomes from the meeting. Read more… This article was posted on 18 September 2006
News from the IETF Chair
IETF 66 was held in the Palais des congrès in Montréal, Canada, close to the city’s Chinatown and a short walk from the famous old town. We shared this enormous facility with a conference on pediatric pulmonology, and from its attendees we learned that we could be far more imaginative in our naming of meeting rooms. Their exhibit area, for example, was named Thoracic Park. IETF 66 was hosted by Ericsson Canada which, with the help of Combat Networks and a team of dedicated volunteers, provided excellent wireless networking throughout the week. More than 1,200 people from 44 countries attended. Notably, more than 70 people named China as their country of origin. As always, the week was a busy combination of working group (WG) meetings, BoF (birds-of-a-feather) sessions, research groups, and formal and informal meetings of all kinds on the side. Read more… This article was posted on 18 September 2006
News from the IAB Chair
During the Thursday plenary at the Montreal IETF meeting, I gave an overview of the IAB’s activities since the last IETF meeting. The details, including pointers, can be fount at www3.ietf.org/proceedings/06jul. In this note, I’d like to draw attention to 3 particular areas you might want to keep an eye on and/or participate in. First, as voiced at the IAB’s BoF sessions at the network operator group meetings during the last year (NANOG, APRICOT, RIPE), as well as many other places, there are growing concerns about the evolution of network addressing and routing architectures. Read more… This article was posted on 18 September 2006
IETF66 Plenary – New Administrative Process and New Challenges Discussed at IETF 66By Mirjam Kühne More than 1200 participants from 44 countries convened in Montreal in July for IETF 66. Hosted by Ericsson and held at the Palais des congrès in Montréal, the meeting featured a robust network provided by RISQ and CANARIE. In his welcoming remarks in the first plenary session, IETF Chair Brian Carpenter described the progress made in the past four months since IETF 65. Read more… This article was posted on 19 September 2006
IETF 66 Review: RoutingBy Geoff Huston The IETF uses a broad classification of activity into “Areas”, and within each one working groups (WGs) are chartered. For most of the IETF Areas, in addition to working group meetings, there is a general area meeting that is intended to review work across the entire Area. This is a report of the Routing Area meeting held at IETF66. Read more… This article was posted on 20 September 2006
Recent IESG Document and Protocol ActionsListing of recent IESG Document and Protocol Actions Read more… This article was posted on 20 September 2006
IETF 66 Review: DNSBy Jaap Akkerhuis and Peter Koch For more details about DNS-related working-group meetings, refer to the minutes and Jabber notes for each meeting at www3.ietf.org/proceedings/06jul. DNS Extensions Working Group The DNS Extensions Working Group deals with both the details of the DNS protocol and its extensions, such as the Security Extension (DNSSEC) . The group reports progress on reducing backlog and advancing documents. To date, the Wild Card Clarify draft, which updated the wildcard definition of RFC 1034, achieved RFC status (RFC 4592: The Role of Wildcards in the Domain Name System). According to the authors, the RFC did not change the essence of the protocol; rather, it refined the definition of RFC 1034 to make it more consistent and to reflect reality. Read more… This article was posted on 20 September 2006
IETF 66 Review: WirelessBy James Kempf A new wireless-related working group, 16NG, which is working on IPv6 over 802.16 wireless links, met for the first time during IETF 66. The group previously met twice as a BoF and several times in interim meetings as part of its aggressive agenda to meet the deadlines for WiMax network deployment. A design team is currently working on a document describing how to map the IPv6 subnet onto the 802.16 link. Read more… This article was posted on 20 September 2006
Impressions of Two IETF NewcomersBy Alain Aina and Michuki Mwangi The ultimate achievement for a technical engineer is the opportunity to participate at the highest level of Internet development, perhaps even serve as a co-author of an RFC. To most Internet engineers, the IETF is a revered organisation and involvement is regarded as a career high. We felt that our participation at the IETF meeting in Montreal was both a personal achievement and a motivational experience. It gave life to a process that we had experienced only on mailing lists. Having had the opportunity to be at the meeting, we were able to appreciate the passion and the energy that are put into the IETF for the good of the Internet. Read more… This article was posted on 20 September 2006
News from the IRTFBy Aaron Falk, IRTF Chair, and Mirjam Kühne  Aaron Falk IRTF Chair OFFPATH A BoF session on path-decoupled signalling for data (OFFPATH) was held to discuss creation of a research group (RG) on signalling between end-systems and components in the network, such as firewalls. The purpose of the group is to develop a flexible framework around a simple protocol. Initial work includes a SIP-based implementation from Cornell University. Delay-Tolerant Networking (DTN) RG The DTN RG met in Berkeley, California, in May in addition to conducting a review with the IAB. New work has begun on bundle-in-bundle encapsulation and on defining new bundle headers/blocks. Read more… This article was posted on 20 September 2006
New Tools Enhance Meeting EfficienciesBy Henrik Levkowetz, Chair of the Tools Team, and Mirjam Kühne In an effort to enhance IETF participants’ meeting preparations, the IETF Tools Team has made a few different tools related to the IETF meetings avalable during the first part of this year. The working pages under http://tools.ietf.org/wg now provide HTML versions of all the WG agendas, including links to uploaded slides. This should provide a one-stop-shop for everything associated with an individual WG meeting, and has been made possible by the early access to presentations which the Secretariat’s new materials upload tool provides. In addition, the overall meeting agenda at http://tools.ietf.org/agenda has been enhanced so that IETF meeting attendees are able to view the layout of the meeting venue online and locate WG meeting rooms by clicking on the room number next to the WG meeting time. Read more… This article was posted on 20 September 2006
TCP/IP 25th AnniversaryBy Brian Carpenter, IETF Chair The foundation of the Internet is composed of the basic Internet Protocol (IP) and the generally used Transmission Control Protocol (TCP), which together are known as TCP/IP. TCP/IP was formally standardised in September 1981 – 25 years ago – by the publication of RFC 791 and RFC 793. Read more… This article was posted on 20 September 2006
DNS Security: A Historical PerspectiveBy James M. Galvin DNS security work began to organize as its own activity in 1993. I do not remember when the first conversations took place, but we met for the first time as a sub-group of what was then the DNS working group during the 28th IETF, November 1993, in Houston, Texas. Today’s IETF would call that meeting a BoF, since its principal objectives were to evaluate interest and commitment, and to develop a charter for its own working group. It has been 13 years since those early days and DNS security has undergone many changes since then. Read more… This article was posted on 20 September 2006
An Overview of Multihoming and Open Issues in GSEBy Lixia Zhang Abstract This draft has three objectives:
1. Introduction In its original design IPv4 had a class-based address structure that divided the 2^32 address space into 2^7 large networks (Class-A), 2^14 medium size networks (Class-B), and 2^21 small networks (Class-C)3. GSE stands for Global, Site, and End-system address elements.
Each network is represented by a Network ID, also called a network prefix, with the length of 8 bits, 16 bits, and 24 bits for Class A, B, C networks, respectively. Global routing was performed by matching the high order bits of the packet destination address against a table indexed by network prefixes. Each prefix took one entry in the global routing table and the length of the prefix was implied by the address class. Read more… This article was posted on 20 September 2006
CalendarAutumn 2006 – 67th IETF Spring 2007 – 68th IETF Summer 2007 – 69th IETF Autumn 2007 – 70th IETF This article was posted on 20 September 2006
|
By Brian Carpenter, IETF Chair
By Leslie Daigle, IAB Chair
