issues
search
martinthomson
/
train-protocol
Choo Choo!
Other
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add some more words to the text on applicability
#28
martinthomson
closed
4 days ago
0
Alternative Privacy Consideration section
#27
huitema
closed
4 days ago
1
Privacy considerations
#26
huitema
opened
1 week ago
13
Privacy analysis
#25
martinthomson
closed
1 week ago
1
Attempt to explain the off path attack
#24
huitema
closed
2 weeks ago
0
Feedback options
#23
martinthomson
closed
1 week ago
0
NO need to request TRAIN
#22
martinthomson
closed
2 weeks ago
0
No need for request frame, but maybe echo frame
#21
huitema
closed
1 week ago
2
Automatic update of README.md
#20
martinthomson
closed
2 weeks ago
0
Add something important
#19
martinthomson
closed
2 weeks ago
0
Fix aasvg glitch in diagram
#18
martinthomson
closed
2 weeks ago
0
A protocol needs to support all three registries
#17
martinthomson
closed
2 weeks ago
0
Allow SCID to match the next packet
#16
martinthomson
closed
2 weeks ago
1
Pick some limits
#15
martinthomson
opened
1 month ago
0
Rate limit or rate limit over time
#14
martinthomson
opened
1 month ago
1
Source Connection ID value
#13
martinthomson
closed
2 weeks ago
4
Add Kazuho as author.
#12
kazuho
closed
1 month ago
0
Attack by malicious endpoint
#11
huitema
opened
1 month ago
6
Rework design
#10
martinthomson
closed
2 weeks ago
0
Add Christian as author.
#9
huitema
closed
1 month ago
0
the design should be QUIC-version neutral
#8
kazuho
closed
2 weeks ago
2
Move more to a single new version
#7
martinthomson
closed
1 month ago
5
shotgun thumpers
#6
huitema
closed
2 weeks ago
1
Switch from "rewriting" to "injecting"
#5
kazuho
closed
2 weeks ago
5
Jana's notes
#4
martinthomson
opened
1 month ago
0
Transport parameter and trigger version
#3
huitema
closed
1 month ago
3
Transport parameter
#2
huitema
closed
2 weeks ago
5
How do we protect from spoofed packets?
#1
huitema
opened
1 month ago
2