IETF Logo Mail Archive

[regext] Re: Review of draft-ietf-regext-rdap-versioning, draft-ietf-regext-rdap-x-media-type, and draft-ietf-regext-rdap-extensions

"Andrew Newton (andy)" <andy@hxr.us> Tue, 27 August 2024 18:09 UTC

Return-Path: <andy@hxr.us>
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 76056C1D876D for <regext@ietfa.amsl.com>; Tue, 27 Aug 2024 11:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20230601.gappssmtp.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 3OamNDtzRU1S for <regext@ietfa.amsl.com>; Tue, 27 Aug 2024 11:09:14 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 8ADF1C1D8759 for <regext@ietf.org>; Tue, 27 Aug 2024 11:09:14 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-e1161ee54f7so6241292276.2 for <regext@ietf.org>; Tue, 27 Aug 2024 11:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1724782153; x=1725386953; darn=ietf.org; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=E1ju0UpzsUMQXZFclh6+AffMSKoJ92xsg5kiRYt1NnQ=; b=C3BkW5VC0xrcOvvTaoFq/RCPOq/uruu+rBuhJlmUpCB03YFikbEZl8K74FlGi0p1Xy jy9hMAzlVSqjTNSFFVhL72NXyFXExbOpzSJugQgZtZWFfg0KFCoZVQY8UDCEaXWNpfiM l4p/1jAQ02cf+6uZerJ3b3PShsBXNggcAJnjFzGaQDvqsTjwcJGzPlbX7th0W7bHxCDF yIgEeR2yFtLbOjCs1LGBeqX+QdSuErbCo2RKum/2T3hDCJDeQQnYskvNyLFW7vM7ComN tzdKFiJYCbvEh/aqc3BYSS8Ptz0BAKuLA+EvYzT/SuRtOo9yMY6jsc3Hh2FPHmh7DE0N W35Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724782153; x=1725386953; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=E1ju0UpzsUMQXZFclh6+AffMSKoJ92xsg5kiRYt1NnQ=; b=lpZQch0pZCUOraczUpq3ugc6IKrXaEagcb0/OOTKNoxCWjGyK9AwpwrNXaW0SL558f DfRLvJ1SK5oQwFL+HupPo58eoENEH5lKUTbUdUbx5LBP6j5oO6k8jetv704yTdedhywv 4xXqPzjgm8iJkyY8mkd25PEvpfWY+wIn+iiUzD/sGL36LeR/CncQX+/ifwGs73mIBKBT 7JhXh8DJy4OIVR7pVCyvXNy+98ODTxBfWMWZxFj07D0wSvSgZ9EUQWd6Fr6eUtEvH1e+ 2CWSBDO8lEmvu/6SvJ3efbNHoid+8RfmIyNhmiHpPpb7CfHZAGzsp2ZxsS2LGGmorGv4 noxA==
X-Forwarded-Encrypted: i=1; AJvYcCVvcVRjaica8wkJatgDOamNv1fv9muKsINEAtRIgB5Ze9OC6UWTUtp4HdMsn8JsekqiyLpjoAs=@ietf.org
X-Gm-Message-State: AOJu0YyURhCavDjW03BJ5nZUy2Ab6dzOiLN8nSkRSkcmpkmw6k8GaA2W G20PMbx+srZHclmwccMvpesK8lBoCth+knVgae/5rT54mm005zQXJK8THzwfmlQ=
X-Google-Smtp-Source: AGHT+IHq2ukpHj93wZBpnFczjzFzRsGofrlJ77sQdQ2TfamvCKAlSztZj9EK4OEFemxiyKQVSGwOlw==
X-Received: by 2002:a05:6902:1893:b0:e13:d86c:7f6 with SMTP id 3f1490d57ef6-e17a866394cmr16882644276.36.1724782153218; Tue, 27 Aug 2024 11:09:13 -0700 (PDT)
Received: from [10.2.8.160] (pool-72-83-25-32.washdc.fios.verizon.net. [72.83.25.32]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e178def4afasm2546555276.0.2024.08.27.11.09.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 27 Aug 2024 11:09:12 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------QdkzfWe6xX9z5ZM3HGOE6KkC"
Message-ID: <bc73ab2a-3a6a-497a-b572-44abf74b07c0@hxr.us>
Date: Tue, 27 Aug 2024 14:09:11 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Gould, James" <jgould=40verisign.com@dmarc.ietf.org>, "jasdips@arin.net" <jasdips@arin.net>, "regext@ietf.org" <regext@ietf.org>
References: <5BE870CA-3D80-4888-9C5F-7F4FC33A008F@verisign.com>
Content-Language: en-US
From: "Andrew Newton (andy)" <andy@hxr.us>
In-Reply-To: <5BE870CA-3D80-4888-9C5F-7F4FC33A008F@verisign.com>
Message-ID-Hash: DJHADIRZXFM2TWNRUIP7REGUJHEAF4N5
X-Message-ID-Hash: DJHADIRZXFM2TWNRUIP7REGUJHEAF4N5
X-MailFrom: andy@hxr.us
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: Review of draft-ietf-regext-rdap-versioning, draft-ietf-regext-rdap-x-media-type, and draft-ietf-regext-rdap-extensions
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/IMdNX6g0yaQbjE1FStVcfa7V9qo>
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 James,

On 8/26/24 11:58, Gould, James wrote:
> I have an issue with the “Query Parameters Considered Harmful” section 
> in draft-ietf-regext-rdap-x-media-type, where query parameters are 
> used in the base RDAP RFCs as well as other RDAP extensions including 
> the Versioning Extension.  If use of query parameters should be 
> discouraged in RDAP, it should be moved from 
> draft-ietf-regext-rdap-x-media-type to 
> draft-ietf-regext-rdap-extensions.  I personally don’t agree that the 
> use of query parameters in RDAP should be considered “harmful”, but it 
> can be pointed out in draft-ietf-regext-rdap-extensions that query 
> parameters may not be preserved via redirects.  An author of an RDAP 
> extension that has the need for client input can take into 
> consideration that query parameters may not be presented via redirects 
> while creating the extension.  I don’t view this as unique to the 
> passing of the desired set of extensions in the RDAP query.

I see your point here. That language should be changed because it is too 
broad. I put an issue for that in the tracker [1]. Also, it needs to 
point to the language in the rdap-extensions draft.

WRT to normative use of the versioning extension, I have a tracking 
issue here [2].


-andy



[1] 
https://github.com/anewton1998/draft-regext-ext-json-media-type/issues/30

[2] 
https://github.com/anewton1998/draft-regext-ext-json-media-type/issues/31

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