Re: [tae] [tsv-area] Transport negotiation

John Leslie <john@jlc.net> Mon, 08 December 2008 20:30 UTC

Return-Path: <tae-bounces@ietf.org>
X-Original-To: tae-archive@ietf.org
Delivered-To: ietfarch-tae-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B91633A680D; Mon, 8 Dec 2008 12:30:07 -0800 (PST)
X-Original-To: tae@core3.amsl.com
Delivered-To: tae@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99BD43A67D6; Mon, 8 Dec 2008 12:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.192
X-Spam-Level:
X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=0.407, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9tRLmyVfzS9; Mon, 8 Dec 2008 12:30:02 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id AAB673A680D; Mon, 8 Dec 2008 12:30:02 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id C7EE333C37; Mon, 8 Dec 2008 15:29:56 -0500 (EST)
Date: Mon, 8 Dec 2008 15:29:56 -0500
From: John Leslie <john@jlc.net>
To: Lloyd Wood <L.Wood@surrey.ac.uk>
Message-ID: <20081208202956.GF43294@verdi>
References: <3BB334D8-B00C-48C1-ACBF-4D09576DEADF@mpi-sws.org> <492C7F97.3030000@isi.edu> <EDCC4CF2-DC3C-409F-8F99-3BE51BAE4111@surrey.ac.uk> <492DE8AD.1090300@isi.edu> <7DA33930-1767-492B-807E-7A7DA661AFE9@apple.com> <EAB5CBF0-4C7A-44F1-BF57-641915CBE6AB@surrey.ac.uk> <493CB9D3.2080308@isi.edu> <4B36B0DC-54CC-4ADE-9688-074312E70E0D@surrey.ac.uk>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4B36B0DC-54CC-4ADE-9688-074312E70E0D@surrey.ac.uk>
User-Agent: Mutt/1.4.1i
Cc: tae@ietf.org, tsv-area@ietf.org
Subject: Re: [tae] [tsv-area] Transport negotiation
X-BeenThere: tae@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Architecture Evolution <tae.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tae>
List-Post: <mailto:tae@ietf.org>
List-Help: <mailto:tae-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tae-bounces@ietf.org
Errors-To: tae-bounces@ietf.org

Lloyd Wood <L.Wood@surrey.ac.uk> wrote:
> 
> Similarly, though http is expected to live over TCP, being able to  
> explicitly override it in the URI if desired has merit in some cases.  
> That is, 'http' would be the same as writing 'http-tcp'.

   Given that there's existing work for http over sctp, and that sometimes
ambiguity is intentional and can be a good thing, I'd recommend that
plain 'http' be allowed to continue whatever ambiguity it already has, and
that we create a different access-method name for http over tcp if we
intend to forbid any transport except TCP.

   And if we define any such thing, we should consider registering it
according to RFC 4395...

--
John Leslie <john@jlc.net>
_______________________________________________
tae mailing list
tae@ietf.org
https://www.ietf.org/mailman/listinfo/tae