idnits 2.17.1 draft-ietf-sip-digest-aka-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3310 5 Title: Hypertext Transfer Protocol (HTTP) Digest 6 Authentication Using Authentication and Key 7 Agreement (AKA) 8 Author(s): A. Niemi, J. Arkko, V. Torvinen 9 Status: Informational 10 Date: September 2002 11 Mailbox: aki.niemi@nokia.com, jari.arkko@ericsson.com, 12 vesa.torvinen@ericsson.fi 13 Pages: 18 14 Characters: 36985 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-sip-digest-aka-03.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3310.txt 21 This memo specifies an Authentication and Key Agreement (AKA) based 22 one-time password generation mechanism for Hypertext Transfer Protocol 23 (HTTP) Digest access authentication. The HTTP Authentication 24 Framework includes two authentication schemes: Basic and Digest. Both 25 schemes employ a shared secret based mechanism for access 26 authentication. The AKA mechanism performs user authentication and 27 session key distribution in Universal Mobile Telecommunications System 28 (UMTS) networks. AKA is a challenge-response based mechanism that 29 uses symmetric cryptography. 31 This document is a product of the Session Initiation Protocol Working 32 Group of the IETF. 34 This memo provides information for the Internet community. It does 35 not specify an Internet standard of any kind. Distribution of this 36 memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.