Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)

Fernando Gont <fgont@si6networks.com> Thu, 28 January 2021 07:52 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB623A13C7; Wed, 27 Jan 2021 23:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 XsGj7Po7XLys; Wed, 27 Jan 2021 23:52:16 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B98AE3A138D; Wed, 27 Jan 2021 23:52:16 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2] (unknown [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 30D83283A41; Thu, 28 Jan 2021 07:52:12 +0000 (UTC)
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <20210128063819.GT21@kduck.mit.edu>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <4f8eb79c-d646-a4cf-4e6e-69226e2643bd@si6networks.com>
Date: Thu, 28 Jan 2021 04:50:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210128063819.GT21@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_poh3X8xPHPWZa4gEwLdCMldeiY>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 07:52:26 -0000

On 28/1/21 03:38, Benjamin Kaduk wrote:
[...]
> [...]
>>> Section 8.2
>>>
>>> It would feel more natural, at least to me, if RFC 7084 was listed as a
>>> normative reference.  (In the sense that we are Updating it to make
>>> incremental additions, but you need the whole combined assembly of both
>>> documents in order to have a functional setup.)
>>
>> I would assume so. But it would be a downref. Is that possible?
> 
> Most things are possible ... but with 7084 not listed at
> https://datatracker.ietf.org/doc/downref/ it might mean another IETF LC.
> Your responsible AD should probably be the one to make the call, and the
> "don't change it" option has a fair bit of inertia going for it.

Agreed.

Thanks!
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492