Subject: [6lo] FW: New Version Notification for draft-ietf-6lo-ap-nd-21.txt

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Mon, 20 Apr 2020 14:06:03 +0000

Dear WG

We are still fighting with the IANA section but at least fixed the other topics that we found working in it, namely:
- use the full CIPO in the signature
- use JWS to encode the signature in the NDPSO
- Extend the 6CIO to expose support of AP-ND by the 6LR using the formats in this document (JSON-based)

We'll keep you tuned on the progress on the IANA. Apparently we have 2 choices:
- get the IANA section straight or
- remove Crypto-type 2 for now, reintroduce it later e.g., using René's LWIG draft

Please recheck the diffs, this doc is soon in the RFC editor's hand.

Keep safe

Pascal

-----Original Message-----
From: [email-masked] <[email-masked]> 
Sent: lundi 20 avril 2020 16:00
To: Pascal Thubert (pthubert) <[email-masked]>; Mohit Sethi <[email-masked]>; Rene Struik <[email-masked]>; Behcet Sarikaya <[email-masked]>
Subject: New Version Notification for draft-ietf-6lo-ap-nd-21.txt

A new version of I-D, draft-ietf-6lo-ap-nd-21.txt has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-ietf-6lo-ap-nd
Revision:	21
Title:		Address Protected Neighbor Discovery for Low-power and Lossy Networks
Document date:	2020-04-20
Group:		6lo
Pages:		32
URL:            https://www.ietf.org/internet-drafts/draft-ietf-6lo-ap-nd-21.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-6lo-ap-nd/
Htmlized:       https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-21
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-6lo-ap-nd
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-ap-nd-21

Abstract:
   This document updates the 6LoWPAN Neighbor Discovery (ND) protocol
   defined in RFC 6775 and RFC 8505.  The new extension is called
   Address Protected Neighbor Discovery (AP-ND) and it protects the
   owner of an address against address theft and impersonation attacks
   in a low-power and lossy network (LLN).  Nodes supporting this
   extension compute a cryptographic identifier (Crypto-ID) and use it
   with one or more of their Registered Addresses.  The Crypto-ID
   identifies the owner of the Registered Address and can be used to
   provide proof of ownership of the Registered Addresses.  Once an
   address is registered with the Crypto-ID and a proof-of-ownership is
   provided, only the owner of that address can modify the registration
   information, thereby enforcing Source Address Validation.

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