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] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Ingvoldstad
frettled at gmail.com
Tue May 19 18:55:54 CEST 2015
On Tue, May 19, 2015 at 6:32 PM, David Huberman < David.Huberman at microsoft.com> wrote: > > > In 2014 there were 12 organizations that elected to receive a 4-byte AS > number and later came back to ARIN to exchange it for a 2-byte AS number. > Each of these organizations stated issues with their transit providers > either unwilling or unable to accept the use of a 4-byte AS number by a > customer. > > It's seems as if the transit providers are mentioned a bit too frequently here. Does anyone have any information about how long it would take to get transit providers 4-byte-ready? -- Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20150519/42ea13ba/attachment.html>
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]