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 3E93D3A090A for ; Tue, 14 Apr 2020 08:00:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Cy3kL1qlG7-D for ; Tue, 14 Apr 2020 08:00:08 -0700 (PDT) Received: from smtp.iit.cnr.it (mx3.iit.cnr.it [146.48.98.150]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 969FE3A0909 for ; Tue, 14 Apr 2020 08:00:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id 32D486002CD for ; Tue, 14 Apr 2020 17:00:06 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mx3.iit.cnr.it Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx3.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBqkEU7qzGAC for ; Tue, 14 Apr 2020 17:00:03 +0200 (CEST) Received: from [192.12.193.108] (pc-loffredo.nic.it [192.12.193.108]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by smtp.iit.cnr.it (Postfix) with ESMTPSA id 2D0D760010A for ; Tue, 14 Apr 2020 17:00:03 +0200 (CEST) References: <158687617908.27110.2068674518703704745@ietfa.amsl.com> To: "regext@ietf.org" From: Mario Loffredo X-Forwarded-Message-Id: <158687617908.27110.2068674518703704745@ietfa.amsl.com> Message-ID: <2bf95c43-1b3d-b10c-2e20-84f173271e28@iit.cnr.it> Date: Tue, 14 Apr 2020 16:57:41 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <158687617908.27110.2068674518703704745@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------2A16A425F336A692FD63B97A" Content-Language: it Archived-At: Subject: [regext] Fwd: New Version Notification for draft-ietf-regext-rdap-partial-response-09.txt X-BeenThere: regext@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Registration Protocols Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 15:00:18 -0000 This is a multi-part message in MIME format. --------------2A16A425F336A692FD63B97A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I just published a new version fixing a minor issue raised by Jasdip. I apologize. Best, Mario -------- Messaggio Inoltrato -------- Oggetto: New Version Notification for draft-ietf-regext-rdap-partial-response-09.txt Data: Tue, 14 Apr 2020 07:56:19 -0700 Mittente: internet-drafts@ietf.org A: Mario Loffredo , Maurizio Martinelli A new version of I-D, draft-ietf-regext-rdap-partial-response-09.txt has been successfully submitted by Mario Loffredo and posted to the IETF repository. Name: draft-ietf-regext-rdap-partial-response Revision: 09 Title: Registration Data Access Protocol (RDAP) Partial Response Document date: 2020-04-14 Group: regext Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-partial-response-09.txt Status: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/ Htmlized: https://tools.ietf.org/html/draft-ietf-regext-rdap-partial-response-09 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-partial-response Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-partial-response-09 Abstract: The Registration Data Access Protocol (RDAP) does not include capabilities to request partial responses. In fact, according to the user authorization, the server can only return full responses. A partial response capability, especially in the case of search queries, could bring benefits to both clients and servers. This document describes an RDAP query extension that allows clients to specify their preference for obtaining a partial response. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --------------2A16A425F336A692FD63B97A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

I just published a new version fixing a minor issue raised by Jasdip.

I apologize.

Best,

Mario

-------- Messaggio Inoltrato --------
Oggetto: New Version Notification for draft-ietf-regext-rdap-partial-response-09.txt
Data: Tue, 14 Apr 2020 07:56:19 -0700
Mittente: internet-drafts@ietf.org
A: Mario Loffredo <mario.loffredo@iit.cnr.it>, Maurizio Martinelli <maurizio.martinelli@iit.cnr.it>



A new version of I-D, draft-ietf-regext-rdap-partial-response-09.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.

Name: draft-ietf-regext-rdap-partial-response
Revision: 09
Title: Registration Data Access Protocol (RDAP) Partial Response
Document date: 2020-04-14
Group: regext
Pages: 14
URL: https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-partial-response-09.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/
Htmlized: https://tools.ietf.org/html/draft-ietf-regext-rdap-partial-response-09
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-partial-response
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-partial-response-09

Abstract:
The Registration Data Access Protocol (RDAP) does not include
capabilities to request partial responses. In fact, according to the
user authorization, the server can only return full responses. A
partial response capability, especially in the case of search
queries, could bring benefits to both clients and servers. This
document describes an RDAP query extension that allows clients to
specify their preference for obtaining a partial response.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--------------2A16A425F336A692FD63B97A--