draft-ietf-hip-native-nat-traversal-32.txt   draft-ietf-hip-native-nat-traversal-33.txt 
HIP Working Group A. Keranen HIP Working Group A. Keranen
Internet-Draft J. Melen Internet-Draft J. Melen
Intended status: Experimental M. Komu, Ed. Intended status: Experimental M. Komu, Ed.
Expires: January 28, 2021 Ericsson Expires: February 4, 2021 Ericsson
July 27, 2020 August 3, 2020
Native NAT Traversal Mode for the Host Identity Protocol Native NAT Traversal Mode for the Host Identity Protocol
draft-ietf-hip-native-nat-traversal-32 draft-ietf-hip-native-nat-traversal-33
Abstract Abstract
This document specifies a new Network Address Translator (NAT) This document specifies a new Network Address Translator (NAT)
traversal mode for the Host Identity Protocol (HIP). The new mode is traversal mode for the Host Identity Protocol (HIP). The new mode is
based on the Interactive Connectivity Establishment (ICE) methodology based on the Interactive Connectivity Establishment (ICE) methodology
and UDP encapsulation of data and signaling traffic. The main and UDP encapsulation of data and signaling traffic. The main
difference from the previously specified modes is the use of HIP difference from the previously specified modes is the use of HIP
messages instead of ICE for all NAT traversal procedures due to the messages instead of ICE for all NAT traversal procedures due to the
kernel-space dependencies of HIP. kernel-space dependencies of HIP.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 28, 2021. This Internet-Draft will expire on February 4, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 46 skipping to change at page 6, line 46
HIP offer: HIP offer:
Before two end-hosts can establish a communication channel using Before two end-hosts can establish a communication channel using
the NAT traversal procedures defined in this document, they need the NAT traversal procedures defined in this document, they need
exchange their locators (i.e. candidates) with each other. In exchange their locators (i.e. candidates) with each other. In
ICE, this procedure is called Candidate Exchange and it does not ICE, this procedure is called Candidate Exchange and it does not
specify how the candidates are exchanged but Session Description specify how the candidates are exchanged but Session Description
Protocol (SDP) "offer/answer" is mentioned as an example. In Protocol (SDP) "offer/answer" is mentioned as an example. In
contrast, the Candidate Exchange in HIP is the base exchange contrast, the Candidate Exchange in HIP is the base exchange
itself or a subsequent UPDATE prodecure occurring after a itself or a subsequent UPDATE prodecure occurring after a
handover. Following [RFC5770] and SDP [RFC3264] naming handover. Following [RFC5770] and SDP related naming conventions
conventions, "HIP offer" is the the Initiator's LOCATOR_SET [RFC3264], "HIP offer" is the the Initiator's LOCATOR_SET
parameter in a HIP I2 or in an UPDATE control packet. parameter in a HIP I2 or in an UPDATE control packet.
HIP answer: HIP answer:
The Responder's LOCATOR_SET parameter in a HIP R2 or UPDATE The Responder's LOCATOR_SET parameter in a HIP R2 or UPDATE
control packet. Corresponds to the SDP answer parameter control packet. Corresponds to the SDP answer parameter
[RFC3264], but is HIP specific. Please refer also to the longer [RFC3264], but is HIP specific. Please refer also to the longer
description of the "HIP offer" term above. description of the "HIP offer" term above.
HIP connectivity checks: HIP connectivity checks:
In order to obtain a direct end-to-end communication path (without In order to obtain a direct end-to-end communication path (without
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/