…pdated by RFC 8553 RFC 7590 Obsoletes RFC 3920 Was draft-ietf-xmpp-3920bis xmpp WG Select version 22 RFC 6120 Compare versions Author Peter Saint-Andre Email authors RFC stream Other formats txt html pdf bibtex Additional resources Mailing list discussion Report a datatracker bug…
…ho, in the context of the work on RFC 1995bis, recently has provided the DNSEXT WG access to a privately archived DNSIND mailing list thread on RFC 1995, in which such issues have been discussed in November 1999. For the record, the technical issues in RFC 1995 that can be addres…
…ho, in the context of the work on RFC 1995bis, recently has provided the DNSEXT WG access to a privately archived DNSIND mailing list thread on RFC 1995, in which such issues have been discussed in November 1999. For the record, the technical issues in RFC 1995 that can be addres…
…lass of mechanisms). RFC 2945 [ RFC2945 ] is an example of such technology. The WG elected not to use EKE like mechanisms as a basis for SCRAM. If an attacker obtains the authentication information from the authentication repository and either eavesdrops on one authentication exc…
…f round-trips required to complete authentication exchange is not minimal. SASL WG is working on a separate document that should address these limitations. 1.1 . Relationship to Other Documents This document, together with RFC 4422 , obsoletes RFC 2222 in its entirety. This docum…
Simple Authentication and Security Layer (sasl) Skip to main content Concluded WG Simple Authentication and Security Layer (sasl) About Documents Meetings History Photos Email expansions List archive » Note: The data for concluded WGs is occasionally incorrect. WG Name Simple Aut…
… by Paul Hoffman and Marc Blanchet. This document is a product of the IETF SASL WG. Zeilenga Standards Track [Page 4] RFC 4013 SASLprep February 2005 7. Normative References [StringPrep] Hoffman, P. and M. Blanchet, "Preparation of Internationalized Strings ("stringprep")", RFC 3…
… from RFC 3629 by Francois Yergeau. This document is a product of the IETF SASL WG. 8 . Normative References [ ABNF ] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234 , October 2005. [ IMAIL ] Resnick, P., "Internet Message Format", RFC 2822 ,…
…to contact for further information: Kurt Zeilenga <kurt@openldap.org> IETF SASL WG <ietf-sasl@imc.org> Intended usage: COMMON Author/Change controller: IESG <iesg@ietf.org> Note: Updates existing entry for PLAIN 7 . Acknowledgements This document is a revision of RFC 2595 by Chri…
…sername 'user' and password 'pencil' are being used. C: n,,n=user,r=rOprNGfwEbeRWgbNEkqO S: r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0, s=W22ZaJ0SNY7soEsUEjb6gQ==,i=4096 C: c=biws,r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0, p=dHzbZapWIk4jUhN+Ute9ytag9zjfMHgsqm…
Welcome - IRCv3 Working Group WG FAQs Specifications Specs Registry Reg Support Tables Networks Clients Servers Bridges Libraries SASL Mechanisms Open, extensible, feature-rich chat, proven through years of use. Specifications These are the specifications which make up modern IRC…
…th /arch/msg/http-auth/rnEElFCnTD9JAoj_9r7Vm3zMWAs/ 2337046 1689007 [http-auth] WG Action: Conclusion of Hypertext Transfer Protocol Authentication (httpauth) [http-auth] WG Action: Conclusion of Hypertext Transfer Protocol Authentication (httpauth) IESG Secretary 2017-02-01 http…
…oduction During its formalization of the core Jabber protocols, the IETF's XMPP WG introduced the concept of XML stream features. While the order in which features shall be negotiated is clearly defined for the features specified in RFC 3920 ] and RFC 3921 ], the number of possib…
… involved input from Mark Crispin and other participants of the IMAP Extensions WG. Newman, et al. Standards Track [Page 16] RFC 5255 IMAP Internationalization June 2008 . Relevant Sources of Documents for Internationalized IMAP Implementations This is a non-normative list of sou…
…ains a "data" attribute that base64 decodes as follows: n,,n=user,r=rOprNGfwEbeRWgbNEkqO The server then responds with a "data" attribute that base64 decodes as follows: r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF,s=W22ZaJ0SNY7soE sUEjb6gQ==,i=4096 The next client request c…