From nobody Mon Nov 2 06:27:45 2020 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631B13A109B for ; Mon, 2 Nov 2020 06:27:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=chriswendt-net.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9jfGn_T4TZ1 for ; Mon, 2 Nov 2020 06:27:35 -0800 (PST) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C95B03A108F for ; Mon, 2 Nov 2020 06:27:34 -0800 (PST) Received: by mail-qk1-x72c.google.com with SMTP id 140so11591542qko.2 for ; Mon, 02 Nov 2020 06:27:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriswendt-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=cPlJYpyZ4m6plbdFH9gylcBrTFRaIGWDPx3V5ucBsag=; b=nStoqgmmVeIjuogawp4MSbL6/gZdAkCg3nxgp0GjXjugWsPHb6cKRvK6/fsI5rPSBJ SLb5jbiAtzjeopkNfzI+y+45biyF+gv0it0DH/Q4lXrlPQj7qwcu/FHY1QG7IokYQ4lp u/t49m/GXX/9oHYh/sIX+QEdXwQjQa7fOExa2zB3/Gi4i2iSgRgPtZEGnpOB/bPa+UJ9 5cBi6DFKFkzBCE2VPOh192sWd/aFgx+xIvJiHFwVP6/8fIW9+3fJVq0cBbfhqSu4JN7J g8t5dULWh79Sz5FJ5d9VDnKGUVwlzMuHE4D/IgjVJ7529hIV5/8n8o+JeVmrzBqgFdy1 H4jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=cPlJYpyZ4m6plbdFH9gylcBrTFRaIGWDPx3V5ucBsag=; b=Am6jgYM2LvmQ95auUiSlsQeGLMRMLrb6tqvfnQLBolqQ2x8RRnSDLBeObztiu1zdCL qSS7pVSkyes6gJk1PoKchZDhQfPzeBVNHOYLOqmacc+dw3/Wkzyw/v7QyTZtVKGDSQNF bH4bEuu6/Heh/5O2/eUiT5YiUKTWCKy59eVDoKTItF4Tee9Og481TSF/ttqbGuC/RLZr CgTGHH4Fc1HjSLAD+KgsEauHyu72mF/c8WXkSM+Z6eu55jOMOfFjjiod+tjWfCYC1u7G q1kfLvU2GOaO87sj+Ndxwtu7THme/if/GN4I+qiPv2W5rDRJNTBjbg4jX5KOK/VZqre5 QW3Q== X-Gm-Message-State: AOAM53225+/t43B1m7M3QbfBsv1GoW7AAtKlRQ2ZIeQEdJmrahxIU6EZ Uiemkcil2D2MCGNRoe4JtOwvpRo+rg4zpOZr X-Google-Smtp-Source: ABdhPJwK/uAlmCel31RZ8uXo58DUMcA+CZ/7/T9YebWNzK56/9HV0CSHPBsHRuk1BOHaR5MIh1ocqA== X-Received: by 2002:a37:7f83:: with SMTP id a125mr817846qkd.423.1604327253832; Mon, 02 Nov 2020 06:27:33 -0800 (PST) Received: from [192.168.0.136] (c-68-82-121-87.hsd1.pa.comcast.net. [68.82.121.87]) by smtp.gmail.com with ESMTPSA id q188sm8133547qka.56.2020.11.02.06.27.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2020 06:27:33 -0800 (PST) From: Chris Wendt Message-Id: <5AA89066-5522-4A93-B69C-EB20FEA08DE9@chriswendt.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_70952109-6EA2-4F77-918E-2B3A56C25C9F" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Mon, 2 Nov 2020 09:27:32 -0500 In-Reply-To: <4B853BAF-CCD2-488B-B969-418631EA1F82@brianrosen.net> Cc: SIPCORE To: Brian Rosen References: <4B853BAF-CCD2-488B-B969-418631EA1F82@brianrosen.net> X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [sipcore] Call For Adoption draft-went-sipcore-callinfo-rcd X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 14:27:44 -0000 --Apple-Mail=_70952109-6EA2-4F77-918E-2B3A56C25C9F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 HI Brian, It=E2=80=99s been more than two weeks and i haven=E2=80=99t seen any = objections. Can i submit a WG document? Thanks! -Chris > On Oct 9, 2020, at 1:06 PM, Brian Rosen wrote: >=20 > This message starts a two week call for adoption of = https://tools.ietf.org/html/draft-wendt-sipcore-callinfo-rcd-03 = >=20 > Please send comments and offers to assist/review/comment to the list. >=20 > Brian > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore --Apple-Mail=_70952109-6EA2-4F77-918E-2B3A56C25C9F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 HI = Brian,

