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. -- -=[L]=- `is not a sentence' is not a sentence.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Mar 29, 2010 at 11:17 PM, Lou Katz <lou@metron.com> wrote:
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 -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.5.3 (Build 5003) wj8DBQFLsZn8q1pz9mNUZTMRAmRdAKDNEdRM+DqS2SPG2t0QdZVsqyUMdwCg7bva 9dRverAlWwIVO7AH1smGEZg= =QjV0 -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/
On Mar 30, 2010, at 2:17 AM, Lou Katz wrote:
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.
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 -- Patrick Muldoon Network/Software Engineer INOC (http://www.inoc.net) PGPKEY (http://www.inoc.net/~doon) Key ID: 0x370D752C /* Don't meddle in the affairs of sysadmins, * for they are subtle and quick to anger. */
On 29 Mar 2010, at 11:17, Lou Katz wrote:
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... 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
At 8:24 -0700 3/30/10, Leo Vegoda wrote:
192.0.0.0/24 is used for the IANA IPv4 Special Purpose Address Registry:
For the record, there's an RFC dedicated to that range (which Leo co-edited): http://www.rfc-editor.org/in-notes/rfc5736.txt -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NeuStar You can leave a voice message at +1-571-434-5468 New pithy statement under construction...
On 30 Mar 2010, at 8:24, Leo Vegoda wrote: On 29 Mar 2010, at 11:17, Lou Katz wrote:
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.
I have now updated the registration for 192.0.0.0/24 in the ARIN whois database with more current references. Regards, Leo
participants (5)
-
Edward Lewis -
Leo Vegoda -
Lou Katz -
Patrick Muldoon -
Paul Ferguson