Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-token-authnz-02.txt

"Olle E. Johansson" <oej@edvina.net> Wed, 10 July 2019 07:08 UTC

Return-Path: <oej@edvina.net>
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 8F1BF12011C for <sipcore@ietfa.amsl.com>; Wed, 10 Jul 2019 00:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 oerSN1frs1Zq for <sipcore@ietfa.amsl.com>; Wed, 10 Jul 2019 00:08:11 -0700 (PDT)
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 DA454120105 for <sipcore@ietf.org>; Wed, 10 Jul 2019 00:08:10 -0700 (PDT)
Received: from [192.168.1.80] (static-212-247-19-62.cust.tele2.se [212.247.19.62]) (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 3520DA40; Wed, 10 Jul 2019 09:08:07 +0200 (CEST)
From: "Olle E. Johansson" <oej@edvina.net>
Message-Id: <EBC3DB59-FA4A-454A-9EC3-BD3EF52F73A5@edvina.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1D09B734-6563-4FC4-9524-8581C9284904"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 10 Jul 2019 09:08:06 +0200
In-Reply-To: <CAGL6epK8Z938pnMKVyWGBK=6fMzNq6+gmxro-AAO2nzvGT4jeg@mail.gmail.com>
Cc: Olle E Johansson <oej@edvina.net>, Roman Shpount <roman@telurix.com>, "sipcore@ietf.org" <sipcore@ietf.org>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
References: <156249821133.14592.1211919336596009446@ietfa.amsl.com> <CAGL6epLsP_UfZMAcFLsORrR05Enu-vp=jnkgUFuKSttQm8swAw@mail.gmail.com> <c8d5c42e-ab21-80e8-3189-c8592dd02d3a@alum.mit.edu> <HE1PR07MB3161C55955B2FCED2C0F6A9993F60@HE1PR07MB3161.eurprd07.prod.outlook.com> <68ed93ae-57df-6bc7-774b-47959417abda@alum.mit.edu> <HE1PR07MB3161D46B4A44FC7E789ADDB893F10@HE1PR07MB3161.eurprd07.prod.outlook.com> <4a9787e5-b5e2-bc08-0fa0-fae6bd44148d@alum.mit.edu> <527F4C39-F065-4335-A939-6D443F1801E7@ericsson.com> <CAD5OKxuK_2+JcbGvo6LNeRbCYXWXQmhKQPNUzoZvZEOupPWyjw@mail.gmail.com> <HE1PR07MB3161612130F07C8F727A2BB693F10@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxtR-WBhfa4msbAfXoK7JowYaKK3fSCbw0cXm6SRGwkLxg@mail.gmail.com> <CAGL6epK8Z938pnMKVyWGBK=6fMzNq6+gmxro-AAO2nzvGT4jeg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/6Oa6kELin44U6uDw33pfQ98fq_o>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-token-authnz-02.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 07:08:15 -0000


> On 9 Jul 2019, at 23:16, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> wrote:
> 
> This document is specifically focused on confidential UAs.
> UAs running in the browser, public UAs, will be addressed in a separate document.
Maybe you should make that more clear, as it is very confusing terminology… I see that section 1.2 in your draft defines theses
types, based on RFC 6749. You apply it to the term “UA” which I think confuses things. A “public UA” may have support
for confidentiality, but not from an Oauth point of view. I think we should look for other terms for this.

In addition, I don’t find any text in your draft indicating that “Public UAs” is out of scope.

/O
> 
> Regards,
>  Rifaat
> 
> 
> On Tue, Jul 9, 2019 at 3:29 PM Roman Shpount <roman@telurix.com <mailto:roman@telurix.com>> wrote:
> On Tue, Jul 9, 2019 at 3:11 PM Christer Holmberg <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> wrote:
> >> As far as I know, OAuth for SIP has only been used for REGISTER requests, between the UA and the registrar. 
> >> I have never heard about anyone using it for non-REGISTER authentication, and I wonder whether we even need 
> >> to cover it in the draft. We could limit the scope the REGISTER requests. Then, if anyone ever needs OAuth for non-REGISTER requests, a separate draft can be written.
> > 
> > Really? Normally, for a secure solution, every SIP request, including requests sent by UA in dialog established from the 
> > server to the registered end point must be authenticated. OAuth for REGISTRER requests only is kind of useless since it 
> > does not allow UA to send any messages to the server without some additional authentication mechanism.
> 
> Not sure what you mean by "secure solution", but UAs can still use SIP Digest authentication.
> 
> What I am saying is that only use-case for SIP OAuth I am aware of is for REGISTER.
> 
> How do they get these SIP Digest credentials?
> 
> I am looking at a very simple SIP-Over-Websockets client scenario:
> 
> User logs into the web site which uses OAuth. UA, running in the browser gets a token which is used to Register UA with a SIP proxy.
> 
> What credentials is UA using to place a call (send INVITE to the proxy)? 
> If a call comes in from the proxy to UA, what credentials is UA using to hang up the call (send BYE message)?
> 
> Best Regards,
> _____________
> Roman Shpount
>  
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org <mailto:sipcore@ietf.org>
> https://www.ietf.org/mailman/listinfo/sipcore <https://www.ietf.org/mailman/listinfo/sipcore>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore