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

Roman Shpount <roman@telurix.com> Wed, 10 July 2019 03:29 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 CA0051200E5 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 20:29:06 -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 47HpL6enyRgJ for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 20:29:05 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 02E9C1200E3 for <sipcore@ietf.org>; Tue, 9 Jul 2019 20:29:04 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id p184so372703pfp.7 for <sipcore@ietf.org>; Tue, 09 Jul 2019 20:29:04 -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=0T+KLlBq5fLV2Zc9026K83DRPMhXPYMWPh9zjlacX4U=; b=qNFqPs7tj+BLOw0587fjbfim4gbwKO/4H3vByn4OlvmOcawb12R8Yoi59HThCGED8K u54WBJoPhjHbETIugNdEf0gK4c+4GN6YpnXBJ2B6tfZbFDCz2GcH4lClSsiYYq2DmQnU yIL39HAiLu0mK7LV+2OmNEiBqsj4lfseM5akpWyBya5GH5CwtNkzI+WvWl2Wq/wde8tw BhS9uO/FcaaWhAj6qA3oWZ6ZfQyBPACJhbqv2rtKEljdNUNm5Bohd2G60uKq/DbU4SKl 8ssRmhmD9X+MFsne5pVgWngKIWV0QedcVk3ksS8dwN8UuN1rqSY+FF7g6WMEGFGVswk6 L9CA==
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=0T+KLlBq5fLV2Zc9026K83DRPMhXPYMWPh9zjlacX4U=; b=qLgXhCfEMeLnC1jVgMrr0kK/yL9P6NjMhdMZsw/mHnKghOvD4vUNj6QSiXPecwArMc EHMHyi1A8eZgSpK1XWLPGKHumDF1vFS11nV8clcJEjhGRJ3bSTYORugl2G+QvELgnB1U 7XdCuQ14pf3yJGbF/wp7ZXaBnAPgp1+wh2bg3mx7RHnpoqXV6kAFvyRZbK7ct0rmFO9t oBYquGnjriEJ2qAP4AMaGBtfHhCbM41KVyhiqHjKibHoNzrph5caAByiB/UyAG3pVYKf lpASbmk6TCxNQp/Y0ydjfddT/68RoY1P+x4s6HLxYqtSa5CIGUIq+V7KtvkPhfmLnYhN s1/g==
X-Gm-Message-State: APjAAAVJWxHTgenW8vRIXFgpc1K+y9uon8z3BXqNVoEWVclaFCwVFOi8 MGZeKOCHYUCvYICokiecS9KRmZMLBQA=
X-Google-Smtp-Source: APXvYqwHQNe4WKR1pddvlyb1HDDeu61/UNrUPeqViXuStGnK6E+oolnIiDSuw4ykZtGhVFLUCYEO7A==
X-Received: by 2002:a63:1c22:: with SMTP id c34mr24812079pgc.56.1562729343729; Tue, 09 Jul 2019 20:29:03 -0700 (PDT)
Received: from mail-pf1-f176.google.com (mail-pf1-f176.google.com. [209.85.210.176]) by smtp.gmail.com with ESMTPSA id c5sm438408pgq.80.2019.07.09.20.29.01 for <sipcore@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jul 2019 20:29:02 -0700 (PDT)
Received: by mail-pf1-f176.google.com with SMTP id 19so379290pfa.4 for <sipcore@ietf.org>; Tue, 09 Jul 2019 20:29:01 -0700 (PDT)
X-Received: by 2002:a63:7a06:: with SMTP id v6mr34822323pgc.115.1562729341452; Tue, 09 Jul 2019 20:29:01 -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> <CAGL6epJWXBTcnNk3nMN3Yfsh5y6+pddQSW_MbkAdNZbmWf6_Gg@mail.gmail.com> <CAD5OKxt=sJhKGRRFPUon=JokbJ2Vb=P7GcfJ8LpXt_Yp-eOg3Q@mail.gmail.com> <CAGL6ep+CGEs8OW4vO2vNuGg8co9rXiUiD1JWaR9W7BBm8+SpQw@mail.gmail.com> <CAD5OKxsmXUjFP0mGELdPxCgXKwDs+9iYKE327fB1Jtn0jsXAbg@mail.gmail.com> <CAGL6epLg2-gEuL=eHe+84W=wPUMO3dPRGBk-MPT_K6_Qr+_L7A@mail.gmail.com>
In-Reply-To: <CAGL6epLg2-gEuL=eHe+84W=wPUMO3dPRGBk-MPT_K6_Qr+_L7A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 09 Jul 2019 23:28:49 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsoELbipY3M+1WSOEx_ymAp5BQ_7y0APW7hbW3+-Md8Rw@mail.gmail.com>
Message-ID: <CAD5OKxsoELbipY3M+1WSOEx_ymAp5BQ_7y0APW7hbW3+-Md8Rw@mail.gmail.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000470549058d4b4758"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/8j_c-mqDdB-KfCR74T6kUrKm9mw>
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 03:29:07 -0000

Can you then explain, what is covered, ideally providing a real world use
case?

Roman Shpount

On Tue, Jul 9, 2019, 21:59 Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> wrote:

> Such a use case is not covered by this document, and is out of scope.
>
> Regards,
>  Rifaat
>
>
> On Tue, Jul 9, 2019 at 9:44 PM Roman Shpount <roman@telurix.com> wrote:
>
>> On Tue, Jul 9, 2019 at 9:29 PM Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
>> wrote:
>>
>>> For me, the main motivation is SSO.
>>> The user would use one set of corporate credentials to authenticate,
>>> login to a deskphone, and get access to SIP and non-SIP services.
>>>
>>> I am not sure I am following your use case.
>>> How would the user authenticate and obtain a an access token in this
>>> case?
>>>
>>>
>> The use case is the same SSO in combination with hot desks and multiple
>> PBXs. User picks a desk at a remote office, goes to a web page to login,
>> enters his credentials and desk location. Expected result is that the phone
>> on this temporary desk will ring when user gets a call on user's extension
>> on the user home PBX. Internally, SSO system produces a token, which is
>> sent to the PBX in the remote office. PBX in the remote office registers
>> using this token with use home PBX, and configures that all the calls for
>> this registration are forwarded to the phone on the user temporary desk.
>> All the calls placed from that desk are also placed through user home PBX
>> so that correct line is used and user home caller ID is displayed.
>>
>> Best Regards,
>> _____________
>> Roman Shpount
>>
>>
>