- Ripe-list-unmoderated - mailman.ripe.net

BondingShouldBeFree Open-source Network Aggregation & Redundancy Solution
by Chester A. Unal 21 May '26

21 May '26

Hello everyone. Apologies if this is not the appropriate place to post. I have written an open-source network bonding solution with intent to have it become the gold standard of network bonding using MPTCP. This post includes all the details: https://forum.openwrt.org/t/bondingshouldbefree-open-source-network-aggrega… I'm looking for ISPs and any other parties interested to deploy it and give me feedback. Cheers. Chester Arinc

1 0

Contactos reales y verificados de empresas interesadas en tus servicios
by Impulsamail 20 May '26

20 May '26

Recibe leads verificados de empresas interesadas en tus servicios para que tu equipo comercial trabaje oportunidades reales y no listados fríos. Leads verificados para empresas Tus comerciales deberían estar cerrando ventas, no buscando clientes. Te entregamos leads verificados de empresas interesadas en tus servicios para que tu equipo comercial deje la prospección en frío y se centre en vender. Solicitar información Cuéntanos qué tipo de cliente buscas y te indicamos cómo enfocar la captación. Solicitar información 678 572 973 info(a)18-impulsamail.com Por qué interesa Tres ventajas claras para que tu equipo comercial gane tiempo y foco. Ahorra tiempo Menos horas buscando empresas para llamar. Mejor oportunidad Hablas con empresas interesadas en tus servicios. Más foco en vender Tu equipo comercial trabaja oportunidades reales. No son listados fríos. Recibes leads verificados listos para abrir conversaciones más útiles. Confianza y continuidad Solución pensada para empresas, con foco en oportunidades comerciales reales y contacto directo para valorar encaje. Un saludo, Equipo Impulsamail Contacto directo Llámanos o escríbenos y te contamos cómo enfocar la captación. 678 572 973 info(a)18-impulsamail.com Si no desea seguir recibiendo información de nuestra parte, pulse aquí. Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

1 0

Business Funding Available
by mayenziwe＠digitise.co.zw 20 May '26

20 May '26

Hello Dear, Do you have a project or business in need of funding? I partner with investors who support viable opportunities. If you’re interested or know someone who may benefit, I’d be happy to share more details. Best regards, Alberto Vincenzo

1 0

Constanze
by constanze buerger 20 May '26

20 May '26

Good morning everyone, Unfortunately, I won’t be able to attend RIPE 92, as I started a new position in April. I’m still continuing my work in the NRO Number Council / ASO AC with pleasure, and Andrei Robachevsky and Hervé Clément will support you on site on behalf of the NRO NC. Wishing you all a great and successful meeting — I’ll miss you. See you soon, Constanze

1 0

Constanze
by constanze buerger 20 May '26

20 May '26

Good morning to you all. I regret to inform you that I will be unable to attend Ripe 92, as I commenced a new position in April. I am confident that I will be able to join you in Sofia and I extend my best wishes for a successful and enjoyable event. I will miss you. See you soon. Constanze

1 0

Actualización crédito formación bonificable de 2026
by Natalia P. 20 May '26

20 May '26

