Skip to main content

Minutes interim-2022-ietfiana-02: Thu 17:30
minutes-interim-2022-ietfiana-02-202204071730-00

Meeting Minutes IETF-IANA (ietfiana) IAB ASG
Date and time 2022-04-07 17:30
Title Minutes interim-2022-ietfiana-02: Thu 17:30
State Active
Other versions plain text
Last updated 2022-09-20

minutes-interim-2022-ietfiana-02-202204071730-00
Summary of Meeting Minutes 
Thursday, April 7, 2022
Virtual interim meeting 
1730 UTC
 
Attendees:
 
Jari Arkko
Russ Housley
Lars Eggert
Mirja Kuehlewind
Kim Davies
Amy Creamer
Sabrina Tanamal
Michelle Thangtamsatid
Amanda Baber
 
Regrets:
Jay Daley is unable to attend.
 
PENDING ACTION ITEMS
 
1.    18 Nov 2019: IANA term usage (K. Davies, in progress)
	K. Davies: Objective is just to simplify/rationalize use of 
	terms like "IANA" and "PTI."
	L. Eggert: Trust leaned strongly in the direction of wanting to 
	be their own LLC. You probably want to look into the objective 
	risks from an ICANN/IANA perspective.
2.    26 Aug 2021: Complete the licensing issue (K. Davies, completed)
3.    10 Feb 2022: Including mailing lists in cc during AUTH48 (K. 
	Davies, completed)
 
TOPICS
 
• IANA Services Activity/Performance
  ○ November – February [error in slides; stats are Nov 21 – Jan 22] 
    with 100 percent processing times
  ○ Fiscal Year 2024 (FY24) Operating Plan and Budget
  ○ Initial engagement efforts for FY24 priorities is scheduled in May
  ○ Public Webinars will take place in July with invites sent to IETF 
    community and leadership
 
• Annual IANA Engagement Survey
2021 Survey saw an increase in IETF leadership participation. Survey 
looks at six facets -- credibility, transparency, attentiveness, 
fairness, timeliness, and accountability -- across naming, numbers, and 
protocol parameters. IANA usually ranks fairly well (4 or higher out of 
5) across the six concepts. Our ratings are consistently highest for the 
protocol parameter function.
 
• Operational Activities Updates
 
- Nameservers for the Address and Routing Parameter Area
  ○ (“arpa”) Domain approved for publication: 
    https://datatracker.ietf.org/doc/draft-iab-arpa-authoritative-servers/
  ○ Implementation plans have been discussed with Verisign and is 
    scheduled for late April
 
- .INT Document
  ○ https://datatracker.ietf.org/doc/draft-davies-int-historic/
  ○ Currently in IETF Last Call

K. Davies: You would have seen that John Klensin had a substantial 
response, especially to the notion that RFC 1591 was appropriate to 
amend, given its status and legacy and the views others have. I think we 
should consider this carefully. Some of his review also speaks to IETF 
process questions. I'll respond to him about IANA-specific issues.

L. Eggert: There's a low-intensity ongoing discussion where a small part 
of the community questions whether the IETF/IESG can do anything with 
the status of RFCs in the legacy stream, suggesting they're out of 
control of the IETF. Although pragmatically, who else would be able to 
do this? We're hitting this with other documents as well. You can tell 
Warren that this aspect needs to be figured out on the IESG side.
 
-Licensing IANA Registries:
  ○ The statement has been posted at 
    https://www.iana.org/help/licensing-terms
  ○ Added the link to the protocol registries
 
- Registry workflow system
  ○ Estimated completion of development July 2022 for PEN application
 
- TZ Database: Editorial Dispute
  ○ A pseudo-fork has been created by Colebourne, but the fork merely 
    maps deltas from IANA source. Some downstream projects signaled they 
    will use the fork.
  ○ IANA is continuing to monitor the situation

K. Davies: The dispute is about an editorial philosophy concerning 
historical data. The IESG-designated expert and backup both take a 
minimalist view and have been stripping out some things they consider 
questionable. Others say not to take out old data unless it's 
demonstrably wrong. This has been flaring up on/off for years. This had 
been quiet in recent months, but just recently the main advocate for a 
maximalist approach has created a fork that has the deltas that can then 
be applied to the TZDB. Better than a full-blown fork. There are one or 
two downstream projects, possibly including FreeBSD, that have indicated 
that they're going to follow the fork. It appears that there is room for 
compromise, perhaps where the TZDB could include the fork, but that's my 
observation, and I'm not sure we have a role to play. We continue to 
monitor.

R. Housley: Have you offered to host both files?

K. Davies: I have not. We've tried not to step into editorial disputes. 
But if that's a useful step, we can take it under consideration. But we 
don't want to be seen as taking sides.

R. Housley: I don't think the IESG want to step in either. It just seems 
less forky if they're in the same place.

K. Davies: Paul Eggert controls the whole repository, rather than giving 
us edits to apply. Two repos could sit with IANA.
 
- ftp.iana.org
  ○ Internal discussion prompted by the IETF turning down their FTP 
    service
  ○ Plan on supporting FTP service for the foreseeable future
 
- IETF 112 Office Hours received 14 visits which included such topics as 
  discussion about I-Ds due to early reviews
 
• Upcoming Meeting Schedule
                ○ IESG/IAB Retreat

- Proposed IETF/IANA Meeting schedule:
  ○ In-Person or Virtual July 2022 (Philadelphia) – M. Kuehlewind asked 
    IANA to give an update to the IAB
  ○ In-Person or Virtual November 2022 (London)
 
NEW ACTION ITEMS: 
None.