[tor-commits] [torspec/master] 326-tor-relay-well-known-uri-rfc8615.md: use more generic wording

[nickm@xxxxxxxxxxxxxx]

commit 4ca9f7a9d1e09dc0c88617a9bd81c48fb37e552a
Author: nusenu <360-nusenu@xxxxxxxxxxxxxxxxxxxxx>
Date:   Sat Oct 10 14:40:06 2020 +0000

    326-tor-relay-well-known-uri-rfc8615.md: use more generic wording
    
    The operatorurl field got renamed to 'url' in
    https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/
    This motivated this change, so we do not have to change prop 326
    everything the referenced spec is updated.
---
 proposals/326-tor-relay-well-known-uri-rfc8615.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/proposals/326-tor-relay-well-known-uri-rfc8615.md b/proposals/326-tor-relay-well-known-uri-rfc8615.md
index cd7f074..a741e1c 100644
--- a/proposals/326-tor-relay-well-known-uri-rfc8615.md
+++ b/proposals/326-tor-relay-well-known-uri-rfc8615.md
@@ -10,8 +10,7 @@ Status: Open
 
 This is a specification for a well-known [registry](https://www.iana.org/assignments/well-known-uris/) entry according to [RFC8615](https://tools.ietf.org/html/rfc8615).
 
-This resource identifier is used for the the verification of [Tor](https://www.torproject.org/) relay contact information 
-(more specifically the [operatorurl](https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/#operatorurl)).
+This resource identifier can be used for serving and finding proofs related to [Tor](https://www.torproject.org/) relay contact information.
 It can also be used for autodiscovery of Tor relays run by a given entity, if the entity domain is known.
 It solves the issue that Tor relay contact information is an unidirectional and unverified claim by nature.
 This well-known URI aims to allow the verification of the unidirectional claim.
@@ -23,7 +22,7 @@ organization by pointing to its website: Tor relay contact information field ->
 * The "tor-relay" URI allows for the verification of that claim by fetching the files containing Tor relay ID(s) under the specified URI, 
 because attackers can not easily place these files at the given location.
 
-* By publishing Tor relay IDs under this URI the website operator claims to operate these relays.
+* By publishing Tor relay IDs under this URI the website operator claims to be the responsible entity for these Tor relays.
 The verification of listed Tor relay IDs only succeeds if the claim can be verified bidirectionally (website -> relay and relay -> website).
 
 * This URI is not related to Tor bridges or Tor onion services.
@@ -62,7 +61,7 @@ Tor Project Development Mailing List <tor-dev@xxxxxxxxxxxxxxxxxxxx>
 
 * [https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt](https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt)
 * [https://gitweb.torproject.org/torspec.git/tree/cert-spec.txt](https://gitweb.torproject.org/torspec.git/tree/cert-spec.txt)
-* [https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/#operatorurl](https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/#operatorurl)
+* [https://nusenu.github.io/ContactInfo-Information-Sharing-Specification](https://nusenu.github.io/ContactInfo-Information-Sharing-Specification)
 * [RFC8615](https://tools.ietf.org/html/rfc8615)
 
 



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits