The latest RFC draft for SVCB and HTTPS records (https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-https-08.html) renames the "echconfig" parameter key to "ech". This proposed change implements that renaming. For backwards compatibility of text parsing, the "echconfig" parameter name will still be allowed and treated the same as "ech". When outputting as text, the "ech" name will always be used.
This change also fixes an off-by-one error in ldns_rdf2buffer_str_svcparams() that causes it to fail to emit the final parameter for a SVCB record if it was one that does not have a value (such as "no-default-alpn"). For example, a record like this previously failed to emit "key10000" at the end -
svcb-service.nlnetlabs.nl. 3600 IN SVCB 1 test.com. alpn=h2,h3 port=1234 key10000
The latest RFC draft for SVCB and HTTPS records (https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-https-08.html) renames the "echconfig" parameter key to "ech". This proposed change implements that renaming. For backwards compatibility of text parsing, the "echconfig" parameter name will still be allowed and treated the same as "ech". When outputting as text, the "ech" name will always be used.
This change also fixes an off-by-one error in ldns_rdf2buffer_str_svcparams() that causes it to fail to emit the final parameter for a SVCB record if it was one that does not have a value (such as "no-default-alpn"). For example, a record like this previously failed to emit "key10000" at the end -
svcb-service.nlnetlabs.nl. 3600 IN SVCB 1 test.com. alpn=h2,h3 port=1234 key10000