[Aggsrv] understanding the scope of "discovery"

"Andrew Biggs (adb)" <adb@cisco.com> Sun, 17 March 2013 20:20 UTC

Return-Path: <adb@cisco.com>
X-Original-To: aggsrv@ietfa.amsl.com
Delivered-To: aggsrv@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F288821F8BC0 for <aggsrv@ietfa.amsl.com>; Sun, 17 Mar 2013 13:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iDd+C8KSw4F6 for <aggsrv@ietfa.amsl.com>; Sun, 17 Mar 2013 13:20:36 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3462E21F8BBD for <aggsrv@ietf.org>; Sun, 17 Mar 2013 13:20:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2468; q=dns/txt; s=iport; t=1363551636; x=1364761236; h=from:to:subject:date:message-id:mime-version; bh=s++aPpkYSpWm9XwHVAAhlqQ+MGM8TnhNxbwUCtlSHUU=; b=NOL3VlUzP6XSBGDp8FVHVyZx9ELdUpbCS5FfAmnb1ldsnLH7h9/kIerY e/zIfmWfAz/qHYoGm5pdEUQD/5gTwzJiXhNLtipPEobk5LuutdljQy8Om 39TKeU4yRvnAbqewDJ5uvLdBrwzSIkLVrFGiv5GeS6WpEc4pAh2Hj0u7Q 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAD4kRlGtJV2a/2dsb2JhbABDhCnBDoFzFm0HgiwBBIELAQwBHVYnBBuIDKFOoC6NVIEQgxdhA6dggwqCKA
X-IronPort-AV: E=Sophos; i="4.84,860,1355097600"; d="scan'208,217"; a="188403270"
Received: from rcdn-core-3.cisco.com ([]) by rcdn-iport-8.cisco.com with ESMTP; 17 Mar 2013 20:20:35 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com []) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2HKKZYg004275 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <aggsrv@ietf.org>; Sun, 17 Mar 2013 20:20:35 GMT
Received: from xmb-aln-x06.cisco.com ([]) by xhc-rcd-x10.cisco.com ([]) with mapi id 14.02.0318.004; Sun, 17 Mar 2013 15:20:35 -0500
From: "Andrew Biggs (adb)" <adb@cisco.com>
To: "aggsrv@ietf.org" <aggsrv@ietf.org>
Thread-Topic: understanding the scope of "discovery"
Thread-Index: AQHOI0zhdxnePYTEk0CJfRyfOYIPhw==
Date: Sun, 17 Mar 2013 20:20:35 +0000
Message-ID: <4289BE64A83C6C4384EE9245D4644539237DD2AB@xmb-aln-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_4289BE64A83C6C4384EE9245D4644539237DD2ABxmbalnx06ciscoc_"
MIME-Version: 1.0
Subject: [Aggsrv] understanding the scope of "discovery"
X-BeenThere: aggsrv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Aggregated Service Discovery \(aggsrv\)" <aggsrv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aggsrv>, <mailto:aggsrv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aggsrv>
List-Post: <mailto:aggsrv@ietf.org>
List-Help: <mailto:aggsrv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aggsrv>, <mailto:aggsrv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2013 20:20:37 -0000

I thought an interesting point raised in the BoF was the possible overlap of aggregated discovery with the idea of automated client configuration.  This got me to wonder where the line ought to be drawn, if at all, as to the sort of information intended for inclusion in an aggregated service discovery document.  For example, would any of the following be appropriate data to include in a discovery document when configuring a particular service?

* Synchronization window (such as for calendaring).
* Session timeout.
* Minimum polling interval.
* Settings defaults for client behaviors, auto sign-in, etc.