[core] FW: New Version Notification for draft-vasu-ace-core-access-privilege-provisioning-00.txt

Vasu Kantubukta <vasu.kantubukta@huawei.com> Mon, 18 April 2016 10:23 UTC

Return-Path: <vasu.kantubukta@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 718A112DE08; Mon, 18 Apr 2016 03:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level:
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIHfCm9WmYAw; Mon, 18 Apr 2016 03:23:24 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 549D412DDF9; Mon, 18 Apr 2016 03:23:23 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CHT94160; Mon, 18 Apr 2016 09:56:42 +0000 (GMT)
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 18 Apr 2016 10:56:34 +0100
Received: from BLREML509-MBB.china.huawei.com ([169.254.1.138]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0235.001; Mon, 18 Apr 2016 15:26:24 +0530
From: Vasu Kantubukta <vasu.kantubukta@huawei.com>
To: "core@ietf.org" <core@ietf.org>, "ace@ietf.org" <ace@ietf.org>
Thread-Topic: New Version Notification for draft-vasu-ace-core-access-privilege-provisioning-00.txt
Thread-Index: AQHRlzE4W5soGoneV0Ws+BItK+DdmJ+PgGNg
Date: Mon, 18 Apr 2016 09:56:23 +0000
Message-ID: <D6EBB546995C064A9492E8E27F62D90D0AA2B2C2@blreml509-mbb.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.211.249]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/glEPDiVJysP6gvcepkJ90dVaOxk>
Cc: Ashutosh prakash <ashutosh.prakash@huawei.com>, Javed siddiqui <javed.siddiqui@huawei.com>, "Zuojing (2012 Laboratories)" <jing.zuo@huawei.com>
Subject: [core] FW: New Version Notification for draft-vasu-ace-core-access-privilege-provisioning-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 18 Apr 2016 10:23:25 -0000

Dear CORE and ACE,

We have submitted a draft on "access privilege provisioning for constrained devices" that provides a method to configure the policies for admission as well as resource control in constrained environment (including both constrained and non-constrained devices) which includes complete system architecture, methods for defining policies, and with commissioning procedures. Here, the service provisioning includes authentication, authorization, admission and resource control.

The draft details about the following:

1) Discover provisioning server, and verify registered service with CORE-RD using commissioning procedure.
2) Defining admission control policies for registered resources.
3) How resource control policies can be configured to allow only privileged users to access the resource?

We would like to discuss the CoRE, and ACE aspects of this draft in the CORE and ACE WG meeting.

Thanks and Best Regards
K Vasu


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: 2016年4月15日 21:40
To: Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs); Vasu Kantubukta; Vasu Kantubukta; Yangneng; Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)
Subject: New Version Notification for draft-vasu-ace-core-access-privilege-provisioning-00.txt


A new version of I-D, draft-vasu-ace-core-access-privilege-provisioning-00.txt
has been successfully submitted by Kantubukta Vasu and posted to the IETF repository.

Name:		draft-vasu-ace-core-access-privilege-provisioning
Revision:	00
Title:		Access Privilege Provisioning for Constrained Devices
Document date:	2016-04-15
Group:		Individual Submission
Pages:		30
URL:            https://www.ietf.org/internet-drafts/draft-vasu-ace-core-access-privilege-provisioning-00.txt
Status:         https://datatracker.ietf.org/doc/draft-vasu-ace-core-access-privilege-provisioning/
Htmlized:       https://tools.ietf.org/html/draft-vasu-ace-core-access-privilege-provisioning-00


Abstract:
   As more constrained devices are integrating with current Internet,
   the ubiquitous computing in scenarios like smart home is very
   important. In smart home, the constrained devices (ex. thermostat)
   need to be provisioned in such a way that it can inter-operate with
   any kind of devices like other constrained devices (ex. Air
   conditioner) or client devices (ex. smart phone). This document
   provides a method to support access privilege provisioning based on
   pre-configured admission and resource control policies, where this
   method explains device's service access in two different use cases:
   first provisioning the service when a constrained device accessing
   the service provided by other constrained device, second, accessing
   the service provided by constrained device from the client device
   (non constrained device).

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat