Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / quicwg/datagram issues and pull requests

#86 - Anomaly Protection Layer

Pull Request - State: closed - Opened by kjsisco about 2 years ago - 1 comment

#86 - Anomaly Protection Layer

Pull Request - State: closed - Opened by kjsisco about 2 years ago - 1 comment

#85 - Changes from AUTH48

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#85 - Changes from AUTH48

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#84 - Would you like to change "and" to "-" here? Current (comment 4)

Issue - State: closed - Opened by LPardue almost 3 years ago - 2 comments
Labels: auth48

#84 - Would you like to change "and" to "-" here? Current (comment 4)

Issue - State: closed - Opened by LPardue almost 3 years ago - 2 comments
Labels: auth48

#83 - For clarity, may this sentence be updated as follows? Original (comment 3)

Issue - State: closed - Opened by LPardue almost 3 years ago - 2 comments
Labels: auth48

#83 - For clarity, may this sentence be updated as follows? Original (comment 3)

Issue - State: closed - Opened by LPardue almost 3 years ago - 2 comments
Labels: auth48

#82 - RFC Editor comment 2

Issue - State: closed - Opened by LPardue almost 3 years ago - 2 comments
Labels: auth48

#81 - RFC Editor comment 1

Issue - State: closed - Opened by LPardue almost 3 years ago - 1 comment
Labels: auth48

#81 - RFC Editor comment 1

Issue - State: closed - Opened by LPardue almost 3 years ago - 1 comment
Labels: auth48

#80 - Editorial nits

Pull Request - State: closed - Opened by ekinnear about 3 years ago

#80 - Editorial nits

Pull Request - State: closed - Opened by ekinnear about 3 years ago

#79 - Suggestion from Murray

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#79 - Suggestion from Murray

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#78 - Address John Scudder's AD comments

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#78 - Address John Scudder's AD comments

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#77 - Grammar nit from Murray

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#77 - Grammar nit from Murray

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#76 - Editorial suggestions from Benjamin Kaduk's IESG Evaluation

Pull Request - State: closed - Opened by kaduk about 3 years ago

#75 - Clarify 0-RTT TP

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#75 - Clarify 0-RTT TP

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#74 - Clarify fingerprinting security consideration

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#73 - Include "About this draft" information in the markdown

Pull Request - State: closed - Opened by martinthomson about 3 years ago - 2 comments

#72 - Discussion venue

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#72 - Discussion venue

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#71 - Replace with Discussion Venue

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#71 - Replace with Discussion Venue

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#70 - Explain VLI demux rationale

Pull Request - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#70 - Explain VLI demux rationale

Pull Request - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#69 - Explain 0-RTT/1-RTT requirement

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#69 - Explain 0-RTT/1-RTT requirement

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#68 - Bandwidth distribution to media and non-media traffic - applicablity statements

Issue - State: closed - Opened by zaheduzzaman about 3 years ago - 5 comments

#68 - Bandwidth distribution to media and non-media traffic - applicablity statements

Issue - State: closed - Opened by zaheduzzaman about 3 years ago - 5 comments

#67 - Congestion related information to the application

Issue - State: closed - Opened by zaheduzzaman about 3 years ago - 8 comments

#67 - Congestion related information to the application

Issue - State: closed - Opened by zaheduzzaman about 3 years ago - 8 comments

#65 - consequence of not protecting DATAGRAM with 0-RTT or 1-RTT

Issue - State: closed - Opened by zaheduzzaman about 3 years ago - 1 comment

#64 - What happens if an application wants to send a too large datagram?

Issue - State: closed - Opened by mirjak over 3 years ago - 7 comments
Labels: editorial

#64 - What happens if an application wants to send a too large datagram?

Issue - State: closed - Opened by mirjak over 3 years ago - 7 comments
Labels: editorial

#63 - Clarify 0-RTT handling

Issue - State: closed - Opened by mirjak over 3 years ago - 4 comments
Labels: editorial

#63 - Clarify 0-RTT handling

Issue - State: closed - Opened by mirjak over 3 years ago - 4 comments
Labels: editorial

#62 - rough in shepherd writeup

Pull Request - State: closed - Opened by LPardue over 3 years ago

#62 - rough in shepherd writeup

Pull Request - State: closed - Opened by LPardue over 3 years ago

#61 - Why do IANA considerations duplicate information from the body?

Issue - State: closed - Opened by LPardue over 3 years ago - 1 comment

#61 - Why do IANA considerations duplicate information from the body?

Issue - State: closed - Opened by LPardue over 3 years ago - 1 comment

#60 - Make IANA registrations permanent

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago - 1 comment

#60 - Make IANA registrations permanent

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago - 1 comment

#59 - State clearly the IANA registration type of TP and frame type

Issue - State: closed - Opened by LPardue over 3 years ago - 1 comment

#59 - State clearly the IANA registration type of TP and frame type

Issue - State: closed - Opened by LPardue over 3 years ago - 1 comment

