headers
Daniel Roesen | 2 Oct 2007 07:43
Picon

Mailing list hickup

Hi,

sorry for the mailing list hickup.... Mailman had some bad day and
unfortunately it went unnoticed by myself until Gert Doering
pointed me to it, thanks for that!

List ops should be back to normal again. Apologies for the late
deliveries.

Best regards,
Daniel

--

-- 
CLUE-RIPE -- Jabber: dr <at> cluenet.de -- dr <at> IRCnet -- PGP: 0xA85C8AA0
Permalink | Reply | 0 comments |
headers
Rico -mc- Gloeckner | 5 Oct 2007 09:17
Picon

someone from Sprintv6 2001:440::?

Hello,

Is someone from Sprint on the List?  If yes, please look at the Router
listed at Hop #8, as it seems to break PMTUD.

#beginDisclaimer
Since some people do rate-limiting even on ICMP sent out for PMTUD, it
is difficult to debug at times - this analysis may be not right.
#endDisclaimer

| 7. 2001:440:1239:100d::1         0.0%    10   98.7  98.7  98.6  98.8   0.1
| 8. 2001:440:eeee:ffea::2         0.0%    10  157.3 157.4 157.2 157.7   0.2

I have the full mail of the guy who did the debugging, so if you need
further infos, ill happily forward the full mail offlist.

Greetings,
--

-- 
http://www.ukeer.de/about.html

"If it's really a supercomputer, how come the bullets don't 
 bounce off when I shoot it ?"
                --The Covert Comic
Permalink | Reply | 0 comments |
headers
Gert Doering | 8 Oct 2007 22:40
Favicon

Re: IPV6 BGP Peering

Hi,

On Thu, Sep 13, 2007 at 06:01:28PM +0300, Vadim Grinco wrote:
> I need someone to establish ipv6 over ipv4 tunnel bgp peering. I have a /32
> address allocation space I am going to announce.
> 
> I need a host in europe with a full ipv6 bgp view.

I'm not sure whether you already got an offer for an IPv6 upstream.

In general, the recommendation is "ask your native IPv4 upstream to 
provide IPv6 upstream", but I am aware that this is quite often not
possible, so using "short" tunnels (short RTTs, over well-controlled
IPv4 infrastructure) can be a viable alternative.

So who are you using as IPv4 upstreams?  I can see rdsnet.ro, so maybe
they can do something?  From the RIPE stats files, I can see 5 IPv6
allocations to .ro, so maybe someone of those is in a good position to
assist?

stats> grep RO.ipv6 *ripencc*latest        
ripencc|RO|ipv6|2001:b30::|32|20030219|allocated
ripencc|RO|ipv6|2001:1518::|32|20030723|allocated
ripencc|RO|ipv6|2001:4098::|32|20040721|allocated
ripencc|RO|ipv6|2001:4b48::|32|20050121|allocated
ripencc|RO|ipv6|2001:4d80::|32|20051018|allocated

(My main goal isn't to send you away, but to avoid setting up far-distance
tunnels if a more regional solution can be found)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bernhard Schmidt | 11 Oct 2007 02:33
Picon

Connectivity to Latin American NRENs

Hello everyone,

this is my usual whining about the sad state of the global IPv6 routing
in certain parts of the DFZ. Today's episode is about the mess one has
to cross when trying to reach most educational destinations in Latin
America as well as Canada. I've tried to reach someone responsible by
mail for the last four weeks, but failed to get any response.

There seems to be a subcontinental educational network called CLARA
(AS27750) which seems to serve as educational backbone for most if not
all Latin American NRENs, just like GEANT or Abilene. CLARA is
interconnected to both GEANT and Abilene which makes, apart from some
exceptions, IPv6 to perform about equally to IPv4 - seen from the
educational world.

However, just like e.g. Abilene used to in the beginning, CLARA does not
provide any transit to the commercial world. This is where our friends
at UNAM.MX (AS278) jump in and provide that entire CLARA cloud upstream
to the commercial world. Unfortunately, UNAM.MX itself is a tunnel shop
specialized in world sightseeing, uplinked to Lava.net (Hawaii) which is
uplinked to ChungHwa Telecom (Taiwan, maybe with some equipment in US)
uplinked to Sprint. Example path

2001:1338::/32	8767 3549 6175 17715 6435 278 18592 27750 27807 20312 i

this is a prefix holding two ccTLD nameservers (ns[12].nic.ve) with glue
in the root-zone and all other whistles and bells.

As one might imagine, the performance on this path is less than optimal.
I set up a smokeping when I started to contact UNAM and it looks rather
(Continue reading)

Permalink | Reply | 11 comments |
headers
JORDI PALET MARTINEZ | 11 Oct 2007 09:49
Picon

Re: Connectivity to Latin American NRENs

I've raised this several times in the IPv6 working group of CLARA, the need
for commercial peering. I've copied that WG, hoping that a voice different
than mine can help to convince them.

Totally agree with your points. Not having good commercial peering means
they become unreachable and this is against the CLARA objectives !

I've even offered long time ago free transit because some tier ones offered
to me for CLARA, but nothing happened.

Regards,
Jordi

