Minutes interim-2023-ietfiana-02: Wed 15:00
minutes-interim-2023-ietfiana-02-202308091500-00

IETF-IANA group meeting
9 August 2023

Attendees:
A. Baber
A. Creamer
K. Davies
D. Dong
R. Housley
M. Kühlewind
S. Tanamal
J. Yao

I. Introductions/Welcome
       Welcomed David Dong, attended IETF 117 as his first IETF meeting, has
       been supporting Amanda and Sabrina in handling tickets

II. Review Action Items and Projects
1.    IANA Term Usage
Continues to be paused due to lower priority, but expect to pick it up as it is
part of our strategic plan. 2.    Expert Outreach Project Amanda will write
blog about outreach findings after completing phase 2 which is targeted for end
of 2023 (Phase 1: outreach to individual experts; Phase 2: outreach to expert
teams) 3.    Plenary Report Prototype Completed, changed the format of
presentation for IETF 117.

III. IANA Services Activity / Performance
Maintained 100% of processing SLAs from March through June.
How Did We Do Surveys were almost 100% satisfaction except for one negative
review on a request with delays due to the expert. IANA had escalated to the AD.

IV. Operational Activities Updates
2024 IETF-IANA Supplemental Agreement
Draft will be sent to IETF with suggested changes in the next 2 weeks

FY25 Operating Plan and Budget Priorities for FY25
High-level preliminary areas of focus were shared for discussion:
o    Registry Workflow System
o    Redesign IANA website
o    Implement changes to IANA audit processes
o    Develop FY26-FY30 Plan

SAC113 – Private use TLD
First public comment proceeding, which reviewed the proposed process, was
conducted. Board Technical Committee review and approved moving forward with
execution. Next step is for the full ICANN Board to review and approve,
expected to happen on 10 September.

Execution will involve IANA identifying and reviewing candidate strings, and
then conduct a second public comment proceeding. Meaningfulness assessment will
be made in 6 UN languages (relying on ICANN’s language expertise) and will
reach out to community groups if novel issues arise, as needed. IANA estimates
its evaluation would be approximately 6 weeks. Should have assessment completed
in time for IETF 118 and ICANN 78 later in the year.

IETF asked for a pre-notification about string IANA selects to provide early
feedback if there are concerns.

V. Topics for Discussion
1.    Registry Workflow System
Mirja: Questions on timeline for system and website
Kim:  Both the workflow system and website are multi-year projects working in
phases. Don’t have a long-term roadmap but are seeking to develop longer term
prioritization. 1st phase of workflow system launched for Private Enterprise
Numbers in 2022, next phase should begin toward the end of year. Have brought
on a dedicated product manager, also added a second project manager. Always
looking for IETF feedback about identification and prioritization of features,
and other areas of improvement.

Mirja: Are you planning tighter integrations with the Datatracker?
Kim: Do see further integrations, conceptually IANA is developing a
“Datatracker” on the IANA side. Many registries are currently manual, XML-based
workflow with validations. Git repositories edited manually by staff as a
result of requests submitted as tickets. Will move to automation over time.

Mirja: Resource constrained on the datatracker side, any changes will need
advance notice so it’s on their roadmap NOTE: After meeting Kim wrote in email:
IANA’s lead developer attended IETF 117’s code sprint and met with Robert
Sparks about the API evolution between IETF and IANA, so it is actively being
discussed.

2.    Early review for documents for IETF 117
Contacted authors about 71 documents

3.    Annual engagement survey results
IANA continues to see low participation rates, working out how to evolve
approach to get meaningful input. One idea is to prompt communities with QR
codes during in-person engagements.

Mirja: Preference for conversations with IANA to discuss concerns. Such a small
population of IETF/IESG actually interfacing with IANA means the survey is
statistically not meaningful and personally she feels she always fills out the
same marks so it seems repetitive and not meaningful.  Suggested a mini-survey
on Slack. Mirja also thanked IANA for answering questions promptly when brought
up on Slack.

Action - IANA to discuss with Jay and IESG about other feedback they can
provide.

4.    IETF 117 office hours update
        15 I-D discussions, 10 process/general registry discussions

5.   Ports Outreach
Should be completed by the end of year. Most attempts to contact result in
bounces or no responses. Once complete, Sabrina will share the results with
Mirja and the IESG to determine next steps.

       6.    IETF-IANA group meeting: In-Person vs. Remote
IANA expects to always be on-site for IETF meetings. Scheduling remote meetings
hits more conflicts and leads to reduced participation.

Russ: prefers in-person for discussing SLAs
Mirja: prefers 1 in-person meeting per year, 2 or more remote. Can always hold
additional meetings if necessary. Kim: Suggest that specific topics could be
delegated by the larger group to be held with a subset as separate discussions,
so scheduling conflicts aren’t as impactful to progress

Agreement to have a minimum of 1 in-person IETF-IANA group meeting per year. 
Remaining 2 will be dependent on urgency or complexity of topics.

SUMMARY OF ACTION ITEMS:

IANA – Discuss with Jay and IESG about other feedback they can provide for
annual engagement surveys. IANA – Discuss remote meetings at the next in-person
IETF-IANA group meeting in Prague. IANA – Share stats about the port outreach
program before the next IETF meeting to allow preparations for discussions
about next steps. IANA - Update on expert outreach project; Amanda will write a
blog with findings at the end

 MEETING MINUTES - END