Thread uses DTLS relay as a building block for bootstrapping. The DRY was solved with Thread specific messaging. You can find some details in their public whitepapers.
-----Original Message----- From: Michael Richardson [mailto:[email protected]] Sent: Friday, November 17, 2017 3:12 PM To: Sandeep Kumar <[email protected]>; [email protected] Cc: [email protected] Subject: Re: [Ace] DTLS proxy in EST-coaps Sandeep Kumar <[email protected]> wrote: > DTLS relaying draft was in DICE wg. The WG was not chartered for the > activity. Other SDOs picked it up and filed the gaps. mcr> For DTLS, I thought we had a few IDs on how to relay DTLS in a mcr> stateless manner. I can't seem to find any (Yes, I did look through mcr> expired drafts mcr> too). I was reminded in a private email that the document I wanted was yours: https://tools.ietf.org/html/draft-kumar-dice-dtls-relay-02 but it does not detail what the DRY header would look like. I assume it has to fit into DTLS clothing so that it can be demux'ed. I was hoping that your document had already figured that part out. Perhaps you have some thinking you can share? Which SDOs picked up the gap, and where are the documents? Were there IANA allocations required? -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- ________________________________ The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email. _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
