# IntArea WG Agenda

IETF 115 - Hybrid meeting, London (UK) + Online
Wednesday, November 9th, 2022

13:00-14:30 Wednesday Session I (London local time, UTC+1)

Chairs:
Juan Carlos Zuniga (Cisco)
Wassim Haddad (Ericsson)

Scribe: Luigi Iannone


# Agenda Bashing, WG & Document Status Updates (Chairs)


## Update from IEEE on IANA Considerations and IETF Protocol and Documentation Usage, Donald Eastlake
(draft-ietf-intarea-rfc7042bis-00)

Chairs: Q&A after next presentation (because they are related)

## Current IEEE initiatives related to draft-ietf-intarea-rfc7402bis-00, Juan Carlos Zuniga 

Q&A:

Donald Eastlake: There is a joint IETF/IEEE leadership mailing list where this draft has been noticed and request people from IEEE to look at it but no comments received so far. Not sure what the path forawrd is, if we need a formal liason.

Paul Cogdon (task group chair 802.1): Next week we will have the 802 plenary and we have in the agenda to review this document. Expert review would be welcome. We will discuss if a liaison is needed, and if so we will kick it off from the IEEE side.

Suresh Krishnan: RFC7042 has no guidance on how to request an ethertype. I can show you how we did it but some form of guidance on how to go to ask for a IEEE number would be helpful.

Donald Eastlake: You need IESG clearance. Any WG chair can go through the process. The IESG belief was that one cleared IANA was applying for it, but since I am the expert I can say that actually the WG chair applied for it. The process is not used that often that is why is not up to date. We definitely can add text to clarify.

Suresh Krishnan: You can do it by yourself and pay the fee. But an official process would be welcome.

Rob Wilson: The liason has a meeting with them once every four months. It's like once before each meeting. Email Russ and Dorothy and ask them just to track this as an issue. 

Juan Carlos Zuniga: It is already tracked. Donald and myself are expert and can help. We hope to simplify the process in the future, and as a stretch goal, also simplify and harmonize the IEEE registry and IANA IEEE numbers pages.


## Internet Protocol Number for SCHC, Robert Moskowitz
draft-ietf-intarea-schc-ip-protocol-number-00

Q&A

Éric Vyncke: No hat. No problem on the protocol number with routers.

Éric Vyncke: As AD. This I-D has been adopted to have a protocol number, so a change of goals requires a new adoption call. Other requests make sense but UDP port may be in transport.

David Black: You better define the UDP port so to have everything in one place. And as transport person, I am happy to help.

Robert Moskowitz: If we want everything in one place I can do the UDP port request.

Juan Carlos Zuniga: We might need to coordinate with transport area. But make sense to have everything in one document.

Robert Hinden: I don't think we need a new adoption call. If you go for WG LC there is a consensus call anyway.

Suresh Krishnan: Would this be SCHC all the way?

Robert Moskowitz: SCHC all the way.

Suresh Krishnan: But it should be stated clearly in the document.

David Black: SCHC is an interesting protocol, so UDP port request make sense and will be routine.

Robert Moskowitz: This will help make very interesting things.


# Non-WG Documents

## IP Parcels, Fred Templin
draft-templin-intarea-parcels-18

Q&A

Éric Vyncke: As AD. Work was not adopted but wanted to give a last chance for Fred to present his work. If anybody changed is mind and wants to support this work espress yourself by end of this week.

No more questions or comments from the room.

 
##  eBPF update, Dave Thaler
Dave Thaler

Side meeting advertisement (Thursday 6-7 PM) and very short overview of what eBPF is.

Q&A

Suresh Krishnan: Need check with people on change control issues.

Dave Thaler: Yes, one of the topics of a meeting  I fixed with eBPF peolple. Not sure the IETF is the right place for this specific aspect.

Boris Khasanov (chat): Is the side meeting page?

Dave Thaler: Yes. Can send more information on the list.