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

Eric Rescorla <ekr@rtfm.com> Sun, 21 August 2016 17:01 UTC

Return-Path: <ekr@rtfm.com>
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 6BDE512B040 for <stir@ietfa.amsl.com>; Sun, 21 Aug 2016 10:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 N1sLOc0p__BL for <stir@ietfa.amsl.com>; Sun, 21 Aug 2016 10:01:04 -0700 (PDT)
Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::230]) (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 BF9C2127735 for <stir@ietf.org>; Sun, 21 Aug 2016 10:01:04 -0700 (PDT)
Received: by mail-yb0-x230.google.com with SMTP id a88so4370614ybi.0 for <stir@ietf.org>; Sun, 21 Aug 2016 10:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LEQp70w741i8MJKtb1lVVjUBw2LhdK3CwLoY1jXrhVw=; b=O/PsqRi7Y8B9AprR7jvMhnQFQS2qoosC45norlZTNAywZ1jlFOyr2RlPd9OOL6SIiH it+ifN7SY5fbuBle2uVLCfVo18BYuZX+J3xzWb+wl2f3ld1aK7jLj0LxOvBJXMdVfSVg WvH/WynBcqxqb10uQsgYsw4oGTgTUk2dWguSqrmzxzXDHfFO6Ssd76nxIC2YtGPTkLJd UDSvfkyP1Zhq7j9fW3ZF7UNVEmOtxtBUfb3iWuz1qUeQI7O002SKEebVZQi6DiRDJTIs ddx3/i3u172jnL8HwFbDWWUEPfieEllAZ6eu77Nq3NKA09EHKNIBxfL8YnW45kElDpvz HT7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LEQp70w741i8MJKtb1lVVjUBw2LhdK3CwLoY1jXrhVw=; b=AYYfmOZBp0Tx2zYnV9nsJ3Dz2jdSzYhXWC1xr5or0zXaMz2BpIZolqW+CFd8Fm3g19 3M/U+zU1PCsnf65x9mv1IiexXeVrbhlQzdG0HTfLzt7/aUWAK+n7/YR90JiBrYm3RMWb kIgp7tdingwwlMg1pzT1FUvnpZmDbVx3z7+HXKGgIP9xT1Zd5I2Lgo2FK9J5gfsi1Xt0 P4wYdICCWnqioCmsK9c5UhRp/bHe4xsVgdGjHX374VwG1ewKciVX2EbkRXRkw1ZyTWew bGdBQ9qocT1QwNiytaqUzX4gpeppQBDi61xf37Rvm0rysn30L6111AjCLKQ0Zk/R2wQi FmPA==
X-Gm-Message-State: AEkooutLNI6ALUUhMTc7qlLw4VhLRu4dQlRiOA/1MW8GV3cmHOJ7JNX9tF0Cv1lfYDs6V1YXStxlDOwJrYrYrQ==
X-Received: by 10.37.203.7 with SMTP id b7mr12516131ybg.162.1471798863171; Sun, 21 Aug 2016 10:01:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.48.193 with HTTP; Sun, 21 Aug 2016 10:00:22 -0700 (PDT)
In-Reply-To: <ca7ad669-02c8-fa6f-038e-9dc2b3284bb1@dcrocker.net>
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> <CABcZeBNQgsjDOrW2k4WOucTVXSMHjEUjKgGkhYT119Z3yoUv1g@mail.gmail.com> <ca7ad669-02c8-fa6f-038e-9dc2b3284bb1@dcrocker.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 21 Aug 2016 10:00:22 -0700
Message-ID: <CABcZeBPEP9nyahBeCCvpfA1etcX+4hZZwE-ysrRJUu70oPzbDw@mail.gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary="94eb2c05a3be6bd2bf053a97e0b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/jBYMEtVMiV92u4GbblUfsLIwytM>
Cc: IETF STIR Mail List <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
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: Sun, 21 Aug 2016 17:01:07 -0000

On Sun, Aug 21, 2016 at 9:29 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/21/2016 8:37 AM, Eric Rescorla wrote:
>
>> Dave,
>>
>> Whenever we want to add some cryptographic functionality to a
>> protocol [0] (especially when it's messaging/object security
>> functionality) we have to ask whether it would be better to define
>> something new, specific to the protocol, and hopefully simple, or
>> reuse something pre-existing, generic, and presumably more
>> complicated. In my experience, the history of those who take the
>> former approach is that we find ourselves reinventing a bunch of
>> stuff and that it's not as simple as we hoped [1][2]
>>
>
>
> We agree.
>
> I'm not sure what the point of saying here is, since it is highly
> consonant with points I have posted here more than once.


Well, I'm still wading through the traffic on the list, so sorry if I
missed them, but I took the message I was responding to be arguing that we
should not use JOSE here but rather should define something specific. Did I
misread you? If so, then I apologize and I would greatly appreciate it if
you could restate what you are proposing.

Thanks,
-Ekr


>
>
>
> d/
>
> --
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>
> --
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>