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

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Tue, 09 July 2019 21:16 UTC

Return-Path: <rifaat.ietf@gmail.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 5FF1D1200C7 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 14:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 y_olFjTFaOtC for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 14:16:49 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 7281312006F for <sipcore@ietf.org>; Tue, 9 Jul 2019 14:16:49 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id j6so97862ioa.5 for <sipcore@ietf.org>; Tue, 09 Jul 2019 14:16:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LqLxrhekE+RTwYEOhIxmp2o/w3P+C3N/F78AmdKyFxI=; b=KKyqW52fgw//pQIeHLSiOcFrNq7S9LtszUAWGijdYQ8cYMMtC2hz6TnksltTdowOU4 gja3zeij6HeasaObDz788RFXLmIpvFeW2Ix88Kh1dwcPFGaUhgIkownigDksckSpflEW vaANAfeLyjsiSg2LRNofpP7AeXmzRcX+N5qIuM4b4y7AeJTqWOsI+/zfpJVcemdEXAVY E27UyvY9ZYe8AMQSpK6A5B53R7XJ4VdhprbaHaaRitSlBf7EolJD87/Zm8e/ZrQTAQve UnsojST4sVyLV0T3ah/32OuToy0cmXDWbLVTFbXNoIIeebQzfbiC0adh/T5+bKjLz5zi HWkA==
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=LqLxrhekE+RTwYEOhIxmp2o/w3P+C3N/F78AmdKyFxI=; b=XaCEuu9wQ0wV5iOKgrKIgbQoJTMfOrSInnzVyosSZOaZQKIxY6Gwxnc0AqnusDV7np f57vGBYPaEbapKPXVabaN/8Gns3C3phOxXpfFzVP+4qCpBl6v8rgwBHqACl2IStLG/5D I9GrYbh4mZb7ZnihSmlfEFcKcE89/aWJVstatMnm7wjH1613xxQ4q74hdLZxzrQTMjwB kRl9HwcxvHa1oeDRHRajMpDlsjsumQduSDwGknBB7KnvrhfRU8sTNwPbB58AgRU41v3U V0nzcEx9B9YnzUqQ8wHdKH7mKOfUL5GBjlcCR7clBq39QeDpe1yQFLh+KaBt4u+X0QRH gWWA==
X-Gm-Message-State: APjAAAUNEHjp4HWhFWJFZAg76XOcir/jCXgEPX2TFgWDP9pRYH++E6AF xCcmXlw9M9E5l7U7vf9TK2Gn2Ams2hY1pujwWaQ=
X-Google-Smtp-Source: APXvYqxHnwwOhtvG74oFOzWNp2+DVIKa4ZkKBKrwD3aZXRqxnmUHFwDMTB556xq/kumbFWlsFXbRxrwaxBt1gmfXkxg=
X-Received: by 2002:a5d:9282:: with SMTP id s2mr1691632iom.36.1562707008790; Tue, 09 Jul 2019 14:16:48 -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>
In-Reply-To: <CAD5OKxtR-WBhfa4msbAfXoK7JowYaKK3fSCbw0cXm6SRGwkLxg@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 09 Jul 2019 17:16:39 -0400
Message-ID: <CAGL6epK8Z938pnMKVyWGBK=6fMzNq6+gmxro-AAO2nzvGT4jeg@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000025a475058d46144d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/g4tCDlX4iuwxvZEyuLiEaRya5uI>
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 21:16:51 -0000

This document is specifically focused on *confidential *UAs.
UAs running in the browser, public UAs, will be addressed in a separate
document.

Regards,
 Rifaat


On Tue, Jul 9, 2019 at 3:29 PM Roman Shpount <roman@telurix.com> wrote:

> On Tue, Jul 9, 2019 at 3:11 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.
>
> 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
> https://www.ietf.org/mailman/listinfo/sipcore
>