Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to publish
Allison Mankin <allison.mankin@gmail.com> Mon, 21 May 2018 16:09 UTC
Return-Path: <allison.mankin@gmail.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAD5128961; Mon, 21 May 2018 09:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_PASS=-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 mv861jWvBTMA; Mon, 21 May 2018 09:09:25 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 BEB3A12E8C2; Mon, 21 May 2018 09:09:25 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id a20-v6so7316407pfo.0; Mon, 21 May 2018 09:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=U796yv9i4cderEg0j3BEAw6xBrOSXLh1ac1GjfKF45E=; b=P/DvSjrajS1cGY6iQuJQVoqoUXKMKYKCAxiogrem9kmbW5RCXLp+H+OZd/SLp3F/XV Xp47nu22AlbeqfAvu5m2g+pdGG1nwxPPndrOpvC8ZP1fyY8lN5JJ3am/B+6rFo2aGLpn LVTMcSLcK50miL773AmLtW748Qash9PTUEvNZjj7L6HEK5bye126CCsl0jp8hFAi8vl0 TCD+XQ1oCYg1rbCd9nAV322Bnu1UMPiuN0Jn36jonFw7kfKTYhAYsXHEv57PulwkIyIn 5++K4XqxlRzhW8+kUBHRpK5AyiaALmeQvZl0RxW51Csl0YMdGam6MtJQpyMthgMGHTFg 6tPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=U796yv9i4cderEg0j3BEAw6xBrOSXLh1ac1GjfKF45E=; b=ZGd33Q+jiFRuPC9LuT3NnxP3e8vMq26kG+C3O9f+QqYpZnW3uCkaP5Dmy17olIpeJy G5Oq9lq42T8mv+1BCbbNfDtMGMm2C/TvX1mECKGUliikgeojXOwIOmorFkkLekKX4P4X 6J/TIGSz33MfKZOhtraev4R0m34OsMhuDbTYjTis/AJPfeSoEszV+SWgAYt2+HPnYyfr gTz5LunbrlqcVzXa/kBAcwaGF5WXcRaVav3wssxopzWlWUhg6gEtifTOO7aQSHpqJXGI jq0S/XBHDb9cDiF/dsWhjKeFSsh8hfmKQEvbfbRIAi9URrqCmuNf1s0lg+pTl0d6iH7+ 6nmQ==
X-Gm-Message-State: ALKqPwf8T7OlCOGLjFW0gEQE3vAxTahM19g10Z1ZlV6k1vNTDlsn9fJP 8EzFIgzZ+BmDBGpZql2hCvO2ixVTNdxeP4KkLxw=
X-Google-Smtp-Source: AB8JxZqUJSg7g5wbzYONpUQbe6skMmjCnksair/fsTfg18UkZFeXhzvpTI/WVXdfoq9IZwVzvBHIMhAZoRb6bazNYEk=
X-Received: by 2002:a62:91b:: with SMTP id e27-v6mr20538929pfd.93.1526918965226; Mon, 21 May 2018 09:09:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1991:0:0:0:0 with HTTP; Mon, 21 May 2018 09:09:24 -0700 (PDT)
In-Reply-To: <CAKKJt-d6XyjEK66RU1K6mFR--+CubKR4UBrJK93TNzdN4ayh1w@mail.gmail.com>
References: <00ed01d3efd8$50af5a80$f20e0f80$@augustcellars.com> <CAKKJt-d6XyjEK66RU1K6mFR--+CubKR4UBrJK93TNzdN4ayh1w@mail.gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Mon, 21 May 2018 12:09:24 -0400
Message-ID: <CAP8yD=ujWd5t0Fm70y2q0N+eHJLL4-CVua_LPb-bvNZL-aTUYA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Jim Schaad <ietf@augustcellars.com>, "irtf-chair@irtf.org" <irtf-chair@irtf.org>, "t2trg@irtf.org" <t2trg@irtf.org>, "irsg@irtf.org Steering Group" <irsg@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000085f452056cb986e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/rAElWAOfjbOuYALRYjsyjgctQgI>
Subject: Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to publish
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 May 2018 16:09:29 -0000
Hi Jim and all, I’m taking a look and will request the IESG’s conflict review later today. Allison On Monday, 21 May 2018, Spencer Dawkins at IETF < spencerdawkins.ietf@gmail.com> wrote: > Hi, Jim, > > On Sat, May 19, 2018 at 8:17 PM Jim Schaad <ietf@augustcellars.com> wrote: > >> This draft has completed the IRSG poll with a final result of 2 'Ready to >> publish' (in addition to the implicit RG chairs positions) and one 'No >> Objection'. The positions have been recorded in the data tracker. >> >> A new version of the document has been published to deal with the last of >> the IRSG Poll comments. >> >> I have sent the message to IANA for review and have received a response >> (IANA ticket # 1109425) from Amanda which says that no IANA actions are >> present. >> >> Stephen Farrell did a review of the document back in February. He made >> many >> suggestions to the document which were mainly adopted, but still expressed >> some skepticism about the final worth of the document. What I read as >> his >> major reservations were 1) A worry that this document was expressed as a >> sales pitch and as such might have some limited long term applicability, >> 2) >> A worry that some of the references to current work (SUIT and OSCORE being >> two) in a long term document may not be useful, and 3) Some of the >> document >> might be better if it were re-organized. >> >> Vincent Roca did a review and requested that issues around privacy were >> highlighted to a greater degree. He recognized that this might need a new >> document to be fully addressed, but felt that it needed to be stressed >> more. >> In addition to this he provided a solid review that lead to some >> significant >> fixes to the document. Vincent expressed that his comments were >> adequately >> addressed before responding to the poll. >> >> Arbnor Zeqiri volunteered to review the draft, but not follow through as >> near as I can tell. >> >> Finally, Spencer Dawkins provided a review of the document that mostly >> focused on nits with some small questions that have been addressed in this >> last update. I have gone through his review and the edits and believe >> that >> they have been adequately addressed. (Most of his comments can with some >> suggested text.) >> > > I agree that my comments have been adequately addressed. Thanks to you all > for that. > > Spencer > > >> If you have any questions please let me know. >> >> Jim >> >> >> >> >> >> _______________________________________________ >> T2TRG mailing list >> T2TRG@irtf.org >> https://www.irtf.org/mailman/listinfo/t2trg >> >
- Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to… Mohit Sethi
- [T2TRG] draft-irtf-t2trg-iot-seccons ready to pub… Jim Schaad
- Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons r… Stephen Farrell
- Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to… Spencer Dawkins at IETF
- Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to… Allison Mankin
- Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons r… Mohit Sethi
- Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons r… Mohit
- Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons r… Stephen Farrell
- Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to… Garcia-Morchon O, Oscar
- Re: [T2TRG] draft-irtf-t2trg-iot-seccons ready to… Mohit Sethi M