Hi Gavin,
On 18.11.2022 12:42, Gavin Brown wrote:
Hi all,
A couple of days ago I uploaded a new version draft-regext-brown-epp-ttl.
This version adds a new extension element, , which specifies
the date and time after which a "custom" TTL should revert to the default.
Feedback welcome - I
Gavin,
How about providing the feature for the client to unset the custom TTL via an
empty element instead of adding a new element that would
require the server to manage the expiry? This way the client is in complete
control over exactly when the custom TTL value is in place. The ability
> -Original Message-
> From: Mario Loffredo
> Sent: Friday, November 18, 2022 6:59 AM
> To: Pawel Kowalik ; Hollenbeck, Scott
> ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Web Service Client Flow
>
> Caution: This email originated from outside the organization. Do not click
>
Il 18/11/2022 12:19, Pawel Kowalik ha scritto:
Hi Scott,
Am 17.11.22 um 20:26 schrieb Hollenbeck, Scott:
The RDAP Web Service Client sends queries that require user
identification, authentication, and authorization to an RDAP server
that include the ID Token in an HTTP bearer authorization
Hi all,
A couple of days ago I uploaded a new version draft-regext-brown-epp-ttl.
This version adds a new extension element, , which specifies the
date and time after which a "custom" TTL should revert to the default.
Feedback welcome - I am hoping the WG will be able to pick this document up
Hi Scott,
Am 17.11.22 um 20:26 schrieb Hollenbeck, Scott:
The RDAP Web Service Client sends queries that require user
identification, authentication, and authorization to an RDAP server
that include the ID Token in an HTTP bearer authorization header.
[PK] The client should never be sending
