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 ]
amar at telia.net
amar at telia.net
Wed Jun 16 12:02:52 CEST 2004
Quoting Kurt Erik Lindqvist <kurtis at kurtis.pp.se>: > Why not? If I have a large infrastructure, or is in the start-up phase > or going through a network merger etc. I might have a lot of internal > infrastructure but not many customer allocations. I fail to see why we > would not include own allocations as those will be coming out of your > block anyway. The policy states that You can assign a /48 per POP - lets say a "broadband POP". If that should include the users asignments or not is not defined. -- amar ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
- 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 ]