IETF Logo Mail Archive

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

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Wed, 10 July 2019 00:30 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 05048120306 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 17:30:41 -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 gtynjbIk1_BB for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 17:30:39 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 5C1B512011C for <sipcore@ietf.org>; Tue, 9 Jul 2019 17:30:37 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id i10so844537iol.13 for <sipcore@ietf.org>; Tue, 09 Jul 2019 17:30:37 -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=CkekE8di0C0G9VUFsll/Qyn8Hq4phDwRuium0NlES6M=; b=dESoGohSx3xPNFFrfmu+EfJkZczWzHQ4X0WCVIdud9Yxe0ny4lDztKZRs+MMKMlL3H /eXmQ8vQgbgrjJ/NjuRAEzmKX3wkB5uCntdGolONIzAUQQFoOOyRAukYSSjiIaSe6wkS VJDnOrqaswCLzGSLA3zRHvQXAGWFy861XvtwoA831nKtsbN+iAaDwnjzglYXSlCqjBUh J7X1Bt1qbT5uc8/4k0dpBbLqXvC2FFztjL6JhR/dfBelwbbGXIWcMMQqMteeNBLbXql/ YHK8+n2rSwLG/r+g1XrtUurDyKmc4MegJZA99wTLgesT88wPA7nBTdk9Y1R8wt5FQs9K hwUg==
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=CkekE8di0C0G9VUFsll/Qyn8Hq4phDwRuium0NlES6M=; b=dA4p+kSwfN+xGbaes/I79cSLxGNGjuRs1OqUyv/3Rer8ym8f6CTF6rSYyim5ceBYG9 GX81By3hV1cNH4XJCLugDDytY2GE6ZwWeuAc0sDRuSGkhzU49dRTsRQvWLsEKwAPSrjy +U0sSNWZmlUq59PF6itgplrntYn8FEZ1I83p26Mf6SyI2MVwnNjJKSkA4FnyD7jg5MOC LXMjYVT1Tbno1x8p9a7fGOfj9VL9tqAUf6Y17PSoNKfn0Wt3yQR3fDPsU5QvIQXWMSCh qfJuGlzQ8fnnyfaMzmVb3VJJZXKkvxl2wHaaZ6naHRT2Qxp3Oy0OLlBkmSds+RefQPd4 SkkQ==
X-Gm-Message-State: APjAAAXZNkpfH9hJZW4b7lWgJ83UuR7hfuirzZccTWU7kEQt1W068569 WTe5sHDoc74XuRJSdZD4XpxYPIFs4CWnbOPiEhM=
X-Google-Smtp-Source: APXvYqzfxdOVJqO5r4J+yexOpHRg2FVMUjE9oVVjyc8J++8mLcsr2UiKjN/ltcmC+jujSsnguUkQHi06reRqk3Hxz24=
X-Received: by 2002:a5d:9642:: with SMTP id d2mr10808874ios.278.1562718636679; Tue, 09 Jul 2019 17:30:36 -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> <CAGL6epK8Z938pnMKVyWGBK=6fMzNq6+gmxro-AAO2nzvGT4jeg@mail.gmail.com> <CAD5OKxs6g+6mLbMRc9C0q5BSSn=+7HHzKf5Ya5uL-+RbhVfEaA@mail.gmail.com> <CAGL6epKfLWA=RW3T84feSud9sZ+TcpB=XRA6fvTzP-jL3h4+4A@mail.gmail.com> <CAD5OKxs3=XdOFYThY1gCu23M4nqJV-bJOSCU7-Ogn0J=xy+E3A@mail.gmail.com>
In-Reply-To: <CAD5OKxs3=XdOFYThY1gCu23M4nqJV-bJOSCU7-Ogn0J=xy+E3A@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 09 Jul 2019 20:30:26 -0400
Message-ID: <CAGL6epJWXBTcnNk3nMN3Yfsh5y6+pddQSW_MbkAdNZbmWf6_Gg@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="000000000000392646058d48c976"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ZHQLZdryOLLAoTkFQWEszjIAy8g>
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 00:30:47 -0000

The document clearly allows the use of access token to authenticate
non-REGISTER requests when challenged in the context of the same realm.

Whether that is needed or not is a different discussion.
Assuming the UA was able to authenticate the user and obtain an access
token, then establish an authenticated TLS channel with the server, and
register the user; is there a need for further challenges from server?

Regards,
 Rifaat


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

> On Tue, Jul 9, 2019 at 7:17 PM Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
> wrote:
>
>> Can you provide a real life example of confidential UA using OAuth for
>>> registration only and not generating calls or sending any messages in
>>> dialog (or using different authentication method for these actions)?
>>>
>>
>> What? why do you think that is the case?
>> How did you get to the conclusion that the UA will not be able to make a
>> call?
>>
>>
> Quoting Christer:
>
> 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.
>
>
> So, I am trying to understand the use case where:
>
> 1. UA is confidential
> 2. OAuth is used for registration only
> 3. Other messages are not sent or different authentication method is used
> for them, i.e. calls and in dialog messages are not initiated or initiated
> using a different authentication method.
>
> So far, I cannot figure out what this is.
>
> Best Regards,
> _____________
> Roman Shpount
>
>
>

v2.23.0 | Report a Bug | By Email