[regext] Re: [IANA #1410981] expert review for draft-ietf-regext-epp-eai (xml-registry)
Tim Bray <tbray@textuality.com> Fri, 17 January 2025 16:12 UTC
Return-Path: <tbray@textuality.com>
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 1182FC14F69F for <regext@ietfa.amsl.com>; Fri, 17 Jan 2025 08:12:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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 (1024-bit key) header.d=textuality.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 uaDO1bg1BAE3 for <regext@ietfa.amsl.com>; Fri, 17 Jan 2025 08:12:28 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 ietfa.amsl.com (Postfix) with ESMTPS id DD707C151070 for <regext@ietf.org>; Fri, 17 Jan 2025 08:12:28 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-21bc1512a63so47115065ad.1 for <regext@ietf.org>; Fri, 17 Jan 2025 08:12:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality.com; s=google; t=1737130348; x=1737735148; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3Jsizf2YHB4kN3v3elM0SPdcCY3HMNF7YkQ8AF7kVH0=; b=NF1dOAxbiEXmXJh0UAGiRuIzWlZ2tUyIgF1ghApymaAbihv5GQqq5IH3r/56nwfk2D AU4xC4tFfcvOxYwDJYg2TJVQmpLmtiB5rtLnSBXXW3y7OrcfT175Z7gAsg31X0LLcIrx tdBu2sviFhJ4HW9VObeRzteots5+rIfKKCkK4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737130348; x=1737735148; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3Jsizf2YHB4kN3v3elM0SPdcCY3HMNF7YkQ8AF7kVH0=; b=bBQFyOUpRK5eu5ZONp+ZWOccCunTdpvoug1IpF77VfFeJCeApv6Oswnx7NRNNirqCO fbdMTAQDHavXDnH4j5YfzAA6+QAfhMc0BguRVDmSd2h0wdFHXeFB4i51LuqazKUJBxX+ SY5GBOBa8CDSfAYsfpTj9ZdmZ9wM0H8VaPybheDP3zcUw1f3+widH6xc/w5D5JoZwaKC 8x23BCOGQTHWcBPshonJZGI9mOeYM23VmCnyFRRkwk6yfKKiEJU4gF5br+c8Fb46KfWr R4u8vwaPb1zpYRQeqAGdFXumNaXZ+O37JtfR+C/ku2YdZviDQasuBpLGugXNeZbkuBAP UeSA==
X-Forwarded-Encrypted: i=1; AJvYcCXjFG9hrx595E5qPaP8wGghmjhRttPQb/p4a35Sfj4Pw66iJd9oy7TxWveErIdyPSIH05hqSmo=@ietf.org
X-Gm-Message-State: AOJu0YzG6KsaAtErCeLjKJgwfRbWGyvrBXNJr/9xR0YnbbiIhzBLWpWO hMawaQhC5SubcTY1x6D8edeSMGAM4issxrAwxESY5/yGVZYstUCXSTi9n60wKyMFRep+AnZUWlI QV/NlndSF2TIjCjqi/PHkGuPSVLlJTeYImGCXlw==
X-Gm-Gg: ASbGnct/anAm2t2SHVXVJ+FrJ2QPJvgjadaRsqQ2hELGAiGzWn+qe+VSAzgIcVNYhmR 2tURNeeYrT/fOkEvUvAViPV4U7mJb3SmYSjvnWw==
X-Google-Smtp-Source: AGHT+IHFg+mM/GzpHHwkScH48jPKeU9ZQ6wX90NRc284BzOe934kGqJN+aOxOJAoVe5C4aLZCa0J6J9lcyUCl/sCzsw=
X-Received: by 2002:a17:902:cec6:b0:215:a3fb:b4d6 with SMTP id d9443c01a7336-21c3553b55dmr35225505ad.8.1737130348056; Fri, 17 Jan 2025 08:12:28 -0800 (PST)
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Fri, 17 Jan 2025 08:12:27 -0800
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Fri, 17 Jan 2025 08:12:24 -0800
MIME-Version: 1.0 (Mimestream 1.5.0)
References: <RT-Ticket-1410981@icann.org> <rt-5.0.3-873023-1736906767-999.1410981-9-0@icann.org> <rt-5.0.3-1093986-1736981576-467.1410981-9-0@icann.org> <CAHBU6ium09jXBMp+BG+HkBcKJNk-LsA--OX5BxtHoEtZnWmvyA@mail.gmail.com> <2AB1F20E-71F5-4D55-904D-E84182A522E7@verisign.com>
In-Reply-To: <2AB1F20E-71F5-4D55-904D-E84182A522E7@verisign.com>
From: Tim Bray <tbray@textuality.com>
Date: Fri, 17 Jan 2025 08:12:27 -0800
X-Gm-Features: AbW1kvZFdPuW7joF1QnfmYuN72U4GFKkJ2z-fIuhMcNLlpJG7otHh57V8LmF61Y
Message-ID: <CAHBU6it6L=RJuspy7TvDW_mbWC6QPsH0QRrYgbnqVxy+dmei6g@mail.gmail.com>
To: "Gould, James" <jgould@verisign.com>
Content-Type: multipart/alternative; boundary="000000000000532dce062be92d54"
Message-ID-Hash: AEIEVDRI4HSEKVBBGT3DWBW2FTTNTJFU
X-Message-ID-Hash: AEIEVDRI4HSEKVBBGT3DWBW2FTTNTJFU
X-MailFrom: tbray@textuality.com
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: "mt@lowentropy.net" <mt@lowentropy.net>, "regext@ietf.org" <regext@ietf.org>, "drafts-expert-review-comment@iana.org" <drafts-expert-review-comment@iana.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Re: [IANA #1410981] expert review for draft-ietf-regext-epp-eai (xml-registry)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/xig8QwY0IgW0-t42bPEX9huVrMM>
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>
On Jan 17, 2025 at 6:22:32 AM, "Gould, James" <jgould@verisign.com> wrote: > Tim, > > > > Thank you for the review. In your note, is the concern that the namespace > prefix is being used for the element name (e.g., “addlEmail”)? I found > similar definitions in the following EPP RFCs, which are broadly > implemented: > > > > · EPP RFC 5730 with xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" > and <element name="epp" type="epp:eppType"/>. > No, the element name is fine, it’s the value of the “type” attribute that is troublesome. The namespace prefix “epp" is really only designed to prefix element & attribute names, not to be used inside the element content or the attribute value. There aren’t any standards (afaik) that require a standard off-the-shelf XML processor to make those prefix/URI mappings available. For example, would you expect this to work? <something xmlns:foo="urn:ietf:params:xml:ns:epp-1.0”><element name="epp" type=“foo:eppType”/> I mean, it’s probably OK, enough people do this that most XML software can handle it. It’s just that as the designated XML pedant, I feel I should point out departures from the letter of the standard. -T
- [regext] [IANA #1410981] expert review for draft-… David Dong via RT
- [regext] Re: [IANA #1410981] expert review for dr… Tim Bray
- [regext] Re: [IANA #1410981] expert review for dr… Gould, James
- [regext] Re: [IANA #1410981] expert review for dr… Tim Bray
- [regext] Re: [IANA #1410981] expert review for dr… Hollenbeck, Scott
- [regext] Re: [IANA #1410981] expert review for dr… Tim Bray
- [regext] Re: [IANA #1410981] expert review for dr… Gould, James
- [regext] Re: [IANA #1410981] expert review for dr… Tim Bray
- [regext] Re: [IANA #1410981] expert review for dr… Hollenbeck, Scott