IETF Logo Mail Archive

Re: [stir] JWT/JSON (was - Re: Review of: draft-ietf-stir-passport-05)

Dave Crocker <dhc@dcrocker.net> Thu, 04 August 2016 18:41 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64EAE12DAC1 for <stir@ietfa.amsl.com>; Thu, 4 Aug 2016 11:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.209
X-Spam-Level:
X-Spam-Status: No, score=-1.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 jwQtIOeg0k3a for <stir@ietfa.amsl.com>; Thu, 4 Aug 2016 11:41:40 -0700 (PDT)
Received: from simon.songbird.com (unknown [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B52312D1BC for <stir@ietf.org>; Thu, 4 Aug 2016 11:41:40 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u74IfaSd002741 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 4 Aug 2016 11:41:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1470336097; bh=IWeEmvmUkNBCO1gLzBZFL1y7cLhf2khqAv4YxLYKjvs=; h=Subject:To:References:From:Reply-To:Cc:Date:In-Reply-To:From; b=E0smv2Q4Z6srmtkynTYpcbBGAhYW4K30WUmnbhvQIkF4OHDpSGSK8aNcJ3uJMP789 zom0h70VtEcMDDLbtnoiCj5JWKQ+YNyd3s8MH/QA0SeAgPs/GklN78NscnvhacZ9jX h1+m6GWUwoflemqTxtfxA9eWPdmWaFQSxZWCBo1Y=
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <07e0eb16-6758-cdf1-c571-1f1ed768e741@dcrocker.net> <D3C152B2.1A69BA%jon.peterson@neustar.biz> <b096b541-c8af-9617-c9d7-5a1beb5230e8@dcrocker.net> <D3C16040.1A6A09%jon.peterson@neustar.biz> <d66d91f0-9ea2-6295-e749-e48ea37b4892@dcrocker.net> <cfd714ce-6145-1b60-aca2-ae702a8c133d@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B4771FF73@ESESSMB209.ericsson.se> <5fdf4ad3-1528-3d79-6bdb-b5eb350e5c2a@alum.mit.edu>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <dbb24381-55fd-fa64-d32b-fcc50265ccab@dcrocker.net>
Date: Thu, 04 Aug 2016 11:41:21 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <5fdf4ad3-1528-3d79-6bdb-b5eb350e5c2a@alum.mit.edu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/b3bId7kryiDfA2SzrOzzEXoZMtQ>
Cc: stir@ietf.org
Subject: Re: [stir] JWT/JSON (was - Re: Review of: draft-ietf-stir-passport-05)
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2016 18:41:41 -0000

On 8/4/2016 10:03 AM, Paul Kyzivat wrote:
> I have been loosely following this discussion. IIUC, one of Dave's
> arguments is that SIP implementations don't currently involve JSON, so
> introducing it with STIR will further complicate those implementations.
>
> But, again IIUC, the use of JSON with passport doesn't require anyone to
> *parse* JSON. It is only necessary to *generate* a very special purpose
> JSON and then generate a signature over it.


Clever point.  I think you are correct, except for the contents of the 
so-called "ppt" parameter, which does require parsing.

Now about JWT...?  From my reading, so far, I suspect the answer for JWT 
is the same as for JSON?



d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email