From de4e98802f6f66aedc33d2ea79d227de9c0c63b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Ams=C3=BCss?= Date: Sun, 7 Jul 2024 22:03:04 +0200 Subject: [PATCH] SVCB: swap URI production and literals --- draft-ietf-core-transport-indication.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/draft-ietf-core-transport-indication.md b/draft-ietf-core-transport-indication.md index 38888ec..21f0e47 100644 --- a/draft-ietf-core-transport-indication.md +++ b/draft-ietf-core-transport-indication.md @@ -815,12 +815,6 @@ it would have required that the server present some credential that could be ver for example an x5chain containing a Let's Encrypt certificate. -## Expressing Service Parameters as literals {#svcblit} - -TBD - -### Examples - ## Producing a URI from a discovered service {#svcb2uri} If a service's discovery process does not produce a URI but an address, host name and/or Service Binding Parameters, @@ -832,6 +826,13 @@ TBD ### Examples + +## Expressing Service Parameters as literals {#svcblit} + +TBD + +### Examples + # Guidance to upcoming transports {#upcomingtransports} When new transports are defined for CoAP,