[urgent assistance] 198.32.0.0/16 - Disappeared...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paging Bill Manning...

Unfortunately, we've tried to reach Bill, as well as other folks at
EP.NET to no avail, and this is impacting us quite negatively.

[snip]

Not available in any routing tables I have access to or any of the looking
glasses from http://www.nanog.org/lookingglass.html.

this is significant because any in-addr blocks that are authoritative @
flag.ep.net and dot.ep.net will now suffer from reverse name resolution
issues.

- From ATT route server:

route-server>sh ip bgp 198.32.4.13
% Network not in table

- From CerfNET route server:

route-server>sh ip bgp 198.32.4.13
% Network not in table

Allstream Toronto:

route-server.east>sh ip bgp 198.32.4.13
% Network not in table

This has been a problem since yesterday evening.

[snip]

FYI, some of our address space has been sub-allocated via EP.net
and relies on it's reachability:

[DOMAIN whois information for EP.NET ]
   Domain Name: EP.NET
   Namespace: ICANN Unsponsored Generic TLD - http://www.icann.org
   TLD Info: See IANA Whois - http://www.iana.org/root-whois/net.htm
   Registry: VeriSign, Inc. - http://www.verisign-grs.com
   Registrar: NETWORK SOLUTIONS, LLC. - http://www.networksolutions.com
   Whois Server: whois.networksolutions.com
   Name Server[whois+dns with ip] DOT.EP.NET 198.32.2.10
   Name Server[from whois+dns, whois ip]: DOT.EP.NET
2001:478:6:0:230:48FF:FE22:6A29
   Name Server[whois+dns with ip] FLAG.EP.NET 198.32.4.13
   Updated Date: 11-Jan-2007
   Creation Date: 09-Dec-1994
   Expiration Date: 08-Dec-2012
   Status: clientTransferProhibited
[whois.networksolutions.com]
Welcome to the Network Solutions Registrar WHOIS Server.

The IP address from which you have visited the Network Solutions Registrar
WHOIS
database is contained within a list of IP addresses that may have failed
to abide by Network Solutions' WHOIS policy. Failure to abide by this
policy can
adversely impact our systems and servers, preventing the processing of
other WHOIS requests.

To see the Network Solutions WHOIS Policy, click on or copy and paste the
following
URL into your browser:

http://www.networksolutions.com/whois/index.jhtml

If you feel that you have received this message in error, please contact us
at:
whoisquery@networksolutions.com and include the following information:

Whois Query: domain ep.net
YOUR IP address is 216.151.198.186
Date and Time of Query: Fri May 11 21:39:55 EDT 2007
Reason Code: CE
[whois.networksolutions.com]

Please contact me off-list is you have any inisght into this.

Thanks,

- - ferg

Fergie wrote:

Paging Bill Manning...

Unfortunately, we've tried to reach Bill, as well as other folks at
EP.NET to no avail, and this is impacting us quite negatively.

Congratulations, finally, after almost a year after the shutdown and
deprecation of the 6bone address space, returning it to IANA, all the
6bone prefixes are finally gone from the IPv6 routing tables at all
ISP's peering with GRH (which thus more or less gives a global IPv6 BGP
view)

grh.sixxs.net> show bgp 3ffe::/16 longer-prefixes
grh.sixxs.net>

(aka none :wink:

Checking Ghost Route Hunter : IPv6 DFP visibility : 6bone :: SixXS - IPv6 Deployment & Tunnel Broker

pTLA: 3ffe::/24
Country: us
NetName: ROOT66/US-CA
ASN: AS4555
Allocated: 1997-08-14
Last Seen: 2007-05-10 12:17:22

pTLA: 3ffe:800::/24
Country: us
NetName: ISI-LAP/US-CA
ASN: 4555
Allocated: 1997-08-14
Last Seen 2007-05-10 12:17:22

Thanks Bill for finally(!) shutting down the machines that you where
still using for announcing these prefixes. This definitely shows that
everybody is done experimenting with IPv6, expect for the upcoming Great
IPv6 Experiment of course :wink:

For the folks still using only IPv4: Remember that Geoff Huston and Tony
Hain have now aligned their prognoses for IPv4 Address Depletion: 2009
is the new date, so if you are not doing IPv6 yet, you better start
doing something about it, or you will be too late, and everybody who did
do something about it, is going to point and laugh at you while
ridiculing you saying "we told you so", which is going to be quite a lot
of fun :slight_smile:

Greets,
Jeroen

(only partially kidding, but it was time that 6bone routes finally
disappeared, he can resurrect the rest of ep.net though)

Is it just me or is this happening again? Re-paging :wink:

Thanks
Chris

Fergie wrote:

Since 198.32.0.0/16 is cut up and used by many, many different people in many disconnected networks, it seems to me that the absence of 198.32.0.0/16 in the RIB is a feature, not a bug.

(And I'm fairly sure this was pointed out last time, too :slight_smile:

Joe

However 198.32.2.10 and 198.32.4.13 (ep.net DNS) are not covered by any active prefix right now, 198.32/16 or otherwise, so that is a bug and not a feature :wink: I am not so concerned about 198.32/16 not showing up as I am that no other prefix which will handle those hosts is either.

Thanks
Chris

Joe Abley wrote:

A failure to reach ep.net's nameservers is presumably something to be taken up with ep.net, though, not NANOG :slight_smile:

Looks like the failure was temporary:

route-views.oregon-ix.net>sh ip bgp regex _4555$
BGP table version is 213222472, local router ID is 198.32.162.100
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
               S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

    Network Next Hop Metric LocPrf Weight Path
* 198.32.2.0 202.249.2.86 0 7500 2497 1239 4555 i
* 207.172.6.20 5 0 6079 3356 1239 4555 i
* 209.10.12.160 0 4513 701 1239 4555 i
* 65.106.7.139 3 0 2828 1239 4555 i

(etc, etc)

Joe

* jabley@ca.afilias.info (Joe Abley) [Fri 31 Aug 2007, 16:10 CEST]:

A failure to reach ep.net's nameservers is presumably something to be taken up with ep.net, though, not NANOG :slight_smile:

Huh. flag.ep.net was renamed flag.ip4.int?

Given that the best I can find out about ip4.int is a very brief and long-expired I-D from 1996, why is this domain still in the root zone?

At least ip6.int. was actually used for a brief time...

  -- Niels.