Further update on authenticating to use the IETF Network at IETF 125 Shenzhen

IETF Executive Director <exec-director@ietf.org> Tue, 10 March 2026 20:49 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: ietf-announce@mail2.ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id ADF1FC7C86C7 for <ietf-announce@mail2.ietf.org>; Tue, 10 Mar 2026 13:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=staff-ietf-org.20230601.gappssmtp.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 edvlU-6I_89X for <ietf-announce@mail2.ietf.org>; Tue, 10 Mar 2026 13:49:38 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 5EAC3C7C8610 for <ietf-announce@ietf.org>; Tue, 10 Mar 2026 13:49:30 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id 41be03b00d2f7-c73a5473bbdso1302924a12.2 for <ietf-announce@ietf.org>; Tue, 10 Mar 2026 13:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1773175769; x=1773780569; darn=ietf.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=pazLpv024j2c70vd6bGVJEF4Mvn7FBqLePCF66UZdzo=; b=yZITVGmp/Gnj4yBNwCuP1uU0BMvJDtOU8tzmga3fTrHxGvWUj3GqGnOQ6BgoxB2uCm rmp/9GQQ4xh6AqsxfRrkIug5ix7j08zpFeX84e6pvyAW11J0RXOqXHg/n3lo1e0uHSMn xqzoo2QBQe16nT4+vWjc9TQ1JvXOBGBiUi8x7IhOg2HL1edyak2BXwBqmp94oufjbrxI +9TxJm6n5EUWmh94lFVDZvfYCvz63s1rP5hWttbt/VEr5xGAnHX+L03LCVg79a0tf5M5 ZIqdcojSpCoW+p61gP9m/7ayxPcR3UFGS4olmplvZuIM41xZaKncog8zz08fAkNPafEZ JSLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1773175769; x=1773780569; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pazLpv024j2c70vd6bGVJEF4Mvn7FBqLePCF66UZdzo=; b=q9GzbTXEYJh31l1cWWmSh8L9Ko7/u5vTpTymyZawznSuM41YlrQihuNN+IgZDg8MLA pCmfYCzZBB0oz8p4Ee7LykcXUEqi/j98/YNa6YSsvzXh4b+VKqSbPJ8Alq48nRAG78pV EzelG1yJ4kRk1aLsRcKpiR+J4kxsAoBxmyDEB1ORBPSmftBpS8QQpxgEiImYq846j6bs Yikkcs33SLT5EABHUgnnOJ6Q7yA2Fa4uUSdoM6P5mYgbayfE5dLDtZAF5lcc83B0kSe9 5bG4iXqrz0VTwHB29HzQu9PVFrP/B8Y6yrH/CgmZmXe+CP+eL8zW1V+EUPFsBFtPg92K SR8Q==
X-Forwarded-Encrypted: i=1; AJvYcCWpfcsQ5zYF4nayx8OaEmXnWeXVjVmbM+1ztIWKXYSqKLI/6aMjfWvP6g69UMx9a1ojH9WQyKyFm+jFb5NO@ietf.org
X-Gm-Message-State: AOJu0Yzg8zlBKPq7QYnXgweNU811CRJW0YNR+4iWMfKhr4cD3thT7v5s 6wviBlS3Nn7j8pFfgyFPlGpxm4NnHExnaHoY4+SxM8RB0p5etJL8LAQ2+hqX1tCi99pJV0g/26k W42XEpZF3Jw==
X-Gm-Gg: ATEYQzx5BeLMHYygQ58tOcknDFooXjfzs/0MGhwA/c5vrgLPwWM/RU2C6i0JnBVU8Ej qmac13aLjBgz0Bcj+FO5a4+pRro8WSgHAduYPF4JP6wHk7Sh1ASdubthpWxhftBvl7xq4y0ieOK p3O8wN4allAdg2We2/h/NysC/ucXvnCt6EmsUG0Ijw2ZkX9wuG1IrUqxfSgaAiMD6064SUxug09 +jyKhTjEHqwtkDpIp+jmYY2s/WjglS3IKdg9Ev0TEXklT07DeeocKwzs4ULQT6A6W/4TBATE/h/ vf5Nn0EEFWLQeaO1bqN4H4s82VdqeaG0P2cnuTXWEF9W5H0dmqznQzCkzJAFPMhTuIn9qqB2uyx sJkKU6NhcMnpk9yePNFDG67dDEa/mmPsAFfziVbKCLBBTfoYDv7d7g76a7CW7ORKni/NemUrsrT 0803ZviXyLA2zpLrbfPK2KSpCxbNoGbwkqyhDtHWGyhpKiYqKy7yWoxBJdbocRXwyxSRzEAkUSZ FjkZXkgGOwy+J5ItGdL19TG1NVwSaj6Dwc+
X-Received: by 2002:a17:90b:530c:b0:359:fecd:1cd3 with SMTP id 98e67ed59e1d1-35a0135ac60mr187506a91.23.1773175769445; Tue, 10 Mar 2026 13:49:29 -0700 (PDT)
Received: from smtpclient.apple (203-96-138-83.dsl-dynamic.connections.net.nz. [203.96.138.83]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-359ffdb6e53sm97555a91.0.2026.03.10.13.49.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2026 13:49:28 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Subject: Further update on authenticating to use the IETF Network at IETF 125 Shenzhen
Message-Id: <27B851E4-43C3-40DE-9580-8426D46C7D57@ietf.org>
Date: Wed, 11 Mar 2026 09:49:14 +1300
To: 125all@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: 2AGGINZ2OBCVIHBTLXK53426TCUPUWGB
X-Message-ID-Hash: 2AGGINZ2OBCVIHBTLXK53426TCUPUWGB
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.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
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/SSokEHwWXvVbwxriPj-r4gDC_Ro>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

I am sorry to inform you that the regulatory requirements around authenticating to use the IETF Network at IETF 125 Shenzhen have again changed and again become more restrictive. The IETF Network itself remains an open, unfiltered network that allows VPNs and other security technologies to be used, with these changes only affecting authentication to the network.

The changes are:

1. Previously we have stated that the only information to be shared is the mapping between RADIUS account names and registrant names. Now, we are required to share RADIUS accounting logs including account name, IP address, last 24 bits of the MAC address, RADIUS accounting message types (start session, stop session, interim-update) and timestamp. This data will be provided after the meeting.

2. Previously we have stated that a registrant can have as many sets of RADIUS credentials as they wish. Now, there is a limit of two sets of credentials per registrant. Replacements are allowed if one set is lost, but only if the lost set is deactivated. We are also required to investigate whenever a single set of credentials is used on more than five MAC addresses to check that the credentials have not been lost, shared or compromised.

Please note that Chinese participants are expected to follow local laws that require real identity registration before using the network, but this does not apply to non-Chinese participants.

The IETF Administration LLC apologises for these unanticipated late changes and reiterates that any onsite registration can be converted to a remote registration with no handling fee.

We welcome the work recently proposed to clarify community expectations around anonymity and privacy on the IETF Network.

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org