From mschmidt at ripe.net Wed Feb 3 14:59:06 2016 From: mschmidt at ripe.net (Marco Schmidt) Date: Wed, 03 Feb 2016 14:59:06 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) Message-ID: <56B207AA.2080907@ripe.net> Dear colleagues, The draft documents for version 3.0 of the policy proposal 2015-04, "RIPE Resource Transfer Policies" have now been published, along with an impact analysis conducted by the RIPE NCC. The goal of this proposal is to create a single document with all relevant information regarding the transfer of Internet number resources. Some of the differences from version 2.0 include: - clarification in the policy text about entities that can receive a transfer - further clarification in the policy text and policy summary regarding the 24-month holding period for scarce resources You can find the full proposal and the impact analysis at: https://www.ripe.net/participate/policies/proposals/2015-04 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2015-04/draft We encourage you to read the draft document and send any comments to before 3 March 2016. Regards Marco Schmidt Policy Development Officer RIPE NCC From ebais at a2b-internet.com Wed Feb 3 18:18:58 2016 From: ebais at a2b-internet.com (Erik Bais) Date: Wed, 3 Feb 2016 18:18:58 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <56B207AA.2080907@ripe.net> References: <56B207AA.2080907@ripe.net> Message-ID: <017801d15ea6$fb563cd0$f202b670$@a2b-internet.com> Hi Marco, Thanks for the update and the work. Regards, Erik Bais -----Oorspronkelijk bericht----- Van: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Namens Marco Schmidt Verzonden: woensdag 3 februari 2016 14:59 Aan: address-policy-wg at ripe.net Onderwerp: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) Dear colleagues, The draft documents for version 3.0 of the policy proposal 2015-04, "RIPE Resource Transfer Policies" have now been published, along with an impact analysis conducted by the RIPE NCC. The goal of this proposal is to create a single document with all relevant information regarding the transfer of Internet number resources. Some of the differences from version 2.0 include: - clarification in the policy text about entities that can receive a transfer - further clarification in the policy text and policy summary regarding the 24-month holding period for scarce resources You can find the full proposal and the impact analysis at: https://www.ripe.net/participate/policies/proposals/2015-04 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2015-04/draft We encourage you to read the draft document and send any comments to before 3 March 2016. Regards Marco Schmidt Policy Development Officer RIPE NCC From gert at space.net Wed Feb 3 19:00:53 2016 From: gert at space.net (Gert Doering) Date: Wed, 3 Feb 2016 19:00:53 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <56B207AA.2080907@ripe.net> References: <56B207AA.2080907@ripe.net> Message-ID: <20160203180053.GB58491@Space.Net> Dear Working Group, On Wed, Feb 03, 2016 at 02:59:06PM +0100, Marco Schmidt wrote: > The draft documents for version 3.0 of the policy proposal 2015-04, > "RIPE Resource Transfer Policies" > have now been published, along with an impact analysis conducted by the > RIPE NCC. So this is the impact analysis you have been waiting for :-) Please read, think about, and comment [ ] yes, this makes sense, go there [ ] I agree with the general direction of having a single document, but I disagree with changing _______________, because... [ ] I think we should be organizing this differently, and totally not group the policy documents "by activity" but "by resource" (= transfer policy section in the IPv4, IPv6 and AS number policy documents) Gert Doering -- APWG chair -- 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 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From remco.vanmook at gmail.com Wed Feb 3 19:41:30 2016 From: remco.vanmook at gmail.com (Remco van Mook) Date: Wed, 3 Feb 2016 19:41:30 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160203180053.GB58491@Space.Net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> Message-ID: <4368DB76-3C21-482A-8592-D586AB9A042F@gmail.com> Hi all, (all hats off) While I am highly sympathetic to harmonising transfer policies across all resources, I object to the proposal as written. The really short reason is as follows (and I quote) [The following policy will replace: - Sections 5.5 and 6.4 in ripe-649, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" - Section 4.0 in ripe-638, "Autonomous System (AS) Number Assignment Policies" - Section 8. in ripe-655, "IPv6 Address Allocation and Assignment Policy" - ripe-644, "Policy for Inter-RIR Transfers of Internet Resources" Accordingly, these sections or policy documents will be deleted.] (end quote) Up until this policy proposal, the structure of RIPE policy documents has always been very much resource aligned, not process aligned. There's a document for IPv4, for IPv6, for ASNs. This policy proposal changes that structure in a material way, and inadvertently creates a matrix of resource-oriented and activity-oriented policies, in an attempt to harmonise and simplify. While laudable goals, this matrix created the loophole I discovered in the previous version of the policy text, and the fix to that loophole in this version is to remove most of the simplification that was introduced. This is in my opinion inherent to a matrix structure for policies, and while I can't find a new loophole in this text right now, we'll introduce the risk for similar-sized loopholes in all future policy proposals. The one in this proposal was caught. We're likely to miss others. So what's left is policy harmonisation between resources. I don't think that warrants restructuring our policies. Of course, we've already had activity-oriented policies (the inter-RIR one, mergers and closures, resources for the RIPE NCC) but those were in very specific, well-defined areas that didn't stipulate specific requirements for resources, which is where the loophole potential comes in. I'd be much more in favour of taking the proposed policy text, and merge it into the various existing resource policies instead of creating a separate document. If we DO keep it as a separate document, I must insist that instead of removing sections from other policy documents altogether, reference is made to this new policy instead. On a broader scale, perhaps it's time to look at the structure of RIPE policy as a whole. The problem is, I don't have a clue where that discussion belongs, and whether even the PDP applies to that kind of discussion :) Kind regards, Remco > On 03 Feb 2016, at 19:00 , Gert Doering wrote: > > Dear Working Group, > > On Wed, Feb 03, 2016 at 02:59:06PM +0100, Marco Schmidt wrote: >> The draft documents for version 3.0 of the policy proposal 2015-04, >> "RIPE Resource Transfer Policies" >> have now been published, along with an impact analysis conducted by the >> RIPE NCC. > > So this is the impact analysis you have been waiting for :-) > > Please read, think about, and comment > > [ ] yes, this makes sense, go there > [ ] I agree with the general direction of having a single document, but > I disagree with changing _______________, because... > [ ] I think we should be organizing this differently, and totally not > group the policy documents "by activity" but "by resource" (= transfer > policy section in the IPv4, IPv6 and AS number policy documents) > > Gert Doering > -- APWG chair > -- > 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 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From anw at artfiles.de Thu Feb 4 10:11:06 2016 From: anw at artfiles.de (Andreas Worbs) Date: Thu, 4 Feb 2016 10:11:06 +0100 Subject: [address-policy-wg] [policy-announce] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <56B2078C.3000507@ripe.net> References: <56B2078C.3000507@ripe.net> Message-ID: <56B315AA.7090306@artfiles.de> Hi, i don't know if it's not to late to comment some points in general.. I would suggest to relax the restrictions of a transfer. The restriction were introduced because there were many new LIRs who wanted to grep one of the last IPv4 subnets only to have/sell them. So i think there should be a relaxed solution for longstanding LIRs. Sure, it could be that they request their last /22 only in mind to sell it. But is it really a realistic vision?! However, a transfer within a a group of companies which belongs together should be allowed or at least it should be possible to differ from the strict policies and check the individual case. We have currently the case that we wanted to transfer our last /22 (which were allocated last march) to our 100% subsidiary in the US but it's not possible because of the restrictions. Although we already use two /24 of the /22 there. I don't expect that there will be a near-term solution but i think it's worth to think about it for the future. Am 03.02.16 um 14:58 schrieb Marco Schmidt: > Dear colleagues, > > The draft documents for version 3.0 of the policy proposal 2015-04, > "RIPE Resource Transfer Policies" > have now been published, along with an impact analysis conducted by > the RIPE NCC. > > The goal of this proposal is to create a single document with all > relevant information regarding > the transfer of Internet number resources. > > Some of the differences from version 2.0 include: > > - clarification in the policy text about entities that can receive a > transfer > - further clarification in the policy text and policy summary > regarding the 24-month holding period for scarce resources > > You can find the full proposal and the impact analysis at: > https://www.ripe.net/participate/policies/proposals/2015-04 > > And the draft documents at: > https://www.ripe.net/participate/policies/proposals/2015-04/draft > > We encourage you to read the draft document and send any comments to > before 3 March 2016. > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > -- With best regards Artfiles New Media GmbH Andreas Worbs Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95 E-Mail: support at artfiles.de | Web: http://www.artfiles.de Gesch?ftsf?hrer: Harald Oltmanns | Tim Evers Eingetragen im Handelsregister Hamburg - HRB 81478 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 522 bytes Desc: OpenPGP digital signature URL: From rgori at wirem.net Fri Feb 5 18:01:44 2016 From: rgori at wirem.net (Riccardo Gori) Date: Fri, 5 Feb 2016 18:01:44 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <4368DB76-3C21-482A-8592-D586AB9A042F@gmail.com> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <4368DB76-3C21-482A-8592-D586AB9A042F@gmail.com> Message-ID: <56B4D578.1020204@wirem.net> Hi all, I'm not approving this policy even if I share its goals. I am almost same opinion as Remco, laudable goals but difficult matter. Change a lot of procedures puts higher the risk of new loopholes and requires a big effort. Impact analysis makes me thinks everything is fine is separated documents and same goals can be reached in merging the new text in current policies. I am against this 2015-04, I would keep revised separated documents and procedures. kind regards Riccardo Il 03/02/2016 19:41, Remco van Mook ha scritto: > Hi all, > > (all hats off) > > While I am highly sympathetic to harmonising transfer policies across all resources, I object to the proposal as written. > > The really short reason is as follows (and I quote) > > [The following policy will replace: > > - Sections 5.5 and 6.4 in ripe-649, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" > - Section 4.0 in ripe-638, "Autonomous System (AS) Number Assignment Policies" > - Section 8. in ripe-655, "IPv6 Address Allocation and Assignment Policy" > - ripe-644, "Policy for Inter-RIR Transfers of Internet Resources" > > Accordingly, these sections or policy documents will be deleted.] > > (end quote) > > Up until this policy proposal, the structure of RIPE policy documents has always been very much resource aligned, not process aligned. There's a document for IPv4, for IPv6, for ASNs. This policy proposal changes that structure in a material way, and inadvertently creates a matrix of resource-oriented and activity-oriented policies, in an attempt to harmonise and simplify. > > While laudable goals, this matrix created the loophole I discovered in the previous version of the policy text, and the fix to that loophole in this version is to remove most of the simplification that was introduced. This is in my opinion inherent to a matrix structure for policies, and while I can't find a new loophole in this text right now, we'll introduce the risk for similar-sized loopholes in all future policy proposals. The one in this proposal was caught. We're likely to miss others. > > So what's left is policy harmonisation between resources. I don't think that warrants restructuring our policies. > > Of course, we've already had activity-oriented policies (the inter-RIR one, mergers and closures, resources for the RIPE NCC) but those were in very specific, well-defined areas that didn't stipulate specific requirements for resources, which is where the loophole potential comes in. > > I'd be much more in favour of taking the proposed policy text, and merge it into the various existing resource policies instead of creating a separate document. If we DO keep it as a separate document, I must insist that instead of removing sections from other policy documents altogether, reference is made to this new policy instead. > > On a broader scale, perhaps it's time to look at the structure of RIPE policy as a whole. The problem is, I don't have a clue where that discussion belongs, and whether even the PDP applies to that kind of discussion :) > > Kind regards, > > Remco > > >> On 03 Feb 2016, at 19:00 , Gert Doering wrote: >> >> Dear Working Group, >> >> On Wed, Feb 03, 2016 at 02:59:06PM +0100, Marco Schmidt wrote: >>> The draft documents for version 3.0 of the policy proposal 2015-04, >>> "RIPE Resource Transfer Policies" >>> have now been published, along with an impact analysis conducted by the >>> RIPE NCC. >> So this is the impact analysis you have been waiting for :-) >> >> Please read, think about, and comment >> >> [ ] yes, this makes sense, go there >> [ ] I agree with the general direction of having a single document, but >> I disagree with changing _______________, because... >> [ ] I think we should be organizing this differently, and totally not >> group the policy documents "by activity" but "by resource" (= transfer >> policy section in the IPv4, IPv6 and AS number policy documents) >> >> Gert Doering >> -- APWG chair >> -- >> 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 (0)89/32356-444 USt-IdNr.: DE813185279 -- Ing. Riccardo Gori e-mail: rgori at wirem.net Mobile: +39 339 8925947 Mobile: +34 602 009 437 Profile: https://it.linkedin.com/in/riccardo-gori-74201943 WIREM Fiber Revolution - Net-IT s.r.l. Via Cesare Montanari, 2 47521 Cesena (FC) Tel +39 0547 1955485 Fax +39 0547 1950285 -------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by re- plying to info at wirem.net Thank you WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC) -------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logoWirem_4cm_conR.jpg Type: image/jpeg Size: 41774 bytes Desc: not available URL: From tore at fud.no Sat Feb 6 14:54:33 2016 From: tore at fud.no (Tore Anderson) Date: Sat, 6 Feb 2016 14:54:33 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160203180053.GB58491@Space.Net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> Message-ID: <20160206145433.5c9e5f84@envy> * Gert Doering > On Wed, Feb 03, 2016 at 02:59:06PM +0100, Marco Schmidt wrote: > > The draft documents for version 3.0 of the policy proposal 2015-04, > > "RIPE Resource Transfer Policies" > > have now been published, along with an impact analysis conducted by the > > RIPE NCC. > > So this is the impact analysis you have been waiting for :-) > > Please read, think about, and comment [x] yes, this makes sense, go there I think it makes a lot of sense to consolidate all the transfer-related policies in a single document, rather than having mostly redundant/duplicated text scattered around various other documents. In my opinion, this makes the policy more approachable and easy to understand for the casual reader or resource holder [to be]. I've read through the NCC's Impact Analysis and it seems eminently sensible to me - confirming that the entire proposal is for the most part editorial, i.e., causing no major changes to transfer policy. The adjustments that do happen seem non-controversial to me. Remco suggested adding references to the new policy document in lieu of the removed sections in ripe-638, ripe-649, and ripe-655. I would not object to that. Tore From apwg at c4inet.net Sat Feb 6 19:57:43 2016 From: apwg at c4inet.net (Sascha Luck [ml]) Date: Sat, 6 Feb 2016 18:57:43 +0000 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160206145433.5c9e5f84@envy> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <20160206145433.5c9e5f84@envy> Message-ID: <20160206185743.GE3589@cilantro.c4inet.net> On Sat, Feb 06, 2016 at 02:54:33PM +0100, Tore Anderson wrote: >[x] yes, this makes sense, go there +1 However: I'd like to see a paragraph defining which resources are "scarce resources" That way, it is immediately clear which resources are covered by hold times etc, and more importantly there is a formal process by which a resource is declared "scarce" (through the PDP). The impact statement currently states: "The RIPE NCC understands "scarce resources" to include IPv4 PA, IPv4 PI and 16-bit AS Numbers. If the community declares other resources to be scarce, the list of resources for which the holding period will apply will be adjusted accordingly." This needs to be part of the policy to avoid doubt and increase clarity to both NCC personnel and resource holders. >Remco suggested adding references to the new policy document in >lieu of the removed sections in ripe-638, ripe-649, and >ripe-655. I would not object to that. Sensible addition. rgds, Sascha Luck From ebais at a2b-internet.com Sat Feb 6 20:55:45 2016 From: ebais at a2b-internet.com (Erik Bais - A2B Internet) Date: Sat, 6 Feb 2016 20:55:45 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160206185743.GE3589@cilantro.c4inet.net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <20160206145433.5c9e5f84@envy> <20160206185743.GE3589@cilantro.c4inet.net> Message-ID: <55C0E24D-D7DC-4880-940F-A1AD75DF2005@a2b-internet.com> Hi Sascha, The policy proposal states : > 2.2 Transfer Restrictions > Scarce resources, which are understood as those resources that are allocated or assigned >by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs), cannot be >transferred for 24 months from the date the resource was received by the resource holder. >This restriction also applies if the resource was received due to a change in the >organisation?s business (such as a merger or acquisition). Point 2.2 already states what is to be understood by scares resources. All RIPE NCC issued IPv4 and 16bit ASNs. That means indeed as the IA states : PI IPv4 and IPv4 PA space and 16 bit ASNs .. Is there something missing ? Regards, Erik Bais > Op 6 feb. 2016 om 19:57 heeft Sascha Luck [ml] het volgende geschreven: > >> On Sat, Feb 06, 2016 at 02:54:33PM +0100, Tore Anderson wrote: >> [x] yes, this makes sense, go there > > +1 However: I'd like to see a paragraph defining which resources are > "scarce resources" That way, it is immediately clear which > resources are covered by hold times etc, and more importantly > there is a formal process by which a resource is declared "scarce" > (through the PDP). The impact statement currently states: > > "The RIPE NCC understands "scarce resources" to include IPv4 PA, > IPv4 PI and 16-bit AS Numbers. If the community declares other > resources to be scarce, the list of resources for which the > holding period will apply will be adjusted accordingly." > > This needs to be part of the policy to avoid doubt and increase > clarity to both NCC personnel and resource holders. > >> Remco suggested adding references to the new policy document in >> lieu of the removed sections in ripe-638, ripe-649, and >> ripe-655. I would not object to that. > > Sensible addition. > rgds, > Sascha Luck > -------------- next part -------------- An HTML attachment was scrubbed... URL: From apwg at c4inet.net Sat Feb 6 21:20:07 2016 From: apwg at c4inet.net (Sascha Luck [ml]) Date: Sat, 6 Feb 2016 20:20:07 +0000 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <55C0E24D-D7DC-4880-940F-A1AD75DF2005@a2b-internet.com> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <20160206145433.5c9e5f84@envy> <20160206185743.GE3589@cilantro.c4inet.net> <55C0E24D-D7DC-4880-940F-A1AD75DF2005@a2b-internet.com> Message-ID: <20160206202007.GF3589@cilantro.c4inet.net> On Sat, Feb 06, 2016 at 08:55:45PM +0100, Erik Bais - A2B Internet wrote: >The policy proposal states : > >> 2.2 Transfer Restrictions > >> Scarce resources, which are understood as those resources that >> are allocated or assigned >by the RIPE NCC on a restricted >> basis (such as IPv4 or 16-bit ASNs), cannot be >transferred >> for 24 months from the date the resource was received by the >> resource holder. >This restriction also applies if the >> resource was received due to a change in the >> organisation???s business (such as a merger or >> acquisition). > > >Point 2.2 already states what is to be understood by scares >resources. All RIPE NCC issued IPv4 and 16bit ASNs. In that case, there is a conflict between the proposal and the impact statement. 2.2 seems to suggest that the NCC unilaterally declares a resource "scarce" and the impact statement says the Community does that - presumably through policy. Why not re-word 2.2 to be the authoritative list of "scarce" resources and any additions/rmovals can be done via the PDP? rgds, Sascha Luck From guych at btireland.net Mon Feb 8 11:10:13 2016 From: guych at btireland.net (Guy Chilton) Date: Mon, 8 Feb 2016 10:10:13 +0000 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160203180053.GB58491@Space.Net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> Message-ID: <56B86985.7010809@btireland.net> Hello, [X ] yes, this makes sense, go there I'm happy with the proposal and the approach and would also agree with Remco's suggestion of the reference in the existing documents, that would make perfect sense. Guy On 03/02/16 18:00, Gert Doering wrote: > Dear Working Group, > > On Wed, Feb 03, 2016 at 02:59:06PM +0100, Marco Schmidt wrote: >> The draft documents for version 3.0 of the policy proposal 2015-04, >> "RIPE Resource Transfer Policies" >> have now been published, along with an impact analysis conducted by the >> RIPE NCC. > > So this is the impact analysis you have been waiting for :-) > > Please read, think about, and comment > > [ ] yes, this makes sense, go there > [ ] I agree with the general direction of having a single document, but > I disagree with changing _______________, because... > [ ] I think we should be organizing this differently, and totally not > group the policy documents "by activity" but "by resource" (= transfer > policy section in the IPv4, IPv6 and AS number policy documents) > > Gert Doering > -- APWG chair > -- Guy Chilton | Network Optimisation Engineer | BT Ireland | M: +353 (0) 86 8381637 | E: guy.chilton at bt.com | This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual(s) or entity to whom they are addressed. As email can be subject to operational or technical difficulties and time delays, communications that are subject to deadlines should also be sent by post. Any unauthorised direct or indirect dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this e-mail in error, please let me know immediately on the e-mail address above and delete the e-mail from your system. Thank you for your co-operation. BT accepts no responsibility for changes to or interception of this e-mail after it was sent or for any damage to the recipient?s systems or data caused by this message or its attachments. We monitor our e-mail system, and may record your e-mails. This e-mail shall not constitute a binding contract. BT Communications Ireland Limited. Registered office: Grand Canal Plaza, Upper Grand Canal Street, Dublin 4, Registered in Ireland no 141524 being a wholly owned subsidiary of BT Group plc. Think before you print! Consider the environment before printing this email! From pk at DENIC.DE Mon Feb 8 12:18:23 2016 From: pk at DENIC.DE (Peter Koch) Date: Mon, 8 Feb 2016 12:18:23 +0100 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160203180053.GB58491@Space.Net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> Message-ID: <20160208111823.GC11379@x28.adm.denic.de> On Wed, Feb 03, 2016 at 07:00:53PM +0100, Gert Doering wrote: > [X] I think we should be organizing this differently, and totally not > group the policy documents "by activity" but "by resource" (= transfer > policy section in the IPv4, IPv6 and AS number policy documents) while I understand the desire, I believe there are better ways to "explain" things to the audience than re-grouping part of the policy documents. A non-normative introductory text on the NCC's website would be one such better way. Generally I'm always nervous when policy/legislation is "streamlined" by "just editorial changes", and also recent experience here would suggest extreme caution. Things get complicated when they are taken out of their respective context (tempus and locus). At least, the work is incomplete as proposed now, simply because the affected policies will have to be re-published with a new number and timestamp, so the (outdated) references will have to be adjusted (this includes evaluation and thus is more than a simple editorial change) and now obsolete text ought to be dealt with accordingly. The necessity to add normative references to a new omnibus document has already been mentioned. -Peter From stolpe at resilans.se Mon Feb 8 13:48:36 2016 From: stolpe at resilans.se (Daniel Stolpe) Date: Mon, 8 Feb 2016 13:48:36 +0100 (CET) Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: <20160206202007.GF3589@cilantro.c4inet.net> References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <20160206145433.5c9e5f84@envy> <20160206185743.GE3589@cilantro.c4inet.net> <55C0E24D-D7DC-4880-940F-A1AD75DF2005@a2b-internet.com> <20160206202007.GF3589@cilantro.c4inet.net> Message-ID: On Sat, 6 Feb 2016, Sascha Luck [ml] wrote: > On Sat, Feb 06, 2016 at 08:55:45PM +0100, Erik Bais - A2B Internet wrote: >> The policy proposal states : >> >> > 2.2 Transfer Restrictions >> >> > Scarce resources, which are understood as those resources that >> > are allocated or assigned >by the RIPE NCC on a restricted >> > basis (such as IPv4 or 16-bit ASNs), cannot be >transferred >> > for 24 months from the date the resource was received by the >> > resource holder. >This restriction also applies if the >> > resource was received due to a change in the >> > organisation???s business (such as a merger or >> > acquisition). >> >> >> Point 2.2 already states what is to be understood by scares >> resources. All RIPE NCC issued IPv4 and 16bit ASNs. > > In that case, there is a conflict between the proposal and the > impact statement. 2.2 seems to suggest that the NCC unilaterally declares a > resource "scarce" and the impact statement says the Community > does that - presumably through policy. > Why not re-word 2.2 to be the authoritative list of "scarce" > resources and any additions/rmovals can be done via the PDP? I agree with Sascha that if we go in this direction the therm "scarce" should be well defined in an authoritative way and also the proces for updating the list. Cheers, Daniel _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm From erik at bais.name Mon Feb 8 15:17:14 2016 From: erik at bais.name (Erik Bais) Date: Mon, 8 Feb 2016 14:17:14 +0000 Subject: [address-policy-wg] 2015-04 New Draft Documents and Impact Analysis Published (RIPE Resource Transfer Policies) In-Reply-To: References: <56B207AA.2080907@ripe.net> <20160203180053.GB58491@Space.Net> <20160206145433.5c9e5f84@envy> <20160206185743.GE3589@cilantro.c4inet.net> <55C0E24D-D7DC-4880-940F-A1AD75DF2005@a2b-internet.com> <20160206202007.GF3589@cilantro.c4inet.net> Message-ID: <862A73D42343AE49B2FC3C32FDDFE91C0161323CC6@E2010-MBX03.exchange2010.nl> Hi Sascha & Daniel, The reason for using the term "scares resource", is because we can't/shouldn't use the term "depleted'.. If one would use the term "Depleted' the NCC might say that the pool isn't completely empty yet.. so it isn't depleted yet.. Which would mean that there is, until it is really empty, no transfer restriction. ( that is a different discussion.. ) The community suggested in the last 2 RIPE meetings that the transfer restrictions should not apply for 32 bits ASN and IPv6.. The policy proposal states : > 2.2 Transfer Restrictions > Scarce resources, which are understood as those resources that are allocated or assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs), cannot be transferred for 24 months from the date the resource > was received by the resource holder. The Impact Analyses states : > Holding Period for Scarce Resources > The RIPE NCC understands ?scarce resources? to include IPv4 PA, IPv4 PI and 16-bit AS Numbers. If the community declares other resources to be scarce, the list of resources for which the holding period will apply will be adjusted accordingly. The policy proposal dictates what a scares resource is (after community discussion in the last 2 RIPE meetings) and it is the policy that is leading here.. The Impact Analyses of the RIPE NCC, is what the RIPE NCC thinks what is written and intended by the policy.. and they are re-hashing what we did and how additional 'future' scares resources might need to be defined in the future. If the community declares other resources to be scarce, the list of resources for which the holding period will apply will be adjusted accordingly.. And as that is a policy change, it should go through the PDP process. I think that what you are asking is what is already in the proposal and what you are looking for in a procedure, is already what is the used process ... If not, what are we missing ? Regards, Erik Bais From sander at steffann.nl Mon Feb 8 21:24:17 2016 From: sander at steffann.nl (Sander Steffann) Date: Mon, 8 Feb 2016 21:24:17 +0100 Subject: [address-policy-wg] Working group chair rotation 2 Message-ID: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Hello working group, A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: * age 39 * shoe size 46, usually not wearing sandals though * university degree in computer science, master on distributed systems for supporting business processes * self-employed IPv6 consultant, customers include ISPs and enterprises * run a small LISP based ISP on AS57771 * attending RIPE meetings since RIPE 49 in Manchester, 2004 (missed none) * address policy working group co-chair since RIPE 54 in Tallinn, 2007 (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) And now for the future plans * guide the working group in making good policies * maintain a good standard of communication on the mailing list * while also giving space to people with different opinions * aiming to arrive at simple and fair policies for the benefit of the whole community * and explicitly not having a personal agenda while doing so I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. Cheers, Sander Steffann (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: From zsako at iszt.hu Tue Feb 9 11:14:53 2016 From: zsako at iszt.hu (Janos Zsako) Date: Tue, 9 Feb 2016 11:14:53 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <56B9BC1D.5050702@iszt.hu> Dear all, > A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. > > So, let me start by volunteering again :) I support the nomination. I know Sander for more than 10 years. He has been very active in the AP-WG for a long time and did a good job as co-chair. I am glad he still has the energy and is willing to continue. :) Best regards, Janos From elmi at 4ever.de Tue Feb 9 11:26:39 2016 From: elmi at 4ever.de (Elmar K. Bins) Date: Tue, 9 Feb 2016 11:26:39 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <56B9BC1D.5050702@iszt.hu> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <56B9BC1D.5050702@iszt.hu> Message-ID: <20160209102639.GR27220@nbmacvieebi.local> zsako at iszt.hu (Janos Zsako) wrote: > >A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. > > > >So, let me start by volunteering again :) > > I support the nomination. I know Sander for more than 10 years. > He has been very active in the AP-WG for a long time and did a good > job as co-chair. I am glad he still has the energy and is willing to > continue. :) Well, Janos, I am not really certain Sander would be the man for the job! He is much too involved, does much too much work, keeps everybody in the loop, is competent, has shown leadership skills, is overall a very agreeable guy whom I like a lot since he appeared on the scene. I would not want him wasted and lost in the maelstrom of beeing a WG chair. Well, but maybe maybe he can survive this, too, so hell, yeah, choose the guy, he's the best and most motivated one we have for the "job". *SUPPORT* *running away now* Elmar. From jan at go6.si Tue Feb 9 14:49:47 2016 From: jan at go6.si (Jan Zorz - Go6) Date: Tue, 09 Feb 2016 14:49:47 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <20160209102639.GR27220@nbmacvieebi.local> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <56B9BC1D.5050702@iszt.hu> <20160209102639.GR27220@nbmacvieebi.local> Message-ID: <56B9EE7B.5040303@go6.si> On 09/02/16 11:26, Elmar K. Bins wrote: > zsako at iszt.hu (Janos Zsako) wrote: > >>> A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. >>> >>> So, let me start by volunteering again :) >> >> I support the nomination. I know Sander for more than 10 years. >> He has been very active in the AP-WG for a long time and did a good >> job as co-chair. I am glad he still has the energy and is willing to >> continue. :) > > Well, Janos, I am not really certain Sander would be the man for the job! > > He is much too involved, does much too much work, keeps everybody in the > loop, is competent, has shown leadership skills, is overall a very > agreeable guy whom I like a lot since he appeared on the scene. I would > not want him wasted and lost in the maelstrom of beeing a WG chair. > > Well, but maybe maybe he can survive this, too, so hell, yeah, choose > the guy, he's the best and most motivated one we have for the "job". > > *SUPPORT* > > *running away now* Elmar. > Well said, Elmar :) Adding also my support for Sander continuing being a WG co-chair. He did a great job in the past and if he's got enough energy and motivation to continue - why not ;) Let's keep good stability of the WG. Cheers, Jan From jim at rfc1035.com Tue Feb 9 14:53:18 2016 From: jim at rfc1035.com (Jim Reid) Date: Tue, 9 Feb 2016 13:53:18 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <56B9EE7B.5040303@go6.si> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <56B9BC1D.5050702@iszt.hu> <20160209102639.GR27220@nbmacvieebi.local> <56B9EE7B.5040303@go6.si> Message-ID: <79214F06-5004-4934-BDB5-BC1EA6212472@rfc1035.com> > On 9 Feb 2016, at 13:49, Jan Zorz - Go6 wrote: > > Adding also my support for Sander continuing being a WG co-chair. He did a great job in the past and if he's got enough energy and motivation to continue - why not ;) Let's keep good stability of the WG. +1 From robert.sleigh at ee.co.uk Tue Feb 9 15:00:41 2016 From: robert.sleigh at ee.co.uk (Sleigh, Robert) Date: Tue, 9 Feb 2016 14:00:41 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <79214F06-5004-4934-BDB5-BC1EA6212472@rfc1035.com> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <56B9BC1D.5050702@iszt.hu> <20160209102639.GR27220@nbmacvieebi.local> <56B9EE7B.5040303@go6.si> <79214F06-5004-4934-BDB5-BC1EA6212472@rfc1035.com> Message-ID: <679694A32AB94046931C676BEF4BA8B83E09871E@UK30S005EXS05.EEAD.EEINT.CO.UK> +1 - Sander's the man Regards Bob 07958 318592 -----Original Message----- From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Jim Reid Sent: 09 February 2016 13:53 To: Jan Zorz Cc: address-policy-wg at ripe.net Subject: Re: [address-policy-wg] Working group chair rotation 2 > On 9 Feb 2016, at 13:49, Jan Zorz - Go6 wrote: > > Adding also my support for Sander continuing being a WG co-chair. He did a great job in the past and if he's got enough energy and motivation to continue - why not ;) Let's keep good stability of the WG. +1 NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. EE Limited Registered in England and Wales Company Registered Number: 02382161 Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW. From silvia.hagen at sunny.ch Tue Feb 9 15:04:26 2016 From: silvia.hagen at sunny.ch (Silvia Hagen) Date: Tue, 9 Feb 2016 14:04:26 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: Go for it! :-) +1 -----Urspr?ngliche Nachricht----- Von: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Im Auftrag von Sander Steffann Gesendet: Montag, 8. Februar 2016 21:24 An: RIPE Address Policy Working Group Betreff: [address-policy-wg] Working group chair rotation 2 Hello working group, A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: * age 39 * shoe size 46, usually not wearing sandals though * university degree in computer science, master on distributed systems for supporting business processes * self-employed IPv6 consultant, customers include ISPs and enterprises * run a small LISP based ISP on AS57771 * attending RIPE meetings since RIPE 49 in Manchester, 2004 (missed none) * address policy working group co-chair since RIPE 54 in Tallinn, 2007 (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) And now for the future plans * guide the working group in making good policies * maintain a good standard of communication on the mailing list * while also giving space to people with different opinions * aiming to arrive at simple and fair policies for the benefit of the whole community * and explicitly not having a personal agenda while doing so I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. Cheers, Sander Steffann (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) From erik at bais.name Tue Feb 9 16:02:17 2016 From: erik at bais.name (Erik Bais) Date: Tue, 9 Feb 2016 15:02:17 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <862A73D42343AE49B2FC3C32FDDFE91C0161324476@E2010-MBX03.exchange2010.nl> Hi Sander, You have my vote and support as AP-WG Chair :) +1 Erik Bais -----Oorspronkelijk bericht----- Van: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Namens Sander Steffann Verzonden: maandag 8 februari 2016 21:24 Aan: RIPE Address Policy Working Group Onderwerp: [address-policy-wg] Working group chair rotation 2 Hello working group, A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: * age 39 * shoe size 46, usually not wearing sandals though * university degree in computer science, master on distributed systems for supporting business processes * self-employed IPv6 consultant, customers include ISPs and enterprises * run a small LISP based ISP on AS57771 * attending RIPE meetings since RIPE 49 in Manchester, 2004 (missed none) * address policy working group co-chair since RIPE 54 in Tallinn, 2007 (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) And now for the future plans * guide the working group in making good policies * maintain a good standard of communication on the mailing list * while also giving space to people with different opinions * aiming to arrive at simple and fair policies for the benefit of the whole community * and explicitly not having a personal agenda while doing so I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. Cheers, Sander Steffann (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) From ggiannou at gmail.com Tue Feb 9 18:55:28 2016 From: ggiannou at gmail.com (George Giannousopoulos) Date: Tue, 9 Feb 2016 19:55:28 +0200 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: Hello all, Although I don't know Sander personally, I really like his work in this WG. I'm glad he wants to continue as a co-chair and I support his nomination too. -- George On Mon, Feb 8, 2016 at 10:24 PM, Sander Steffann wrote: > Hello working group, > > A year has passed since we implemented our working group chair rotation > mechanism, so it is time for one of the APWG chairs to offer his place in > case the working group would like to see a change of chair. This time it is > my turn to step down, and I will do so in the APWG session at RIPE 72 in > Copenhagen. So this is the time for candidates to volunteer and make > themselves known here on the list! To be considered candidates must make > themselves know before the start of RIPE 72. > > So, let me start by volunteering again :) I would love to serve this > working group for another term as one of its chairs. A short introduction > for those who don't know me: > > * age 39 > * shoe size 46, usually not wearing sandals though > * university degree in computer science, master on distributed systems for > supporting business processes > > * self-employed IPv6 consultant, customers include ISPs and enterprises > * run a small LISP based ISP on AS57771 > > * attending RIPE meetings since RIPE 49 in Manchester, 2004 > (missed none) > > * address policy working group co-chair since RIPE 54 in Tallinn, 2007 > ( > https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) > > And now for the future plans > > * guide the working group in making good policies > > * maintain a good standard of communication on the mailing list > * while also giving space to people with different opinions > > * aiming to arrive at simple and fair policies for the benefit of the > whole community > * and explicitly not having a personal agenda while doing so > > I essentially want to use what I have learned in the last 9 years and > continue to guide the working group in always-improving ways. > > Cheers, > Sander Steffann > > (and thanks to Gert for providing a template to use when writing messages > like this: > https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) > ;) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ripe-wgs at radu-adrian.feurdean.net Tue Feb 9 23:29:56 2016 From: ripe-wgs at radu-adrian.feurdean.net (Radu-Adrian FEURDEAN) Date: Tue, 09 Feb 2016 23:29:56 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <1455056996.3301989.516714418.09B4BAD4@webmail.messagingengine.com> On Mon, Feb 8, 2016, at 21:24, Sander Steffann wrote: > So, let me start by volunteering again :) I would love to serve this > working group for another term as one of its chairs. A short introduction > for those who don't know me: +1 -- Radu-Adrian FEURDEAN fr.ccs / fr.coriolis From elvis at velea.eu Wed Feb 10 08:21:04 2016 From: elvis at velea.eu (Elvis Daniel Velea) Date: Tue, 9 Feb 2016 23:21:04 -0800 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <20160209102639.GR27220@nbmacvieebi.local> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <56B9BC1D.5050702@iszt.hu> <20160209102639.GR27220@nbmacvieebi.local> Message-ID: <56BAE4E0.5000203@velea.eu> Hi, On 2/9/16 2:26 AM, Elmar K. Bins wrote: > zsako at iszt.hu (Janos Zsako) wrote: > > > [...] >> I support the nomination. I know Sander for more than 10 years. >> He has been very active in the AP-WG for a long time and did a good >> job as co-chair. I am glad he still has the energy and is willing to >> continue. :) > Well, Janos, I am not really certain Sander would be the man for the job! > > He is much too involved, does much too much work, keeps everybody in the > loop, is competent, has shown leadership skills, is overall a very > agreeable guy whom I like a lot since he appeared on the scene. I would > not want him wasted and lost in the maelstrom of beeing a WG chair. > > Well, but maybe maybe he can survive this, too, so hell, yeah, choose > the guy, he's the best and most motivated one we have for the "job". > > *SUPPORT* > > *running away now* Elmar. > hahaha, well put. +1 for Sander from me too. Regards, Elvis From stolpe at resilans.se Wed Feb 10 14:35:13 2016 From: stolpe at resilans.se (Daniel Stolpe) Date: Wed, 10 Feb 2016 14:35:13 +0100 (CET) Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <1455056996.3301989.516714418.09B4BAD4@webmail.messagingengine.com> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <1455056996.3301989.516714418.09B4BAD4@webmail.messagingengine.com> Message-ID: On Tue, 9 Feb 2016, Radu-Adrian FEURDEAN wrote: > On Mon, Feb 8, 2016, at 21:24, Sander Steffann wrote: > >> So, let me start by volunteering again :) I would love to serve this >> working group for another term as one of its chairs. A short introduction >> for those who don't know me: > > +1 As long as you have the passion, go for it! :-) +1 Cheers, Daniel _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm From kas at kas.no Wed Feb 10 15:10:42 2016 From: kas at kas.no (Knut A. Syed) Date: Wed, 10 Feb 2016 15:10:42 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <56BB44E2.5060804@kas.no> +1 Kind Regards, Knut On 08/02/16 21:24, Sander Steffann wrote: > So, let me start by volunteering again:) I would love to serve this working group for another term as one of its chairs. From dcunningham at airspeed.ie Wed Feb 10 16:01:56 2016 From: dcunningham at airspeed.ie (Donal Cunningham) Date: Wed, 10 Feb 2016 15:01:56 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: Sander said: > So, let me start by volunteering again :) +1, with bells on. Donal. -- Senior IP Network Engineer DC323-RIPE : http://as29644.peeringdb.com/ Airspeed Telecom From mathew.newton643 at official.mod.uk Wed Feb 10 20:49:43 2016 From: mathew.newton643 at official.mod.uk (Mathew Newton) Date: Wed, 10 Feb 2016 19:49:43 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: Hi Sander, On 8 February 2016 20:24:17 GMT+00:00, Sander Steffann wrote: >I would love to serve this >working group for another term as one of its chairs. [...] >I essentially want to use what I have learned in the last 9 years and >continue to guide the working group in always-improving ways. And a great job you are doing. Full support from me for this to continue. Mathew From LIR at bva.bund.de Thu Feb 11 10:42:11 2016 From: LIR at bva.bund.de (LIR (VMA II 9)) Date: Thu, 11 Feb 2016 09:42:11 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <8508FF468849BE46A0FB0661E72BAC3617BA4B@S01KR975.intern.dir> +1 for Sander from us because we from our point of view you have done very well . Kind Regards, Annette Suedmeyer LIR de.government -----Urspr?ngliche Nachricht----- Von: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Im Auftrag von Sander Steffann Gesendet: Montag, 8. Februar 2016 21:24 An: RIPE Address Policy Working Group Betreff: [address-policy-wg] Working group chair rotation 2 Hello working group, A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: * age 39 * shoe size 46, usually not wearing sandals though * university degree in computer science, master on distributed systems for supporting business processes * self-employed IPv6 consultant, customers include ISPs and enterprises * run a small LISP based ISP on AS57771 * attending RIPE meetings since RIPE 49 in Manchester, 2004 (missed none) * address policy working group co-chair since RIPE 54 in Tallinn, 2007 (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) And now for the future plans * guide the working group in making good policies * maintain a good standard of communication on the mailing list * while also giving space to people with different opinions * aiming to arrive at simple and fair policies for the benefit of the whole community * and explicitly not having a personal agenda while doing so I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. Cheers, Sander Steffann (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) From frettled at gmail.com Thu Feb 11 14:24:04 2016 From: frettled at gmail.com (Jan Ingvoldstad) Date: Thu, 11 Feb 2016 14:24:04 +0100 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: On Mon, Feb 8, 2016 at 9:24 PM, Sander Steffann wrote: > Hello working group, > Hi there! > A year has passed since we implemented our working group chair rotation > mechanism, so it is time for one of the APWG chairs to offer his place in > case the working group would like to see a change of chair. This time it is > my turn to step down, and I will do so in the APWG session at RIPE 72 in > Copenhagen. So this is the time for candidates to volunteer and make > themselves known here on the list! To be considered candidates must make > themselves know before the start of RIPE 72. > > So, let me start by volunteering again :) I would love to serve this > working group for another term as one of its chairs. A short introduction > for those who don't know me: > Well re-volunteered! I essentially want to use what I have learned in the last 9 years and > continue to guide the working group in always-improving ways. > > I think you've done a splendid job so far, and I agree with all the positive noises being made in favour of your continued chair occupancy. That said, I do think it would be interesting if there were other candidates, even though it's a tall order to try to fill your shoes. -- Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.smyth at wirelessconnect.eu Fri Feb 12 03:50:16 2016 From: tom.smyth at wirelessconnect.eu (Tom Smyth) Date: Fri, 12 Feb 2016 02:50:16 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8508FF468849BE46A0FB0661E72BAC3617BA4B@S01KR975.intern.dir> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <8508FF468849BE46A0FB0661E72BAC3617BA4B@S01KR975.intern.dir> Message-ID: + 1 for Sander, thanks for your time and effort. On Thu, Feb 11, 2016 at 9:42 AM, LIR (VMA II 9) wrote: > +1 > > for Sander from us because we from our point of view you have done very > well . > > Kind Regards, > Annette Suedmeyer > LIR de.government > > -----Urspr?ngliche Nachricht----- > Von: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Im > Auftrag von Sander Steffann > Gesendet: Montag, 8. Februar 2016 21:24 > An: RIPE Address Policy Working Group > Betreff: [address-policy-wg] Working group chair rotation 2 > > Hello working group, > > A year has passed since we implemented our working group chair rotation > mechanism, so it is time for one of the APWG chairs to offer his place in > case the working group would like to see a change of chair. This time it is > my turn to step down, and I will do so in the APWG session at RIPE 72 in > Copenhagen. So this is the time for candidates to volunteer and make > themselves known here on the list! To be considered candidates must make > themselves know before the start of RIPE 72. > > So, let me start by volunteering again :) I would love to serve this > working group for another term as one of its chairs. A short introduction > for those who don't know me: > > * age 39 > * shoe size 46, usually not wearing sandals though > * university degree in computer science, master on distributed systems for > supporting business processes > > * self-employed IPv6 consultant, customers include ISPs and enterprises > * run a small LISP based ISP on AS57771 > > * attending RIPE meetings since RIPE 49 in Manchester, 2004 > (missed none) > > * address policy working group co-chair since RIPE 54 in Tallinn, 2007 > ( > https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) > > And now for the future plans > > * guide the working group in making good policies > > * maintain a good standard of communication on the mailing list > * while also giving space to people with different opinions > > * aiming to arrive at simple and fair policies for the benefit of the > whole community > * and explicitly not having a personal agenda while doing so > > I essentially want to use what I have learned in the last 9 years and > continue to guide the working group in always-improving ways. > > Cheers, > Sander Steffann > > (and thanks to Gert for providing a template to use when writing messages > like this: > https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) > ;) > > > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 --------------------------------- PLEASE CONSIDER THE ENVIRONMENT BEFORE YOU PRINT THIS E-MAIL This email contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify me by telephone or by electronic mail immediately. Any opinions expressed are those of the author, not the company's .This email does not constitute either offer or acceptance of any contractually binding agreement. Such offer or acceptance must be communicated in writing. You are requested to carry out your own virus check before opening any attachment. Thomas Smyth accepts no liability for any loss or damage which may be caused by malicious software or attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guych at btireland.net Fri Feb 12 09:41:41 2016 From: guych at btireland.net (Guy Chilton) Date: Fri, 12 Feb 2016 08:41:41 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <56BD9AC5.70700@btireland.net> +1 for Sander keep up the good work. Guy On 08/02/16 20:24, Sander Steffann wrote: > Hello working group, > > A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. > > So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: > > * age 39 > * shoe size 46, usually not wearing sandals though > * university degree in computer science, master on distributed systems for supporting business processes > > * self-employed IPv6 consultant, customers include ISPs and enterprises > * run a small LISP based ISP on AS57771 > > * attending RIPE meetings since RIPE 49 in Manchester, 2004 > (missed none) > > * address policy working group co-chair since RIPE 54 in Tallinn, 2007 > (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) > > And now for the future plans > > * guide the working group in making good policies > > * maintain a good standard of communication on the mailing list > * while also giving space to people with different opinions > > * aiming to arrive at simple and fair policies for the benefit of the whole community > * and explicitly not having a personal agenda while doing so > > I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. > > Cheers, > Sander Steffann > > (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) > -- Guy Chilton | Network Optimisation Engineer | BT Ireland | M: +353 (0) 86 8381637 | E: guy.chilton at bt.com | This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual(s) or entity to whom they are addressed. As email can be subject to operational or technical difficulties and time delays, communications that are subject to deadlines should also be sent by post. Any unauthorised direct or indirect dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this e-mail in error, please let me know immediately on the e-mail address above and delete the e-mail from your system. Thank you for your co-operation. BT accepts no responsibility for changes to or interception of this e-mail after it was sent or for any damage to the recipient?s systems or data caused by this message or its attachments. We monitor our e-mail system, and may record your e-mails. This e-mail shall not constitute a binding contract. BT Communications Ireland Limited. Registered office: Grand Canal Plaza, Upper Grand Canal Street, Dublin 4, Registered in Ireland no 141524 being a wholly owned subsidiary of BT Group plc. Think before you print! Consider the environment before printing this email! From adam.warren at bt.com Fri Feb 12 12:00:04 2016 From: adam.warren at bt.com (adam.warren at bt.com) Date: Fri, 12 Feb 2016 11:00:04 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <33c915560f804c0c9cc2c832c3e054d3@tpw09926dag11f.domain1.systemhost.net> Hey all? First time attendee at RIPE71 and Sander?s dedication was evident +1 for me Adam From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of George Giannousopoulos Sent: 09 February 2016 17:55 To: Sander Steffann Cc: RIPE Address Policy Working Group Subject: Re: [address-policy-wg] Working group chair rotation 2 Hello all, Although I don't know Sander personally, I really like his work in this WG. I'm glad he wants to continue as a co-chair and I support his nomination too. -- George On Mon, Feb 8, 2016 at 10:24 PM, Sander Steffann > wrote: Hello working group, A year has passed since we implemented our working group chair rotation mechanism, so it is time for one of the APWG chairs to offer his place in case the working group would like to see a change of chair. This time it is my turn to step down, and I will do so in the APWG session at RIPE 72 in Copenhagen. So this is the time for candidates to volunteer and make themselves known here on the list! To be considered candidates must make themselves know before the start of RIPE 72. So, let me start by volunteering again :) I would love to serve this working group for another term as one of its chairs. A short introduction for those who don't know me: * age 39 * shoe size 46, usually not wearing sandals though * university degree in computer science, master on distributed systems for supporting business processes * self-employed IPv6 consultant, customers include ISPs and enterprises * run a small LISP based ISP on AS57771 * attending RIPE meetings since RIPE 49 in Manchester, 2004 (missed none) * address policy working group co-chair since RIPE 54 in Tallinn, 2007 (https://www.ripe.net/participate/ripe/wg/ap/minutes/minutes-from-ripe-54) And now for the future plans * guide the working group in making good policies * maintain a good standard of communication on the mailing list * while also giving space to people with different opinions * aiming to arrive at simple and fair policies for the benefit of the whole community * and explicitly not having a personal agenda while doing so I essentially want to use what I have learned in the last 9 years and continue to guide the working group in always-improving ways. Cheers, Sander Steffann (and thanks to Gert for providing a template to use when writing messages like this: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2015-April/009659.html) ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: From modonovan at btireland.net Fri Feb 12 14:34:44 2016 From: modonovan at btireland.net (Mick O'Donovan) Date: Fri, 12 Feb 2016 13:34:44 +0000 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> Message-ID: <20160212132654.GA6011@carra.btireland.net> On Tue, Feb 09, 2016 at 07:55:28PM +0200, George Giannousopoulos wrote: > Hello all, > > Although I don't know Sander personally, I really like his work in this WG. > I'm glad he wants to continue as a co-chair and I support his nomination > too. > > -- > George > +1 to that! Like George I don't know Sander personally but want to firstly congratulate him for the work he's done to date as WG Chair and also commend him for his selfless, level headed way he has chaired the working group thus far. Mick -- Mick O'Donovan | Network Engineer | BT Ireland | Website: http://www.btireland.net Looking Glass: http://lg.as2110.net Peering Record: http://as2110.peeringdb.com AS-SET Macro: AS-BTIRE | ASN: 2110 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From sean.stuart at gmail.com Fri Feb 12 23:57:01 2016 From: sean.stuart at gmail.com (Sean Stuart) Date: Fri, 12 Feb 2016 17:57:01 -0500 Subject: [address-policy-wg] Working group chair rotation 2 In-Reply-To: <20160212132654.GA6011@carra.btireland.net> References: <8D837289-63C5-470D-ADF4-38D80D9D7EEA@steffann.nl> <20160212132654.GA6011@carra.btireland.net> Message-ID: I do know Sander, and he has been doing a fantastic job as a working group chair. I back his nomination as well. Thanks for continuing to be willing to stand in the crossfire Sander. Thanks, Sean > On Feb 12, 2016, at 8:34 AM, Mick O'Donovan wrote: > >> On Tue, Feb 09, 2016 at 07:55:28PM +0200, George Giannousopoulos wrote: >> Hello all, >> >> Although I don't know Sander personally, I really like his work in this WG. >> I'm glad he wants to continue as a co-chair and I support his nomination >> too. >> >> -- >> George > > +1 to that! > > Like George I don't know Sander personally but want to firstly > congratulate him for the work he's done to date as WG Chair and also > commend him for his selfless, level headed way he has chaired the > working group thus far. > > Mick > > -- > Mick O'Donovan | Network Engineer | BT Ireland | > Website: http://www.btireland.net > Looking Glass: http://lg.as2110.net > Peering Record: http://as2110.peeringdb.com > AS-SET Macro: AS-BTIRE | ASN: 2110