[MS-IPHTTPS]:
IP over HTTPS (IP-HTTPS) Tunneling Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
§ Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
§ Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
§ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
§ License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map.
§ Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
§ Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Support. For questions and support, please contact .
Revision Summary
Date / Revision History / Revision Class / Comments /12/5/2008 / 0.1 / Major / Initial Availability
1/16/2009 / 0.1.1 / Editorial / Changed language and formatting in the technical content.
2/27/2009 / 0.1.2 / Editorial / Changed language and formatting in the technical content.
4/10/2009 / 0.1.3 / Editorial / Changed language and formatting in the technical content.
5/22/2009 / 1.0 / Major / Updated and revised the technical content.
7/2/2009 / 1.0.1 / Editorial / Changed language and formatting in the technical content.
8/14/2009 / 1.0.2 / Editorial / Changed language and formatting in the technical content.
9/25/2009 / 2.0 / Major / Updated and revised the technical content.
11/6/2009 / 3.0 / Major / Updated and revised the technical content.
12/18/2009 / 4.0 / Major / Updated and revised the technical content.
1/29/2010 / 5.0 / Major / Updated and revised the technical content.
3/12/2010 / 5.0.1 / Editorial / Changed language and formatting in the technical content.
4/23/2010 / 5.0.2 / Editorial / Changed language and formatting in the technical content.
6/4/2010 / 5.0.3 / Editorial / Changed language and formatting in the technical content.
7/16/2010 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
8/27/2010 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
10/8/2010 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
11/19/2010 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
1/7/2011 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
2/11/2011 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
3/25/2011 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
5/6/2011 / 5.0.3 / None / No changes to the meaning, language, or formatting of the technical content.
6/17/2011 / 5.1 / Minor / Clarified the meaning of the technical content.
9/23/2011 / 5.1 / None / No changes to the meaning, language, or formatting of the technical content.
12/16/2011 / 6.0 / Major / Updated and revised the technical content.
3/30/2012 / 6.0 / None / No changes to the meaning, language, or formatting of the technical content.
7/12/2012 / 7.0 / Major / Updated and revised the technical content.
10/25/2012 / 7.0 / None / No changes to the meaning, language, or formatting of the technical content.
1/31/2013 / 7.0 / None / No changes to the meaning, language, or formatting of the technical content.
8/8/2013 / 8.0 / Major / Updated and revised the technical content.
11/14/2013 / 8.0 / None / No changes to the meaning, language, or formatting of the technical content.
2/13/2014 / 8.0 / None / No changes to the meaning, language, or formatting of the technical content.
5/15/2014 / 8.0 / None / No changes to the meaning, language, or formatting of the technical content.
6/30/2015 / 9.0 / Major / Significantly changed the technical content.
10/16/2015 / 9.0 / None / No changes to the meaning, language, or formatting of the technical content.
7/14/2016 / 9.0 / None / No changes to the meaning, language, or formatting of the technical content.
6/1/2017 / 9.0 / None / No changes to the meaning, language, or formatting of the technical content.
Table of Contents
1 Introduction 6
1.1 Glossary 6
1.2 References 6
1.2.1 Normative References 6
1.2.2 Informative References 7
1.3 Overview 7
1.4 Relationship to Other Protocols 7
1.5 Prerequisites/Preconditions 8
1.6 Applicability Statement 8
1.7 Versioning and Capability Negotiation 9
1.8 Vendor-Extensible Fields 9
1.9 Standards Assignments 9
2 Messages 10
2.1 Transport 10
2.2 Message Syntax 11
3 Protocol Details 12
3.1 IP-HTTPS Client Details 12
3.1.1 Abstract Data Model 13
3.1.2 Timers 14
3.1.2.1 Reconnect Timer 14
3.1.3 Initialization 14
3.1.4 Higher-Layer Triggered Events 15
3.1.4.1 Enable IP-HTTPS Link 15
3.1.4.2 Disable IP-HTTPS Link 15
3.1.5 Processing Events and Sequencing Rules 15
3.1.5.1 Establishing the HTTPS Connection 15
3.1.5.2 Bringing the IP-HTTPS Link Up 15
3.1.5.3 Data Transfer 15
3.1.5.4 Error Handling 16
3.1.6 Timer Events 16
3.1.7 Other Local Events 16
3.2 IP-HTTPS Server Details 16
3.2.1 Abstract Data Model 16
3.2.2 Timers 17
3.2.3 Initialization 17
3.2.3.1 Entering the Listen State 17
3.2.4 Higher-Layer Triggered Events 17
3.2.4.1 Enable IP-HTTPS Link 17
3.2.4.2 Disable IP-HTTPS Link 17
3.2.5 Processing Events and Sequencing Rules 17
3.2.5.1 Accepting IP-HTTPS Clients 17
3.2.5.2 Data Transfer 17
3.2.5.2.1 Sending a Packet to a Client 17
3.2.5.2.2 Receiving a Packet from a Client 18
3.2.5.3 Error Handling 18
3.2.6 Timer Events 18
3.2.7 Other Local Events 18
3.2.7.1 Changing Authentication Mode 19
3.2.7.2 Client Disconnection 19
3.2.7.3 Shutdown 19
4 Protocol Examples 20
4.1 Packet Flow and Connection Establishment 20
4.2 Attack Scenarios 21
4.2.1 Unauthorized Client Connecting to an IP-HTTPS Server 21
4.2.2 Unauthorized Client Connecting to an IP-HTTPS Server (When Authentication Mode Is Set to Certificates) 21
4.2.3 Unauthorized Client Connecting to an IP-HTTPS Server (When Authentication Mode Is Set to None) 22
4.2.4 Unauthorized IP-HTTPS Server Accepting Connections from a Genuine IP-HTTPS Client 23
4.2.5 Man in the Middle 24
5 Security 25
5.1 Security Considerations for Implementers 25
5.2 Index of Security Parameters 25
6 Appendix A: Product Behavior 26
7 Change Tracking 27
8 Index 28
1 Introduction
This document specifies the IP over HTTPS (IP-HTTPS) Protocol, a mechanism to transport IPv6 packets on an HTTPS connection.
Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
1.1 Glossary
This document uses the following terms:
IP-HTTPS client: A computer that implements the IP over HTTPS (IP-HTTPS) Protocol and that initiates an IP-HTTPS connection to an IP-HTTPS server over TCP port 443.
IP-HTTPS endpoint: An entity that communicates to an IP-HTTPS client via the IP-HTTPS server.
IP-HTTPS server: A computer that implements the IP over HTTPS (IP-HTTPS) Protocol and listens and accepts IP-HTTPS connections from IP-HTTPS clients over TCP port 443.
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information.
[RFC1945] Berners-Lee, T., Fielding, R., and Frystyk, H., "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996, http://www.ietf.org/rfc/rfc1945.txt
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc-editor.org/rfc/rfc2119.txt
[RFC2460] Deering, S., and Hinden, R., "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998, http://www.rfc-editor.org/rfc/rfc2460.txt
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999, http://www.rfc-editor.org/rfc/rfc2616.txt
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000, http://www.rfc-editor.org/rfc/rfc2818.txt
[RFC4346] Dierks, T., and Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.1", RFC 4346, April 2006, http://www.ietf.org/rfc/rfc4346.txt
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and Soliman, H., "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007, http://www.ietf.org/rfc/rfc4861.txt
[SSLPROXY] Luotonen, A., "Tunneling SSL Through a WWW Proxy", March 1997, http://tools.ietf.org/html/draft-luotonen-ssl-tunneling-03
1.2.2 Informative References
[RFC1661] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", STD 51, RFC 1661, July 1994, http://www.ietf.org/rfc/rfc1661.txt
[RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and Nikander, P., "SEcure Neighbor Discovery (SEND)", RFC 3971, March 2005, http://www.rfc-editor.org/rfc/rfc3971.txt
1.3 Overview
Many virtual private network (VPN) services provide a way for mobile and home users to access the corporate network remotely by using the Point-to-Point Tunneling Protocol (PPTP) and the Layer Two Tunneling Protocol/Internet Protocol security (L2TP/IPsec). However, with the popularization of firewalls and web proxies, many service providers (for example, hotels) do not allow the PPTP and L2TP/IPsec traffic. This results in users not receiving ubiquitous connectivity to their corporate networks. For example, generic routing encapsulation (GRE) port blocking by many Internet service providers (ISPs) is a common problem when using PPTP.
The IP over HTTPS (IP-HTTPS) Tunneling Protocol Specification defines the IP over HTTPS (IP-HTTPS) Protocol. IP-HTTPS is a mechanism to encapsulate IP traffic over an HTTPS protocol, as defined in [RFC1945], [RFC2616], and [RFC2818]. This protocol enables remote users behind a protocol blocking firewall or proxy server to access a private network using HTTPS. The use of HTTPS enables traversal of most firewalls and web proxies. IP-HTTPS supports HTTP proxy authentication.
This protocol employs two main roles: client and server. The IP-HTTPS client and IP-HTTPS server can use either HTTPS or HTTP as a transport.
An IP-HTTPS client: This component is similar to a VPN client. The IP-HTTPS client initiates connections to a configured IP-HTTPS server. The client could become active either automatically (for example, when the client machine is located behind an HTTP firewall and/or HTTP proxy), or based on administrative policy (for example, always on), or based on an explicit user action.
When an IP-HTTPS client is behind an HTTP proxy, the client first establishes a tunnel to the IP-HTTPS server using the CONNECT method, as described in [SSLPROXY].
An IP-HTTPS server: This component is similar to a VPN server, and it is typically positioned at the edge of a network. The IP-HTTPS server directly accepts HTTPS connections made by IP-HTTPS clients. When positioned behind a device that terminates HTTPS on its behalf (such as a reverse proxy or a TLS/SSL load balancer), the server can be configured to listen over HTTP.
1.4 Relationship to Other Protocols
The IP over HTTPS (IP-HTTPS) Protocol allows encapsulation of IPv6 traffic over HTTPS. To do so, it depends on the following protocols:
§ Hypertext Transfer Protocol -- HTTP/1.0 [RFC1945].
§ Hypertext Transfer Protocol -- HTTP/1.1 [RFC2616].
§ HTTP Over TLS [RFC2818].
§ Tunneling SSL Through a WWW Proxy [SSLPROXY].
§ The Transport Layer Security (TLS) Protocol Version 1.1 [RFC4346].
Once the underlying transport is established, IP-HTTPS enables IPv6 traffic exchanges per usual IPv6 specifications such as:
§ Neighbor Discovery for IP Version 6 (IPv6) [RFC4861].
§ Protocol, Version 6 (IPv6) Specification [RFC2460].
NoteThe IP-HTTPS Protocol itself does not have any security or authentication methods. Instead, it relies on HTTPS for authentication, data integrity, and confidentiality.