And I’d point to the evidence of a transfer market specifically for 16-bit ASNs
as good evidence of this.
That said, I’d like to understand better the relative imbalance of supply and
demand for these resources in the various RIR regions before I form a
conclusion as to whether that imbalance j
On Tue, Feb 06, 2018 at 12:25:05PM -0800, Owen DeLong wrote:
> Extended communities can solve the problem for all ASNs issued today
This simply is not true.
Kind regards,
Job
___
PPML
You are receiving this message because you are subscribed to
the ARI
Extended communities can solve the problem for all ASNs issued today or likely
to be issued in a very long time (at least 24 bits, more like 30 bits IIRC)
even if Large communities are not widely supported yet. Extended communities
are ubiquitous in most of the gear I’m familiar with.
Owen
> O
On Wed, Jan 31, 2018 at 2:20 PM, ARIN wrote:
> Draft Policy ARIN-2018-1: Allow Inter-regional ASN Transfers
>
> Problem Statement:
> There is a need to allow RIR transfers of ASNs with RIRs with an equivalent
> transfer policy.
Hello,
I OPPOSE the transfer of number resources to APNIC where rest
I will note that there is also working code widely deployed for extended
communities which do have formats which can work for all currently issued
32-bit ASNs.
(RFCs 4360 and 7153)
Owen
> On Feb 5, 2018, at 11:54 , David R Huberman wrote:
>
>
> If I may, I'd like to try and re-focus the dis
+1 works for me.
Owen
> On Feb 5, 2018, at 13:12 , Potter, Amy wrote:
>
> In response to the staff & legal assessment for 2017-3, we are proposing the
> following new language for subsection 3.6.5:
>
> 3.6.5
>
> An invalid POC is restricted to payment and contact update functionality
> w
RFC8092 was published roughly a year ago. I can’t imagine that we’ll see
universal support for it anytime soon, and there’s plenty of gear out there on
the internet today that won’t be getting a software update to support it.
I have encountered exactly this scenario, albeit on a private network
Job, I mostly agree with you.
There is, however, one issue with the way ARIN does things.
On ARIN whois records, there is a field for “Origin AS”.
In the event that an organization transfers out an AS that is listed on
their blocks as “Origin AS”, you’d like to think that the organization
in que
> On Feb 6, 2018, at 09:02 , hostmas...@uneedus.com wrote:
>
> I agree that IP addresses and ASN's are not associated with each other to the
> extent that changes in one, must trigger a change in the other. Thus, I
> disagree that an ASN transfer must only occur on "clean" ASNs without any
>
I agree that IP addresses and ASN's are not associated with each other to
the extent that changes in one, must trigger a change in the other. Thus,
I disagree that an ASN transfer must only occur on "clean" ASNs without
any associated IP networks.
For example, I might have an ASN because I am
On Thu, Feb 01, 2018 at 06:21:06PM +, Roberts, Orin wrote:
> You could, but then IPv6 routing/fragmentation becomes an issue.
How so?
> Unless when an ASN is transferred from ARIN all IP networks associated
> to that ASN are revoked/removed/deleted from ARIN. ie. I can acquire
> an ASN that
11 matches
Mail list logo
