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
Thu Jun 17 14:55:36 CEST 2004
Quoting Pekka Savola <pekkas at netcore.fi>: > I saw that -- but I don't see *any* justification for this > interpretation. Remember, the goal is to require 200 assignments to > *other* organizations, not be satisfied that you can make 200 > assignemnts to your internal network, or 100 assignments to your > internal network and 100 to other organizations! If so - please state this clearly in the policy so noone will make their own "interpretation" of how this should be done. -- 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 ]