--- 1/draft-ietf-regext-rdap-openid-04.txt	2020-07-13 07:14:14.662510514 -0700
+++ 2/draft-ietf-regext-rdap-openid-05.txt	2020-07-13 07:14:14.726511360 -0700
@@ -1,19 +1,19 @@
 
 REGEXT Working Group                                       S. Hollenbeck
 Internet-Draft                                             Verisign Labs
-Intended status: Standards Track                        January 16, 2020
-Expires: July 19, 2020
+Intended status: Standards Track                           July 13, 2020
+Expires: January 14, 2021
 
    Federated Authentication for the Registration Data Access Protocol
                       (RDAP) using OpenID Connect
-                    draft-ietf-regext-rdap-openid-04
+                    draft-ietf-regext-rdap-openid-05
 
 Abstract
 
    The Registration Data Access Protocol (RDAP) provides "RESTful" web
    services to retrieve registration metadata from domain name and
    regional internet registries.  RDAP allows a server to make access
    control decisions based on client identity, and as such it includes
    support for client identification features provided by the Hypertext
    Transfer Protocol (HTTP).  Identification methods that require
    clients to obtain and manage credentials from every RDAP server
@@ -31,21 +31,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on July 19, 2020.
+   This Internet-Draft will expire on January 14, 2021.
 
 Copyright Notice
 
    Copyright (c) 2020 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -1154,20 +1154,21 @@
    01:  Modified ID Token delivery approach to note proper use of an
       HTTP bearer authorization header.
    02:  Modified token delivery approach (access token is the bearer
       token) to note proper use of an HTTP bearer authorization header,
       fixing the change made in -01.
    03:  Updated OAuth 2.0 Device Authorization Grant description and
       reference due to publication of RFC 8628.
    04:  Updated OAuth 2.0 token exchange description and reference due
       to publication of RFC 8693.  Corrected the RDAP conformance
       identifier to be registered with IANA.
+   05:  Keepalive refresh.
 
 Author's Address
 
    Scott Hollenbeck
    Verisign Labs
    12061 Bluemont Way
    Reston, VA  20190
    USA
 
    Email: shollenbeck@verisign.com