idnits 2.17.1 draft-pfister-capport-pvd-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 90: '... MUST have an "https" scheme....' RFC 2119 keyword, line 107: '... device SHOULD fetch the Additional ...' RFC 2119 keyword, line 113: '... the client SHOULD assume that the n...' RFC 2119 keyword, line 117: '... client device SHOULD assume that th...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 30, 2018) is 2127 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-08) exists of draft-ietf-capport-api-00 == Outdated reference: A later version (-11) exists of draft-ietf-intarea-provisioning-domains-02 ** Downref: Normative reference to an Informational RFC: RFC 7556 == Outdated reference: A later version (-10) exists of draft-ietf-capport-architecture-02 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Pfister 3 Internet-Draft Cisco 4 Intended status: Standards Track T. Pauly 5 Expires: January 1, 2019 Apple Inc. 6 June 30, 2018 8 Using Provisioning Domains for Captive Portal Discovery 9 draft-pfister-capport-pvd-00 11 Abstract 13 Devices that connect to Captive Portals need a way to identify that 14 the network is restricted and discover a method for opening up 15 access. This document defines how to use Provisioning Domain 16 Additional Information to discover a Captive Portal API URI. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 1, 2019. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Captive Portal URI Option . . . . . . . . . . . . . . . . . . 2 54 3. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 57 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 58 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 60 7.2. Informative References . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 The Captive Portal Architecture [I-D.ietf-capport-architecture] 66 defines the interaction model for how client devices (also referred 67 to as User Equipment) interact with a network that is restricted and 68 requires explicit user interaction to allow a device to access the 69 Internet. The first step of this process involves a Provisioning 70 Service communicating with the User Equipment to indicate that the 71 network is captive, and how to get out of captivity. The key piece 72 of information that the Provisioning Service provides is the URI of a 73 JSON-based API that allows the User Equipment to interact with the 74 captive portal. This API is specified in [I-D.ietf-capport-api]. 76 This document defines the mechanism for using Provisioning Domain 77 (PvD) Additional Information as the Captive Portal Provisioning 78 Service. A PvD defines a consistent and usable set of network 79 configurations [RFC7556]. A Captive Network is one example of a PvD 80 that has unique properties that a device needs to be aware of when 81 presenting networks to generic applications. Naming specific PvDs 82 and presenting a set of Additional Information for a PvD is defined 83 in [I-D.ietf-intarea-provisioning-domains]. 85 2. Captive Portal URI Option 87 The Additional Information fetched for a PvD is presented as JSON. 88 This document defines a new key to be used to identify the Captive 89 Portal API URI. As specified in [I-D.ietf-capport-api], this URI 90 MUST have an "https" scheme. 92 JSON Key: captive-api 94 Description: URI of Captive Portal API 96 Type: UTF-8 string [RFC3629] 97 Example: "https://captive.example.com/api" 99 3. Client Behavior 101 When a client device that support PvDs attaches a network, it will 102 discover if there is one or more named PvDs on the network with a 103 Router Advertisement as specified in 104 [I-D.ietf-intarea-provisioning-domains]. 106 If the PvD indicates that it has Additional Information, the client 107 device SHOULD fetch the Additional Information prior to allowing the 108 PvD to be used for generic network access, in case the network is 109 restricted or captive. If the Additional Information contains the 110 "captive-api" key, then the client device can interact with the 111 Captive Portal API before proceeding with using the network. If the 112 Additional Information does not contain the "captive-api" key, then 113 the client SHOULD assume that the network is not captive, and proceed 114 with using the network. 116 If the PvD indicates that it has no Additional Information, the 117 client device SHOULD assume that the network is not captive, and 118 proceed with using the network. 120 It is possible that a misconfigured network will provide a named PvD 121 without explicitly marking the captive option, while still 122 restricting network access and providing a Captive Portal. In this 123 case, connections made by the client device may be blocked or 124 redirected, as occurs in captive network in which there is no 125 explicit provisioning. 127 4. Security Considerations 129 The Captive Portal PvD option is subject to the same security 130 considerations as any other options provisioned via Router 131 Advertisements and Explicit Provisioning Domains. This information 132 should not be used by client devices to trust the safety or security 133 of a network attachment. 135 5. IANA Considerations 137 This document adds a new key to the "Additional Information PvD Keys" 138 defined in [I-D.ietf-intarea-provisioning-domains]. See Section 2 139 for the new key definition. 141 6. Acknowledgements 143 Thanks to contributions from Eric Vyncke, Mark Townsley, David 144 Schinazi, and Kyle Larose. 146 7. References 148 7.1. Normative References 150 [I-D.ietf-capport-api] 151 Pauly, T. and D. Thakore, "Captive Portal API", draft- 152 ietf-capport-api-00 (work in progress), February 2018. 154 [I-D.ietf-intarea-provisioning-domains] 155 Pfister, P., Vyncke, E., Pauly, T., Schinazi, D., and W. 156 Shao, "Discovering Provisioning Domain Names and Data", 157 draft-ietf-intarea-provisioning-domains-02 (work in 158 progress), June 2018. 160 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 161 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 162 2003, . 164 [RFC7556] Anipko, D., Ed., "Multiple Provisioning Domain 165 Architecture", RFC 7556, DOI 10.17487/RFC7556, June 2015, 166 . 168 7.2. Informative References 170 [I-D.ietf-capport-architecture] 171 Larose, K. and D. Dolson, "CAPPORT Architecture", draft- 172 ietf-capport-architecture-02 (work in progress), June 173 2018. 175 Authors' Addresses 177 Pierre Pfister 178 Cisco 179 11 Rue Camille Desmoulins 180 Issy-les-Moulineaux 92130 181 France 183 Email: pierre.pfister@darou.fr 184 Tommy Pauly 185 Apple Inc. 186 One Apple Park Way 187 Cupertino, California 95014 188 United States of America 190 Email: tpauly@apple.com