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

Mark Smith <markzzzsmith@gmail.com> Fri, 24 May 2019 05:43 UTC

Return-Path: <markzzzsmith@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 78B861200B4 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2019 22:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 s2h_X509fvsU for <ipv6@ietfa.amsl.com>; Thu, 23 May 2019 22:43:17 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 356D112004E for <ipv6@ietf.org>; Thu, 23 May 2019 22:43:17 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id g18so7600190otj.11 for <ipv6@ietf.org>; Thu, 23 May 2019 22:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=E3+23Z0f36ZZwNORNBAraNEiLwgb5TKBxK5D7o30PsU=; b=eUkBbOtNY1K5GFTwD3MrjH6R9rKN3z+8QTSkUu/zmjp9pH8m4FQKDKc0rn+RCSKgO6 7XByawjlVXETKm8QnDaZHOe3N0bbiJCPPb5n4ubmbPLFBK+j2vAF1QkY27QG6goIfzaP 9Vik9dLyzKRaulxJjsgL64UQavFGrF4yjOaa64rNflVxw6vRipHwWjzXbOMbI4ecA8RL vQVo9lHcIJRsrp2MUNMMyNPonKSg4d0ezpqNEIzHICb8sd+J5qMKTbjMFnUP1WTx74+i jauq7cPf3nGKgOcv5R8b25t5QCArYYOdaEab8C+rs9gCGs6s6bUhzLTvVWVmvd5DVRNh 1HCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=E3+23Z0f36ZZwNORNBAraNEiLwgb5TKBxK5D7o30PsU=; b=D47ssIxj4e50kk51CuLVBMJjwqKY6Wx5zL9lH+KXmU2zSgjbRHu5MNGfiQJx1GV/z3 71U/ooGFy00/HdQ7E/s5YEQKRNrNwS9bTDB+N1KN8yaaQk8zc+MmnzT41U33kspCyJCy +MAR4PsVBLLgrjcOgmkc/4PDTlLOkxLzvjsYDHx6BDmghEmZmXaYxbNSJOCv/RPrkA5N Vdkhd7vJJeyeqDT1k5mjz8DECmfOUbgetLZpFVh82LLNEEzPNJadUpMj6TVhJarc1e/p subIXeiQmV3BxOYLaxW18M6O4Z6ykH2gJP+4kAdjF7AuHN/YIcLnsKuuUpK04us4LABK sNAw==
X-Gm-Message-State: APjAAAW0dtJS1uX85+B73aqJBoiiwbjFJIxj1VKQDplX7C7qgB9tlmGR CQ9C5/kWnF8jr70iMbnKFGvxZURojSMEC1kgCdCBWA==
X-Google-Smtp-Source: APXvYqyjKIxO17WwHekpifnAGceCxo8ZPFSNzwxEFB8pTvMJVvytJAnyBUSkZt0HOTRfm/+Kg0Oo+cYmuwwpy9jJk+s=
X-Received: by 2002:a9d:58c5:: with SMTP id s5mr31284187oth.153.1558676596250; Thu, 23 May 2019 22:43:16 -0700 (PDT)
MIME-Version: 1.0
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <22774.1556560887@localhost> <m1hLB3s-0000ItC@stereo.hq.phicoh.net> <CAO42Z2y0L7pJqKxmLsQCmm393h29auMzBRvFPGC+Qg_G-vO45w@mail.gmail.com> <F3885D53-45A0-4331-9056-F877C1BB3AE5@steffann.nl>
In-Reply-To: <F3885D53-45A0-4331-9056-F877C1BB3AE5@steffann.nl>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 24 May 2019 15:42:48 +1000
Message-ID: <CAO42Z2zOGf6hSpUE9FJtbOCV0MsDJfhfL1XzakBrmj0Kg40aRA@mail.gmail.com>
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Sander Steffann <sander@steffann.nl>
Cc: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xglUptjr7KjRtgYEPSlM6eSFgJ4>
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: Fri, 24 May 2019 05:43:19 -0000

Hi Sander,

Sorry not to get back to you sooner.

On Wed, 1 May 2019 at 00:33, Sander Steffann <sander@steffann.nl> wrote:
>
> Hi Mark,
>
> >> Here is the opinion of operators at the RIPE meeting last fall:
> >> https://ripe77.ripe.net/archives/video/2335/
> >> Reactions at 5:38
> >
> > How many have read the draft?
> >
> > Should they be making judgement and we accept judgement based on a short and single presentation by somebody who has a bias against it?
>
> I gave that presentation after discussing it with Ole to provide some sort of feedback on this draft from the operator community. I presented both the benefits and the dangers. Yes, I am personally against this draft, but I gave an honest representation of both sides.
>

I think the one thing missing from the presentation was a statement of
what sorts of numbers of hosts likely attached to a link where
link-layer broadcast volume may become a consideration or concern.
That would have better set the context for the problem trying to be
solved.


> I haven't seen any active outreach from the IETF, and the operators who do speak up here are often ignored as "single voices" that don't represent the operators, and when someone goes out and tries to get broader feedback its biased. All of this makes it very difficult for operators to deal with the IETF, and I know many who have given up.
>

So I was indirectly hoping to encourage more operators to participate
with this presentation at the 2015 AusNOG conference.

"Why you should read RFCs and Internet Drafts (and what you need to
know to do so)"
http://www.ausnog.net/sites/default/files/ausnog-2015/presentations/1.4_Mark_Smith_AusNOG2015.pdf


I wonder what an operator who tries to participate in the IETF expects?


Regards,
Mark.




> If you have a better way of getting a feel for operator support I am all ears.
>
> Cheers,
> Sander
>