search

anima-wg / constrained-join-proxy

1 stars 2 forks source link

Suggested changes to IANA considerations from ED #7

Closed mcr closed 2 years ago

mcr commented 2 years ago

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
petervanderstok commented 2 years ago

thanks, has been added to text closed