Luconi Trombacchi
, Lorenzo Trombacchi
, Marcin Machnio , Mario
Loffredo , Maurizio Martinelli
A new version of I-D, draft-loffredo-regext-epp-over-http-02.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-loffredo-regext-epp-over-http
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://
Hi Scott,
Il 16/06/2022 15:30, Hollenbeck, Scott ha scritto:
-Original Message-
From: regext On Behalf Of Mario Loffredo
Sent: Thursday, June 16, 2022 2:57 AM
To: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] OK, What Next? (was RDAP Extensions
Approach Analysis v2)
Caution: This
il and delete it immediately.
[ Antes de imprimir esta mensagem pense no ambiente. Before printing
this message, think about environment ]
Às 08:28 de 14/06/22, Mario Loffredo escreveu:
Hi folks,
in view of the panel about epp-over-http at next ROW, I just
published version -02.
In addition to hav
Sorry, I forgot to reply to all ;-)
Messaggio Inoltrato
Oggetto: Re: [regext] Fwd: New Version Notification for
draft-loffredo-regext-epp-over-http-02.txt
Data: Fri, 24 Jun 2022 18:11:37 +0200
Mittente: Mario Loffredo
A: Patrick Mevzek
Hi Patrick,
thanks
ust my personal views of course.
--
Patrick Mevzek
p...@dotandco.com
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
D
.com%2Fs%2F5kk9CERmYxi37AlSP2r_h%3Fdomain%3Dverisigninc.com%2F&data=05%7C01%7Crcarney%40godaddy.com%7Cf7f575f03b434a22320808da55ffe472%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637916855724654440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7
hanged to
"lunarNIC_level_0" if that's preferred. Andy and I believe that the
original
intent was for the values to be consistent, and this change would also
align
with use of "rdap_level_0".
> -Original Message-
> From: regext O
d into responses, conformance to those custom
specifications MUST be indicated by including a unique string
literal value
registered in the IANA RDAP Extensions registry specified in
[RFC7480]".
That's clear linkage.
I've said earlier that the errata change to 9083 co
thout an active session is
processed differently than the "login followed by a login" situation. Is that
really the best course of action? I think consistent behavior would be
preferred.
Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.o
gin
> received
> while a session is active, but the other command sequences present
> problems.
> As you described above, a logout received without an active session is
> processed differently than the "login followed by a login"
situation. Is that
> really the best course of action? I th
seems to me harmful for both clients and servers.
Best,
Mario
Il 15/07/2022 14:13, Gould, James ha scritto:
Andy,
Thanks for weighing in on this. I provide my replies embedded below.
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT
Hi Scott,
please find my comments inline.
Il 18/07/2022 15:11, Hollenbeck, Scott ha scritto:
-Original Message-
From: Mario Loffredo
Sent: Monday, July 18, 2022 4:40 AM
To: Gould, James ; a...@hxr.us
Cc: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] OK, What
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Ital
Il 19/07/2022 19:34, Andrew Newton ha scritto:
On Tue, Jul 19, 2022 at 12:21 PM Mario Loffredo
wrote:
HI Andy,
In my opinion, it doesn't work when the extension is related to a
specification defined out of the RDAP context but is used in RDAP such
as JSContact or VCARD itself. In this
security experts.
I would suggest to explore another approach where a third-party
authority interconnects clients and servers that are mutually authenticated.
Best,
Mario
Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailma
-extension-identifier-and-rdapconformance/
RECORDING: https://www.meetecho.com/ietf114/recordings#REGEXT
Thanks,
Antoin and Jim
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit
Hi Scott,
lease find my comments below.
Il 09/08/2022 16:42, Hollenbeck, Scott ha scritto:
-Original Message-
From: Andrew Newton
Sent: Monday, August 1, 2022 4:31 PM
To: Mario Loffredo
Cc: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Federated Authentication
Gould, Marc Blanchet, Jasdip Singh, Scott
Hollenbeck, Andrew Newton, Mario Loffredo, Tom Harrison, Rick Wilhelm, Pawel
Kowalik.
Comments are still welcome. The CONSENSUS CALL will close later today.
Antoin and Jim
On 1 Aug 2022, at 9:49, James Galvin wrote:
As everyone knows there has been
: internet-dra...@ietf.org
A: Mario Loffredo , Maurizio Martinelli
A new version of I-D, draft-ietf-regext-rdap-reverse-search-13.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-reverse-search
Revision: 13
Title
mple, would it be fine for you If I changed the sentence to the
following?
To limit the impact of processing the search predicates, servers are
RECOMMENDED to make use of techniques to speed up the data retrieval in their
underlying data store such as indexes or similar.
Best,
Mario
"title": "Authenticated Response",
"description": [
"This is a response for an authenticated user"
]
}
Best,
Mario
-Tom
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/l
__
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:
Il 11/10/2022 15:04, Andrew Newton ha scritto:
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
my humble opinion is that this document shouldn't deal with any kind of RDAP
client other than a browser.
At the moment, I disagree with this. Authentication for non-browser
clients c
Hi Pavel,
please find me comments below.
Il 11/10/2022 17:42, Pawel Kowalik ha scritto:
Hi Mario,
Am 11.10.22 um 16:38 schrieb Mario Loffredo:
Il 11/10/2022 15:04, Andrew Newton ha scritto:
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
my humble opinion is that this document
. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
___
regext mailing list
onse MUST include a "farv1_session" data structure that
includes a "userClaims" object and a "sessionInfo" object.
to
..response MUST include a "farv1_session" data structure that includes
a "sessionInfo" object and an optional "userClaims&qu
xt mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.
document and publish a new
version.
Best,
Mario
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
rafts
directories.
This draft is a work item of the Registration Protocols Extensions WG of
the IETF.
Title : Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Authors : Mario Loffredo
Gavin Brown
Filename : draft-ietf-regext-rdap-jscontact-14.txt
Pages : 24
Dat
Hi Scott,
Il 2022-10-21 15:46 Hollenbeck, Scott ha scritto:
-Original Message-
From: Pawel Kowalik
Sent: Friday, October 21, 2022 5:18 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-
18.txt
Caution: This email ori
Hi Scott and Pavel,
please find my comments below.
Il 2022-10-24 16:57 Pawel Kowalik ha scritto:
Hi Scott,
Am 19.10.22 um 14:13 schrieb Hollenbeck, Scott:
1. How do we address web service clients?
[PK] I think the elements we need for web service clients were
already
elaborated in the disc
Hi Pavel,
please find my comments embedded below.
Il 26/10/2022 17:56, Pawel Kowalik ha scritto:
Am 26.10.22 um 15:48 schrieb Mario Loffredo:
[ML] Before going into detail with technical aspects, think we should
address some privacy implications connected with the following sentence:
RDAP
Il 28/10/2022 12:25, Pawel Kowalik ha scritto:
Am 28.10.22 um 11:35 schrieb Mario Loffredo:
[PK] The text was proposed in the way which does not exclude certain
valid use-cases but still allows the RDAP server to set its own
policy on sharing data.
This is clear that RDAP server is acting
Hi Pavel,
Il 29/10/2022 10:59, Pawel Kowalik ha scritto:
Hi Mario,
Am 28.10.22 um 16:36 schrieb Mario Loffredo:
[PK] There is quite relevant drawback from this scenario, that there
is no assurance the identity provided to the RDAP client by the IdP
would be the same as the one used towards
xt mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http:
m the on-line Internet-Drafts
directories.
This draft is a work item of the Registration Protocols Extensions WG of
the IETF.
Title : Registration Data Access Protocol (RDAP) Reverse search capabilities
Authors : Mario Loffredo
Maurizio Martinelli
Filename : draft-ietf-regext-rdap-reverse-sear
xt to the draft that describes OAuth-like token processing for
clients and servers that need that capability.
My preference is for the first option.
Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
e omitted and the
redaction method should be "removal".
Hope it could be helpful.
Best,
Mario
Il 10/11/2022 19:38, Gould, James ha scritto:
This is a formal request to start the WGLC for
draft-ietf-regext-rdap-redacted. There is a normative reference to
draft-ietf-jsonpath-bas
-annou...@ietf.org
CC: regext@ietf.org
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Registration Protocols Extensions WG
of the IETF.
Title : Registration Data Access Protocol (RDAP) Reverse search
capabilities
Authors
ly RS and RP, but it's unusual in the OpenID context.
In addition, the UserInfo endpoint (that the RDAP server can always
access) has been introduced by OpenID.
Best,
Mario
_______
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/l
Hi Scott,
Il 16/11/2022 14:37, Hollenbeck, Scott ha scritto:
-Original Message-
From: Mario Loffredo
Sent: Wednesday, November 16, 2022 2:31 AM
To: Hollenbeck, Scott ;
marc.blanc...@viagenie.ca; kowa...@denic.de
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] draft-ietf-regext
Hi Pawel,
thnks for your quick reply.
Il 16/11/2022 17:06, Pawel Kowalik ha scritto:
Hi Mario,
My feedback below.
Am 15.11.22 um 19:58 schrieb Mario Loffredo:
Hi Pawel,
thanks a lot for your review.
Please find my comments inline.
Il 15/11/2022 17:28, Pawel Kowalik ha scritto:
Hi
ss token" is
something other than the Access Token defined by OAuth? If so, it
sounds like
we need to design our own token format.
See above. RFC9068 defines such access tokens.
Kind Regards,
Pawel
___
regext mailing list
regext@ietf.org
https:
-rdap-reverse-search-16.txt
Data: Mon, 21 Nov 2022 07:20:08 -0800
Mittente: internet-dra...@ietf.org
A: Mario Loffredo , Maurizio Martinelli
A new version of I-D, draft-ietf-regext-rdap-reverse-search-16.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repos
Hi Tom,
thank you for your feedback.
Please find my comments below.
Il 22/11/2022 14:00, Tom Harrison ha scritto:
Hi Mario,
On Mon, Nov 21, 2022 at 04:40:28PM +0100, Mario Loffredo wrote:
With regard to the registration of the reverse search properties, I
have opted for adding entries in
Hi Tom,
please see my comments below prefixed by [ML2]
Il 24/11/2022 13:46, Tom Harrison ha scritto:
Hi Mario,
On Wed, Nov 23, 2022 at 09:42:56AM +0100, Mario Loffredo wrote:
Il 22/11/2022 14:00, Tom Harrison ha scritto:
On Mon, Nov 21, 2022 at 04:40:28PM +0100, Mario Loffredo wrote:
With
Hi Tom,
please find my comments below prefixed with ML3.
Il 27/11/2022 22:49, Tom Harrison ha scritto:
Hi Mario,
On Fri, Nov 25, 2022 at 02:18:35PM +0100, Mario Loffredo wrote:
Il 24/11/2022 13:46, Tom Harrison ha scritto:
This is the part I (still) don't follow, sorry. The fact tha
648 Section 3 and 4 offer
some guidance which we may reference to or adapt into this draft.
[ML] Sure, thanks. The recommendations in section 3 look like very
fitting to me.
Best,
Mario
Kind Regards,
Pawel
___
regext mailing list
r
Hi Pawel,
Il 28/11/2022 22:02, Pawel Kowalik ha scritto:
Hi Mario,
My comment inline.
Am 28.11.22 um 21:20 schrieb Mario Loffredo:
"A custom reverse search property MUST NOT collide with a
registered reverse
search property and MUST NOT match an RDAP property, or any of its
var
Hi Tom,
my comments below.
Il 28/11/2022 23:36, Tom Harrison ha scritto:
Hi Mario,
On Mon, Nov 28, 2022 at 07:19:20PM +0100, Mario Loffredo wrote:
Il 27/11/2022 22:49, Tom Harrison ha scritto:
On Fri, Nov 25, 2022 at 02:18:35PM +0100, Mario Loffredo wrote:
Even now there is no real way to
on" wrote:
Hi Mario,
On Mon, Nov 28, 2022 at 07:19:20PM +0100, Mario Loffredo wrote:
> Il 27/11/2022 22:49, Tom Harrison ha scritto:
>> On Fri, Nov 25, 2022 at 02:18:35PM +0100, Mario Loffredo wrote:
>>> Even now there is no real way to prevent co
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.lof
d now.
Should I ask for a new WGLC?
Will you do that?
Best,
Mario
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.c
Hi folks,
would like to invite everyone who is interested in implementing
JSContact in RDAP to provide feedback about the JSContact spec to the
CalExt list.
Any feedback/remark would be appreciated.
Best,
Mario
Messaggio Inoltrato
Oggetto:[calsify] Working Group La
osition of a
fixed length array" to provide the proper scope?
OK, now I get it. My proposal would be: "The Redaction by
Removal Method MUST NOT be used to remove an element of an
array where position of the elements in the array determines
semantic meaning of the eleme
Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
*From: *Mario Loffredo
*Date: *Tuesday, November 15, 2022 at 9:05 AM
*To: *James Gould , "regext@ietf.org"
*Subject: *[EXTERNAL] Re: [regext] Request WGLC for
draft-ietf-regext-rdap-redacted
Hi James,
so
tionally, it would be possible to register and then use a new
StreetComponent type value.
Please review and provide any feedback.
Thanks a lot in adavance,
Mario
Messaggio Inoltrato
Oggetto: New Version Notification for
draft-ietf-regext-rdap-jscontact-15.txt
Data: Sat, 10
case?
I'm OK with it. A new redaction method is surely much better than my
conservative proposal.
Mario
--
JG
*James Gould
*Fellow Engineer
jgo...@verisign.com
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
*From: *Mario Loff
Hi Andy,
thanks for your feedback.
Please find my comments inline.
Il 13/12/2022 15:27, Andrew Newton ha scritto:
Response in-line.
On Sat, Dec 10, 2022 at 4:41 AM Mario Loffredo
wrote:
Hi folks,
this new version is complaint with last JSContact spec. I also added a section
about
Hi Andy,
again my comments below
Il 13/12/2022 19:38, Andrew Newton ha scritto:
On Tue, Dec 13, 2022 at 12:12 PM Mario Loffredo
wrote:
The entity lookup URL MUST always be used regardless of the query generating
the response including the contact card.
Does it work for you?
JSContact says
that all their issues are now
addressed in version 17, so that the document shepherd can confirm
there are no new changes to be expected during WGLC?
Once we have confirmation, we will issue a 3th WGLC when the document
is stable.
Regards,
Jim and Antoin
Op 1 dec. 2022, om 14:2
@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
t determine whether there is the
need to cover the case of redacting a required JSON member in
draft-ietf-regext-rdap-redacted and if so how best to handle it.
Thanks,
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Researc
d information.
Best,
Mario
--
JG
James Gould
Fellow Engineer
jgo...@verisign.com
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
On 1/4/23, 4:58 AM, "Mario Loffredo" wrote:
Hi James,
honestly don't think that the &q
aches, the document should state that RDAP queries MUST be allowed
only to those users that can access the unredacted values of the
response fields the queries are based upon.
Best,
Mario
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT
Hi Scott,
Inviato da iPhone
> Il giorno 4 gen 2023, alle ore 18:24, Hollenbeck, Scott
> ha scritto:
>
>
>>
>> -Original Message-
>> From: regext On Behalf Of Mario Loffredo
>> Sent: Wednesday, January 4, 2023 11:33 AM
>> To: Gould, Jam
used regardless of the query generating the response including the
contact card.
Option 2) uid is required - uid must be inherently opaque and undecipherable
The JSCard "uid" property MUST be a URN in the UUID namespace [RFC4122]. If
the
uid value is generated starting from a reda
istent. Has there been push-back from calext on the idea of
making the uid OPTIONAL?
Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
I
Jan 10, 2023 at 4:39 AM Mario Loffredo
wrote:
Hi folks,
have discussed with Robert (the other JSContact co-author) about whether
to make uid optional in JSContact.
We have finally agreed that we need to keep it mandatory because, in
calext context, it's a fundamental requirement to ident
ation if the
mandatory constraint of the uid property can be worked around somehow.
Best,
Mario
Thanks,
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124
the protocol.
Kind Regards,
Pawel
_______
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Rese
invited to give his own preference..
Best,
Mario
Il 17/01/2023 08:12, Mario Loffredo ha scritto:
Hi Marc, Pawel and others,
as you may have known, I have asked CalExt for defining in JSContact
spec possible conditions where uid can be optional, for example the
use of JSContact in another
rences to drafts, but I'll see
what I can say about the issue.
Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Tele
Hi Scott,
please find my comments below.
Il 26/01/2023 20:10, Hollenbeck, Scott ha scritto:
-Original Message-
From: Mario Loffredo
Sent: Tuesday, January 24, 2023 9:57 AM
To: Hollenbeck, Scott ; jbern...@cofomo.com;
regext@ietf.org
Subject: [EXTERNAL] Re: [regext] I-D Action: draft
k provided by Julien Bernard and
Mario Loffredo. Please let me know if I missed anything or if you see anything
else that needs to be addressed.
[ML] Looks good to me.
Best,
Mario
Julien, I just realized that I missed adding your name in the "Acknowledgments"
section. I'l
Definitively, up to now we have used query parameter names that aren't
1:1 mapped to the response fields.
With regard to the "fn" reverse search property, have nothing to object
to rename it to further clarify the above concept.
Best,
Mario
-Tom
____
me as last IETF 115 meeting.
So if you intend to request for a presentation, please let the chairs know.
Regards,
Jim and Antoin
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological
: Mario Loffredo , Maurizio Martinelli
A new version of I-D, draft-ietf-regext-rdap-reverse-search-18.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-reverse-search
Revision: 18
Title: Registration Data Access Protocol (RDAP
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This Internet-Draft is a work item of the Registration Protocols
Extensions WG of the IETF.
Title : Registration Data Access Protocol (RDAP) Reverse search capabilities
Authors : Mario Loffredo
Maurizio Marti
reply or any comment from others.
Best,
Mario
Overall, this work has evolved pretty well. :)
Thanks,
Jasdip
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Hi Jasdip,
again my comments below
Il 09/03/2023 16:40, Jasdip Singh ha scritto:
Hi Mario,
On 3/9/23, 5:41 AM, "Mario Loffredo" mailto:mario.loffr...@iit.cnr.it>> wrote:
- Section 3: "Servers MUST NOT provide or implement unregistered reverse searches or
unregi
gh" mailto:regext-boun...@ietf.org> on behalf of jasd...@arin.net <mailto:jasd...@arin.net>>
wrote:
On 3/9/23, 12:34 PM, "Mario Loffredo" mailto:mario.loffr...@iit.cnr.it> <mailto:mario.loffr...@iit.cnr.it
<mailto:mario.loffr...@iit.cnr.it>>> wrote:
- S
A: Mario Loffredo , Maurizio Martinelli
A new version of I-D, draft-ietf-regext-rdap-reverse-search-20.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-reverse-search
Revision: 20
Title: Registration Data Access Protocol
: Mario Loffredo
A: regext@ietf.org
Hi everybody,
this new version addresses last feedback provided by Jasdip.
Best,
Mario
Messaggio Inoltrato
Oggetto: New Version Notification for
draft-ietf-regext-rdap-reverse-search-20.txt
Data: Fri, 10 Mar 2023 00:51:23
AP property.
Best,
Mario
Thanks.
-andy
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT
HI Andy,
again my comments below.
Il 20/03/2023 12:06, Andrew Newton ha scritto:
On Fri, Mar 17, 2023 at 10:45 AM Mario Loffredo
wrote:
1) Section 3 has some strong MUST language regarding JSContact and
EPP. As I'm reading it, I am trying to deduce what interoperability
problem is
listinfo/regext
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PI
Hi Andy,
again my response below.
Il 22/03/2023 22:17, Andrew Newton ha scritto:
Mario,
Response in-line.
On Tue, Mar 21, 2023 at 2:39 AM Mario Loffredo
wrote:
[ML] I refer to the interoperability issues coming from using different JSON
labels to identify the same logical JSON object.>
-01
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-rir-search-01
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
_______
regext mailing list
regext@ie
the use of uid values that prevent from correlation
(e.g. either randomly generated or nil UUIDs)
4) Anything else ?
Please, express your preference(s).
Best,
Mario
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research
act to the response on request.
Each server arbitrarily decides when it's time to stop supporting jCard.
Please see Section 4.2.1 of the rdap-jscontact document and my today's
presentation for more information about pros/cons of each approach and
provide feedback.
Best,
Mario
--
Le 30 mars 2023 à 19:47, Mario Loffredo a écrit :
Hi folks,
this is a post to resume the discussion about how to execute the transition
from jCard to JSContact.
Up to now, there are two approaches on the table:
1) Returning JSContact in place of jCard (current proposal)
Until transition i
Sorry, forgot to reply to all.
Messaggio Inoltrato
Oggetto:Re: [regext] Redacting JSContact uid in RDAP
Data: Fri, 31 Mar 2023 13:14:50 +0200
Mittente: Mario Loffredo
A: Gavin Brown
Hi Gavin,
Il 31/03/2023 12:48, Gavin Brown ha scritto:
Ciao Mario
ld
3) Recommending the use of UUIDs that prevent from correlation (e.g.
either randomly generated or nil UUIDs)
4) Redacting by using a registered URN in the IANA namespace (e.g.
"urn:ietf:params:json:rdap+jscontact:uidRedacted")
- G. Brown
5) Anything else ?
Best,
Mario
Hi Scott,
Il 31/03/2023 14:32, Hollenbeck, Scott ha scritto:
-Original Message-
From: regext On Behalf Of Mario Loffredo
Sent: Friday, March 31, 2023 7:45 AM
To: regext@ietf.org
Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated
Caution: This email originated from
it with a valid value and, when needed, redacting it by the
Removal method
- omitting the uid property
That being said, if the WG agreed about adding a new redaction method to
macth Option 3 and Option 4, I wouldn't object.
Best,
Mario
-andy
On Fri, Mar 31, 2023 at 11:52 PM Mario L
e client can definitively remove the jcard handling from
its implementation.
Does it work for you and everyone else ?
Best,
Mario
-andy
On Thu, Mar 30, 2023 at 8:37 PM Mario Loffredo
wrote:
Hi Marc,
thanks for your quick reply.
Think it's always better to reduce the response payl
M
*To: *Mario Loffredo
*Cc: *Marc Blanchet , regext@ietf.org
*Subject: *[EXTERNAL] Re: [regext] jCard to JSContact transition
CAUTION: This email came from outside your organization. Don’t trust
emails, links, or attachments from senders that seem suspicious or you
are not expecting.
I really
*Date: *Saturday, April 1, 2023 at 6:27 AM
*To: *Mario Loffredo
*Cc: *Marc Blanchet , regext@ietf.org
*Subject: *[EXTERNAL] Re: [regext] jCard to JSContact transition
CAUTION: This email came from outside your organization. Don’t
trust emails, links, or attachments from se
1 - 100 of 555 matches
Mail list logo
