%% You should probably cite rfc8910 instead of this I-D.
@techreport{ietf-capport-rfc7710bis-02,
    number =    {draft-ietf-capport-rfc7710bis-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-capport-rfc7710bis/02/},
    author =    {Warren "Ace" Kumari and Erik Kline},
    title =     {{Captive-Portal Identification in DHCP / RA}},
    pagetotal = 11,
    year =      2020,
    month =     mar,
    day =       8,
    abstract =  {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. RFC7710 used DHCP code point 160. Due to a conflict, this document specifies TBD. {[} This document is being collaborated on in Github at: https://github.com/capport-wg/7710bis. 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. {]}},
}