Re: [Aggsrv] understanding the scope of "discovery"
"Andrew Biggs (adb)" <firstname.lastname@example.org> Tue, 19 March 2013 15:22 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907AF21F8D5F for <email@example.com>; Tue, 19 Mar 2013 08:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 mail.ietf.org ([188.8.131.52]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DU7haN8tTxWG for <firstname.lastname@example.org>; Tue, 19 Mar 2013 08:22:35 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [184.108.40.206]) by ietfa.amsl.com (Postfix) with ESMTP id EE91B21F8D5D for <email@example.com>; Tue, 19 Mar 2013 08:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; firstname.lastname@example.org; 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-AV: E=Sophos;i="4.84,872,1355097600"; d="scan'208";a="189082089"
Received: from rcdn-core-5.cisco.com ([220.127.116.11]) by rcdn-iport-2.cisco.com with ESMTP; 19 Mar 2013 15:22:34 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [18.104.22.168]) by rcdn-core-5.cisco.com (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 xmb-aln-x06.cisco.com ([169.254.1.248]) by xhc-rcd-x11.cisco.com ([22.214.171.124]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 10:22:34 -0500
From: "Andrew Biggs (adb)" <email@example.com>
To: Alexey Melnikov <firstname.lastname@example.org>
Thread-Topic: [Aggsrv] understanding the scope of "discovery"
Date: Tue, 19 Mar 2013 15:22:33 +0000
Content-Type: text/plain; charset="us-ascii"
Cc: "email@example.com" <firstname.lastname@example.org>
Subject: Re: [Aggsrv] understanding the scope of "discovery"
List-Id: "Aggregated Service Discovery \(aggsrv\)" <aggsrv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aggsrv>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aggsrv>, <mailto:firstname.lastname@example.org?subject=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" <email@example.com> 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 >discovery. > >On 17 Mar 2013, at 16:20, "Andrew Biggs (adb)" <firstname.lastname@example.org> 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 >
- [Aggsrv] understanding the scope of "discovery" Andrew Biggs (adb)
- Re: [Aggsrv] understanding the scope of "discover… Alexey Melnikov
- Re: [Aggsrv] understanding the scope of "discover… Andrew Biggs (adb)