IETF Logo Mail Archive

Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld

Tom Ritter <tom@ritter.vg> Mon, 15 June 2015 23:57 UTC

Return-Path: <tom@ritter.vg>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCDC1B316A for <dnsop@ietfa.amsl.com>; Mon, 15 Jun 2015 16:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=no
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 9FzjOmL2Xm9Y for <dnsop@ietfa.amsl.com>; Mon, 15 Jun 2015 16:57:56 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (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 00C8B1A893E for <dnsop@ietf.org>; Mon, 15 Jun 2015 16:57:55 -0700 (PDT)
Received: by qcwx2 with SMTP id x2so323757qcw.1 for <dnsop@ietf.org>; Mon, 15 Jun 2015 16:57:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ritter.vg; s=vg; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=SYvs9pzK9LMZWo1WKxOtcr3o9U3olk3MW0Ey8cF6JaM=; b=dhiDGVfynS9xqCHf/NRRI8oNvTAOtdQnx9ME+BPROap5cUIScO2XUoocDZn3BzMyj0 3Z3tXdedWuZ05HYEw2bmvY/5hkICjOyOmC8F67zF+FraLZrgfHpgUiGaKrBTWkG/kybD QFB+s2YHWW3qywKI57CCWcLzbCn8YokpPKofY=
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:content-type; bh=SYvs9pzK9LMZWo1WKxOtcr3o9U3olk3MW0Ey8cF6JaM=; b=IzGnDZAV7UpWZ1TNuND46qrV5lpHNGvTePVJQ0NVhncXu/wIMhZDOCSWdUMtDmALEc FuMqWn7e6mzhBCLxuLJ7ir/WHs2ML6Ug1vluEcL1Dtx4qSfrH3uow7IhBNc6EhtJZB/v 5u0S53mZkTHnVhR6rds8ijKECc5fWWe6M797j1lmY0lanHw/xCFvkNZGtlhSdvek5veG 6Qw204hveODMg+Act7mIqAg2z7jrGULz1UW2SEIS6kK7Q35jkpR00ZhaJRKv+84PO88z 105ynqUs7j53zkQcgFcG/CbdZHKJjarhy/5jiQNXxFFTrlJigPCJ61cwoKrmfAM0fQL4 ZKSg==
X-Gm-Message-State: ALoCoQnHNANmBHm0jOHEXmAl14xxuU8UX7uthbFP1E7xFiAS6gxSFeVaQ7zqRkw01aPE49k7Gikz
X-Received: by 10.55.31.164 with SMTP id n36mr19360355qkh.76.1434412675323; Mon, 15 Jun 2015 16:57:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.51.103 with HTTP; Mon, 15 Jun 2015 16:57:34 -0700 (PDT)
In-Reply-To: <CAL02cgSdb4goJ=PaucvEHZp_0fssdPQ8t4z964Znp-_Hho6psQ@mail.gmail.com>
References: <555CC061.7040109@gmail.com> <CAL02cgSdb4goJ=PaucvEHZp_0fssdPQ8t4z964Znp-_Hho6psQ@mail.gmail.com>
From: Tom Ritter <tom@ritter.vg>
Date: Mon, 15 Jun 2015 18:57:34 -0500
Message-ID: <CA+cU71nGJkPEr2yU1c+J3MRVdkPBurfvAtVZ9aGXfPkpwg0-3A@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/_t_7kF6Wd_bEGkjaJlyf6bWMa0o>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2015 23:57:57 -0000

On 23 May 2015 at 09:35, Richard Barnes <rlb@ipv.sx> wrote:
> tl;dr: Ship it.

++

Nits:
 - Noted for the first time that the IETF boilerplate uses the oxford
comma. (I like the Oxford comma, but it seems most don't.)
 - "visually or apparently semantically similar to the desired
service" - not sure what "or apparently semantically" adds to this,
seems to be a repeat of "visually"

-tom

v2.23.0 | Report a Bug | By Email