Re: Usage of services without IPv6 Support

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 22 April 2020 15:32 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92DF3A0971 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 08:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 DDsBDgUPt2sY for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 08:32:16 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 CF74B3A08E5 for <ietf@ietf.org>; Wed, 22 Apr 2020 08:32:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 496kvM6f1Xz6GGlB; Wed, 22 Apr 2020 08:32:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1587569535; bh=a6aHIz85s3kILzs0xdVMgRgIu4wTp72GdAmqswxtxXY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=OelluLk8RKSlMRRTsezTxiLpt/qXFca/An0braRadUJoPOj0IogoxN8h6Q+Tr2DQY BYbf91/mHoT97AHisbd/ZzEOYMDMYlcmQN9YuUJNMTryEPY6jIqS5fRBCLtHqfE+K4 DIefKByCsLLneShSJZhJAmxRRRpgwFkVHzVC3lp0=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 496kvM2cBdz6GGjR; Wed, 22 Apr 2020 08:32:14 -0700 (PDT)
Subject: Re: Usage of services without IPv6 Support
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
References: <ba1450e1-4288-7682-3e15-f36909f6a1fa@gmail.com> <6.2.5.6.2.20200421004335.0c471478@elandnews.com> <1c4a6ad2-fc65-207a-6a89-558f6b86b0a1@gmail.com> <20200422013643.GU27494@kduck.mit.edu> <778c9b47-ee07-9f5b-de1d-da9d2c5be476@meetinghouse.net> <839aed3a-edf6-2c62-2ac0-47a83b951ca9@network-heretics.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <28350b6e-ba50-c000-7839-d64e3d06f0f5@joelhalpern.com>
Date: Wed, 22 Apr 2020 11:32:02 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <839aed3a-edf6-2c62-2ac0-47a83b951ca9@network-heretics.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/ietf/KltHiyveddgaHH4uOfdF51M4Bi4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 15:32:18 -0000

Let's take this apart.

We can't and won't stop individuals from developing drafts using github.
    Nor can we stop them from posting pointers to those githubs on WG 
email lists.
Similarly, we can't and won't stop design teams from using github.

Given the above, I am glad we have documents describing the best 
practices for using those.
Also given the above, insisting that if a WG formally wants to use a 
repository, they MUST use something different seems really odd.  While I 
personally would prefer not to use github at all, I think the current 
path is the right one for the community.
And more importantly, it is the one the community adopted.
And adopted knowing the constraints.

Yours,
Joel

On 4/22/2020 11:24 AM, Keith Moore wrote:
> On 4/22/20 11:02 AM, Miles Fidelman wrote:
> 
>> Last time I looked, Internet standards were VOLUNTARY standards.
> 
> Yes, but we're talking about the tools that /we/ choose (i.e. volunteer) 
> to use.   Nobody's proposing that github be forced to implement IPv6, 
> the question is only whether IETF should continue to use it if we can't 
> somehow make it accessible via IPv6.
> 
>