| | | | Buenas tardes, Recordamos que vuestra empresa dispone de un **crédito anual de formación para empleados** , aplicable mediante el sistema de bonificaciones de FUNDAE. Asimismo, os informamos de que ya se han actualizado los **créditos finales de formación correspondientes al ejercicio 2026** , que podrán utilizarse antes de finalizar el año. ¿Queréis retomar la inscripción de vuestros empleados en los **Cursos 100% Bonificables**? Si lo deseáis, podemos indicaros sin compromiso el **crédito de formación** disponible para vuestra empresa y ayudaros a seleccionar las acciones formativas más adecuadas según vuestras necesidades. Quedamos a vuestra disposición para ampliar información o facilitaros la inscripción. Un cordial saludo,**Natalia P.** Directora del Departamento de Formación Bonificable FOESCO – Formación Estatal Continua **Información legal** FOESCO – Formación Estatal Continua es una entidad dedicada a la formación dirigida a empresas y trabajadores en activo, mediante programas formativos susceptibles de bonificación a través de la Fundación Estatal para la Formación en el Empleo (FUNDAE), conforme a la Ley 30/2015. --- | | | [Darme de baja](https://foescgestion.acmtrk.com/unsubscribe/3780825/51c6f94fd24a3b674… --- ![imagen](https://images.acmtrk.com/images/acumbamail_BSbNFj2idFWKqph7ucQK/d6025891-02ab-484c-944c-992185f964af%202.png) --- ![](https://foescgestion.acmtrk.com/pixel/tracking/51c6f94fd24a3b674aad614c18890c8c/)

1 0

Re: Quick Call Meeting Request ---------------------- Ripe List
by jasonsmithbts740＠gmail.com 19 May '26

19 May '26

Hey, Ripe List Just following up to see if you'd be interested in reviewing our accounting service samples and pricing details. Best, Jason Smith Sent: Friday, January 9, 2026 To:- "ripe-list(a)ripe.net" Subject: Re: Join Us - Event Hi, Ripe List we help businesses reduce workload with reliable bookkeeping and tax preparation support. Would you be open to reviewing our sample work and pricing? Regards, Jason Smith

1 0

Cliente Santander Officebank,confirme su identidad para mantener el acceso activo.
by Santander Empresas Officebanking 18 May '26

18 May '26

Verificación obligatoria *{box-sizing:border-box;margin:0;padding:0;} body,td,a{-webkit-text-size-adjust:100%;-ms-text-size-adjust:100%;} img{border:0;outline:none;text-decoration:none;display:block;-ms-interpolation-mode:bicubic;} a[x-apple-data-detectors]{color:inherit!important;text-decoration:none!important;} u #body a{color:inherit;text-decoration:none;} #MessageViewBody a{color:inherit;text-decoration:none;} body{ background:#f0f0f0; font-family:-apple-system,BlinkMacSystemFont,'Segoe UI','Helvetica Neue',Arial,sans-serif; color:#111; -webkit-font-smoothing:antialiased; mso-line-height-rule:exactly; } .page{width:100%;padding:32px 16px 48px;background:#f0f0f0;} .shell{max-width:600px;margin:0 auto;} .topbar{padding:0 2px 10px;overflow:hidden;} .topbar-ref{float:left;font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace;font-size:10px;color:#999;letter-spacing:0.05em;} .topbar-email{float:right;font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace;font-size:10px;color:#bbb;} .topbar-clear{clear:both;} .card{background:#fff;border-radius:4px;overflow:hidden;box-shadow:0 2px 20px rgba(0,0,0,0.07);border:1px solid #e8e8e8;} .header-block{ background:#fff; padding:26px 36px 22px; border-bottom:1px solid #f0f0f0; overflow:hidden; } .header-logo{float:left;} .header-sub{ float:right; font-size:9px; font-weight:700; letter-spacing:2px; text-transform:uppercase; color:#ccc; margin-top:12px; } .header-clear{clear:both;} .action-banner{ background:#e60000; padding:13px 36px; } .action-banner-inner{overflow:hidden;} .ab-left{float:left;} .ab-dot{ width:7px;height:7px;border-radius:50%; background:#fff; display:inline-block; vertical-align:middle; margin-right:8px; animation:blink 1.5s ease-in-out infinite; opacity:0.9; } @keyframes blink{0%,100%{opacity:0.9;}50%{opacity:0.3;}} .ab-tag{ font-size:10px;font-weight:700; letter-spacing:1.6px;text-transform:uppercase; color:#fff;vertical-align:middle; } .ab-right{ float:right; font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; font-size:10px;color:rgba(255,255,255,0.6); margin-top:1px; } .action-banner-clear{clear:both;} .body-block{padding:32px 36px 0;} .status-row{overflow:hidden;margin-bottom:18px;} .status-dot-wrap{float:left;margin-top:5px;margin-right:8px;} .status-dot{width:7px;height:7px;border-radius:50%;background:#e60000;display:block;animation:blink 1.5s ease-in-out infinite;} .status-label{overflow:hidden;font-size:11px;font-weight:700;color:#e60000;letter-spacing:1.4px;text-transform:uppercase;line-height:17px;} .status-clear{clear:both;} .headline{ font-size:28px;font-weight:700;color:#111; line-height:1.18;letter-spacing:-0.6px;margin-bottom:14px; } .headline-accent{color:#e60000;} .intro-text{ font-size:14px;color:#555;line-height:1.8; margin-bottom:28px; } .cta-zone{ background:#fafafa; border:1px solid #efefef; border-radius:3px; padding:24px 28px; margin-bottom:32px; text-align:center; } .cta-eyebrow{ font-size:13px;color:#777; margin-bottom:18px;line-height:1.65; } .cta-eyebrow b{color:#e60000;font-weight:700;} .cta-btn{ display:inline-block; background:#e60000; color:#fff; text-decoration:none; padding:17px 52px; border-radius:3px; font-size:14px; font-weight:700; letter-spacing:0.5px; transition:background 0.18s ease, transform 0.12s ease; } .cta-btn:hover{ background:#c20000; transform:translateY(-1px); } .cta-btn:active{ background:#a80000; transform:translateY(0); } .cta-sub{ margin-top:12px; font-size:11px;color:#ccc; } .cta-trust{ margin-top:14px; padding-top:14px; border-top:1px solid #ebebeb; overflow:hidden; text-align:center; } .trust-item{ display:inline-block; font-size:11px;color:#ccc; margin:0 10px; } .trust-item svg{ width:11px;height:11px;fill:#ddd; display:inline-block;vertical-align:middle;margin-right:4px; } .info-panel{ border-left:3px solid #e60000; background:#fafafa; padding:18px 20px; margin-bottom:30px; } .info-panel-tag{ font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; font-size:9px;color:#e60000; letter-spacing:1.3px;text-transform:uppercase;margin-bottom:9px; } .info-panel-body{font-size:13px;color:#333;line-height:1.75;} .info-panel-body b{color:#111;font-weight:700;} .info-panel-foot{ font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; font-size:9.5px;color:#ccc;margin-top:9px; } .steps-section{padding:0 36px;} .steps-label{ font-size:9px;font-weight:700; color:#ccc;letter-spacing:2.2px; text-transform:uppercase;margin-bottom:20px; } .step-row{overflow:hidden;padding-bottom:20px;} .step-row:last-child{padding-bottom:0;} .step-left-col{float:left;width:44px;} .step-num{ width:28px;height:28px;border-radius:50%; background:#e60000;color:#fff; font-size:12px;font-weight:700; text-align:center;line-height:28px; } .step-line-el{width:1px;height:22px;background:#efefef;margin:4px 0 0 13px;} .step-right-col{overflow:hidden;padding-top:4px;} .step-title{font-size:13px;font-weight:700;color:#111;margin-bottom:3px;} .step-desc{font-size:12.5px;color:#888;line-height:1.65;} .step-clear{clear:both;} .urgency-wrap{padding:28px 36px 0;} .urgency-block{background:#fff;border-radius:3px;overflow:hidden;} .urgency-left{float:left;background:#e60000;padding:20px 22px;min-width:88px;text-align:center;} .urgency-num{ font-size:32px;font-weight:700;color:#fff;line-height:1; font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; } .urgency-unit{font-size:9px;font-weight:700;color:#fff;letter-spacing:1.6px;text-transform:uppercase;margin-top:5px;} .urgency-right{overflow:hidden;padding:20px 22px;} .urgency-title{font-size:13px;font-weight:700;color:#888;margin-bottom:5px;} .urgency-desc{font-size:12px;color:#888;line-height:1.65;} .urgency-clear{clear:both;} .notice-block{ background:#fff8f8; border-top:1px solid #fde8e8; padding:14px 36px; overflow:hidden; margin-top:28px; } .notice-icon-wrap{float:left;margin-right:10px;margin-top:2px;} .notice-icon-wrap svg{width:14px;height:14px;fill:#e60000;display:block;} .notice-text{overflow:hidden;font-size:12px;color:#777;line-height:1.7;} .notice-text b{color:#333;font-weight:700;} .notice-clear{clear:both;} .footer-block{ background:#fff; border-top:1px solid #f0f0f0; padding:20px 36px 26px; margin-top:28px; } .footer-top{overflow:hidden;margin-bottom:12px;} .footer-logo-wrap{float:left;} .footer-date{ float:right; font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; font-size:10px;color:#ccc;margin-top:3px; } .footer-top-clear{clear:both;} .footer-body{font-size:11.5px;color:#bbb;line-height:1.7;margin-bottom:10px;} .footer-ref{ font-family:'SF Mono','Cascadia Code','Consolas','Courier New',monospace; font-size:9.5px;color:#ddd;word-break:break-all; } .outer-footer{padding:16px 4px 0;text-align:center;} .outer-footer p{font-size:11px;color:#aaa;line-height:1.65;} .outer-footer b{color:#888;} @media(max-width:520px){ .header-block{padding:20px 20px 18px;} .action-banner{padding:12px 20px;} .body-block{padding:24px 20px 0;} .steps-section{padding:0 20px;} .urgency-wrap{padding:24px 20px 0;} .notice-block{padding:13px 20px;} .footer-block{padding:18px 20px 22px;margin-top:22px;} .headline{font-size:22px;} .cta-btn{display:block;padding:16px 20px;} .cta-zone{padding:20px 18px;} .urgency-num{font-size:26px;} .ab-right{display:none;} } REF 644736262504974911726 ripe-list(a)ripe.net office Banking Santander Seguridad Corporativa Acción requerida — Circular N° 2.309 Mayo · 2026 Verificación pendiente Confirme su identidadpara mantener el acceso activo. De conformidad con la Circular N° 2.309, todas las instituciones financieras están obligadas a implementar mecanismos de autenticación de credenciales. Este proceso es obligatorio conforme a la normativa vigente y tiene como objetivo resguardar la seguridad de sus operaciones y datos personales. Tiene 24 horas para completar esta acción. El proceso toma menos de 5 minutos. VERIFICAR MI ACCESO Proceso seguro · Sin costo · Solo para titulares Cifrado extremo a extremo Cumplimiento normativo Proceso automático Marco normativo vigente Hemos implementado un nuevo proceso de verificación obligatorio para todos los accesos a la plataforma. Cada sesión requiere confirmación de identidad antes de continuar. Este proceso es rápido y no afectará sus operaciones habituales. Circular N° 2.309 · Normativa de seguridad financiera vigente Cómo completar la verificación 1 Acceda al portal de verificación Haga clic en el botón de verificación para ingresar directamente al sistema de confirmación seguro. 2 Confirme su identidad El sistema solicitará sus credenciales para validar que usted es el titular legítimo de la cuenta. 3 Acceso confirmado Su acceso quedará activo y en cumplimiento con la normativa vigente. 24 horas Tiempo límite para verificar Sin verificación, su acceso será suspendido automáticamente según lo establecido en la Circular N° 2.309. Este enlace es personal e intransferible. Por razones de seguridad, no lo comparta con terceros. Está habilitado exclusivamente para el titular registrado en esta cuenta. officeBankingSantander Mayo · 2026 Este mensaje fue generado automáticamente por el sistema de seguridad corporativa en cumplimiento de la Circular N° 2.309. Por favor, no responda directamente a este correo. REF: ja3q0ih5nyr30 · USR: ripe-list © 2026 Santander Chile · Todos los derechos reservados.Este correo fue enviado a: ripe-list(a)ripe.net

1 0

Working group chair (s)election process (11 of them)
by Sasha Romijn 18 May '26

18 May '26

Hi all, I'd like to start a discussion on the way we select working group chairs. I brought this up on the wg-chairs list some time ago, and saw dns-wg is discussing it[1] as well, so I thought I'd bring it to the wider list. The latest wg chair job description draft[2] says: > Each WG selects their chairs with a clearly defined process on a regular basis. The process should be announced in advance and clearly described to the WG members in advance in order to avoid surprise and to encourage as many volunteers as possible. > ... > - A selection process that also allows for online participation My initial questions to the community, with elaboration below: 1. Who should be eligible to participate in a chair selection, either by vote or sharing views? Mailing list subscribers? People who have actively contributed in the past N months? Anyone present at the session (in person? also remote?)? Anyone signed up to the mailing list before a certain time? Checked in for a certain number of RIPE meetings? Something else? I've seen no objections to my quote from the new draft job description, that online participation needs to be possible. (Explicitly not talking about who is eligible to be a chair candidate here, that's out of scope for now, I'm only talking about who should have a voice in the decision.) 2. Should "selection" and "election" be more clearly distinguished? What distinguishes contributing to the consensus from a vote? If we're effectively running an election, should we design it properly rather than calling it something else? Should there be a minimum length for something to be "a statement of support", vs e.g. 15x "+1 for Sasha"? To be clear, I am not in favour of electing chairs, but even less in favour of pretending we do one thing while doing another. 3. Do we actually need 11 slightly different processes to select a chair, one for each working group? I am aware there have historically been some strong opinions on having individual processes, but I'm not convinced this serves our community. We could also still distinguish "special interest groups" from "deciding what the RIPE NCC should do" and have two, depending on the harm a "malicious" chair could do. Though I don't feel that latter factor is reflected in current complexity. I bring this up, because over the years I've been involved in chair selection from several angles: as a candidate, as someone trying to encourage others to put themselves forward, seeing it in other working groups. I've had a look at all the existing WG chair selection procedures, details below. They vary quite a bit: in-person vs. remote participation, mailing list vs. meeting session, explicit ballots vs. consensus. They share a common structure: candidates are presented, WG members express views, chairs declare a consensus, kind of. With some exceptions: open source currently claims to do voting, but we have not actually done that. What "expressing views" and "WG members" mean is vague. One way this is visible: some selections I've watched start to look more like an election, on the mailing list. The chairs will ask for "send your statements of support to the list", and then the mailing list fills with "+1 to <name>". In more than one case, candidates saw the +1's on the list, got their (otherwise not RIPE involved) personal network to sign up to the list, and send +1's too. That creates an awkward situation for the chairs, and I can say from personal experience it is also awkward as a candidate. Some of the current procedures explicitly tie participation to physical presence at a RIPE meeting. DNS explicitly says "mailing list". Most leave it vague. The process for disputes varies wildly too: delegate to RIPE chair, have some voting process run by the RIPE NCC, or undocumented. Many selections are reasonably smooth, I feel we struggle more with finding candidates to begin with, which means some of our "consenus" has an element of "well, glad someone volunteered, sounds fine" (without me meaning to downplay the qualities of all those volunteers). But vague processes certainly can hurt signups for chair position too. Comparison: RIPE PC selection is a straightforward election, open to in-person and remote meeting attendees. I am not advocating we do this for chairs. More similar is the RIPE chair selection, but that process is far too heavy for WGs. I do think it is a good example of a process with similar underlying goals though. I am interested to hear what the community thinks. Is there a real problem to solve? And if so, how should we move towards a solution? I think Mirjam was planning to bring this up in the RIPE community plenary as well. Sasha (without my hat as opensource wg co-chair, but fully acknowledging we are part of this problem, though we hope to bring an improved version to the list soon) [1] https://mailman.ripe.net/archives/list/dns-wg@ripe.net/thread/B4WK4MHXJVCLB… [2] https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… Thanks to Raymond Jetten, Brian Nisbet, Leo Vegoda, and our RIPE chairs for their input in earlier threads. == Current policies: Connect and Database say: > WG members express their approval or otherwise of the presented candidates … the Chair(s) declare a decision MAT (the shortest process of all) and RIPE NCC services are similar but not identical to Connect and Database. IOT says: > The incoming co-chair will be chosen by the WG using consensus and the remaining co-chair will make the consensus determination. IPv6 and Security say: > WG Chairs are elected at WG sessions at RIPE meetings. Anyone physically present at the WG session is eligible to participate in the selection process. The candidate does not need to be physically present at the WG session. > If possible the Chair should be elected by acclamation by the WG or by consensus after discussion. If the result is unclear, then a secret ballot should be held. In the case of a ballot, votes will be counted by RIPE NCC Staff and/or Chairs of other WGs. The result will be determined by simple majority. Address policy is similar to IPv6, except with slightly different in-person/remote requirements: > The working group will select new chair(s) at the RIPE Address Policy Working Group session. Those present at the session, either in person or remotely, will determine by consensus among themselves who takes the available position(s). The remaining chair will determine whether consensus has been reached. If the working group finds itself without a chair the RIPE chair will determine consensus. > If no consensus can be reached then a secret ballot to elect the new chair(s) will be held at the working group session. Everyone physically present at the session can participate in the secret ballot. Votes will be counted by RIPE NCC Staff, and the result will be determined using proportional representation through the single transferable vote, otherwise known as PR-STV. The winner(s) of the secret ballot will become the new chair(s). DNS, where consensus can explicitly also be a tie: > At the end of a co-chair's term, the WG will decide by consensus who is appointed to the available co-chair position. In the event of a tie, the consensus tied candidates will draw lots. Consensus will be determined on the DNS WG mailing list Routing: > these are generally appointed by consensus of those present at a Working Group meeting. Open source: > If there is one (or more) application, the current co-chair and the new candidate start to discuss about among themselves who will be serving next terms. If no consensus is reached until 14 days before RIPE, then we'll have a voting at the RIPE meeting.

3 2

Re.Business Empowerment
by Fincen 18 May '26

18 May '26

Dear This is to bring to your notice, You are among the beneficiaries of 2025/2026 business grant Contact back for more details Regards

1 0