Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-02.txt
Lorenzo Colitti <lorenzo@google.com> Mon, 05 March 2018 05:08 UTC
Return-Path: <lorenzo@google.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 41DC3126C3D for <v6ops@ietfa.amsl.com>; Sun, 4 Mar 2018 21:08:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 RSN7eFQu3nX6 for <v6ops@ietfa.amsl.com>; Sun, 4 Mar 2018 21:08:27 -0800 (PST)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 B1CDE124B0A for <v6ops@ietf.org>; Sun, 4 Mar 2018 21:08:26 -0800 (PST)
Received: by mail-wr0-x235.google.com with SMTP id k9so15834224wre.9 for <v6ops@ietf.org>; Sun, 04 Mar 2018 21:08:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=48H8bCdy22bvm2towxQJcSbH+y2TFaiL8QyT9v+0yFY=; b=ZPEEgmmU2a3gE6jBuZ/43fyugcpMJNd1t866ujDv4JUzmNAK6X93k89X288eBJcuB2 9KuulzQqOU6VkIx5w/n9c5nzcl1bz6lBexWA2guUlOHoehd8PWa0H5nmo4B2tleCPk0u OQcG/sWjjhKp9rcQ6oGDPVj8ngGfSNDNDhLJa9Ab0cWlqgS/7DmRALT2bvhNXsEyhh0w zpKHq0l6xdJcO/qIetcepe1/HphLkJlacLwbMKl6arIB2H3DMMSeu9frUrMDDfYmE+8m E/Kt6EEkYtPaeHWa6he0YH7FzRUqK17AD+5eIWBy+yB4sTe7aGBeYoGW8XfiAbnDFFdH 81Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=48H8bCdy22bvm2towxQJcSbH+y2TFaiL8QyT9v+0yFY=; b=QjmG3G+rBCScrBmebqeWe9OulxGRb90f0vO1X4OcHX4k9C+8XW9+cYyiy1B0F6IiNl EQnqp4/4MIIcVujwUY1emFc4N9jnxlXufNhPd+7sYzwmVIqnkpjGaB7ATB6LXCltIWIg IaOmZ8i0HCmKOCZY3mlCKIdm4YYq4XJn8VqIU9WfXQqcNnqC7+yZCGgoeQ4VPVn0SHmL MZkAelq+voamqbxito4zWS2jAtUCiy2/tlf1H8RVwaMuxebS7bidbk/NdbABFEb7XckH h5c1fYV/XLZL4XGZg1k5ZypwAw+lp1doUjhoGk2nYtNVHOTJyuqwdxTU5RIg1OlC87YW 3gZA==
X-Gm-Message-State: APf1xPCrvMHtDY1nb3ZK4VSLcVG2GYI+NXGmJXanDW4AOYGT/FlVUV8J kpEKjPk+0QSqZ48DomLEgu/5J8YhUdwv1Kzlzv5b4Q==
X-Google-Smtp-Source: AG47ELuUvSpagHqt6/HSvvaOtEBv2JdgZbpMnZnemhlW9/sEPqukhKy61xg6oXDx54t2aSBV0pMXmVuQbCNLfw9lWq8=
X-Received: by 10.223.145.67 with SMTP id j61mr11911824wrj.152.1520226504954; Sun, 04 Mar 2018 21:08:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.63.79 with HTTP; Sun, 4 Mar 2018 21:08:04 -0800 (PST)
In-Reply-To: <152021615239.27925.6946415833371012617@ietfa.amsl.com>
References: <152021615239.27925.6946415833371012617@ietfa.amsl.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 05 Mar 2018 14:08:04 +0900
Message-ID: <CAKD1Yr00qjz7z8VF5=WeZ+baBPxJfmnYVhvNqKn_m7gu9H2GTA@mail.gmail.com>
To: internet-drafts <internet-drafts@ietf.org>
Cc: i-d-announce@ietf.org, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c06b392cecae80566a350ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jC-iTNbpbqmSmcOnbrfTRBvSCxo>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 05 Mar 2018 05:08:29 -0000
On Mon, Mar 5, 2018 at 11:15 AM, <internet-drafts@ietf.org> wrote: > Title : Requirements for IPv6 Routers > Authors : Zaid Ali Kahn > John Brzozowski > Russ White > Filename : draft-ietf-v6ops-ipv6rtr-reqs-02.txt > I continue to object to the one-size-fits all approach taken in the document. Here are two examples of how that leads to harmful outcomes. Saying that mobile phones (which forward IPv6 packets when the user desires them to) should support YANG, SNMP, and syslog would just be ridiculous if it wasn't harmful (because it creates the potential for a security vulnerability - the more remote management code running on the device, the greater the risk of vulnerability). Saying that mobile phones must support DHCPv6 is harmful, because: - If DHCPv6 is enabled, it's harmful to users for the reasons explained in https://www.ietf.org/mail-archive/web/v6ops/current/msg26286.html . - If DHCPv6 is disabled, it's harmful to users because somebody wrote code for something that's never enabled. - I don't think there will ever be any other choices than the above two, since no popular OS will provide a configuration mechanism for the user to enable/disable DHCPv6 on the mobile hotspot. (If you don't agree with that assertion then consider: those OSes don't even allow the user to enable/disable IPv6. Why would they allow the user to enable/disable DHCPv6?) Authors: the last time v6ops dealt with a "kitchen sink shopping list" document of this sort was RFC 7849. That document generated a lot of noise on the mailing lists, went back and forth for many months, and ended up being withdrawn as a WG document and published as individual submission which has zero normative value. I assume that's not your desired goal for this document? If so, I would suggest adding an applicability statement that clarifies that not every piece of equipment under the sun that ever happens to forward an IPv6 packet must meet these requirements.
- [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… Pablo Alvarez
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… 7riw77
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-… 7riw77