IETF Logo Mail Archive

Re: [regext] IANA Considerations in draft-ietf-regext-rdap-reverse-search

Patrick Mevzek <pm@dotandco.com> Fri, 31 July 2020 14:34 UTC

Return-Path: <pm@dotandco.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 74BC43A0E18 for <regext@ietfa.amsl.com>; Fri, 31 Jul 2020 07:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level:
X-Spam-Status: No, score=-2.12 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=owQGU6ib; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ach9Ou9Y
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QqcK8-igkGT0 for <regext@ietfa.amsl.com>; Fri, 31 Jul 2020 07:34:22 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB4EE3A1160 for <regext@ietf.org>; Fri, 31 Jul 2020 07:34:12 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id DFC5D5C007B for <regext@ietf.org>; Fri, 31 Jul 2020 10:34:11 -0400 (EDT)
Received: from imap22 ([10.202.2.72]) by compute3.internal (MEProxy); Fri, 31 Jul 2020 10:34:11 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=oupj4WSAy/iQ5ftBaTSG/2XwmSymUz1 765rpB5XkRB0=; b=owQGU6ibPUNC/3l0wMgUVJ1X23CUbfM6Ak7AdppnUvvfQ5W IF4A5fU75lEWoUqVbZKeMoQYqvFL7Cqa3Rszm83MrW28fKR75YI6h+eotebKw1+W SgVPLl2/FvA4JSOwStrxG2jpDa13+NBiAwhBCiwHpx6mgaWTf5cFbGL9/Uhp8gjR hrdpOqqzOTy2YUQEqHaNrS2+h1acNr6DmrOhlNevhie7a/7gbiFPkYQKwleV5atA vWbeyEBGpJHTMvYiq2kHFMqXWYvg9zqu48P2IEufHjRoifpU0ZVKZy7ztguoBvv8 +2r5xmdEY/qWhjw3sLFuWrYBHyGMbo4L7uCGx7Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=oupj4W SAy/iQ5ftBaTSG/2XwmSymUz1765rpB5XkRB0=; b=ach9Ou9YXkO06jd69bAfx5 qCwcB4geHj0pnV2mfyJfqixRgL7DisPnVBunUBPyfrBvbSWvubN4AD/bY9TVr0xI /1NYqqu3z1kGUPMC1MR/GgqACoKsWfpPzQow1Ejh+GAupv3HD0uqw/49i6VLT3kZ cjspFxhpgHF/c0+5UCJlDKcyY0cAokAVVIo9yctX9Bjm4iezWiCgpdhVjXXyP0Y2 A1HTEQExIFFvRuAdcpDT9orOMOXGjCffkIwR49UOiZ747yRn9U+otkzgCxHJewZV PIbxVrW7KxlSprCQvZU2q4udILl1CtSvof9Huvhdsia1E8e2hpKrMQ2j7tYduZrQ ==
X-ME-Sender: <xms:4yskX-RDkXOIlMxltgPGJv0HTX8J_Qimwy2WwXK7qNVHDW7vPJAzIdUX7dQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrieekgdejkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreerjeenucfhrhhomhepfdfrrghtrhhitghkucfovghviigvkhdfuceophhmseguohht rghnuggtohdrtghomheqnecuggftrfgrthhtvghrnhepfeeuueeifeffvdelueevhfetud fgheejveejteefudfhvefgledthfegheejheevnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepphhmseguohhtrghnuggtohdrtghomh
X-ME-Proxy: <xmx:4yskXzzc_k0Vt0-mgevFgk5dBqJuqlsSl5SY1p7xfw5kjZa3rlFKBA> <xmx:4yskX70FEjamudQPzOf3Koq6Ds_QgqXSx3vWvEYwqIfxeWtx-KXV6g> <xmx:4yskX6Cr86uY8zTXRKbS5ZzDUOmbUy2GeiJ8vDk9xECLaapDOPyMGw> <xmx:4yskX2Rwi8I3zreoB461uRD0V4ZAwPaRRYwQLJnP7d5pgMekUYuAzg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2C8B56680078; Fri, 31 Jul 2020 10:34:11 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-128-gd51a832-fm-20200728.001-gd51a8328
Mime-Version: 1.0
Message-Id: <0f361bcb-cd2d-4336-8f71-f06f72430e48@www.fastmail.com>
In-Reply-To: <df404a43-8284-5466-7d83-88e27d5691ef@iit.cnr.it>
References: <1cb2fde4261748afa8163333d090b84a@verisign.com> <df404a43-8284-5466-7d83-88e27d5691ef@iit.cnr.it>
Date: Fri, 31 Jul 2020 09:33:49 -0500
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/LbMvs6-7aXqVH6nTOoLx6tqWUlo>
Subject: Re: [regext] IANA Considerations in draft-ietf-regext-rdap-reverse-search
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2020 14:34:24 -0000

On Fri, Jul 31, 2020, at 08:02, Mario Loffredo wrote:
> Furthermore, my opinion is that Section 4.1 of RFC7483bis should be 
> updated to treat this use case. I mean, a server should signal in 
> rdapConformance not only the extensions used in building the response 
> but all the supported features.

I am not sure to agree.

A server could advertise everything it supports in some reply to an help query
or another one that could be created, as a generic advertisement of features.

But I believe a specific reply (message) should just list what pertains to this specific reply.

Considering that, in the future, for the same query, the reply can be different based on the client and its level of access.

-- 
  Patrick Mevzek
  pm@dotandco.com

v2.23.0 | Report a Bug | By Email