Hello, Based on my earlier review comments: see below Section 9 proposed text. It adds these elements that I think are missing in the current -05 text. I hope that clarifies it. Also it refers to an existing IANA policy from RFC 8126.
--- 9. IANA Considerations 9.1 Registry for JPY protocol header fields This document defines a new IANA registry for map indices of the CBOR Map used in the JPY protocol. The IANA policy for registration of an entry in the registry is "IETF Review" as defined by [RFC 8126]. A new registry entry MUST define the fields Map Index, Name, CBOR Type (referring to [RFC 8949] defined types), and Description. The initial contents of the registry are as follows: Map Index Name CBOR Type Description ========= ========== =========== ======================================== 0 ip byte string Pledge IPv4/IPv6 link-local address (4 or 16 bytes) 1 port integer Pledge's UDP port number 2 family integer IP address family; IPv4 (value 4) or IPv6 (value 6) 3 index integer Join Proxy network interface index/identifier 4 payload byte string DTLS message payload --- -----Original Message----- From: Anima <[email protected]> On Behalf Of [email protected] Sent: Monday, October 18, 2021 14:12 To: [email protected] Cc: [email protected] Subject: [Anima] I-D Action: draft-ietf-anima-constrained-join-proxy-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF. Title : Constrained Join Proxy for Bootstrapping Protocols Authors : Michael Richardson Peter van der Stok Panos Kampanakis Filename : draft-ietf-anima-constrained-join-proxy-05.txt Pages : 19 Date : 2021-10-18 Abstract: 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". This document extends the work of [RFC8995] by replacing the Circuit- proxy between Pledge and Registrar by a stateless/stateful constrained (CoAP) Join Proxy. It relays join traffic from the Pledge to the Registrar. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-join-proxy/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-join-proxy-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-constrained-join-proxy-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
