****
               Drone Remote ID Protocol (drip)
                  IETF#113 Meeting Agenda
                         2022-03-23
         13:00-14:00 Wednesday Afternoon session I
    https://datatracker.ietf.org/meeting/113/session/drip
               WG Chairs: Daniel Migault & Mohamed Boucadair
          On-site Chairs: Jim Reid & Stephan Wenger
                 Minutes: Stuart Card
*******

Notes here summarize oral contributions to discussion, not text chat, which is logged separately.

# 1. Introduction & Logistics  (5 min)

# 2. Updates of Documents that passed WGLC & misc (5mn)
These items are reserved to major issues to be reported. If none, the slot is skipped. 
  2.1 draft-ietf-drip-arch (Shuai - skipped)
  2.2 draft-ietf-drip-rid (Bob - skipped). DRIP RID update slides are at:  
https://raw.githubusercontent.com/ietf-wg-drip/draft-ietf-drip-rid/main/slides-113-drip-drip-uas-remote-id-updates-ss1921.pdf
  2.3 ASTM F3411 Update  (Stu - summarized): Refer to the slide included in the presentation material. 

# 3. DRIP Implementations  (15 min)

3.1 Iroha & DRIP Implementation Update (Andrei except as noted)
Hyperledger based UAS tracking & partial prototype for registry, suggested to be reflected in DRIP Registries draft.
attempting Bluetooth XMT/RCV integration
Adam: some typical issues with that
Wi-Fi NaN working at short range
Wi-Fi Beacon in progress
OpenHIP being updated: mostly OpenSSL related;
NAT Traversal also worked (is it relevant to DRIP?);
formal verification being undertaken
DRIP integration to be shown in EU project demos
Daniel: How much work involved in OpenSSL update?
Andrei: Almost like writing from scratch.
Bob: HIP use here is mostly for Network RID & C2.
Stu: For ID based initiation of C2 & other apps.

3.2 Any other implementation work?
Stu & Adam: Yes, struggling for release permission.

# 4. Updates & Next Steps for Active WG documents (30 mn)
4.1. DRIP Authentication Formats          (Adam)             15 min
     (draft-ietf-drip-auth) 
     * Pending issues:
     FEC compatibility among libraries/platforms;
     resolving comments, not major issues
     * Next Steps: linguistic proofreading
     * When to be ready for the WGLC: very soon

4.2. DRIP Registries                      (Adam)             15 min
     (draft-ietf-drip-registries)
     Recently massively rewritten.
     Current registration text loosely coupled to EPP and RDAP, coupled to DNS, tightly 
     coupled to HHIT based DRIP Entity Tag (Bob's -rid draft).
     
*     * Issues, open questions, & next steps
     How much DNS, EPP, RDAP, Andrei's blockchain detail to include here?
     Bob: Moving some -rid draft text to Registries.
     Detailed registration walk-through including Z-diagrams & DNS RRs.

# 5. Open Mic & Closing (5 min)
Stu: How abstract vs detailed in these docs?
Bob: Key roll-over as specific case of this.
Adam: Some discussion needed re: federation & keys.
Bob: Slides available but no time to present today; coordinating w/IANA; feedback needed.
Adam: Preparing for physical demo/hackathon of DRIP at IETF 114 going beyond prior successful
       test of baseline ASTM interoperability.
Jim: Thanked all, closed meeting.


===
Main notes for the chat room
==
Mohamed Boucadair asked Stu if he sees any impact of the "negative" ballot on the auth I-D
          as it requires some registration governed by ASTM rules. 
Stephan Wenger asked: Regarding the ASTM normative reference: have you guys a plan how to 
        make they doc available to the IETF reviewers without charge?  It's a hiccup that has come up before
Bob Moskowitz: To get the ASTM doc, IETF will have to enter into an agreement with ASTM.  I looked
               into these 2 years ago, and did not get energy for IAB for this step.
Stephan Wenger: Liaison relationship?
Bob Moskowitz: Basically.  Yes.
Mohamed Boucadair: We included in RFC9153 a pointer to a previous version that is available
                  for free. I don't know if we need to revive the discussion how to make this available 
                 for reviewers. Some of the details were included in the doc write-up.
Stephan Wenger: OK.  sleeping dogs and all...
Éric Vyncke: As long as it is only informative, then this should be OK.
Mohamed Boucadair: It is normative for AUTH but info for RID.
Éric Vyncke: This will be a problem for a normative reference.
Éric Vyncke: Then, Med, we need to plan for it.
Mohamed Boucadair: We used to have that same concern with 9153, but let’s see if there is something we can do more.
Stephan Wenger: So, what worked in AVTCORE for a ISO/JPEG spec recently was to find a way to make the ISO spec freely available to those reviewers who request it, with the understanding that it will not be shared. Such was implemented informally.
Bob Moskowitz: We will see if we can coordinate with Andrei for remote testing.