From db15d5a7d644e998e05f4ed8be4d5ecbd8cb16cd Mon Sep 17 00:00:00 2001 From: Carsten Bormann Date: Tue, 2 Jul 2024 21:38:30 +0200 Subject: [PATCH] Mention RFC 9146 (via Achim Kraus) --- draft-bormann-core-corr-clar.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/draft-bormann-core-corr-clar.md b/draft-bormann-core-corr-clar.md index aad5a14..5c34fec 100644 --- a/draft-bormann-core-corr-clar.md +++ b/draft-bormann-core-corr-clar.md @@ -42,6 +42,9 @@ informative: target: https://github.com/eclipse-californium/californium/blob/main/element-connector/src/main/java/org/eclipse/californium/elements/EndpointContextMatcher.java title: EndpointContextMatcher.java date: false + RFC9146: + # Connection Identifiers for DTLS 1.2. That keeps the session/epoch and enables to change the ip-address/port, if the matching is relaxed from the ip-endpoints. + --- abstract @@ -261,6 +264,17 @@ Therefore, enhancements may be called for: Where extensions are already actively being developed, this work should be done in the context of the extension effort. + {:type="a"} + 1. Protocol mechanisms that have been defined for stitching + together connections or phases of an underlying connection, such + as Connection Identifiers for DTLS 1.2 {{RFC9176}}, may enable + keeping the session/epoch unchanged and even to change the + transport address (ip-address/port), once appropriately modified + match boxing rules are specified for the stitching mechanism. + (These rules either need to be defined to be implicitly active + for any use of the mechanism or they may require negotiation, + see below.) + 2. Optimizations such as Eclipse/Californium EndpointContextMatcher {{CF-MATCHER}} might not work properly unless both sides of the communication agree on the extent of the matching boxes.