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/address-policy-wg@ripe.net/
[address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Tue Aug 11 13:26:28 CEST 2015
> - if an end user wants a single ASN32 and they don't already have one, they > should get it on the basis of entitlement. > > - if an end user wants more than one ASN32, they should get it on the basis > of a needs-based policy. > > - if an end user wants one or more ASN16s, they should get it on the basis > of an needs-based policy, unless the remaining pool of ASN16s has reached a > certain threshold > > - regardless of the requirement, end users may only receive one ASN16 from > the remaining pool, and this should be assigned on the basis of a > needs-based policy. those last two do not correlate and, does end user include lir? randy
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]