IETF Logo Mail Archive

Re: [hrpc] draft-irtf-hrpc-association-02

Joseph Lorenzo Hall <joe@cdt.org> Thu, 28 March 2019 14:15 UTC

Return-Path: <jhall@cdt.org>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67ACC120474 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 07:15:25 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 Za1VSdKLKywA for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 07:15:23 -0700 (PDT)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 21A7D120459 for <hrpc@irtf.org>; Thu, 28 Mar 2019 07:15:22 -0700 (PDT)
Received: by mail-ot1-x334.google.com with SMTP id m10so10837534otp.2 for <hrpc@irtf.org>; Thu, 28 Mar 2019 07:15:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QxAz5IE4yP8NL76AcCMINpRl3j2kG5dhPxN8PN8372E=; b=bagGGnWi8G6vTq4yLsWQSKL9XZZmn2c7OQA4b8KR5UCwpuHPJsSf8MDcY+0U8hoMHD lNCM5zNjTNjOP+FeotqQ2ACITGmeX5fNvKOopSVLvyVzzT12Sob1uAw1Q4MsCYJsX7yi 3uSJeFtRX17oxqso/RhSgLr8kfkzPXZzqU9fc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QxAz5IE4yP8NL76AcCMINpRl3j2kG5dhPxN8PN8372E=; b=mmaKFLXXrCvYIrYtQp8z2d4NK2DIX/gLujCD6jdjrGmKenVakowmJLthyN9PlkVgKK 15ABMMhK+P3WSv5dcCqd1RaP6HTkViLhUVp36SVu4WkGY7H4bZ76hrpgYrD8VCOYaG/k I82zhjGWiOkwHP3sco1S2J81q2TG2ecFS4Ri45SM/IGhoV9klYuDC/GXjjcfjH1Vd19/ yMyJKRmjT7KpcjEaALrpAE6HzH9VNc+rCL1acxysDd4hsrJb75MGg4ew4UuJ4etBaM8u wlvoCTW7t4gTr78LV3+yW42E7suj5hqAPx+ijWFXdbHt0dpAMHsJSKNTpwgv+SoHqBLK syHA==
X-Gm-Message-State: APjAAAVik7L8cnuSO00TZJ7WSc0Q1a0aIkxjzq1F8Ztg2avkY/cBXC0D EBCP7zMTSO+bd/O4PImhr1IP1jZGAF5ykAKewwRuewI7tdPycQ==
X-Google-Smtp-Source: APXvYqzhOKaKBaUbzlw9z4NeiqI632YFxxjb8XwXHcvwnx6PXL/1Lpq7bpI+mns3XbR4hj6BTlPF0mtrN2ILgXeHM0E=
X-Received: by 2002:a9d:5f06:: with SMTP id f6mr30074852oti.18.1553782521299; Thu, 28 Mar 2019 07:15:21 -0700 (PDT)
MIME-Version: 1.0
References: <0555df8d-5a4b-e78c-774a-b9665e1c5ca4@nielstenoever.net> <b620a6d4-2f3e-40bf-a8b6-40083b1dd23e@avris-iPad>
In-Reply-To: <b620a6d4-2f3e-40bf-a8b6-40083b1dd23e@avris-iPad>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 28 Mar 2019 10:15:10 -0400
Message-ID: <CABtrr-VWD=1SeAzxrxrPLQV225J08DHW4N1Tu1qasAYeZnugxg@mail.gmail.com>
To: Avri <avri@apc.org>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000003d9c230585282f49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Dc3Z5DdQ7vAReQP6u49sBVzipQ8>
Subject: Re: [hrpc] draft-irtf-hrpc-association-02
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2019 14:15:26 -0000

On Thu, Mar 28, 2019 at 9:50 AM Avri <avri@apc.org> wrote:

> Leaving aside the rest of your responses for a later time after more
> consideration.
>
> Regarding the point below, RFC Editor made a special meniton on this sort
> of thing yesterday and asked that people not leave such issues for the RFC
> editor..
>

Big +1 here; we should give the RFC Editor as clean of a document as we
can, hoping that they will need to make as few changes as possible. We can
do it. best, Joe

v2.23.0 | Report a Bug | By Email