draft-ietf-hip-native-nat-traversal-15.txt   draft-ietf-hip-native-nat-traversal-16.txt 
HIP Working Group A. Keranen HIP Working Group A. Keranen
Internet-Draft J. Melen Internet-Draft J. Melen
Intended status: Standards Track M. Komu, Ed. Intended status: Standards Track M. Komu, Ed.
Expires: August 5, 2017 Ericsson Expires: August 8, 2017 Ericsson
February 1, 2017 February 4, 2017
Native NAT Traversal Mode for the Host Identity Protocol Native NAT Traversal Mode for the Host Identity Protocol
draft-ietf-hip-native-nat-traversal-15 draft-ietf-hip-native-nat-traversal-16
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 36 skipping to change at page 1, line 36
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 August 5, 2017. This Internet-Draft will expire on August 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 11, line 34 skipping to change at page 11, line 34
LSIs and by IPv6 based applications using HITs. The LSIs and HITs of LSIs and by IPv6 based applications using HITs. The LSIs and HITs of
the local virtual interfaces MUST be excluded in the candidate the local virtual interfaces MUST be excluded in the candidate
gathering phase as well to avoid creating unnecessary loopback gathering phase as well to avoid creating unnecessary loopback
connectivity tests. connectivity tests.
Gathering of candidates MAY also be performed as specified in Gathering of candidates MAY also be performed as specified in
Section 4.2 of [RFC5770] if STUN servers are available, or if the Section 4.2 of [RFC5770] if STUN servers are available, or if the
host has just a single interface and no STUN or HIP data relay host has just a single interface and no STUN or HIP data relay
servers are available. servers are available.
Eeach local address candidate MUST be assigned a priority. The Each local address candidate MUST be assigned a priority. The
recommended formula in [I-D.ietf-ice-rfc5245bis] SHOULD be used: recommended formula in [I-D.ietf-ice-rfc5245bis] SHOULD be used:
priority = (2^24)*(type preference) + (2^8)*(local preference) + priority = (2^24)*(type preference) + (2^8)*(local preference) +
(2^0)*(256 - component ID) (2^0)*(256 - component ID)
In the formula, type preference follows the ICE specification section In the formula, type preference follows the ICE specification section
4.1.2.2 guidelines: the RECOMMENDED values are 126 for host 4.1.2.2 guidelines: the RECOMMENDED values are 126 for host
candidates, 100 for server reflexive candidates, 110 for peer candidates, 100 for server reflexive candidates, 110 for peer
reflexive candidates, and 0 for relayed candidates. The highest reflexive candidates, and 0 for relayed candidates. The highest
value is 126 (the most preferred) and lowest is 0 (last resort). For value is 126 (the most preferred) and lowest is 0 (last resort). For
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

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