- BCOP - mailman.ripe.net

Documenting the RIPE Consensus Process
by jordi.palet＠consulintel.es 29 Oct '24

29 Oct '24

Hi all, I had a clash during the yesterday BCOP TF meeting, so looked at the slides and video online today. Regarding the "Documenting the RIPE Consensus Process”, I agree that we could do something and I will like to participate in the effort. Also I agree with the inputs from different people in the mic, but still think we can have some progress in a document that can be useful for the community. Tks! 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.

1 0

RIPE BCOP TF meeting in Prague on Monday...
by Jan Zorz - Go6 23 Oct '24

23 Oct '24

Dear BCOP TF community, We are looking forward to another BCOP TF session in Prague at RIPE89! After the report from "Documenting the best operational practices of running networks during the war (Ukraine)" topic - we'll open a discussion about if we should start documenting what our community consensus process actually is. Currently, we use bits and pieces from the IETF and other organizations, but the problem is that this is not documented anywhere and every RIPE community member may have their own version in their mind. That being said, I would like to invite all interested in this topic to the BCOP TF session at the end of Monday, so we can discuss it, figure out if we need this documented and (if yes) - maybe form a small group of people that will start working on it. https://ripe89.ripe.net/programme/meeting-plan/bcop-tf/ Cheers and thnx! Benno and Jan, BCOP TF co-chairs -- Anything that can be configured can be misconfigured. [RFC5505]

1 0

BCOP Task Force RIPE 86 - Best Operational Practices to Survive Natural Disasters or War
by Alena Muravska 19 May '24

19 May '24

Dear Colleagues, Following up from the past week's BCOP Task Force session at the RIPE 86 Meeting, I would like to report that we have completed forming a group of volunteers who will conduct series of interviews with Ukrainian operators to record their experience of running networks under extreme conditions of war. This will become a basis for a future document, current working title of which is Best Operational Practices to Survive Natural Disasters or War. We will be reporting about our progress on this mailing list and at RIPE Meetings. Kind regards, Alena Muravska

3 5

BCOP TF agenda published for RIPE 86 in Rotterdam
by Benno Overeinder 11 May '23

11 May '23

Hi all, The agenda for the BCOP TF is published on the RIPE 86 Meeting Plan, https://ripe86.ripe.net/programme/meeting-plan/bcop-tf/. Monday, 22 May 17:30 - 18:30 (UTC+2) Chaired By: Benno Overeinder, Jan Žorž A. Opening, Administrative, Global Activities [5 min] B. RIPE DNS Resolver Task Force Recommendations - Update [10 min] Shane Kerr C. Identifying and Documenting Best Practices to Survive Natural Disasters or War: Call for Action [40 min] Alena Muravska D. Open Microphone and Closing [5 min] See you all on Monday! Jan and Benno

1 0

BCOP TF meeting at RIPE86 in Rotterdam
by Jan Zorz - Go6 26 Apr '23

26 Apr '23

Dear BCOP community, We are now planning the agenda for BCOP TF meeting in Rotterdam. Any ideas or suggestions that you would like to put on the agenda and ask the community if they would help you with? Cheers, Benno and Jan

1 0

A question about RIPE-690
by Xuo Guoto 23 Jun '22

23 Jun '22

Hello all, I have a question about RIPE-690. In section 4.1.1 it says: <quote> Using a /64 prefix from a dedicated pool of IPv6 prefixes is the most common scenario and currently the best practice. A separate block of IPv6 space is allocated for the WAN links to the end customer CPEs, so that when CPE connects to the network and performs router discovery, a /64 prefix is used to number both ends of the connection. </quote> My question is that: Is the /64 prefix common for all WAN links or a separate /64 prefix is to be allotted for each WAN link? It may be obvious, but from reading the docs its not clear for me. I understand that for PD it has to be a separate prefix for each customer CPE. Apologies if this is not the right forum for asking this question. X.

3 3

Meeting of BCOP TF in Berlin @RIPE84
by Jan Zorz - Go6 26 Apr '22

26 Apr '22

Dear BCOP community, There is a possibility for BCOP TF to meet at RIPE84 in Berlin if there's interest from the community and we have at least 2 or 3 items on the agenda. We did not meet during online meetings as we felt that this TF should meet in-person and discuss how we can help each other document bect operational practices together - and now it's time again. Any ideas, proposals, work in progress? Maybe we should also discuss how to document best practices in building resilient network infrastructure that would work well during natural disasters or during the war... Cheers, Benno and Jan RIPE BCOP TF chairs

5 7

