[98057] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: An Internet IPv6 Transition Plan

daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Tue Jul 24 12:00:29 2007

Date: Tue, 24 Jul 2007 15:35:25 +0000
From: bmanning@vacation.karoshi.com
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
Cc: bmanning@vacation.karoshi.com, John Curran <jcurran@istaff.org>,
        nanog <nanog@merit.edu>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD402A3D658@PACDCEXCMB05.cable.comcast.com>
Errors-To: owner-nanog@merit.edu


On Tue, Jul 24, 2007 at 10:59:34AM -0400, Durand, Alain wrote:
>  
> 
> > -----Original Message-----
> > From: bmanning@vacation.karoshi.com 
> > [mailto:bmanning@vacation.karoshi.com] 
> 
> > > 1) What is the IPv6 'service'?
> > >    For example, is it reasonable to define a 'basic' level
> > >    service as web+mail and an 'extended' service as 
> > everything else?   
> > > 
> > 
> > 	actually, for some of us there is the thought that before 
> > 	the "basic" service of web+email can work at all, one needs
> > 	to have a couple of other infrastructure pieces in play, 
> > 	namely DNS and NTP... Oh, and the routing to knit these
> > 	services together.
> 
> Sure, this is very important... but I was talking about the "user
> experience".
> 
>   - Alain.

	good point.  there are "levels" of basic services.
	i suspect that the network operations folks would want
	to have working viable v6 (naming, timestamps, audit,
	measurement) running -before- turning up production
	"basic" service for the "user experience".

	assuming that is the case, what things to these assembled
	operators think are critical for operational stability
	in bringing online a new address family?

	Randy had a non-exaustive list at the last IEPG.  To memory:
		MIB, AAAA, DNS, NTP, SYSLOG, DHCP, RADIUS,
		CALEA, etc. 

--bill
	

home help back first fref pref prev next nref lref last post