draft-ietf-hip-native-nat-traversal-29.txt   draft-ietf-hip-native-nat-traversal-30.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 22, 2020 Ericsson Expires: August 24, 2020 Ericsson
February 19, 2020 February 21, 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-29 draft-ietf-hip-native-nat-traversal-30
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 its messages instead of ICE for all NAT traversal procedures due to its
kernel-space dependencies. kernel-space dependencies.
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 August 22, 2020. This Internet-Draft will expire on August 24, 2020.
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 44, line 52 skipping to change at page 44, line 52
| | | address" format IPv4 address [RFC4291] | | | | address" format IPv4 address [RFC4291] |
+-----------+----------+--------------------------------------------+ +-----------+----------+--------------------------------------------+
Table 1: Fields of the LOCATOR_SET Parameter Table 1: Fields of the LOCATOR_SET Parameter
5.8. RELAY_HMAC Parameter 5.8. RELAY_HMAC Parameter
As specified in Legacy ICE-HIP [RFC5770], the RELAY_HMAC parameter As specified in Legacy ICE-HIP [RFC5770], the RELAY_HMAC parameter
value has the TLV type 65520. It has the same semantics as RVS_HMAC value has the TLV type 65520. It has the same semantics as RVS_HMAC
as specified in section 4.2.1 in [RFC8004]. Similarly as with as specified in section 4.2.1 in [RFC8004]. Similarly as with
RVS_HMAC, also RELAY_HMAC is is keyed with the HIP integrity key RVS_HMAC, also RELAY_HMAC is keyed with the HIP integrity key (HIP-lg
(HIP-lg or HIP-gl as specified in section 6.5 in [RFC7401]), or HIP-gl as specified in section 6.5 in [RFC7401]), established
established during the relay registration procedure as described in during the relay registration procedure as described in Section 4.1.
Section 4.1.
5.9. Registration Types 5.9. Registration Types
The REG_INFO, REG_REQ, REG_RESP, and REG_FAILED parameters contain The REG_INFO, REG_REQ, REG_RESP, and REG_FAILED parameters contain
Registration Type [RFC8003] values for Control Relay Server Registration Type [RFC8003] values for Control Relay Server
registration. The value for RELAY_UDP_HIP is 2 as specified in registration. The value for RELAY_UDP_HIP is 2 as specified in
Legacy ICE-HIP [RFC5770]. The value for RELAY_UDP_ESP is (value [TBD Legacy ICE-HIP [RFC5770]. The value for RELAY_UDP_ESP is (value [TBD
by IANA: 3]). by IANA: 3]).
5.10. Notify Packet Types 5.10. Notify Packet Types
skipping to change at page 52, line 38 skipping to change at page 52, line 38
gathering against fake requests and responses. Further, replay gathering against fake requests and responses. Further, replay
attacks are not possible because the HIP base exchange (and also attacks are not possible because the HIP base exchange (and also
UPDATE procedure) is protected against replay attacks. UPDATE procedure) is protected against replay attacks.
7. IANA Considerations 7. IANA Considerations
This section is to be interpreted according to [RFC8126]. This section is to be interpreted according to [RFC8126].
This document reuses the same default UDP port number 10500 as This document reuses the same default UDP port number 10500 as
specified by Legacy ICE-HIP [RFC5770] for tunneling both HIP control specified by Legacy ICE-HIP [RFC5770] for tunneling both HIP control
plane and data plane traffic. The selection between Legacy ICE-HIP plane and data plane traffic. IANA is requested to add a reference
to this document in the entry for UDP port 10500 in the Transport
Protocol Port Number Registry. The selection between Legacy ICE-HIP
and Native ICE-HIP mode is negotiated using NAT_TRAVERSAL_MODE and Native ICE-HIP mode is negotiated using NAT_TRAVERSAL_MODE
parameter during the base exchange. By default, hosts listen this parameter during the base exchange. By default, hosts listen this
port for incoming UDP datagrams and can use it also for sending UDP port for incoming UDP datagrams and can use it also for sending UDP
datagrams. Other emphemeral port numbers are negotiated and utilized datagrams. Other emphemeral port numbers are negotiated and utilized
dynamically. dynamically.
This document updates the IANA Registry for HIP Parameter Types This document updates the IANA Registry for HIP Parameter Types
[RFC7401] by assigning new HIP Parameter Type values for the new HIP [RFC7401] by assigning new HIP Parameter Type values for the new HIP
Parameters: RELAYED_ADDRESS (length 20), MAPPED_ADDRESS (length 20, Parameters: RELAYED_ADDRESS (length 20), MAPPED_ADDRESS (length 20,
defined in Section 5.12), PEER_PERMISSION (length 48, defined in defined in Section 5.12), PEER_PERMISSION (length 48, defined in
 End of changes. 5 change blocks. 
9 lines changed or deleted 10 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/