Audio is ok
", "time": "2026-07-23T09:31:04.000Z"}, {"author": "Ketan Talaulikar", "text": "Welcome to FANN
", "time": "2026-07-23T09:31:21.000Z"}, {"author": "Eddie Ruan", "text": "Welcome to FANN
", "time": "2026-07-23T09:31:33.000Z"}, {"author": "Adrian Farrel", "text": "Hey Eddie. Would be nice to be able to see you (if you're not in bed ;-)
", "time": "2026-07-23T09:33:34.000Z"}, {"author": "Jie Dong", "text": "hope we can have some fun here:)
", "time": "2026-07-23T09:33:47.000Z"}, {"author": "Adrian Farrel", "text": "Hello :-)
", "time": "2026-07-23T09:34:06.000Z"}, {"author": "Eddie Ruan", "text": "Hi Adrian, nice to meet you here
", "time": "2026-07-23T09:34:18.000Z"}, {"author": "Jeff Tantsura", "text": "Hey Eddie :)
", "time": "2026-07-23T09:35:04.000Z"}, {"author": "Eddie Ruan", "text": "Hi Jeff, just saw you walked in. :)
", "time": "2026-07-23T09:35:19.000Z"}, {"author": "Mike McBride", "text": "What's the purpose of the problem statement, etc not being published.
", "time": "2026-07-23T09:36:26.000Z"}, {"author": "Alia Atlas", "text": "hello
", "time": "2026-07-23T09:38:59.000Z"}, {"author": "Carlos Bernardos", "text": "@Mike the purpose is to guide the framework work, and not publishing it is just stated in the charter
", "time": "2026-07-23T09:39:01.000Z"}, {"author": "Adrian Farrel", "text": "@Mike The IESG seems to be tidal on this sort of thing. Current thinking is along the lines of \"What purpose would be served by publication?\"
", "time": "2026-07-23T09:40:05.000Z"}, {"author": "Adrian Farrel", "text": "My advice. Work on the doc as though it was going to be an RFC. When it is ready, talk to the AD and get them to read the doc before saying yes or no
", "time": "2026-07-23T09:41:22.000Z"}, {"author": "Mike McBride", "text": "Thanks will do. If problem/gap/requirement documents are typically not published I'll leave it alone.
", "time": "2026-07-23T09:42:15.000Z"}, {"author": "Ketan Talaulikar", "text": "The document is identified as a support document for WG decision making and guiding the framework and further work. I leave it to the WG on how much time to spend on polishing it and when to switch focus on the framework.
", "time": "2026-07-23T09:47:09.000Z"}, {"author": "Jeffrey Haas", "text": "It's a bit peculiar that the criticism of BFD's time is less about what the protocol can carry (it carries timers in microseconds), and more about what implementations have chosen to do for scale. Different applications might push the core protocol faster.
", "time": "2026-07-23T09:47:39.000Z"}, {"author": "Carlos Bernardos", "text": "For online note taking this is the notepad: https://notes.ietf.org/notes-ietf-126-fann
", "time": "2026-07-23T09:47:50.000Z"}, {"author": "Ketan Talaulikar", "text": "There is recognition that this is a fast moving area in the industry.
", "time": "2026-07-23T09:48:05.000Z"}, {"author": "Jeffrey Haas", "text": "Much of the recognition is there is a great deal of sticky pasta being thrown rapidly at the wall to see what clings to it.
", "time": "2026-07-23T09:48:47.000Z"}, {"author": "Jeffrey Haas", "text": "@meetecho The FANN room mics are running very quiet.
", "time": "2026-07-23T09:54:57.000Z"}, {"author": "Lorenzo Miniero", "text": "@Jeffrey Haas do you mean for local or remote attendees?
", "time": "2026-07-23T09:55:33.000Z"}, {"author": "Jeffrey Haas", "text": "locally. Remote may be fine because I'm having to read the AI transcripts because I can't hear the speakers.
", "time": "2026-07-23T09:56:01.000Z"}, {"author": "Lorenzo Miniero", "text": "Ack, I'll let the AV team know
", "time": "2026-07-23T09:56:18.000Z"}, {"author": "Carolina Caeiro", "text": "guys, I have a question on what document will establish the type of information of Fast Network Notifications, would this be established by the problem statement? Requirements doc further down?
", "time": "2026-07-23T09:59:54.000Z"}, {"author": "Carlos Bernardos", "text": "the ps document should shed the light on what is needed (based on the gap analysis) and then the framework define and specify that
", "time": "2026-07-23T10:01:42.000Z"}, {"author": "Carolina Caeiro", "text": "thanks Carlos, question for Jie, can you clarify what you mean by \"Fine-grained network status information\"? What would this entail and how this is limited to link failures/ signal degradation ?
", "time": "2026-07-23T10:09:25.000Z"}, {"author": "Joel Halpern", "text": "I note that pfc has an explicit lifetime, which could easily be shorter than the latency across the wide area network. Is there an expectation that this propagation takes that into account?
", "time": "2026-07-23T10:15:08.000Z"}, {"author": "Mike McBride", "text": "@Caroline: Look at section 4.1: \"This can include quantifiable network metrics like link utilization, queue length, level of congestion, link or node delay, jitter, packet loss, etc.
", "time": "2026-07-23T10:15:42.000Z"}, {"author": "Jie Dong", "text": "@Carolina Caeiro as Mike replied, fine-grained network status information can be quantifiable information about network status such as link utilization, link degradation, level of congestion or queue buildup information
", "time": "2026-07-23T10:21:53.000Z"}, {"author": "Carolina Caeiro", "text": "thank you both -- looking at the draft now
", "time": "2026-07-23T10:22:43.000Z"}, {"author": "Adrian Farrel", "text": "@Joel. Important question, but akin to interflap or bandwidth variance in TE. I think trigger thresholds and damping will be critical
", "time": "2026-07-23T10:23:24.000Z"}, {"author": "Joel Halpern", "text": "@Adrian I am concerned because the PFC generation is structured around assumptions about network topology, and thus it seems important in trying to propagate such information to recognize the differences in cases and explain how to deal with them. For our existing IP TE solutions we recognize the inherent latency of the responses in the design of the system.
", "time": "2026-07-23T10:25:12.000Z"}, {"author": "Jie Dong", "text": "Regarding the scope of recipients, my understanding is the major target is the network nodes which are in the traffic forwarding path and can take actions in the network layer, delivering the notification to hosts would need coordination with the transport area WGs.
", "time": "2026-07-23T10:26:38.000Z"}]