This is a neat idea,
Is there a reasoning or use case for such need?
One of the challenges that I see, is that knowing the server address is one
thing, but generally clients (registrars) keep the connections open for a long
period of time, so the need to reduce the connection speed may not be a
Hi Mario,
Response inline.
On 31 Mar 2022, at 13:03, Mario Loffredo wrote:
Hi Francisco,
appreciated but:
1) The ssl variables in NGINX are different.
Yes, they usually are :-)
2) Even supposing to extract CN or SAN, as it seems one should do in
NGINX via a regular expression, it does
th-nginx>
Best,
Mario
Il 31/03/2022 19:36, Francisco Obispo ha scritto:
In a scenario where a proxy/load balancer is terminating the TLS
connection, it will most likely need to extract the certificate
information, and encode it into a HTTP header, so that the backend
could later tie the |clI
In a scenario where a proxy/load balancer is terminating the TLS
connection, it will most likely need to extract the certificate
information, and encode it into a HTTP header, so that the backend could
later tie the `clID` with the certificate in a way (i.e.: `cn`).
That's what I would do, to
ully they’ll
fix it.
Sending an *error* code requires the client to implement some sort of
rate-limiting awareness making it non-trivial, whereas a delayed server
response is handled automatically in most cases.
Best,
Francisco Obispo
VP - Technology
Uniregistry
400 Spe
availability check or reason why the object is not available, should
be mandated by policy and not in anyway by limitations of the protocol.
Best regards,
—
Francisco Obispo
Uniregistry Inc.
On 16 Dec 2016, at 9:22, Gould, James wrote:
> That is one of my concerns, RDAP is a lookup protocol
registry policy / contract, it
should be a different issue.
regards
—
Francisco Obispo
Uniregistry Inc.
On 16 Dec 2016, at 3:34, Andrew Newton wrote:
> This topic keeps appearing over and over again, so Marcos and I
> decided to address it.
> As it turns out, there's not much nee
der address rejected: Blocked for spam, please
see http://www.ietf.org/secretariat.html (in reply to RCPT TO command)
```
On 7 Dec 2016, at 15:51, Francisco Obispo wrote:
> Hi *,
>
> In my opinion, in order for RDAP to be successful, those use cases will have
> to be taken in
ions.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
___
regext mailing list
regext@ietf.org
h
