> -----Original Message-----
> From: Roman Danyliw via Datatracker <nore...@ietf.org>
> Sent: Sunday, November 5, 2023 11:19 AM
> To: The IESG <i...@ietf.org>
> Cc: draft-ietf-regext-rdap-ope...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org; AlBanna, Zaid <zalba...@verisign.com>; AlBanna, Zaid
> <zalba...@verisign.com>
> Subject: [EXTERNAL] Roman Danyliw's Discuss on draft-ietf-regext-rdap-
> openid-26: (with DISCUSS and COMMENT)
>
> 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.
>
> Roman Danyliw has entered the following ballot position for
> draft-ietf-regext-rdap-openid-26: Discuss
>
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
>
>
> Please refer to https://secure-
> web.cisco.com/1SYN9xgMUeHrStOXM4V9ajEx9sFSvkO9nm2vACJ0HznMELG
> VFdtkWt6Dvz30U-8ny2qpgRVfguDPOZqc2jmx2zR78rQCkvixRu-
> rJhFpY1tUPbgFGj2qtLbaQh1g3ICwAKtEEUM2Nz-KBJ3R2TkaMBgl_fk83-
> M7a302Du6nhvmDQShrgcYvUx5EQg-
> 3Yrp6Sbal2kM8y363tpfiUvOeN0oXZXkv687bnE6VG0qWMAzjc56pQScJSi62Sa
> wl5qFPMM9I9-
> hDsKympyjYom2tjV_muin9dGF6ilrbjnJAUC3Q/https%3A%2F%2Fwww.ietf.or
> g%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-
> positions%2F
> for more information about how to handle DISCUSS and COMMENT
> positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://secure-
> web.cisco.com/1CVp_vOAUfFsdR3IALZC1xsTOak9JkRPRAlfn16SEqimQNBivD
> a0MyMktLI1y9xLK1u3GJhsHYkvBzW5k2lKIP3hj1bWrZsgxnFRHjIF9PgoHaqX4e
> pSvSvMGx6BrwhvNqPB0W8uRE1HOjl0sYvPa178GnbjR81-dNnFb1yxC-
> MIo4HqBsKfpu_xia5vu5kiGgrd-IXOkdcEwp5yMPBEZ57T-
> iSqfDSMCNEiRJG7MB7faL9MNfOdu4LIlHEePz0vezkvl05hURDwhxcx9mBTQHl
> kG2VhwXXAq9NIg42bdLM0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2
> Fdraft-ietf-regext-rdap-openid%2F
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> (revising ballot down to the remaining item not addressed in -26)
>
> ** Section 11.
>    An RDAP server
>    operator SHOULD develop policies for information disclosure to ensure
>    that personally identifiable information is disclosed only to clients
>    that are authorized to process that information.
>
> Why is this not a MUST?  What are the circumstances where PII should be
> disclosed without authorization?
>
> See ongoing discussion at
> https://secure-web.cisco.com/1c5fLIYhODzLg-
> rYHsNkSrawK8_q0JaQohefxhvUcdcGwOH_0DCPs8b9GfsiCfcBrqeogbz7E1Bdf
> HbMYZuONpi7LwWQnXkyELKGeQ9EVTXT4pfOWgteJIK6hgcUxnJJ18k9T-
> ZTuoNE40m80Mabn9_2eL_t6FaqyXHwqjx3HikauzfoyFesRGDNSxZCAKuDkwP
> a-Lgba4Pnpr1jClGAWv-4Zo8u7gKRyYxsDT0-
> f0o6IjJmfkmJFBeOyBmwEh7UWGBEMOjD7Q1sWgClzfWyLqbzvUhT5LDXZ1H
> XzFFqnUAo/https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fregext
> %2FlTZEAyvBUaE3V2Ih2o8TgoNQ7Zk%2F
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you to the authors for reaching out to the OAuth WG when this
> document
> was first being drafted.
>
> Thank you to Justin Richer for providing a timely review of this work from the
> OAuth WG perspective.  See
> https://secure-
> web.cisco.com/1Rur8ZC_mJz4Kz2y18idtbd2iLdAgKNbTurjCOA7xEGTiT-
> cnpOTK9EGzeZS1NoQ2R3IM8LmdKcLQAVgWprbaEfHSFsZ-QR-
> CQPpFVvPMoVdswJRRWYOsuvjNYNULMwgzxxTvZjbG4CPiX3K_QdTJFkxcbrh
> apirrWyPfRsGQWLn7LW33I5j-
> RoL9m9JHrMejsI8lauVWuFrDIrUP7LRTGXUBOypYUVU1RP17dGpbCWK-
> llPNm8H04foZjHejGYFijTgbYrKSsTNcfp_kKrFdI1nRM5pf6zRNfgHMruPqCpg/h
> ttps%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Foauth%2F33Ci5v7EH
> DLRC7pvvK85uarXutY%2F
>
> I appreciate the patience of the WG given my deferral of this document to
> this
> telechat.
>
> Thanks for resolving my COMMENTs and DISCUSS feedback.

[SAH] Thanks again for the feedback, Roman. I just submitted a document update 
to address the final issue.

Scott
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to