IETF Logo Mail Archive

Re: [core] About draft-doi-core-parameter-option

Yusuke DOI <yusuke.doi@toshiba.co.jp> Thu, 08 August 2013 08:10 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
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 CAC6921E804B for <core@ietfa.amsl.com>; Thu, 8 Aug 2013 01:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level:
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 u40eYwhNuz6n for <core@ietfa.amsl.com>; Thu, 8 Aug 2013 01:10:27 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 680C921E8055 for <core@ietf.org>; Thu, 8 Aug 2013 01:10:25 -0700 (PDT)
Received: from tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp ([133.199.200.50]) by imx2.toshiba.co.jp with ESMTP id r788AMuj007343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <core@ietf.org>; Thu, 8 Aug 2013 17:10:22 +0900 (JST)
Received: from tsbmgw-mgw02 (localhost [127.0.0.1]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r788AMNO005663 for <core@ietf.org>; Thu, 8 Aug 2013 17:10:22 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw02 (JAMES SMTP Server 2.3.1) with SMTP ID 246 for <core@ietf.org>; Thu, 8 Aug 2013 17:10:22 +0900 (JST)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r788AMg3005645 for <core@ietf.org>; Thu, 8 Aug 2013 17:10:22 +0900
Received: (from root@localhost) by arc1.toshiba.co.jp id r788AMr4007841 for core@ietf.org; Thu, 8 Aug 2013 17:10:22 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id TAA07833; Thu, 8 Aug 2013 17:10:22 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id r788ALPs025090 for <core@ietf.org>; Thu, 8 Aug 2013 17:10:21 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id r788ALVI021937; Thu, 8 Aug 2013 17:10:21 +0900 (JST)
Received: from [10.0.2.15] (ncg-dhcp117.isl.rdc.toshiba.co.jp [133.196.16.117]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id 262E997D3A; Thu, 8 Aug 2013 17:10:21 +0900 (JST)
Message-ID: <5203526F.1090706@toshiba.co.jp>
Date: Thu, 08 Aug 2013 17:10:23 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.2; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Zach Shelby <zach@sensinode.com>
References: <51FCDE1D.4010807@toshiba.co.jp> <5DF819CB-1CBA-47F1-867A-CFC9C9D377BA@sensinode.com>
In-Reply-To: <5DF819CB-1CBA-47F1-867A-CFC9C9D377BA@sensinode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: core@ietf.org
Subject: Re: [core] About draft-doi-core-parameter-option
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: Thu, 08 Aug 2013 08:10:37 -0000

Dear Zach,

(2013/08/05 23:59), Zach Shelby wrote:
> Did you submit a new version of the draft updated with this? I guess
> you are asking for reviews and comments, just making sure what
> version to look at.

Thanks, I just updated it with minor fixes.

http://www.ietf.org/id/draft-doi-core-parameter-option-03.txt

>> FYI: There is a proposal on NetConf to use EXI. Currently, there is
>> no adpotion of CoAP on NetConf (there is another proposal on
>> RESTful API of NetConf). But I think this could be an interesting
>> combination: NetConf RESTful API transported over CoAP.
>
> In the COMAN discussion group we have been coming to the conclusion
> that a RESTful representation of MiBs would be very useful. I am not
> sure what added benefit a RESTful representation of NetConf would
> necessarily serve? I would think that would be more useful for
> proxying NetConf to HTTP.

At this time, I'm a quite newbie of NetConf and am not a right person to 
say 'what added benefit'. My guess is there are good number of users of 
NetConf and they are extending their world as others do.

Regards,

-- 
// Yusuke DOI <yusuke.doi@toshiba.co.jp>

v2.23.0 | Report a Bug | By Email