commit b865a43f13e1533c8eea8bf609c4936595d6a478 parent 5a73d0b006bd2f2921632d2fb17648f7e9c7ebcc Author: Christian Grothoff <christian@grothoff.org> Date: Fri, 30 Jun 2023 18:10:13 +0200 try to be more clear in overview Diffstat:
| M | draft-schanzen-gns.xml | | | 14 | +++++++------- |
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml @@ -362,14 +362,14 @@ example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884 </sourcecode> <t> - Now consider the petname "pet.gns.alt" for the example zone - of the name above. - The following name would point to the same record as the - globally unique name above but it is only valid locally: + Now consider the case where a user locally configured the petname + "pet.gns.alt" for the zone with the "example" record of the name + above. + The name "example.pet.gns.alt" would then point to the same record as the + globally unique name above, but name resolution would only + work on the local system where the "pet.gns.alt" petname is + configured. </t> - <sourcecode> -example.pet.gns.alt - </sourcecode> <t> The delegation of petnames and subsequent resolution of delegation builds on ideas from the Simple Distributed Security Infrastructure