> -----Original Message----- > From: regext <regext-boun...@ietf.org> On Behalf Of Hollenbeck, Scott > Sent: Monday, October 2, 2023 4:06 PM > To: paul.wout...@aiven.io; i...@ietf.org > Cc: draft-ietf-regext-rdap-ope...@ietf.org; regext-cha...@ietf.org; > regext@ietf.org; AlBanna, Zaid <zalba...@verisign.com> > Subject: [EXTERNAL] Re: [regext] Paul Wouters' Discuss on draft-ietf-regext- > rdap-openid-25: (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. > > > -----Original Message----- > > From: Paul Wouters via Datatracker <nore...@ietf.org> > > Sent: Monday, October 2, 2023 3:14 PM > > 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] Paul Wouters' Discuss on > > draft-ietf-regext-rdap-openid- > > 25: (with DISCUSS and COMMENT) > >
[SAH] [snip] > > Can a reference link be provided for these to make it easier on the > > reader/implementer. Ideally these (and the ones below) could use > > section specific links, eg: > > https://secure- > > > web.cisco.com/1VX5Briiu_dl8t7xWAjNuQpbWYxGIsNIDOhNx7lwo5oY8mydz > > > XxIeOwPdgEM1hDCmakkDltPe4H7Q0H3jC9vNXqwGSmoHnBlNffKdqMiL68ZI > > > 2SrtrUuFDbyVQiA80gtsFSs9ab85s7pSf9sWHXCf2fMmrvUTtF8H9kZiVrySdVh9 > > 7EHRLj6Ai7CjcRoRRKXPWR3vjScp3RBRWiLJ7NYR- > > > c7YS8PMKByYj2sGu4Rb5lxVIWqi0NUOQHNmhWUuBSHxikQM3e3gLFvQASlfp > > su4xrPkNCwlZFDBSejjU2NXxIIVWvoClPAXMn_JS- > > sflolM/https%3A%2F%2Fopenid.net%2Fspecs%2Fopenid-connect-core- > > 1_0.html%23TokenRequestValidation > > [SAH] Sure, I can see what <eref> markup does in both the text and HTML > versions of the draft to make it easier to access those sections of the > specifications. [SAH] This is what it will look like in both the text and HTML versions of the draft: "The benefits of using the Authorization Code Flow for authenticating a human user are described in Section 3.1 of the OpenID Connect Core protocol (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth)." I understand the utility, but that long URL looks cluttered to me. Is it really worth adding multiple URLs like this to the text? Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
