You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.md
+11-5Lines changed: 11 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -70,11 +70,17 @@ further in [our charter](https://datatracker.ietf.org/wg/quic/about/).
70
70
71
71
## Implementing QUIC
72
72
73
-
There are a range of [implementations](https://github.com/quicwg/base-drafts/wiki/Implementations). Some focus on providing features of the core protocol, while some also include support for in-progress extensions.
73
+
There are a range of [implementations and tools](https://quicwg.org/staging.quicwg.github.io/implementations.html),
74
+
with a range of support for features of the core protocol and extensions.
74
75
75
-
Implementers should join the [quicdev Slack](https://quicdev.slack.com/) to coordinate testing; contact the [WG chairs](mailto:quic-chairs@ietf.org) for an invitation. Note that discussions on Slack are considered IETF contributions under "Note Well".
76
+
Implementers should join the [quicdev Slack](https://quicdev.slack.com/) to
77
+
coordinate testing; contact the [WG chairs](mailto:quic-chairs@ietf.org) for an
78
+
invitation. Note that discussions on Slack are considered IETF contributions
79
+
under "Note Well".
76
80
77
-
[Automated, continuous interop testing](https://interop.seemann.io/) is performed for participating QUIC implementations. Implementers are encouraged to join this effort by making [compatible Docker images](https://github.com/marten-seemann/quic-interop-runner#building-a-quic-endpoint) of their implementations available.
81
+
[Automated, continuous interop testing](https://interop.seemann.io/) is
82
+
performed for participating QUIC implementations. Implementers are encouraged to
83
+
join this effort by making [compatible Docker images](https://github.com/marten-seemann/quic-interop-runner#building-a-quic-endpoint) of their implementations available.
78
84
79
85
## Upcoming Meetings
80
86
@@ -92,8 +98,8 @@ directly to the responsible party. The IETF does not have a formal means to reac
92
98
these parties and cannot do so on your behalf. Implementers or operators often
93
99
provide their own publicly-available disclosure documents that provide contact
0 commit comments