Il 17/02/2022 17:00, Hollenbeck, Scott ha scritto:
*From:* Jasdip Singh <jasd...@arin.net>
*Sent:* Thursday, February 17, 2022 10:57 AM
*To:* Marc Blanchet <marc.blanc...@viagenie.ca>; Hollenbeck, Scott
<shollenb...@verisign.com>
*Cc:* regext@ietf.org
*Subject:* [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
*Caution:*This email originated from outside the organization. Do not
click links or open attachments unless you recognize the sender and
know the content is safe.
My comment below.
Jasdip
*From: *Marc Blanchet <marc.blanc...@viagenie.ca>
*Date: *Thursday, February 17, 2022 at 10:17 AM
*To: *"Hollenbeck, Scott" <shollenbeck=40verisign....@dmarc.ietf.org>
*Cc: *Jasdip Singh <jasd...@arin.net>, "regext@ietf.org" <regext@ietf.org>
*Subject: *Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-10.txt
Le 17 févr. 2022 à 08:24, Hollenbeck, Scott
<shollenbeck=40verisign....@dmarc.ietf.org> a écrit :
*From:* regext <regext-boun...@ietf.org> *On Behalf Of
*Hollenbeck, Scott
*Sent:* Monday, February 14, 2022 12:12 PM
*To:* jasd...@arin.net; regext@ietf.org
*Subject:* [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
*Caution:*This email originated from outside the organization. Do
not click links or open attachments unless you recognize the
sender and know the content is safe.
*From:* Jasdip Singh <jasd...@arin.net>
*Sent:* Monday, February 14, 2022 10:34 AM
*To:* Hollenbeck, Scott <shollenb...@verisign.com>; regext@ietf.org
*Subject:* [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
*Caution:*This email originated from outside the organization. Do
not click links or open attachments unless you recognize the
sender and know the content is safe.
Hello Scott,
I like the overall direction of this draft to help simplify things
for RDAP clients and facilitate adoption, but wanted to share
couple of observations:
1. There are 3 newly proposed RDAP path segments, starting with
“login”, “session”, and “logout”. Looks like, for simplicity, we
could coalesce them as “session/{start|refresh|end}”, with “login”
becoming “session/start”, and “logout” “session/end”. “device” and
“devicepoll” could be appended in the path as-n-when needed.
*/[SAH] What do you all think of this suggestion? The draft
currently has “login”, logout”, and “session” path segments.
Should they be combined?/*
*/[SAH] I’m going to make a suggestion in the absence of any
feedback. I’d like to remove the session path segment and combine
it with the login path segment such that the draft will describe
the following path segments:/*
*//*
*//login/*
*//login/status/*
*//login/refresh/*
*//login/device/*
*//login/devicepoll/*
*//logout/*
*//*
*/This eliminates the session path segment and merges the
functionality with the “easier to understand” login/logout
semantics. /*
I would prefer to have a single endpoint for the “sessions”, as
current practice. How about:
/session/login
/session/status
/session/refresh
/session/device
/session/devicepoll
/session/logout
[JS] Like this better if everyone agrees. :)
*/[SAH] Works for me, too./*
/*Agreed.*/
/*Mario
*/
*//*
_______________________________________________
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://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
