draft-ietf-hip-native-nat-traversal-09.txt   draft-ietf-hip-native-nat-traversal-10.txt 
HIP Working Group A. Keranen HIP Working Group A. Keranen
Internet-Draft J. Melen Internet-Draft J. Melen
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: January 24, 2016 July 23, 2015 Expires: July 22, 2016 January 19, 2016
Native NAT Traversal Mode for the Host Identity Protocol Native NAT Traversal Mode for the Host Identity Protocol
draft-ietf-hip-native-nat-traversal-09 draft-ietf-hip-native-nat-traversal-10
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 for all NAT traversal procedures. messages for all NAT traversal procedures.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 24, 2016. This Internet-Draft will expire on July 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 4 skipping to change at page 5, line 4
When a data relay receives an UPDATE with a PEER_PERMISSION When a data relay receives an UPDATE with a PEER_PERMISSION
parameter, it MUST check if the sender of the UPDATE is registered parameter, it MUST check if the sender of the UPDATE is registered
for data relaying service, and drop the UPDATE if the host was not for data relaying service, and drop the UPDATE if the host was not
registered. If the host was registered, the relay checks if there is registered. If the host was registered, the relay checks if there is
a permission with matching information (address, protocol, port and a permission with matching information (address, protocol, port and
SPI values). If there is no such permission, a new permission MUST SPI values). If there is no such permission, a new permission MUST
be created and its lifetime MUST be set to 5 minutes. If an be created and its lifetime MUST be set to 5 minutes. If an
identical permission already existed, it MUST be refreshed by setting identical permission already existed, it MUST be refreshed by setting
the lifetime to 5 minutes. A registered host SHOULD refresh the lifetime to 5 minutes. A registered host SHOULD refresh
permissions roughly 1 minute before the expiration if the permission permissions 1 minute before the expiration if the permission is still
is still needed. needed.
3.3. Relaying UDP Encapsulated Data and Control Packets 3.3. Relaying UDP Encapsulated Data and Control Packets
When a HIP data relay accepts to relay UDP encapsulated data, it When a HIP data relay accepts to relay UDP encapsulated data, it
opens a UDP port (relayed address) for this purpose as described in opens a UDP port (relayed address) for this purpose as described in
Section 3.1. If the data relay receives a UDP encapsulated HIP Section 3.1. If the data relay receives a UDP encapsulated HIP
control packet on that port, it MUST forward the packet to the control packet on that port, it MUST forward the packet to the
registered host and add a RELAY_FROM parameter to the packet as if registered host and add a RELAY_FROM parameter to the packet as if
the data relay was acting as a HIP relay server [RFC5770]. the data relay was acting as a HIP relay server [RFC5770].
skipping to change at page 7, line 27 skipping to change at page 7, line 27
The acknowledgment UPDATE packets MUST contain a MAPPED_ADDRESS The acknowledgment UPDATE packets MUST contain a MAPPED_ADDRESS
parameter with the port, protocol, and IP address of the address parameter with the port, protocol, and IP address of the address
where the connectivity check request was received from. where the connectivity check request was received from.
After a working candidate pair, or pairs, have been discovered, the After a working candidate pair, or pairs, have been discovered, the
controlling host MUST conclude the checks by nominating the highest controlling host MUST conclude the checks by nominating the highest
priority candidate pair for use. The pair MUST be nominated by priority candidate pair for use. The pair MUST be nominated by
sending an ESP packet on the selected pair. If the controlling host sending an ESP packet on the selected pair. If the controlling host
does not have any data to send, it SHOULD send an ICMP echo request does not have any data to send, it SHOULD send an ICMP echo request
using the nominated pair to signal to the controlled host that it can using the nominated pair to signal to the controlled host that it can
stop checks and start using the nominated pair. stop checks and start using the nominated pair. When the controlled
host receives the first ESP packet, it MUST select that pair for use
and send back an ESP packet to acknowledge a working candidate pair.
If the controlled host does not have any data to send, it SHOULD send
an ICMP echo request.
If the connectivity checks failed the hosts SHOULD notify each other If the connectivity checks failed the hosts SHOULD notify each other
about the failure with a CONNECTIVITY_CHECKS_FAILED Notify Message about the failure with a CONNECTIVITY_CHECKS_FAILED Notify Message
Type [RFC5770]. Type [RFC5770].
3.9. NAT Keepalives 3.9. NAT Keepalives
To keep the NAT bindings towards the HIP relay server and the HIP To keep the NAT bindings towards the HIP relay server and the HIP
data relay alive, if a registered host has not sent any data or data relay alive, if a registered host has not sent any data or
control messages to the relay for 15 seconds, it MUST send a HIP control messages to the relay for 15 seconds, it MUST send a HIP
 End of changes. 6 change blocks. 
7 lines changed or deleted 11 lines changed or added

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