Re: [Spud] discovery
Brian Trammell <ietf@trammell.ch> Fri, 20 March 2015 02:01 UTC
Return-Path: <ietf@trammell.ch>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 6455B1A912F
for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 19:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001,
T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 f1fdKzhH5Zag for <spud@ietfa.amsl.com>;
Thu, 19 Mar 2015 19:01:15 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66])
by ietfa.amsl.com (Postfix) with ESMTP id 3386B1A9129
for <spud@ietf.org>; Thu, 19 Mar 2015 19:01:15 -0700 (PDT)
Received: from [10.120.1.181] (rrcs-184-75-115-252.nyc.biz.rr.com
[184.75.115.252])
by trammell.ch (Postfix) with ESMTPSA id AE9991A01AC;
Fri, 20 Mar 2015 03:00:43 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <E97A77C9-0C06-4036-95AF-8D8EF19D0AB0@ifi.uio.no>
Date: Thu, 19 Mar 2015 22:00:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8996D749-9936-4BB3-B494-08556CE8D41C@trammell.ch>
References: <CAD62q9V8wg6YrTVmg4px=sBdXZyEYZE0iAUd6mJfmgJnDLEMmg@mail.gmail.com>
<BAD98A61-4B9D-43B6-B79E-0B3CE26A6740@trammell.ch>
<E97A77C9-0C06-4036-95AF-8D8EF19D0AB0@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/8jgUyzzVVH9cze61WiG90Ag8k9M>
Cc: Aaron Falk <aaron.falk@gmail.com>, "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] discovery
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>,
<mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>,
<mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2015 02:01:17 -0000
> On 19 Mar 2015, at 19:21, Michael Welzl <michawe@ifi.uio.no> wrote: > > >> On 19. mar. 2015, at 17.18, Brian Trammell <ietf@trammell.ch> wrote: >> >> hi Aaron, >> >>> On 19 Mar 2015, at 11:48, Aaron Falk <aaron.falk@gmail.com> wrote: >>> >>> The draft >> >> ... where "the draft" is draft-hildebrand-spud-prototype ... >> >>> doesn't say much about how one efficiently determines whether the other end is SPUD-capable so that an application can know whether it can use it. >> >> No, it doesn't. >> >>> Has anyone given thought to this? >> >> Yes, I have... >> >> I think for the most part that this question is (1) very important but (2) mostly orthogonal to that we're trying to answer in spud-prototype. >> >> Initially, I would expect that discovery works the same way that it does for any other user of the transport layer: you either have a URL, or a name and a port, or some information from your application-layer protocol's discovery service, which includes "uses x-over-SPUD" in its semantics. >> >> Dynamically discovering a SPUD endpoint might make sense if a server port / URL schema is assigned to a service over X or a service over x-over-SPUD. In this case, the magic number we've selected makes SPUD server probing by the client possible: a SPUD packet is neither valid UTF-8, UTF-16, UTF-32, ASN.1 BER or DER, DTLS, NTP, DNS, DHCP, TFTP, or Bittorrent. This is not an exhaustive list, but we haven't found a protocol over UDP that is likely to consider d8 00 00 d8 as the first four bytes anything other than an error. > > - but that won't tell you if SPUD actually does work across the path... True. But discovery (is there an endpoint there?) is a separate question from path transparency (once you've found the endpoint, can you actually talk to it?) This would be an argument for specifying a dynamic discovery method, though -- not for determining whether you should use SPUD, but whether you can. Cheers, Brian >> Maybe we should mention this in the draft, but I think it's the *next* problem to solve. > > to me, this has a "famous last words" feel to it... > > Cheers, > Michael > > _______________________________________________ > Spud mailing list > Spud@ietf.org > https://www.ietf.org/mailman/listinfo/spud
- Re: [Spud] discovery Mirja Kühlewind
- [Spud] discovery Aaron Falk
- Re: [Spud] discovery Brian Trammell
- Re: [Spud] discovery Joe Hildebrand (jhildebr)
- Re: [Spud] discovery Michael Welzl
- Re: [Spud] discovery Brian Trammell
- Re: [Spud] discovery Michael Welzl
- Re: [Spud] discovery Brian Trammell
- Re: [Spud] discovery Michael Welzl