IETF Logo Mail Archive

Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 28 May 2019 21:54 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9E0D120020 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2019 14:54:33 -0700 (PDT)
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_HELO_NONE=0.001, SPF_PASS=-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 GZUPFM5pgPHu for <ipv6@ietfa.amsl.com>; Tue, 28 May 2019 14:54:32 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 A041312000F for <ipv6@ietf.org>; Tue, 28 May 2019 14:54:32 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id w22so6725pgi.6 for <ipv6@ietf.org>; Tue, 28 May 2019 14:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fG03Pu4gh2aWFb9ZnSbScWMW5+mBiTP/sbJvqiGuZhk=; b=MJd67Mz6RCb/dVVJ414GNZSoxbMzolGJcAKczXelSd2jcVE9H5NKKdcEJ4tkRRszpW Dq85FF3Ho4aHsxO0BkeVL8b8JCsmJk7zoG+SZbryh0Rmz0L68W9IlyYK/hSAT+NAK8q6 8DHpe2ENgF5InlZKXt7mmzgqRkJKU1qo3iWfIX4hg8uhBk8N03x0GLEQ3r5UK5eWXqRB FF/OksvjQtpLxloDbany5J+qgMyqwRoz858YUvJ3kTQUOdoxcqnJDYuSaaX4/PiXSQPl cIuHwaNakxflyy109eJBUzdIAUSLqEiL0wLOwNQxyBv2yVIzPFR4VXvEA2nrkmj3bgb3 dHPw==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fG03Pu4gh2aWFb9ZnSbScWMW5+mBiTP/sbJvqiGuZhk=; b=Ad9UdQCemoJxQMsnYdtcxfl3CvzhK8feCYkrjOXUoYB+KhXeuXCtc4cPM4SiYtLT14 Of2qJwEvra1cnBb6EGn95S/ZVwFx/7J59ctsC5JjmSSxnESGq0mCOecY9vOPS84QEKYK 43BF+SQZigFaNiWP1soXvg3FoHyt+623NfUJDUMqXx5HlgjOyhBUjFEcvUGw7f2fHMbD XegZDWjdol3Ycjx5cHtftGKehnYuii1U3zeOeOW8pMYyBQ7oQdrIOaI2SpoAp7DDsJn5 dnU3t/qx4oJtH3WU/VSrTJtErdohFW16dqeiBw9egzcouEJZSeXYLFHv7rIU1p897F9U a4ng==
X-Gm-Message-State: APjAAAXc7wzgL/zaxhAVQzJfE+xnV4miMiCB1vElYCOi6oN7ynWJFKFq ZZPAI1mdTX13FJneBUDaQajWJCG/
X-Google-Smtp-Source: APXvYqxDyiDkxOEcGMC2aa/+FKS+O9oBhNXoTFEK9IzJ+IsmVX22SVuN1OdvgUkJOulDg0DpY2SDew==
X-Received: by 2002:a62:1a51:: with SMTP id a78mr45237270pfa.39.1559080471863; Tue, 28 May 2019 14:54:31 -0700 (PDT)
Received: from [10.71.7.45] ([119.17.54.66]) by smtp.gmail.com with ESMTPSA id y7sm5654502pja.26.2019.05.28.14.54.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 May 2019 14:54:30 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <561d9dc3-c769-c774-8f65-f975ac2a10a0@gont.com.ar> <m1hT1DZ-0000HEC@stereo.hq.phicoh.net> <ce07ade8-5105-055f-4798-f4ef20a2393c@si6networks.com> <CAN-Dau02MYCrKx2BgyuYJeHBdoz6SHCnp+-byM+LMM8af0S+rA@mail.gmail.com> <40e99171-6dda-29e3-6152-da5ca5219ed9@foobar.org> <CAN-Dau0ALqfAA-Dz56oHAfOtY7E2obx5E7TgoeH357Mckp3t9g@mail.gmail.com> <093ba8e2-6f0a-4c91-9df1-cda33fffea97@foobar.org> <CAN-Dau3kVqb+ZEHB7iPGeRuq1Mu8UHR3FEZv8SgmiqZexaFhuA@mail.gmail.com> <12db9629-f92a-e12a-5ff1-7db2c5d2137e@foobar.org> <F6F0C9DC-545E-4FE5-BB4C-55BB29022E84@steffann.nl> <CAO42Z2yUDi3FHOZsLrHqwLsEWkB1X9FREa8m6dU6ecOr=SsX4g@mail.gmail.com> <E51102E7-D4F0-4469-8888-5072F624EE06@steffann.nl> <CAN-Dau1S57wQ+3+m+m5grMe5N2SdfFqhELteSYfkmAC85_8H3w@mail.gmail.com> <8523a960-d551-1c24-d756-10c1840289de@foobar .org> <CAN-Dau27O9QB9MHhk81RsewwpH=xW=D1ZrUDmEq+WP0_Fyeh5Q@mail.gmail.com> <m1hVeWz-0000HvC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <789fe5a4-aa48-1ce4-8226-d7f73c2c24d7@gmail.com>
Date: Wed, 29 May 2019 09:54:27 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <m1hVeWz-0000HvC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ub0SCnfnk0iJyid6CZJyMlB2c00>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2019 21:54:34 -0000

On 29-May-19 04:00, Philip Homburg wrote:
>> Filtering by itself leaves hosts sending futile traffic and wasting battery
>> power, and RFC2563 by itself leaves the network susceptible to hosts that
>> ignore the signal from RFC2563.
>>
>> The requirement to do both seems perfectly reasonable to me. If you are
>> going to ignore peoples requirements don't be surprised if they ignore your
>> solutions.
> 
> It seems to me that any switch that can implement RA-guard can also limit
> IPv4 traffic to just DHCPv4.
> 
> In addition, any host that is really concerned about battery lifetime can
> just keep IPv4 LL disabled until needed by an application, i.e. a phone could
> enable IPv4 LL only when the user wants to print something and other ways to 
> discover a printer fail.

Wait, on that argument the host shouldn't waste resources on IPv6 either. The
theory here is that the desired endpoint is IPv6-only in switches, routers
and hosts, in a world where dual stack hosts have to be ready for dual stack
operation for obvious reasons.

    Brian

v2.23.0 | Report a Bug | By Email