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

Roman Shpount <roman@telurix.com> Tue, 09 July 2019 22:57 UTC

Return-Path: <roman@telurix.com>
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 83086120075 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 15:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.592
X-Spam-Level:
X-Spam-Status: No, score=-0.592 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.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 LaicivLRnkO1 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 15:57:56 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 722A5120059 for <sipcore@ietf.org>; Tue, 9 Jul 2019 15:57:56 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id b7so142517pls.6 for <sipcore@ietf.org>; Tue, 09 Jul 2019 15:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rDMUCjZzZPiBa7WlDRmUm5QWCJKFZVrLe2Gj9ntswVM=; b=sYiMO/JKxDiuRmhf8OquCx682tZo0480j1uim9qUUV2sPCNS9aYG+ErmUeACX3XBmu abeOddC8MDjHcjoB2GObBOfJJzZMODbD9NU4cNwOJtKHD6E1VZOG+KK1XyYT/8F+hwqp lgWrE9mV1hyhUI2Bei/akbnMhsII6CYpzRUHaEXC41lHSpVj5mVmsNSUnipRXBmNeg8B vKPndLvwEh9Ar4OwehxWfxGZQ584GihhBXLuShi+d2iMceuka9WwkDUL83y5RtZZ6sr+ hWZl63lBpy+/XQowRr8Owq4HKeu1GDGee1TkwOoGbeIFu0Zmq5dKU5fKeIgoTBRE5Pgb QqFg==
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=rDMUCjZzZPiBa7WlDRmUm5QWCJKFZVrLe2Gj9ntswVM=; b=pSOmAVVzHJprPatR4rzwCnOg88lzBk4KXvvfGQjDjAZtVnMnr2oBgKW/ZdK7SmoiB3 gqWE/SBZx6N92diCVAiRt/0rk5lRvWRl6z5SFj6c0G4Vj1GZedOzyL0nSXlHCdOLfbfB /TJrms6MPKug6egTpBOKvbV8vVaTYlwc9/PvsP8ztIx8Xy8ryCw4UgRPrEYeFJEasN98 CYgPahPvOYx6HuCNbLEC5FBgtwdmJ2EChAfb+1e75sbaw56Tkxm421nbCOEpkWXBcFe4 b/JOJJLuwV8wKrAvneYAKBgKpinFgKqpsbjI+QMKrPn/qmklAEMYrVs+zr8LBRmj1Ltn +vAA==
X-Gm-Message-State: APjAAAW0hi5cvtav3kMz5ddjsXjAxoF3A/+edIxrmjfZH1D/j17bHDHs s6GbGLWReIDNEDYv2HdM2ekWpsf8hrw=
X-Google-Smtp-Source: APXvYqxM9TcymqmIK0nq12yenXOMxQFIZ1NVKjzcPkmVQxTqStkd4uasEDuKBSj5tTf2aV4UShZBng==
X-Received: by 2002:a17:902:2aab:: with SMTP id j40mr33474010plb.76.1562713075654; Tue, 09 Jul 2019 15:57:55 -0700 (PDT)
Received: from mail-pg1-f181.google.com (mail-pg1-f181.google.com. [209.85.215.181]) by smtp.gmail.com with ESMTPSA id p15sm139958pjf.27.2019.07.09.15.57.54 for <sipcore@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jul 2019 15:57:54 -0700 (PDT)
Received: by mail-pg1-f181.google.com with SMTP id q4so183006pgj.8 for <sipcore@ietf.org>; Tue, 09 Jul 2019 15:57:54 -0700 (PDT)
X-Received: by 2002:a17:90a:b104:: with SMTP id z4mr2816084pjq.102.1562713074138; Tue, 09 Jul 2019 15:57:54 -0700 (PDT)
MIME-Version: 1.0
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> <HE1PR07MB3161434F0C9714266EF22DF093F10@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3161434F0C9714266EF22DF093F10@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 09 Jul 2019 18:57:44 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtyGEkxbmTMLyTa6VObrQQTUGLFRHiGm1OaS2SaY+SurA@mail.gmail.com>
Message-ID: <CAD5OKxtyGEkxbmTMLyTa6VObrQQTUGLFRHiGm1OaS2SaY+SurA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ab8459058d477d36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/JsT-nRNrL1fGV-mj5YFauQbdi8Q>
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: Tue, 09 Jul 2019 22:57:58 -0000

On Tue, Jul 9, 2019 at 4:00 PM Christer Holmberg <
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.
>
> Wouldn't  you use OAuth to establish the WebSocket connection?
>

No, WebSocket connection is to a different server and typically does not
require authentication. In this specific case, I was thinking OpenSIPS with
SIP-over-WS support. Implementing OAuth authentication of SIP message would
be trivial there, but OAuth authentication for WebSocket would be much less
obvious.

>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)?
>
> If the registry and the call handling is part of the same service I guess
> you could use the same credentials, assuming 3261 generally allows using
> the same credentials for registrations and calls.
>

Are you saying using OAuth token authentication for calls (INVITE) and in
dialog messages (BYE)?
_____________
Roman Shpount