draft-ietf-hip-over-hip-01.txt   draft-ietf-hip-over-hip-02.txt 
HIP Working Group A. Keranen HIP Working Group A. Keranen
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Experimental July 12, 2010 Intended status: Experimental October 18, 2010
Expires: January 13, 2011 Expires: April 21, 2011
Host Identity Protocol Signaling Message Transport Modes Host Identity Protocol Signaling Message Transport Modes
draft-ietf-hip-over-hip-01 draft-ietf-hip-over-hip-02
Abstract Abstract
This document specifies two transport modes for Host Identity This document specifies two transport modes for Host Identity
Protocol signaling messages that allow conveying them over encrypted Protocol (HIP) signaling messages that allow conveying them over
connections initiated with the Host Identity Protocol. encrypted connections initiated with the Host Identity Protocol.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 13, 2011. This Internet-Draft will expire on April 21, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 2, line 15 skipping to change at page 2, line 15
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
described in the BSD License. described in the BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3 3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Mode Negotiation in HIP Base Exchange . . . . . . . . . . . 3 3.1. Mode Negotiation in HIP Base Exchange . . . . . . . . . . . 3
3.2. Mode Negotiation After HIP Base Exchange . . . . . . . . . 4 3.2. Mode Negotiation After HIP Base Exchange . . . . . . . . . 5
3.3. HIP Messages on Encrypted Connections . . . . . . . . . . . 5 3.3. HIP Messages on Encrypted Connections . . . . . . . . . . . 5
3.3.1. ESP mode . . . . . . . . . . . . . . . . . . . . . . . 5 3.3.1. ESP mode . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.2. ESP-TCP mode . . . . . . . . . . . . . . . . . . . . . 6 3.3.2. ESP-TCP mode . . . . . . . . . . . . . . . . . . . . . 6
3.4. Recovering from Failed Encrypted Connections . . . . . . . 6 3.4. Recovering from Failed Encrypted Connections . . . . . . . 6
3.5. Host Mobility . . . . . . . . . . . . . . . . . . . . . . . 6 3.5. Host Mobility . . . . . . . . . . . . . . . . . . . . . . . 7
4. Notify Packet Types . . . . . . . . . . . . . . . . . . . . . . 7 4. Notify Packet Types . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8
8.2. Informational References . . . . . . . . . . . . . . . . . 8 8.2. Informational References . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Host Identity Protocol (HIP) [RFC5201] signaling messages can be Host Identity Protocol (HIP) [RFC5201] signaling messages can be
exchanged over plain IP using the protocol number reserved for this exchanged over plain IP using the protocol number reserved for this
purpose, or over UDP using the UDP port reserved for HIP NAT purpose, or over UDP using the UDP port reserved for HIP NAT
traversal [RFC5770]. When two hosts perform a HIP base exchange, traversal [RFC5770]. When two hosts perform a HIP base exchange,
they set up an encrypted connection between them for data traffic, they set up an encrypted connection between them for data traffic,
but continue to use plain IP or UDP for HIP signaling messages. but continue to use plain IP or UDP for HIP signaling messages.
skipping to change at page 4, line 11 skipping to change at page 4, line 11
mode for the following HIP signaling messages sent between them for mode for the following HIP signaling messages sent between them for
the duration of the HIP association or until another mode is the duration of the HIP association or until another mode is
negotiated. negotiated.
If the Initiator cannot or will not use any of the modes proposed by If the Initiator cannot or will not use any of the modes proposed by
the Responder, the Initiator SHOULD include an empty the Responder, the Initiator SHOULD include an empty
HIP_TRANSPORT_MODE parameter to the I2 packet to signal that it HIP_TRANSPORT_MODE parameter to the I2 packet to signal that it
support this extension but will not use any of the proposed modes. support this extension but will not use any of the proposed modes.
Depending on local policy, the Responder MAY either abort the base Depending on local policy, the Responder MAY either abort the base
exchange or continue HIP signaling without using an encrypted exchange or continue HIP signaling without using an encrypted
connection. If the Initiator selects a mode that the Responder does connection, if there was no HIP_TRANSPORT_MODE parameter in I2 or the
not support (and hence was not included in R1), the Responder SHOULD parameter was empty. If the Initiator selects a mode that the
reply with a NO_VALID_HIP_TRANSPORT_MODE NOTIFY packet (see Responder does not support (and hence was not included in R1), the
Section 4) and abort the base exchange. Responder MUST abort the base exchange. If the base exchange is
aborted due to (possibly lack of) HIP_TRANSPORT_PARAMETER, the
Responder SHOULD send a NO_VALID_HIP_TRANSPORT_MODE NOTIFY packet
(see Section 4) to the Initiator.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mode ID #1 | Mode ID #2 | | Mode ID #1 | Mode ID #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mode ID #n | Padding | | Mode ID #n | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type [ TBD by IANA; 7680 ] Type [ TBD by IANA; 7680 ]
Length length in octets, excluding Type, Length, and Padding Length length in octets, excluding Type, Length, and Padding
Mode ID defines the proposed or selected transport mode(s) Mode ID defines the proposed or selected transport mode(s)
The following mode IDs are defined: The following Mode IDs are defined:
ID name Value ID name Value
RESERVED 0 RESERVED 0
DEFAULT 1 DEFAULT 1
ESP 2 ESP 2
ESP-TCP 3 ESP-TCP 3
Figure 1: Format of the HIP_TRANSPORT_MODE parameter Figure 1: Format of the HIP_TRANSPORT_MODE parameter
The mode DEFAULT indicates that the same transport mode (e.g., plain The mode DEFAULT indicates that the same transport mode (e.g., plain
skipping to change at page 5, line 4 skipping to change at page 5, line 11
subsequent HIP signaling messages. In the ESP mode the messages are subsequent HIP signaling messages. In the ESP mode the messages are
sent as such on the encrypted ESP connection and in the ESP-TCP mode sent as such on the encrypted ESP connection and in the ESP-TCP mode
TCP is used within the ESP tunnel. TCP is used within the ESP tunnel.
3.2. Mode Negotiation After HIP Base Exchange 3.2. Mode Negotiation After HIP Base Exchange
If a HIP hosts wants to change to a different transport mode (or If a HIP hosts wants to change to a different transport mode (or
start using a transport mode) some time after the base exchange, it start using a transport mode) some time after the base exchange, it
sends a HIP UPDATE packet with a HIP_TRANSPORT_MODE parameter sends a HIP UPDATE packet with a HIP_TRANSPORT_MODE parameter
containing the mode(s) it would prefer to use. The host receiving containing the mode(s) it would prefer to use. The host receiving
the UPDATE MUST respond with an UPDATE packet containing the mode the UPDATE SHOULD respond with an UPDATE packet containing the mode
that is selected as in the negotiation during the base exchange. If that is selected as in the negotiation during the base exchange. If
the receiving host does not support, or is not willing to use, any of the receiving host does not support, or is not willing to use, any of
the listed modes, it MUST respond with an UPDATE packet containing the listed modes, it SHOULD respond with an UPDATE packet where the
only the currently used transport mode (even if one was not included HIP_TRANSPORT_MODE parameter contains only the currently used
in the previous UPDATE packet) and continue using it. transport mode (even if one was not included in the previous UPDATE
packet) and continue using that mode.
Since the HIP_TRANSPORT_MODE parameter's type is not critical (as Since the HIP_TRANSPORT_MODE parameter's type is not critical (as
defined in Section 5.2.1 of [RFC5201]), a host not supporting this defined in Section 5.2.1 of [RFC5201]), a host not supporting this
extension would simply acknowledge the UPDATE without responding with extension would simply reply with an acknowledgement UPDATE packet
an UPDATE containing a HIP_TRANSPORT_MODE parameter. without a HIP_TRANSPORT_MODE parameter. In such a case, depending on
local policy as in mode negotiation during the base exchange, the
host that requested the new transport mode MAY close the HIP
association. If the association is closed, the host closing the
association SHOULD send a NO_VALID_HIP_TRANSPORT_MODE NOTIFY packet
to the other host before closing the association.
3.3. HIP Messages on Encrypted Connections 3.3. HIP Messages on Encrypted Connections
This specification defines two different transport modes for sending This specification defines two different transport modes for sending
HIP packets over encrypted ESP connections. These modes require that HIP packets over encrypted ESP connections. These modes require that
the ESP transport format [RFC5202] is negotiated to be used between the ESP transport format [RFC5202] is negotiated to be used between
the hosts. If the ESP transport format is not used, these modes MUST the hosts. If the ESP transport format is not used, these modes MUST
NOT be offered in the HIP_TRANSPORT_MODE parameter. If a NOT be offered in the HIP_TRANSPORT_MODE parameter. If a
HIP_TRANSPORT_MODE parameter containing an ESP transport mode is HIP_TRANSPORT_MODE parameter containing an ESP transport mode is
received but the ESP transport format is not used, a host MUST NOT received but the ESP transport format is not used, a host MUST NOT
skipping to change at page 5, line 41 skipping to change at page 6, line 5
cases where all signaling traffic should be encrypted. If the HIP cases where all signaling traffic should be encrypted. If the HIP
messages may become so large that they would need to be fragmented, messages may become so large that they would need to be fragmented,
e.g., because of HIP certificates [I-D.ietf-hip-cert] or DATA e.g., because of HIP certificates [I-D.ietf-hip-cert] or DATA
messages [I-D.ietf-hip-hiccups], it is RECOMMENDED to use the ESP-TCP messages [I-D.ietf-hip-hiccups], it is RECOMMENDED to use the ESP-TCP
mode which can handle message fragmentation at TCP level instead of mode which can handle message fragmentation at TCP level instead of
relying on IP level fragmentation. relying on IP level fragmentation.
HIP messages that result in changing or generating new keying HIP messages that result in changing or generating new keying
material, i.e., the base exchange and re-keying UPDATE messages, MUST material, i.e., the base exchange and re-keying UPDATE messages, MUST
NOT be sent over an encrypted connection that is created using the NOT be sent over an encrypted connection that is created using the
keying material that is being changed. keying material that is being changed, nor over an encrypted
connection using the newly created keying material.
3.3.1. ESP mode 3.3.1. ESP mode
If the ESP mode is selected in the base exchange, both hosts MUST If the ESP mode is selected in the base exchange, both hosts MUST
listen for incoming HIP signaling messages and send outgoing messages listen for incoming HIP signaling messages and send outgoing messages
on the encrypted connection. The ESP header's next header value for on the encrypted connection. The ESP header's next header value for
such messages MUST be set to HIP (139). such messages MUST be set to HIP (139).
3.3.2. ESP-TCP mode 3.3.2. ESP-TCP mode
If the ESP-TCP mode is selected, the host with the larger HIT If the ESP-TCP mode is selected, the host with the larger HIT
(calculated as defined in Section 6.5 of [RFC5201]) MUST start to (calculated as defined in Section 6.5 of [RFC5201]) MUST start to
listen for an incoming TCP connection on the port 10500 on the listen for an incoming TCP connection on the port 10500 on the
encrypted connection and the other host MUST create a TCP connection encrypted connection and the other host MUST create a TCP connection
to that port. The host with the lower HIT SHOULD use port 10500 as to that port. The host with the smaller HIT SHOULD use port 10500 as
the source port for the TCP connection. Once the TCP connection is the source port for the TCP connection. Once the TCP connection is
established, both hosts MUST listen for incoming HIP signaling established, both hosts MUST listen for incoming HIP signaling
messages and send the outgoing messages using the TCP connection. messages and send the outgoing messages using the TCP connection.
The ESP next header value for messages sent using the ESP-TCP mode The ESP next header value for messages sent using the ESP-TCP mode
connections MUST be set to TCP (6). connections MUST be set to TCP (6).
If the hosts are unable to create the TCP connection, the host that If the hosts are unable to create the TCP connection, the host that
initiated the mode negotiation MUST restart the negotiation with initiated the mode negotiation MUST restart the negotiation with
UPDATE message and SHOULD NOT propose the ESP-TCP mode. If local UPDATE message and SHOULD NOT propose the ESP-TCP mode. If local
policy does not allow using any other mode than ESP-TCP, the HIP policy does not allow using any other mode than ESP-TCP, the HIP
skipping to change at page 6, line 43 skipping to change at page 7, line 5
3.4. Recovering from Failed Encrypted Connections 3.4. Recovering from Failed Encrypted Connections
If the encrypted connection fails for some reason, it can no longer If the encrypted connection fails for some reason, it can no longer
be used for HIP signaling and the hosts SHOULD re-establish the be used for HIP signaling and the hosts SHOULD re-establish the
connection using HIP messages that are sent outside of the encrypted connection using HIP messages that are sent outside of the encrypted
connection. Hence, while listening for incoming HIP messages on the connection. Hence, while listening for incoming HIP messages on the
encrypted connection, hosts MUST still accept incoming HIP messages encrypted connection, hosts MUST still accept incoming HIP messages
using the same transport method (e.g., UDP or plain IP) that was used using the same transport method (e.g., UDP or plain IP) that was used
for the base exchange. When responding to a HIP message sent outside for the base exchange. When responding to a HIP message sent outside
of encrypted connection, the response MUST be sent using the same of encrypted connection, the response MUST be sent using the same
transport method as the original message used. transport method as the original message used. Hosts SHOULD send
outside of the encrypted connection only HIP messages that are used
to reestablish the encrypted connection. Especially, messages that
are intended to be sent only encrypted (e.g., DATA messages using an
encrypted transport mode) MUST NOT be sent before the encrypted
connection is reestablished.
The UPDATE messages used for re-establishing the encrypted connection The UPDATE messages used for re-establishing the encrypted connection
MUST contain a HIP_TRANSPORT_MODE parameter and the negotiation MUST contain a HIP_TRANSPORT_MODE parameter and the negotiation
proceeds as described in Section 3.2. proceeds as described in Section 3.2.
3.5. Host Mobility 3.5. Host Mobility
If the host's address changes, it may not be able to send the If the host's address changes, it may not be able to send the
mobility UPDATE messages using the encrypted connection before it mobility UPDATE messages using the encrypted connection before it
breaks. This results in a similar situation as if the encrypted breaks. This results in a similar situation as if the encrypted
skipping to change at page 7, line 20 skipping to change at page 7, line 36
4. Notify Packet Types 4. Notify Packet Types
The new Notify Packet Type [RFC5201] defined in this document is The new Notify Packet Type [RFC5201] defined in this document is
shown below. The Notification Data field for the error notifications shown below. The Notification Data field for the error notifications
SHOULD contain the HIP header of the rejected packet. SHOULD contain the HIP header of the rejected packet.
NOTIFICATION PARAMETER - ERROR TYPES Value NOTIFICATION PARAMETER - ERROR TYPES Value
------------------------------------ ----- ------------------------------------ -----
NO_VALID_HIP_TRANSPORT_MODE 70 NO_VALID_HIP_TRANSPORT_MODE [TBD by IANA;100]
If a host sends UPDATE message that does not have any transport If a host sends an UPDATE message that does not have any transport
mode the receiving host is willing to use, it sends back a NOTIFY mode the receiving host is willing to use, the receiving host
error packet with this type. sends back a NOTIFY error packet with this type.
5. Security Considerations 5. Security Considerations
By exchanging the HIP messages over ESP connection, all HIP signaling By exchanging the HIP messages over ESP connection, all HIP signaling
data (after the base exchange) will be encrypted, but only if NULL data (after the base exchange but excluding keying material
encryption is not used. Thus, host requiring confidentiality for the (re)negotiation) will be encrypted, but only if NULL encryption is
HIP signaling messages must check that encryption is negotiated to be not used. Thus, a host requiring confidentiality for the HIP
used on the ESP connection. signaling messages must check that encryption is negotiated to be
used on the ESP connection. Moreover, the level of protection
provided by the ESP transport modes depends on the selected ESP
transform; see [RFC5202] and [RFC4303] for security considerations of
the different ESP transforms.
6. Acknowledgements 6. Acknowledgements
Thanks to Gonzalo Camarillo, Kristian Slavov, Tom Henderson, Miika Thanks to Gonzalo Camarillo, Kristian Slavov, Tom Henderson, Miika
Komu, and Jan Melen for comments on the draft. Komu, and Jan Melen for comments on the draft.
7. IANA Considerations 7. IANA Considerations
This section is to be interpreted according to [RFC5226]. This section is to be interpreted according to [RFC5226].
skipping to change at page 8, line 11 skipping to change at page 8, line 29
HIP_TRANSPORT_MODE parameter (defined in Section 3.1). HIP_TRANSPORT_MODE parameter (defined in Section 3.1).
The HIP_TRANSPORT_MODE parameter has 16-bit unsigned integer fields The HIP_TRANSPORT_MODE parameter has 16-bit unsigned integer fields
for different modes, for which IANA is to create and maintain a new for different modes, for which IANA is to create and maintain a new
sub-registry entitled "HIP Transport Modes" under the "Host Identity sub-registry entitled "HIP Transport Modes" under the "Host Identity
Protocol (HIP) Parameters" registry. Initial values for the Protocol (HIP) Parameters" registry. Initial values for the
transport mode registry are given in Section 3.1; future assignments transport mode registry are given in Section 3.1; future assignments
are to be made through IETF Review [RFC5226]. Assignments consist of are to be made through IETF Review [RFC5226]. Assignments consist of
a transport mode identifier name and its associated value. a transport mode identifier name and its associated value.
This document also defines new HIP Notify Packet Type [RFC5201]
NO_VALID_HIP_TRANSPORT_MODE in Section 4.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5201] Moskowitz, R., Nikander, P., Jokela, P., and T. Henderson, [RFC5201] Moskowitz, R., Nikander, P., Jokela, P., and T. Henderson,
"Host Identity Protocol", RFC 5201, April 2008. "Host Identity Protocol", RFC 5201, April 2008.
[RFC5202] Jokela, P., Moskowitz, R., and P. Nikander, "Using the [RFC5202] Jokela, P., Moskowitz, R., and P. Nikander, "Using the
Encapsulating Security Payload (ESP) Transport Format with Encapsulating Security Payload (ESP) Transport Format with
the Host Identity Protocol (HIP)", RFC 5202, April 2008. the Host Identity Protocol (HIP)", RFC 5202, April 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
8.2. Informational References 8.2. Informational References
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005.
[RFC5204] Laganier, J. and L. Eggert, "Host Identity Protocol (HIP) [RFC5204] Laganier, J. and L. Eggert, "Host Identity Protocol (HIP)
Rendezvous Extension", RFC 5204, April 2008. Rendezvous Extension", RFC 5204, April 2008.
[RFC5770] Komu, M., Henderson, T., Tschofenig, H., Melen, J., and A. [RFC5770] Komu, M., Henderson, T., Tschofenig, H., Melen, J., and A.
Keranen, "Basic Host Identity Protocol (HIP) Extensions Keranen, "Basic Host Identity Protocol (HIP) Extensions
for Traversal of Network Address Translators", RFC 5770, for Traversal of Network Address Translators", RFC 5770,
April 2010. April 2010.
[I-D.ietf-hip-cert] [I-D.ietf-hip-cert]
Heer, T. and S. Varjonen, "HIP Certificates", Heer, T. and S. Varjonen, "HIP Certificates",
draft-ietf-hip-cert-03 (work in progress), April 2010. draft-ietf-hip-cert-04 (work in progress), September 2010.
[I-D.ietf-hip-hiccups] [I-D.ietf-hip-hiccups]
Camarillo, G. and J. Melen, "HIP (Host Identity Protocol) Camarillo, G. and J. Melen, "HIP (Host Identity Protocol)
Immediate Carriage and Conveyance of Upper- layer Protocol Immediate Carriage and Conveyance of Upper- layer Protocol
Signaling (HICCUPS)", draft-ietf-hip-hiccups-03 (work in Signaling (HICCUPS)", draft-ietf-hip-hiccups-05 (work in
progress), July 2010. progress), July 2010.
Author's Address Author's Address
Ari Keranen Ari Keranen
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
02420 Jorvas 02420 Jorvas
Finland Finland
 End of changes. 24 change blocks. 
36 lines changed or deleted 61 lines changed or added

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