IETF Logo Mail Archive

Re: [sipcore] Draft new: draft-holmberg-sipcore-auth-id-00

worley@ariadne.com (Dale R. Worley) Mon, 27 October 2014 21:15 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70EEF1ACE30 for <sipcore@ietfa.amsl.com>; Mon, 27 Oct 2014 14:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 Fm_F6LBZa-sr for <sipcore@ietfa.amsl.com>; Mon, 27 Oct 2014 14:15:34 -0700 (PDT)
Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 271681AD53A for <sipcore@ietf.org>; Mon, 27 Oct 2014 14:15:34 -0700 (PDT)
Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-01v.sys.comcast.net with comcast id 8MFJ1p0044vw8ds01MFZVd; Mon, 27 Oct 2014 21:15:33 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-04v.sys.comcast.net with comcast id 8MFY1p00E1KKtkw01MFYKx; Mon, 27 Oct 2014 21:15:33 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s9RLFV2Z004632; Mon, 27 Oct 2014 17:15:31 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s9RLFV0j004631; Mon, 27 Oct 2014 17:15:31 -0400
Date: Mon, 27 Oct 2014 17:15:31 -0400
Message-Id: <201410272115.s9RLFV0j004631@hobgoblin.ariadne.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-reply-to: <7594FB04B1934943A5C02806D1A2204B1D4CC977@ESESSMB209.ericsson.se> (christer.holmberg@ericsson.com)
References: <7594FB04B1934943A5C02806D1A2204B1D4CC977@ESESSMB209.ericsson.se>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1414444533; bh=VfWsuJWTatsRlE8gNqLaTmtDc+Gl3QRToNTgn+DxBF4=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=LyYoEcKiPGwBdOpTw2FEm+Lsd7k0nlzXu6SPHce1DQ9EqChexiYVSrfzmi1WmtVpY TNwWDRqyFnknO2glc/v+6NRcIQDXxRE5EiS9MaSftDk0Kc6078PAxt5OLqujdZxig6 N9UeN+kVvB9qCwcAijkkXPWBUcgB8TMogCHbL6kzCOHCPKjBibGgaDaN1Zoq9LXFGI t/a7aJjzePikjPbcFMUQ1Ydi+UR46wimarPsKxXqBep9Rz8KVB/XBWMWBnRtOoige3 Hxu2TSp7uIsYfaddmi891Gj3QyEJuAZs8CW3eLcV3M1KkBT99BGQ/X3leJ3J69aTHi PC0nUz0PNbN+w==
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/FhMiDqMHFayd5KQbPyq1tVPmyJI
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Draft new: draft-holmberg-sipcore-auth-id-00
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 21:15:38 -0000

> From: Christer Holmberg <christer.holmberg@ericsson.com>
> 
> I've submitted a new draft, draft-holmberg-sipcore-auth-id-00.

It would help if the Abstract was rewritten so that one did not need
to know the meanings of "eP-CSCF", "WAF", and "S-CSCF" to understand
what the mechanism can do.

> The draft defines a new Authorization header field parameter, which
> can carry a string value identifying an authorization server, based
> on a requirement from 3GPP (the mechanism is general, though).

The text says that the "authorization-entity" parameter carries "a
string value which represents the identity of an authorization
server".  You might want to expand on that.  I'm guessing it means
that any entity that wants to verify the authorization of the REGISTER
request should present the request contents to the specified
authorization server.

Dale

v2.23.0 | Report a Bug | By Email