V6-Deployment Gathering Minutes

[bound@zk3.dec.com]

Folks,

If you want to get involved with this list
you can join by sending mail to majrodomo@alpha.zk3.dec.com by
subscribing to v6-deployment-cabal list.

This should not replace the purpose of the v6imp list.

/jim

----------------------
Return-Path: bound@alpha.zk3.dec.com
Received: from bryalpha.zk3.dec.com by mailhub2.zk3.dec.com (5.65v4.0/1.1.10.5/24Sep96-0323PM)
	id AA05631; Mon, 11 Jan 1999 09:11:29 -0500
Received: by alpha.zk3.dec.com (8.8.8/1.1.8.2/18Feb95-1123AM)
	id JAA0000025487; Mon, 11 Jan 1999 09:10:35 -0500 (EST)
Received: from quarry.zk3.dec.com by alpha.zk3.dec.com (8.8.8/1.1.8.2/18Feb95-1123AM)
	id JAA0000020829; Mon, 11 Jan 1999 09:10:34 -0500 (EST)
From: Jim Bound <bound@alpha.zk3.dec.com>
Received: from localhost by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM)
	id AA20816; Mon, 11 Jan 1999 09:10:34 -0500
Message-Id: <199901111410.AA20816@quarry.zk3.dec.com>
To: v6-deployment-cabal@alpha.zk3.dec.com
Subject: High-Level Minutes from the Gathering
Date: Mon, 11 Jan 1999 09:10:34 -0500
X-Mts: smtp
Sender: owner-v6-deployment-cabal@alpha.zk3.dec.com
Precedence: bulk
Reply-To: Jim Bound <bound@alpha.zk3.dec.com>

Folks,

Here is my recollection of the high-points of the gathering.
Please send me bullets and additions OK.

Critical reqs for IPv6 deployment:

  Vendors must deploy IPv6 in base products:

     Required First Stage deployment needs:

       1) IPv6 stack supporting core specs
       2) Transition Mechanisms (1933-update) and V6overV4 Tunnels
       3) RIPng and BGP4+ (for forwarding)
       4) AAAA Records for now
       5) WEB Server and Browser
       6) Basic API
       7) Basic Network Utilities (ping, ifconfig, netstact, tcpdump)
       8) FTP and TELNET
       9) Email via Sendmail
       
   We need to discuss this list more in depth on the mail list and 
   sub-bullet requirements.

   We need to define additional stages of deployment and transition
   scenarios.

   What time-frames can Host and Routers vendors commit to now?

  Need to discuss the business reasons for IPv6 and killer apps that
  will benefit.

  What key features do ISPs need?

  What key features do commercial end users need?

  What key features do highly-technical end users need?  

  What applicatons are critical path to be ported supported by
     VENDORS?
     ISVs?
     FREE-WARE APPS?

  We need to set up an intense technical grass roots movement?

    Perry Metzger suggested this and will try to set up mail 
    lists and coordinate IPv6 servers within the technical 
    community.  We will have another mail list called v6-lovers
    which will be for the entire world to discuss the needs 
    of IPv6 for deployment.

    This will be our first priority and this list will feed
    future requirements and bugs, etc...

    Comment was we need real customers on this list too.

  We need to coordinate efforts in the IPv6 community to 
  get IPv6 deployed by sharing information across the 
  board.

  We will need "how to" for transition mechanisms.

/jim