Re: Apology

Bob Hinden <bob.hinden@gmail.com> Tue, 26 February 2019 21:40 UTC

Return-Path: <bob.hinden@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 BED74130E6D for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 13:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 1fRVQYORF4I8 for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 13:40:12 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 633E312D7F8 for <ipv6@ietf.org>; Tue, 26 Feb 2019 13:40:12 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id m1so3883197wml.2 for <ipv6@ietf.org>; Tue, 26 Feb 2019 13:40:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+asZps9RRKoIe7WPv6EKbSbqlrGQb8XrV+d/frnqjmE=; b=bUpOpPCSr0cJTuCvam2xy8riDmO3kfYvetOqYoKQwpZ0PoA072YA9ADRsJZ6/cTe9t MBXRxuUmreqlVLoRe7/W20qHWPfw/l/BZif8KNtjWMLgR6cyDt22VldLDD9u9tIqgPhn Yhs3AnHP/1dVmB2IF+FLPeL9bCrCtgxJY4MB72hIMu8zxlmrxMxBn1knC6QdMy0r5Uza dx/FDVIpm5i8j9mnA/qD/JEhOjgbgKew3qVi69AVNDRafNOIwd4tgD+Wq5T7JfP6M8Gj lGBu6SDlityNgGiGm0buef9JW28XMBOc6tiugvUiTeizPWmU5cefWtGp9J/0Bi9AidRz QdPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+asZps9RRKoIe7WPv6EKbSbqlrGQb8XrV+d/frnqjmE=; b=Ld1yUkonmJWhPxJH7k0FPT2qsJwk5P/sFb6s2r693HmDLT9htBro5bG1OJmMx6u3hb yzF5o2oYBjaokA08iCJNKtM1vDeri50J9emt6yopJATRvxmLH3TwQ9vTztLhnGLCYR6/ 12VDZfDiNwDmesNmySWJtQb6H5KvPMQV/TSaitAMYZRWH73SqXwQ5znMKFO5wOh+Ij7G 3Al1C1AurhHiKJqJDBYUN01AyRmt92wgwB0jl7xURoMkGoBTB6ddo2Lzib+WzWBdsQYL 0jxB5wZ+geZBL1Hg9WjX6+r8fxePIco+kyq7i1trLWuFlWPo7aqQm3RDwjHCX4Ks1QCV eVPA==
X-Gm-Message-State: AHQUAuZy1DKr6mIGW57C0Vsw7rFcjc8+kjiw4s0tH5qzj3J3RYNLvTzm 6rdA4k8ZUH9hJKv/nw3L0vk=
X-Google-Smtp-Source: AHgI3IadHJf0s8u3FYJoefCG9yplKRfKcA1W3LHhQ/O7ldhZ1OIzV4aMG0llt5+uuKzMGs5uQ7/meg==
X-Received: by 2002:a7b:c348:: with SMTP id l8mr97745wmj.135.1551217210666; Tue, 26 Feb 2019 13:40:10 -0800 (PST)
Received: from [172.25.3.212] (rrcs-67-52-140-5.west.biz.rr.com. [67.52.140.5]) by smtp.gmail.com with ESMTPSA id z129sm398167wmc.33.2019.02.26.13.40.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 13:40:09 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Apology
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <e4a13615-421c-8d1e-77bf-ea9adfe3175f@go6.si>
Date: Tue, 26 Feb 2019 13:40:06 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D84AE07-B2DB-4597-8211-43B88EEC166B@gmail.com>
References: <7d6009ff-bb1a-df18-99c6-6ba1dbbdccfe@asgard.org> <3C1D9767-548D-4BA2-A5E4-3EF57738C4DD@employees.org> <b2d536f5-c299-3a73-bf46-ce11ed373186@go6.si> <649d1dde-ecbc-c346-b514-85c6b5858821@si6networks.com> <e4a13615-421c-8d1e-77bf-ea9adfe3175f@go6.si>
To: Jan Zorz <jan@go6.si>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vJShLhDVDKuGM4EomzGDexNL29g>
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, 26 Feb 2019 21:40:15 -0000

Might start with looking at the working group charter:

https://datatracker.ietf.org/wg/6man/about/

Bob



> On Feb 26, 2019, at 10:57 AM, Jan Zorz - Go6 <jan@go6.si> wrote:
> 
> On 26/02/2019 17:00, Fernando Gont wrote:
>> On 26/2/19 12:35, Jan Zorz - Go6 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?
>> Normally maintenance has to do with addressing problems/flaws found in
>> the specs and/or operationally. -- which is essentially what we are
>> doing here.
>> As a datapoint, e.g., tcpm, for one of the most widely-deployed
>> protocols (almost 40 years old) there has been a fair share of work,
>> ranging from generation and processing of sequence numbers and ack
>> numbers (e.g. RFC6528 and RFC5961), definitions of new options,
>> deprecation of features (e.g. URG indications), changing the initial
>> window, changing RTO values, etc.
>> Not sure what the debate wuld be about with respect to what
>> "maintenance" is about.
> 
> Well, my response was aimed at Ole's "Perhaps it is time to have a wider debate about how the working group should function and what it’s role should be."
> 
> Maybe the first thing to figure out is what version of meaning of "maintenance" we would like to use and that could set a nice path forward for a discussion that Ole proposed.
> 
> Cheers, Jan
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------