Re: [hybi] [Uri-review] ws: and wss: schemes

Kristof Zelechovski <giecrilj@stegny.2a.pl> Sat, 12 September 2009 20:55 UTC

Return-Path: <giecrilj@stegny.2a.pl>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA1173A692F; Sat, 12 Sep 2009 13:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.758
X-Spam-Level: **
X-Spam-Status: No, score=2.758 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_40=-0.185, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95]
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 Q6umAz2egr5O; Sat, 12 Sep 2009 13:55:10 -0700 (PDT)
Received: from shark.2a.pl (shark.2a.pl [195.117.102.3]) by core3.amsl.com (Postfix) with ESMTP id DB2753A686B; Sat, 12 Sep 2009 13:55:09 -0700 (PDT)
Received: from av.2a.pl (av.2a.pl [195.117.102.9]) by shark.2a.pl (Postfix) with ESMTP id CA3352A6AD4; Sat, 12 Sep 2009 22:55:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at 2a.pl
Received: from shark.2a.pl ([195.117.102.3]) by av.2a.pl (av.2a.pl [195.117.102.9]) (amavisd-new, port 10024) with ESMTP id zLbUA9h5XMx1; Sat, 12 Sep 2009 22:55:43 +0200 (CEST)
Received: from POCZTOWIEC (unknown [10.8.1.26]) by shark.2a.pl (Postfix) with ESMTPA id EB86A2A6B05; Sat, 12 Sep 2009 22:55:06 +0200 (CEST)
From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
To: 'Lloyd Wood' <L.Wood@surrey.ac.uk>, 'Infinity Linden' <infinity@lindenlab.com>
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com><4AA2A630.32731.824DABF@dan.tobias.name><1252444455.16404.646.camel@dbooth-laptop><4AA70134.28006.1928A41F@dan.tobias.name><ca722a9e0909111212l29d378afn8a97dfee15247b2b@mail.gmail.com><3a880e2c0909111251sace699bp7a5deb24529abed@mail.gmail.com> <62264C3D-3351-4401-8E64-1539745B2D06@surrey.ac.uk>
Date: Sat, 12 Sep 2009 22:55:33 +0200
Message-ID: <5BEEDCAC837445B3A3FE89E67B45BB1E@POCZTOWIEC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
thread-index: Acoz6BKKl8MroEKTST2kUtbc+PPpEAAAZhnA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <62264C3D-3351-4401-8E64-1539745B2D06@surrey.ac.uk>
Cc: "'Daniel R. Tobias'" <dan@tobias.name>, uri-review@ietf.org, hybi@ietf.org, 'URI' <uri@w3.org>
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 12 Sep 2009 20:55:10 -0000

  1. DNS can use UDP.
  2. There is no need to do interplanetary name lookup each time; the local
resolver can have all desired hosts preconfigured.
  3. Even if this fails, you can have numeric addresses in an URI authority,
so it does not preclude using URI if only numeric addresses are feasible.
(BTW, domain names are for people; appliances do not need them at all unless
their host has an unstable IP number.)
IMHO,
Chris

-----Original Message-----
From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org] On
Behalf Of Lloyd Wood
Sent: Saturday, September 12, 2009 12:01 AM
To: Infinity Linden
Cc: hybi@ietf.org; Lloyd Wood; uri-review@ietf.org; Daniel R. Tobias; URI;
Lisa Dusseault
Subject: Re: [Uri-review] [hybi] ws: and wss: schemes

[snip]

But URIs in space? URIs are predicated on an authoritative DNS.
In deep space, DNS as it stands is likely not to be useful - lookups
take too long, contacts are scheduled and planned, late binding,
rather than early binding, is needed. And TCP's assumptions
and timers aren't a good fit with the environment. But that doesn't
rule out IP or other protocols in the suite.