idnits 2.17.1 draft-ietf-sipping-nai-reqs-02.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 3324 5 Title: Short Term Requirements for Network Asserted 6 Identity 7 Author(s): M. Watson 8 Status: Informational 9 Date: November 2002 10 Mailbox: mwatson@nortelnetworks.com 11 Pages: 11 12 Characters: 21964 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-sipping-nai-reqs-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3324.txt 19 A Network Asserted Identity is an identity initially derived by 20 a Session Initiation Protocol (SIP) network intermediary as a result 21 of an authentication process. This document describes short term 22 requirements for the exchange of Network Asserted Identities within 23 networks of securely interconnected trusted nodes and to User Agents 24 securely connected to such networks. 26 There is no requirement for identities asserted by a UA in a SIP 27 message to be anything other than the user's desired alias. 29 This document is a product of the Session Initiation Proposal 30 Investigation Working Group of the IETF. 32 This memo provides information for the Internet community. It does 33 not specify an Internet standard of any kind. Distribution of this 34 memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.