From mathias.westerlund at wdmab.se Tue Mar 1 08:21:06 2022 From: mathias.westerlund at wdmab.se (Mathias Westerlund) Date: Tue, 1 Mar 2022 08:21:06 +0100 Subject: [address-policy-wg] RU goverment IP revoke In-Reply-To: References: Message-ID: While i fully support ukraine in these tough times and can easily say i will do what i can against russia, i would like to remind you that there is a difference between talking about lawful sanctions and us implementing them versus outright cyber attack requests which at least i feel is not for this forum. No matter how justified. On Mon, Feb 28, 2022, 16:04 Den wrote: > Hi Jan, > > Thanks for your time, looks like other's are too busy or already at the > basement / under attack.. > > Here's what I've found: > > AS8291 The Federal Guard Service of the Russian Federation / Main > Division of Informations Resources / kremlin.ru, etc. > AS43797 The Federal Guard Service of the Russian Federation > AS42121 The Federal Guard Service of the Russian Federation > AS48552 OJSC The Russian Armed Forces Broadcasting Company ZVEZDA > AS57767 Federal State-owned Enterprise Russian Television and Radio > Broadcasting Network > AS57352 Federal State Unitary Enterprise Rossiya Segodnya > International Information Agency > AS57107 Federal State Unitary Enterprise "Russian Satellite > Communication Company" > AS57767 Federal State-owned Enterprise Russian Television and Radio > Broadcasting Network > AS59541 Federal State-owned Enterprise "Russian Television and Radio > Broadcasting Network" > AS44479 Federal State Unitary Enterprise Rossiya Segodnya > International Information Agency > AS25292 Federal State Unitary Enterprise "The Russian Television and > Radio Broadcasting Company" > AS211382 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS208075 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS201030 Federal state unitary enterprise "Public corporation for > organisation of air traffic in Russian Fede > AS198372 Federal State Unitary Enterprise "Television Technical Center > "Ostankino" > AS197969 Federal State Unitary Enterprise "Morsviazsputnik" > AS197553 Federal state unitary enterprise 'State Research Institute of > Aviation Systems' > AS197150 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS196641 Federal Unitary State Enterprise General Radio Freqency Centre > AS57724 DDOS-GUARD THAT HIDES RT.COM and others russian's broadcasting > companies > > .... > > (This list can be much longer, it's from my quick research) > > Guys, who read, please help us, please make some unexpected failures, > anyway you know what to do. > > *Let's make our work Now!* > > Thanks for all of you guys, we all want Internet with freedom and without > dictatorship! > > Love and peace for all of you guys! > > -- > > Cheers, Den > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://mailman.ripe.net/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at rfc1035.com Tue Mar 1 08:48:43 2022 From: jim at rfc1035.com (Jim Reid) Date: Tue, 1 Mar 2022 07:48:43 +0000 Subject: [address-policy-wg] RU goverment IP revoke In-Reply-To: References: Message-ID: <941A65A8-D7F9-4076-86CB-7E0D665138D7@rfc1035.com> > On 1 Mar 2022, at 07:21, Mathias Westerlund wrote: > > While i fully support ukraine in these tough times and can easily say i will do what i can against russia, i would like to remind you that there is a difference between talking about lawful sanctions and us implementing them versus outright cyber attack requests which at least i feel is not for this forum. No matter how justified. I agree 100%. The NCC *MUST* remain neutral no matter how much we oppose the attack on Ukraine. It's the start of a very slippery slope if we (for some definition of we) start taking decisions about who does and doesn't get numbering resources. Or freezing/withdrawing those that have already been allocated. [Apart from the usual sanctions when an LIR is in breach of the membership agreement, say by not paying.] Those decisions have to be taken elsewhere: ie the Dutch courts. There's no need for the NCC to intervene here. Those who want to make life difficult for the Russian government can take their own decisions about which prefixes get advertised or dropped by their routers. From mathias.westerlund at wdmab.se Tue Mar 1 08:50:30 2022 From: mathias.westerlund at wdmab.se (Mathias Westerlund) Date: Tue, 1 Mar 2022 08:50:30 +0100 Subject: [address-policy-wg] RU goverment IP revoke In-Reply-To: <941A65A8-D7F9-4076-86CB-7E0D665138D7@rfc1035.com> References: <941A65A8-D7F9-4076-86CB-7E0D665138D7@rfc1035.com> Message-ID: I agree with you. However i still feel there is the need to discuss and check what actions RIPE is supposed to take under the sanctions by EU. On Tue, Mar 1, 2022, 08:48 Jim Reid wrote: > > > > On 1 Mar 2022, at 07:21, Mathias Westerlund > wrote: > > > > While i fully support ukraine in these tough times and can easily say i > will do what i can against russia, i would like to remind you that there is > a difference between talking about lawful sanctions and us implementing > them versus outright cyber attack requests which at least i feel is not for > this forum. No matter how justified. > > I agree 100%. > > The NCC *MUST* remain neutral no matter how much we oppose the attack on > Ukraine. > > It's the start of a very slippery slope if we (for some definition of we) > start taking decisions about who does and doesn't get numbering resources. > Or freezing/withdrawing those that have already been allocated. [Apart from > the usual sanctions when an LIR is in breach of the membership agreement, > say by not paying.] Those decisions have to be taken elsewhere: ie the > Dutch courts. > > There's no need for the NCC to intervene here. Those who want to make life > difficult for the Russian government can take their own decisions about > which prefixes get advertised or dropped by their routers. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at rfc1035.com Tue Mar 1 09:09:37 2022 From: jim at rfc1035.com (Jim Reid) Date: Tue, 1 Mar 2022 08:09:37 +0000 Subject: [address-policy-wg] RU goverment IP revoke In-Reply-To: References: <941A65A8-D7F9-4076-86CB-7E0D665138D7@rfc1035.com> Message-ID: > On 1 Mar 2022, at 07:50, Mathias Westerlund wrote: > > However i still feel there is the need to discuss and check what actions RIPE is supposed to take under the sanctions by EU. I'm not so sure. If the Dutch courts or government require a certain course of action, there's little to discuss or check: do as you're told or the board and CEO go to jail for sanctions busting and/or contempt of court. BTW, it's RIPE NCC, not RIPE, that will be bound by any EU sanctions. The RIPE community has no legal identity or formal membership. RIPE NCC does. The distinction is significant. I'm sure the NCC's management and legal team will look into the EU's sanctions and advise this WG (and NCC Services? and the NCC's GM?) on how to proceed. Let's leave them to get on with that work and avoid a long, pointless debate here by amateur, wannabe lawyers. From jameskennedy001 at gmail.com Tue Mar 1 12:04:45 2022 From: jameskennedy001 at gmail.com (James Kennedy) Date: Tue, 1 Mar 2022 12:04:45 +0100 Subject: [address-policy-wg] RU goverment IP revoke In-Reply-To: References: Message-ID: Community friends, The urge for action is understandably strong but please, refrain from using this working group as a platform for targeted cyber attacks. Despite where the moral compass may point. Also this is not the most effective forum for discussing potential sanctions or exceptions for specific RIPE NCC members. I would suggest the ripe-list (www.ripe.net/ripe/mail/archives/ripe-list/) or perhaps the RIPE NCC Services WG (https://www.ripe.net/participate/ripe/wg/active-wg/services) are more appropriate for airing such concerns. Address Policy - which is the focus of this working group - is applied consistently to all RIPE NCC members. Regards, James APWG co-chair On Mon, Feb 28, 2022 at 4:03 PM Den wrote: > Hi Jan, > > Thanks for your time, looks like other's are too busy or already at the > basement / under attack.. > > Here's what I've found: > > AS8291 The Federal Guard Service of the Russian Federation / Main > Division of Informations Resources / kremlin.ru, etc. > AS43797 The Federal Guard Service of the Russian Federation > AS42121 The Federal Guard Service of the Russian Federation > AS48552 OJSC The Russian Armed Forces Broadcasting Company ZVEZDA > AS57767 Federal State-owned Enterprise Russian Television and Radio > Broadcasting Network > AS57352 Federal State Unitary Enterprise Rossiya Segodnya > International Information Agency > AS57107 Federal State Unitary Enterprise "Russian Satellite > Communication Company" > AS57767 Federal State-owned Enterprise Russian Television and Radio > Broadcasting Network > AS59541 Federal State-owned Enterprise "Russian Television and Radio > Broadcasting Network" > AS44479 Federal State Unitary Enterprise Rossiya Segodnya > International Information Agency > AS25292 Federal State Unitary Enterprise "The Russian Television and > Radio Broadcasting Company" > AS211382 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS208075 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS201030 Federal state unitary enterprise "Public corporation for > organisation of air traffic in Russian Fede > AS198372 Federal State Unitary Enterprise "Television Technical Center > "Ostankino" > AS197969 Federal State Unitary Enterprise "Morsviazsputnik" > AS197553 Federal state unitary enterprise 'State Research Institute of > Aviation Systems' > AS197150 Federal State Unitary Enterprise of the Order of the Red > Banner of Labour "Russian Broad-casting and > AS196641 Federal Unitary State Enterprise General Radio Freqency Centre > AS57724 DDOS-GUARD THAT HIDES RT.COM and others russian's broadcasting > companies > > .... > > (This list can be much longer, it's from my quick research) > > Guys, who read, please help us, please make some unexpected failures, > anyway you know what to do. > > *Let's make our work Now!* > > Thanks for all of you guys, we all want Internet with freedom and without > dictatorship! > > Love and peace for all of you guys! > > -- > > Cheers, Den > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://mailman.ripe.net/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adallara at ripe.net Thu Mar 3 15:13:53 2022 From: adallara at ripe.net (Angela Dall'Ara) Date: Thu, 3 Mar 2022 15:13:53 +0100 Subject: [address-policy-wg] New on RIPE Labs: IPv4 Allocations - Is Fairness Still the Goal? Message-ID: <0a03d5e6-fae1-ef9d-5ea1-ac0e69c7adf7@ripe.net> Dear colleagues, An interesting discussion took place last December on whether current policies and procedures for the allocation and transfer of IPv4 resources in the RIPE NCC service region are in line with the original policy intent. To help lend clarity on the issue, I give an overview of the relevant changes that have come into effect since the RIPE NCC started distributing the last /8 we received from IANA. I hope you will find this helpful. https://labs.ripe.net/author/angela_dallara/ipv4-allocations-is-fairness-still-the-goal/ Kind regards, Angela -- Angela Dall'Ara RIPE NCC Policy Officer From marcus at grmpf.org Mon Mar 7 12:32:16 2022 From: marcus at grmpf.org (Marcus Stoegbauer) Date: Mon, 07 Mar 2022 12:32:16 +0100 Subject: [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies In-Reply-To: References: <3963a1a4-6783-b06f-2fa9-d041ea28d346@ripe.net> Message-ID: Apologies for the late reply, I'm just catching up with my mailing lists.. On 27 Jan 2022, at 16:44, JORDI PALET MARTINEZ via address-policy-wg wrote: > I'm not convinced that we should "today", provide IPv4 temporary assignments, neither for conferences or experiments. > > A conference can perfectly survive today with a single IPv4 public address (or very few of them) from the ISP providing the link (even if running BGP), using 464XLAT, so the participants get dual-stack in the same way they are used to (private IPv4 addresses) and they also have global IPv6 addresses. This can be made with pure open source in a VM (if the provider doesn't have a NAT64, it can be also in the VM, in addition to the CLAT support, both using Jool, or other choices), etc. It is very well proven. A conference is not a very well defined term. I agree with your assessment for conferences like RIPE meetings, NOGs and so on. However, also events like Chaos Communication Congresses (https://events.ccc.de/congress/2019/wiki/index.php/Main_Page as an example) have the word conference in it. And those are events with >15,000 users, stretching over almost a week, where each participant is bringing multiple devices. Here you won't simply use one or even a handful of public IPv4 addresses for translation, but rather want a public IPv4 address per device. In short: I still see a need, also for shorter temporary assignments for conferences like this. Marcus -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 858 bytes Desc: OpenPGP digital signature URL: From jordi.palet at consulintel.es Mon Mar 7 13:08:30 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Mon, 07 Mar 2022 13:08:30 +0100 Subject: [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies In-Reply-To: References: <3963a1a4-6783-b06f-2fa9-d041ea28d346@ripe.net> Message-ID: <8CD7A8B6-60B9-4065-8C93-5DE688FBA0E9@consulintel.es> Hi Marcus, I don't think any RIR is in a position to reserve space for a conference/event with thousands of participants bringing their own multiple devices and allowing public addresses for each one. Even many ISPs will not be able to do that! With 464XLAT you don't really need that, and the effect "for the participant devices" is the same as having NAT or CGN, with the advantage that they will also get global IPv6 addresses (as many as they want for every device if they deliver /64 per host as per RFC8273). In section 3.4 (IPv4 Pool Size Considerations) of https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-comparison/ (which has been already submitted to the IESG for publication), you can find a simple calculation that demonstrates that a /22 (IPv4) can server, for example, over 275.000 subscribers (devices in a conference), in the worst case. Saludos, Jordi @jordipalet ?El 7/3/22 12:32, "address-policy-wg en nombre de Marcus Stoegbauer" escribi?: Apologies for the late reply, I'm just catching up with my mailing lists.. On 27 Jan 2022, at 16:44, JORDI PALET MARTINEZ via address-policy-wg wrote: > I'm not convinced that we should "today", provide IPv4 temporary assignments, neither for conferences or experiments. > > A conference can perfectly survive today with a single IPv4 public address (or very few of them) from the ISP providing the link (even if running BGP), using 464XLAT, so the participants get dual-stack in the same way they are used to (private IPv4 addresses) and they also have global IPv6 addresses. This can be made with pure open source in a VM (if the provider doesn't have a NAT64, it can be also in the VM, in addition to the CLAT support, both using Jool, or other choices), etc. It is very well proven. A conference is not a very well defined term. I agree with your assessment for conferences like RIPE meetings, NOGs and so on. However, also events like Chaos Communication Congresses (https://events.ccc.de/congress/2019/wiki/index.php/Main_Page as an example) have the word conference in it. And those are events with >15,000 users, stretching over almost a week, where each participant is bringing multiple devices. Here you won't simply use one or even a handful of public IPv4 addresses for translation, but rather want a public IPv4 address per device. In short: I still see a need, also for shorter temporary assignments for conferences like this. Marcus-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. From gert at space.net Mon Mar 7 22:35:10 2022 From: gert at space.net (Gert Doering) Date: Mon, 7 Mar 2022 22:35:10 +0100 Subject: [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies In-Reply-To: <8CD7A8B6-60B9-4065-8C93-5DE688FBA0E9@consulintel.es> References: <3963a1a4-6783-b06f-2fa9-d041ea28d346@ripe.net> <8CD7A8B6-60B9-4065-8C93-5DE688FBA0E9@consulintel.es> Message-ID: Hi, On Mon, Mar 07, 2022 at 01:08:30PM +0100, JORDI PALET MARTINEZ via address-policy-wg wrote: > I don't think any RIR is in a position to reserve space for a conference/event with thousands of participants bringing their own multiple devices and allowing public addresses for each one. Even many ISPs will not be able to do that! This is particularily the point why we have this policy. So short-lived events that need more addresses that people usually have "in stock" can still be held. (And, as you can easily see, we have at least one RIR "in a position to reserve space", as mandated by its community) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer 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: 833 bytes Desc: not available URL: From ripe-wgs.cs at schiefner.de Mon Mar 14 10:03:39 2022 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Mon, 14 Mar 2022 10:03:39 +0100 Subject: [address-policy-wg] Last call and final reminder for nominations to the 2022 Rob Blokzijl Award Message-ID: [Apologies for cross-posting to various RIPE lists] Dear Address Policy WG members - this is the last call and final reminder for nominations to the 2022 Rob Blokzijl Award that will be accepted until this Friday, 18th March, at 23:59 UTC. In seeking nominations for this prestigious award, which was created to celebrate Rob's contributions to the development of the Internet, the Award Committee (https://rob-blokzijl-foundation.org/2021/11/22/2022-award-committee/) is interested to receive nominations of those who have reflected Rob's approach in either a technical or operational capacity. Please give some consideration to nominating individuals - but also teams and groups of people! - in your own community and/or the wider industry in the RIPE region who, in your opinion, deserve to be recognised for their work to make the internet and/or internet community better. To specifically have this emphasised again after some according queries: nominations of teams and groups of people are very well possible and wished for as well in case their collective work would match the criteria of the call as laid out! The Award Committee is particularly interested to receive nominations of contributors who, in addition to their own contributions, have also supported and enabled others anywhere in the world. Also, the Award Committee would like to encourage those making nominations to consider not only the community members in the later stages of their careers or who are widely known but also those who may have contributed greatly in the springtime of their career or discreetly for the greater good or who may be considered to be part of an unrepresented group. And last but not least: those of you who previously have made a nomination other than Wilfried Woeber, the 2018 awardee, may want to consider resubmitting a nomination. The complete details of the call and the nomination process can be found at: https://rob-blokzijl-foundation.org/2021/11/25/call-for-nominations-2022/ Best wishes and kind regards Carsten (on behalf of the Award Committee) From jordi.palet at consulintel.es Wed Mar 16 10:54:10 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Wed, 16 Mar 2022 10:54:10 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals Message-ID: Hi all, In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? Regards, Jordi @jordipalet ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. From mathias.westerlund at wdmab.se Wed Mar 16 11:06:29 2022 From: mathias.westerlund at wdmab.se (=?utf-8?Q?mathias=2Ewesterlund?=) Date: Wed, 16 Mar 2022 11:06:29 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: Message-ID: Heya. while i know and understand this is a call for the original volunteers to speak up, if there is a need for more people then i would personally like to volunteer, This was something discussed before we became members but as we are an ISP and MSP aiming to be 100% IPv6 native for all our customers this lies close to my heart and i hope that if you do need more people that you could accept someone very green to RIPE but very weilling to contribute. Regards, Mathias W. On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg wrote: > > Hi all, > > In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. > > I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. > > I've not seen any discussion in the list, neither the volunteers being in touch to start work ing on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? > > > Regards, > Jordi > @jordipalet > > > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited , will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Mar 16 11:20:30 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Wed, 16 Mar 2022 11:20:30 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: Message-ID: Hi Mathias, Sorry if I didn?t make it clear: of course, is NOT restricted to any specific group or set of ?original? volunteers, anyone willing to participate must be allowed to. Regards, Jordi @jordipalet El 16/3/22, 11:06, "mathias.westerlund" escribi?: Heya. while i know and understand this is a call for the original volunteers to speak up, if there is a need for more people then i would personally like to volunteer, This was something discussed before we became members but as we are an ISP and MSP aiming to be 100% IPv6 native for all our customers this lies close to my heart and i hope that if you do need more people that you could accept someone very green to RIPE but very weilling to contribute. Regards, Mathias W. On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg wrote: Hi all, In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? Regards, Jordi @jordipalet ? ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathias.westerlund at wdmab.se Wed Mar 16 11:42:48 2022 From: mathias.westerlund at wdmab.se (=?utf-8?Q?mathias=2Ewesterlund?=) Date: Wed, 16 Mar 2022 11:42:48 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: Message-ID: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> Alright! Good to know. Do you perhaps have a pointer to the meeting notes so i can read deeper on the discussion and see what i could contribute with in more details? Or if you feel you have the time to help me catch up what has been said. Either is perfectly fine to me. On 2022-03-16 11:23, JORDI PALET MARTINEZ via address-policy-wg wrote: > > > > Hi Mathias, > > > > > > > > Sorry if I didn?t make it clear: of course, is NOT restricted to any specific group or set of ?original? volunteers, anyone willing to participate must be allowed to. > > > > > > > > > Regards, > > > > Jordi > > > > @jordipalet > > > > > > > > > > > > > > > > > > > El 16/3/22, 11:06, "mathias.westerlund" escribi?: > > > > > > > > > > > > > Heya. while i know and understand this is a call for the original volunteers to speak up, if there is a need for more people then i would personally like to volunteer, This was something discussed before we became members but as we are an ISP and MSP aiming to be 100% IPv6 native for all our customers this lies close to my heart and i hope that if you do need more people that you could accept someone very green to RIPE but very weilling to contribute. > > > > > > > > > > > > Regards, Mathias W. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg wrote: > > > > > > > Hi all, > > > > In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. > > > > I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. > > > > I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? > > > > > > Regards, > > Jordi > > @jordipalet > > > > > > > > > > > > ********************************************** > > IPv4 is over > > Are you ready for the new Internet ? > > http://www.theipv6company.com > > The IPv6 Company > > > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > > > > > > > > -- > > > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Mar 16 11:51:35 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Wed, 16 Mar 2022 11:51:35 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> Message-ID: <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> Not too much, was a short presentation: https://ripe83.ripe.net/archives/video/644/ Saludos, Jordi @jordipalet El 16/3/22, 11:43, "address-policy-wg en nombre de mathias.westerlund" escribi?: Alright! Good to know. Do you perhaps have a pointer to the meeting notes so i can read deeper on the discussion and see what i could contribute with in more details? Or if you feel you have the time to help me catch up what has been said. Either is perfectly fine to me. On 2022-03-16 11:23, JORDI PALET MARTINEZ via address-policy-wg wrote: Hi Mathias, Sorry if I didn?t make it clear: of course, is NOT restricted to any specific group or set of ?original? volunteers, anyone willing to participate must be allowed to. Regards, Jordi @jordipalet El 16/3/22, 11:06, "mathias.westerlund" escribi?: Heya. while i know and understand this is a call for the original volunteers to speak up, if there is a need for more people then i would personally like to volunteer, This was something discussed before we became members but as we are an ISP and MSP aiming to be 100% IPv6 native for all our customers this lies close to my heart and i hope that if you do need more people that you could accept someone very green to RIPE but very weilling to contribute. Regards, Mathias W. On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg wrote: Hi all, In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? Regards, Jordi @jordipalet ? ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jameskennedy001 at gmail.com Wed Mar 16 11:56:46 2022 From: jameskennedy001 at gmail.com (James Kennedy) Date: Wed, 16 Mar 2022 11:56:46 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> Message-ID: Hi, An intentionally small group of community members - in order to be agile, work efficiently, and avoid too many cooks, etc. - have already started work on the IPv6 policy review. They will provide a status update over the coming days. Other community members are encouraged and warmly welcomed to actively contribute to the review by providing their feedback and input on the mailing list. Regards, James On Wed, Mar 16, 2022 at 11:51 AM JORDI PALET MARTINEZ via address-policy-wg wrote: > Not too much, was a short presentation: > > > > > > https://ripe83.ripe.net/archives/video/644/ > > > > > > Saludos, > > Jordi > > @jordipalet > > > > > > > > El 16/3/22, 11:43, "address-policy-wg en nombre de mathias.westerlund" < > address-policy-wg-bounces at ripe.net en nombre de > mathias.westerlund at wdmab.se> escribi?: > > > > Alright! > > > > Good to know. > > Do you perhaps have a pointer to the meeting notes so i can read deeper on > the discussion and see what i could contribute with in more details? Or if > you feel you have the time to help me catch up what has been said. > > > > Either is perfectly fine to me. > > > > > > > > > > > > On 2022-03-16 11:23, JORDI PALET MARTINEZ via address-policy-wg < > address-policy-wg at ripe.net> wrote: > > Hi Mathias, > > > > Sorry if I didn?t make it clear: of course, is NOT restricted to any > specific group or set of ?original? volunteers, anyone willing to > participate must be allowed to. > > > > Regards, > > Jordi > > @jordipalet > > > > > > > > El 16/3/22, 11:06, "mathias.westerlund" > escribi?: > > > > Heya. while i know and understand this is a call for the original > volunteers to speak up, if there is a need for more people then i would > personally like to volunteer, This was something discussed before we became > members but as we are an ISP and MSP aiming to be 100% IPv6 native for all > our customers this lies close to my heart and i hope that if you do need > more people that you could accept someone very green to RIPE but very > weilling to contribute. > > > > Regards, Mathias W. > > > > > > > > > > On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg < > address-policy-wg at ripe.net> wrote: > > Hi all, > > In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. > > I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. > > I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? > > > Regards, > Jordi > @jordipalet > > > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > -- To unsubscribe from this mailing list, get a password reminder, or > change your subscription options, please visit: > https://mailman.ripe.net/ > > -- To unsubscribe from this mailing list, get a password reminder, or > change your subscription options, please visit: > https://mailman.ripe.net/ > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://mailman.ripe.net/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Mar 16 12:25:27 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Wed, 16 Mar 2022 12:25:27 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> Message-ID: <996B1DC4-4A71-476A-8DC2-8CBD22DA4B47@consulintel.es> Hi James, I was among the 3-4 volunteers that spoke up in the meeting and I knew nothing about this ?small? group. So now is the group just 2 people and how this people were ?selected?? Anyway, I don?t think it could be a problem if instead of 2, 3 or 4 we have 5 or even 10 people. We have already seen several samples of discrimination in the RIPE community since some months ago. Is this one more? Should we change the principles of openness and inclusivity? Regards, Jordi @jordipalet El 16/3/22, 11:57, "address-policy-wg en nombre de James Kennedy" escribi?: Hi, An intentionally small group of community members - in order to be agile, work efficiently, and avoid too many cooks, etc. - have already started work on the IPv6 policy review. They will provide a status update over the coming days. Other community members are encouraged and warmly welcomed to actively contribute to the review by providing their feedback and input on the mailing list. Regards, James On Wed, Mar 16, 2022 at 11:51 AM JORDI PALET MARTINEZ via address-policy-wg wrote: Not too much, was a short presentation: https://ripe83.ripe.net/archives/video/644/ Saludos, Jordi @jordipalet El 16/3/22, 11:43, "address-policy-wg en nombre de mathias.westerlund" escribi?: Alright! Good to know. Do you perhaps have a pointer to the meeting notes so i can read deeper on the discussion and see what i could contribute with in more details? Or if you feel you have the time to help me catch up what has been said. Either is perfectly fine to me. On 2022-03-16 11:23, JORDI PALET MARTINEZ via address-policy-wg wrote: Hi Mathias, Sorry if I didn?t make it clear: of course, is NOT restricted to any specific group or set of ?original? volunteers, anyone willing to participate must be allowed to. Regards, Jordi @jordipalet El 16/3/22, 11:06, "mathias.westerlund" escribi?: Heya. while i know and understand this is a call for the original volunteers to speak up, if there is a need for more people then i would personally like to volunteer, This was something discussed before we became members but as we are an ISP and MSP aiming to be 100% IPv6 native for all our customers this lies close to my heart and i hope that if you do need more people that you could accept someone very green to RIPE but very weilling to contribute. Regards, Mathias W. On 2022-03-16 10:54, JORDI PALET MARTINEZ via address-policy-wg wrote: Hi all, In the last WG meeting (at the RIPE 83), there was a brief presentation from the chairs about the possible review of IPv6 policy goals. I recall there was at least 3-4 people that volunteered (included myself), but after that we didn't get any discussion in the list or among the people that volunteered. I've not seen any discussion in the list, neither the volunteers being in touch to start working on this, so I think we must move on somehow to get the work done. Could the volunteers confirm they are still willing to participate and we can find a way to organize the work together? Regards, Jordi @jordipalet ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gert at space.net Wed Mar 16 13:04:06 2022 From: gert at space.net (Gert Doering) Date: Wed, 16 Mar 2022 13:04:06 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: <996B1DC4-4A71-476A-8DC2-8CBD22DA4B47@consulintel.es> References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> <996B1DC4-4A71-476A-8DC2-8CBD22DA4B47@consulintel.es> Message-ID: Hi, On Wed, Mar 16, 2022 at 12:25:27PM +0100, JORDI PALET MARTINEZ via address-policy-wg wrote: > We have already seen several samples of discrimination in the RIPE community since some months ago. Is this one more? Should we change the principles of openness and inclusivity? You can not force random volunteer people (with no formal power or mandate) to work with you. This has nothing to do with "inclusivity" but with "it's my choice who I spend my time with". It's also only discrimination if there is a process for joining and you are rejected because you are "Jordi", instead of generic reasoning, like "we have enough people already". (OTOH, with all these accusations being thrown around by you, I'm sure all volunteer groups will all be totally happy to have you on board, and will be making exceptions to their rules, just for you. Which would not be discriminating, of course.) Now, for everything relevant to policy decisions, this happens on the public list. If you haven't seen anything, this is because nothing has happened yet. Gert Doering -- volunteer -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer 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: 833 bytes Desc: not available URL: From den.rlir at gmail.com Wed Mar 16 13:04:48 2022 From: den.rlir at gmail.com (Den) Date: Wed, 16 Mar 2022 14:04:48 +0200 Subject: [address-policy-wg] address-policy-wg Digest, Vol 122, Issue 3 In-Reply-To: References: Message-ID: Okay, no problem, I have only the one question: - Why RIPE NCC ignores EU sanctions against Russia? -- Regards, Den 02.03.2022 13:00, address-policy-wg-request at ripe.net wrote: > Send address-policy-wg mailing list submissions to > address-policy-wg at ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ripe.net/ > or, via email, send a message with subject or body 'help' to > address-policy-wg-request at ripe.net > > You can reach the person managing the list at > address-policy-wg-owner at ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of address-policy-wg digest..." > > > Today's Topics: > > 1. Re: RU goverment IP revoke (James Kennedy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 1 Mar 2022 12:04:45 +0100 > From: James Kennedy > To:address-policy-wg at ripe.net > Subject: Re: [address-policy-wg] RU goverment IP revoke > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Community friends, > > The urge for action is understandably strong but please, refrain from using > this working group as a platform for targeted cyber attacks. Despite where > the moral compass may point. > > Also this is not the most effective forum for discussing potential > sanctions or exceptions for specific RIPE NCC members. I would suggest the > ripe-list (www.ripe.net/ripe/mail/archives/ripe-list/) or perhaps the RIPE > NCC Services WG (https://www.ripe.net/participate/ripe/wg/active-wg/services) > are more appropriate for airing such concerns. Address Policy - which is > the focus of this working group - is applied consistently to all RIPE NCC > members. > > Regards, > James > APWG co-chair > > > On Mon, Feb 28, 2022 at 4:03 PM Den wrote: > >> Hi Jan, >> >> Thanks for your time, looks like other's are too busy or already at the >> basement / under attack.. >> >> Here's what I've found: >> >> AS8291 The Federal Guard Service of the Russian Federation / Main >> Division of Informations Resources / kremlin.ru, etc. >> AS43797 The Federal Guard Service of the Russian Federation >> AS42121 The Federal Guard Service of the Russian Federation >> AS48552 OJSC The Russian Armed Forces Broadcasting Company ZVEZDA >> AS57767 Federal State-owned Enterprise Russian Television and Radio >> Broadcasting Network >> AS57352 Federal State Unitary Enterprise Rossiya Segodnya >> International Information Agency >> AS57107 Federal State Unitary Enterprise "Russian Satellite >> Communication Company" >> AS57767 Federal State-owned Enterprise Russian Television and Radio >> Broadcasting Network >> AS59541 Federal State-owned Enterprise "Russian Television and Radio >> Broadcasting Network" >> AS44479 Federal State Unitary Enterprise Rossiya Segodnya >> International Information Agency >> AS25292 Federal State Unitary Enterprise "The Russian Television and >> Radio Broadcasting Company" >> AS211382 Federal State Unitary Enterprise of the Order of the Red >> Banner of Labour "Russian Broad-casting and >> AS208075 Federal State Unitary Enterprise of the Order of the Red >> Banner of Labour "Russian Broad-casting and >> AS201030 Federal state unitary enterprise "Public corporation for >> organisation of air traffic in Russian Fede >> AS198372 Federal State Unitary Enterprise "Television Technical Center >> "Ostankino" >> AS197969 Federal State Unitary Enterprise "Morsviazsputnik" >> AS197553 Federal state unitary enterprise 'State Research Institute of >> Aviation Systems' >> AS197150 Federal State Unitary Enterprise of the Order of the Red >> Banner of Labour "Russian Broad-casting and >> AS196641 Federal Unitary State Enterprise General Radio Freqency Centre >> AS57724 DDOS-GUARD THAT HIDES RT.COM and others russian's broadcasting >> companies >> >> .... >> >> (This list can be much longer, it's from my quick research) >> >> Guys, who read, please help us, please make some unexpected failures, >> anyway you know what to do. >> >> *Let's make our work Now!* >> >> Thanks for all of you guys, we all want Internet with freedom and without >> dictatorship! >> >> Love and peace for all of you guys! >> >> -- >> >> Cheers, Den >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change >> your subscription options, please visit: >> https://mailman.ripe.net/ >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Subject: Digest Footer > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at rfc1035.com Wed Mar 16 13:13:40 2022 From: jim at rfc1035.com (Jim Reid) Date: Wed, 16 Mar 2022 12:13:40 +0000 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: References: Message-ID: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> > Why RIPE NCC ignores EU sanctions against Russia? Which specific EU sanctions do you think the NCC is ignoring? From jordi.palet at consulintel.es Wed Mar 16 13:17:16 2022 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Wed, 16 Mar 2022 13:17:16 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> <996B1DC4-4A71-476A-8DC2-8CBD22DA4B47@consulintel.es> Message-ID: <3390965A-A8DD-4487-B6F1-89912D8115CD@consulintel.es> Of course, nobody can force others to work with anyone, however this means: 1) We can't call this community anymore open, transparent and inclusive. 2) Several people not willing to work with others will create a number of groups of people working on the same or very similar things, and they we will have funny discussions when we have competing policy proposals. I don't think this is right neither good at all. Of course, in that case, the chairs will need to avoid discrimination and accept all the possible different proposals from different people, which is smarter than having a single one. And by the way, if you don't want to work with other community member(s), you should openly tell that. Also, the chairs should have made explicit that the call for volunteers was done to create different groups of people not willing to work with others, as clearly the chairs knew that some "small" group was working already on that, and they didn't even provide the opportunity to the other volunteers to participate. Regards, Jordi @jordipalet ?El 16/3/22, 13:04, "Gert Doering" escribi?: Hi, On Wed, Mar 16, 2022 at 12:25:27PM +0100, JORDI PALET MARTINEZ via address-policy-wg wrote: > We have already seen several samples of discrimination in the RIPE community since some months ago. Is this one more? Should we change the principles of openness and inclusivity? You can not force random volunteer people (with no formal power or mandate) to work with you. This has nothing to do with "inclusivity" but with "it's my choice who I spend my time with". It's also only discrimination if there is a process for joining and you are rejected because you are "Jordi", instead of generic reasoning, like "we have enough people already". (OTOH, with all these accusations being thrown around by you, I'm sure all volunteer groups will all be totally happy to have you on board, and will be making exceptions to their rules, just for you. Which would not be discriminating, of course.) Now, for everything relevant to policy decisions, this happens on the public list. If you haven't seen anything, this is because nothing has happened yet. Gert Doering -- volunteer -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. From mohta at necom830.hpcl.titech.ac.jp Wed Mar 16 13:31:53 2022 From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta) Date: Wed, 16 Mar 2022 21:31:53 +0900 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> Message-ID: <46b9c45a-5fcf-decc-2b91-25845de6706c@necom830.hpcl.titech.ac.jp> James Kennedy wrote: > An intentionally small group of community members - in order to be agile, > work efficiently, and avoid too many cooks, etc. - have already started > work on the IPv6 policy review. Agile!!! Yeah! Very reasonable goal. So, if we can't see full IPv6 deployment within a certain period of time, obviously less than a year, or, at most, 3 years, we must conclude that IPv6 inoperational. Or, are you saying that just reviewing the current policy situation requires several years of *agile* reviewing period, after which several tens of years will be wasted to modify current policy only after, in the real world, IPv6 will be fully abandoned? Then, I'm afraid RIPE is hopeless. Masataka Ohta From wusel+ml at uu.org Wed Mar 16 14:03:55 2022 From: wusel+ml at uu.org (Kai 'wusel' Siering) Date: Wed, 16 Mar 2022 14:03:55 +0100 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> Message-ID: <419b3df9-dd17-0613-a152-498e9ac349c2@uu.org> On 16.03.22 13:13, Jim Reid wrote: >> Why RIPE NCC ignores EU sanctions against Russia? > Which specific EU sanctions do you think the NCC is ignoring? Well, the SWIFT ban for certain Russian banks, circumvented via [1], springs to mind. But these things are outside the scope of APWG, as James already pointed out. [1] https://www.ripe.net/ripe/mail/archives/ncc-announce/2022-March/001555.html From gert at space.net Wed Mar 16 14:28:55 2022 From: gert at space.net (Gert Doering) Date: Wed, 16 Mar 2022 14:28:55 +0100 Subject: [address-policy-wg] address-policy-wg Digest, Vol 122, Issue 3 In-Reply-To: References: Message-ID: Hi, On Wed, Mar 16, 2022 at 02:04:48PM +0200, Den wrote: > Okay, no problem, I have only the one question: > > - Why RIPE NCC ignores EU sanctions against Russia? The "address policy WG" is the wrong place to ask about "why does the RIPE NCC something". We're not the NCC. Gert Doering -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer 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: 833 bytes Desc: not available URL: From gert at space.net Wed Mar 16 14:39:02 2022 From: gert at space.net (Gert Doering) Date: Wed, 16 Mar 2022 14:39:02 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: <46b9c45a-5fcf-decc-2b91-25845de6706c@necom830.hpcl.titech.ac.jp> References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> <46b9c45a-5fcf-decc-2b91-25845de6706c@necom830.hpcl.titech.ac.jp> Message-ID: Hi, On Wed, Mar 16, 2022 at 09:31:53PM +0900, Masataka Ohta wrote: > Or, are you saying that just reviewing the current policy situation > requires several years of *agile* reviewing period, after which > several tens of years will be wasted to modify current policy > only after, in the real world, IPv6 will be fully abandoned? The intent was to have a small group come up with something like a current policy assessment - what were the original goals? - have we succeeded in reaching them? - if not, is there something that should be done differently? - is the situation today, 25 years later, significantly different? - if yes, which goals could be adjusted? - and then, discuss consequences of these findings, in the larger group (or maybe come to the conclusion that some of the findings are just incorrect due to small-group bias) It turns out that we're all not very agile and have spent too much time with families and friends instead of working on that document, so there is nothing to present yet. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer 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: 833 bytes Desc: not available URL: From leo at vegoda.org Wed Mar 16 17:05:07 2022 From: leo at vegoda.org (Leo Vegoda) Date: Wed, 16 Mar 2022 09:05:07 -0700 Subject: [address-policy-wg] Address Policy WG Co-Chair Selection Process - 2022 Message-ID: Dear Address Policy WG, According to our WG Chair Selection process, one of the WG chairs has to step down every two years, and a new WG chair is selected by the WG. Erik Bais is the co-chair whose term ends and he has volunteered to serve again. Other nominations are also welcome. If you would like to put your name forward then you may do so. Please send your name to James Kennedy (jameskennedy001 at gmail.com) and me. Please include a short bio and your reason for applying. We will collect applications and publish them all on Monday, 25 April. The Address Policy WG will choose at RIPE 84 in Berlin. Kind regards, Leo Vegoda for the Address Policy WG Co-Chairs From ripe at liopen.fr Wed Mar 16 18:37:53 2022 From: ripe at liopen.fr (Denis Fondras) Date: Wed, 16 Mar 2022 18:37:53 +0100 Subject: [address-policy-wg] Review of IPv6 policy goals In-Reply-To: <46b9c45a-5fcf-decc-2b91-25845de6706c@necom830.hpcl.titech.ac.jp> References: <36621921-3697-41c3-a67e-542c02ff1ce3@wdm-syn-col-001> <4878B85B-8FCF-4292-B1DA-822387BE06FF@consulintel.es> <46b9c45a-5fcf-decc-2b91-25845de6706c@necom830.hpcl.titech.ac.jp> Message-ID: Hi, Le Wed, Mar 16, 2022 at 09:31:53PM +0900, Masataka Ohta a ?crit : > > So, if we can't see full IPv6 deployment within a certain period of > time, obviously less than a year, or, at most, 3 years, we must conclude > that IPv6 inoperational. > I think everyone knows you are an IPv6 opponent by now. If you have nothing more constructive or positive to add than 'IPv6 is a failure', you can refrain to send a message to this list. I am sure you have more important things to do with your life :) -- Denis Fondras / Liopen From den.rlir at gmail.com Wed Mar 16 21:30:12 2022 From: den.rlir at gmail.com (Den) Date: Wed, 16 Mar 2022 22:30:12 +0200 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> Message-ID: <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> I'm not a law-specialist, but while so many companies exits from Russia you are still doing your business there and supporting them, i.e. from Hans words "We have also informed Russian members that they do not risk closure if sanctions-related factors mean they are unable to make payment.". -- Regards, Den 16.03.2022 14:13, Jim Reid wrote: >> Why RIPE NCC ignores EU sanctions against Russia? > Which specific EU sanctions do you think the NCC is ignoring? > From matthias.merkel at staclar.com Wed Mar 16 21:37:14 2022 From: matthias.merkel at staclar.com (Matthias Merkel) Date: Wed, 16 Mar 2022 20:37:14 +0000 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> Message-ID: The sanctions don't prohibit all trade with Russia and most of the companies choosing not to continue it are doing so because they think it will help. I'm sure the RIPE NCC will not be willingly violating law here. Matthias Merkel -----Original Message----- From: address-policy-wg On Behalf Of Den Sent: Wednesday, March 16, 2022 9:30 PM To: Jim Reid Cc: address-policy-wg at ripe.net Subject: Re: [address-policy-wg] EU sanctions against Russia I'm not a law-specialist, but while so many companies exits from Russia you are still doing your business there and supporting them, i.e. from Hans words "We have also informed Russian members that they do not risk closure if sanctions-related factors mean they are unable to make payment.". -- Regards, Den 16.03.2022 14:13, Jim Reid wrote: >> Why RIPE NCC ignores EU sanctions against Russia? > Which specific EU sanctions do you think the NCC is ignoring? > -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ From den.rlir at gmail.com Thu Mar 17 21:08:12 2022 From: den.rlir at gmail.com (Den) Date: Thu, 17 Mar 2022 22:08:12 +0200 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> Message-ID: <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> In such a critical time, we see that the RIPE board decided to work with them, to support them... no comments. -- Regards, Den 16.03.2022 22:37, Matthias Merkel wrote: > The sanctions don't prohibit all trade with Russia and most of the companies choosing not to continue it are doing so because they think it will help. I'm sure the RIPE NCC will not be willingly violating law here. > > Matthias Merkel > > -----Original Message----- > From: address-policy-wg On Behalf Of Den > Sent: Wednesday, March 16, 2022 9:30 PM > To: Jim Reid > Cc: address-policy-wg at ripe.net > Subject: Re: [address-policy-wg] EU sanctions against Russia > > I'm not a law-specialist, but while so many companies exits from Russia you are still doing your business there and supporting them, i.e. from Hans words "We have also informed Russian members that they do not risk closure if sanctions-related factors mean they are unable to make payment.". > > -- > Regards, > Den > > 16.03.2022 14:13, Jim Reid wrote: >>> Why RIPE NCC ignores EU sanctions against Russia? >> Which specific EU sanctions do you think the NCC is ignoring? >> From afragkou at ripe.net Fri Mar 18 17:35:55 2022 From: afragkou at ripe.net (Athina Fragkouli) Date: Fri, 18 Mar 2022 18:35:55 +0200 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> Message-ID: <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> Dear colleagues, After the recent adoption of EU sanctions against Russia, we?ve seen some confusion about our compliance. We have published an article that explains why the RIPE NCC remains fully compliant with the latest sanctions: https://labs.ripe.net/author/athina/eu-sanctions-and-our-russian-membership/ Kind regards, Athina Fragkouli Chief Legal Officer RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: From tasic at academ.kiev.ua Sat Mar 19 06:59:48 2022 From: tasic at academ.kiev.ua (Taras Heichenko) Date: Sat, 19 Mar 2022 07:59:48 +0200 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> Message-ID: <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> > On 18 Mar 2022, at 18:35, Athina Fragkouli wrote: > > Dear colleagues, Peace. I am glad to see that RIPE NCC is legally clean. There are questions about humanism but of course this is not a cope of work of RIPE NCC. > > After the recent adoption of EU sanctions against Russia, we?ve seen some confusion about our compliance. We have published an article that explains why the RIPE NCC remains fully compliant with the latest sanctions: > > https://labs.ripe.net/author/athina/eu-sanctions-and-our-russian-membership/ > > Kind regards, > > Athina Fragkouli > Chief Legal Officer > RIPE NCC > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- Taras Heichenko tasic at academ.kiev.ua From stary.bezpiecznik at gmail.com Sat Mar 19 10:29:38 2022 From: stary.bezpiecznik at gmail.com (Stary Bezpiek) Date: Sat, 19 Mar 2022 10:29:38 +0100 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> Message-ID: W dniu 19.03.2022 o?06:59, Taras Heichenko pisze: > Peace. > > I am glad to see that RIPE NCC is legally clean. There are questions about humanism but of course this is not a cope of work of RIPE NCC. In my opinion - it is not. RIPE NCC claims to operate in accordance with its own policies, that are created by the community. Meanwhile, we have a selective treatment of Members in terms of payments without: a) RIPE NCC resolutions b) without annexes to contracts with users. c) policy change Neither the Agreement nor the existing policies allow for discretionary behavior like "this user may not pay, and others must" without formal authorization. Of course Ukraine as an attacked country can and must be treated with any aid, including exemption from payments, when possible. But it has to be passed by a resolution of the RIPE NCC ordinance. The resolution may contain one sentence: "We do not issue invoices to Ukrainian members until the end of the war." Vote: who is in favor? All? The End. On the other end is Russia, as a country that has been subject to sanctions. It should not be of our interest, that they cannot pay. In result, recognizing that Russia users may not pay, because they have "banking difficulties" means, that no one from Russia will pay. Without any consequences. Although they probably can pay. Letting go at this point is very unfair to other Members. I also have a difficult in payment because the Euro exchange rate is very high. Does it interest someone? -- Stary Bezpiecznik From leo at vegoda.org Sat Mar 19 12:59:18 2022 From: leo at vegoda.org (Leo Vegoda) Date: Sat, 19 Mar 2022 04:59:18 -0700 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> Message-ID: Hi Everyone, Discussion of the charging scheme and how it is applied falls outside the scope of the Address Policy WG. The RIPE NCC's membership has a discussion list. That is the right place to discuss this topic: https://www.ripe.net/participate/member-support/membership-mailing-lists/subscribing-to-members-discuss It is worth noting that there are active discussions of charging related topics on that list. Kind regards, Leo Vegoda for the Address Policy WG Co-Chairs On Sat, Mar 19, 2022 at 2:29 AM Stary Bezpiek wrote: > > W dniu 19.03.2022 o 06:59, Taras Heichenko pisze: > > Peace. > > > > I am glad to see that RIPE NCC is legally clean. There are questions about humanism but of course this is not a cope of work of RIPE NCC. > > In my opinion - it is not. > RIPE NCC claims to operate in accordance with its own policies, that are > created by the community. > > Meanwhile, we have a selective treatment of Members in terms of payments > without: > a) RIPE NCC resolutions > b) without annexes to contracts with users. > c) policy change > Neither the Agreement nor the existing policies allow for discretionary > behavior like "this user may not pay, and others must" without formal > authorization. > > Of course Ukraine as an attacked country can and must be treated with > any aid, including exemption from payments, when possible. But it has to > be passed by a resolution of the RIPE NCC ordinance. The resolution may > contain one sentence: "We do not issue invoices to Ukrainian members > until the end of the war." Vote: who is in favor? All? The End. > > On the other end is Russia, as a country that has been subject to > sanctions. It should not be of our interest, that they cannot pay. In > result, recognizing that Russia users may not pay, because they have > "banking difficulties" means, that no one from Russia will pay. Without > any consequences. Although they probably can pay. Letting go at this > point is very unfair to other Members. > > I also have a difficult in payment because the Euro exchange rate is > very high. Does it interest someone? > > -- > Stary Bezpiecznik > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ From gert at space.net Sat Mar 19 20:29:14 2022 From: gert at space.net (Gert Doering) Date: Sat, 19 Mar 2022 20:29:14 +0100 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> Message-ID: Hi, On Sat, Mar 19, 2022 at 10:29:38AM +0100, Stary Bezpiek wrote: > Meanwhile, we have a selective treatment of Members in terms of payments > without: [...] as has been pointed out a number of times, LIR payment issues are totally off-topic on the APWG list, and need to be addressed to the ripe-members@ list or to the board. Gert Doering -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer 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: 833 bytes Desc: not available URL: From greysticky at gmail.com Sun Mar 20 15:10:28 2022 From: greysticky at gmail.com (Serg Galat) Date: Sun, 20 Mar 2022 16:10:28 +0200 Subject: [address-policy-wg] EU sanctions against Russia In-Reply-To: References: <0BB15714-6E94-48AC-8F89-D94378A2F2C0@rfc1035.com> <3c26428a-9203-77b3-a1d6-7750a3b38132@gmail.com> <318e80f0-f5ee-402a-fe0d-cf848b4d78f7@gmail.com> <39338E98-122C-4C97-90DA-300D86F40CB8@ripe.net> <562619FF-DA30-4044-9E90-6E5FB74C0B5D@academ.kiev.ua> Message-ID: Dear Leo, Would you please say this to Athina Fragkouli. Or she can? On Sat, Mar 19, 2022 at 1:59 PM Leo Vegoda wrote: > > Hi Everyone, > > Discussion of the charging scheme and how it is applied falls outside > the scope of the Address Policy WG. > > The RIPE NCC's membership has a discussion list. That is the right > place to discuss this topic: > > https://www.ripe.net/participate/member-support/membership-mailing-lists/subscribing-to-members-discuss > > It is worth noting that there are active discussions of charging > related topics on that list. > > Kind regards, > > Leo Vegoda for the Address Policy WG Co-Chairs > > On Sat, Mar 19, 2022 at 2:29 AM Stary Bezpiek > wrote: > > > > W dniu 19.03.2022 o 06:59, Taras Heichenko pisze: > > > Peace. > > > > > > I am glad to see that RIPE NCC is legally clean. There are questions about humanism but of course this is not a cope of work of RIPE NCC. > > > > In my opinion - it is not. > > RIPE NCC claims to operate in accordance with its own policies, that are > > created by the community. > > > > Meanwhile, we have a selective treatment of Members in terms of payments > > without: > > a) RIPE NCC resolutions > > b) without annexes to contracts with users. > > c) policy change > > Neither the Agreement nor the existing policies allow for discretionary > > behavior like "this user may not pay, and others must" without formal > > authorization. > > > > Of course Ukraine as an attacked country can and must be treated with > > any aid, including exemption from payments, when possible. But it has to > > be passed by a resolution of the RIPE NCC ordinance. The resolution may > > contain one sentence: "We do not issue invoices to Ukrainian members > > until the end of the war." Vote: who is in favor? All? The End. > > > > On the other end is Russia, as a country that has been subject to > > sanctions. It should not be of our interest, that they cannot pay. In > > result, recognizing that Russia users may not pay, because they have > > "banking difficulties" means, that no one from Russia will pay. Without > > any consequences. Although they probably can pay. Letting go at this > > point is very unfair to other Members. > > > > I also have a difficult in payment because the Euro exchange rate is > > very high. Does it interest someone? > > > > -- > > Stary Bezpiecznik > > > > -- > > > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- Sergey From jameskennedy001 at gmail.com Tue Mar 29 08:51:42 2022 From: jameskennedy001 at gmail.com (James Kennedy) Date: Tue, 29 Mar 2022 08:51:42 +0200 Subject: [address-policy-wg] Policy building - call for volunteers Message-ID: Community friends, Who would like to get involved in some policy building? Putting the ?work? back into Working Group, we are seeking volunteers to follow-up on the following two RIPE Database Requirements Task Force recommendations relating to address policy. 2.1. The task force recommends that as resource holders have full responsibility over the registration of their IPv4 PA assignment(s), they are free to make assignments or not. If the community accepts this recommendation, the relevant RIPE Policies should be updated accordingly, and documenting IPv4 PA assignment(s) will stop being a policy requirement. 2.2. Following the data consistency principle, the task force also recommends resource registration requirements be applied consistently to all Internet number resources, regardless of their type or status. https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/database-requirements-task-force-recommendations https://www.ripe.net/publications/docs/ripe-767 Much of the heavy lifting has already been performed by the task force, and the recommendations have received positive feedback during previous RIPE meetings and BoFs. Please respond with your interest to this thread or directly to the Address Policy WG Co-Chairs. Regards, James APWG co-chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From jameskennedy001 at gmail.com Tue Mar 29 08:59:44 2022 From: jameskennedy001 at gmail.com (James Kennedy) Date: Tue, 29 Mar 2022 08:59:44 +0200 Subject: [address-policy-wg] Policy building - call for volunteers Message-ID: Apologies for the previous formatting :) --- Community friends, Who would like to get involved in some policy building? Putting the ?work? back into Working Group, we are seeking volunteers to follow-up on the following two RIPE Database Requirements Task Force recommendations relating to address policy. 2.1. The task force recommends that as resource holders have full responsibility over the registration of their IPv4 PA assignment(s), they are free to make assignments or not. If the community accepts this recommendation, the relevant RIPE Policies should be updated accordingly, and documenting IPv4 PA assignment(s) will stop being a policy requirement. 2.2. Following the data consistency principle, the task force also recommends resource registration requirements be applied consistently to all Internet number resources, regardless of their type or status. https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/database-requirements-task-force-recommendations https://www.ripe.net/publications/docs/ripe-767 Much of the heavy lifting has already been performed by the task force, and the recommendations have received positive feedback during previous RIPE meetings and BoFs. Please respond with your interest to this thread or directly to the Address Policy WG Co-Chairs. Regards, James APWG co-chair From ms at uakom.sk Tue Mar 29 11:50:50 2022 From: ms at uakom.sk (Martin Stanislav) Date: Tue, 29 Mar 2022 11:50:50 +0200 Subject: [address-policy-wg] Policy building - call for volunteers In-Reply-To: References: Message-ID: <20220329095050.GB17553@moon> Hi James, On Tue, Mar 29, 2022 at 08:59:44AM +0200, James Kennedy wrote: > > 2.1. The task force recommends that as resource holders have full > responsibility over the registration of their IPv4 PA assignment(s), > they are free to make assignments or not. If the community accepts > this recommendation, the relevant RIPE Policies should be updated > accordingly, and documenting IPv4 PA assignment(s) will stop being a > policy requirement. Is this line of thought that a responsibility over the registration of an aggregate IP resource implies optional documenting of a resouce subset explained somewhere? Was utilization of an aggregate resource the only reason to document details? Thank you for comments or pointers. Martin From jameskennedy001 at gmail.com Tue Mar 29 13:28:36 2022 From: jameskennedy001 at gmail.com (James Kennedy) Date: Tue, 29 Mar 2022 13:28:36 +0200 Subject: [address-policy-wg] Policy building - call for volunteers In-Reply-To: <20220329095050.GB17553@moon> References: <20220329095050.GB17553@moon> Message-ID: Hi Martin, On Tue, Mar 29, 2022 at 11:50 AM Martin Stanislav wrote: > > Hi James, > > On Tue, Mar 29, 2022 at 08:59:44AM +0200, James Kennedy wrote: > > > > 2.1. The task force recommends that as resource holders have full > > responsibility over the registration of their IPv4 PA assignment(s), > > they are free to make assignments or not. If the community accepts > > this recommendation, the relevant RIPE Policies should be updated > > accordingly, and documenting IPv4 PA assignment(s) will stop being a > > policy requirement. > > Is this line of thought that a responsibility over the registration > of an aggregate IP resource implies optional documenting of a resouce > subset explained somewhere? Was utilization of an aggregate resource > the only reason to document details? Explanation and analysis from the TF on that recommendation can be found in the archives of APWG RIPE meeting sessions: - RIPE83, agenda item F: https://ripe83.ripe.net/programme/meeting-plan/ap-wg/ - RIPE83, agenda item G: https://ripe82.ripe.net/programme/meeting-plan/ap-wg/ In the interest of being productive and moving forward with the recommendations to the next phase, we would now like to focus on getting interested volunteers to work on developing policy proposals via the PDP (Policy Development Process). There will be ample opportunity for the community to revisit and discuss any detail once again during the PDP: https://www.ripe.net/participate/policies https://www.ripe.net/publications/docs/ripe-710 Regards, James APWG co-chair