IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 May 2019 23:17 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 379F41200EB for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 16:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 m78OKhPIeWF4 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 16:17:56 -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 3839F1200DE for <ipv6@ietf.org>; Thu, 9 May 2019 16:17:56 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id y11so2089913pfm.13 for <ipv6@ietf.org>; Thu, 09 May 2019 16:17:56 -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=vPd85aCp1jSV5kHhVeWUroStavcRyccrjfebDZ9rquA=; b=roZ+LUSa4R7e2r2viyHT2mV94BUgCjyUYHkHnGQYvtmkh55pYbnf1tx4Rh/b4bOfvs FY2mU8iGLvaf2qUeTc2dq6eQNKcxyVI6cL4xjxkayMfHy3oCYewW5G/4IH2EdQa7Jgfr q5hzhwUyRSzQ7rI9SHjncHNvygPXWslwRaz/1L/fHbwOh2gm9JPGiziRGB6pxKjHuUqG iTDlQ+6bwFdbYmPHMUla9arpkL/nR0spHBF/dqX08cXo6sS4SYl6UKRpsTfPHByJ+Onp vZQrd8MajweDS9qq5CnNq99FwMqBN9az+huq1irn98GjryJOBKOpVPlpa6yzUGbSRveB ME4A==
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=vPd85aCp1jSV5kHhVeWUroStavcRyccrjfebDZ9rquA=; b=QlSef/MOUqeHn1lYozNks4GSlEus1uOxLPVQWqny9fNQkiHlwVefU3EW9cEOKdUYVO dcdWOHwzQMciZweFTtQh/WV31xyrnczdQPbyAXjjz0mVA7nguHI96Q1c65QoK9Ol0oNJ icUiCiru102YF5uOY+eoPHpPRaRpiz8C5QoHLJ5bjYtjHq87pJLrz0W/rjT2WsfBzja5 cqKxvDm7/459tJn/QCiOkVQOzduyxmX2nWF5eM10qAlWj82pxk709ot7GfKRnl8XW8+k OtB3R2LeUm5AG6+UfLvdA9OGbBa/sqWT6PngDCVsPU+TJnyUQFCEN+nyQw1R6Wy2gIqr IsiA==
X-Gm-Message-State: APjAAAWz97KsjlvIL3nkbPkce+XwTx+tXZK61P5PtuZFTbAWpgbgL/8K e3Q9nimLQTWknu0+q3jMseD3ZO2I
X-Google-Smtp-Source: APXvYqykYrcUvmlLkAv6JXJlm8CP8YpFDCZimYsSY/11ISSrsDQRX5cMh9o4+w4B3zkUPrjE7WFM6Q==
X-Received: by 2002:aa7:8392:: with SMTP id u18mr9424972pfm.217.1557443874794; Thu, 09 May 2019 16:17:54 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id l1sm4223015pgp.9.2019.05.09.16.17.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 May 2019 16:17:53 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: j h woodyatt <jhw@conjury.org>, IPv6 List <ipv6@ietf.org>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.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> <b33de303-eaca-f7f6-804e-2c9343eb92a1@gmail.com> <6C4ABEF1-2565-4BA9-9FC5-5B3C45A719AD@gmail.com> <c2222416-6491-1906-a403-d012777a4b38@gmail.com> <CABNhwV0-SdKZqQa4z9jhpc8h1Eq=8UxRhtvHt1==BYEMTVRjug@mail.gmail.com> <96790121-7D50-4C6F-924F-87065B989E44@gmail.com> <ccab3694-54f2-bdd1-f8ac-cb159dbc0a81@gont.com.ar> <CAN-Dau0_w0n9C6grqi1bXAL-k239K7RMiQyhx5=c-Y_wqrV2OQ@mail.gmail.com> <CAO42Z2wwftO6wtF7PAJ9CCK2iBvtOj0BQP7O0UREr-pMmPegvQ@mail.gmail.com> <A116C7B4-9ED0-4268-9086-5768CB53898D@conjury.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e77514fa-cb76-88a8-894e-764b374f363d@gmail.com>
Date: Fri, 10 May 2019 11:17:51 +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: <A116C7B4-9ED0-4268-9086-5768CB53898D@conjury.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8uvvvPZXBYQBS5x586D6t-3jcZ4>
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, 09 May 2019 23:17:57 -0000

On 10-May-19 05:14, j h woodyatt wrote:
> On May 8, 2019, at 23:09, Mark Smith <markzzzsmith@gmail.com <mailto:markzzzsmith@gmail.com>> wrote:
>>
>> The primary goal is to reduce and ideally entirely eliminate link-layer broadcasts on the link caused by IPv4.
> 
> I don’t think 6MAN can work on that goal. I’m looking at the active charter, and I’m just not seeing where it says it can have that as a goal for its work. There is a clause about addressing "protocol limitations/issues discovered during deployment and operation” but I think it’s a big stretch to tag this goal with that topic. This isn’t a limitation or issue with the IPv6 protocol.

The charter is naturally silent on this issue. However, the WG adopted the draft, presumably under "The working group will address protocol limitations/issues discovered during deployment and operation." (Explicitly: discovered on an IPv6-only network several IETFs ago, if you want chapter and verse. The limitation being the absence of a mechanism to signal "IPv6-only" to dual stack hosts.)

    Brian

v2.23.0 | Report a Bug | By Email