[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sig-dns]George's #2: Escalation of reports
At 8:55 +1000 5/2/03, George Michaelson wrote:
Secondly, a process for APNIC staff to escalate reports on these tests, which
include specific time periods, to lead to a deadline for de-listing. This
process is very likely to reflect ARIN processes. This part of the proposal is
likely to be more APNIC specific than the first part. The process for
communication and escalation is separated from the definition of
lameness tests
to permit process-centric changes to be made independently.
The ARIN policy specifies that once we determine that there is lameness we:
first contact POC's for the network via email
failing that, contact the POC's for the AS originating routes for the prefix
failing that, call POC's
failing that, send postal mail
In our region we have a lot of interaction between the registrants
and the registry. This includes phone calls, as the region has a
dominate language and is fairly constrained in time zones. This
interaction is handled by the registration staff. Engineering is
conducting the testing, has produced the tools and has given training
to the Registration staff.
Not having travelled widely in Asia myself, I would be hard pressed
to recommend a process for APNIC. Also, the division of labor we use
may not be desirable elsewhere.
I can expand on the second contact point though. In our database,
organizations have network registrations and AS number registrations.
It is tempting to think that the networks registered are originated
in the AS numbers we see. However, this is not the case - it is up
to our operation community to configure routing of what they work
with. To perform the correlation, we rely on examinations of the BGP
routing tables we can see into.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-703-227-9854
ARIN Research Engineer
Your office is *not* a reality-based sit-com TV show.
