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

"Andrew Biggs (adb)" <> Tue, 19 March 2013 15:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 907AF21F8D5F for <>; Tue, 19 Mar 2013 08:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DU7haN8tTxWG for <>; Tue, 19 Mar 2013 08:22:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EE91B21F8D5D for <>; Tue, 19 Mar 2013 08:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1596; q=dns/txt; s=iport; t=1363706555; x=1364916155; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=SKtlM9CltAItBbi1WqKbklEXDBzXFHx4zsrMZcCeIuU=; b=b7PJa8MFYC4ALzqdevNSXjsbWRRx+TqSiVvxONm9d6lxl6nhHoGdiql6 MmkyquXTvubrf/dLZSxJ3ZPA05h2PNbc0Sm2DIzvcdTnhtqx8BeI0Jqkd TSAts+Eo6bo6KIuxoZavM8Gi1z3LanEuVkQRBf/Pgf92ZOhGw4lmMIlDg o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.84,872,1355097600"; d="scan'208";a="189082089"
Received: from ([]) by with ESMTP; 19 Mar 2013 15:22:34 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r2JFMYPP012507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 15:22:34 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 10:22:34 -0500
From: "Andrew Biggs (adb)" <>
To: Alexey Melnikov <>
Thread-Topic: [Aggsrv] understanding the scope of "discovery"
Thread-Index: AQHOI0zhdxnePYTEk0CJfRyfOYIPh5itXyoA//+0nwA=
Date: Tue, 19 Mar 2013 15:22:33 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [Aggsrv] understanding the scope of "discovery"
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Aggregated Service Discovery \(aggsrv\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 Mar 2013 15:22:35 -0000

I definitely agree, it might even be worth making an explicit statement to
that effect in the draft.

Even in the case where the protocol being negotiated doesn't provide a
means for establishing a given operational parameter, I'm wondering if we
should provide any guidance on the kind of information that should be
included as part of discovery.  For example, should it be limited strictly
to information needed to establish a connection to a service, or should
implementors be free to include anything they find useful, up to and
including general client configuration?

On 3/19/13 7:52 AM, "Alexey Melnikov" <> wrote:

>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
>On 17 Mar 2013, at 16:20, "Andrew Biggs (adb)" <> 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