San Jose IETF 6bone BOF

[Bob Fink LBNL]

As I have had nothing but positive comments on an "official BOF" at San
Jose, both online and offline, I have sent the following to the IETF agenda
folk to get it rolling.  My  concern is that waiting any longer will risk
not getting a time slot at all.

However, please keep the discussion up so we can maintain a focus at the BOF=
=2E

At worst, we decide no working group desired, report this to the area
directors and go our merry way.  Can't hurt :-)


As the requestor of the BOF, I will be its chair, but this has nothing to
do with what you decide to do for a working group.


Thanks,

Bob

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
Date: Wed, 16 Oct 1996 07:38:40 -0700
To: agenda@ietf.org
=46rom: Bob Fink LBNL <RLFink@lbl.gov>
Subject: arranging for a 6bone BOF at the San Jose IETF
Cc: mo@uunet.uu.net, RLFink@lbl.gov, sob@harvard.edu

Per Scott Bradner's email below, I am requesting an agenda slot at the San
Jose IETF meeting for a 6bone BOF under the Operational Requirements Area.

It would be mosty helpful to not have this scheduled against IPng meetings
as this is a highly related activity, and of course no one wants Fridays :-)


The purpose of this BOF is to decide if a 6bone deployment working group
would be helpful to the 6bone process that is already underway, and to
discuss other ongoing items of 6bone business.  You can see current 6bone
information at:

	http://www-6bone.lbl.gov/6bone/

I have also enclosed an overview of the 6bone activities below.


The agenda will be:

1.  Discussion of usefulness and goals of a 6bone deployment working group

2.  Ongoing 6bone business


I will act as chair of the BOF and be responsible for its report and roster.

Please let me know what else you may need to aid in setting this BOF up.


Thanks,

Bob Fink


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
Date: Fri, 11 Oct 1996 16:18:24 -0400 (EDT)
=46rom: Scott Bradner <sob@newdev.harvard.edu>
To: mo@uunet.uu.net, RLFink@lbl.gov, sob@harvard.edu
Subject: Re: 6bone BOF for the IETF in San Jose

Bob,
	Sorry for the delay in getting back to you - yes, I think
it is fine for you to hold a 6bone BOF

	you need to do a writeup on what the BOF is about and an agenda
and send them to agenda@ietf.org with a cc to mike & me

Scott
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
6bone Overview (from the 6bone web pages)

The 6bone is an independent outgrowth of the IETF IPng project that
resulted in the creation of the IPv6 protocols intended eventually to
replace the current Internet network layer protocols known as IPv4. The
6bone is currently an informal collaborative project covering North
America, Europe, and Japan.

One essential part in the IPv4 to IPv6 transition is the development of an
Internet-wide IPv6 backbone infrastructure that can transport IPv6 packets.
As with the existing IPv4 Internet backbone, the IPv6 backbone
infrastructure will be composed of many Internet Service Providers (ISPs)
and user networks linked together to provide the world-wide Internet.

Until the IPv6 protocols are widely implemented and fully tested for
interoperability, production ISP and user network routers will not readily
place production Internet (IPv4) routers at risk. Thus a way is needed to
provide Internet-wide IPv6 transport in an organized and orderly way for
early testing and early use.

The 6bone is a virtual network layered on top of portions of the physical
IPv4-based Internet to support routing of IPv6 packets, as that function
has not yet been integrated into many production routers. The network is
composed of islands that can directly support IPv6 packets, linked by
virtual point-to-point links called "tunnels". The tunnel endpoints are
typically workstation-class machines having operating system support for
Ipv6.

Over time, as confidence builds to allow production routers to carry native
IPv6 packets, it is expected that the 6bone would disappear by agreement of
all parties. It would be replaced in a transparent way by production ISP
and user network IPv6 Internet-wide transport.

The 6bone is thus focused on providing the early policy and procedures
necessary to provide IPv6 transport in a reasonable fashion so testing and
experience can be carried out. It would not attempt to provide new network
interconnect architectures, procedures and policies that are clearly the
purview of ISP and user network operators. In fact, it is the desire to
include as many ISP and user network operators in the 6bone process as
possible to guarantee a seamless transition to IPv6.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
=10