[babel] Fwd: Action required: Update to IETF Datatracker password requirements starting 8 July
Donald Eastlake <d3e3e3@gmail.com> Thu, 03 July 2025 16:03 UTC
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@mail2.ietf.org
Delivered-To: babel@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A504C3D9588A; Thu, 3 Jul 2025 09:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2bW6MqfLteDp; Thu, 3 Jul 2025 09:03:50 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 05C693D9587D; Thu, 3 Jul 2025 09:03:50 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id d75a77b69052e-4a7a8c2b7b9so85029961cf.1; Thu, 03 Jul 2025 09:03:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751558629; x=1752163429; darn=ietf.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=st8ABj+r5FyyCzCEGkanJ9uXLqAQUNuHOUB+loKpsFg=; b=WK1LtQsu8ENXmnTQm6abuM86nKtGwP7AP7sv/sVdrkOpqpqNNcs35po6n+mwgdaRBa 4uxTUJZca2VqsUl0aJcw4w2eDyv9y77Ee1ZzH00SaZ9cu3S/ksajWwzXNUL6PxWDKghu ml7w7j3LQPzduEoYB8WsfsSAXX/wktsK5Nr6svSp46JSzNqGdt9awCypOtLr5Tc+1FLn RUDa8Sxuq2OfDoUikNufA2DLKp3aV2+dETWhVXsGfrHBmQoY8CR2pYbb1y/7RBuf6O+b jC0vP1kqSvx1wSPwA7vA/xBGvn8JB5+/+pkamp6+nivoYTRadZWxeIyhDOoPeAgn3lNz OLBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751558629; x=1752163429; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=st8ABj+r5FyyCzCEGkanJ9uXLqAQUNuHOUB+loKpsFg=; b=HE4TRFtTUDgfsRrlqvtSMhG1pBCjOHwBDzCa4whQDR3EmkfJ3WlMY7oPcpv9/zwrlN shMosk+ToMc9osAosNhUjPij5ORthKcC2MSRNwa1fTAEUOxUeQ3j7oUqnFHlkm7tYRb+ uOAnuuB79ORhSDaBd4+1vyKSTGRhQqhMxgDZEBTx5i7wD6lde6VVbi4kuGE3A754WJqG Agt+ngh9kSMzRsbRdPakqU5t49iFWUJRXS5hF18bHswMoWmexKD00nMlVt/lq0GTnVMb BqlxLROpsLGQpbpRJWRDmubIEqDKPgKjrBVPF/iMGyMqf2TwnRjtZiD6y2MQpqp+6wzt /G+A==
X-Forwarded-Encrypted: i=1; AJvYcCUFCPLTSOwPlaw0r4AyBOjA8UXbPOKaQ2XfNvpt3Pv9JxRdBeTTBO3VoDNMOnXW6PTAX3WSgQ==@ietf.org
X-Gm-Message-State: AOJu0Yz1M1ZJEFF3dyyrDF4eNXuZNLMTfMm7wMZGb0sOxbIbthf9BSb6 hWR/LdQvOxqv86VM3mOuIBF84QJFKljAriBJO6LPet30j753AwnsQbtt09tnkn56+n2J9H6/YEE R7D+jKbYcc7/lXRHu2wcWlSz6cVF07HudtA==
X-Gm-Gg: ASbGncv4JSaRfxn29cAmtEm2klN5xPfdG9m4BdOUqUUhpJoeic1rAWks895kzLPqkEL buQZXkgHzwT1ugfd6HNvLcMqQWTK1b4pMRkOJW1h70D1dqSqqw+luN9x1gdzfuXXk41EVmDXnCw nPsl3hxQjaQUgeWLMK3jsFUIKC44l+KW1MYIGwVcPVUQ==
X-Google-Smtp-Source: AGHT+IHCJuYCwm/Oxz6HGEjv4Q2AxZI0SOHfR9gBc2KOFP/lA87pX+kzFVCm3L10idSYa5kJK/vP0k1lUdvnd0ba4OQ=
X-Received: by 2002:ac8:578c:0:b0:48a:2429:9dc1 with SMTP id d75a77b69052e-4a9768a0638mr95106601cf.9.1751558628922; Thu, 03 Jul 2025 09:03:48 -0700 (PDT)
MIME-Version: 1.0
References: <fb165592-ddc6-400d-ae85-f2debbdb93f4@nostrum.com>
In-Reply-To: <fb165592-ddc6-400d-ae85-f2debbdb93f4@nostrum.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 03 Jul 2025 12:03:37 -0400
X-Gm-Features: Ac12FXyvrjtwPG3RGMNFBSnzQkax3BrVghYxtUh5W77jD0SNBgfPDxC7WGbWZz0
Message-ID: <CAF4+nEFTeL62eM7kkFts=swU72JOzySwdwxpYR5R-gkCD_fcFg@mail.gmail.com>
To: manet <manet@ietf.org>, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: T2E4JBRTWTJXIHCZACX2G42HYUK4WB67
X-Message-ID-Hash: T2E4JBRTWTJXIHCZACX2G42HYUK4WB67
X-MailFrom: d3e3e3@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-babel.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [babel] Fwd: Action required: Update to IETF Datatracker password requirements starting 8 July
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/tqfVS_eOdh8QQYQhHefK0CzQ3kg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Owner: <mailto:babel-owner@ietf.org>
List-Post: <mailto:babel@ietf.org>
List-Subscribe: <mailto:babel-join@ietf.org>
List-Unsubscribe: <mailto:babel-leave@ietf.org>
Password requirements for the IETF Datatracker are changing as in the message below. This would impact your ability to participate remotely in the upcoming July IETF meeting so you may wish to update your password. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com ---------- Forwarded message --------- From: Robert Sparks <rjsparks@nostrum.com> Date: Tue, Jul 1, 2025 at 4:02 PM Subject: Action required: Update to IETF Datatracker password requirements starting 8 July To: <ietf-announce@ietf.org> Beginning with a Datatracker update scheduled for 8 July, after the I-D submission deadline for IETF 123 Madrid has passed, passwords for the IETF Datatracker will be required to have at least 12 characters and be sufficiently complex.[1] You should verify your password meets the new requirements using the “New password” field on the change password form after logging in: https://datatracker.ietf.org/accounts/password/ On that form, a complexity bar and text below the new password field will provide guidance. When the bar is green, the password will be accepted. If your current password does not meet the requirements, please go through the password change process to set a new one that does meet them. If you are not already logged into Datatracker, this process requires confirmation via your primary Datatracker email address. IMPORTANT: If you are already logged into the Datatracker, do not assume that your password will continue to work without verifying it. Especially if you plan to participate in IETF 123, you should verify your password meets these requirements as soon as possible. Datatracker login is required to join MeetEcho for meeting sessions, whether you are participating in-person or remotely. Logging into the Datatracker well before the meeting starts will help ensure you don’t encounter delays when joining a meeting session for the first time. If you are the chair of an IETF working group or IRTF research group, please share this update with your group. This change eases a future migration to an authentication system that will allow for federated login, MFA, and passkeys. The new system also will allow the authentication process used for various IETF-provided services to be more robust. Another reminder about this change will be sent shortly after the Datatracker update is deployed on 8 July. Robert Sparks Senior Director of Information Technology for the IETF LLC [1] zxcvbn is being used to determine complexity (https://github.com/dropbox/zxcvbn) _______________________________________________ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-leave@ietf.org
- [babel] Fwd: Action required: Update to IETF Data… Donald Eastlake