IETF Logo Mail Archive

[core] Group Management feature

TianLinyi <tianlinyi@huawei.com> Fri, 18 November 2011 04:00 UTC

Return-Path: <tianlinyi@huawei.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37DF211E80CA for <core@ietfa.amsl.com>; Thu, 17 Nov 2011 20:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.082
X-Spam-Level:
X-Spam-Status: No, score=-5.082 tagged_above=-999 required=5 tests=[AWL=1.516, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 7LrpqQtVmShZ for <core@ietfa.amsl.com>; Thu, 17 Nov 2011 20:00:49 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2489811E8073 for <core@ietf.org>; Thu, 17 Nov 2011 20:00:49 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUU00K4O8BOKB@szxga04-in.huawei.com> for core@ietf.org; Fri, 18 Nov 2011 11:57:24 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUU002ES8AYCD@szxga04-in.huawei.com> for core@ietf.org; Fri, 18 Nov 2011 11:57:24 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFD70308; Fri, 18 Nov 2011 11:57:24 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 18 Nov 2011 11:57:12 +0800
Received: from SZXEML513-MBX.china.huawei.com ([169.254.8.59]) by szxeml405-hub.china.huawei.com ([10.82.67.60]) with mapi id 14.01.0323.003; Fri, 18 Nov 2011 11:56:39 +0800
Date: Fri, 18 Nov 2011 03:57:11 +0000
From: TianLinyi <tianlinyi@huawei.com>
X-Originating-IP: [172.24.2.40]
To: "core@ietf.org" <core@ietf.org>
Message-id: <3615F3CCD55F054395A882F51C6E5FDA182027B3@szxeml513-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_SEJI4ZRezNBydqVPLkPKEw)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: Group Management feature
Thread-index: AcylpY1VpkIBbtWwT+uaxHCAwurMBA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
Subject: [core] Group Management feature
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 04:00:50 -0000

Hi, All



I would like to give some information about how application guys doing by leveraging our drafts:

1. When sensor is detected by the gateway, or it is registered with gateway using mechanism defined in draft-nieminen-core-service-discovery-01</doc/draft-nieminen-core-service-discovery/> or some othe mechanisms.

2. Gateway can notify the application server with inventory information.

3. Application Server can create the group by listing the device identifiers or based on some condition. Then gateway can assign the group identifer and gives to application server.



Group management is completely possible in application layer. Maybe we don't need to keep it in appendix either.



For multicast topic i see some value in this draft. I agree with Jari that we need to focus on specific topics in this draft and make it simpler.



Cheers,

Linyi

v2.23.0 | Report a Bug | By Email