aboutsummaryrefslogtreecommitdiff
path: root/draft-schanzen-gns.xml
diff options
context:
space:
mode:
authorSchanzenbach, Martin <mschanzenbach@posteo.de>2019-11-10 12:41:44 +0100
committerSchanzenbach, Martin <mschanzenbach@posteo.de>2019-11-10 12:41:44 +0100
commit3e7622c5905ba4c680d6379943e54640d234ade1 (patch)
tree05f0a8438d76326dc9be9753dc238473058f881d /draft-schanzen-gns.xml
parent7e312d1ea676a0034a4ff2ae646dc074c35811da (diff)
downloadlsd0001-3e7622c5905ba4c680d6379943e54640d234ade1.tar.gz
lsd0001-3e7622c5905ba4c680d6379943e54640d234ade1.zip
update box with ref
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r--draft-schanzen-gns.xml65
1 files changed, 46 insertions, 19 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index e6de72e..317f367 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -419,6 +419,17 @@
419 <section anchor="gnsrecords_box" numbered="true" toc="default"> 419 <section anchor="gnsrecords_box" numbered="true" toc="default">
420 <name>BOX</name> 420 <name>BOX</name>
421 <t> 421 <t>
422 In GNS, every "." in a name delegates to another zone, and
423 GNS lookups are expected to return all of the required useful
424 information in one record set. This is incompatible with the
425 special labels used by DNS for SRV and TLSA records. Thus, GNS
426 defines the BOX record format to box up SRV and TLSA records and
427 include them in the record set of the label they are associated
428 with. For example, a
429 TLSA record for "_https._tcp.foo.gnu" will be stored in the record set of
430 "foo.gnu" as a BOX record with service (SVC) 443 (https) and protocol (PROTO) 6
431 (tcp) and record_type "TLSA".
432 For reference, see also <xref target="RFC2782" />
422 A BOX DATA entry has the following format: 433 A BOX DATA entry has the following format:
423 </t> 434 </t>
424 <figure anchor="figure_boxrecord"> 435 <figure anchor="figure_boxrecord">
@@ -956,16 +967,7 @@
956 <section anchor="box_processing" numbered="true" toc="default"> 967 <section anchor="box_processing" numbered="true" toc="default">
957 <name>BOX</name> 968 <name>BOX</name>
958 <t> 969 <t>
959 In GNS, every "." in a name delegates to another zone, and 970 When a BOX record is received, a GNS resolver
960 GNS lookups are expected to return all of the required useful
961 information in one record set. This is incompatible with the
962 special labels used by DNS for SRV and TLSA records. Thus, GNS
963 defines the BOX record format to box up SRV and TLSA records and
964 include them in the record set of the label they are associated
965 with. For example, a
966 TLSA record for "_https._tcp.foo.gnu" will be stored in the record set of
967 "foo.gnu" as a BOX record with service (SVC) 443 (https) and protocol (PROTO) 6
968 (tcp) and record_type "TLSA". When a BOX record is received, a GNS resolver
969 must unbox it if the name to be resolved continues with "_SERVICE._PROTO", 971 must unbox it if the name to be resolved continues with "_SERVICE._PROTO",
970 otherwise it is to be left untouched. This way, TLSA (and SRV) 972 otherwise it is to be left untouched. This way, TLSA (and SRV)
971 records do not require a separate network request, and TLSA 973 records do not require a separate network request, and TLSA
@@ -1215,22 +1217,47 @@
1215 <date year="1999" month="March"/> 1217 <date year="1999" month="March"/>
1216 </front> 1218 </front>
1217 </reference> 1219 </reference>
1220 <reference anchor="RFC2782" target="https://www.rfc-editor.org/info/rfc2782">
1221 <front>
1222 <title>
1223 A DNS RR for specifying the location of services (DNS SRV)
1224 </title>
1225 <author initials="A." surname="Gulbrandsen" fullname="A. Gulbrandsen">
1226 <organization/>
1227 </author>
1228 <author initials="P." surname="Vixie" fullname="P. Vixie">
1229 <organization/>
1230 </author>
1231 <author initials="L." surname="Esibov" fullname="L. Esibov">
1232 <organization/>
1233 </author>
1234 <date year="2000" month="February"/>
1235 <abstract>
1236 <t>
1237 This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS-TRACK]
1238 </t>
1239 </abstract>
1240 </front>
1241 <seriesInfo name="RFC" value="2782"/>
1242 <seriesInfo name="DOI" value="10.17487/RFC2782"/>
1243 </reference>
1244
1218 1245
1219 <!-- <reference anchor="ISO20022"> 1246 <!-- <reference anchor="ISO20022">
1220 <front> 1247 <front>
1221 <title>ISO 20022 Financial Services - Universal financial industry message scheme</title> 1248 <title>ISO 20022 Financial Services - Universal financial industry message scheme</title>
1222 <author> 1249 <author>
1223 <organization>International Organization for Standardization</organization> 1250 <organization>International Organization for Standardization</organization>
1224 <address> 1251 <address>
1225 <uri>http://www.iso.ch</uri> 1252 <uri>http://www.iso.ch</uri>
1226 </address> 1253 </address>
1227 </author> 1254 </author>
1228 <date month="May" year="2013"/> 1255 <date month="May" year="2013"/>
1229 </front> 1256 </front>
1230 </reference>--> 1257 </reference>-->
1231 </references> 1258 </references>
1232 <!-- Change Log 1259 <!-- Change Log
1233 v00 2017-07-23 MS Initial version 1260 v00 2017-07-23 MS Initial version
1234 --> 1261 -->
1235 </back> 1262 </back>
1236 </rfc> 1263 </rfc>