IETF Logo Mail Archive

Re: [hybi] Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.txt

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Sat, 11 November 2017 10:45 UTC

Return-Path: <hurtta@siilo.fmi.fi>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 277ED1294E8 for <hybi@ietfa.amsl.com>; Sat, 11 Nov 2017 02:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=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 GIM0De4BO2lK for <hybi@ietfa.amsl.com>; Sat, 11 Nov 2017 02:45:24 -0800 (PST)
Received: from smtpVgate.fmi.fi (smtpvgate.fmi.fi [193.166.223.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B81301294E6 for <hybi@ietf.org>; Sat, 11 Nov 2017 02:45:23 -0800 (PST)
Received: from basaari.fmi.fi (basaari.fmi.fi [193.166.211.14]) (envelope-from hurtta@siilo.fmi.fi) by smtpVgate.fmi.fi (8.13.8/8.13.8/smtpgate-20161014/smtpVgate) with ESMTP id vABAjDJC018118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 11 Nov 2017 12:45:13 +0200
Received: from shell.siilo.fmi.fi by basaari.fmi.fi with ESMTP id vABAjDg6003143 ; Sat, 11 Nov 2017 12:45:13 +0200
Received: from shell.siilo.fmi.fi ([127.0.0.1]) by shell.siilo.fmi.fi with ESMTP id vABAjDcp027389 ; Sat, 11 Nov 2017 12:45:13 +0200
Received: by shell.siilo.fmi.fi id vABAjCvK027388; Sat, 11 Nov 2017 12:45:12 +0200
Message-Id: <201711111045.vABAjCvK027388@shell.siilo.fmi.fi>
In-Reply-To: <CANatvzz8YP0fDBfxSzFsRCG+q7XGpmRqsb5yy5DvHDzLdi4RAw@mail.gmail.com>
References: <CAD3-0rPPGx4k+ksk-QDnNhnescfPHiYSJ-z2AQeMR2=khaO_HQ@mail.gmail.com> <20171110061456.1349EB532F@welho-filter2.welho.com> <CANatvzya831tQdWsjpiwdF537jVqZYCQpi3aFHLdQoGjShcCRw@mail.gmail.com> <CAH9hSJapY-KxFwMzGp4vmNcZuu5R8gJ+es4Rs1Le8G2CWPLjsQ@mail.gmail.com> <201711101751.vAAHpqHC031731@shell.siilo.fmi.fi> <CAH9hSJZGN-VLLGFs46HHZSV+sWbAeh+sNC2sck-OQbi1GGK+ZQ@mail.gmail.com> <CANatvzz8YP0fDBfxSzFsRCG+q7XGpmRqsb5yy5DvHDzLdi4RAw@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
Date: Sat, 11 Nov 2017 12:45:12 +0200
Sender: hurtta@siilo.fmi.fi
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Takeshi Yoshino <tyoshino@google.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, hybi <hybi@ietf.org>, Patrick McManus <pmcmanus@mozilla.com>, HTTP Working Group <ietf-http-wg@w3.org>
X-Mailer: ELM [version ME+ 2.5 PLalpha46]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Filter: smtpVgate.fmi.fi: 3 received headers rewritten with id 20171111/38395/01
X-Filter: smtpVgate.fmi.fi: ID 38397/01, 1 parts scanned for known viruses
X-Filter: basaari.fmi.fi: ID 162806/01, 1 parts scanned for known viruses
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (smtpVgate.fmi.fi [193.166.223.36]); Sat, 11 Nov 2017 12:45:14 +0200 (EET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/GR8IPeGLBYiOZRmg3kKzSAjkx8o>
Subject: Re: [hybi] Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Nov 2017 10:45:26 -0000

Kazuho Oku <kazuhooku@gmail.com>: (Sat Nov 11 09:46:58 2017)
<...>
> > We could design error code, fallback, etc. for this kind of cases if it
> > turns out we really need to take care of. For the initial implementation,
> > maybe we could just let browsers give up when a connection attempt fails on
> > a connection with ENABLE_UPGRADE (or ENABLE_CONNECT_PROTOCOL) announced.
> 
> I agree.
> 
> While I agree that having a status code that indicates failure to
> upgrade the connection "end-to-end" might be a nice idea, I would also
> argue that the necessity is not specific to HTTP/2.
> 
> We could have had a connection-cannot-be-upgraded status code for
> HTTP/1.1. But in reality, we do not have such a status code, and
> nobody has argue for having that (as I know of).

There is (sort of)

426 Upgrade Required


normally, if Upgrade can not done, http request is processed without protocol
change.  This status code allows refusing of processing.

426 Upgrade Required

is defined on

RFC 2817: Upgrading to TLS Within HTTP/1.1
https://tools.ietf.org/html/rfc2817


Yes, that status code is for somewhat different purpose.


> Considering the fact, I would anticipate that we will be fine without
> adding a new status code to indicate such failure.
> 
> -- 
> Kazuho Oku

/ Kari Hurtta

v2.23.0 | Report a Bug | By Email