Re: [Anima] Ben Campbell's No Objection on draft-ietf-anima-prefix-management-06: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 14 December 2017 23:16 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAD8127775; Thu, 14 Dec 2017 15:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable 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 ndqn8Ez9yXfu; Thu, 14 Dec 2017 15:16:07 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 8145A12714F; Thu, 14 Dec 2017 15:16:05 -0800 (PST)
Received: from [10.0.1.99] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vBENFr9i048024 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 14 Dec 2017 17:15:53 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.99]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <218EBB0B-FEAF-4AA9-90BE-268E613F0686@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3A246D62-3DF2-4F94-85CA-3921D9A77826"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 14 Dec 2017 17:15:52 -0600
In-Reply-To: <407128de-3e9d-cace-82ec-71716c4b583d@gmail.com>
Cc: The IESG <iesg@ietf.org>, anima-chairs@ietf.org, draft-ietf-anima-prefix-management@ietf.org, Toerless Eckert <tte@cs.fau.de>, tte+anima@cs.fau.de, anima@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <151322520961.6124.6728640618034204081.idtracker@ietfa.amsl.com> <407128de-3e9d-cace-82ec-71716c4b583d@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/E3jcAJx4oaYjufkH2GCPMrbXApI>
Subject: Re: [Anima] Ben Campbell's No Objection on draft-ietf-anima-prefix-management-06: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 23:16:09 -0000

Just to close the loop: All of Brian’s responses look fine to me.

Thanks!

Ben.

> On Dec 14, 2017, at 12:42 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 14/12/2017 17:20, Ben Campbell wrote:
> ...> - On my first reading, I wondered why this was informational. It seems to seek
>> to standardize protocol elements. The explanation in the shepherd report
>> clarifies that; it would be helpful to include (a perhaps shortened version of)
>> that in the draft.
> 
> Awaiting instructions, but we can certainly do that if there's to be
> a new version of the draft.
> 
>> 
>> -2: RFC 8174 has boilerplate to address the "only in upper case" part. Please
>> consider using it rather than modifying the 2119 boilerplate.
> 
> Ack, the RFC Editor could do that too.
> 
>> 
>> -4.4: "It is therefore important to record all the prefix assignment history."
>> Isn’t this a local policy choice? Perhaps some operator believes in extreme log
>> minimization, does this mean to argue they are mistaken?
> 
> I'd say it is a requirement in order to detect or trace lost prefixes
> after outages, and probably a legal requirement in many countries
> (once jurisdictions realise that IPv6 prefixes are needed for tracing,
> not just addresses). But I agree that it isn't a requirement on the
> protocol defined in this draft, so it should be rephrased.
> 
> Thanks
>    Brian
> 
> 
>