New BCOP
by Kai Bojens 15 Oct '19

15 Oct '19

Good morning, after the talk "How to Detect that Your Domains are Being Abused for ..." (which was pretty good btw) it was said that there would be a small group working on a new BCOP paper in regard to the presented topic. Would it be possible to take parts of the discussion to this mailing list? I found this topic to be very interesting and would like to follow this topic :) with best regards Kai Bojens -- Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95 E-Mail: support(a)artfiles.de | Web: http://www.artfiles.de Geschäftsführer: Harald Oltmanns | Tim Evers Eingetragen im Handelsregister Hamburg - HRB 81478

3 2

presentation "How to Detect that Your Domains are Being Abused for ..." is uploaded
by Benno Overeinder 14 Oct '19

14 Oct '19

The BCOP TF presentation "How to Detect that Your Domains are Being Abused for ..." by Karl Lovink is uploaded to the RIPE website. Best regards, -- Benno -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

RIPE 79 BCOP TF Agenda, Monday 14 October, 18:00-19:00
by Benno Overeinder 10 Oct '19

10 Oct '19

Hi all, For the upcoming RIPE 79 meeting, the BCOP TF meeting is scheduled for Monday evening, 18:00 to 19:00. The agenda for the BCOP TF meeting is: A. Opening, Administrative, Global Activities [5 min] B. How to Detect that Your Domains are Being Abused for ... -- Detecting Phishing [50 min] Karl Lovink, Belastingdienst C. Open Microphone and Closing [5 min] Cheers, -- Benno & Jan -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

Initiative to create a RIPE BCOP discussion document on proactively mitigating IoT attacks in CPE
by sandoche Balakrichenan 17 Jun '19

17 Jun '19

Dear all, The origin for this initiative came from the ICANN SSAC document on DNS and IoT : https://www.icann.org/en/system/files/files/sac-105-en.pdf As RIPE IoT chairs, we asked (in the RIPE IoT mailing list) whether we should prepare a Best Current Operational Practice (BCOP) document in RIPE scope for proactively mitigating IoT attacks. From both the Academy and the Industry, we got interests to contribute to this work. Possible contributors name can be found at the end of this mail: Thanks for your input on how to proceed further: 1. Do you think the topic is useful for the RIPE community? If yes, any guidance on how to proceed further will be appreciated. 2. Should this discussion be initiated in the RIPE IoT WG and not in the BCOP task force? 3. Anyone in this mailing list would be interested in contributing or provided references to people who will be interested to contribute? People who have already expressed interest in contributing: *From the Academy: * 1. Andrzej Duda (http://duda.imag.fr/) 2. Maciej Korczynski (http://mkorczynski.com/) *From the Industry:* 1. Ad Bresser (SPIN product manager) 2. Eliott Lear (CISCO) 3. Jacques Latour (CIRA - The Canadian Internet registry) 4. Peter Steinhauser (Embedd.com) 5. Possiblity from CZNIC (Czech Internet registry) who are involved in Turris router project Sandoche.

4 4

BCOP about CPE minimum security requirements
by JORDI PALET MARTINEZ 21 May '19

21 May '19

Hi all, Here are the links about the document I mention yesterday in the meeting, regarding the "Minimum security requirements for CPEs": https://www.lacnog.net/docs/lac-bcop-1 https://www.m3aawg.org/CPESecurityBP Also, the other relevant document "IPv6-only CPEs with IPv4-as-a-Service": https://datatracker.ietf.org/doc/rfc8585/ Regards, Jordi ********************************************** 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.

1 0

RIPE 706 Wording
by James Blessing 03 Aug '18

03 Aug '18

Hi, First of all, this is not a comment about MANRS but the published document RIPE706 and is a question of wordsmithing rather than anything else. In reference to : 3.3 Network operators who agree to the Principles and implement at least one of the Actions (though not solely the Coordination Action) can become a MANRS Participant. This entitles you to use of the MANRS badge, you will be listed on the routingmanifesto.org website, and you can contribute to this document and others like it. As I read that clause it says to make changes to RIPE706 then you *must* first be a MANRS signee, I assume the intent was to transpose the original MANRS documents with as few changes as possible, but in doing so the reference to "this document" should have been updated to point at the original version. If however, it's an intentional attempt to restrict changes to RIPE706 to a subset of the RIPE community then this is a dangerous precedent to set and we should challenge this assertion. And secondly (and maybe more importantly) we now have two documents that (the original MANRS and RIPE706) that, whilst are currently in sync have no explicit method for updating and cross checking. I thought we'd all learnt the hard way that we should always have a single source of truth... Thx J -- James Blessing 07989 039 476

