[address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Dear all,

On 12/11/2015 17:13, Saku Ytti wrote:
> You should be saying this. This is what we got from RIPE NCC trying to
> pull it off. And I agree with them. If hostmasters need to decide, we
> need to tell them what are the rules. i.e. w need to iterate
> acceptable uses, which I don't want. I don't expect to know all use
> cases.

Well, if the only limitation making 16bit ASN required is to be able 
to export BGP communities to clients, why not just use this as the 
condition to request a 16bit ASN instead of a 32bit :
 - demander must have plans for BGP transit (re)selling
 - demander must explain the communities he plans to export.

These are criteria that do not require Ripe NCC staff to have much
knowledge about BGP operation nor about all possible use cases.

Moreover these should apply to the EndUser (signer of a LIR sponsor
agreement), not to the LIR.

I believe next to come policies should always include respect of
the policiy as mandatory to avoid the granted ressource to be 
withdrawn.

Best regards,
Sylvain Vallerot

- -- 
http://www.opdop.fr  -  mutualiser et interconnecter en coopérative
Opdop - Société Coopérative d'Interêt Collectif sous forme de SARL
sur IRC réseau geeknode #opdop - tél: 0950 31 54 74, 06 86 38 38 68
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iF4EAREIAAYFAlZGT2gACgkQJBGsD8mtnRH3qQD/e4GBIumaAY9SZVhoomfy7Qkr
e0gntlUwU4r0qJ/wi40A/R6gqT8Yiemi8m9ysXC4et0CA2y8y0NxO/pr9EnwPneD
=4uVo
-----END PGP SIGNATURE-----