draft-ietf-hip-over-hip-00.txt   draft-ietf-hip-over-hip-01.txt 
HIP Working Group A. Keranen HIP Working Group A. Keranen
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Experimental April 14, 2010 Intended status: Experimental July 12, 2010
Expires: October 16, 2010 Expires: January 13, 2011
Host Identity Protocol Signaling Message Transport Modes Host Identity Protocol Signaling Message Transport Modes
draft-ietf-hip-over-hip-00 draft-ietf-hip-over-hip-01
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 signaling messages that allow conveying them over encrypted
connections initiated with the Host Identity Protocol. 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
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 October 16, 2010. This Internet-Draft will expire on January 13, 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 3, line 10 skipping to change at page 3, line 10
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 . . . . . . . . . . . . . . . . . 8
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 [I-D.ietf-hip-nat-traversal]. When two hosts perform a HIP traversal [RFC5770]. When two hosts perform a HIP base exchange,
base exchange, they set up an encrypted connection between them for they set up an encrypted connection between them for data traffic,
data traffic, but continue to use plain IP or UDP for HIP signaling but continue to use plain IP or UDP for HIP signaling messages.
messages.
This document defines how the encrypted connection can be used also This document defines how the encrypted connection can be used also
for HIP signaling messages. Two different modes are defined: HIP for HIP signaling messages. Two different modes are defined: HIP
over Encapsulating Security Payload (ESP) and HIP over TCP. The over Encapsulating Security Payload (ESP) and HIP over TCP. The
benefit of sending HIP messages over ESP is that all signaling benefit of sending HIP messages over ESP is that all signaling
traffic (including HIP headers) will be encrypted. If HIP messages traffic (including HIP headers) will be encrypted. If HIP messages
are sent over TCP (which in turn is transported over ESP), TCP can are sent over TCP (which in turn is transported over ESP), TCP can
handle also message fragmentation where needed. handle also message fragmentation where needed.
2. Terminology 2. Terminology
skipping to change at page 4, line 26 skipping to change at page 4, line 26
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; 990 ] 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
skipping to change at page 7, line 7 skipping to change at page 7, line 7
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
connection had failed and the hosts need to re-negotiate the new connection had failed and the hosts need to re-negotiate the new
addresses using un-encrypted UPDATE messages and possibly rendezvous addresses using un-encrypted UPDATE messages and possibly rendezvous
[RFC5204] or HIP relay [I-D.ietf-hip-nat-traversal] servers. Also [RFC5204] or HIP relay [RFC5770] servers. Also these UPDATE messages
these UPDATE messages MUST contain the HIP_TRANSPORT_MODE parameter MUST contain the HIP_TRANSPORT_MODE parameter and perform the
and perform the transport mode negotiation. transport mode negotiation.
4. Notify Packet Types 4. Notify Packet Types
The new Notify Packet Types [RFC5201] defined in this document are 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 70
If a host sends UPDATE message that does not have any transport If a host sends 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, it sends back a NOTIFY
skipping to change at page 8, line 34 skipping to change at page 8, line 34
[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
[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.
[I-D.ietf-hip-nat-traversal] [RFC5770] Komu, M., Henderson, T., Tschofenig, H., Melen, J., and A.
Komu, M., Henderson, T., Tschofenig, H., Melen, J., and A. Keranen, "Basic Host Identity Protocol (HIP) Extensions
Keranen, "Basic HIP Extensions for Traversal of Network for Traversal of Network Address Translators", RFC 5770,
Address Translators", draft-ietf-hip-nat-traversal-09 April 2010.
(work in progress), October 2009.
[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-02 (work in progress), October 2009. draft-ietf-hip-cert-03 (work in progress), April 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-02 (work in Signaling (HICCUPS)", draft-ietf-hip-hiccups-03 (work in
progress), March 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
Email: Ari.Keranen@ericsson.com Email: Ari.Keranen@ericsson.com
 End of changes. 10 change blocks. 
22 lines changed or deleted 20 lines changed or added

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