Minutes interim-2024-iesg-24: Tue 15:00
minutes-interim-2024-iesg-24-202409171500-00

IETF 121 BOF Coordination Call
2024-09-17, updated 2024-09-26

Reported by: Liz Flynn, IETF Secretariat

Additional reference materials available in the datatracker
(https://datatracker.ietf.org/doc/bof-requests)

PRESENT:

-  Matthew Bocci  
-  Deb Cooley 
-  Roman Danyliw 
-  Dhruv Dhody
-  Liz Flynn
-  Wes Hardaker
-  Mahesh Jethanandani 
-  Erik Kline 
-  Suresh Krishnan
-  Mirja Kühlewind
-  Murray Kucherawy 
-  Cindy Morgan 
-  Francesca Palombini 
-  Tommy Pauly 
-  Colin Perkins
-  Alvaro Retana
-  Zaheduzzaman (Zahed) Sarker 
-  David Schinazi 
-  John Scudder 
-  Orie Steele 
-  Éric Vyncke 
-  Greg Wood
-  Paul Wouters 
-  Qin Wu


REGRETS:

-  Alissa Cooper
-  Jim Guichard 
-  Cullen Jennings
-  Warren Kumari 
-  Gunter Van de Velde 
-  Christopher Wood


1. Securely COmmunicating NEtwork PROperties (SCONEPRO)  
   Area: WIT
   Responsible AD: Zahed Sarker 

SCONEPRO is in the process of WG formation (as SCONE) and is 
expected to be approved as a WG before IETF 121. It appears on the 
BOF list as a scheduling placeholder. Should the WG not be 
approved by IETF 121, it will not hold a session at the meeting 
because this group has already had two previous BOF sessions.


2. RESTful Provisioning Protocol (RPP)
   Area: ART
   Responsible AD: Orie Steele

Roman Danyliw noted that the BOF request appeared reasonably 
scoped. Paul Wouters agreed that it seemed useful and a good 
request. Éric Vyncke had no objection but wanted to take another 
look at the conflict list and make some additions. Dhruv Dhody 
suggested that the one-hour session request be lengthened 
to two hours.

A WG-forming BOF was approved.


3. Deepspace
   Area: INT
   Responsible AD: Éric Vyncke

Éric Vyncke thought this would be a very interesting discussion 
and a well-formed BOF request. 

Zahed Sarker noted that there is some overlap with DTN which will 
make for a lively discussion at the BOF. There also may be some 
research overlap; Colin Perkins reported that there is a proposed 
research group in a similar area. Determining the boundary between 
research and engineering is a key question. 

Erik Kline noted that the proponent of this BOF has held many side 
meetings and is well organized, and there can be space for both a 
WG and RG. 

A WG-forming BOF was approved.


4. ALLDISPATCH
   Area: GEN
   Responsible AD: Roman Danyliw

The IESG has agreed to run the ALLDISPATCH experiment a third
time. It appears on the BOF list as a scheduling placeholder.


5. MODeration PrOceDures (MODPOD)
   Area: GEN
   Responsible AD: Roman Danyliw

MODPOD is in the process of WG formation and is expected to be 
approved as a WG before IETF 121. It appears on the BOF list as a 
scheduling placeholder. 


6. Digital Emblems Part Deux (DIEM)
   Area: INT
   Responsible AD: Éric Vyncke

This request is for a second BOF. Éric Vyncke reported some 
competing ideas at the first BOF and that the proponents are 
discussing creating two separate WGs out of this BOF. He is 
working with a design team to be very well prepared for the BOF. 

Orie Steele commented that much of this work is similar to work in 
other WGs and questioned a need for this group at all. Dhruv Dhody,
Suresh Krishnan, and Deb Cooley suggested that Éric send a strong 
message to the proponents that only a single WG will be entertained 
and the IESG and IAB would not support two separate WGs after this BOF. 

On 2024-09-26, Éric Vyncke reported that the proponents had 
returned with a new BOF agenda and a single proposed charter as 
requested. 

The IESG approved a second BOF for DIEM.


7. High Performance Wide Area Network (HP-WAN)
   Area: WIT
   Responsible AD: Zahed Sarker

Zahed Sarker spoke with the proponents and advised them to narrow 
down the focus and be more specific about what they want to 
achieve with a non-WG forming BOF. The subject could be considered 
either transport or routing related.

Matthew Bocci agreed that the request seemed a bit vague and 
needed more focus. 

Zahed Sarker volunteered to follow up with the proponents and 
encourage them to spend some more time developing their proposal.

On 2024-09-26, Zahed Sarker reported that the proponents revised 
their proposal to focus on transport related issues. He 
recommended approving the BOF to see if they can find community 
support for a clear outcome.

The IESG approved a non-WG forming BOF. 


8. GREEN 
   Area: OPS
   Responsible AD: Mahesh Jethanandani

GREEN is in the process of WG formation and is expected to be 
approved as a WG before IETF 121. It appears on the BOF list as a 
scheduling placeholder. 


9. SSH Maintenance (SSHM)
   Area: SEC
   Responsible AD: Deb Cooley

SSHM is in the process of WG formation and is expected to be 
approved as a WG before IETF 121. It appears on the BOF list as a 
scheduling placeholder. 


10. SW103L protocol
11. Integration of SW103K protocol with HLS protocol
12. Integration of SW103K compression decompression protocol with 
    VXLAN protocol 
13. Integrating SW103K protocol with QUIC protocol
14. Integrating SW103K with PPTP
    Area: ?
    Responsible AD: ?

A user named ChazahGroup submitted five separate BOF requests that 
were not fully developed and has not communicated with anyone on 
the IESG or IAB. The requests also contain some IPR that is 
incompatible with the IETF and names of some IETF participants 
listed as proponents who are not involved. 

All five requests were declined. Roman Danyliw volunteered to 
communicate with the proponent and suggest other ways to start new 
work in the IETF.


15. Non euclidean closures
    Area: ?
    Responsible AD: ?

This request appeared inapplicable and unclear as an 
IETF BOF. The request was declined and Roman Danyliw will 
communicate with the proponent.