Hi Pascal:
I had a quick glance at the document, just to see which type of crypto
was being recommended. {For now, I did not review anything else yet.}
The document includes the option of using Curve25519, as defined in RFC
7748, for signing. In my mind, this should be Ed25519, as defined in RFC
8032.
Notes:
1) Curve25519 is a so-called Montgomery curve, whereas Ed25519 is a
(twisted) Edwards curve. Both can be thought of as being the same thing
mathematically, since a point of Ed25519 can be viewed as simply another
representation of a point of Curve25519 (i.e., both are isomorphic, in
math speak). However, Ed25519 is unambiguously specified, see RFC 8032,
Section 5.1, whereas the use of Curve25519 with signatures in not (at
least not with IETF or NIST documents).
2) Please note that RFC 8032 also suggests some flavors of Ed25519 (with
ctx, ph suffix). I would not recommend using the ctx flavor and do not
have an opinion on whether one should use the ph (also known as
pre-hashing) flavor (the latter depends on I/O restrictions of
implementations).
Best regards, Rene
On 9/21/2017 7:57 AM, Pascal Thubert (pthubert) wrote:
This update implements Charlie's editorial suggestions and solves the issues
that he found during his in depth review. Thanks a bunch Charlie!
Dear chairs: The document is now ready for a SECAREA review prior to last call.
Would it be possible to trigger it?
Thanks for all
Pascal
-----Original Message-----
From: 6lo [mailto:[email protected]] On Behalf Of [email protected]
Sent: jeudi 21 septembre 2017 13:42
To: [email protected]
Cc: [email protected]
Subject: [6lo] I-D Action: draft-ietf-6lo-ap-nd-03.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over Networks of Resource-constrained
Nodes WG of the IETF.
Title : Address Protected Neighbor Discovery for Low-power
and Lossy Networks
Authors : Behcet Sarikaya
Pascal Thubert
Mohit Sethi
Filename : draft-ietf-6lo-ap-nd-03.txt
Pages : 17
Date : 2017-09-21
Abstract:
This document defines an extension to 6LoWPAN Neighbor Discovery RFC
6775. Nodes supporting this extension compute a cryptographic Owner
Unique Interface ID and associate it with one or more of their
Registered Addresses. Once an address is registered with a
Cryptographic ID, only the owner of that ID can modify the anchor
state information of the Registered Address, and Source Address
Validation can be enforced.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6lo-ap-nd/
There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03
https://datatracker.ietf.org/doc/html/draft-ietf-6lo-ap-nd-03
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-ap-nd-03
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.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
--
email: [email protected] | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
