test
", "time": "2023-11-07T08:32:30Z"}, {"author": "Ben Rosenblum", "text": "received
", "time": "2023-11-07T08:32:38Z"}, {"author": "Francesca Palombini", "text": "ok so ignore what I said: I went and re-checked the criteria for erratas (https://www.ietf.org/about/groups/iesg/statements/processing-errata-ietf-stream/ ) and according to what was said, I will mark the errata \"Verified\" :)
", "time": "2023-11-07T08:42:02Z"}, {"author": "Kevin Ma", "text": "thanx!
", "time": "2023-11-07T08:42:21Z"}, {"author": "Ben Rosenblum", "text": "Kevin, to answer your question, the current draft does not register capacity limit types as an IANA registry.
", "time": "2023-11-07T08:46:49Z"}, {"author": "Kevin Ma", "text": "got it. i will go back and review it . thanx.
", "time": "2023-11-07T08:54:11Z"}, {"author": "Glenn Goldstein", "text": "i think the FCI wrapper actually makes usage clearer.
", "time": "2023-11-07T09:02:47Z"}, {"author": "Glenn Goldstein", "text": "please go back to the slide showing all teh variables and functions
", "time": "2023-11-07T09:27:29Z"}, {"author": "Rajeev RK", "text": "Vote for extension of the charter to include this
", "time": "2023-11-07T09:29:52Z"}, {"author": "Rajeev RK", "text": "This might also be a point in the system that we can implement hooks to implement various other standards that need to go into the Request/Response flows. Think of a lightweight implementation of things like CMCD/CMSD or Tracing Standards like TraceData/ProxyStatus or even potentially upcoming standards like Streaming Media Tracing's TraceData headers.
", "time": "2023-11-07T09:37:49Z"}, {"author": "Rajeev RK", "text": "Let me fix my mic first...
", "time": "2023-11-07T09:38:49Z"}, {"author": "Sanjay Mishra", "text": "ok
", "time": "2023-11-07T09:39:09Z"}, {"author": "Rajeev RK", "text": "ok, think i've gotten it fixed
", "time": "2023-11-07T09:39:56Z"}, {"author": "Rajeev RK", "text": "Also, just to confirm, we maintain backwards compatibility with the older W3C Based ELF Format as a supported legacy format in this new standard.
", "time": "2023-11-07T09:54:13Z"}, {"author": "Kevin Ma", "text": "thanks rajeev. noted
", "time": "2023-11-07T09:55:04Z"}, {"author": "Benson Muite", "text": "Will there be a framework to enable billing for exchange of capacity or are the proposed drafts sufficient?
", "time": "2023-11-07T10:05:03Z"}, {"author": "Rajeev RK", "text": "@benson My expectation is that this will act as an underlying layer that allows for exchange of actual traffic/usage data, which in turn feeds into billing systems. However, we dont yet tackle the actual billing workflows yet, and i'm guessing that will be separate work potentially to be taken up in the future.
", "time": "2023-11-07T10:07:57Z"}, {"author": "Benson Muite", "text": "Thanks Rajeev
", "time": "2023-11-07T10:08:37Z"}, {"author": "Rajeev RK", "text": "@benson However, we are going to be discussing capabilities like custom fields, sampling, filtering and aggregation in the 2nd part of the logging work in the SVTA, which may be useful to tie in to billing systems and get things like aggregated traffic volumes by region or time period etc.
", "time": "2023-11-07T10:13:08Z"}, {"author": "Rajeev RK", "text": "Extended status and error capability as an important capability, and has been extremely useful in our existing content preposition API implementations that are in our CDN platform.
", "time": "2023-11-07T10:16:59Z"}, {"author": "Sanjay Mishra", "text": "ACK
", "time": "2023-11-07T10:17:33Z"}, {"author": "Glenn Goldstein", "text": "ambitious!
", "time": "2023-11-07T10:22:39Z"}, {"author": "Rajeev RK", "text": "Just wanted to bring up an example in response to @KevinMa -- \"Purge all 4K variant segments across all video assets in the local cache\" , wich may be difficult to do across multiple assets that my have different paths, leading to a complex regex to cover it
", "time": "2023-11-07T10:29:45Z"}, {"author": "Ben Rosenblum", "text": "Thank you!
", "time": "2023-11-07T10:30:25Z"}, {"author": "Alfonso Sil\u00f3niz", "text": "thank you all!
", "time": "2023-11-07T10:30:28Z"}]