IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Mon, 08 August 2016 23:24 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 50B2112B030 for <stir@ietfa.amsl.com>; Mon, 8 Aug 2016 16:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 gmOTd6lQ-Gyb for <stir@ietfa.amsl.com>; Mon, 8 Aug 2016 16:24:34 -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 9F70D12B012 for <stir@ietf.org>; Mon, 8 Aug 2016 16:24:34 -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 u78NOWs4030340 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 8 Aug 2016 16:24:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1470698672; bh=Ly50G2j788KSZ1lIIoF0gWjmm2Ptd3Oul/0g+gPGiys=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=f6PNGfKlBKOKTWkASRxzLYRuLDHHypqGynGqB9o+AW+IO3LSGET3Iw7gIlkzWzsX+ qzrMmiVbBsdGFXDQpM0Pba+Vvae1e2K7SMxM+21oyFdZWW1PEeqNqE5Uj9NPUkcI8d yOJkQr6sb8MGA1Jq96Ot2nOud0x9ftoZtapoqgHE=
To: "Peterson, Jon" <jon.peterson@neustar.biz>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <07e0eb16-6758-cdf1-c571-1f1ed768e741@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> <dbb24381-55fd-fa64-d32b-fcc50265ccab@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B47723C55@ESESSMB209.ericsson.se> <503738d8-c166-dfc1-d153-338d56b844c1@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B4BBB1D69@ESESSMB208.ericsson.se> <51D45AE5-67D2-4120-BCA2-7BFC845E2126@neustar.biz> <fe9c9960-55f3-1187-f093-9adf13aaf841@dcrocker.net> <D3CE482C.1A6E69%jon.peterson@neustar.biz> <01df1722-2cb0-d238-dcb4-df101a657820@dcrocker.net> <D3CE549C.1A6E8E%jon.peterson@neustar.biz> <c356412b-dfa5-6d3e-2762-f69adafba476@dcrocker.net> <D3CE5B89.1A6EAA%jon.peterson@neustar.biz> <6688dd94-5c7e-4a9c-f873-69c4eb33f59a@bbiw.net> <D3CE6020.1A6EC1%jon.peterson@neustar.biz>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5e418462-1670-75f8-6c68-6857ceff4a09@dcrocker.net>
Date: Mon, 08 Aug 2016 16:24:06 -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: <D3CE6020.1A6EC1%jon.peterson@neustar.biz>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/aj7a70Kn9gZBV-q_BTvMr0IPcvo>
Cc: "stir@ietf.org" <stir@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
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: Mon, 08 Aug 2016 23:24:35 -0000

On 8/8/2016 4:14 PM, Peterson, Jon wrote:
> In that case, if the list has heard your issues, I'd be interested in
> knowing how much support there is for implementing the changes you
> proposed.


Jon,

It appears you misread my note.  What I asked for was that the feedback 
I provided be processed in the usual way it is done in the IETF.

That is:

On 8/8/2016 3:45 PM, Dave Crocker wrote:
> In order to avoid having authors do a guessing game about what will
> resolve questions and concerns, they normally pursue those items on
> the working group's mailing list.


Unless things are done differently in this part of the IETF, it is not 
considered normal IETF process to request working group consensus about 
whether to respond to the details of a review...

But perhaps the word 'respond' is unclear?  In the IETF it means to give 
meaningful responses.  That's quite different from, say, automatically 
expecting suggestions to be agreed to.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email