Re: [Sip-security] S/MIME usage

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Mon, 03 June 2002 02:22 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 WAA22556 for <sip-security-archive@odin.ietf.org>; Sun, 2 Jun 2002 22:22:57 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA01094 for sip-security-archive@odin.ietf.org; Sun, 2 Jun 2002 22:23:24 -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 WAA01041; Sun, 2 Jun 2002 22:21:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01006 for <sip-security@optimus.ietf.org>; Sun, 2 Jun 2002 22:21:41 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22539 for <sip-security@ietf.org>; Sun, 2 Jun 2002 22:21:13 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.84]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g532MKYH001258; Sun, 2 Jun 2002 22:22:21 -0400 (EDT)
Message-ID: <3CFAD279.5A5CA6ED@dynamicsoft.com>
Date: Sun, 02 Jun 2002 22:20:41 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tat.Chan@nokia.com
CC: sip-security@ietf.org
Subject: Re: [Sip-security] S/MIME usage
References: <E320A8529CF07E4C967ECC2F380B0CF993D4E0@bsebe001.NOE.Nokia.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-security-admin@ietf.org
Errors-To: sip-security-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Security Issues for the SIP protocol <sip-security.ietf.org>
X-BeenThere: sip-security@ietf.org
Content-Transfer-Encoding: 7bit

There is no specific response specified for this case (although there
probably should be). 403 probably is closest; I would advise a reason
phrase that indicates that the problem was an unverifiable cert.

-Jonathan R.

Tat.Chan@nokia.com wrote:
> 
> Hi,
> 
> I've been studying S/MIME usage in SIP from the bis 09 draft. I have
> this question, if a UAC sends an S/MIME message to the UAS, who cannot
> verify the sender's certificate, what response should the UAS send back
> to the UAC? Should it be a 403 Forbidden? How can the UAS notify the UAC
> that the certificate cannot be verified?
> 
> Thanks!
> 
> -Tat
> 
> _______________________________________________
> Sip-security mailing list
> Sip-security@ietf.org
> https://www1.ietf.org/mailman/listinfo/sip-security

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sip-security mailing list
Sip-security@ietf.org
https://www1.ietf.org/mailman/listinfo/sip-security