Join Proxy for Bootstrapping of Constrained Network Elements
draft-ietf-anima-constrained-join-proxy-15
| Document | Type |
Expired Internet-Draft
(anima WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Richardson , Peter Van der Stok , Panos Kampanakis | ||
| Last updated | 2024-05-09 (Latest revision 2023-11-06) | ||
| Replaces | draft-vanderstok-anima-constrained-join-proxy | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Reviews |
GENART Last Call review
(of
-14)
by Ines Robles
Almost ready
IOTDIR Last Call review
(of
-14)
by Russ Housley
Almost ready
ARTART Last Call review
(of
-10)
by Rich Salz
Ready w/nits
GENART Last Call review
(of
-09)
by Ines Robles
On the right track
OPSDIR Last Call review
(of
-09)
by Jürgen Schönwälder
Serious issues
IOTDIR Last Call review
(of
-05)
by Russ Housley
On the right track
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| Document shepherd | Sheng Jiang | ||
| Shepherd write-up | Show Last changed 2022-02-24 | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | Mahesh Jethanandani | ||
| Send notices to | jiangsheng@huawei.com, shengjiang@bupt.edu.cn | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA expert review state | Issues identified | ||
| IANA expert review comments | From the designated expert for Resource Type (rt=) Link Target Attribute Values: I looked at the registration requests in the draft. They use somewhat unusual language about discovering ports - resource discovery is understood to discover resources. For brski.jp, this appears to be about discovering a CoAP or CoAPs entry point (without describing how exactly that is then used, e.g., what happens if that has a different IP address in the authority than the request address). For brski.rjp, this appears to be about discovering an entry point for a protocol that I don’t seem to fully understand the description for. I didn’t try to obtain a deep understanding of the protocol before writing this, but I would prefer if the language used for the description were understandable for other registrants in this registry, i.e., discussing resources, not ports (port numbers?). All the other criteria for a registration appear to be fulfilled. |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document extends the work of Bootstrapping Remote Secure Key Infrastructures (BRSKI) by replacing the Circuit-proxy between Pledge and Registrar by a stateless/stateful constrained Join Proxy. The constrained Join Proxy is a mesh neighbor of the Pledge and can relay a DTLS session originating from a Pledge with only link-local addresses to a Registrar which is not a mesh neighbor of the Pledge. This document defines a protocol to securely assign a Pledge to a domain, represented by a Registrar, using an intermediary node between Pledge and Registrar. This intermediary node is known as a "constrained Join Proxy". An enrolled Pledge can act as a constrained Join Proxy.
Authors
Michael Richardson
Peter Van der Stok
Panos Kampanakis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)