> De: Bernhard Schmidt <berni <at> birkenwald.de>
> Responder a: <ipv6-ops-bounces+jordi.palet=consulintel.es <at> lists.cluenet.de>
> Fecha: Thu, 11 Oct 2007 02:33:26 +0200
> Para: <ipv6-ops <at> lists.cluenet.de>
> Asunto: Connectivity to Latin American NRENs
> 
> Hello everyone,
> 
> this is my usual whining about the sad state of the global IPv6 routing
> in certain parts of the DFZ. Today's episode is about the mess one has
> to cross when trying to reach most educational destinations in Latin
> America as well as Canada. I've tried to reach someone responsible by
> mail for the last four weeks, but failed to get any response.
> 
> There seems to be a subcontinental educational network called CLARA
> (AS27750) which seems to serve as educational backbone for most if not
> all Latin American NRENs, just like GEANT or Abilene. CLARA is
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gert Doering | 11 Oct 2007 10:20
Favicon

Re: Connectivity to Latin American NRENs

Hi,

On Thu, Oct 11, 2007 at 02:33:26AM +0200, Bernhard Schmidt wrote:
> this is my usual whining about the sad state of the global IPv6 routing
> in certain parts of the DFZ. Today's episode is about the mess one has
> to cross when trying to reach most educational destinations in Latin
> America as well as Canada. I've tried to reach someone responsible by
> mail for the last four weeks, but failed to get any response.

Next week there's the NANOG meeting in the US.

Is someone on this list who would volunteer to take this to NANOG, and
raise a stink^Wgood discussion on the topic?

(My routing table talk is there, but I myself am not - I could raise
the topic at RIPE, but I think that NANOG would be a better audience)

Gert Doering
        -- NetMaster
--

-- 
Total number of prefixes smaller than registry allocations:  122119

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
Permalink | Reply | 7 comments |
headers
Carlos Friacas | 11 Oct 2007 10:51
Picon
Favicon

Re: Connectivity to Latin American NRENs

On Thu, 11 Oct 2007, Gert Doering wrote:

> Hi,
>
> On Thu, Oct 11, 2007 at 02:33:26AM +0200, Bernhard Schmidt wrote:
>> this is my usual whining about the sad state of the global IPv6 routing
>> in certain parts of the DFZ. Today's episode is about the mess one has
>> to cross when trying to reach most educational destinations in Latin
>> America as well as Canada. I've tried to reach someone responsible by
>> mail for the last four weeks, but failed to get any response.
>
> Next week there's the NANOG meeting in the US.
>
> Is someone on this list who would volunteer to take this to NANOG, and
> raise a stink^Wgood discussion on the topic?
>
> (My routing table talk is there, but I myself am not - I could raise
> the topic at RIPE, but I think that NANOG would be a better audience)
>
> Gert Doering
>        -- NetMaster
> -- 
> Total number of prefixes smaller than registry allocations:  122119
>
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Roger Jorgensen | 11 Oct 2007 13:28
Picon

Re: Connectivity to Latin American NRENs

On Thu, 11 Oct 2007, Bernhard Schmidt wrote:
<snip>
>
> 2001:410::/32	8767 3549 6175 17715 6435 278 18592 27750 6509
>
> 		286 1273 6830 6830 6830 6830 6939 6939 6939 6939 2516 \
> 		7660 22388 11537 6509

that path can only mean that there dont exist any other reasonable routing 
toward that prefix... quite bad.

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger <at> jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------
Permalink | Reply | 1 comment |
headers
Bernhard Schmidt | 11 Oct 2007 12:59
Picon

Re: Connectivity to Latin American NRENs

On Thu, Oct 11, 2007 at 09:51:52AM +0100, Carlos Friacas wrote:

> Not sure if i've seen this in english... but last month (20th Sept) the 
> Brazilian NREN (RNP) announced that they activated IPv6 on their transit 
> connection towards Global Crossing (on 13th Sept).
> Geographically, they are a big part of South America.... :-)

That's why I wrote "most educational destinations" :-)

Maybe it is finally time for combined efforts by the large commercial
carriers to shutdown the full-table "filler-feeds" they have (for
example UPC for C&W, ANC for GBLX, I guess IIJ for Tiscali, no clue who
that is for NTT). Whoever is not a downstream customer of at least one
of them isn't globally visible, period. 

I'm not a big fan of the Tier-1/Tier-2 structure that might evolve out
of this, but at the moment I think paths like in my original posting are
worse. 

Just my two very briefly evaluated cents, I'm not too sure this is going
to work. But something finally needs to be done about people hooking up
with 3000mi tunnels expecting global reachability.

The other option would be to kill of the known full-table leaks, e.g.

6175 17715 6435
6175 2497 3257 3549 6830 6830 12401 - argh!
6939 2497 3257 6175 - oh come on, seriously?
(6939|3257) 2497 2500 2914
6939 2516 7660
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gert Doering | 11 Oct 2007 15:06
Favicon

Re: Connectivity to Latin American NRENs

Hi,

On Thu, Oct 11, 2007 at 01:28:37PM +0200, Roger Jorgensen wrote:
> On Thu, 11 Oct 2007, Bernhard Schmidt wrote:
> <snip>
> >
> >2001:410::/32	8767 3549 6175 17715 6435 278 18592 27750 6509
> >
> >		286 1273 6830 6830 6830 6830 6939 6939 6939 6939 2516 \
> >		7660 22388 11537 6509
> 
> that path can only mean that there dont exist any other reasonable routing 
> toward that prefix... quite bad.

And it means that too many networks are giving transit to other networks
without consideration what they are effecting by it.

Having *no* path would be preferreble to one of those - because then the
software will very quickly fail over to IPv4, instead of taking ages
with v6.

Gert Doering
        -- NetMaster
--

-- 
Total number of prefixes smaller than registry allocations:  122119

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
(Continue reading)

Permalink | Reply | 0 comments |

Gmane