Skip to main content
  • Towards a net zero IETF

    Introducing a new project to measure and potentially offset IETF carbon emissions so that the IETF could potentially reach the level of a net zero emitter.

    • Jay DaleyIETF Executive Director
    6 May 2022
  • IETF 113 post-meeting survey

    The results from our IETF 113 post-meeting survey are now available on a web-based interactive dashboard. This commentary highlights where changes we have made based on feedback have been a success, and areas we still need to work on.

    • Jay DaleyIETF Executive Director
    2 May 2022
  • IETF 113 Hackathon – Back in person!

    The IETF 113 Hackathon held 19-20 March 2022 in Vienna and online marked the return to in-person collaboration on running code related to Internet standards.

    • Charles EckelIETF Hackathon Co-chair
    19 Apr 2022
  • IETF Datatracker updates and service outages planned

    Two updates in the coming weeks will significantly revise the look of the IETF Datatracker and, after a short outage on 25 April 2022, upgrade the hardware for most IETF services.

    • Robert SparksIETF Tools Project Manager
    13 Apr 2022
  • New Independent Submissions Editor looks for interoperability, continuous improvement

    Eliot Lear, a long-time Internet Engineering Task Force participant and engineer for Cisco Systems, was recently appointed independent submissions editor by the Internet Architecture Board (IAB).

    • Grant GrossIETF Blog Reporter
    31 Mar 2022

Filter by topic and date

Filter by topic and date

Birds of a Feather at IETF 109

  • Alissa CooperIETF Chair

21 Oct 2020

Two proposals for early-stage discussion were made for IETF 109.

IETF 109 Birds of a Feather


Update as of 2020-11-04:

The MADINAS BoF is now scheduled for 0500 UTC on 18 Wednesday. (Check out the IETF 109 Agenda for details.)

Based on further discussion:, conversation about the APN topic will be continued at an upcoming virtual interim meeting of the DNSOP Working Group to be scheduled soon.


Before each IETF meeting, the Internet Engineering Steering Group (IESG) collects proposals for Birds of a Feather (BOF) sessions. These sessions are designed to help determine the path for new work in the IETF, to generate discussion about a topic within the IETF community, and to determine whether there is interest in working on the topic within the IETF.

The IESG approved two BOFs for scheduling at IETF 109, pending further refinements to the BOF proposals: MADINAS and APN.

MAC Address Device Identification for Network and Application Services (MADINAS)

MADINAS aims to discuss issues related to service continuity in the presence of MAC address randomization. Many network functions rely on MAC addresses, including LAN forwarding policy, captive portals, sticky DHCP IP assignments, static NAT policy, and MAC address ACLs for blocking malicious or unwanted devices. With the advent of MAC address randomization in major operating systems and its unintended and likely unforeseen impacts to the network, questions have arisen about how to support continuity within these kinds of services. 

The BOF proposal is still under definition and will go forward if the current proposal is clarified. The BoF will explore how the network community (OS vendors, device manufacturers, application developers) can work together to solve the needs of end users (including their privacy). In some cases a greater awareness by Network and Application Services to current MAC address usage may be enough. For other cases, a new solution may need to be developed and standardized to reach the desired outcome.

Application-Aware Networking (APN)

APN is focused on developing mechanisms to convey user-, application-, and service-level requirements at the network layer. It is motivated by a desire to give operators fine-grained information they can use to optimize application performance on their networks.

The BOF proposal and supporting drafts list numerous use cases for network-layer application awareness, including network slicing, deterministic networking, service function chaining, SLA guarantees, and network measurement. Given this breadth of scope, it is difficult to analyze the implications of what is being proposed vis a vis security and threat modeling, user and application control, and consumption of APN information by network intermediaries. If the scope of the proposal can be sufficiently narrowed to allow for this kind of analysis, this BOF will go forward at IETF 109.

The responsible area directors and Internet Architecture Board BOF shepherds are working with the MADINAS and APN BOF proponents to refine their proposals along the lines described above. 


Share this page