[tor-relays] Re: Reducing ContactInfo to the family ID level

["DTMF dont.track.my.stuff via tor-relays" <tor-relays@xxxxxxxxxxxxxxxxxxxx>]

Hello together, 

thank you for raising the idea. 

As far as i understood - defining some kind of data attributes centrally which are unique on family level is causing more struggle in usability even if there could be a slight benefit in reducing the general payload. 

////////////////////////////////////////// Single Point of Truth /////// 

I see a potential down side in the definition of the central point of truth. It could be one relay of the family. But when a single relay is holding that information and that relay disappears or is compromise, the information could be lost/altered. Are there any other location (non-torrc) where that information could be included. Maybe some functionality that could be added by the TOR-Project themselves instead of having workaround with third party specs like CIISS.

////////////////////////////////////////// Levels of relevancy /////// 

Furthermore i see different levels of relevancy. 

- FamilyID / HappyFamilyID Level 

- vServer Level (Multiple Relays) 

- Relay Fingerprint Level 

The ContactInfo (according to spec ciissversion:3) can contain also data attributes (hoster, ram, etc..) which are only relevant on Relay Fingerprint Level, or even vServer Level (multiple relays). 

That means when we will end up in a hydrid-state anyways. 

All relays would contain their specific (Relay Fingerprint Level ) data attributes in the ContactInfo field - only one relay would have have the additional information. I also like to understand which data attributes of ciissversion:3 you are specifically talking about. 

@NUSENU Is it only about these - that you want to markup centrally? 

(1) email: 

(2) url: 

(3) proof: 

Kind regards 

DTMS - dont track my stuff

_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx