From nobody Wed Aug 24 15:38:28 2022 Return-Path: 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 B2D32C14CF1E; Mon, 22 Aug 2022 23:43:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 4khWeAPZZaG1; Mon, 22 Aug 2022 23:43:43 -0700 (PDT) Received: from mail-yw1-x112b.google.com (mail-yw1-x112b.google.com [IPv6:2607:f8b0:4864:20::112b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26654C1527A4; Mon, 22 Aug 2022 23:43:38 -0700 (PDT) Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-335624d1e26so354934557b3.4; Mon, 22 Aug 2022 23:43:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=bK+GNKlhy9PbWwtZRUZiegHq//ysTDzHZe9GZzfDloA=; b=ByrJk2sRh0Tp4dMuhsYE3VNC+mbxSB1YjP7YBLLTjhwPbBhSs2HHTKo1oIXTjVOVUZ Igqggz6XZklv0tqnYrOR9V+k9g9dvfTraZS0wAgnnH30ztjXxQysFOt3ecanlBeVgylt jNhmtJFMyfs6Zm2vC7HkvDE0bCf5q8HEyo8HHo0Ja2urcttqurkVVwtptNt5eo7zKHVA AuHgtVwlwyA4cwsMdL/gNoql+x3TUMveEmCfWk1jrygqSyv+Smn/oioDLmNa8OcUdL9V v8hGP6Voy+heiNlmecFAzU83yFWzbhykqaBrLNYgkLH+91Xi9kTp/5fAlxuJj0jcDrZm G29w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=bK+GNKlhy9PbWwtZRUZiegHq//ysTDzHZe9GZzfDloA=; b=F57ydCHemq9K36q/o5XecdL5STIGTL1OxZweLlr5t+fCK0kkDhqp6/bHzMlVX5RHjr 0B9xa/FeJrKWHdHghI/YUbnhGoNXJysxyKSCvhBv1gDRIj7sVMio0xAyrq1A3PHqCz6j 2fiuQ57oJuwIapx+JGU9HVeke67H5mL4ulEiOKua9YUb08ecnEcCs7yXrUzjkcqfj051 9cQ1CyhAfpxM9iUCach2hnofXsB9hRgImJxZzHR7/SM5xv+lUb9raiee3pDbqISCavDj wYnAXB5dN4n/NWZQTtW4HGZ2ST4yLMlObeAoTzl8cjZf3mFKd39uM8Bo1xHBubYEqYc3 O95w== X-Gm-Message-State: ACgBeo3oc78pnYlierfjY+xenMbe6hDs4A6C/BkHBo1uPE1/vYhwOvjq x/338qIN+f4fHrZLmJtJE2EJKdETzjzvBalh61c= X-Google-Smtp-Source: AA6agR6bz+NsZvgSASLA/ITOb0st/nRMGJcBEGlzvC3+WTizJGZld3SsLPMKXacVxY6tp6uGjr/E+kUw+tRQnvDDMDw= X-Received: by 2002:a81:ad1:0:b0:318:3b63:6d00 with SMTP id 200-20020a810ad1000000b003183b636d00mr24527289ywk.146.1661237017065; Mon, 22 Aug 2022 23:43:37 -0700 (PDT) MIME-Version: 1.0 References: <4FFD4044-CB4C-46EC-AAAE-B84E6B3AB4B0@verisign.com> In-Reply-To: From: Dmitry Belyavsky Date: Tue, 23 Aug 2022 08:43:25 +0200 Message-ID: To: John C Klensin Cc: "Gould, James" , =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= , "Gould, James" , art@ietf.org, draft-ietf-regext-epp-eai.all@ietf.org, last-call@ietf.org, regext , i18ndir@ietf.org, gen-art@ietf.org Content-Type: multipart/alternative; boundary="0000000000004a3ca005e6e2e236" Archived-At: X-Mailman-Approved-At: Wed, 24 Aug 2022 15:38:19 -0700 Subject: Re: [regext] [Last-Call] last call reviews of draft-ietf-regext-epp-eai-12 (and -15) X-BeenThere: regext@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Registration Protocols Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2022 06:43:47 -0000 --0000000000004a3ca005e6e2e236 Content-Type: text/plain; charset="UTF-8" Dear John On Tue, 23 Aug 2022, 04:27 John C Klensin, wrote: > > > --On Monday, August 22, 2022 16:01 +0000 "Gould, James" > wrote: > > > John, > > > > How about if we change the approach to use the well-understood > > command-response extension? > > If things were changed to create an extension type that is > defined in RFC 5730 rather than creating a new type, that would > certainly eliminate the need to update 5730 (or explain clearly > why that was not necessary). > > That, of course, leaves the more substantive SMTPUTF8 issues, > particularly the need for a slot for an alternate all-ASCII > address. > No. SMTPUTF8 email address _is_ email address. Otherwise we are stuck with email addresses of first-class and of second-class forever. We don't need separate slot for all-ASCII addresses. --0000000000004a3ca005e6e2e236 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear John=C2=A0

On Tue, 23 Aug 2022, 04:27 John C Klens= in, <john-ietf@jck.com> wrot= e:


--On Monday, August 22, 2022 16:01 +0000 "Gould, James"
<jgould@verisign.com> wrote:

> John,
>
> How about if we change the approach to use the well-understood
> command-response extension?

If things were changed to create an extension type that is
defined in RFC 5730 rather than creating a new type, that would
certainly eliminate the need to update 5730 (or explain clearly
why that was not necessary).

That, of course, leaves the more substantive SMTPUTF8 issues,
particularly the need for a slot for an alternate all-ASCII
address.

No. SMTPUTF8 email address _is_ email address. Otherwise we are s= tuck with email addresses of first-class and of second-class forever.=C2=A0=

We don't need separ= ate slot for all-ASCII addresses.=C2=A0=C2=A0
--0000000000004a3ca005e6e2e236--