Re: Functioning of 6man (was: Re: Apology)

Lorenzo Colitti <lorenzo@google.com> Wed, 27 February 2019 13:36 UTC

Return-Path: <lorenzo@google.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 ED55E130EC5 for <ipv6@ietfa.amsl.com>; Wed, 27 Feb 2019 05:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 ss8n5x0gQk9g for <ipv6@ietfa.amsl.com>; Wed, 27 Feb 2019 05:36:52 -0800 (PST)
Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 DCC52127287 for <ipv6@ietf.org>; Wed, 27 Feb 2019 05:36:51 -0800 (PST)
Received: by mail-it1-x134.google.com with SMTP id g17so1132975ita.2 for <ipv6@ietf.org>; Wed, 27 Feb 2019 05:36:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lu8eEU4NQvjfQTPLsVickIjTTfu7gibw6laLR28o+as=; b=eCIMoFB95Ghw4o3BQuXFRnmoscgh7V1hc/czmT90yMuuylsaG9higkVCajoZ/xOzzR cWkHhbSbDHtBBcvQF2QyxE9sWH6Hhn7mkkI01VvcmjFZOYplbhO2x+xHEcMAIVaXssI/ ADap3nszKr2AC7CaqxHBg+/ycZCcUphmFsyr5/gd16tgqFJmU15HpkSGXm8pRgc5pnUj N72Mw/3CiBWaucuXm08ObMOXqBJd5G4+gfp23cjpPfj2n91thYJK9ErSnokxkp38kG7l PWLSP7am7MQbrOtbPMSLs+JwyTLbEZi09Eh4d3a4uLP7jHJpSr6sPUI5RWFIo/op6gc7 vMjQ==
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; bh=lu8eEU4NQvjfQTPLsVickIjTTfu7gibw6laLR28o+as=; b=Fz+njMWDZJtJypcc3HAjJsAE0OryKmhpf4n79YQoP4MoTiHPBQzNXMVeLQoMKdwQct CKng85MFeOWHt2TkawOk1ijZXY3lRdI3HnzhI1pwJrulUxk5CBbtJ8D6WtdCBZIsWp3x 3WVTyKhGKhsVn7ywUqbfx61r9GFFqIfaEVMuDc93A8rGJG2ucQDdr2aFE84z3mM6V/DN 6RwZGQjLoLUv2O0fAkOUDJryRuhhGnQovTnEK+cUjKoUTo2+Y2lwZCj7YVn2DuHabRFn 96UzlT4mylVEdJGQr51+5jOz20HNwFIZwN/oM2DRTGQAqUKeRzaUjw3TcFgrCcdndF1x 0UHA==
X-Gm-Message-State: AHQUAuaW/hTd9cX/sQ8mZTqWJ+eUEVXKhV+drsLeTM8PG3bdr/bWNCDJ stfp0rFaOxCKovWY83uqqIDRxNpj++kpmgLe9ZTeGQ==
X-Google-Smtp-Source: AHgI3IbRzoBpvaeDhnWfdzxyRCsTmvA3BSrGtlopvsRn8aKasyjbeE+IS1+ymQ3ESBz1HluncCj+d2AUAnB3MD6X6gQ=
X-Received: by 2002:a02:10c9:: with SMTP id 192mr1163993jay.51.1551274610472; Wed, 27 Feb 2019 05:36:50 -0800 (PST)
MIME-Version: 1.0
References: <7d6009ff-bb1a-df18-99c6-6ba1dbbdccfe@asgard.org> <3C1D9767-548D-4BA2-A5E4-3EF57738C4DD@employees.org> <b2d536f5-c299-3a73-bf46-ce11ed373186@go6.si> <E7CF8C39-DA64-4A09-9FEC-BA0EFAD6C454@employees.org>
In-Reply-To: <E7CF8C39-DA64-4A09-9FEC-BA0EFAD6C454@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 27 Feb 2019 22:36:38 +0900
Message-ID: <CAKD1Yr1DBatZ3j3-+x0pLp5Q18cs3Yr1ot-ju1m842bHufU80Q@mail.gmail.com>
Subject: Re: Functioning of 6man (was: Re: Apology)
To: Ole Troan <otroan@employees.org>
Cc: Jan Zorz - Go6 <jan@go6.si>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001bc8d00582e0443a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Xn7IJG-2dNEvK2hSVCvb40POkns>
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: Wed, 27 Feb 2019 13:36:55 -0000

I agree that "making sure that IPv6 protocol doesn't change" is not the
goal. But there is some of that. I do think that one important role of 6man
is to preserve the IPv6 design from change requests by operators that do
not have enough (or, in some cases, any) real-world experience with
deploying it. If we don't do that, we'll end up with a copy of IPv4, just
because it's what everybody knows.

On Wed, Feb 27, 2019 at 9:35 PM Ole Troan <otroan@employees.org> wrote:

> Renaming this thread.
>
> And just as a note, I think more than me find references to “real world
> requirements” a little taxing.
> It insinuates that some people live in the real world, and understand
> what’s going on there, and some others aren’t.
> While reality is probably more along the lines of lots of paralell
> universes with somewhat conflicting requirements… ;-)
>
> Cheers,
> Ole
>
> > On 26 Feb 2019, at 16:35, Jan Zorz - Go6 <jan@go6.si> wrote:
> >
> > Dear @all,
> >
> > On 25/02/2019 09:37, Ole Troan wrote:> 6man is a long lived working
> group, tasked with maintaining the IPv6
> >> specifications. That’s different from the typical IETF working group.
> >> Perhaps it is time to have a wider debate about how the working group
> >> should function and what it’s role should be.
> >
> > This is an important discussion to have. Can we define first what
> exactly "maintaining the IPv6 specifications" mean?
> >
> > Is this about being a guardian making sure that IPv6 protocol doesn't
> change? IPv6 was defined many many years ago and meanwhile the reality of
> networking architectures and deployments changed a lot...
> >
> > In my mind, protocol development should go in circles...
> >
> > Protocol development and standardization (IETF) -> Vendors
> implementation in HW/SW -> Operators deployment in networks -> Feedback
> from real world back to IETF from operators (through vendors or direct) ->
> IETF adjusts protocol to real world requirements -> Vendors -> etc...
> >
> > Where did things go wrong? Why? Did they go wrong in first place? ;)
> >
> > Cheers, Jan
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>