This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Morgado
chbm at cprm.net
Tue Jun 22 16:05:08 CEST 2004
On Tue, Jun 22, 2004 at 02:26:40PM +0200, Gert Doering wrote: > Not that much. One could apply more-specific filters to routes coming > from other regions, so it *would* save something. Or the customer might What's this "regions" you speak about ? We're a fairly small (in the global scheme of things) transit provider and we're connected to 4 continents. Are you thinking about toy ISPs with one transit and a connection to the local IX ? -- Carlos Morgado <chbm at cprm.net> - Internet Engineering GPG key: 0x75E451E2 FP: B98B 222B F276 18C0 266B 599D 93A1 A3FB 75E4 51E2 The views expressed above do not bind my employer.
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]