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 01:59 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 8A7E3120096 for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 18:59:07 -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 E5XGccMEmjto for <sipcore@ietfa.amsl.com>; Tue, 9 Jul 2019 18:59:05 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 3D9CD120048 for <sipcore@ietf.org>; Tue, 9 Jul 2019 18:59:05 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id k20so1212227ios.10 for <sipcore@ietf.org>; Tue, 09 Jul 2019 18:59:05 -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=iTFNtJaSpbz+P4EQ5acqkaIoHCZquoZxThHpmXv/Hso=; b=piL/0JwxQiG/7RKt4WQFYRQDpE98AiY6SZVOL/7HzR+7wu5jS1Aib6tKeEZWGcpUQI yHg/wje3B0pl8CNRrje1VwpU2RdzvrRZHtaopt6T86d5Yxa8XnF6OvtFT0KY/yzsspTH yzFdbYWp8y0Mzb+xnwUbOsjlgEvVs/GKy53qEm8Sj7qyfaUTzTeLZzcOlqXrqV10uVXi sFaQFXkFXobkxfWo5vBGDbnHC914+rHcJg8S9v3Lb/ol6R0ROlPElJwizvN8r9ROg7kV trUh9mQcjhNhfsFOOP5ffCYgekE48Jt2cHoSDasMH7MHQapLHkVp3L7/1w0kw1TjooCU ZkTg==
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=iTFNtJaSpbz+P4EQ5acqkaIoHCZquoZxThHpmXv/Hso=; b=J0/iSOb7eCTq7hjsOEDBKCsQg4SVDOLifiB2m1L65LPMg8j97a3xnjOerLGdjU4dk2 Z56drp66loNWcxLe6sUGkE0b1COXWPAVa4/dop7RmWDeo6Y9SVGzOkwrjmwVDn+TTltY No8H/pFVNNFVUvBya0qxXlenbiSbijfAAoI25O4yvys/p3iIW9bUU5oSmZGyaNZwtZup 547SxhXTyKU1hZaPDl88Lo/JSd2jKYxfRb0PbIDIMevQFQQ7EYUcLdtvN1v+Afe2bb1C P9mTjk6fTvv2NuFBmQKf+m1Q+SxygvEdwunmuzXbj9D1/ubsySP+n/AnDbH6sYvkM8iU 69pw==
X-Gm-Message-State: APjAAAUy6UXJc9kuaXDQha2EjaW4sRpLCZsbkzVQ/ncZVM0NxnF6pt0l 6Ml3/TXToj8W4UfWAWa1nFA9cWLWl++G38MNhS0=
X-Google-Smtp-Source: APXvYqxzOBMy/yJ1X4ZYdzez8oZGkeD6oXwCtj104fm7A3TX52LCXtpkPX4uRjYJNNk/cUssKEKcOTZcaUd3NzszLc4=
X-Received: by 2002:a5d:9642:: with SMTP id d2mr11195701ios.278.1562723944415; Tue, 09 Jul 2019 18:59:04 -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>
In-Reply-To: <CAD5OKxsmXUjFP0mGELdPxCgXKwDs+9iYKE327fB1Jtn0jsXAbg@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 09 Jul 2019 21:58:54 -0400
Message-ID: <CAGL6epLg2-gEuL=eHe+84W=wPUMO3dPRGBk-MPT_K6_Qr+_L7A@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="00000000000096c9ab058d4a05db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/8tJXTwVzPFIJL7J6uj8DOG8R6XU>
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 01:59:07 -0000

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
>
>

v2.23.0 | Report a Bug | By Email