I'm currently seeing on two completely independent mail platforms
incoming mails from newsletter4-bounces(a)moneycab.ws, which seem to be
out-of-office replies sent back to the mailing list and
redistributed again... you get the idea ;)
I suggest you check your smtp logs whether you or your customers are
also victims of this sender, and act accordingly if you are.
from=<newsletter4-bounces(a)moneycab.ws>, relay=ml05.ispgateway.de [126.96.36.199]
(I wouldn't assume the relay to be constant though). At least one
mailing list currently being part of this problem is:
"Swiss Leadership Forum - Newsletter vom 30.04.2012"
nice to know Swiss leadership doesn't know how to deal with buggy
exchange out of office replies :)
Hi again Swinog members,
Many thanks for the many informative replies.
Some or maybe most (random sample) of the /48s in the routing table are not PIs - needs further analysis.
Regarding the PI suggestion, what do we do with customers who will never have an own AS and will never be dual homed? Do they have to "resign" to using Provider space - with renumbering when they change Provider. Or is there another way?
I know of this document which seems to tolerate /48 prefix propagation (even if the case described is not exactly our case)
http://www.ripe.net/ripe/docs/ripe-532. Does this document mean anything to SPs out there?
From: swinog-bounces(a)lists.swinog.ch [mailto:firstname.lastname@example.org] On Behalf Of Bernhard Schmidt
Sent: Freitag, 27. April 2012 10:39
Subject: Re: [swinog] IPv6 de-aggregation
On 27.04.2012 10:09, John.Collins(a)BIT.admin.ch wrote:
> we're a LIR, we got a /32 from RIPE and we want to allocate /40s and
> /48s to customers. Only snag is that the customers will not have their
> Internet feed from us but from any Service Provider of their choice. The
> customers will have to convince their SPs (X, Y, Z) to route these "non
> X,Y,Z" or "foreign" prefixes. We're getting a lot of "raised eyebrows"
> about this. What's this about prefixes longer that /32 not being
> propagated? When I look at the IPv6 table I see:
> IPv6 Routing Table Summary - 8625 entries
> 5 local, 2 connected, 3 static, 0 RIP, 8615 BGP 0 IS-IS, 0 OSPF
> Number of prefixes:
> /0: 1, /8: 1, /10: 1, /12: 1, /16: 1, /19: 2, /20: 5, /21: 3
> /22: 5, /23: 5, /24: 7, /25: 4, /26: 9, /27: 10, /28: 31, /29: 19
> /30: 15, /31: 13, /32: 4049, /33: 97, /34: 87, /35: 93, /36: 242, /37: 7
> /38: 50, /39: 22, /40: 385, /41: 12, /42: 18, /43: 34, /44: 151, /45: 15
> /46: 75, /47: 45, /48: 3006, /49: 3, /50: 1, /52: 5, /56: 9, /64: 40
> /126: 1, /128: 45
> So where did all the /48s come from ... also one or two /40s... ??
Deaggregation and PIv6 prefixes (which are /48s usually).
> What do you think about this? If you're a SP would you route the /48s or
> /40s from the customers? What about your upstream peers?
If you were my paying customer insisting on getting a /40 or /48 from
your PA space announced I would of course do so. But that's only half of
the story, because others have to accept that. And there will be
networks that don't.
There is no real consensus on if and how much deaggregation from PA
space should be allowed. As long as that is not there, we are filtering
>/36 from PA space. And I know others do, too.
If you absolutely need to do this, make sure you announce the covering
/32 somewhere. And make sure you do everything possible to prove the
validity of those routes (proper route6-objects, maybe RPKI ROA, ...)
swinog mailing list
Hi SWINOG members,
we're a LIR, we got a /32 from RIPE and we want to allocate /40s and /48s to customers. Only snag is that the customers will not have their Internet feed from us but from any Service Provider of their choice. The customers will have to convince their SPs (X, Y, Z) to route these "non X,Y,Z" or "foreign" prefixes. We're getting a lot of "raised eyebrows" about this. What's this about prefixes longer that /32 not being propagated? When I look at the IPv6 table I see:
IPv6 Routing Table Summary - 8625 entries
5 local, 2 connected, 3 static, 0 RIP, 8615 BGP 0 IS-IS, 0 OSPF
Number of prefixes:
/0: 1, /8: 1, /10: 1, /12: 1, /16: 1, /19: 2, /20: 5, /21: 3
/22: 5, /23: 5, /24: 7, /25: 4, /26: 9, /27: 10, /28: 31, /29: 19
/30: 15, /31: 13, /32: 4049, /33: 97, /34: 87, /35: 93, /36: 242, /37: 7
/38: 50, /39: 22, /40: 385, /41: 12, /42: 18, /43: 34, /44: 151, /45: 15
/46: 75, /47: 45, /48: 3006, /49: 3, /50: 1, /52: 5, /56: 9, /64: 40
/126: 1, /128: 45
So where did all the /48s come from ... also one or two /40s... ??
What do you think about this? If you're a SP would you route the /48s or /40s from the customers? What about your upstream peers?
Thanks in advance for your answers.
Eidgenössisches Finanzdepartement EFD
Bundesamt für Informatik und Telekommunikation BIT
Netzplanung und Engineering
We currently face an excessive amount of open/closing connections on our webservers (dozends of servers showing the same thing) and it is going to all different domains and different files, looks like massive connection aborts going on.
Does anyone know if a large ADSL/Cableprovider is having problems? We do not see packet drops at our Firewalls at all
Dear list members
Thanks to all the participants who have already filled out the survey and given valuable information.
Those who have not done so yet, we kindly ask them to fill it out by this Friday April 27. We highly appreciate your time and answers. The more answers, the more representative of the Swiss landscape the analysis will be. Here's the survey link: https://www.surveymonkey.com/s/SR7NRTG
Some of you have stated interest in presenting at our next member event on May 14 in Zurich, but forgot to leave their contact information. If this happened to you, pls contact us at info at swissipv6council.ch. Pls note, that we will treat your information strictly confidential unless we have a personal agreement with you.
Thanks again for your time and we hope to see you on May 14, whether you are presenting or simply participating, we would be happy to welcome you. And also don't forget to register for the party on June 6!
Here's the link: http://www.swissipv6council.ch/de/events
Looking forward to seeing you
Anyone interested in rackspace at Equinix 2? We have a rack there which
is no longer needed. I'm currently searching for a next tenant
(Nachmieter). Please contact me offlist.
together with the Informatikdienste of ETH Zurich we are organizing
four Perl courses with Damian Conway (probably the worlds most
well known, entertaining, instructive and knowledgable Perl
7 May 2012 Object-Oriented Design In Perl
8 May 2012 API Design For Perl
9/10 May 2012 Test-Driven Development in Perl
11 May 2012 Optimizing Your Perl Development
These are brand-new courses that have never been held before.
for details and registration info.
In addition, Damian will give a special evening seminar:
8 May 2012 Fun with Dead Languages
Attendance is free, but registration is required. See
http://www.digicomp.ch/opentuesday for more infos.
Damian first came to prominence as the winner of the 1998, 1999,
and 2000 Larry Wall Awards for Practical Utility. He has been a
member of the technical committee for The Perl Conference and a
columnist for former "The Perl Journal". He is a keynote speaker at
many Open Source conferences, author of the books "Object Oriented
Perl" and "Perl Best Practices", and co-author of "Perl Hacks" and
of numerous well-known software modules including:
Parse::RecDescent and Regexp::Grammars (sophisticated parsing
In addition to his work as Perl instructor and consultant he works
closely together with Larry Wall on the definition of Perl 6.
Fritz Zaucker and Tobi Oetiker
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi(a)oetiker.ch ++41 62 775 9902 / sb: -9900