Native NAT Traversal Mode for the Host Identity Protocol
draft-ietf-hip-native-nat-traversal-10
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (hip WG)
|
|
Last updated |
|
2016-01-19
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
HIP Working Group A. Keranen
Internet-Draft J. Melen
Intended status: Standards Track Ericsson
Expires: July 22, 2016 January 19, 2016
Native NAT Traversal Mode for the Host Identity Protocol
draft-ietf-hip-native-nat-traversal-10
Abstract
This document specifies a new Network Address Translator (NAT)
traversal mode for the Host Identity Protocol (HIP). The new mode is
based on the Interactive Connectivity Establishment (ICE) methodology
and UDP encapsulation of data and signaling traffic. The main
difference from the previously specified modes is the use of HIP
messages for all NAT traversal procedures.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 22, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Keranen & Melen Expires July 22, 2016 [Page 1]
Internet-Draft HIP Native NAT Traversal Mode January 2016
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Description . . . . . . . . . . . . . . . . . . . . 3
3.1. Relay Registration . . . . . . . . . . . . . . . . . . . 3
3.2. Forwarding Rules and Permissions . . . . . . . . . . . . 4
3.3. Relaying UDP Encapsulated Data and Control Packets . . . 5
3.4. Candidate Gathering . . . . . . . . . . . . . . . . . . . 5
3.5. Base Exchange via HIP Relay Server . . . . . . . . . . . 6
3.6. Native NAT Traversal Mode Negotiation . . . . . . . . . . 6
3.7. Connectivity Check Pacing Negotiation . . . . . . . . . . 6
3.8. Connectivity Checks . . . . . . . . . . . . . . . . . . . 6
3.9. NAT Keepalives . . . . . . . . . . . . . . . . . . . . . 7
3.10. Handling Conflicting SPI Values . . . . . . . . . . . . . 7
4. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. RELAYED_ADDRESS and MAPPED_ADDRESS Parameters . . . . . . 8
4.2. PEER_PERMISSION Parameter . . . . . . . . . . . . . . . . 9
4.3. HIP Connectivity Check Packets . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
The Host Identity Protocol (HIP) [RFC7401] is specified to run
directly on top of IPv4 or IPv6. However, many middleboxes found in
the Internet, such as NATs and firewalls, often allow only UDP or TCP
traffic to pass [RFC5207]. Also, especially NATs usually require the
host behind a NAT to create a forwarding state in the NAT before
other hosts outside of the NAT can contact the host behind the NAT.
To overcome this problem, different methods, commonly referred to as
NAT traversal techniques, have been developed.
Two NAT traversal techniques for HIP are specified in [RFC5770]. One
of them uses only UDP encapsulation, while the other uses also the
Interactive Connectivity Establishment (ICE) [RFC5245] protocol,
which in turn uses Session Traversal Utilities for NAT (STUN)
Show full document text