# IETF 109 DRIP 
Wednesday, November 18, 2020 (+07)


[meetecho](https://meetings.conf.meetecho.com/ietf109/?group=drip&short=&item=1)
[codim](https://codimd.ietf.org/notes-ietf-109-drip)
[session]() 
[jabber] https://www.ietf.org/jabber/logs/drip/2020-11-18.html

## Agenda

1. Note well, logistics, and introduction 5 min
2. Architecture   15 min
* draft-ietf-drip-arch Shuai 
3. Solutions & Implementations
* DRIP Implementation Andrei 10 min
* Enabling UAS registration/lookup with EPP and RDAP Michael 10 min
* Attestation, Claims, Assertions Adam 5 min
* UAS Operator Privacy for RemoteID Messages Bob 10 min
  * draft-moskowitz-drip-operator-privacy
4. Closing 5 min


## Minutes
"Blue Sheet" sign-in _not_ needed here as logged automatically.
False start. :-)
Bob Moskowitz voluntold to be Jabber Scribe.
Focus today is architecture.
Requirements draft has passed WGLC & gone to AD.
Architecture draft is hoped to follow by end of 2020.
Liaison statement received from ITU-T on UAS & IMT-2020;
sent out to DRIP mailing list.
Jim Reid: How shall we coord response to ITU-T?
Eric Vyncke: Response to be written by chair based on WG consensus.
Sean Turner: Has done this before; LOE discretionary but must be timely.

Shuai presented Architecture update:
 - started using Github;
 - addressing comments in progress;
 - 8 DRIP drafts exist (most still individual not WG);
 - focusing on HHIT based solution approach;
 - laying out relationships among entities;
 - trying to make draft self-contained;
 - correcting informational language;
 - safety vs security still ambiguous;
 - many clarifications still needed;
 - solicited inputs;
 - new version -06 ETA 2 weeks;
 - suggested deferring further review until -06 released.

Andrei presented open source implementation progress:
 - several students;
 - OpenHIP, OpenDroneID;
 - new crypto, new ORCHIDs, HHITs;
 - testing w/CORE -- new HIPv2 BEX works;
 - RPi sender, Android receiver;
 - WiFi NAN challenging due to vendor restricted APIs;
 - switched to Bluetooth for now, but multi beacon types;
 - BT4 range disappointing;
 - full prototype by end of 2020;
 - new related projects planned for spring term.


Stu presented interactions outside IETF:
 - Lots of stuff beyond writing drafts
 - ASTM will wait for FAA final rule
 - ASTM is friendly but all mods in backlog
 - Lots of work at ICAO
 - Lots of FAA interaction
 - US agencies are waiting for FAA rule
 - Disruption in FAA rules switching from Nrid to Bcast
 - UPP2 big demo to FAA
 - Range tests for broadcast done on side
 - FAA is contradicting itself
 - Slides excerpted from briefs to US agencies
 - Lots of big stuff to move on to

Adam presented Claims etc.:
 - substantial rewrite in progress;
 - terminology needs to be nailed down;
 - ladder is claim, assertaton, attestation, certificate;
 - we could insist certs must be from Trusted Third Parties;
 - (MUCH discussion of all this in chat!!!)
     - Claims == predicates?
     - X is unique claim is weak and not right term (Jonathan)
 - prior scheme changing to mitigate replay attacks;
 - related to other drafts from Adam and Bob;
 - solicited help w/term for what UA sends to prove registration.
     - Attestation?
     - Jonathan says Cert Pack
Jonathan - uniqueness cannot be proven.

Bob presented Operator Privacy update:
 - private from whom drives design;
 - can base crypto on UAS-USS relationship;
 - specific candidate cipher schemes justified;
 - encryption is conditional on USS connectivity & approval;
 - satisfies Requirements PRIV-1 & PRIV-2;
 - requesting WG adoption.

Chairs adjourned meeting at 15:32 ICT.