Re: IPv6 web server

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 14 May 2018 18:32 UTC

Return-Path: <sarikaya2012@gmail.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 26A621275AB for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 11:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 GipqkeMhsvbc for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 11:32:47 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 8C8391273E2 for <ietf@ietf.org>; Mon, 14 May 2018 11:32:47 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id q72-v6so13444518itc.0 for <ietf@ietf.org>; Mon, 14 May 2018 11:32:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pkvcWSjVilR0GxnWXWyPKTYfYKFd9zonJ4VerJk6Nbg=; b=j9O/dA7fIZXBuV8YOpapNvaeOcJtmzKCQysHKnHoCu0m+73fzgJyboa93sXdE3koYe G/hzo70pO9M4Z6oZiKnSLnkwlp8zhC8KuNnu/AmzDNSPEMIyedjRjl9bTkVDXzWmSbpI mISYOk8ZlwfcCaCI73kES2EdO7eDHaCKabEu946F6PxZoSxHNR+1eg94r1dJpm2VRKAS ejoKqVbd0PHxtIjTLo4UiMeM7evGhamTUzya+Bcai2W72Prmyjz67IdzFuP5lV307inS JZkwQtig8nkEdKAq/bm9oRw1ZHSkhxSdxLjuGM0GFdF67MOGFjsmdNNcwoJ0uPdOz0uP VcUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=pkvcWSjVilR0GxnWXWyPKTYfYKFd9zonJ4VerJk6Nbg=; b=lwfF+LZ5NrCfd9rA02L+WhZ/7wEHLq9W+ec4zUe/yFggFWDlacZusfHYe9MVypHunu 79z1C09fBDSxAUMejq7lt8FX+B7jsICmLiAZvD+z9MZyV6ZA4sl34XD7iKANkyAlVraN 1CA5GrWilH4PbJMCc1ZXcwQJX7uMIEbWJHDi4jTEd+h6dt11Li5CI8WsTsLVo2culwp4 aFwuj5mQS96yrjFwGDOiHc77TqeB8VD0XulD0HWe2LwbmVkvYh9We2S9zTpVS+cVgTh7 En6tucbv5bTypHtQn5q6MbYid21F3wm0odQEjKDhJG1l3eox/k1CaDV4ZYQ4M9o11rym C4DA==
X-Gm-Message-State: ALKqPweing6ZGStWCMbZ3gxIGfFGCoa1rlEmUuG3rYKHg/IlKP3S3bV9 JekzX5JlCVT3XGpNtZ/z4WpwW5kt7ULMYgJ2dJ0=
X-Google-Smtp-Source: AB8JxZo6SguOrgBP1Q3iKzraZhRqxKq/o8K9C05GpCiSodmzBpLBD8IGSzI2eSFzNBMPCpG6fyAw2ZLmiqqMqx78xrc=
X-Received: by 2002:a24:d309:: with SMTP id n9-v6mr10212914itg.29.1526322766972; Mon, 14 May 2018 11:32:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.192.170.54 with HTTP; Mon, 14 May 2018 11:32:46 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <1f6ed856-47a5-24ae-cb19-8687999938c0@huitema.net>
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> <1f6ed856-47a5-24ae-cb19-8687999938c0@huitema.net>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 14 May 2018 13:32:46 -0500
Message-ID: <CAC8QAccn+r7bX0e1M6mZoDQK+RELSMhMH8Bas=io9ZhJdVV6MA@mail.gmail.com>
Subject: Re: IPv6 web server
To: Christian Huitema <huitema@huitema.net>
Cc: IETF <ietf@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000568c10056c2eb6f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7BXxTIoosi51YhHPchkf7e1p-hI>
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:32:49 -0000

Bonjour Christian,

On Mon, May 14, 2018 at 1:19 PM, Christian Huitema <huitema@huitema.net>
wrote:

> 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.
>
>
It is OK, Alex wanted it this way, we are going (I hope someone soon) post
a copy on the mailing then it is  going to become an I-D.

Behcet

> -- Christian Huitema
>
>