Drone Remote ID Protocol (drip)
IETF#112 Meeting Agenda
Co-Chairs: Daniel Migault & Mohamed Boucadair
Minute takers: Stu Card
- Note well, code of conduct logistics, and introduction 5 min
DM: -reqs soon, hoping to be pubmished by tyhe end of year
EV: lucky if end of year
DM: hope that -arch in Editor queue by end of year, please focus so we can ship it!
solution space docs also in process, soliciting cfrg feedback
- DRIP Architecture 10 min
- 2.1. draft-ietf-drip-arch: Status (Shuai)
DM sharing slides, SZ speaking
feedback primarily from authors
8 editorial notes remaining in v17
try to wrap up in 2 weeks, move author discussions to list
more complex figure: use it? - SC to provide explanatory text
Stu shared figure in question - explains the “new terms” in figure that are present. Argues that there is no “full” picture in any doc.
Andrei approves, Adam approves. Bob thinks all items are in arch but sometimes not clear in text.
Med: Agree it fits the arch. We just need to make sure in the narrative that some interfaces are not in drip scope (DAA/V2V), etc.
Sean: more simplified in -arch already and this adds more context
consensus is to include, tweak text, clarify that it is just context into which DRIP fits, some elements in figure are outside DRIP scope (subtle example from chat window: V2V is out of scope, but using DRIP to identify entities in a manner enabling initiation of V2V is not)
- 2.2. Discussion: Ready to request publication?
almost ready, all comments to be resolved in v18
- DRIP Implementations 15 min
3.1 Secure Drone Identification with Hyperledger (Andrei)
Iroha & DRIP Implementation Update
students + ~10 others making progress on code esp. crypto
use blockchain as registry & log of e.g. location updates
leverage properties of Hyperledger Iroha e.g. multisig
use smart contracts to log not just writes but also queries
SC: appears to use blockchain as Surveillance SDSP?
location updates not yet shrunk to comply w/ASTM F3411
blocks in ~30kB range
hope to begin flight tests by end of this year
3.2 Any other implementation work?
no one spoke up
- DRIP Solutions
4.1. UAS Remote ID (draft-ietf-drip-rid) (Bob) 10 min
- Reviews: iotdir/secdir/saag/cfrg
- Ready for the WGLC?
new name DRIP Entity Tag (DET) descriptive of RID app of HHIT
moving proof message formats to draft-ietf-drip-auth
tracking proposed updates to ASTM F3411
mapping to static serial number defined, primarily benefits “Broadcast Module” that FAA requires use serial number
privacy & security consideration sections reviews requested
mutual dependence among functions defined in various drafts
2 known independent implementations (SC: soon to test interop?)
RM requests WGLC
RW: can RATS and/or SUIT and/or ACE help here (for registries)? who are the right parties to relationships?
RM: looking at REGEXT
4.2. DRIP Authentication Formats (Adam) 10 min
- Pending issues
- Implementation status
- Next Steps
tracking proposed updates to ASTM F3411
Specific Authentication Method (SAM) enables external to ASTM extensions to F3411 authentication
DRIP WG will need to make request, similar to IANA request, but to Int’l Civil Aviation Organization (ICAO), for SAM codes
Forward Error Correction (FEC) also enabled by F3411 changes
time stamps a matter of debate
combination of (chain of) links + manifest (SC: or any other receiver sanity checkable signed dynamic data) enables trust
several significant work items remain
WGLC before IETF 113?
4.3. DRIP Registries (Adam) 5 min
- Ready for the Call for Adoption?
draft is an admitted mess, we need help!
do we keep definitions of attestations etc. in -arch? must be decided for -arch to proceed, not just -auth MB: keep in -arch
lots of supporting materials (e.g. fancy color pix) recently developed, could put in non-ASCII versions of draft?
do we adopt in WG?
- Open Mic & Closing 5 min
SC: Observer to Pilot private comms need now recognized by multiple US Federal agencies, but we are not quite ready to tackle in DRIP WG