IETF Logo Mail Archive

Re: [Spud] discovery

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 19 March 2015 17:02 UTC

Return-Path: <jhildebr@cisco.com>
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 BE1D71A1A47 for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 10:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 vp6Dwr8lIJLA for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 10:02:08 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CF351A1EF3 for <spud@ietf.org>; Thu, 19 Mar 2015 10:02:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1192; q=dns/txt; s=iport; t=1426784528; x=1427994128; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=OaT0qChyqSQTYe4gIHySi+QSkubnDp8aEjQToII0S5U=; b=VpGEVZK7u342Er096cgEit2PiyqUk44CcPkqUEvaEJuzOnAvnA2FJXW8 pUuc1tqDw0xTiidE6jOCBnoubw8nXjlvR3RnPik+ZT94AJrrC8qjvgkK+ l0p7DUyak4ijwWJdkG69z/k0cNM5EWTM9KzhJJFMFHHdsi8vlBSnu0C+R s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BYCgDT/wpV/4UNJK1cgwaBLASDCcBdiC8CHIEwTAEBAQEBAX2EEAEBBCMRRRACAQgODAImAgICMBUQAgQBDQWIL7IunAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSGJdoQ+MweCaC+BFgEEjjuCDoltgRuPRoNHIoNub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,430,1422921600"; d="scan'208";a="133563352"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP; 19 Mar 2015 17:02:07 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t2JH27q0032711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Mar 2015 17:02:07 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.80]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Thu, 19 Mar 2015 12:02:06 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Brian Trammell <ietf@trammell.ch>, Aaron Falk <aaron.falk@gmail.com>
Thread-Topic: [Spud] discovery
Thread-Index: AQHQYlwdY0g4PRrXtUWIpxnYDpPRSJ0kT9iA//+nhoA=
Date: Thu, 19 Mar 2015 17:02:05 +0000
Message-ID: <D5BA19E3-9957-4764-8D7F-FCEB3355D012@cisco.com>
References: <CAD62q9V8wg6YrTVmg4px=sBdXZyEYZE0iAUd6mJfmgJnDLEMmg@mail.gmail.com> <BAD98A61-4B9D-43B6-B79E-0B3CE26A6740@trammell.ch>
In-Reply-To: <BAD98A61-4B9D-43B6-B79E-0B3CE26A6740@trammell.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/15.8.1.150311
x-originating-ip: [10.129.24.156]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1A1EA83ED2D4AA46ADD15AD15E2DB444@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/aZiFJwS_BQ31qQ6YyIwR8pHaG3s>
Cc: "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: Thu, 19 Mar 2015 17:02:12 -0000

On 3/19/15, 10:18 AM, "Brian Trammell" <ietf@trammell.ch> wrote:

>>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.

Agree.

>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.

RFC 3263 provides an existence proof, but probably not a design pattern to follow.

-- 
Joe Hildebrand

v2.8.7 | Report a Bug | By Email