It=E2=80=99s = been more than two weeks and i haven=E2=80=99t seen any objections. =  Can i submit a WG document?

Thanks!

-Chris

On Oct = 9, 2020, at 1:06 PM, Brian Rosen <br@brianrosen.net> wrote:

This message starts a = two week call for adoption of https://tools.ietf.org/html/draft-wendt-sipcore-callinfo-rcd-03=

Please send = comments and offers to assist/review/comment to the list.

Brian
______________________________________________= _
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

= --Apple-Mail=_70952109-6EA2-4F77-918E-2B3A56C25C9F-- From nobody Mon Nov 2 07:42:25 2020 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122233A0D75 for ; Mon, 2 Nov 2020 07:42:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uF8eTk-gfwwC for ; Mon, 2 Nov 2020 07:42:14 -0800 (PST) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 396883A1186 for ; Mon, 2 Nov 2020 07:42:14 -0800 (PST) Received: by mail-qk1-x730.google.com with SMTP id r7so11850190qkf.3 for ; Mon, 02 Nov 2020 07:42:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7hBif808St4hsLHVoiwiZMO3yOOo6Xuju6KlJgGiWyY=; b=jfA2+rp/g6KBQmJIWiZgTt+ByxoqEIjcrhbYDzRb1C26iCjEL07K1kADFgcvfkLU4o sQ7I127NgPaSjrQu3hz755IYVNvahu8FuKZUacR3HlW3SypdGrqKSIUqJ3OOEFbEtEyP A4HlSPeNbvox8SJyfG6/SWSa5RyYrMFz6J0rhIWWNG2ThL4HGYjuTCmP+WFI51myE1XA Dxtpdpy/byMEHY7LJFnR2jG+fnw1Um2chBHg5WlN5kyAeM5hSteRpLwe+riEDlxsC5zc LdgXa4tlLGboroHMbZWhh+pBxa070mN72Xwgo14lhMEXU8l86rN9Vsg95yk+vnzu7Isx AT8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7hBif808St4hsLHVoiwiZMO3yOOo6Xuju6KlJgGiWyY=; b=NTrfQLzG8CDmmzKdmnWTLC8OfvrFqUTMU1M9fNTqB5sPQyp4cd1MF6y2ZtEBKXUuxv duU1qSKaMtwV1BhT/7N2onF5cfOAl4Tvl5j37AWMCOGBNvYblD+PikNoQx9SI5OXJjbT TRJeCmaLWdGiXJlp0c4sge7+fOCTifXiQKhLt/61zk7upl5qTZU0lVxiWaN6j9CeuWM4 /zpe6xhEV1l1wgCdcwTrlfGU9sTTqI+Fdju/Uksk8lix8QWStqjdCfEbYmwumyTMe+k8 IIIydXzIQLlZrFNRbDUzKBMDmtEyfrfodEUR0XBo0rTSl5WYKF2nRUyS2h0HFFtk4oeD 2mug== X-Gm-Message-State: AOAM533TWHrBQqErRgWqOYxYPdKqw/pNjwC/QefMPuctZl3aKLTbdFNu VwhJLd74Rgb6vR+ahPXjIXw/BPMD9d08zkCg X-Google-Smtp-Source: ABdhPJw9wb8lWQe12dZePXLo00x6o7da/GgnTxUlhK9uWhkuqJt8oatqKnTwMCOgylaRYiZNNbjsaQ== X-Received: by 2002:a05:620a:2010:: with SMTP id c16mr14968868qka.226.1604331733189; Mon, 02 Nov 2020 07:42:13 -0800 (PST) Received: from brians-mbp-2871.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id r62sm8289724qkd.80.2020.11.02.07.42.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2020 07:42:12 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) From: Brian Rosen In-Reply-To: <4A8025B5-7E1C-4C96-A7DF-D5A2DB16698F@shockey.us> Date: Mon, 2 Nov 2020 10:42:10 -0500 Cc: Paul Kyzivat , sipcore@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <4B853BAF-CCD2-488B-B969-418631EA1F82@brianrosen.net> <774e399f-35ae-b934-f9e6-a3fc1a9e6911@alum.mit.edu> <4A8025B5-7E1C-4C96-A7DF-D5A2DB16698F@shockey.us> To: Richard Shockey X-Mailer: Apple Mail (2.3608.120.23.2.1) Archived-At: Subject: Re: [sipcore] Call For Adoption draft-went-sipcore-callinfo-rcd X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 15:42:24 -0000 We have had several people supporting adoption and none opposed. = Authors are requested to submit a draft-ietf-sipcore-callinfo-rcd-00 Brian > On Oct 10, 2020, at 6:37 PM, Richard Shockey = wrote: >=20 >=20 > + 1 I support adoption as well. >=20 > =E2=80=94=20 > Richard Shockey >=20 > Shockey Consulting LLC >=20 > Chairman of the Board SIP Forum >=20 > www.shockey.us >=20 > www.sipforum.org >=20 > richardshockey.us >=20 > Skype-Linkedin-Facebook =E2=80=93Twitter rshockey101 >=20 > PSTN +1 703-593-2683 >=20 >=20 >=20 > =EF=BB=BFOn 10/10/20, 3:06 PM, "sipcore on behalf of Paul Kyzivat" = wrote: >=20 > I support adoption. >=20 > On 10/9/20 1:06 PM, Brian Rosen wrote: >> This message starts a two week call for adoption of=20 >> https://tools.ietf.org/html/draft-wendt-sipcore-callinfo-rcd-03=20 >> >>=20 >> Please send comments and offers to assist/review/comment to the list. >>=20 >> Brian >>=20 >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore >>=20 >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >=20 >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Mon Nov 2 08:59:43 2020 Return-Path: X-Original-To: sipcore@ietf.org Delivered-To: sipcore@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 735D23A12E1; Mon, 2 Nov 2020 08:59:30 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipcore@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.21.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: sipcore@ietf.org Message-ID: <160433637043.28714.16222091924080470743@ietfa.amsl.com> Date: Mon, 02 Nov 2020 08:59:30 -0800 Archived-At: Subject: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-rcd-00.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 16:59:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core WG of the IETF. Title : SIP Call-Info Parameters for Rich Call Data Authors : Chris Wendt Jon Peterson Filename : draft-ietf-sipcore-callinfo-rcd-00.txt Pages : 16 Date : 2020-11-02 Abstract: This document describes a SIP Call-Info header field usage defined to include rich data associated with the identity of the calling party that can be rendered to called party for providing more useful information about the caller or the specific reason for the call. This includes extended comprehensive information about the caller such as what a jCard object can represent for describing the calling party or other call specific information such as describing the reason or intent of the call. The elements defined for this purpose are intended to be extensible to accommodate related information about calls that helps people decide whether to pick up the phone and additionally, with the use of jCard and other elements, to be compatible with the STIR/PASSporT Rich Call Data framework. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-rcd/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipcore-callinfo-rcd-00 https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-callinfo-rcd-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 18 19:40:02 2020 Return-Path: X-Original-To: sipcore@ietf.org Delivered-To: sipcore@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 700243A0803; Wed, 18 Nov 2020 19:39:55 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipcore@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.23.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: sipcore@ietf.org Message-ID: <160575719534.25921.14754401743631122634@ietfa.amsl.com> Date: Wed, 18 Nov 2020 19:39:55 -0800 Archived-At: Subject: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-rcd-01.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2020 03:39:56 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core WG of the IETF. Title : SIP Call-Info Parameters for Rich Call Data Authors : Chris Wendt Jon Peterson Filename : draft-ietf-sipcore-callinfo-rcd-01.txt Pages : 16 Date : 2020-11-18 Abstract: This document describes a SIP Call-Info header field usage defined to include rich data associated with the identity of the calling party that can be rendered to called party for providing more useful information about the caller or the specific reason for the call. This includes extended comprehensive information about the caller such as what a jCard object can represent for describing the calling party or other call specific information such as describing the reason or intent of the call. The elements defined for this purpose are intended to be extensible to accommodate related information about calls that helps people decide whether to pick up the phone and additionally, with the use of jCard and other elements, to be compatible with the STIR/PASSporT Rich Call Data framework. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-rcd/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipcore-callinfo-rcd-01 https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-callinfo-rcd-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-callinfo-rcd-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Nov 24 04:31:17 2020 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79A153A0A00 for ; Tue, 24 Nov 2020 04:31:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VOnLuSR1-Ux for ; Tue, 24 Nov 2020 04:31:14 -0800 (PST) Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44A373A0A06 for ; Tue, 24 Nov 2020 04:31:12 -0800 (PST) Received: from pinguicula.webway.org (h-205-16.A165.corp.bahnhof.se [176.10.205.16]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id 19E153291; Tue, 24 Nov 2020 13:31:09 +0100 (CET) From: "Olle E. Johansson" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Message-Id: Date: Tue, 24 Nov 2020 13:31:08 +0100 Cc: Olle E Johansson To: sipcore@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [sipcore] SIP client certs X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2020 12:31:17 -0000 Hi! I hope everyone stays safe in these times. During last week=E2=80=99s IETF I ended up in a discussion in RUM about = using TLS client certs in SIP. I have been testing this a long time ago, = but obviously not fully. The question I got I failed to find an answer = to, which is annoying :-) Here it goes, let=E2=80=99s see if you can help: SIP UA -> Ingress proxy -> Registrar If the Ingress Proxy requires a client cert for authentication, that = certificate is only seen on the first hop between the UA and the proxy. = How can we make the registrar validate and trust the client cert for the = registration? If there is absolute trust between the ingress proxy and the registrar, = I guess we could parse out a lot of cert info and add to SIP headers and = send forward. If there is no trust relationship (let=E2=80=99s say the = Ingress Proxy is an enterprise SBC and the registrar is a service = provider) then we have a problem. In HTTP there=E2=80=99s a CONNECT method so the SIP UA can establish a = direct TLS session to the registrar through a proxy. There is a very old = expired draft for a SIP connect method that could potentially be helpful = here. I do remember that we had a SIP Connect draft many years ago. Any ideas? Cheers, /Olle= From nobody Tue Nov 24 09:41:24 2020 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330723A122D for ; Tue, 24 Nov 2020 09:41:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.198 X-Spam-Level: X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGCVoJ7ojyCw for ; Tue, 24 Nov 2020 09:41:21 -0800 (PST) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F6BC3A1218 for ; Tue, 24 Nov 2020 09:41:21 -0800 (PST) Received: by mail-qt1-x82a.google.com with SMTP id p12so16660217qtp.7 for ; Tue, 24 Nov 2020 09:41:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sGa55alFkE+1oZrCqlrvDSkmS+p6P02gLGraOPXiTQE=; b=BNdksYPJT8Oj4/q9qyK5h0iypzrH8PzJSCh8zBZegqX122gonZsb6twPL0eHsH6RHz ynvWOAwcFzG2AhFbs6dh3sNPePXWchgyZklwXQGJvSHDbefS45QsVDwWuxkFP0zSsp3d 0RpQYmEEPHzfyHonXQcze84Pcd8AY0C4Sn/ilzNnUNfThW+xmQyyLYXVPFmoH/ysIOT2 zj1MGmIaP6sbSmnk/y2NNGWUGyD8QfbB7uk3/zka8ZG1qATwUAqwyLcWtFR5c7wudfpX K/zDfnXKEV3EbD3DYHs5ZvAHM3HYwdcLidFL2JFqBjohLXcvXvXD3XmumnmNf86XBZyd Krvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sGa55alFkE+1oZrCqlrvDSkmS+p6P02gLGraOPXiTQE=; b=BCTt++L0I4B072QlVqoBmN51XCsK6iqHol+boJqFXSg+qJCIvK7M2OdLQxB35LJnmY rmH+YhE3tF9NQWdI40rTjT99mePOMeA4lQ+5Y0/v/BKK/zj28+wm307xgwV+smIpL8wH ewGXzorZj5cqCdbDv5l8YIvOHR6IyC+MTYEk2mxf2VEHYz5N5nAkFZtOK+20NbdkUJQ4 hNRMrAZSpVC2Q6hCc74PKlvlzpnLluz2rontnUc1tNutg6MWVHinnH/MjEzMOgSZu0nF VFtE9uq7LfW8nox8LZy05W6shuk6yd+6uKjZzvoh8KsBjKquoxyFTGvCbcwid7SSkb9G ydNw== X-Gm-Message-State: AOAM530fOjeVheFXZ8OpJrJPLqniLl2i2Vin8kov1V34OFL71xf+B4aI oVY/GWg0OshVUH+pN/eTv3XX/n95kMLdiiYESIqvlue+q+hTuA== X-Google-Smtp-Source: ABdhPJzUfzY4sOuwkymp9t3er1+to/CNxyhl2doIR0gWDcu3Niy7qR6vyXhC/hdD1DhHoCN8kp32jrqnnwAMRutwW8s= X-Received: by 2002:ac8:5741:: with SMTP id 1mr5392333qtx.294.1606239680056; Tue, 24 Nov 2020 09:41:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ash Wilson Date: Tue, 24 Nov 2020 09:41:08 -0800 Message-ID: To: "Olle E. Johansson" Cc: sipcore@ietf.org Content-Type: multipart/alternative; boundary="0000000000008de75105b4ddd12c" Archived-At: Subject: Re: [sipcore] SIP client certs X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2020 17:41:23 -0000 --0000000000008de75105b4ddd12c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Olle, Are you referring to https://tools.ietf.org/html/draft-dotson-sip-certificate-auth-04 ? -Ash On Tue, Nov 24, 2020 at 4:31 AM Olle E. Johansson wrote: > Hi! > I hope everyone stays safe in these times. > > During last week=E2=80=99s IETF I ended up in a discussion in RUM about u= sing TLS > client certs in SIP. I have been testing this a long time ago, but > obviously not fully. The question I got I failed to find an answer to, > which is annoying :-) > > Here it goes, let=E2=80=99s see if you can help: > > SIP UA -> Ingress proxy -> Registrar > > If the Ingress Proxy requires a client cert for authentication, that > certificate is only seen on the first hop between the UA and the proxy. H= ow > can we make the registrar validate and trust the client cert for the > registration? > > If there is absolute trust between the ingress proxy and the registrar, I > guess we could parse out a lot of cert info and add to SIP headers and se= nd > forward. If there is no trust relationship (let=E2=80=99s say the Ingress= Proxy is > an enterprise SBC and the registrar is a service provider) then we have a > problem. > > In HTTP there=E2=80=99s a CONNECT method so the SIP UA can establish a di= rect TLS > session to the registrar through a proxy. There is a very old expired dra= ft > for a SIP connect method that could potentially be helpful here. > > I do remember that we had a SIP Connect draft many years ago. > > Any ideas? > > Cheers, > /Olle > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > --=20 *Ash Wilson* | Technical Director *e:* ash.wilson@valimail.com This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system. --0000000000008de75105b4ddd12c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Olle,=C2=A0
-Ash

