[ppml] Proposed Policy: Capturing Originations in Templates

[Michael.Dillon at btradianz.com]

> Making a step toward validating that, in an off-line process not
> really related to BGP, someone who presents you with a block to which
> they want to announce reachability actually has the owner's permission
> to make that happen. Currently the process, absent IRR/RADB/RPSL, is
> left as an exercise to the reader to puzzle through.

Whether it is done in the BGP code of your router or in
an off-line process, is irrelevant. It is still a BGP issue.
People want BGP filters to clean up BGP announcements based
on the originating ASN in the BGP path.

I agree that this is best implemented off-line in an OSS
system and not on the router. I also believe that this should
not be viewed as BUILDING BGP filters because in many networks
it is wiser to use this information to VALIDATE or CROSS-CHECK
filters that are built in another manner. 

> all discusson of RR usage or quality is moot, it's not relevant to 
> this policy.

I think it is highly relevant because the policy proposal
explicitly mentions RRs and the lack of authoritative information
in them. This is a problem that ARIN can solve in their RR.
It doesn't need to be solved in WHOIS. 

At the same time, there is nothing wrong with collecting
this info on SWIP forms and then updating the RR database 
rather than the whois database. But since we are dealing 
with a fundamental RR issue, I think we should focus our
efforts on solving it in the RR, not on munging the whois
directory to be more RR-like.

--Michael Dillon