Return-Path: X-Original-To: spasm@mail2.ietf.org Delivered-To: spasm@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 84A221189B327; Fri, 17 Jul 2026 15:50:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784328625; bh=Vo3Op4lSNQW74ipkOjw9CXj8u5hT23sV/d/6o3igCSw=; h=Subject:From:Reply-To:In-Reply-To:References:CC:Date; b=HA1MbGtgtNGk45elRnYf6OH+2pgBStc6mWNdcRFY1IJi24TPrX39sAaKb+z3DO18C l5W2lsInXor3jMqNEgzIGHnlBl+7EWxD+UJPp/a3lSDxkixcWUunNwgsI0s/F4mt1D ndgIS2z29Ct3LRUYBtNnssL3/B0CczeG3nsl6phs= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -3.375 X-Spam-Level: X-Spam-Status: No, score=-3.375 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=iana.org 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 7lPsVeGgNcjU; Fri, 17 Jul 2026 15:50:24 -0700 (PDT) Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (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 D4B0D1189B31F; Fri, 17 Jul 2026 15:50:24 -0700 (PDT) Received: from request7.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 463ECE1706; Fri, 17 Jul 2026 22:50:24 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.lax.icann.org 463ECE1706 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iana.org; s=202509s; t=1784328624; bh=Vo3Op4lSNQW74ipkOjw9CXj8u5hT23sV/d/6o3igCSw=; h=Subject:From:Reply-To:In-Reply-To:References:CC:Date:From; b=pHKfW4eVW4GHfGLmFPvAfpLD4q4ZE/aAqFhpzuWX9ILAkm6e7ux1JccTq1/FMFmMV uuUIOXNtebs8PEqDlablNOux4/9tJWUnqOTcQck845+lcWvJhDwl0hY8YbSkd1SejG YBMtFRumibHaOMDJT5CahmA5eel8KVfD9MEWUAHA= Received: by request7.lax.icann.org (Postfix, from userid 48) id 42C35C129C56; Fri, 17 Jul 2026 22:50:24 +0000 (UTC) RT-Owner: david.dong From: "David Dong via RT" In-Reply-To: References: Message-ID: X-RT-Loop-Prevention: IANA X-RT-Ticket: IANA #1456234 X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/) Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-RT-Original-Encoding: utf-8 Precedence: bulk Date: Fri, 17 Jul 2026 22:50:24 +0000 MIME-Version: 1.0 Message-ID-Hash: DABWIFMUXA2RRLVEQVN6VRQR37DH2XSD X-Message-ID-Hash: DABWIFMUXA2RRLVEQVN6VRQR37DH2XSD X-MailFrom: iana-shared@iana.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: draft-ietf-lamps-one-signature-certs.all@ietf.org, spasm@ietf.org X-Mailman-Version: 3.3.9rc6 Reply-To: iana-issues-comment@iana.org Subject: =?utf-8?q?=5Blamps=5D_=5BIANA_=231456234=5D_Early_review=3A_draft-ietf-lamps?= =?utf-8?q?-one-signature-certs-02_=28IETF_126=29?= List-Id: This is the mail list for the LAMPS Working Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Dear Authors, Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document: https://datatracker.ietf.org/doc/draft-ietf-lamps-one-signature-certs/ 6.1: Should this new registry be placed in an existing registry group, or a new registry group? If you have any questions, just let us know. If you'd like to talk in person, you can find us at the IANA table from Monday through Thursday. You can also request another review at any time by contacting us at iana@iana.org. For more information about IANA Considerations section requirements, please see https://www.iana.org/help/protocol-registration Best regards, David Dong IANA Services Sr. Specialist