Good Morning,
Thanks for the nudge Patrick, I had the minutes in my drafts folder from right
after the meeting and forgot to get them out before taking off for a couple
weeks. I will get these notes cleaned up and sent out today.
Thanks
Roger
-Original Message-
From: regext On Behalf
On Tue, Jul 2, 2019, at 06:57, Gavin Brown wrote:
> It's worth noting that there are "operational practices" RFCs (6781
> being the obvious example)
Yes, but they do not force any kind of specific policies.
They give recommendations and points to be taken into account, for sane choices.
For
Hi Mario,
I like JSContact and the current draft certainly looks good enough to be usable
in RDAP. I imagine more work will be needed before JSContact will have feature
parity with vCard/jCard.
I would be happy to publish a new version of draft-brown-epp-contacts-in-rdap
which uses JSContact r
It's worth noting that there are "operational practices" RFCs (6781 being the
obvious example) that do not describe a protocol, and are published as
Informational documents. This document seems more like those than a protocol
specification.
G.
> On 2 Jul 2019, at 06:56, Patrick Mevzek wrote:
On Fri, Jun 21, 2019, at 08:22, Antoin Verschuren wrote:
> We believe the draft draft-ietf-regext-login-security still has an open
> issue from Patrick Meczek where James response should be confirmed, but
I have reviewed past exchanges and I do not think that there is anything open
left:
I r
Hi all,
I would like to invite you to take a look at this document:
https://tools.ietf.org/html/draft-stepanek-jscontact-03
It aims to define a JSON representation of contact information that
fixes the issues with jCard deserialization and, at the same time,
expands vCard semantics.
Just t
