Minutes IETF111: hrpc
minutes-111-hrpc-00

      Notes HRPC IETF 110

*Action points are denoted in bold, as such.*

# Welcome and introduction

Unfortunately Anriette will not be able to make it today. We will try to
schedule her for IETF 112.

We will cover the two current RG drafts: guidelines and association.

We will talk at the end about finding a co-chair for HRPC.

# Talk: Anriette Esterhuysen

        "The global Internet Governance Forum: It's history and the future"

## Discussion

(Postponed)

# Talk: Kee Jefferys

        "Identity and assembly: Creating a messaging architecture to support
        human rights"

## Discussion

Mallory: What is the difference between Session and other e2ee apps?

Kee: Session is all about not having any identifiers, which lends itself to
human rights defenders. Anonymity is first, while also providing privacy and
security.

Antoine: Install the app and private-public key pair. Then you say you can
reach me with a session ID. How easy is it to get the session ID and then know
who you are since the ID is stable over time? Non-human readable isn’t the same
as anonymous.

Kee: You can destroy and create new accounts, as many as you want.

Antoine: I understand. Documentation of the management of identity could be
improved.

Kee: We want to work on the UX for multiple session IDs in the same client.

Kee: I see in the chat people talking about Zooko’s triangle. We have in the
works the ability to map in the blockchain a human readable name to a session
ID. It removes anonymity but that might be something users want.

Mallory: Process for user feedback?

Kee: Nothing particularly innovative but we ask for feedback through Session
itself and we take GitHub for issue tracking.

Britta: There are authentication issues with anyone creating a key, because one
doesn’t know who anyone is.

Kee: Web of trust is the answer. There is no authentication so users have to
establish trust out of band.

Jeffrey: It would be nice if we had terminology for these systems such that we
don’t criticise systems for goals that they aren’t trying to achieve, like
yours that preferences anonymity over authentication.

*Terminology in encrypted messaging to identify various corners of Zooko’s
triangle, perhaps.*

# Update on drafts: Mallory Knodel

        draft-irtf-hrpc-guidelines
        draft-irtf-hrpc-association

## Discussion

Mallory: Thorough lit review, led to subquestions, which led to sub-section by
case on FAA online and IETF protocols, and finally we have conclusions.

*We will ask for last call on the list.*

Mallory: LC on the list and it’s ready to progress.

Colin: Needs to do a detailed review. Slight concern that it’s one-sided and
are there any counter arguments to be made? Tradeoffs could be clearer.

Mallory: We are trying to come down on the side of human rights, but presenting
the tradeoff, too, so that protocol engineers can make an informed decision.

Colin: Highlight what one might want to do for what reasons.

Mallory: We can give language to authors so that they can capture this in a
human rights considerations section.

Colin: Know the goals of the system and what it’s supposed to be provided.

# Update on co-chair search and outreach

## Discussion

Mallory: As the only chair and co-author on draft-association I need a document
shepherd to take forward this document.

*Need a document shepherd for draft-association.*

*Need to do additional outreach for co-chair.*