We recently were told to contact a client (via ftp) at 192.0.0.201. IANA lists this as
Special Use, but refers to "RFC 3330 for additional information. http://www.rfc-editor.org/rfc/rfc3330.txt".
This RFC says that it might be assigned in the future.
So, did the folks who sent us the IP address fat-finger, or has this been assigned?
There does not appear to be any route to it.
That's because there isn't:
route-views2.routeviews.org> sho ip bgp 192.0.0.201
BGP routing table entry for 0.0.0.0/0
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11686 19151
96.4.0.55 from 96.4.0.55 (96.4.0.55)
Origin IGP, localpref 100, valid, external, best
Last update: Sun Dec 27 02:46:56 1970
- -ferg
My guess is your client is using it that IP internally, perhaps mistakenly thinking it is RFC1918 space? I've seen this a lot when dealing with the less clued.
-Patrick
We recently were told to contact a client (via ftp) at 192.0.0.201. IANA lists this as
Special Use, but refers to "RFC 3330 for additional information. http://www.rfc-editor.org/rfc/rfc3330.txt"\.
This RFC says that it might be assigned in the future.
RFC 3330 was obsoleted with the publication of RFC 5735. I thought I'd updated all the references we made to RFC 3330 but if I've missed one I'd be grateful if you could point me to it.
So, did the folks who sent us the IP address fat-finger, or has this been assigned?
There does not appear to be any route to it.
192.0.0.0/24 is used for the IANA IPv4 Special Purpose Address Registry:
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
No assignments have been made yet but I'd strongly advise people not to use addresses in this range as a substitute for the space reserved in RFC 1918. It's likely to cause operational problems at some point in the future.
Regards,
Leo Vegoda
For the record, there's an RFC dedicated to that range (which Leo co-edited):
http://www.rfc-editor.org/in-notes/rfc5736.txt
I have now updated the registration for 192.0.0.0/24 in the ARIN whois database with more current references.
Regards,
Leo