capport-wg architecture issues

capport-wg / architecture

Captive Portal Architecture

Other

10 stars 8 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

bump to version 10

#163 klarose closed 4 years ago
0
fix phrasing and clean up captive networks

#162 klarose closed 4 years ago
0
Just one typo

#161 martinthomson closed 4 years ago
0
bump to version 9

#160 klarose closed 4 years ago
0
Remove mentioning of PvD in abstract section

#159 liucougar closed 4 years ago
0
replace Captive Network with Captive Portal

#158 klarose closed 4 years ago
0
add a privacy section

#157 klarose closed 4 years ago
0
add an api requirement that UE alone can request

#156 klarose closed 4 years ago
2
use consistent terminology for signalling

#155 klarose closed 4 years ago
0
Include UE joining network in figure 1

#154 klarose closed 4 years ago
0
remove normative MAY from section 2.1

#153 klarose closed 4 years ago
0
mention on path attacks in 7.1

#152 klarose closed 4 years ago
0
replace normative language in 3.1

#151 klarose closed 4 years ago
0
Revisit the Abstract

#150 dcdolson closed 4 years ago
1
Mention API response as state in UE section

#149 klarose closed 4 years ago
0
expand provisioning service section

#148 klarose closed 4 years ago
1
describe attacker in Secure APIs section

#147 klarose closed 4 years ago
0
expand tls use in section 7.2

#146 klarose closed 4 years ago
1
add user interaction to section 4.2

#145 klarose closed 4 years ago
0
Rewording the principles.

#144 dcdolson closed 4 years ago
1
rephrase section 7.1 section on secure URI

#143 klarose closed 4 years ago
0
Mention signal-flooding attack mitigation

#142 dcdolson closed 4 years ago
0
"User equipment ... MUST be given" was unclear in passive voice.

#141 dcdolson closed 4 years ago
0
make section 4 not normative

#140 klarose closed 4 years ago
0
move normative language out of 4.2

#139 klarose closed 4 years ago
1
Mention escaping captivity in api def

#138 klarose closed 4 years ago
0
define session in terminology

#137 klarose closed 4 years ago
3
update component diagram to mention optional visit

#136 klarose closed 4 years ago
0
clean up various review nits

#135 klarose closed 4 years ago
0
recommend that the user portal uri be https

#134 klarose closed 4 years ago
1
refrence rfc6125 in section 2.1

#133 klarose closed 4 years ago
0
clarify that web portal opens up access

#132 klarose closed 4 years ago
0
do not restrict provisioning protocols in abstract

#131 klarose closed 4 years ago
0
add mac address section

#130 klarose closed 4 years ago
2
mention dual stack for ip identifiers

#129 klarose closed 4 years ago
0
mention scale and redundancy

#128 klarose closed 4 years ago
0
Clarify network access when captive

#127 klarose closed 4 years ago
0
expand RA in the abstract

#126 klarose closed 4 years ago
2
expand ue to user equipment

#125 klarose closed 4 years ago
0
Remove title case from section 3.2 list

#124 klarose closed 4 years ago
0
Clarify that we are not handling UI-less devices

#123 klarose closed 4 years ago
0
replace capport with captive portal

#122 klarose closed 4 years ago
0
do not imply that the document is a standard

#121 klarose closed 4 years ago
0
mention that user portal is not mandatory

#120 klarose closed 4 years ago
0
New, consistent term of User Portal

#119 dcdolson closed 4 years ago
2
Section 2.3: explicitly mention that the UE should only be able to check its own captivity status

#118 klarose closed 4 years ago
0
Rephrase 3.2.1: associate rather than give

#117 klarose closed 4 years ago
0
Remove normative MAY from section 2.1

#116 klarose closed 4 years ago
0
Non-spoofable mechanism in section 2.1 for notifying user

#115 klarose closed 4 years ago
1
Clarify that the document is not giving a solution for UI-less devices

#114 klarose closed 4 years ago
0