I would not be opposed to more examples and/or test vectors included in an appendix. I didn’t recognize that the examples were meant as test vectors and don’t recall that specifically being identified in the draft.
-dhs -- Dean H. Saxe, CIDPRO <https://idpro.org/cidpro/> Principal Engineer Office of the CTO Beyond Identity dean.s...@beyondidentity.com On Jan 8, 2025 at 7:37:09 AM, chris.borm...@gmx.de <chris.bormann= 40gmx...@dmarc.ietf.org> wrote: > Hi Jorge, > > > > With that part, we meant the examples given in Section 4 & 10 where > examples are given for 1 and 2 bit status lists (byte array and base64url > encoding for the JWT variant). > > Perhaps a general question: Would more and bigger examples / test vectors > be helpful? > > > > Best Regards, > > Christian > > > > *From: *Oliva Fernandez, Jorge <Jorge.OlivaFernandez= > 40santander.co...@dmarc.ietf.org> > *Date: *Thursday, 2. January 2025 at 15:23 > *To: *Rifaat Shekh-Yusef <rifaat.s.i...@gmail.com>, oauth <oauth@ietf.org> > *Subject: *[OAUTH-WG] Re: WGLC for Token Status List > > Hi Rifaat, > > Just first time reading this new spec, and I have one doubt, in section > “111. Correct decoding and parsing of the encoded Status List” say > “Implementations are RECOMMENDED to verify correctness using the test > vectors given by this specification.” Where are this test vectors located > in the specification? > > Best Regards. > > > > *From: *Rifaat Shekh-Yusef <rifaat.s.i...@gmail.com> > *Date: *Thursday, 2 January 2025 at 13:53 > *To: *oauth <oauth@ietf.org> > *Subject: *[EXT][OAUTH-WG] WGLC for Token Status List > > *CAUTION:* This message is from an EXTERNAL sender – be vigilant, > particularly with links and attachments. If you suspect it, report it > immediately using the phishing button. > > All, > > This is a WG Last Call for the *Token Status List *document. > https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/ > > > Please, review this document and reply on the mailing list if you have any > comments or concerns, by *Jan 17th*. > > Note that this document will be discussed during the OAuth WG *interim* > on *Jan 13th*. > > Regards, > Rifaat & Hannes > > > > Emails aren't always secure, and they may be intercepted or changed after > they've been sent. Santander doesn't accept liability if this happens. If > you think someone may have interfered with this email, please get in touch > with the sender another way. This message doesn't create or change any > contract. Santander doesn't accept responsibility for damage caused by any > viruses contained in this email or its attachments. Emails may be > monitored. If you've received this email by mistake, please let the sender > know at once that it's gone to the wrong person and then destroy it without > copying, using, or telling anyone about its contents. > > Santander UK plc. Registered Office: 2 Triton Square, Regent's Place, > London, NW1 3AN, United Kingdom. Registered Number 2294747. Registered in > England and Wales. https://www.santander.co.uk. Telephone 0800 389 7000. > Calls may be recorded or monitored. Authorised by the Prudential Regulation > Authority and regulated by the Financial Conduct Authority and the > Prudential Regulation Authority. Our Financial Services Register number is > 106054. You can check this on the Financial Services Register by visiting > the FCA’s website https://www.fca.org.uk/register. Santander and the > flame logo are registered trademarks. > > Ref:[PDB#1-4B] > _______________________________________________ > OAuth mailing list -- oauth@ietf.org > To unsubscribe send an email to oauth-le...@ietf.org >
_______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
