San Francisco, USA--March 31, 2009--The Internet Engineering Task Force (IETF), the Internet's premier technical standards body, last week gathered more than 1150 Internet thought leaders at its meeting in San Francisco. Many IETF working groups, where technical work in areas critical to the development of the Internet--including routing, transport and security--met in conjunction with the IETF meeting. Pradeep Sindhu, CTO and founder of official meeting host Juniper Networks, spoke to the IETF on "Clouds - The New Information Infrastructure."
Several groups with key roles in the technical evolution of the Internet announced new leadership at the meeting.
Joel Halpern, Chair of the IETF Nominating Committee, said, "We are extremely pleased with the excellent incoming candidates from the many qualified community members who offered to serve. They demonstrate the community-driven approach that shapes the IETF and will build on the excellent work of past leaders."
The IETF confirmed appointments for the Internet Engineering Steering Group (IESG), which provides the final technical review of Internet standards and is responsible for day-to-day management of the IETF. The confirmed IESG members include:
* IETF Chair: Russ Housley
* Applications Area Director: Alexey Melnikov
* Internet Area Director: Ralph Droms
* Operations and Management Area Director: Ron Bonica
* Real-time Applications Infrastructure Area Director: Robert Sparks
* Routing Area Director: Adrian Farrel
* Security Area Director: Tim Polk
* Transport Area Director: Lars Eggert
Members of the Internet Architecture Board (IAB) were also announced at the IETF meeting. IAB responsibilities include architectural oversight of IETF activities, and Internet Standards Process oversight and appeal. Incoming members of the IAB are:
* Marcelo Bagnulo
* Vijay Gill
* John Klensin
* Jon Peterson
* Danny McPherson (incumbent)
* Dave Thaler (incumbent)
Olaf Kolkman was reappointed as the Chair and Dow Street was reappointed as the Executive Director of the IAB. Aaron Falk was reappointed as chair of the Internet Research Task Force (IRTF), which promotes research of importance to the evolution of the future Internet by creating focused, long-term Research Groups working on topics related to Internet protocols, applications, architecture and technology.
The next meeting of the Internet Engineering Task Force, IETF 75, will be held 26-31 July 2009 in Stockholm, Sweden. Registration for IETF 75 will open in April.
About the IETF
The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual. More information is available on the IETF website: http://www.ietf.org
About the IAB
The Internet Architecture Board (IAB) is a committee of the Internet Engineering Task Force (IETF) and an advisory body of the Internet Society (ISOC). Its responsibilities include architectural oversight of IETF activities, Internet Standards Process oversight and appeal, and the appointment of the RFC Editor. The IAB is also responsible for the management of the IETF protocol parameter registries. For more information about the IAB, see: http://www.iab.org
About the Internet Society
The Internet Society is a non-profit organization founded in 1992 to provide leadership in Internet related standards, education, and policy. With offices in Washington, DC, and Geneva, Switzerland, it is dedicated to ensuring the open development, evolution, and use of the Internet for the benefit of people throughout the world. More information is available at: http://www.isoc.org
Subscribe to:
Post Comments (Atom)
1 comment:
The problem that we are facing, making promotion of IPv6 an ‘Internet Emergency’, is that it will actually take years to properly “operationalize” secure IPv6 capabilities in most carrier’s networks and enterprise infrastructure - - and we’re only 3-5 years from needing it to be operational. Taking too long to activate IPv6 as IPv4 resources dwindle could leave us with a gap in services that will affect Internet availability. That makes IPv6 deployment a business continuity issue for companies that use networked computers for operations, and ecommerce, email, VOIP, etc… and plan to operate past the next decade. Its not like Y2K - its more of an “end of oil” problem where the operating expenses get high - especially for companies trying to grow, compete, and launch new services past 2012. We suggest these as a few sensible steps for all companies and govt institutions:
*2009 - Pilot IPv6 security - don’t ignore it - its likely IPv6 is running on parts of your network already
*2010 - Pilot your “outward facing infrastructure” (www servers, DNS, VOIP, email gateways, ecommerce server, etc) working on IPv6 - Google is doing this already!
*2011 - Pilot (secure!) connections from your desktops/laptops out to other companies “outward facing infrastructure”
*2012 - Start working on your internal apps and infrastructure to eventually wean them off IPv4 - to lower your operational costs. It costs as much as +15% OPEX for your network to operate a dual stack…
Post a Comment