March 2012 - eix-wg - mailman.ripe.net

Re: [eix-wg] [address-policy-wg] 2011-05 New Draft Document Published (Safeguarding future IXPs with IPv4 space)
by Gert Doering 11 Apr '12

11 Apr '12

Dear Address-Policy WG, (cc'ing the EIX wg due to "this is where the proposal came from") after a very lifely debate in the early stages of this proposal, you have been VERY quiet in this review phase. Specifically, *no* comments have been voiced, and this is not enough for the proposal to go anywhere - so unless I see a few more comments really soon now, we'll have to extend the review phase. Please let us know whether this version 3.0 of the proposal is what you want to see become policy, or whether you oppose it. If you oppose it, please make clear whether you oppose the general idea or just specific aspects of the proposal as written now. thanks, Gert Doering, APWG chair On Tue, Mar 06, 2012 at 04:41:23PM +0100, Emilio Madaio wrote: > > Dear Colleagues, > > The text of RIPE Policy Proposal 2011-05, "Safeguarding future IXPs > with IPv4 space", has been revised based on the community feedback > received on the mailing list. We have published the new version > (version 3.0) today. > > Highlights of the changes in version 3.0 are: > > -a new punctuation is used in the first bullet point of the proposed > section 5.6.2 > > > As per RIPE document ripe-500, "Policy Development Process in RIPE", > the suggested change was not considered significant to require a new > Discussion Phase. Hence the proposal moves to the Review Phase of the > RIPE Policy Development Process. > > The draft document for the proposal has been published. The impact > analysis that was conducted for this proposal has also been published > > > You can find the full proposal and impact analysis at: > > http://www.ripe.net/ripe/policies/proposals/2011-05 > > and the draft document at: > > http://www.ripe.net/ripe/policies/proposals/2011-05/draft > > > We encourage you to read the draft document text and send any comments > to address-policy-wg(a)ripe.net before 3 April 2011. > > Regards > > Emilio Madaio > Policy Development Officer > RIPE NCC > > Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? 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

21 23

Re: [eix-wg] [address-policy-wg] 2011-05 New Draft Document Published (Safeguarding future IXPs with IPv4 space)
by Sascha Luck 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 02:36:16PM +0200, Gert Doering wrote: >Those were all in the initial discussion phase. I don't need a full >repetition of all these, but a few statements of position in the review >phase *are* helpful, to see whether people are still agreeing, even if the >text has changed somewhat between v1.0 and v3.0 :-) I'm ok with the proposal. Even "new" IXPs will be connecting existing SPs that already have IPv4 legacy space. Other new organisations will have to build ipv6-only networks eventually anyway. Withholding a /16 from those is not going to have a noticeable impact on the Internet. rgds, Sascha Luck

1 0

"advertise to all" BGP community
by Matjaž Straus Istenič 27 Mar '12

27 Mar '12

Dear group, we are putting a couple of Bird route servers with an IXP manager front-end to Slovenian internet exchange (SIX). At route servers, we are using the well known model for BGP communities: block announcement of a route to a certain peer 0:peer-as announcement of a route to a certain peer ix-as:peer-as block announcement of a route to all peers 0:ix-as announcement of a route to all peers ix-as:ix-as How do you handle the announcements with no community set? Do you request that "announcement of a route to all peers" is set in order to announce the prefixes from your IXP route servers? I will appreciate your feedback, thank you. Kind regards, Matjaž --- Matjaž Straus Istenič, Arnes http://www.arnes.si Tel: +386 1 4798-877 Fax: +386 1 4798-878 matjaz.straus(a)arnes.si MS6745-RIPE PGP 490F3B4F 2009-10-21 Fingerprint = 6172 7BF8 B0B7 1F09 47B3 AFA3 0946 1701 490F 3B4F

5 6