Subject: Re: [Ace] [core] Fw: New Version Notification for draft-li-core-coap-node-id-option-01.txt

From: Likepeng <[email-masked]>
Date: Fri, 27 Jun 2014 09:29:18 +0000

Hi Abhijan,

Thanks for the feedback.

Since this is related to authentication and authorization, I also copy to ace mailing list for discussion.

I checked secure reconfiguration draft, it also includes Node Identifier for authentication.
http://tools.ietf.org/pdf/draft-kang-core-secure-reconfiguration-01.pdf

And I checked Authorization Information Format draft, it proposes to use URI-Host for authentication.
http://tools.ietf.org/pdf/draft-bormann-core-ace-aif-00.pdf

I will also check other related drafts to see which identifier is used, DeviceID/ NodeID or URI-Host.

In my opinion, usually URI-Host is domain name or IP address, and it is very easily to be changed. NodeID is more stable for authentication and authorization.

Also, if this identifier information is conveyed in a standardized way, for example, included in the CoAP header as an option, it will improve the interoperability.

Kind Regards
Kepeng

发件人: Abhijan Bhattacharyya [mailto:[email-masked]]
发送时间: 2014年6月27日 16:52
收件人: Likepeng
抄送: [email-masked]
主题: Re: [core] Fw: New Version Notification for draft-li-core-coap-node-id-option-01.txt

Hi Kepeng,
Thanks for this interesting draft. The concept might be useful in many cases. In fact, we have also used the concept of Node ID in the draft http://tools.ietf.org/html/draft-bhattacharyya-core-coap-lite-auth-00 (Fig. 1 and 2) which presents our work-in-progress on lightweight authentication and key-sharing which we shared few months back. However, we used the payload itself for conveying the NodeID information. Having an additional option to convey the NodeID would be useful.

Regards
Abhijan Bhattacharyya
Associate Consultant
Scientist, Innovation Lab, Kolkata, India
Tata Consultancy Services Limited
Mailto: [email-masked]<mailto:[email-masked]>
Website: http://www.tcs.com<http://www.tcs.com/>
____________________________________________
Experience certainty.        IT Services
                       Business Solutions
                       Consulting
____________________________________________
----- Forwarded by Abhijan Bhattacharyya/KOL/TCS on 06/27/2014 02:01 PM -----

From:        Abhijan Bhattacharyya <[email-masked]<mailto:[email-masked]>>
To:        Abhijan Bhattacharyya <[email-masked]<mailto:[email-masked]>>
Date:        06/27/2014 12:45 PM
Subject:        Fwd: [core] Fw: New Version Notification for draft-li-core-coap-node-id-option-01.txt
________________________________

---------- Forwarded message ----------
From: Likepeng <[email-masked]<mailto:[email-masked]>>
Date: Wed, Jun 25, 2014 at 12:55 PM
Subject: [core] Fw: New Version Notification for draft-li-core-coap-node-id-option-01.txt
To: "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>

Hello all,

This draft is quite simple.

Hope you can spend some short time to review it and give some feedback.

Thanks,
Kind Regards
Kepeng

-----邮件原件-----
发件人: [email-masked]<mailto:[email-masked]> [mailto:[email-masked]<mailto:[email-masked]>]
发送时间: 2014年6月25日 14:05
收件人: Gengyu Wei; Gengyu Wei; Likepeng; Likepeng
主题: New Version Notification for draft-li-core-coap-node-id-option-01.txt

A new version of I-D, draft-li-core-coap-node-id-option-01.txt
has been successfully submitted by Kepeng Li and posted to the IETF repository.

Name:           draft-li-core-coap-node-id-option
Revision:       01
Title:          CoAP Option Extension: NodeId
Document date:  2014-06-24
Group:          Individual Submission
Pages:          7
URL:            http://www.ietf.org/internet-drafts/draft-li-core-coap-node-id-option-01.txt
Status:         https://datatracker.ietf.org/doc/draft-li-core-coap-node-id-option/
Htmlized:       http://tools.ietf.org/html/draft-li-core-coap-node-id-option-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-li-core-coap-node-id-option-01

Abstract:
   CoAP is a RESTful application protocol for constrained nodes and
   networks.  This specification provides a simple extension for CoAP,
   the NodeId Option.  This Option can be used to identify the node,
   either the client or the server.

Note

   Discussion and suggestions for improvement are requested, and should
   be sent to [email-masked]<mailto:[email-masked]>.

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<http://tools.ietf.org/>.

The IETF Secretariat

_______________________________________________
core mailing list
[email-masked]<mailto:[email-masked]>
https://www.ietf.org/mailman/listinfo/core

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you