Re: Apology

Jan Zorz - Go6 <jan@go6.si> Tue, 26 February 2019 18:57 UTC

Return-Path: <jan@go6.si>
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 3BC30129B88 for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 10:57:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=go6.si
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 QzvJ0M2jWDYR for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 10:57:20 -0800 (PST)
Received: from mx.go6lab.si (mx.go6lab.si [IPv6:2001:67c:27e4::23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62EFE130EE6 for <ipv6@ietf.org>; Tue, 26 Feb 2019 10:57:20 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.go6lab.si (Postfix) with ESMTP id 861A96601A; Tue, 26 Feb 2019 19:57:17 +0100 (CET)
X-Virus-Scanned: amavisd-new at go6.si
Received: from mx.go6lab.si ([IPv6:::1]) by localhost (mx.go6lab.si [IPv6:::1]) (amavisd-new, port 10024) with LMTP id dND_6am5DjAx; Tue, 26 Feb 2019 19:57:16 +0100 (CET)
Received: from mail.go6.si (mail.go6.si [IPv6:2001:67c:27e4::61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.go6.si", Issuer "Let's Encrypt Authority X3" (not verified)) by mx.go6lab.si (Postfix) with ESMTPS id 21EAD65FE3; Tue, 26 Feb 2019 19:57:16 +0100 (CET)
Received: from haktar.local (unknown [IPv6:2001:67c:27e4:102:1d8c:fe88:2f88:b29d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Jan Zorz", Issuer "COMODO RSA Client Authentication and Secure Email CA" (not verified)) (Authenticated sender: jan) by mail.go6.si (Postfix) with ESMTPSA id DDF54803B3; Tue, 26 Feb 2019 19:57:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=go6.si; s=mail; t=1551207435; bh=uVOX5XnVyLhppl+NL7lXtM9qu5knPQOb0BA3e5DoPg4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=WEqa7UkzVyMT2w9w3M5JC97DO0zhXe7J0lHe8bypCUzsWAHnuwqzBYuCF/xxgLWL+ 18N3cI1Sjdfa5NuJltFeQWNncmF9YHS9TkJMcY36LBvc7ts9ztL/w020CM/A9xzNj+ 9bITR0Dwm/k9+c6oc02u0Ma2+jqE8INl7ykzG414=
Subject: Re: Apology
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
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>
From: Jan Zorz - Go6 <jan@go6.si>
Message-ID: <e4a13615-421c-8d1e-77bf-ea9adfe3175f@go6.si>
Date: Tue, 26 Feb 2019 19:57:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <649d1dde-ecbc-c346-b514-85c6b5858821@si6networks.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/q0hAdPjFSAFoxpcz7fNBPUR4g-o>
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 18:57:30 -0000

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