Captive-Portal Identification in DHCP / RA

Captive-Portal Identification in DHCP / RA
复制标题

DHCP/RA 中的强制门户识别

DOI：
--
复制
发表时间：
2000
期刊：
影响因子：
--
通讯作者：
Erik Kline
Erik Kline
中科院分区：
--
文献类型：
--
作者：
W. Kumari;Erik Kline

文献摘要

被引文献

相似文献

在许多提供短期或临时Internet访问的环境中， (such作为咖啡店），通常在一个 强制传送模式这高度限制了客户可以做的事情 直到客户认证。本文档介绍DHCP 选项（和路由器通告（RA）扩展）通知客户端 他们在某种俘虏传送门装置的后面， 需要进行身份验证才能访问互联网。这不是一个完整的 解决客户可能遇到的所有问题， 强制门户;它被设计用于更大的解决方案。的 对强制门户进行身份验证并与强制门户进行交互的方法 超出了本文档的范围。[本文件正在 在Github上合作：https://github.com/wkumari/draft-ekwk- capport-rfc7710bis.文档的最新版本，打开 问题等都应该在这里。作者（感激） 接受拉取请求。方括号内的文字将在 出版物]
In many environments offering short-term or temporary Internet access (such as coffee shops), it is common to start new connections in a captive portal mode. This highly restricts what the customer can do until the customer has authenticated. This document describes a DHCP option (and a Router Advertisement (RA) extension) to inform clients that they are behind some sort of captive-portal device, and that they will need to authenticate to get Internet access. It is not a full solution to address all of the issues that clients may have with captive portals; it is designed to be used in larger solutions. The method of authenticating to, and interacting with the captive portal is out of scope of this document. [ This document is being collaborated on in Github at: https://github.com/wkumari/draft-ekwk- capport-rfc7710bis. The most recent version of the document, open issues, etc should all be available here. The authors (gratefully) accept pull requests. Text in square brackets will be removed before publication. ]