From abc4f6f1128e3c39c1de9c3ddbbff053d5b7538a Mon Sep 17 00:00:00 2001 From: Erik Nygren Date: Wed, 10 Jun 2020 22:50:20 -0400 Subject: [PATCH] Different IANA policies for different SvcParamKey ranges Fixes #154 --- draft-ietf-dnsop-svcb-httpssvc.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/draft-ietf-dnsop-svcb-httpssvc.md b/draft-ietf-dnsop-svcb-httpssvc.md index 1892d86e..b4550682 100644 --- a/draft-ietf-dnsop-svcb-httpssvc.md +++ b/draft-ietf-dnsop-svcb-httpssvc.md @@ -1227,9 +1227,20 @@ A registration MUST include the following fields: * Meaning: a short description * Pointer to specification text -Values to be added to this namespace require Expert Review (see -{{!RFC5226}}, Section 4.1). Apart from the initial contents, the name -MUST NOT start with "key". +SvcParamKey values to be added to this namespace +have different policies ({{!RFC5226}}, Section 4.1) +based on their range: + +| SvcParamKey | IANA Policy | +| ----------- | ---------------------- | +| 0-255 | Standards Action | +| 256-32767 | Expert Review | +| 32768-65280 | First Come First Served | +| 65280-65534 | Private Use | +| 65535 | Standards Action | + +Apart from the initial contents, the SvcParamKey +name MUST NOT start with "key". ### Initial contents {#iana-keys}