[IPv6]Fwd: Action required: Update to IETF Datatracker password requirements starting 8 July

Bob Hinden <bob.hinden@gmail.com> Tue, 01 July 2025 22:56 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@mail2.ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A18A73C6D9FF for <ipv6@mail2.ietf.org>; Tue, 1 Jul 2025 15:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 ID_dvRpWaMG2 for <ipv6@mail2.ietf.org>; Tue, 1 Jul 2025 15:56:51 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 276F03C6D9F5 for <ipv6@ietf.org>; Tue, 1 Jul 2025 15:56:51 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id 3f1490d57ef6-e733e25bfc7so3332586276.3 for <ipv6@ietf.org>; Tue, 01 Jul 2025 15:56:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751410610; x=1752015410; darn=ietf.org; h=message-id:to:cc:references:date:subject:mime-version:from:from:to :cc:subject:date:message-id:reply-to; bh=klvCDOalaUUw0xcx+jark1tLnEzMMyIULcvgJih2bHk=; b=TPotTBF6QppeLkw8H+ZGgzJqSElY2TqMeSiwMgS3ia48sC/f18O/rqycp7lsFU9BFf /szBM2hiF6CT4plgTPONkmr7HluQTLM5u5bn8+SS06/5npdjsX1UO7CHVcPYRzo97DEv c7iabl03Yes8RZPDmbmg69HSzrhPVZ9BhL5uThAu2x1LO+VP9Gqmzw3Reg/hc5vip/CG 0busx8LHdDC0R7H2LnzmIQw76e6t5jnnMZ+XasE0yhrnhXJqg1Anf5yUfK06JhguvIl4 2y28W7Mzkvm2LVmVQy7Ix+Qqk7s5B0EfIO0pPfjETPc4vGbicGvSPQRE/nwuQaKb0YF7 jiAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751410610; x=1752015410; h=message-id:to:cc:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=klvCDOalaUUw0xcx+jark1tLnEzMMyIULcvgJih2bHk=; b=Qo56Ewc1E31bYusYkL7SI30bcOJl/I8rHazIf3PKLCeanbQboks4uR5tYxWBO/5etk CWiVdCwCmbrmrIRIXC+zGiP7mqIBBnVazxrGXEpJX8IVjdJ0/0hDRmM/WTbMMLigdi4s MQfrOi5qsGA/WA97duxyvamqvCHMf1G7y1HHOpio8gsFD2YWEI3NS9VWA3k4ZsvRQHx9 A3ojNrL48CMW/Nhq9VEnIWWsIlzrp5GLdRPRBE6uCWXC+lxT2pVFHyT2b3AC6EGKkbA3 KJ8eps2x/6ZUHEVzinydvXBaX0yIPqTFu2v26fNcxQrHAHDpVOrXTnldhw7HV9xpMRVY X7OA==
X-Gm-Message-State: AOJu0YwneLj2yFTjAH3crAONabZzI9d4GfEWuMXNJsaPC8w8gUFk0LlS MIcevkYG1E07kL1ZhUHe4nlvFZYuR0QoCfzr3Zc751XKxnUCwud7oR/gw2MBZA==
X-Gm-Gg: ASbGncvo6FdMjr4I6/XFTanvAoguXJV0OthaT5rLplPcbDIstG0vpDxKvgpdzJZByXD ePfWEmD1qzVG7wHHfJPkkt4apAwjZ6fYY9twkU3iPN/XhdlK1Wh4nAPmXIncHq9rbHpCrrCtqBR 7CUxxtlJiGj/dn2+CyUXVjl97Zc/b6hUrNwVj6xTFlZLRCMPhhs2Wp2C3hXyQ16mvtLd5tP/xIe vTmwt+NqRiuPhFhg6QTUZSdDlsQrqcZAayMvxsB3+TI/l4hI+QU+GNewY4DAnFb7/DWlbPH2pDF 7q7KwCEfZwYubMhPIx6L6dQ7jK5/NCV+0LF5BAMuwM8RT3oQcpUAlRASI6cML7izC2NEjGO6Frs HGpHzuFNt+KEcSa6ZRDhQ
X-Google-Smtp-Source: AGHT+IGlu8HgP4TxkWwjL4rLl52XHG+G4ZWfM2KrTeviVjDATl1eaBi9a5Zs/OqQkkuMGWUQSTGhbQ==
X-Received: by 2002:a05:6902:12c3:b0:e81:ffff:b76a with SMTP id 3f1490d57ef6-e897e29a464mr820787276.35.1751410610054; Tue, 01 Jul 2025 15:56:50 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:2814:c353:a70f:8b82]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e87a6b6447fsm3253367276.17.2025.07.01.15.56.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Jul 2025 15:56:49 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_353B2CBC-82D4-4A7A-894E-250DC35EA408"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Date: Tue, 01 Jul 2025 15:56:27 -0700
References: <fb165592-ddc6-400d-ae85-f2debbdb93f4@nostrum.com>
To: IPv6 List <ipv6@ietf.org>
Message-Id: <EF1A0D68-5E6C-4EAC-98A2-24380357198E@gmail.com>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: HLTSDQ72MHXFGTBELJQ6FBZHQZFTIIA5
X-Message-ID-Hash: HLTSDQ72MHXFGTBELJQ6FBZHQZFTIIA5
X-MailFrom: bob.hinden@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Bob Hinden <bob.hinden@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPv6]Fwd: Action required: Update to IETF Datatracker password requirements starting 8 July
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/01CzNO9k5yYLA2a8eXXDO77UhYM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

FYI

Please check your datatracker password to make sure it complies with the updated password requirements.

Bob & Jen


> Begin forwarded message:
> 
> From: Robert Sparks <rjsparks@nostrum.com>
> Subject: Action required: Update to IETF Datatracker password requirements starting 8 July
> Date: July 1, 2025 at 12:59:12 PM PDT
> To: ietf-announce@ietf.org
> Reply-To: Tools Team Discussion <tools-discuss@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