[Sipping] SIP certificate management (RFC 6072) and SIP outbound
"Olle E. Johansson" <oej@edvina.net> Mon, 10 October 2011 20:05 UTC
Return-Path: <oej@edvina.net>
X-Original-To: sipping@ietfa.amsl.com
Delivered-To: sipping@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE0221F853E for <sipping@ietfa.amsl.com>; Mon, 10 Oct 2011 13:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.39
X-Spam-Level:
X-Spam-Status: No, score=-0.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnkzhzbHVCAO for <sipping@ietfa.amsl.com>; Mon, 10 Oct 2011 13:05:40 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id DE3FB21F8AFC for <sipping@ietf.org>; Mon, 10 Oct 2011 13:05:39 -0700 (PDT)
Received: from [192.168.40.24] (ns.webway.se [87.96.134.125]) by smtp7.webway.se (Postfix) with ESMTPA id 73798754BCD5 for <sipping@ietf.org>; Mon, 10 Oct 2011 20:05:31 +0000 (UTC)
From: "Olle E. Johansson" <oej@edvina.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Oct 2011 22:05:37 +0200
Message-Id: <6CAE043E-9B12-48A9-B9D4-969284B7470C@edvina.net>
To: sipping@ietf.org
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
Subject: [Sipping] SIP certificate management (RFC 6072) and SIP outbound
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2011 20:05:40 -0000
After reading RFC 6072 I can't help to wonder how this works with an outbound proxy configured in the UA. For instance, using SIP Outbound we have two proxys that we keep an active flow to. RFC 6072 says that the UA is required to have a direct connection to the certificate service in order to publish a key and certificate. This is in order to be able to examine the servers certificate. Does this mean that a UA that follows RFC 6072 should override the pre-defined route in the UA and thus also ignore the SIP outbound mechanism for this transaction? /O
- [Sipping] SIP certificate management (RFC 6072) a… Olle E. Johansson
- Re: [Sipping] SIP certificate management (RFC 607… Cullen Jennings