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] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)
- Previous message (by thread): [address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Tue Nov 10 11:41:25 CET 2015
El 10/11/2015 a las 10:49, Peter Hessler escribió: > On 2015 Nov 10 (Tue) at 04:30:22 +0000 (+0000), Aftab Siddiqui wrote: > :Just for my understanding, is there any demand for 16b ASN from the > :community? > > There is a technical case when attempting to use communities in the > <as>:<as> format. There is not yet a 32:32b community available, > even in extended communities. 16b:32b and 32b:16b do exist, so I'm not > sure how critical that is. And that is critical. I only have a 32b ASN and is impossible to work with communities while 32b:32b comm doesnt exists.
- Previous message (by thread): [address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]