IAB's Introduction to the Wed Technical Plenary

"Gregory Lebovitz" <gregory.ietf@gmail.com> Tue, 29 July 2008 19:18 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id DE85B3A6B42; Tue, 29 Jul 2008 12:18:58 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 3990228C104 for <ietf@core3.amsl.com>; Tue, 29 Jul 2008 12:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Tc6GUGhTJ81X for <ietf@core3.amsl.com>; Tue, 29 Jul 2008 12:18:55 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com []) by core3.amsl.com (Postfix) with ESMTP id D8BD23A6B41 for <ietf@ietf.org>; Tue, 29 Jul 2008 12:18:55 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so17260wfd.31 for <ietf@ietf.org>; Tue, 29 Jul 2008 12:19:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type; bh=/kPCGmYJVjVI6g8bB7rv5Ka+EmPmriglsYGt63gF2jg=; b=Y/b1TSaAIwNk82L6otOht3IvJ7jPu0ERDzKfxp3S/l2Qj/8JY5i5jT2xoEB3SYGyJJ 9XhAqinm4sWb9AYfe0fNZgVpXayhrt7y8QY8xfgp+stwpkKCD6QwFpEDe8zZScZbNzlo xadj1AHuqTz3KY8igq06v8LHyVgDK7zOSa5c4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=TbGFZiGk5sF4jqQYziRlYTyM6vcWN6FFXuKIunPbrSd4l0akxcnmlZw35tAclBcjab 41y6jdktkuJzyO2VP/una7te1VDdjpxVo3m8YtzFFCos9w7/sW+5MUbWIomZj/ftywrw /4iSCKOsfpSOqmqZr4dHO1+s5acWcJ9HRv7oo=
Received: by with SMTP id a2mr2302445wff.160.1217359148745; Tue, 29 Jul 2008 12:19:08 -0700 (PDT)
Received: by with HTTP; Tue, 29 Jul 2008 12:19:08 -0700 (PDT)
Message-ID: <f1548840807291219j5909cfe1p3a083f78e2c261ab@mail.gmail.com>
Date: Tue, 29 Jul 2008 12:19:08 -0700
From: Gregory Lebovitz <gregory.ietf@gmail.com>
To: ietf@ietf.org, 72attendees@ietf.org
Subject: IAB's Introduction to the Wed Technical Plenary
MIME-Version: 1.0
Cc: iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0349078674=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

IAB's Introduction to the Wed Technical Plenary

This Wednesday night the IAB invites you to join us at the Technical Plenary
where we will hear first hand from 5 members of the Internet community who
have been embroiled in operational IPv6 deployments. They represent the
perspectives of RIR's, network operations teams, broadband services, content
delivery services, and Host Applications. They will share with us about
their IPv6 adoption successes, hurdles, and IPv4 depletion contingency
planning. There will be both moderated and open Q&A sessions.

Motivation & Background
Studies suggest that the completion of IPv4 address allocations will occur
in the not too distant future. One example,
http://www.potaroo.net/tools/ipv4/ estimates that at the current rate IANA
will allocate its last block of addresses to the RIR's by February 2, 2011.

Regardless the exact date one expects, the concept of an empty storehouse
will change the networking landscape. In order to ready for that eventual
moment, various players are working towards wider IPv6 deployment.

Some content providers are planning ahead, working to ready their content
for IPv6 endpoint hits. This has recently become visible, and the volume of
work is mountainous. Some service providers and broadband providers see the
need, started some time ago, and are moving toward infrastructure and
service delivery that can/will run on IPv6. Both face a bit of a
chicken-and-egg problem: the content providers would move faster if they
knew the operators had the services fully baked to deliver IPv6 eyeballs to
the content. Meanwhile, the operators say they would invest more in their
IPv6 services and infrastructure deployments if the content the
end-customers demand was available and abundant. The two are interdependent;
one cannot be without the other.

Enterprises are, in some way, the swing vote. Objectively, few enterprises,
have moved to wide scale deployments of IPv6. Some have IPv6 pilots, a few
have partial deployments. Yet they may hit the v4 allocation cliff harder
than either the other two communities. This will leave them in a costly
scurry to react at the last minute.

IPv6 deployment in operational networks across the Internet is a work in
progress. Transition mechanisms have existed and been deployed for years,
including dual-stacks and various translation and tunneling mechanisms. Over
time, more hosts and networks are moving to native IPv6 operations.
Collectively, we now have several years of experience with both.

The IAB has established this plenary topic to provide some background  and
input from those experienced with deployments and issues in order to empower
the IETF community do its part to encourage and facilitate the  world-wide
deployment of IPv6.

We have a very full agenda (
https://datatracker.ietf.org/meeting/72/agenda.html) for Wednesday's
Technical Plenary, and will begin promptly at 17:00 in Convention 1 and 2,
just left of the IETF registration desk. We look forward to seeing you then.

Gregory Lebovitz
Wednesday's Panel Moderator,
on behalf of the IAB

IETF related email from
Gregory M. Lebovitz
Juniper Networks
Ietf mailing list