On Tue, Nov 24, 2020 at 4:31 AM Olle E. Johansson= <oej@edvina.net> wrote:
Hi!
I hope everyone stays safe in these times.

During last week=E2=80=99s IETF I ended up in a discussion in RUM about usi= ng TLS client certs in SIP. I have been testing this a long time ago, but o= bviously not fully. The question I got I failed to find an answer to, which= is annoying :-)

Here it goes, let=E2=80=99s see if you can help:

SIP UA -> Ingress proxy -> Registrar

If the Ingress Proxy requires a client cert for authentication, that certif= icate is only seen on the first hop between the UA and the proxy. How can w= e make the registrar validate and trust the client cert for the registratio= n?

If there is absolute trust between the ingress proxy and the registrar, I g= uess we could parse out a lot of cert info and add to SIP headers and send = forward. If there is no trust relationship (let=E2=80=99s say the Ingress P= roxy is an enterprise SBC and the registrar is a service provider) then we = have a problem.

In HTTP there=E2=80=99s a CONNECT method so the SIP UA can establish a dire= ct TLS session to the registrar through a proxy. There is a very old expire= d draft for a SIP connect method that could potentially be helpful here.
I do remember that we had a SIP Connect draft many years ago.

Any ideas?

Cheers,
/Olle
_______________________________________________
sipcore mailing list
sipcore@ietf.org<= br> https://www.ietf.org/mailman/listinfo/sipcore


--

Ash Wilson | Technical Dire= ctor


=

This email and all d= ata transmitted with it contains confidential and/or proprietary informatio= n intended solely for the use of individual(s) authorized to receive it. If= you are not an intended and authorized recipient you are hereby notified o= f any use, disclosure, copying or distribution of the information included = in this transmission is prohibited and may be unlawful. Please immediately = notify the sender by replying to this email and then delete it from your sy= stem.

--0000000000008de75105b4ddd12c--