commit 5a73d0b006bd2f2921632d2fb17648f7e9c7ebcc parent 8bc7b1d226cfc538060bc0348b6e15c5f277cd51 Author: Christian Grothoff <christian@grothoff.org> Date: Fri, 30 Jun 2023 18:05:59 +0200 try to be more clear in overview Diffstat:
| M | draft-schanzen-gns.xml | | | 24 | +++++++++++++----------- |
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml @@ -332,20 +332,22 @@ <li> Memorable petnames for zones: Users can configure local, human-readable references to zones. - Such petnames serve as zTLD monikers in order to support - human-readable domain names. - The petnames may also be published in order to delegate namespaces - of zones. + Such petnames serve as zTLD monikers which provide + convenient names for zones to the local operator. + The petnames may also be published as suggestions for other + users searching for good label to use when referencing the + respective zone. </li> <li> A secure mapping from names to records: - GNS allows zone owners to map petnames to resource records or to - delegate authority of the petname to other zones and publish this - information. - The mappings are signed and encrypted using keys derived from local - labels. - When names are resolved, resource records including delegations can - be verified by the implementation. + GNS allows zone owners to map labels to resource records or to + delegate authority of names below a label to other zones. + Zone owners MAY choose to publish this information to make it + available to other users. + To publishing mappings, mappings MUST be signed and encrypted + using keys derived from the respective label. + When names are resolved, signatures on resource records + including delegations MUST be verified by the implementation. </li> </ol> <t>