Mailing List Archive

208/8 announcements
I am under the impression that the 208/8 network has not yet been
assigned to anyone. It appears we are only up to 207.19/16.

However, as someone (Avi?) pointed out earlier:

| Cis3#sh ip bgp 208.0.0.0 255.0.0.0 long
| BGP table version is 34728, local router ID is 192.35.171.193
| Status codes: s suppressed, * valid, > best, i - internal
| Origin codes: i - IGP, e - EGP, ? - incomplete
|
| Network Next Hop Metric LocPrf Weight Path
| *>i208.0.1.0 192.35.171.34 1 50 0 3561 1280 3847 ?
| *>i208.0.4.0 192.35.171.34 1 50 0 3561 1280 3847 ?
| *>i208.0.5.0 192.35.171.34 1 50 0 3561 1280 3847 ?
| *>i208.0.9.0 192.35.171.34 1 50 0 3561 1280 3847 ?
| Cis3#

Is anyone filtering these routes? From a customer perspective, I think
it would be nice if my providers would do so.

Or maybe these guys would filter them:

| anka:~# whois 3847
| [rs.internic.net]
| Internet Media Network, Inc. (ASN-IMN)
| 20417 NORDHOFF STREET
| CHATSWORTH, CA 91311
|
| Autonomous System Name: IMN
| Autonomous System Number: 3847
|
| Coordinator:
| Joffe, Rodney (RJ48) rjoffe@IMN.NET
| 818-407-0000
| Alternate Contact:
| Gibbs, Mark (MG148) mgibbs@RAIN.ORG
| 818-700-6900
|
| Record last updated on 23-Sep-94.
|
| The InterNIC Registration Services Host contains ONLY Internet Information
| (Networks, ASN's, Domains, and POC's).
| Please use the whois server at nic.ddn.mil for MILNET Information.
| anka:~#

I dunno, maybe I should filter them. What are other people doing?

-alan
Re: 208/8 announcements [ In reply to ]
Well, we're filtering them. :)

RobS


> Is anyone filtering these routes? From a customer perspective, I think
> it would be nice if my providers would do so.
>
> Or maybe these guys would filter them:
Re: 208/8 announcements [ In reply to ]
>
> Well, we're filtering them. :)
>
> RobS
>
>
> > Is anyone filtering these routes? From a customer perspective, I think
> > it would be nice if my providers would do so.
> >
> > Or maybe these guys would filter them:
>

Ah, but what happens when the NIC starts allocating out of 208/8?

Avi
Re: 208/8 announcements [ In reply to ]
......... Avi Freedman is rumored to have said:
rob] Well, we're filtering them. :)
rob] RobS
rob]
rob]
alan] Is anyone filtering these routes? From a customer perspective, I think
alan] it would be nice if my providers would do so.
alan]
alan] Or maybe these guys would filter them:

] Ah, but what happens when the NIC starts allocating out of 208/8?
] Avi

Uhm, take the filters out?

-alan
Obviousness Engineer, level III
Re: 208/8 announcements [ In reply to ]
>
> ......... Avi Freedman is rumored to have said:
> rob] Well, we're filtering them. :)
> rob] RobS
> rob]
> rob]
> alan] Is anyone filtering these routes? From a customer perspective, I think
> alan] it would be nice if my providers would do so.
> alan]
> alan] Or maybe these guys would filter them:
>
> ] Ah, but what happens when the NIC starts allocating out of 208/8?
> ] Avi
>
> Uhm, take the filters out?
>
> -alan
> Obviousness Engineer, level III
>

And so how many of your customers have unreachability problems for how long
before you realize that the NIC is allocating out of 208/8?

<Insert levity, I'm not trying to start flamage.>

And is the NIC going to allocate around the 208/8 terrorists?

Avi
Re: 208/8 announcements [ In reply to ]
Most likely the same thing that happens when the NIC allocates out of
any other part of the address space.. Folks will register these prefixes
in the IRR of their choice, and they won't be filtered any more. :) Any
problems in that area are handled graciously by most providers, and ANS
is happy to assist. :)

