<blockquote>
<p><code>DTLS_PSK</code> and <code>DTLS_ECC</code> should be exposed to the doc somewhere. And maybe renamed <code>SOCK_DTLS_PSK</code>/<code>SOCK_DTLS_ECC</code>. How about adding</p>
<div class="highlight highlight-source-c"><pre>#<span class="pl-k">ifdef</span> DOXYGEN
#<span class="pl-k">define</span> <span class="pl-en">SOCK_DTLS_PSK</span> (<span class="pl-c1">0</span>) <span class="pl-c"><span class="pl-c">/*</span>*< PSK mode <span class="pl-c">*/</span></span>
#<span class="pl-k">define</span> <span class="pl-en">SOCK_DTLS_ECC</span> (<span class="pl-c1">0</span>) <span class="pl-c"><span class="pl-c">/*</span>*< ECC mode <span class="pl-c">*/</span></span>
#<span class="pl-k">endif</span></pre></div>
<p>or something similar to <code>net/sock/dtls.h</code>?</p>
</blockquote>
<p>I think it is better to expose it in tinydtls pkg instead of DTLS sock as <code>DTLS_PSK</code> and <code>DTLS_ECC</code> is tinydtls specific and other DTLS implementation may not have/use defines to enable support for specific cipher suites (e.g. wolfSSL uses <a href="https://www.wolfssl.com/doxygen/group__Setup.html#gac5835a41f08b90828e72ec20d46d6399" rel="nofollow"><code>wolfSSL_CTX_set_cipher_list()</code></a>). There are also other defines that are not documented anywhere other than <a href="https://github.com/RIOT-OS/RIOT/blob/master/examples/dtls-echo/README.md#handling-the-static-memory-allocation">examples/dtls-echo README</a> such as DTLS_CONTEXT_MAX and more.</p>
<p>Or would documenting it all in a new doxygen group (e.g. net_encryption) be better? The group could also describe caveats and configuration options of each DTLS implementation and explain how to use credman with DTLS sock. In general, information on how to get started with using (D)TLS in RIOT.</p>
<blockquote>
<p>Also, it's not clear to me, if the two are mutually exclusive</p>
</blockquote>
<p>No, it is not mutually exclusive. A DTLS sock should be able to use multiple cipher suites.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/11909?email_source=notifications&email_token=ABE7WYGQHPXRFXUENBZWMYTQB4EX7A5CNFSM4IGRA3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BC75I#issuecomment-516042741">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYFL3KXCJKNOPGCH3G3QB4EX7ANCNFSM4IGRA3OA">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABE7WYB6SBXDNF3XHKN56VLQB4EX7A5CNFSM4IGRA3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BC75I.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/pull/11909?email_source=notifications\u0026email_token=ABE7WYGQHPXRFXUENBZWMYTQB4EX7A5CNFSM4IGRA3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BC75I#issuecomment-516042741",
"url": "https://github.com/RIOT-OS/RIOT/pull/11909?email_source=notifications\u0026email_token=ABE7WYGQHPXRFXUENBZWMYTQB4EX7A5CNFSM4IGRA3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BC75I#issuecomment-516042741",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>