Re: IPv6 web server

Christian Huitema <huitema@huitema.net> Mon, 14 May 2018 18:19 UTC

Return-Path: <huitema@huitema.net>
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 48E2F127337 for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 11:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RhdZZisoEpKG for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 11:19:51 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 502281200B9 for <ietf@ietf.org>; Mon, 14 May 2018 11:19:51 -0700 (PDT)
Received: from xsmtp31.mail2web.com ([168.144.250.234] helo=xsmtp11.mail2web.com) by mx60.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fII4Z-00076I-MU for ietf@ietf.org; Mon, 14 May 2018 20:19:49 +0200
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp11.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fII4W-0000LG-CR for ietf@ietf.org; Mon, 14 May 2018 14:19:44 -0400
Received: (qmail 26558 invoked from network); 14 May 2018 18:19:41 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <alexandre.petrescu@gmail.com>; 14 May 2018 18:19:41 -0000
To: ietf@ietf.org, Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <fcee1ad8-255c-5619-1945-bab24c95ca89@gmail.com> <6c352737-991e-c4c2-a104-e7ebfe548009@forfun.net> <4E469EA123CE8A23BCF57C77@PSB> <2bac0d07-df38-edd6-0c06-feeae07f4b7d@cambridgegreys.com> <183a8ccb-c950-4b67-887f-9a0e5372818b@gmail.com> <0B11E010-F9AF-458C-B71E-A294FE167FD5@huitema.net> <5a35455f-e53f-222d-c891-8ff38f584f58@gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <1f6ed856-47a5-24ae-cb19-8687999938c0@huitema.net>
Date: Mon, 14 May 2018 11:19:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5a35455f-e53f-222d-c891-8ff38f584f58@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: IPv6 web server
X-Originating-IP: 168.144.250.234
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.18)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5mwDGDH6iNCLfX+avh+PdcF602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO4tDwdNAVmgs/7KSsJM2vK1s1ujulqUFmMITHM77eiViZHtiOu2zXYEmoefjyvzNWM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB6b6XZpNC1wnpsGpZepb/px/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpX8nIu6prlMU9qLY4Lxa6TD8gXbdCfNGSi/39T/7fACgATy0gqc6hrH gwIgYjkNktqO98fck6astPPFccqiLCixm7xl+RQ3vIZqfBpLwZArl3I1g+tBSv0B+cgW7VoPEiDI +8QkA7WZKXURE/tHtZ/u0KOJrIKT6Yz+kw/sINDgmVhNqyux1yaQvYroLJ1yFFpxmsjqSkuAgJFn o3IMnh0xQZs4iXA/pTuddAL2KCGOjKaoYeoLX/yEBEWAApw66Tq3t9PKqfIkYUDuwnGn3d4uZhUF HKbUZMv7c3cOU/0VErE2BJ6+Ocmt1JPBpwCeIwTbMcctPzMPLiqwr8e+aie3zxvdN0leIxaNIjs7 cbPZdZnckpWaLvahyBjmQxBKOztcoEJy5JI/WnEUTEvEJGtKRioNM4YdAO5dQww9T9HjAWtJl6pO HngTL5HKgxzCo5M=
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dqjs7lWozuZhY6n3RFfe25Ch1Wc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 14 May 2018 18:19:53 -0000

On 5/14/2018 11:02 AM, Alexandre Petrescu wrote:

>
>
> Le 14/05/2018 à 16:34, Christian Huitema a écrit :
>>
>>> On May 14, 2018, at 7:08 AM, Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com> wrote:
>>>
>>>
>>> An IPv6 Draft on an IPv6 server is no more of a rant than a claim
>>> of IPv6 full access on an IPv6 access network.
>>
>> Nobody prevents you from placing a copy of an internet draft on an
>> IPv6 only server. But by definition a document only becomes an
>> internet draft if it is published in the internet draft repository.
>> Part of the process is that it becomes widely available, and the
>> authors do not control the publication process.
>
> I want to control the publication process of what I write, in some cases.
>
> In most cases I am very happy with the publication process of IETF.

The publication process of the IETF is part of the standardization
process. By participating in the process and submitting drafts, you give
up control of the publication process.

>
>> You can absolutely publish notes on an IPv6 only site -- the IPv6
>> turtle was a well known example. But those documents are not internet
>> drafts.
>
> Is an "Internet Note" a qualified naming at IETF?    I think I heard
> "Internet Engineering Note" or something like that.  Maybe that is
> what you meant...

No. I meant that this becomes a document of your choosing, such as for
example a technical report published by some organization. Just not the
IETF.

-- Christian Huitema