Hi Pete, Thanks for your quick reply - we updated to use the latter option (no quotes). Hopefully this is the last you hear from us until the RFC is announced.
RFC Editor/sg > On Mar 16, 2025, at 11:33 PM, Pete Resnick <resn...@episteme.net> wrote: > > Good catch. How about this? > > OLD > > The security considerations of UTF-8 [RFC3629] and SASLprep [RFC8265] > > NEW > > The security considerations of UTF-8 [RFC3629] and "PRECIS: Usernames and > Passwords" [RFC8265] > > or > > The security considerations of UTF-8 [RFC3629] and PRECIS Usernames and > Passwords [RFC8265] > > pr > -- > Pete Resnick https://www.episteme.net/ > All connections to the world are tenuous at best > > On 17 Mar 2025, at 13:25, Sandy Ginoza wrote: > >> Hi Arnt, >> >> Very sorry, but one last reference question about the SASLprep reference — >> the document originally referenced RFC 4013, which has been obsoleted by RFC >> 7613, which has been obsoleted by RFC 8265. However, 7613 and 8265 are no >> longer about SASLprep. >> >> The abstract for RFC 8265 says: >> This document describes updated methods for handling Unicode strings >> representing usernames and passwords. The previous approach was >> known as SASLprep (RFC 4013) and was based on Stringprep (RFC 3454). >> The methods specified in this document provide a more sustainable >> approach to the handling of internationalized usernames and >> passwords. This document obsoletes RFC 7613. >> >> >> Should the reference remain to RFC 4013, or should it reference RFC 8265 and >> perhaps “SASLprep” should be updated to some other descriptor? >> >> Thanks, >> RFC Editor/sg >> >> >> >> >>> On Mar 16, 2025, at 8:53 PM, Sandy Ginoza <sgin...@staff.rfc-editor.org> >>> wrote: >>> >>> Hi Arnt, >>> >>> Thanks for your quick replies. We updated the document and will continue >>> with the publication process at this time. >>> >>> Thanks, >>> RFC Editor/sg >>> >>>> On Mar 16, 2025, at 12:15 PM, Arnt Gulbrandsen <a...@gulbrandsen.priv.no> >>>> wrote: >>>> >>>> Sandy Ginoza writes: >>>>> Hi Arnt, >>>>> >>>>> May we update these references because they have been obsoleted? We will >>>>> announce the RFC once this item is resolved. >>>> >>>> Certainly. How odd that the author-tools didn't catch those. Thank you! >>>> >>>> Arnt >>> -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
