Return-Path: X-Original-To: calsify@mail2.ietf.org Delivered-To: calsify@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A968C43E4C05; Mon, 14 Jul 2025 08:58:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.788 X-Spam-Level: X-Spam-Status: No, score=-2.788 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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=fastmailteam.com header.b="Qnaqj7Fh"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="oRRrZTYY" 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 TcxtbO8uvwoi; Mon, 14 Jul 2025 08:58:32 -0700 (PDT) Received: from fout-a4-smtp.messagingengine.com (fout-a4-smtp.messagingengine.com [103.168.172.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8E94743E455C; Mon, 14 Jul 2025 08:56:39 -0700 (PDT) Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id 76FC8EC060C; Mon, 14 Jul 2025 11:56:39 -0400 (EDT) Received: from phl-imap-15 ([10.202.2.104]) by phl-compute-02.internal (MEProxy); Mon, 14 Jul 2025 11:56:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-type:content-type:date:date:from :from:in-reply-to:message-id:mime-version:reply-to:subject :subject:to:to; s=fm3; t=1752508599; x=1752594999; bh=Huut3Lo+tT 1PqtasdP57V8CrXcCUv9xg28gRVU9SO58=; b=Qnaqj7FhMYbd8B0Qgdl65ABAMH GZ+43da64eCLOrXcTLJ57jF6LF5cZj3AhlnPtXYUZxZlf4vC5s1yxxfPlBQ5njwd kJl0LNs6RR45BoAV7GzVvwPwWrq/2oupfW3lK/JB/Ds4vkJQOA1vHr5GqLSzQYtX NGDbIptjvBQcN2V68tuF8EdeL/3E/1urC1/a/neZkGBgB7zEdqMlW9C17XBNnyZk 2b6S8AhOSbYXWJckcsEIeh5qWQpGOV0chCxE96VHQapJuI4gfORsRD01n9oZ1IgR Atf5cVzOk08hT75+lm++1cFeHYA3cjHOkeiyOI7ilEoKNhmloJ8MiBcdcfUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1752508599; x= 1752594999; bh=Huut3Lo+tT1PqtasdP57V8CrXcCUv9xg28gRVU9SO58=; b=o RRrZTYYzGd5lcR/eUglSufrqeuiBXuap3XbOHw/cjn8Y9fuTDgCgHYRMmS0Bgjft aPF5crOUsss2Pq94NDCep5qOfgejemLePxiCIExV0zkTdI0sdbg8MHI9BWLojnyB nsXnpkXHdx19UBZdy++jNLHfpDQmKPCcNsBoZ1oxeU8bvGv2iRTLrKSyS8KzHboo lIycib0YfZGT/vht3jkSioeYrNvq4yFLmWGV1oGKTdfOEDXFYnsBbRKjLGR8hrYh p2SEUKmfvSvo+wUCPwi5TZoEaL5fkz2gnUoJ9CiGXne1kG486NDQG/vwgFxkB+Wk fygHL0dUKQdtzCjHHnobg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdehvdefjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecunecujfgurhepofggfffhvffkufgtsegrtderreertdejne cuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeeiieehjedtgeetieffgeekud ejhfelhfehiedvledvkeevffeuffevffekjeeukeenucffohhmrghinhepihgvthhfrdho rhhgpdhorhhgrdihohhupdhgihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggr mhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpth htoheptggrlhhsihhfhiesihgvthhfrdhorhhgpdhrtghpthhtohepjhhmrghpsehivght fhdrohhrgh X-ME-Proxy: Feedback-ID: i2d7042ce:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 31A1B780075; Mon, 14 Jul 2025 11:56:39 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface MIME-Version: 1.0 x-forwarded-message-id: <066d6894-4183-4a59-9908-03afb3130069@nostrum.com> Date: Mon, 14 Jul 2025 11:56:19 -0400 From: "Bron Gondwana" To: jmap@ietf.org, calsify@ietf.org Message-Id: Content-Type: multipart/alternative; boundary=46d4f5b37661422f9fd1e0b15d600554 Message-ID-Hash: YHKXIU4DTEM3J5MP22TQATACZ42LUSBJ X-Message-ID-Hash: YHKXIU4DTEM3J5MP22TQATACZ42LUSBJ X-MailFrom: brong@fastmailteam.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-calsify.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: =?utf-8?q?=5Bcalsify=5D_Fwd=3A_Second_Reminder=3A_Action_required=3A_Update_?= =?utf-8?q?to_IETF_Datatracker_password_requirements_starting_8_July?= List-Id: Calendaring and Scheduling Standards Simplification Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --46d4f5b37661422f9fd1e0b15d600554 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Just in case any of you aren't on the announce list. Don't wait until the start of the session and try to log into Datatracke= r to discover you can't get in and have to do a recovery, log into Datat= racker this week and make sure it's still working for you! Bron. ----- Original message ----- From: Robert Sparks To: ietf-announce@ietf.org Subject: Second Reminder: Action required: Update to IETF Datatracker pa= ssword requirements starting 8 July Date: Monday, July 14, 2025 11:16 If you have not already done so, please confirm that your password meets= the new requirements as soon as possible. NOTE: Please make sure the working password is set for both _datatracker= .ietf.org_ and _auth.ietf.org_ domains. auth.ietf.org uses datatracker c= redentials. Sign-in to MeetEcho or any other service that uses datatrack= er credentials will use auth.ietf.org. You can test whether your passwor= d is properly set for auth.ietf.org by logging into _notes.ietf.org_. Robert Sparks On 7/1/25 2:59 PM, Robert Sparks wrote: > 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] >=20 > You should verify your password meets the new requirements using the =E2= =80=9CNew password=E2=80=9D field on the change password form after logg= ing in: >=20 > _https://datatracker.ietf.org/accounts/password/_ >=20 > On that form, a complexity bar and text below the new password field w= ill provide guidance. When the bar is green, the password will be accept= ed. If your current password does not meet the requirements, please go t= hrough the password change process to set a new one that does meet them.= If you are not already logged into Datatracker, this process requires c= onfirmation via your primary Datatracker email address. >=20 > IMPORTANT: If you are already logged into the Datatracker, do not assu= me that your password will continue to work without verifying it. >=20 > Especially if you plan to participate in IETF 123, you should verify y= our password meets these requirements as soon as possible. Datatracker l= ogin is required to join MeetEcho for meeting sessions, whether you are = participating in-person or remotely. Logging into the Datatracker well b= efore the meeting starts will help ensure you don=E2=80=99t encounter de= lays when joining a meeting session for the first time. >=20 > If you are the chair of an IETF working group or IRTF research group, = please share this update with your group. >=20 > This change eases a future migration to an authentication system that = will allow for federated login, MFA, and passkeys. The new system also w= ill allow the authentication process used for various IETF-provided serv= ices to be more robust. >=20 > Another reminder about this change will be sent shortly after the Data= tracker update is deployed on 8 July. >=20 > Robert Sparks Senior Director of Information Technology for the IETF L= LC >=20 > [1] zxcvbn is being used to determine complexity (_https://github.com/= dropbox/zxcvbn_) >=20 _______________________________________________ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-leave@ietf.org -- Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC brong@fastmailteam.com --46d4f5b37661422f9fd1e0b15d600554 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Just in case any of you aren't on the announce list.

Don't wait until the start of the session and try to log into D= atatracker to discover you can't get in and have to do a recovery, log i= nto Datatracker this week and make sure it's still working for you!

Bron.

-----= Original message -----
From: Robert Sparks <rjsparks@nostrum.com>
To:&nbs= p;ietf-announce@ietf.org
Subject: Second Reminder: Action required: Update to IETF Datat= racker password requirements starting 8 July
Date: Monday, Jul= y 14, 2025 11:16

If you have not already done so, please conf= irm that your password meets the new requirements as soon as possible.

NOTE: Please make su= re the working password is set for both datatracker.ietf.org and auth.ietf.org domains. auth.ietf.org uses datatracker credentials. S= ign-in to MeetEcho or any other service that uses datatracker credential= s will use auth.ietf.org. You can test whether your password is properly= set for auth.ietf.org by logging into notes.ietf.org.

=

Robert Sparks

On 7/1/25 2:59 PM, Robert Sparks= wrote:

Beginning with a D= atatracker update scheduled for 8 July, after the I-D submission deadlin= e for IETF 123 Madrid has passed, passwords for the IETF Datatracker wil= l be required to have at least 12 characters and be sufficiently complex= .[1]

You should v= erify your password meets the new requirements using the =E2=80=9CNew pa= ssword=E2=80=9D field on the change password form after logging in:

= https://datatracker.ietf.org/accounts/password/

On that form, a co= mplexity 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 alre= ady logged into Datatracker, this process requires confirmation via your= primary Datatracker email address.

IMPORTANT: If you are already logged into the Datatrac= ker, do not assume that your password will continue to work without veri= fying it.

Especia= lly if you plan to participate in IETF 123, you should verify your passw= ord meets these requirements as soon as possible. Datatracker login is r= equired to join MeetEcho for meeting sessions, whether you are participa= ting in-person or remotely. Logging into the Datatracker well before the= meeting starts will help ensure you don=E2=80=99t encounter delays when= joining a meeting session for the first time.

<= p dir=3D"ltr" style=3D"line-height:1.38;margin-top:10pt;margin-bottom:0p= t;">If you are the chair of an IETF working gr= oup 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 federa= ted login, MFA, and passkeys. The new system also will allow the authent= ication process used for various IETF-provided services to be more robus= t.

Another remind= er about this change will be sent shortly after the Datatracker update&n= bsp;is deployed on 8 July.

Robert Sparks Senior Director of Informati= on Technology for the IETF LLC

[1] zxcvbn is being used to determine complexity (https://githu= b.com/dropbox/zxcvbn)

_________________________= ______________________
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-leave@ietf.org


<= div class=3D"signature">--
  Bron Gon= dwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
  brong@fastmailteam.com


--46d4f5b37661422f9fd1e0b15d600554--