Clean up the abstract a bit #322
Conversation
Read this for the first time in a while and the document has drifted slightly.
draft-ietf-quic-manageability.md
Outdated
| of QUIC-aware middleboxes, e.g. for load balancing. | ||
| on the implications of QUIC's design and wire image on network operations | ||
| involving QUIC traffic. Its intended audience is network and service | ||
| operators who rely on the use of transport-aware network functions, e.g. for |
There was a problem hiding this comment.
Not sure it is clear what is meant by "service operators"
There was a problem hiding this comment.
so maybe "network operators and network equipment vendors"...? However, not sure we really need to call this out separately...
draft-ietf-quic-manageability.md
Outdated
| on the implications of QUIC's design and wire image on network operations | ||
| involving QUIC traffic. Its intended audience is network and service | ||
| operators who rely on the use of transport-aware network functions, e.g. for | ||
| security or load balancing, as well as the implementors of those functions. |
There was a problem hiding this comment.
I don't think the addition of "as well as the implementors of those functions" is needed...
There was a problem hiding this comment.
I wanted to call out specifically that vendors in the operations space (not just operators themselves) should pay attention to this. However, if that's implied, we can cut it.
There was a problem hiding this comment.
I think we can cut this but I would have preferred to keep the examples.I don't see any problems with having e.g. in the abstract.
Co-authored-by: Martin Thomson <mt@lowentropy.net>
Read this for the first time in a while and the document has drifted slightly.