Minutes interim-2022-ietfiana-01: Thu 19:00
minutes-interim-2022-ietfiana-01-202202101900-00

Summary of Meeting Minutes 
Thursday, February 10, 2022
Virtual interim meeting 
1900 UTC
 
Attendees: 
 
Mirja Kühlewind, IAB Chair
Russ Housley, IETF-IANA Group Co-Lead
Jari Arkko, IETF-IANA Group
Jay Daley, IETF LLC Executive Director
Lars Eggert, IETF Chair
Roman Danyliw, IESG Representative
Kim Davies, VP, IANA Services, ICANN, President, Public Technical Identifiers (PTI)
Amy Creamer, Director of Operations
Amanda Baber, IANA Operations Manager
Sabrina Tanamal, Lead IANA Services Specialist 
Michelle Thangtamsatid, IANA Services Specialist
 
1. Introductions and Welcome

Discussion: 

K. Davies expressed that this discussion would be a good opportunity to 
talk about recalibrating expectations and tailoring how we interact with 
each other moving forward and our desires for coverage for individuals, 
etc. 
 
L. Eggert explained that the IETF has had a long-standing assumption 
that IANA has a person who's a liaison to the IESG and IAB, and that's 
even written into some RFCs.  Michelle Cotton’s departure was unexpected 
and there is concern about IANA role changes that were not previously 
vetted with the IETF.  However, how IANA carries out its functions -  
processing/completing registrations, that has been working great.
 
2. IANA Services Team Structure: 

Discussion:

K. Davies shared an overview of the team support.
 
Amy Creamer is the Director of Operations; operations include all of the 
services we provide to our core communities (IETF, Root Zone Management, 
and RIRs).

Marilia Hirano is the Director of Strategic Programs and manages our 
strategic roadmap, auditing, continuous improvement.

James Mitchell is the Technical Director who leads up the team that 
provisions our systems, software development, and KSK ceremonies. 
Manages team that also contributes as internal technical SMEs
 
Within Amy's team, Amanda Baber and Sabrina Tanamal have supported the 
IETF for many years. Michelle Thangtamsatid is ramping up her training 
to support the IETF as  well. Selina and George are primarily targeted 
towards root zone management at this time. A sixth individual is likely 
to be joining shortly as well; we'll let you know at the next meeting.
 
Previous organization: Ten years ago, we had three silos: naming, 
numbers, and an IETF support function. We adjusted that model to 
recognize that it didn't provide much opportunity for coverage or 
growth, and as the team and workload grew, we restructured. Each 
individual has their own specialties, but coverage and growth 
opportunities exist. Satisfaction with our performance demonstrates that 
this model works, and we'd like to retain it. This also allows us to 
dynamically adjust workload if there's a spike in some area. 
 
*The diagram doesn’t show the whole IANA team, which consists of roughly 
15 people. Those not shown include people who provide software 
development, audits, key ceremonies, and administrative support.
 
3. How IANA Will Support the IETF: 

Discussion:

K. Davies: 
Our objective was to remove single points of failure and provide 
coverage

A primary person (with a secondary back-up) is assigned for interactions 
with the IETF, IAB, and IESG
 
L. Eggert: 
Preference for personalized email addresses to be signed up to mailing 
lists vs. role accounts
 
M. Kühlewind: 
The primary IANA contact, besides subscribing to mailing lists, needs to 
be updated on web pages where all of the liaisons are mentioned. 

For places where we have a mailing list, meeting, and a web page, it 
should always be the same person. It's probably a good idea to send out 
an announcement to the IESG and IAB mailing lists and say that you are 
the new IANA contact person. 
 
4. IANA-IETF Communication concerns
L. Eggert: 
Concern would be to avoid this lack of communication in the future
Also reminded IANA that leadership on the IETF site changes regularly, 
so you'll have to repeat this every two years as if nobody had heard it 
before.
 
K. Davies: 
Agreement on IANA needing to be more transparent about staffing plans 
and involve the IETF  in our vision. 
 
5. AOB
L. Eggert: The IESG will send out a message to the community saying that 
we're planning to improve the transparency in communications between 
RPC/RFC Editors with authors/chairs/ADs during the AUTH48 period. 
Typically this discussion is between the RFC Editor and authors along 
with chairs and ADs in cc. The proposal was made to open this up for 
observation. We don't want to build a lot of custom tooling, so we 
landed on building a mailing list that the RFC Editor would cc on 
communications with the authors. Then people could go to the archive.

Considering something similar to the IANA registration interactions that 
are happening, but they're not archived as far as I know.

Discuss with your team if it's possible to copy a mailing list in cc 
from the ticketing system. It would be nice if this mailing list 
approach works for you too.

A written proposal will be worked out and sent out to the community.
 
K. Davies:
We just need to figure out the potential mechanics, and from our side we 
capture all of those conversations in our ticketing system, and it's not 
publicly available. If a direct party asks for it via a request, we will 
provide it. 
 
NEW ACTION ITEMS:
2022-02-10
Token: K. Davies
Action Item: Provide update at the next meeting on including mailing 
lists in cc during AUTH48.