Dear colleagues,
The ENOG 2 Programme Committee (PC) has already attracted a team of
local industry peers with diverse expertise, interesting ideas and
enthusiasm, but there is still space for a few more members.
If you have something to bring to the ENOG 2 PC, it's not too late to
join. Send an email and tell us about your area of expertise by Monday,
26 September to: <meeting(a)ripe.net>
-------------------
What it Means
-------------------
- Use unique knowledge, expertise and insight to drive meeting focus
- Play an important role in shaping the meeting agenda
- Find key players in local and global Internet community to present
- Assist in reviewing presentation submissions
ENOG 2 will take place on 28-30 November 2011 at the Crowne Plaza World
Trade Center in Moscow, and is co-hosted by MSK IX and the RIPE NCC.
More information is available at:
www.enog.org
Kind regards,
Andrei Robachevsky
ENOG Programme Committee Chair
Good day, all.
All of yours, I think, knows about connectivity problem with yandex
services at 19 Aug 2011. According to comment of their IT team, it
happend when all BGP routes was mistakenly redistributed in OSPF, which
leed to memory overflow at routers like a snowball, one-by-one.
As far as I know, there is only one way to avoid it - by limiting
maximum number of OSPF routes in redistribute process (Cisco example
<http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fsoredis.html>)
at ASBR, which explicity is Single Point of Failure(SPoF). What happens
if it failed you've just read above.
So don't the respected community consider to make request for changing
RFC to avoid such SPoF in future and give possibility to limiting
maximum size of OSPF(or, wider, any IGP) routes at any OSPF-routers?
I beg my pardon if that subject are far from ENOG or my networking
skills aren't enough to do such proposal conclusion.
--
With best regards,
Dennis Yusupoff,
network engineer of
Smart-Telecom ISP
Russia, Saint-Petersburg
Dear colleagues,
Please find below a call for papers for the RIPE 63 meeting in October.
It is very important that ideas and experience from this community are
shared with the wider RIPE community, so please consider your
contribution to the RIPE 63 programme.
Regards,
Andrei Robachevsky
On behalf of the RIPE Programme Committee
RIPE 63: Call for Presentations
* To: RIPE WG Chairs wg-chairs@localhost, ripe-list@localhost
* From: RIPE NCC Meetings meeting@localhost
* Date: Thu, 01 Sep 2011 13:52:48 +0200
Dear colleagues,
RIPE 63 takes place on 31 October - 4 November 2011 in Vienna, Austria.
The RIPE Programme Committee is now seeking content proposals from the
RIPE community for the Plenary, BoF and tutorial sessions at RIPE 63
covering subjects including but not limited to:
• IPv6 deployment
• Data centre technologies
• Network and DNS operations
• Internet governance and regulatory practices
• Network and routing security
* Content delivery
* Internet peering and mobile data exchange
Submissions
------------
Content proposals must be submitted for full consideration no later than
*18 September* using the online topic submission system at:
http://meetings.ripe.net/pc/
If you have any questions or requests concerning content submissions,
please email pc@localhost.
For more information about RIPE 63, including how to register, visit:
http://ripe63.ripe.net/
Kind regards,
The RIPE Programme Committee
