william at elan
Apr 14, 2007, 5:50 PM
Post #17 of 53
(1354 views)
Permalink
|
On Sat, 14 Apr 2007, David Conrad wrote:
> Hi,
>
> On Apr 14, 2007, at 12:47 PM, Rob Thomas wrote:
>> We checked with IANA, ARIN, and the US DoD regarding 7.0.0.0/8. We were
>> told that this netblock should not see the light of day,
>
> Right. Packets sourced out of 7.0.0.0/8 should never be seen on the
> Internet.
What about BGP routes for it then (see below)?
>> though there is some debate about its allocation status.
>
> Not really. The debate is about how that status should be reflected in the
> IPv4 registry maintained by IANA. The ARIN data is, as far as I am aware,
> accurate.
>
>> We're waiting for all of those parties to issue a consistent statement
>> before we make any changes.
>
> When we tried to update the IANA registry to reflect what was in the ARIN
> database, we were told not to. We tried to explain the registration
> information was already public via ARIN, but were told not to update the IANA
> registry. IANA and ARIN are working out something to resolve this issue.
Ok. I'm going to take the above to mean that its not in fact a bogon block
and that DoD is correct owner of the block. But as I do have tickets open
with both ARIN and IANA, I'll wait a little bet for an answer there before
making actual update.
The question now still remains regarding 7.1.1.0/24 advertisement.
Is it legitimate or an error or something worse?
P.S. This advertisement has been around from start of the year, around
Jan 15th is I think when it started. Previously I've not seen this block
in BGP although it does not mean it did not happen for specific peers
who did not pass it along further.
--
William Leibzon
Elan Networks
william [at] elan
|
signature.asc
1
