[metrics-team] How to establish identity on converted descriptors

[tl]

Cool, thanks for the feedback! I’ll use "type + published + fingerprint" then [0] and leave digest alone.

ciao,
oma


[0] like this:
    relay         type + published + fingerprint
    bridgeExtra   type + published + fingerprint
    relayExtra    type + published + fingerprint
    bridge        type + published + fingerprint
    relayConsens  type + valid-after
    bridgeStatus  type + valid-after
    relayVote     type + valid-after + identity
    tordnsel      type + downloaded
    torperf       type + start + source + filesize




> On 22.06.2016, at 12:04, Karsten Loesing <karsten at torproject.org> wrote:
> 
> Signed PGP part
> Hi Thomas,
> 
> using "type + published + fingerprint" for those four descriptor types
> sounds reasonable.  There will be edge cases of relays or bridges
> publishing more than one descriptor in a given second, but those cases
> are likely caused by a bug and those descriptors are probably not as
> useful for statistical analysis anyway.  So, while digest may be the
> best unique identifier you could find, a combination of existing
> identifiers should be sufficient in practice.
> 
> Rest looks good.
> 
> All the best,
> Karsten
> 
> 
> On 21/06/16 12:38, tl wrote:
> > Hi,
> >
> > turns out the easiest way to distinguish relays, bridges and the
> > respective extra descriptors from each other is the "digest" value
> > (that so far we haven’t included in the conversion). After our
> > conversation I realized that I’m not sure if "type + published +
> > fingerprint" can't differentiate between descriptors just as good
> > as "digest"? Problem is I’m not so fond of the idea of integrating
> > the digest value just for the purpose of disambiguation. Since the
> > other descriptors will have to rely on combinations of fields for
> > disambiguation anyway couldn’t we go the same route with relays,
> > bridges and extra descriptors?
> >
> > There were other changes as well. For relay vote a combination of
> > "type", "identity" and "valid after" guarentees uniqueness. For
> > relay consensus and bridge status "type" and "valid after" is
> > sufficient. Tordnsel/ExitLists can be identified by "type" and
> > "downloaded", Torperf need a combination of "type", "source", "file
> > size" and "start".
> >
> > So the current state is:
> >
> > relay         digest  (or type + published + fingerprint ?)
> > bridgeExtra   digest  (or type + published + fingerprint ?)
> > relayExtra    digest  (or type + published + fingerprint ?) bridge
> > digest  (or type + published + fingerprint ?) relayConsens  type +
> > valid-after bridgeStatus  type + valid-after relayVote     type +
> > valid-after + identity tordnsel      type + downloaded torperf
> > type + source + filesize + start
> >
> >
> > Cheers, oma
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.torproject.org/pipermail/metrics-team/attachments/20160622/b9fd0e8b/attachment.sig>