IETF Logo Mail Archive

[regext] Thoughts on AuthCodeSEC

Christian Simmen <simmen@denic.de> Mon, 04 November 2024 14:41 UTC

Return-Path: <simmen@denic.de>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23479C20C8D1 for <regext@ietfa.amsl.com>; Mon, 4 Nov 2024 06:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=denic.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DekwvlId8_b for <regext@ietfa.amsl.com>; Mon, 4 Nov 2024 06:41:52 -0800 (PST)
Received: from mout-b-110.mailbox.org (mout-b-110.mailbox.org [195.10.208.55]) (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 ietfa.amsl.com (Postfix) with ESMTPS id E1848C20C8C3 for <regext@ietf.org>; Mon, 4 Nov 2024 06:41:50 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-110.mailbox.org (Postfix) with ESMTPS id 4XhvLL2bdXz9wWY; Mon, 4 Nov 2024 15:41:46 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1730731306; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=b+g6tQWMRGNTp8J09AboRxGnGJEoffxbRdUnKONbt4Q=; b=Pt9epsOjZdlkK61E8tvtnfScUntLsYnGkqjwOk6gIG0Uukikvgfn0AiuwBnDZzYkRcI/f3 Rx5UQY277c2xM/bATMr8rAhsYXpT/HHg54IdHfqXS6qPhC5g9/6e1q+Xbo+ZgWN0K9wC9f IIyrVoSmGmw43htgOdY37Ke7JgsBpSabZJI/KKzy5Xgcqa5atvNGYprhPiGDeTjp10MXCW swoA+UlBQERIUcfzCGK4C3s1wrvNfKffpEyVcf5MHhBTZYNICJLB33XpeB9lRCwJzm1yHy cL+nMezOxU0JseKHs1WeTo/lst6/St14YXhP9q0FF9HamCY/zeVb0TDv4CMAYA==
Message-ID: <a2d39e4d-4d85-4c98-9318-b35a2154674d@denic.de>
Date: Mon, 04 Nov 2024 15:41:44 +0100
MIME-Version: 1.0
Content-Language: en-US, de-DE
To: zzn <zzn@namefi.io>
From: Christian Simmen <simmen@denic.de>
Organization: DENIC
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms030807080707080402090101"
X-MBO-RS-META: kuz3chd5hady8oai5auo4djkfchbf6ao
X-MBO-RS-ID: 445caaef79532f85577
Message-ID-Hash: W6TLGR4G3R4LFDW6U66LWBJKFZDXDW6U
X-Message-ID-Hash: W6TLGR4G3R4LFDW6U66LWBJKFZDXDW6U
X-MailFrom: simmen@denic.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: regext <regext@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Thoughts on AuthCodeSEC
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/0f_DgzA-1MGifQjH_zCiUgr25y4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

Hi Victor,

If I got you right the gaining registrar needs to be known at the time 
the AuthCode is submitted to the registry. AFAIK there are some use 
cases out there where this is not applicable. Can you describe how 
AuthCodeSEC would work in this case?

Thanks in advance
Christian

-- 
Christian Simmen
Product Owner Registry Services

DENIC eG | Theodor-Stern-Kai 1 | 60596 Frankfurt am Main | GERMANY
E-Mail: simmen@denic.de | Fon: +49 69 27235-464
https://www.denic.de

Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main)
Vorstand: Thomas Keller, Martin Küchenthal, Andreas Musielak, Sebastian 
Röthler
Vorsitzender des Aufsichtsrats: Daniel Rink
Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht 
Frankfurt am Main

Allgemeiner Hinweis zur Erfüllung unserer Informationspflichten gemäß 
Art. 13, Art. 14 DS-GVO: Informationen zur Verarbeitung 
personenbezogener Daten durch DENIC finden Sie unter 
https://www.denic.de/datenverarbeitung-allgemein/

v2.46.0 | Report a Bug | By Email | System Status