[address-policy-wg] FW: ASNs of organizations in reported IPv4 transfers
- Previous message (by thread): [address-policy-wg] FW: ASNs of organizations in reported IPv4 transfers
- Next message (by thread): [address-policy-wg] [External] Re: FW: ASNs of organizations in reported IPv4 transfers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Tue Jan 7 07:39:25 CET 2020
> Because it's not rational or meaningful to do that. There's no reason > to assume that there's a static, unchanging binding between address > space and an ASN. if there was, we would not need routing :) further, there is no actual _routing_ binding of an AS to a member LIR identity. i.e. an LIR may have no ASs, or multiple ASs. address space 'belonging' to an LIR might be legitimately announced by an AS belonging to a different LIR. from a research point of view, one might ask whether these confounding complications are sufficiently prevalent to obscure the signal which vasileios seeks. [ persoanlly, i would not go down this capybara hole ] randy
- Previous message (by thread): [address-policy-wg] FW: ASNs of organizations in reported IPv4 transfers
- Next message (by thread): [address-policy-wg] [External] Re: FW: ASNs of organizations in reported IPv4 transfers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]