Sandy and David,
On 18/09/2009, at 5:25 AM, Sandra Murphy wrote:
On Thu, 17 Sep 2009, David Conrad wrote:
Sandy,
On Sep 17, 2009, at 5:59 AM, Sandra Murphy wrote:
I recognize that there is an fear that this system somehow puts
ISPs under someone's control. I would answer that there is not
any more control than is already the case.
I suppose it depends on what people are going to do with RPKI.
Today, RIR influence on routing is essentially advisory in nature
-- if an address holder (say) fails to pay their address
maintenance fee, RIRs can, at most, remove the address holder's
blocks from whois databases. However, as I understand it, this has
limited effect on existing contractual relationships between the
address holders and the folks who already announce their space (it
may have more effect on address holders who are attempting to find
new ISPs to announce their space). The RIR could potentially
reallocate the space, but this would likely be a good way of
annoying multiple parties (not just the folks the address space was
reclaimed from).
Andrei's message acknoledged that address reclamation is a part of
RIR daily life. He did not explicitly mention
For some class of address holders in some regions, I believe that
reclamation is not possible (historical?). Are they outside of the
scope of the RPKI?
re-allocation to a different party, but I can't imagine holding on
to unused address space, particularly in this current era of address-
shortage fears.
I suspect that the time from reclamation to deaggregation and
reallocation will progressively grow smaller.
If RPKI does not change this, then you're right -- there is not any
more control. However, if filter lists are built or routers check
origin authenticity in real-time by traversing the RPKI tree(s),
I think it goes deeper based on draft-pmohapat-sidr-pfx-
validate-02.txt finding its way _into_ routers.
Those who build filter lists either rely on their customers' reports
or on IRR data, which is based on the RIR address allocations.
I think Chris's past email regarding 216.239.63.0/24 suggests that
the various IRRs aren't that tightly bound.
Cheers
Terry
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr