Re: [Aggsrv] understanding the scope of "discovery"

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 19 March 2013 13:46 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: aggsrv@ietfa.amsl.com
Delivered-To: aggsrv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01C0621F8BE2 for <aggsrv@ietfa.amsl.com>; Tue, 19 Mar 2013 06:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.552
X-Spam-Level:
X-Spam-Status: No, score=-101.552 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSDTVjBdQYP7 for <aggsrv@ietfa.amsl.com>; Tue, 19 Mar 2013 06:46:40 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 23AA021F8BDE for <aggsrv@ietf.org>; Tue, 19 Mar 2013 06:46:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1363700796; d=isode.com; s=selector; i=@isode.com; bh=Em+OtVZGWgR1jH4VCzmNz3RglCDpGuRFB/DiqbawhaQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=vaPUSTBNuJXR5lIktkMsIEObrJZAiYPhnK8Yz6W80r3x5TzFNgc2zUB427LJgbqnbfV9zL KsXpdcW7U+YrYNFfRytfl0PIWRgI9MfRVyscE5Tqk0nWDLY3lKE5derdMQtK3dJfHHuU6S mDbkOKbNoDlYL8J025q5E5/J1uvA4E0=;
Received: from [10.8.39.4] (173-14-120-161-richmond.hfc.comcastbusiness.net [173.14.120.161]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UUhsOwA4j5EV@statler.isode.com>; Tue, 19 Mar 2013 13:46:36 +0000
References: <4289BE64A83C6C4384EE9245D4644539237DD2AB@xmb-aln-x06.cisco.com>
In-Reply-To: <4289BE64A83C6C4384EE9245D4644539237DD2AB@xmb-aln-x06.cisco.com>
Message-Id: <0D99038D-1D63-4B6E-944A-7F1EFF255F8C@isode.com>
X-Mailer: iPhone Mail (10A523)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Tue, 19 Mar 2013 09:52:20 -0400
To: "Andrew Biggs (adb)" <adb@cisco.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Cc: "aggsrv@ietf.org" <aggsrv@ietf.org>
Subject: Re: [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: Tue, 19 Mar 2013 13:46:41 -0000

Hi Andrew,

IMHO, if these things are available in the protocol being negotiated, then I think they shouldn't be returned by the aggregated service discovery.

On 17 Mar 2013, at 16:20, "Andrew Biggs (adb)" <adb@cisco.com> wrote:

> 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.
> 
> Cheers,
> Andrew