I'm sorry my RR update was ... too late? Did this cause a problem for
someone?
--N
(AS36561)
On Mar 2, 2010, at 7:28, Larry Blunk <l...@merit.edu> wrote:
Christopher Morrow wrote:
On Tue, Mar 2, 2010 at 3:50 AM, Tomoya Yoshida <yosh...@nttv6.jp>
wrote:
Thank you Geoff.
I asked because I could see 1/8 of merit AS237 but couldn't see
of origin AS36561 for those two in database.
Even if it's an experiment and sort term, It's better to be
registerd
in right origin I think. # It could be guessed but...
which databases?
morr...@localhost:~$ whois -h rr.arin.net 1.2.3.0
% This is the ARIN Routing Registry.
% Note: this output has been filtered.
% Information related to '1.2.3.0/24AS36561'
route: 1.2.3.0/24
descr: YouTube, Inc.
descr: 901 Cherry Ave
descr: San Bruno, CA 94066
descr: US
origin: AS36561
mnt-by: MNT-YOUTU
source: ARIN # Filtered
morr...@localhost:~$ whois -h rr.arin.net 1.1.1.0
% This is the ARIN Routing Registry.
% Note: this output has been filtered.
% Information related to '1.1.1.0/24AS36561'
route: 1.1.1.0/24
descr: YouTube, Inc.
descr: 901 Cherry Ave
descr: San Bruno, CA 94066
descr: US
origin: AS36561
mnt-by: MNT-YOUTU
source: ARIN # Filtered
These ought to then get around to other IRR-ish-things when their
propogation times hit, yes?
-Chris
I'm not positive that this is still the case, but I believe that
there can be quite a bit of latency in mirroring due to the
way RIPE database code (which ARIN uses) works. The
last object(s) registered are not pushed to the mirror stream until
the next object(s) are registered. I believe RIPE regularly pushes
a dummy object in order to keep it's mirrors more regularly
synced. I don't think that ARIN does this. It's a bigger issue
for ARIN as their routing registry is updated less frequently
than the RIPE routing registry.
According to our logs, the objects were not mirrored on
the RADB server until about 2.5 hours after Tomoya posted
his email (the objects were picked up from the ARIN
mirror at 05:37:42 -0500 (EST) March 2).
--Larry
When RPKI comes, is it no problem??
-tomoya
On Tue, 2 Mar 2010 19:17:45 +1100
Geoff Huston <g...@apnic.net> wrote:
|Hi,
|
|As I noted in the previous note quoted below, APNIC are
undertaking a second experiment with these two /24 routes
originated by AS 36561. These two /24s appear to be the major
attractors in the 1.0.0.0/8 space. YouTube have generously
provided assistance for this second experiment, and we are very
grateful for their help!
|
| Geoff Huston
| APNIC
|
|
|
|
|On 02/03/2010, at 6:59 PM, Tomoya Yoshida wrote:
|
|> Are these from youtube also?
|>
|> 1.1.1.0/24 *[BGP/170] 07:04:22, MED 0, localpref 100
|> AS path: 2914 3356 36561 I
|> 1.2.3.0/24 *[BGP/170] 07:01:21, MED 0, localpref 100
|> AS path: 2914 3356 36561 I
|>
|> tomoya
|>
|>
|> On Thu, 25 Feb 2010 14:34:02 +1100
|> Geoff Huston <g...@apnic.net> wrote:
|>
|> |
|> |On 25/02/2010, at 6:13 AM, Alex H. Ryu wrote:
|> |
|> |>
|> |> Today I jumped into one of our routers, and I found that 1.0.0.0/8
is
|> |> announced from AS237, which is MERIT.
|> |>
|> |>
|> |> Network Next Hop Metric LocPrf Weight
Path
|> |> *> 1.0.0.0/8 4.59.200.5 0 60 0
(65001
|> |> 65105) 3356 7018 237 i
|> |>
|> |> Is this supposed to be?
|> |> I thought 1.0.0.0/8 is allocated to APNIC.
|> |
|> |Yes, this is supposed to be. This is one of a number of
planned experiments in advertising all and selected parts of 1/8
in the coming weeks.
|> |
|> |Geoff Huston
|> |APNIC
|>
|> --
|> Tomoya Yoshida <yosh...@nttv6.jp>
|>
--
Tomoya Yoshida <yosh...@nttv6.jp>
