IETF Logo Mail Archive

Re: [v6ops] Discussion focus: draft-ietf-v6ops-ipv6rtr-reqs

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 05 January 2018 01:21 UTC

Return-Path: <brian.e.carpenter@gmail.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 049FB12785F for <v6ops@ietfa.amsl.com>; Thu, 4 Jan 2018 17:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fVP9wLBm5Nr3 for <v6ops@ietfa.amsl.com>; Thu, 4 Jan 2018 17:21:11 -0800 (PST)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (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 22F8E1241F8 for <v6ops@ietf.org>; Thu, 4 Jan 2018 17:21:11 -0800 (PST)
Received: by mail-pg0-x22f.google.com with SMTP id i196so1415856pgd.0 for <v6ops@ietf.org>; Thu, 04 Jan 2018 17:21:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Gn94InKKFKQOHRpa3Fs9EJCxoW9zUuJX3XwkdpCKPdQ=; b=V3Px8dLwCujOPmq+7dOY+AayVn3GR7g8KCGDSBDwx/c62PvdJu8eVBT1bzP3tuEPr4 k873agH9Znd2kn1BUNItTnfqkAg8unGfhxihpRk/17wZlodtNvFGeOjlwKBd4ZGGWfLI yEDa/xEscR0Cn3gFnuQfAv9hMoH7q24a6WgHxLKv4S3GQ0z4ufiM0mhsFkmBSOy1oDEn AQLkzyH47tefMDT2H+CyvTEgsarsB0joKwaKe4nUVcQhN/rNvgDwaEYokYwfZy3etXZO gb+up4Sx91nxcml6ybFpTALrnKiv6qH5yWQk6vJf33o1OFh0+LQrjo2fgbxtmuDhzWOK xKwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Gn94InKKFKQOHRpa3Fs9EJCxoW9zUuJX3XwkdpCKPdQ=; b=lwe2pXs9plnBNEOuiKJpTBGipSqOv+GLAnCTbn/FNBfnWURevfiFGufVghDT7LWNBR sBQh7YvkZ1A4wOJLAt3a9MUnvYf822kB/AqegiiGL9n4kmVl2P2K4k6l3ePKcjkQEtjK qt3RjiKtJrL3pZejru2x6SCDCpI3DtrQXkjBzIZHrYVtNIzL2F+Yc2s6iP8Sf9O11aCx VXSrcgrx9YFohufqUpW13A30nZzATPbPWATZAAi1cIryTiJvA/JdOJLpTzOLFwW2g/hh l5uQFgYgGYT5k4ZNW1CqIJxDbDlWHhL1NiBNkR51yXyByMf/FWrU7vP3HTPlQpP3yoz1 Pdkg==
X-Gm-Message-State: AKGB3mIA31eF/oo9kHvTFzgwErrgC+gCQTCkMbd1rukwdNlsU/Z4i8YY H27FVwxEtdNfmUzPXr9Cniaq/A==
X-Google-Smtp-Source: ACJfBosrpQBbPeV/ui8af+5wTClUUSbFdyLflvYfIkBFtJd8wR5AJKgRn0nuDBL0fITMwXw3Iq4IHA==
X-Received: by 10.99.127.29 with SMTP id a29mr1096932pgd.3.1515115270415; Thu, 04 Jan 2018 17:21:10 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id e9sm10557781pfl.138.2018.01.04.17.21.08 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 17:21:09 -0800 (PST)
To: v6ops@ietf.org
References: <B7CB2B98-F069-425D-A096-AADA0297B34C@gmail.com> <CAKD1Yr0r=OZKWHatcaV5ZfXUcJhTrzGqnd6wno7SLur9cJzF5w@mail.gmail.com> <066901d385ab$64d663b0$2e832b10$@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <95b93f9e-f3f5-0ae3-289d-f82f2eacd45c@gmail.com>
Date: Fri, 05 Jan 2018 14:21:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <066901d385ab$64d663b0$2e832b10$@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-pJlnE2iybX9oLaYNjG7_GUCmHI>
Subject: Re: [v6ops] Discussion focus: draft-ietf-v6ops-ipv6rtr-reqs
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: Fri, 05 Jan 2018 01:21:13 -0000

On 05/01/2018 11:28, 7riw77@gmail.com wrote:
> 
>> As the implementer of devices that are sometimes IPv6 routers, I object to the
>> requirement that such devices MUST implement DHCPv6. The reason is that
>> implementing DHCPv6 will degrade the user experience.
>> See https://www.ietf.org/mail-archive/web/v6ops/current/msg26286.html
>> for an example of how that can happen.
> 
> Being required to implement DHCPv6 is far different than being required to _turn it on by default_ -- the draft specifically does not require DHCPv6 to be turned on by default for this very reason. To argue that implementing something that may go haywire in a specific environment should lead to it not being implemented would doom BGP, OSPF, IS-IS, SLAAC... the list is almost endless.

Given that some customers require DHCPv6, I can't imagine why any router vendor
would be happy shipping a product that does not include DHCPv6 and/or DHCPv6 Relay.
So in a sense the only thing that makes sense in the draft is to recommend
the default status (on or off). "Off" seems reasonable.

   Brian

v2.23.0 | Report a Bug | By Email