Return-Path: <mario.loffredo@iit.cnr.it>
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 089BE1208B4
 for <regext@ietfa.amsl.com>; Fri, 20 Dec 2019 03:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
 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 cKq32Ow_PHq7 for <regext@ietfa.amsl.com>;
 Fri, 20 Dec 2019 03:30:11 -0800 (PST)
Received: from smtp.iit.cnr.it (mx4.iit.cnr.it [146.48.98.151])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 7C89A120088
 for <regext@ietf.org>; Fri, 20 Dec 2019 03:30:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
 by smtp.iit.cnr.it (Postfix) with ESMTP id 283BAB80A7B
 for <regext@ietf.org>; Fri, 20 Dec 2019 12:30:08 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mx4.iit.cnr.it
Received: from smtp.iit.cnr.it ([127.0.0.1])
 by localhost (mx4.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id EGKJQ3Ias-w3 for <regext@ietf.org>;
 Fri, 20 Dec 2019 12:30:05 +0100 (CET)
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 58820B8018C
 for <regext@ietf.org>; Fri, 20 Dec 2019 12:30:05 +0100 (CET)
References: <157684120749.27347.11479578748472034188.idtracker@ietfa.amsl.com>
To: "regext@ietf.org" <regext@ietf.org>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
X-Forwarded-Message-Id: <157684120749.27347.11479578748472034188.idtracker@ietfa.amsl.com>
Message-ID: <92681df8-1d89-588b-377e-592b48d9e819@iit.cnr.it>
Date: Fri, 20 Dec 2019 12:28:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <157684120749.27347.11479578748472034188.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative;
 boundary="------------EF64B5D470AE37FC25E0D9EE"
Content-Language: it
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/TBNm4xzw2RetKRqvXOIuEcit8f8>
Subject: [regext] Fwd: New Version Notification for
 draft-ietf-regext-rdap-sorting-and-paging-07.txt
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, 20 Dec 2019 11:30:14 -0000

This is a multi-part message in MIME format.
--------------EF64B5D470AE37FC25E0D9EE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi folks,

I just published a new version including a section about paging 
responses to POST requests.


Best,

mario



-------- Messaggio Inoltrato --------
Oggetto: 	New Version Notification for 
draft-ietf-regext-rdap-sorting-and-paging-07.txt
Data: 	Fri, 20 Dec 2019 03:26:47 -0800
Mittente: 	internet-drafts@ietf.org
A: 	Maurizio Martinelli <maurizio.martinelli@iit.cnr.it>, Scott 
Hollenbeck <shollenbeck@verisign.com>, Mario Loffredo 
<mario.loffredo@iit.cnr.it>




A new version of I-D, draft-ietf-regext-rdap-sorting-and-paging-07.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.

Name: draft-ietf-regext-rdap-sorting-and-paging
Revision: 07
Title: Registration Data Access Protocol (RDAP) Query Parameters for 
Result Sorting and Paging
Document date: 2019-12-20
Group: regext
Pages: 25
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-sorting-and-paging-07.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/
Htmlized: 
https://tools.ietf.org/html/draft-ietf-regext-rdap-sorting-and-paging-07
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-sorting-and-paging
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-sorting-and-paging-07

Abstract:
The Registration Data Access Protocol (RDAP) does not include core
functionality for clients to provide sorting and paging parameters
for control of large result sets. This omission can lead to
unpredictable server processing of queries and client processing of
responses. This unpredictability can be greatly reduced if clients
can provide servers with their preferences for managing large
responses. This document describes RDAP query extensions that allow
clients to specify their preferences for sorting and paging result
sets.



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


--------------EF64B5D470AE37FC25E0D9EE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi folks,</p>
    <p>I just published a new version including a section about paging
      responses to POST requests.</p>
    <p><br>
    </p>
    <p>Best,</p>
    <p>mario<br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Messaggio Inoltrato --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Oggetto:
            </th>
            <td>New Version Notification for
              draft-ietf-regext-rdap-sorting-and-paging-07.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Data: </th>
            <td>Fri, 20 Dec 2019 03:26:47 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Mittente:
            </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">A: </th>
            <td>Maurizio Martinelli
              <a class="moz-txt-link-rfc2396E" href="mailto:maurizio.martinelli@iit.cnr.it">&lt;maurizio.martinelli@iit.cnr.it&gt;</a>, Scott Hollenbeck
              <a class="moz-txt-link-rfc2396E" href="mailto:shollenbeck@verisign.com">&lt;shollenbeck@verisign.com&gt;</a>, Mario Loffredo
              <a class="moz-txt-link-rfc2396E" href="mailto:mario.loffredo@iit.cnr.it">&lt;mario.loffredo@iit.cnr.it&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <br>
      A new version of I-D,
      draft-ietf-regext-rdap-sorting-and-paging-07.txt<br>
      has been successfully submitted by Mario Loffredo and posted to
      the<br>
      IETF repository.<br>
      <br>
      Name: draft-ietf-regext-rdap-sorting-and-paging<br>
      Revision: 07<br>
      Title: Registration Data Access Protocol (RDAP) Query Parameters
      for Result Sorting and Paging<br>
      Document date: 2019-12-20<br>
      Group: regext<br>
      Pages: 25<br>
      URL:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-sorting-and-paging-07.txt">https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-sorting-and-paging-07.txt</a><br>
      Status:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/">https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/</a><br>
      Htmlized:
      <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-regext-rdap-sorting-and-paging-07">https://tools.ietf.org/html/draft-ietf-regext-rdap-sorting-and-paging-07</a><br>
      Htmlized:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-sorting-and-paging">https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-sorting-and-paging</a><br>
      Diff:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-sorting-and-paging-07">https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-sorting-and-paging-07</a><br>
      <br>
      Abstract:<br>
      The Registration Data Access Protocol (RDAP) does not include core<br>
      functionality for clients to provide sorting and paging parameters<br>
      for control of large result sets. This omission can lead to<br>
      unpredictable server processing of queries and client processing
      of<br>
      responses. This unpredictability can be greatly reduced if clients<br>
      can provide servers with their preferences for managing large<br>
      responses. This document describes RDAP query extensions that
      allow<br>
      clients to specify their preferences for sorting and paging result<br>
      sets.<br>
      <br>
      <br>
      <br>
      Please note that it may take a couple of minutes from the time of
      submission<br>
      until the htmlized version and diff are available at
      tools.ietf.org.<br>
      <br>
      The IETF Secretariat<br>
      <br>
    </div>
  </body>
</html>

--------------EF64B5D470AE37FC25E0D9EE--

