Holding cell for #114 #123
Conversation
living-doc-mops-streaming-opcons.md
Outdated
|
|
||
| # Technical Events | ||
|
|
||
| - ACM Mile High Video (MHV): <https://mile-high.video/> |
There was a problem hiding this comment.
ACM is using the name "ACM Mile-High Video (MHV)" , so there is a dash between mile and high.
draft-ietf-mops-streaming-opcons.md
Outdated
| @@ -855,179 +855,11 @@ Unfortunately, as noted in {{RFC7258}}, there is no way to prevent pervasive mon | |||
|
|
|||
| # Further Reading and References {#further} | |||
|
|
|||
| Editor's note: This section is to be kept in a living document where future references, links and/or updates to the existing references will be reflected. That living document is likely to be an IETF-owned Wiki: https://tinyurl.com/streaming-opcons-reading | |||
| The MOPS working group maintains a living document containing references and further reading at this location: | |||
There was a problem hiding this comment.
The MOPS working group maintains a living document containing references and further reading at this location:
Two things here.
- I'd suggest saying "The Media Operations community" - if this is useful, it is likely to outlive the working group, and we don't need to say anything in this document about who can make changes to the living document.
- Given that we know calling something a "living document" will be an attractive nuisance in IETF Last Call, and perhaps again in IESG Evaluation, I'd suggest saying "maintains a list of references and resources for further reading at this location:",
draft-ietf-mops-streaming-opcons.md
Outdated
|
|
||
| - DASH-IF WebRTC Discussions: https://dashif.org/webRTC/ | ||
| - Overview of WebRTC: https://webrtc.org/ | ||
| Editor's note: The link above should be changed to a link to be determined during IESG discussion of how working groups should manage living documents like this one. See <https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/issues/114> for updates. |
There was a problem hiding this comment.
Same deal as in my previous point here - for
The link above should be changed to a link to be determined during IESG discussion of how working groups should manage living documents like this one.
I'd suggest
The link above might or might not be changed during IESG Evolution.
I want to make sure we aren't saying anything that could be interpreted as "this document should be held until the IESG decides what to do with living documents". That would give @acbegen a stroke, and maybe me, too.
living-doc-mops-streaming-opcons.md
Outdated
| @@ -0,0 +1,211 @@ | |||
| # Introduction | |||
|
|
|||
| This document contains links and references to resources that the MOPS working group at IETF has deemed potentially useful to operators of streaming media services or network operators for networks that carry traffic from such services. | |||
There was a problem hiding this comment.
For
This document contains links and references to resources that the MOPS working group at IETF has deemed potentially useful to operators of streaming media services or network operators for networks that carry traffic from such services.
I'd suggest
This document contains links and references to resources that the IETF Media Operations community has deemed potentially useful to operators of streaming media services or network operators for networks that carry traffic from such services.
|
This works.
These work just fine for me on chrome no 403 or 406, plain 200. |
They work for me in chrome also, but they don't work in curl or wget so the script complains about them. |
"Evolution" -> "Evaluation" 😀 Add our esteemed AD to the Acks section.
|
Looks good to me, modulo a Github Action error that we don't understand. Will merge now, so we can move forward. |
I made one change to the links, because this gets a 404:
But a web search for "SCTE-214-1" found this instead, which seems to be a new location for the same thing:
Additionally, There were 3 more links that failed check-links.sh:
All of these get something with chrome, but fail with curl. The datazoom links get a 403 and the iabtechlab gets a 406. (Changing the UA header to match chrome's made curl succeed with iabtechlab, but not the datazoom links. Didn't dig deeper yet.)
I haven't put in automation for this, but I figure it's useful to have something at least to do a quick scan.