Giters
capport-wg
/
architecture
Captive Portal Architecture
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
9
Watchers:
9
Issues:
78
Forks:
8
capport-wg/architecture Issues
Revisit the Abstract
Closed
4 years ago
Comments count
1
Section 2.3: explicitly mention that the UE should only be able to check its own captivity status
Closed
4 years ago
Rephrase 3.2.1: associate rather than give
Closed
4 years ago
Remove normative MAY from section 2.1
Closed
4 years ago
Non-spoofable mechanism in section 2.1 for notifying user
Closed
4 years ago
Comments count
1
Clarify that the document is not giving a solution for UI-less devices
Closed
4 years ago
Update figure 1 to include that the UE may send a join request to the provisioning service
Closed
4 years ago
Use non-normative language in beginning of section 3.1
Closed
4 years ago
Consistent terminology for alerting/notifying via signal.
Closed
4 years ago
Mention on-path attacks in section 7.1
Closed
4 years ago
Discuss privacy in section 7
Closed
4 years ago
Mention potentially storing API response in section 2.1
Closed
4 years ago
Move guidance on API URI changing to section 2.1
Closed
4 years ago
Comments count
1
Expand section 2.2
Closed
4 years ago
Rephrase section 2 to remove 'at this time'
Closed
4 years ago
Comments count
1
Clarify scope of identifier in section 3.2.1
Closed
4 years ago
Comments count
1
Rephrase section 1 bits about forging to be positive
Closed
4 years ago
Mention using flooding attack to get info in section 7.4
Closed
4 years ago
Comments count
2
Describe the attacker in section 7.3.
Closed
4 years ago
Expand on how we authenticate the API using TLS in 7.2
Closed
4 years ago
Rephrase bit on dhcpv6 auth in section 7.1
Closed
4 years ago
Not clear how new captive portal URIs are retrieved
Closed
4 years ago
Update section 4.2 to mention user interaction
Closed
4 years ago
Clarify that section 4 is non-normative
Closed
4 years ago
Consider mentioning that the User Portal URL be unguessable
Closed
4 years ago
Comments count
2
Update section 2.6 to handle the web portal uri being optional
Closed
4 years ago
Expand Captive Portal API definition
Closed
4 years ago
Add "Captive Portal Session" to definition list
Closed
4 years ago
Review nits
Closed
4 years ago
Comments count
1
TLS for web portal/Captive Portal Server
Closed
4 years ago
Cite RFC6125 in section 2.1
Closed
4 years ago
Comments count
1
The API does not tell the enforcement device to open up
Closed
4 years ago
Do not restrict provisioning in abstract
Closed
4 years ago
Resolve once and for all MAC address identifier questions
Closed
4 years ago
Mention dual stack in the IP Address identifier discussion
Closed
4 years ago
Mention redundancy/scale of components
Closed
4 years ago
Discuss what happens to traffic inside the captive network
Closed
4 years ago
Comments count
2
Use captive portal in the abstract
Closed
4 years ago
Comments count
1
RA used, but not defined
Closed
4 years ago
Comments count
1
Consistent use of UE vs User Equipment
Closed
4 years ago
Fix up section 3.2's bullet list
Closed
4 years ago
New, consistent term for Captive Portal Server
Closed
4 years ago
Document that we are not describing how to escape captivity
Closed
4 years ago
capport/captive portal
Closed
4 years ago
Comments count
1
Confusion regarding the document's principles
Closed
4 years ago
Comments count
1
Language implying that the document is a standard
Closed
4 years ago
Comments count
1
Collocation of functions
Closed
4 years ago
Network vs. Portal
Closed
4 years ago
Is the URI mandatory?
Closed
4 years ago
Comments count
2
Consistently use URI (in place of URL)
Closed
4 years ago
Previous
Next