RobS


>Ah, but what happens when the NIC starts allocating out of 208/8?
>
>Avi
Re: 208/8 announcements [ In reply to ]
> I am under the impression that the 208/8 network has not yet been
> assigned to anyone. It appears we are only up to 207.19/16.
>
> However, as someone (Avi?) pointed out earlier:
>
> | Network Next Hop Metric LocPrf Weight Path
> | *>i208.0.1.0 192.35.171.34 1 50 0 3561 1280 3847 ?
> | *>i208.0.4.0 192.35.171.34 1 50 0 3561 1280 3847 ?

Well, it looks like a fat finger to me...I see that 207.0 - 207.3 is assigned
to MCI. I'll be the client was allocated these out of 207 instead of 208,
and just mistyped them.

Dave

--
Dave Siegel President, RTD Systems & Networking, Inc.
(520)623-9663 Network Engineer -- Regional/National NSPs (Cisco)
dsiegel@rtd.com User Tracking & Acctg -- "Written by an ISP,
http://www.rtd.com/~dsiegel/ for an ISP."
Re: 208/8 announcements [ In reply to ]
> Ah, but what happens when the NIC starts allocating out of 208/8?

for my part, when 208/8 starts to be valid i will stop filtering it.
Re: 208/8 announcements [ In reply to ]
> rob] Well, we're filtering them. :)
> rob] RobS
> rob]
> rob]
> alan] Is anyone filtering these routes? From a customer perspective, I think
> alan] it would be nice if my providers would do so.
> alan]
> alan] Or maybe these guys would filter them:
>
> ] Ah, but what happens when the NIC starts allocating out of 208/8?
> ] Avi
>
> Uhm, take the filters out?

That was ans that responded. The filtering he's refering to is the RADB,
obviously, which is an easy filter to fix, if you know what you're supposed
to do with it. ;-)

Dave

--
Dave Siegel President, RTD Systems & Networking, Inc.
(520)623-9663 Network Engineer -- Regional/National NSPs (Cisco)
dsiegel@rtd.com User Tracking & Acctg -- "Written by an ISP,
http://www.rtd.com/~dsiegel/ for an ISP."
Re: 208/8 announcements [ In reply to ]
Hm, interesting, Rob. So what happens when we register
something the NIC hasn't allocated yet in the IRR?

Sean.
Re: 208/8 announcements [ In reply to ]
Most likely something similiar to what is happening now to every
provider that doesn't filter. It just provides an extra hoop to jump
through. As I'm sure you know, most of these problems are not the result
of maliciousness, but unfortunate error. The IRR's are some
protection. They are not a perfect answer.

RobS

>From: Sean Doran <smd@icp.net>
>Subject: Re: 208/8 announcements

>Hm, interesting, Rob. So what happens when we register
>something the NIC hasn't allocated yet in the IRR?
>
> Sean.
Re: 208/8 announcements [ In reply to ]
On Wed, 3 Jan 1996, Sean Doran wrote:

> Hm, interesting, Rob. So what happens when we register
> something the NIC hasn't allocated yet in the IRR?
>
> Sean.
>
it works. there is no check right now. you can enter anything, including
all your static backbone routes, Sean.


Mike


*********************************************************************
* Unsolicited Commercial E-Mail will cost $500/message under USC 47 *
* which can be found online at http://www.law.cornell.edu/uscode/47/*
*********************************************************************
----------------------------------------------------------
IDT
Michael F. Nittmann ---------
Senior Network Architect \ /
(201) 928 1000 xt 500 -------
(201) 928 1888 FAX \ /
mn@ios.com ---
V
IOS
Re: 208/8 announcements [ In reply to ]
>
> Hm, interesting, Rob. So what happens when we register
> something the NIC hasn't allocated yet in the IRR?
>
> Sean.

Your baiting again Sean. The same thing that happens when
ChinaNet starts advertising the CIDR block 204.94.0.0 - 204.97.255.0
or EUnet starts advertizing block 18/8.

--
--bill