#58 - Update intro about reliable/unreliable data

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#58 - Update intro about reliable/unreliable data

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#57 - grammar nit

Pull Request - State: closed - Opened by martinduke over 3 years ago - 1 comment

#57 - grammar nit

Pull Request - State: closed - Opened by martinduke over 3 years ago - 1 comment

#56 - Is reliability really stream-based?

Issue - State: closed - Opened by martinduke over 3 years ago - 4 comments

#56 - Is reliability really stream-based?

Issue - State: closed - Opened by martinduke over 3 years ago - 4 comments

#55 - Minor last call comments

Pull Request - State: closed - Opened by SpencerDawkins over 3 years ago

#55 - Minor last call comments

Pull Request - State: closed - Opened by SpencerDawkins over 3 years ago

#54 - Question about DATAGRAM frame

Issue - State: closed - Opened by wangweiwei1188 over 3 years ago - 2 comments

#54 - Question about DATAGRAM frame

Issue - State: closed - Opened by wangweiwei1188 over 3 years ago - 2 comments

#53 - Not "strongly" associated

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#53 - Not "strongly" associated

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#52 - Not "strongly" associated

Issue - State: closed - Opened by tfpauly over 3 years ago - 1 comment

#52 - Not "strongly" associated

Issue - State: closed - Opened by tfpauly over 3 years ago - 1 comment

#51 - Can DATAGRAM frame belong to stream?

Issue - State: closed - Opened by wangweiwei1188 over 3 years ago - 2 comments

#49 - The

Issue - State: closed - Opened by wangweiwei1188 over 3 years ago

#49 - The

Issue - State: closed - Opened by wangweiwei1188 over 3 years ago

#48 - Clarify recommendation on datagram acknowledgements

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago

#48 - Clarify recommendation on datagram acknowledgements

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago

#47 - Question about: "not used for loss recovery"

Issue - State: closed - Opened by ddragana over 3 years ago - 5 comments

#47 - Question about: "not used for loss recovery"

Issue - State: closed - Opened by ddragana over 3 years ago - 5 comments

#46 - update frame definition format

Pull Request - State: closed - Opened by LPardue over 3 years ago

#46 - update frame definition format

Pull Request - State: closed - Opened by LPardue over 3 years ago

#45 - Datagram No Ack Frame Proposal

Pull Request - State: closed - Opened by nibanks over 3 years ago - 2 comments

#44 - Datagram No Ack TP Proposal

Pull Request - State: closed - Opened by nibanks over 3 years ago

#44 - Datagram No Ack TP Proposal

Pull Request - State: closed - Opened by nibanks over 3 years ago

#43 - Please define the frame using RFC 9000 style

Issue - State: closed - Opened by LPardue over 3 years ago - 1 comment

#42 - Allow a Sender to Control Datagram ACKs

Issue - State: closed - Opened by nibanks over 3 years ago - 42 comments

#42 - Allow a Sender to Control Datagram ACKs

Issue - State: closed - Opened by nibanks over 3 years ago - 42 comments

#41 - Is it obvious that Datagram frame can be aggregated in the same QUIC packet

Issue - State: closed - Opened by gloinul over 3 years ago - 6 comments

#41 - Is it obvious that Datagram frame can be aggregated in the same QUIC packet

Issue - State: closed - Opened by gloinul over 3 years ago - 6 comments

#40 - Acknowledge Victor

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago

#39 - Update acknowledgements

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#39 - Update acknowledgements

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#38 - Note retransmission logic difference in security considerations

Pull Request - State: closed - Opened by tfpauly over 3 years ago - 1 comment

#38 - Note retransmission logic difference in security considerations

Pull Request - State: closed - Opened by tfpauly over 3 years ago - 1 comment

#37 - Clarify scope to unreliable data only

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#36 - Rework pacing phrasing

Pull Request - State: closed - Opened by tfpauly over 3 years ago - 2 comments

#36 - Rework pacing phrasing

Pull Request - State: closed - Opened by tfpauly over 3 years ago - 2 comments

#35 - Lack of application-defined format

Issue - State: closed - Opened by MikeBishop over 3 years ago - 5 comments

#35 - Lack of application-defined format

Issue - State: closed - Opened by MikeBishop over 3 years ago - 5 comments

#34 - Editorial changes to the introduction

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#34 - Editorial changes to the introduction

Pull Request - State: closed - Opened by tfpauly over 3 years ago

#33 - Update acknowledgements section to include WG contibutors

Issue - State: closed - Opened by tfpauly over 3 years ago

#32 - Awkward phrasing of pacing requirement

Issue - State: closed - Opened by martinthomson over 3 years ago - 1 comment

#32 - Awkward phrasing of pacing requirement

Issue - State: closed - Opened by martinthomson over 3 years ago - 1 comment

#31 - Two items, and no comma

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#31 - Two items, and no comma

Pull Request - State: closed - Opened by martinthomson over 3 years ago