Skip to content

Commit a32f489

Browse files
committed
update index page link to implementations
1 parent baf323b commit a32f489

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

index.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,17 @@ further in [our charter](https://datatracker.ietf.org/wg/quic/about/).
7070

7171
## Implementing QUIC
7272

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.
7475

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".
7680

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.
7884

7985
## Upcoming Meetings
8086

@@ -92,8 +98,8 @@ directly to the responsible party. The IETF does not have a formal means to reac
9298
these parties and cannot do so on your behalf. Implementers or operators often
9399
provide their own publicly-available disclosure documents that provide contact
94100
details and guidelines for reporters. The
95-
[implementations](https://github.com/quicwg/base-drafts/wiki/Implementations)
96-
wiki may include a link to such documents under the "Vulnerability reporting"
101+
[implementations and tools](https://quicwg.org/staging.quicwg.github.io/implementations.html)
102+
page may include a link to such documents under the "Vulnerability reporting"
97103
field.
98104

99105
## See Also

0 commit comments

Comments
 (0)