[53966] in North American Network Operators' Group
RE: Operational Issues with 69.0.0.0/8...
daemon@ATHENA.MIT.EDU (Barry Raveendran Greene)
Fri Dec 6 15:23:55 2002
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "'Adam \"Tauvix\" Debus'" <nanog@delsol.net>, <nanog@merit.edu>
Date: Fri, 6 Dec 2002 12:23:09 -0800
In-Reply-To: <017101c29d64$4e958f30$e2e8b1d8@adam>
Errors-To: owner-nanog-outgoing@merit.edu
IMHO - The RIRs are doing their part. They announce to the operations
aliases their intention to allocate a new block before they start doing
it. People like me (with the ingress-prefix-template), Rob Thomas (with
the bogon template), and Steve Gill (with the Junos flavor of the
ingress-prefix-template) start tweaking our templates and post them to
the community.
After that, it would be up to each operations team to execute within
their own network.
-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of
Adam "Tauvix" Debus
Sent: Friday, December 06, 2002 12:16 PM
To: nanog@merit.edu
Subject: Re: Operational Issues with 69.0.0.0/8...
>
> So for the sake of argument, in your proposal an ISP could filter all
of
> the blocks that the RIRs allocate out of and hamstring them
indefinitely?
>
Perhaps not, but an X month period after the inital allocation to
the
RIR where they don't assign out of that pool might be wise. Perhaps
e-mails
can be sent to the registered contacts of existing IP space upon initial
allocation, on the first of each month, and then on the last day of the
hold.
I know that I am sometimes a bit too busy to take care of something
like
that at the very instant I get the e-mail, and that it can fall to the
wayside. Many times a reminder e-mail has come at a moment where I was
able
do to something about it.
Thanks,
Adam "Tauvix" Debus
Linux Certified Professional, Linux Certified Administrator #447641
Network Administrator, ReachONE Internet
adam@reachone.com
