issues
search
mjoras
/
SCONE-PROTOCL
Repository for files related to the topic formerly known as SADCDN.
Other
9
stars
10
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
UDP 4-tuple
#124
ihlar
closed
2 months ago
0
Intention --> capable
#123
zaheduzzaman
closed
2 months ago
0
sender of packets, not originator of 5-tuple
#122
ihlar
closed
2 months ago
1
Remove hyphen
#121
ihlar
closed
2 months ago
0
reflow charter text
#120
fluffy
closed
2 months ago
1
Explicit mention of QUIC
#119
martinthomson
closed
2 months ago
0
Different signals for 5-tuple or local path
#118
ihlar
closed
2 months ago
4
quic-based solutions in scope
#117
ihlar
closed
2 months ago
1
QUIC
#116
ihlar
closed
2 months ago
0
Clarify the relationship between protocol work and API work
#115
SpencerDawkins
closed
2 months ago
0
defining the "network element" inline to provide the definition ahead of using it, uses throughput advice instead of bitrate
#114
zaheduzzaman
closed
2 months ago
0
Off-path is a non goal
#113
ihlar
closed
2 months ago
2
remove repetition in aim, open issues, and goals
#112
SpencerDawkins
closed
2 months ago
0
Repetition of same description
#111
zaheduzzaman
closed
2 months ago
0
Separate signal for throughput advice
#110
zaheduzzaman
closed
2 months ago
3
Change "application limits" to "throughput advice"
#109
mjoras
closed
3 months ago
0
Remove "conformance" language, clean up open issues.
#108
mjoras
closed
3 months ago
4
Avoid claiming that we will signal receipt and conformance
#107
dkg
closed
3 months ago
2
Application limits vs. video limits
#106
mjoras
closed
3 months ago
10
Add language around "client conformance signaling"
#105
mjoras
closed
3 months ago
0
Define network device
#104
ihlar
closed
4 months ago
0
Tighten up the definition of "network element(s)"
#103
SpencerDawkins
closed
3 months ago
14
Should we mention why it's necessary to develop a in-band protocol solution
#102
RenjieTang
closed
2 months ago
7
Remove allowable bitrate
#101
ihlar
closed
4 months ago
0
Less authoritarian language
#100
ihlar
closed
4 months ago
1
'from' network elements
#99
danwing
closed
4 months ago
0
Coordination with W3C?
#98
JonathanLennox
closed
2 months ago
14
Remove packet core example
#97
mjoras
closed
4 months ago
0
Remove redundant text
#96
ihlar
closed
4 months ago
0
(editorial) remove the bulleted list in the WG scope/focus text
#95
zaheduzzaman
closed
4 months ago
1
Clarify primary objective
#94
ihlar
closed
4 months ago
0
Initial list of topics that are out of scope
#93
SpencerDawkins
closed
4 months ago
2
Less focus on mobile
#92
ihlar
closed
4 months ago
0
Don't overly specify mobile access.
#91
mjoras
closed
4 months ago
3
Tighten scope to remove TCP, and specify video more clearly.
#90
mjoras
closed
4 months ago
0
What does available bitrate mean
#89
fluffy
closed
4 months ago
4
What's out of scope? (was: This is not congestion control)
#88
fluffy
closed
4 months ago
0
Random Qs for IETF-120 BoF
#87
jlivingood
closed
2 months ago
15
Adding EXTREMELY drafty 120 agenda
#86
SpencerDawkins
closed
4 months ago
3
Create IETF 120 BOF directory for agenda and presentations, and whatever else the chairs need
#85
SpencerDawkins
closed
4 months ago
0
Change associativity requirement.
#84
mjoras
closed
4 months ago
0
proposal to use the term "format"
#83
mirjak
closed
4 months ago
2
Add explanation of why SCONEPRO is still needed when L4S exists
#82
ihlar
closed
4 months ago
7
Merge general SCONEPRO and video streaming deliverables
#81
SpencerDawkins
closed
5 months ago
3
typo
#80
martinthomson
closed
5 months ago
0
Associativity requirement
#79
mnot
closed
4 months ago
8
Changed 'bandwidth' to 'throughput' (issue 77)
#78
Kevsy
closed
6 months ago
0
Throughput, not bandwidth
#77
Kevsy
closed
6 months ago
3
Clarify the same channel is used for opt-in and network properties
#76
SpencerDawkins
closed
6 months ago
0
Change security language and NAT/multi path language
#75
mjoras
closed
6 months ago
0
Next