2 1

RIPE-706 published: Mutually Agreed Norms for Routing Security (MANRS) Implementation Guide
by Benno Overeinder 11 Jun '18

11 Jun '18

The document Mutually Agreed Norms for Routing Security (MANRS) Implementation Guide is now published as RIPE document RIPE-706. https://www.ripe.net/publications/docs/ripe-706 Best regards, Jan Zorz & Benno Overeinder -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

Fwd: [routing-wg] Fwd: Abstract of the MANRS BCOP
by Benno Overeinder 04 Jun '18

04 Jun '18

For information to the BCOP mailing list. MANRS BCOP LC is concluded and we move forward to publish the document as a RIPE Document. Best regards, Jan Zorz & Benno Overeinder -------- Forwarded Message -------- Subject: Re: [routing-wg] Fwd: [bcop] Abstract of the MANRS BCOP Date: Mon, 4 Jun 2018 21:55:08 +0200 From: Benno Overeinder <benno(a)NLnetLabs.nl> To: routing-wg(a)ripe.net Thank you all for the discussion and feedback. >From the email thread we conclude there are no principal objections and close the LC. Best regards, Jan Zorz & Benno Overeinder On 29/05/2018 15:12, Job Snijders wrote: > On Tue, May 29, 2018 at 09:03:48AM +0300, Hank Nussbacher wrote: >> On 28/05/2018 14:53, Job Snijders wrote: >>> On Thu, May 17, 2018 at 07:16:34PM +0300, Hank Nussbacher wrote: >>>> On 17/05/2018 17:02, Benno Overeinder wrote: >>>> >>>> Maybe I'm missing it when reading the website and the BCOP but where >>>> does it state to *not *allow /25 or more specifics? >> >>> If someone registers a /25, and announces it, and the RPKI ROA >>> allows it, then what is the problem? :-) >> >> I am not talking about a registered /25. I am talking about someone >> hijacking your /24 or your /21 by announcing a bunch of /25s. > > I'm pretty sure the MANRS documentation suggests that you should not > accept & propagate hijacked prefixes (regardless of prefix length). > > Kind regards, > > Job > -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

RIPE 76 BCOP TF Agenda
by Benno Overeinder 17 May '18

17 May '18

For archival reasons we send the agenda for the BCOP TF of last Monday to the RIPE BCOP mailing list. • A. Opening, Administrative, Global activities [10 min] • B. DNS Privacy BCP [20 min] Sara Dickinson • C. Email servers on IPv6 [20 min] Sander Steffann and Jordi Palet Martinez • D. Closing -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

No BCOP TF meeting at RIPE 75, but...
by Jan Zorz - Go6 22 Oct '17

22 Oct '17

Dear BCOP community, Due to agenda scheduling challenges for this RIPE75 meeting, we'll not have a BCOP TF meeting this time... but... we'll have a "Measurements of routing health system" BOF at 18:00. This will be a proper Bar BoF, taking place today (Sunday) at The Cave bar on Mezzanine (M2) floor of Conrad hotel. Whoever is interested in this discussion is welcome to join. Cheers, Benno and Jan

1 0

Proposal for a new BCOP document...
by Jan Zorz - Go6 18 Oct '17

18 Oct '17

Dear BCOP TF community, Now when we are finished with this IPv6 prefix delegations BCOP, I would like to suggest a new topic for a new document. While traveling around the world and talking to operators - another quite generic complaint formed up as quite a popular one: "I'm running email server on IPv4, because anti-spam mechanisms works quite well on IP-reputation basis, but on IPv6 there is no such thing, therefore I'm not enabling my receiving email server on IPv6" Sooo... let's join in an effort to document the best current operational practices how to effectively run your email server op IPv6 and survive. I'm asking for volunteers here on this mailing list and I'll ask for volunteers at our Dubai meeting. We need people with operational experience running a receiving email servers on IPv6 to document the best ways how to do it. Any takers? Cheers and see you all in Dubai, Jan

2 1

RIPE-690 BCOP is now published...
by Jan Zorz - Go6 16 Oct '17

16 Oct '17

Dear BCOP community, In past year you have heard a lot about this "Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose" BCOP document draft that many of you also co-authored or contributed to - and I would like to tank you for all hard work and time, put in this BCOP. The document was today published as RIPE-690!!! https://www.ripe.net/publications/docs/ripe-690/ Congratulations!!! Cheers, Jan Zorz

1 0

