Spencer Dawkins via Datatracker <noreply@xxxxxxxx> wrote:
> This is a well-written specification. My only question - and I expect
> the answer will be “no” - is whether there is any concern that sizes of
> the resources that are being passed around might exceed the MTU between
> the pledge and the registrar, and whether there should be a mention of
> this possibility in the specification.
There were several answers already.
There are two places where this matters:
a) during the DTLS setup phase. DTLS has a fragmentation mechanism to deal
with DTLS messages which are larger than a UDP packet.
End points can be conservative and keep below 1280.
b) during the data transfer phase, DTLS does not provide any fragmentation
and assumes applications won't send things larger than a UDP message,
or that UDP fragmentation is acceptable.
For this, we use CoAP Block modes. This is also described in RFC9148.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
