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

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Tue, 28 May 2019 17:39 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 47B30120048 for <sipcore@ietfa.amsl.com>; Tue, 28 May 2019 10:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ISS9UoqrDIRq for <sipcore@ietfa.amsl.com>; Tue, 28 May 2019 10:39:16 -0700 (PDT)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 26B251200FA for <sipcore@ietf.org>; Tue, 28 May 2019 10:39:16 -0700 (PDT)
Received: by mail-it1-x12b.google.com with SMTP id t184so5766725itf.2 for <sipcore@ietf.org>; Tue, 28 May 2019 10:39:16 -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=m9mE3AVYPvtYNNFM+KRyu/6Qz9vgLo7N7qGs31rEPIc=; b=NaK1S+R6mfI6DTLlD8VOHXXxpsjtQE2iGvx+uIriRGGx4nPFQilY1RruOnXhzRfD1j PCr+j4kxSgk2U+/caTd/Lvnt9Gl3dnCCgWIF5p88qEyuDwx7aSdt8P8KHRiRvgtpg6YF qwzHMwxeFMb57+o/nzk1MCq4v1JMe2xaNhutFEZNyD18/8WFogDmlvxpmYJ3ZINoo7TO 4HxrPbgAtleii6/cF74u5aiNWf86NjJCYeICF2THSN2HjseyHNYXLZuSjI4TPYzXZULk gYFdlnMj++anavxSZfmVs5JQZTM2YwbSySFmTxA3Z9ip9kW06tq7hK/YK7ZQIyup7oJD 2UYw==
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=m9mE3AVYPvtYNNFM+KRyu/6Qz9vgLo7N7qGs31rEPIc=; b=hAiAiSMZE0OFBll4q1rT9wYFK74q9Hw8cXzP5nObzhHE2YylmNMTcaIsFkgZk4oO9s KELLTHMvJ6sxMA5K4Lf9efdKOK54vHhCHwXhLILdiY/5TrNtAXXhwDqEIAT8JJP3BxCw PlrNN15xl9bDdfsg/eeLA2SgRd+wg4kZLGqmBmShZU8JD/GCfIWmZ2+SObN3j+TgYS/e IothSWl+dkZ/iR0OKNwPmZiE1JdS/9g5cvLrgNblAEmI0p+7G11kkXzW2+dk2z/8oCb/ C0enkhV/0DjlUrFD0z7FK52b63bFtaoEMy8+eOjDQsO1jieN1zBSGebqgdbOe/uA7//3 cOCQ==
X-Gm-Message-State: APjAAAWFBkRuIejPYXI4SGRDsHKBbedscWbTQzv8aqT2Q2T3cQZnGZcm KHSDwfxX2jPFIHtv2T/CA4T4wvG3g1rbm+D1Kdo=
X-Google-Smtp-Source: APXvYqx2C7tqIkLdG8dtT42r/jb6DDLUFCu6G1vwNFGERZyH1yEx83YphIp/jDwM571D/FJkpIVCyNfcGG1/W87XG0g=
X-Received: by 2002:a02:84e6:: with SMTP id f93mr7205126jai.73.1559065155283; Tue, 28 May 2019 10:39:15 -0700 (PDT)
MIME-Version: 1.0
References: <155905748376.25697.10287747269016979905@ietfa.amsl.com> <CAGL6epKcPW55GDZ0f65okQoaoQbT8XWVAfXUMU2PUCY4fKqCTg@mail.gmail.com> <7FE4D8D8-A62E-4322-B87C-973CF77C1141@ericsson.com>
In-Reply-To: <7FE4D8D8-A62E-4322-B87C-973CF77C1141@ericsson.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 28 May 2019 13:39:04 -0400
Message-ID: <CAGL6epJx4xYaZx1dtBuytRzBNgnWWxAMUGme7Re+n1Mi2KQsvg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c3302b0589f62445"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Pn4hRlj2TSotvI0RP8FH-prwc2U>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-token-authnz-00.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, 28 May 2019 17:39:19 -0000

There is some technical addition related to the type of token being issued
(JWT).
Also, the security section is still empty.
I would like to first hear from the WG about their view of the details of
the draft.

So, I do not think the draft is ready to go WGLC at this point.

Regards,
 Rifaat



On Tue, May 28, 2019 at 1:26 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> As far as I know, there should not be anything technically new in this
> draft: it contains the stuff we agreed to move from draft-ietf-sipcore-sip-authn
> into a separate draft.
>
>
>
> So, my suggestion would be to give interested people a couple of weeks to
> refresh their minds what it’s all about, and if nothing major comes up then
> go for WGLC.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From: *sipcore <sipcore-bounces@ietf.org> on behalf of Rifaat
> Shekh-Yusef <rifaat.ietf@gmail.com>
> *Date: *Tuesday, 28 May 2019 at 20.04
> *To: *"sipcore@ietf.org" <sipcore@ietf.org>
> *Subject: *Re: [sipcore] I-D Action:
> draft-ietf-sipcore-sip-token-authnz-00.txt
>
>
>
> All,
>
>
>
> We have just submitted this draft as one of the drafts that will replace
> the draft-ietf-sipcore-sip-authn draft.
>
> This is based on the discussion of separating the existing draft into two
> new drafts that address the different use cases in the original draft.
>
>
>
> Please, take a look and let us know what you think.
>
>
>
> Regards,
>
>  Rifaat
>
>
>
>
>
> On Tue, May 28, 2019 at 11:31 AM <internet-drafts@ietf.org> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Protocol Core WG of
> the IETF.
>
>         Title           : Third-Party Token-based Authentication and
> Authorization for Session Initiation Protocol (SIP)
>         Authors         : Rifaat Shekh-Yusef
>                           Christer Holmberg
>                           Victor Pascual
>         Filename        : draft-ietf-sipcore-sip-token-authnz-00.txt
>         Pages           : 8
>         Date            : 2019-05-28
>
> Abstract:
>    This document defines a mechanism for SIP, that is based on the OAuth
>    2.0 and OpenID Connect Core 1.0 specifications, to enable the
>    delegation of the user authentication and SIP registration
>    authorization to a dedicated third-party entity that is separate from
>    the SIP network elements that provide the SIP service.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-token-authnz/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sipcore-sip-token-authnz-00
>
> https://datatracker.ietf..org/doc/html/draft-ietf-sipcore-sip-token-authnz-00
> <https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-sip-token-authnz-00>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>
>