Re: [v6ops] draft-linkova-v6ops-nd-cache-init to working group draft

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 26 July 2019 09:38 UTC

Return-Path: <swmike@swm.pp.se>
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 C471A1202F9 for <v6ops@ietfa.amsl.com>; Fri, 26 Jul 2019 02:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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=swm.pp.se
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 XMheXqFgb7c7 for <v6ops@ietfa.amsl.com>; Fri, 26 Jul 2019 02:38:05 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BAC41202F8 for <v6ops@ietf.org>; Fri, 26 Jul 2019 02:38:05 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D4CD3B1; Fri, 26 Jul 2019 11:38:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1564133880; bh=zhj49B5emI1IP/GbrSPOtS2OTa1EkIZex//twe31j+c=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Et8+wQazh1OvkddbiPatL/pMdp2mR3XT72vIXJpiw4RVFws2ixOVPmtJAQE+CEw2t BuFOZ6dJO6AkqMWQW7UdujJICIHCnS8AjpEmL/uajbYdx7SInKQwSBTaIRjZJ2rKYQ dDPl+dTyStacejcsA4ybh3FJcxfhNs4yjNxmM8Gk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D2C60B0 for <v6ops@ietf.org>; Fri, 26 Jul 2019 11:38:00 +0200 (CEST)
Date: Fri, 26 Jul 2019 11:38:00 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <351E8A83-734C-448D-B0C6-212C09D564F4@gmail.com>
Message-ID: <alpine.DEB.2.20.1907261134570.19225@uplift.swm.pp.se>
References: <351E8A83-734C-448D-B0C6-212C09D564F4@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/h3wtV9PGkN3zz-Ew7ygmy_ulAew>
Subject: Re: [v6ops] draft-linkova-v6ops-nd-cache-init to working group draft
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: Fri, 26 Jul 2019 09:38:08 -0000

On Tue, 23 Jul 2019, Fred Baker wrote:

> In yesterday's meeting, the sense of the room and a discussion of charters at the mike suggested that draft-linkova-v6ops-nd-cache-init should become a working group draft. Doing so will require 6man to agree to let v6ops suggest specific changes to RFC 4861 under the rubric of "operational solutions", as discussed in the draft and https://datatracker.ietf.org/meeting/105/materials/slides-105-v6ops-neighbor-cache-entries-on-first-hop-routers-operational-considerations-00; the argument for not kicking those out to 6man is that the authors of RFC 4861 are no longer in a position to approve errata to it, which would be the other obvious approach (I'm not sure that's true of Erik Nordmark, but whatever). It would also need to be considered to update RFC 4861.
>
> Do we agree to take draft-linkova-v6ops-nd-cache-init as a working group draft?

I support making this a working group draft, this is a problem we should 
solve.

I'd just like to check, have the authors checked the proposed solution 
list against https://datatracker.ietf.org/wg/savi/documents/ to make sure 
the solutions we're proposing are not in conflict with behavior SAVI 
prescribes?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se