Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

Di Ma <madi@zdns.cn> Tue, 10 April 2018 07:54 UTC

Return-Path: <madi@zdns.cn>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758091200A0 for <sidr@ietfa.amsl.com>; Tue, 10 Apr 2018 00:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 y9nyRR9dWUSF for <sidr@ietfa.amsl.com>; Tue, 10 Apr 2018 00:54:15 -0700 (PDT)
Received: from smtpbgeu2.qq.com (smtpbgeu2.qq.com [18.194.254.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDEEB12704A for <sidr@ietf.org>; Tue, 10 Apr 2018 00:54:12 -0700 (PDT)
X-QQ-mid: bizesmtp7t1523346845tpbw8ruma
Received: from [192.168.101.95] (unknown [218.241.119.117]) by esmtp4.qq.com (ESMTP) with id ; Tue, 10 Apr 2018 15:54:03 +0800 (CST)
X-QQ-SSF: 00400000002000F0FH43000B0000000
X-QQ-FEAT: AU3gs7VM8fW/ZdA6Jc2dPvKnwxIjBRy4WFKlyNfKQ/EFcg4xwEEO8dtzBmYKe hB+Ouu8+GGDCFmvsyfjXRgThwa7RAxzy6Fx/UHdboksrARldeM9MfN8db8WSDhq0Ia/Ng2W 10R7KDSM2x6y/5sRoQFIbe2Ti8xuFRlzPUrP3zJpGBDC1dMFizJxAKqSY4EIUyBNVeEQqH6 HV/QCghcZEJNBgj2RnitlfHejo7t90Cvw7+S2E6wONqUc3SEzzHxrWGK0W7DUqyrHbXo3xm Zd8h0guni/qZySeV8Wn94opOdJ9gwRBOVWh9lX7yXX1/o3
X-QQ-GoodBg: 2
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Di Ma <madi@zdns.cn>
In-Reply-To: <5DE6E2DB-42D9-40ED-BE48-17544419A1FA@nostrum.com>
Date: Tue, 10 Apr 2018 15:54:01 +0800
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, draft-ietf-sidr-slurm@ietf.org, Alissa Cooper <alissa@cooperw.in>, morrowc@ops-netman.net, sidr-chairs@ietf.org, The IESG <iesg@ietf.org>, sidr wg list <sidr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAD3FCC5-C312-4373-8E24-18729B3571E2@zdns.cn>
References: <152286484194.23960.17788058701508276433.idtracker@ietfa.amsl.com> <F171E1D6-FD3E-40DC-870F-947D3073DA0D@zdns.cn> <CAKKJt-f9A5m7cq9=UttdiP+jxrivq7TUYF7-PBe+HSUTWULmSg@mail.gmail.com> <5DE6E2DB-42D9-40ED-BE48-17544419A1FA@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3445.5.20)
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:zdns.cn:qybgforeign:qybgforeign1
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/sLYcjcsOtK4NCNHnWUAm7Iz2fm4>
Subject: Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2018 07:54:22 -0000

Hi, Ben,

Thanks for reminding us:-)

Di

> 在 2018年4月10日,02:28,Ben Campbell <ben@nostrum.com> 写道:
> 
> 
> 
>> On Apr 6, 2018, at 10:06 AM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
>> 
>> Hi, Di,
>> 
>> On Fri, Apr 6, 2018 at 9:33 AM, Di Ma <madi@zdns.cn> wrote:
>> Alissa,
>> 
>> Thanks very much for your comments.
>> 
>> Is BCP 14 exactly the same document as RFC 2119?
>> 
>> It was, until  https://tools.ietf.org/html/rfc8174 was added to BCP 14. That's the process doc that says readers don't have to figure out whether "must" is normative, etc.
>> 
>> Spencer, who is not Alissa, but had a second to answer the question
> 
> Also not Alissa (or Spencer), but to extend the answer a bit: RFC 8174 includes new boilerplate for treating only the upper case versions as keywords.
> 
> Thanks!
> 
> Ben.