[Sip] draft-ietf-sip-sec-agree-04.txt
AC Mahendran <mahendra@qualcomm.com> Thu, 11 July 2002 22:18 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09402 for <sip-archive@odin.ietf.org>; Thu, 11 Jul 2002 18:18:17 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA22058 for sip-archive@odin.ietf.org; Thu, 11 Jul 2002 18:19:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19169; Thu, 11 Jul 2002 17:36:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19138 for <sip@optimus.ietf.org>; Thu, 11 Jul 2002 17:36:15 -0400 (EDT)
Received: from numenor.qualcomm.com (numenor.qualcomm.com [129.46.51.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07305 for <sip@ietf.org>; Thu, 11 Jul 2002 17:35:20 -0400 (EDT)
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.12.3/8.12.3/1.0) with ESMTP id g6BLaCgD024072 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <sip@ietf.org>; Thu, 11 Jul 2002 14:36:12 -0700 (PDT)
Received: from MAHENDRA.qualcomm.com (mahendra.qualcomm.com [129.46.75.104]) by magus.qualcomm.com (8.12.3/8.12.3/1.0) with ESMTP id g6BLa9Zd028809 for <sip@ietf.org>; Thu, 11 Jul 2002 14:36:10 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020711143204.02656460@clea.qualcomm.com>
X-Sender: mahendra@clea.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 11 Jul 2002 14:36:09 -0700
To: sip@ietf.org
From: AC Mahendran <mahendra@qualcomm.com>
In-Reply-To: <200207071633.MAA25356@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [Sip] draft-ietf-sip-sec-agree-04.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
I have question regarding the purpose of the "Security-Client" field. Based on the description, it looks like this field is not used by the server in any way. Can someone explain the purpose of this field? thanks, AC Ps: In the "Server Initiated" (Section 3.4.2) procedures, this field is not used. By the same reasoning, this field should not be applicable to the "Client Initiated" procedures as well. At 12:33 PM 7/7/2002 -0400, Internet-Drafts@ietf.org wrote: >A New Internet-Draft is available from the on-line Internet-Drafts >directories. >This draft is a work item of the Session Initiation Protocol Working Group >of the IETF. > > Title : Security Mechanism Agreement for SIP Sessions > Author(s) : J. Arkko et al. > Filename : draft-ietf-sip-sec-agree-04.txt > Pages : 17 > Date : 05-Jul-02 > >SIP has a number of security mechanisms. Some of them have been built >in to the SIP protocol, such as HTTP authentication or secure >attachments. These mechanisms have even alternative algorithms and >parameters. SIP does not currently provide any mechanism for >selecting which security mechanisms to use between two entities. In >particular, even if some mechanisms such as OPTIONS were used to make >this selection, the selection would be vulnerable against the >Bidding-Down attack. This document defines three header fields for >negotiating the security mechanisms within SIP between a SIP entity >and its next SIP hop. A SIP entity applying this mechanism must >always require some minimum security (i.e. integrity protection) from >all communicating parties in order to secure the negotiation, but the >negotiation can agree on which specific minimum security is used. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-sip-sec-agree-04.txt > >To remove yourself from the IETF Announcement list, send a message to >ietf-announce-request with the word unsubscribe in the body of the message. > >Internet-Drafts are also available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-ietf-sip-sec-agree-04.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv@ietf.org. >In the body type: > "FILE /internet-drafts/draft-ietf-sip-sec-agree-04.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. >Content-Type: text/plain >Content-ID: <20020705142509.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-ietf-sip-sec-agree-04.txt > ><ftp://ftp.ietf.org/internet-drafts/draft-ietf-sip-sec-agree-04.txt> _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] I-D ACTION:draft-ietf-sip-sec-agree-04.txt Internet-Drafts
- [Sip] draft-ietf-sip-sec-agree-04.txt AC Mahendran
- Re: [Sip] draft-ietf-sip-sec-agree-04.txt Gonzalo Camarillo