[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
6bone.net now active
- Subject: 6bone.net now active
- From: [email protected] (Alain Durand)
- Date: Thu, 15 May 1997 19:26:03 +0200
- In-reply-to: Bob Fink <[email protected]> "Re: 6bone.net now active" (May 15, 9:13am)
- References: <v03007823af9ec6ff3176@[128.3.9.22]> from Bob Fink at "May 13 97 06:43:28 pm" <v03007818afa0e5d8d32d@[128.3.9.22]>
On May 15, 9:13am, Bob Fink wrote:
> Subject: Re: 6bone.net now active
> >As I mentioned earlier, I would enter the border routers of every IPv6 site
> >into the 6bone.net zone with the short site name (e.g. "fauern.6bone.net" or
> >"join.6bone.net" or "cisco.6bone.net" - I think you get the idea ;-). That
> >would make traceroutes much easier to understand.
>
> This might be a lot of work. I do think all backbone border routers (and
> maybe the transits as well) could be named like this.
>
> As we are trying to emulate a real network, maybe we should treat the
> "leaf" sites as the users and thus not part of the 6bone.net domain.
I talked about that to some people at last IETF. A common answer is that
we do not want to recreate the .arpa domain.
www.6bone.net, ftp.6bone.net registry.6bone.net, [email protected]
& all sorts of things like that make a lot of sense to me.
For site entry point, we might have 6bone-gw.ipv6.your.site or anything
similar.
That's nice enough for traceroutes.
- Alain.