Join Proxy for Bootstrapping of Constrained Network Elements
draft-ietf-anima-constrained-join-proxy-18

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, anima-chairs@ietf.org, anima@ietf.org, draft-ietf-anima-constrained-join-proxy@ietf.org, jiangsheng@huawei.com, rfc-editor@rfc-editor.org, rwilton@cisco.com
Subject: Protocol Action: 'Constrained Join Proxy for Bootstrapping Protocols' to Proposed Standard (draft-ietf-anima-constrained-join-proxy-09.txt)

The IESG has approved the following document:
- 'Constrained Join Proxy for Bootstrapping Protocols'
  (draft-ietf-anima-constrained-join-proxy-09.txt) as Proposed Standard

This document is the product of the Autonomic Networking Integrated Model and
Approach Working Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-join-proxy/

Ballot Text

Technical Summary

   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.

   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.  It
   relays join traffic from the Pledge to the Registrar.

Working Group Summary

  This document was called draft-vanderstok-anima-constrained-join-proxy
  prior to its adoption. There was unanimous support for it in favor of 
  adoption and none against), so this document was adopted in November
  2020. There was interest in this work posts since its adoption. 
  There was never any opposition for this work.
  
  This document went through a relevant long document development
  period (22 months for individual document period, 15 months for WG 
  document period). It has been reviewed well.

Document Quality

  This document went through multiple reviews by multiple WG
  participants.  For now, there is no known existing implementation.

Personnel

  Sheng Jiang is the document shepherd.
  Robert Wilton is the responsible AD.

RFC Editor Note