Abstract of the MANRS BCOP
by Andrei Robachevsky 22 Aug '17

22 Aug '17

Hi, The final version of the MANRS BCOP has been published on the MANRS website: https://www.manrs.org/bcop/. Both a PDF and an online versions are available. However, to bring the bcop process to an official closure, chairs suggested that instead of publishing the MANRS BCOP as a RIPE document, that might be too constrained, we publish just an abstract. And once the BCOP global repository is in place, we can put it there in whatever format is most convenient. I am attaching the abstract for your review and comments. Regards, Andrei

2 1

IPv6 prefix delegation BCOP document v.7
by Jan Zorz - Go6 21 Aug '17

21 Aug '17

Dear BCOP TF, Version 7 of IPv6 prefix delegation BCOP document was issued some time ago and I would like to propose that we move forward towards making this document a stable RIPE BCP document. https://www.sinog.si/docs/draft-IPv6pd-BCOP-v7.pdf We received quite a number of comments in RIPE IPv6 WG and now it seems that v.7 of the document is satisfactory enough (judging from lack of additional comments). Should we go forward and issue a week long last call and then try to move forward together with RIPE IPv6 WG and get a document number from RIPE NCC? Cheers, Jan

3 2

Version 6 of IPv6 prefix delegations BCOP is out
by Jan Zorz - Go6 08 Aug '17

08 Aug '17

Dear RIPE BCOP TF, We received offline some good and valuable comments from MarcoH, addressed them and issued the version 6 of the document draft. https://sinog.si/docs/draft-IPv6pd-BCOP-v6.pdf Please, read and comment, if you think that we need to carry on with editing this document. If not, I would like to see if we can reach a consensus to move forward and ask RIPE staff to do the language check and publish this document as RIPE BCP. Any comments? Suggestions? For v6_pd_BCOP co-authors team, Jan Žorž

1 0

IPv6 Prefix delegation BCOP version 3 is out...
by Jan Zorz - Go6 27 Jun '17

27 Jun '17

Dear RIPE BCOP TF, After presentation at RIPE74 BCOP TF and IPv6 WG sessions we got some feedback from community over mailing list and while on stage and we addressed those comments as far as we could, resulting in version 3 of the IPv6 prefix delegations draft. To avoid sending around emails with attachment I'm providing the link where you can access the PDF file: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v3.pdf I have a feeling that after all this cycles and comments from the community - we are reaching the point when we'll have to consider calling a consensus if possible, make it a stable RIPE BCOP document and give it a number. Please, read the latest version and see if you can agree with the current text and express your support (if agree) on this mailing list, so chairs can judge if there is enough consensus on the text to maybe go into a TF last call (or maybe even skip that if clear consensus, this is not PDP process ;) ) Cheers and thnx, Jan (on behalf of the co-authors of the document)

2 1

FW: [ipv6-wg] IPv6 prefix delegation BCOP document - draft v.2 for review.
by JORDI PALET MARTINEZ 13 May '17

13 May '17

I just realized that this was not posted to the BCOP list … Inputs welcome! Regards, Jordi -----Mensaje original----- De: ipv6-wg <ipv6-wg-bounces(a)ripe.net> en nombre de Jan Zorz - Go6 <jan(a)go6.si> Responder a: <jan(a)go6.si> Fecha: jueves, 11 de mayo de 2017, 2:44 Para: "ipv6-wg(a)ripe.net" <ipv6-wg(a)ripe.net> Asunto: [ipv6-wg] IPv6 prefix delegation BCOP document - draft v.2 for review. Dear RIPE IPv6 WG, As promised at BCOP TF meeting on Monday, the co-authors present at the RIPE74 meeting gathered on Tuesday afternoon and did some editorial work, addressing majority of the comments and suggestions we got from the community based on first version of the draft. Draft version 2 is now available for reading at https://sinog.si/docs/draft-IPv6pd-BCOP-v2.pdf We'll have a short "lightning talk" in Thursday IPv6 WG session, please go and read the document (those that have enough time and energy), so we get more feedback and input for further improvements (if needed). See you all in couple of hours! For co-authors team, Jan Žorž ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

BCOP TF meeting at RIPE74 in Budapest
by Jan Zorz - Go6 24 Apr '17

24 Apr '17

Dear BCOP community, In roughly two weeks we have a BCOP TF meeting in Budapest and we would like to ask if there are presentation proposals or new ideas for BCOP documents. If so, please send them to this list or the BCOP TF co-chairs (Benno and Jan) so we can put them on the agenda. See you all in Budapest, Jan

1 0