| <<< Chronological >>> | Author Index Subject Index | <<< Threads >>> |
Re: [lir-wg] IPv6 assignments to RIPE itself
- Date: Wed, 15 Jan 2003 14:21:54 +0100
On Wed, Jan 15, 2003 at 14:11:14 +0100, Gert Doering wrote: > Hi, > > On Wed, Jan 15, 2003 at 01:59:35PM +0100, Ronald van der Pol wrote: > > BTW, I agree RIPE* is special. I can understand the need for separate > > /48s for the RIPE NCC office and the RIPE meetings. > > Why? As Leo already explained: RIPE != RIPE NCC. I see the usefulness of a /48 that travels along with the RIPE meetings. As far as I know, this /48 always has the same upstream (the RIPE _NCC_ office) by means of a v6-in-v4 tunnel. When native v6 connectivity will be widely available at meeting sites, this might change. rvdp
- Post To The List:
- Follow-Ups:
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: Gert Doering
- Re: [lir-wg] IPv6 assignments to RIPE itself
- References:
- [lir-wg] IPv6 assignments to RIPE itself
- From: Robert Kiessling
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: Gert Doering
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: Ronald van der Pol
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: leo vegoda
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: Ronald van der Pol
- Re: [lir-wg] IPv6 assignments to RIPE itself
- From: Gert Doering
- [lir-wg] IPv6 assignments to RIPE itself
| <<< Chronological >>> | Author Subject | <<< Threads >>> |
