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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 02 May 2019 23:52 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 6D0EF1206A3 for <ipv6@ietfa.amsl.com>; Thu, 2 May 2019 16:52:50 -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_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 BW63PShzlzkN for <ipv6@ietfa.amsl.com>; Thu, 2 May 2019 16:52:47 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 CBB58120699 for <ipv6@ietf.org>; Thu, 2 May 2019 16:52:47 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id e67so1912756pfe.10 for <ipv6@ietf.org>; Thu, 02 May 2019 16:52:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QS6tcckLpi3UXn4iKXC0oIn2Mq+W1/uo9acQUyaiJBM=; b=N4ND5QLqGgPwA3eld/MAZ4ls38C9PGfNTWFYUipau5fLa4bMejeFbz70RQySE+mGia AaIggzuZ2VD8Ke+/IBt16xReDzNNHahiyVpJPp381OAnLG+SmW5HlWxlYay+G0KJPZBx rTLBSFwpqzKLzoI0dnV3SuGnOVXKyiYaA1cynkykN5KH/EX+lLjorE6IZ56TguP96z00 Xw/jBp6v3hQkgEhTjitQ5j6mE54ENwMgKBsSyXiAc+cWHYupzyRA9YOqB30lV0/HiLnx oI5y5ZSduDifB2nG4Aym5QgaA/5D5PJDv1UuIcRQSAnt2+Ib9+k6+6Zlw6AHmFJ/xV2t kMQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QS6tcckLpi3UXn4iKXC0oIn2Mq+W1/uo9acQUyaiJBM=; b=SI9DUGenFQ57T34GT2eCh8HAmuoBWtZbpZ/JL3ot5sj/8htcgykVAyx9VBNyHdLw10 dW8o6j1zghnaiVUTWDWVHVzZxZJ5OihHFHWtuKjyiNInR7pRjVb1P4hbMnw56H71GVU9 0m+iIM6S3HCCFkKBZHbBMkv1wbsxHxgEpy8P3Tdf6oPaDohJZ/dSTT/6MsfUy21igdp0 XM24VEbL18bjsn9S/PyY5CDHlDlpxBv8exzpwsAkpZp6C3dDZ8t5k+0WWG5TFk8nXii+ uYgQSpgIQNyuev9yHhRzMOTwHkXurJceqiZYWf+AaXQEHl7dGdFvTY9Eu1wfjCg41AUp bTng==
X-Gm-Message-State: APjAAAVg81Sws0XvMPlGJu7cX7tE2+Wo3OtU4oIA+JTGqUaC+aYscHEI sBjZcsGBzSkp5zeQcVka9DbuT8JR
X-Google-Smtp-Source: APXvYqyCG2FHX9ntjXI5OWR4yTGG+np7ZUpT0gloS4OnwOTBpf+DtuaYplDRYrgOD5seyeGKPIUHag==
X-Received: by 2002:aa7:8ad2:: with SMTP id b18mr7139494pfd.232.1556841167086; Thu, 02 May 2019 16:52:47 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id o15sm397612pgb.85.2019.05.02.16.52.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 May 2019 16:52:46 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Nick Hilliard <nick@foobar.org>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, Sander Steffann <sander@steffann.nl>, 6man WG <ipv6@ietf.org>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org> <8b9fd743-bfcc-525c-98f6-154f3fa713cc@foobar.org> <CAO42Z2zEWvt9NyemMb8H0AEvPvmNSDGa4wcXiS6n5yRxNFCHQg@mail.gmail.com> <c7e18765-be04-6494-8193-984dbccb520b@foobar.org> <CANMZLAYh+V57yrWOzmUyjSMK0g95u1D5_GZmyZBMOMKAZnrnCg@mail.gmail.com> <3F474511-6FE3-4A0A-9B84-7C37F08FBB5D@steffann.nl> <E352C226-C708-4418-BCDE-10525CAB109A@jisc.ac.uk> <652fb10e-b8ce-0151-a9a0-62d2378caed2@gmail.com> <0079c716-d56c-7199-f493-f5e56e1307ae@foobar.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b33de303-eaca-f7f6-804e-2c9343eb92a1@gmail.com>
Date: Fri, 03 May 2019 11:52:43 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <0079c716-d56c-7199-f493-f5e56e1307ae@foobar.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/A2yyKNmPES_MRhFVAJRPTnQ6BU8>
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: Thu, 02 May 2019 23:52:56 -0000

Nick,
On 01-May-19 09:55, Nick Hilliard wrote:
> Brian E Carpenter wrote on 30/04/2019 21:48:
>> So I'd rather understand *why* the costs outweigh the benefits. One 
>> more thing for an operator to configure and check in each first-hop 
>> router, vs reduction of pointless traffic on updated hosts. I'm not 
>> sure how to make that an objective rather than a subjective 
>> trade-off.
> Hi Brian,
> 
> Email is being a serious barrier to communication in this discussion :-(
> 
> The problem statement just isn't there:
> 
> https://mailarchive.ietf.org/arch/msg/ipv6/GCGYTXhg0V9mQBrcO7zhC5wtnp0
> 
> The contents of this email largely still apply to the current text in -05.

It's a judgment call. IMHO the problem statement is adequate. In your opinion, it isn't.

> The cost is too high:
> 
> https://mailarchive.ietf.org/arch/msg/ipv6/NIJ194PI8CLkuZT8U_jKEOY01QI
> 
> You've shown no analysis of realistic use cases.
> 
> For something standards track, and this far down the protocol stack and 
> with such a large security considerations section, the proposal ought to 
> be thoroughly compelling for a wide variety of deployment scenarios, but 
> it isn't.  There are better ways of skinning this cat.

Again, a judgment call. We do refer to Layer 2 solutions and this is clearly positioned as a complementary approach.
 
The authors aren't going to make the final judgment call, obviously.

   Brian