< draft-tschofenig-hiprg-host-identities-04.txt		draft-tschofenig-hiprg-host-identities-05.txt >
	HIPRG H. Tschofenig		HIPRG H. Tschofenig
	Internet-Draft Siemens Networks GmbH & Co KG		Internet-Draft Nokia Siemens Networks
	Intended status: Informational J. Ott		Expires: December 19, 2007 J. Ott
	Expires: April 26, 2007 Helsinki University of Technology		Helsinki University of Technology
	H. Schulzrinne		H. Schulzrinne
	Columbia U.		Columbia U.
	T. Henderson		T. Henderson
	The Boeing Company		The Boeing Company
	G. Camarillo		G. Camarillo
	Ericsson		Ericsson
	October 23, 2006		June 17, 2007
	Interaction between SIP and HIP		Interaction between SIP and HIP
	draft-tschofenig-hiprg-host-identities-04.txt		draft-tschofenig-hiprg-host-identities-05.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of 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
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 April 26, 2007.		This Internet-Draft will expire on December 19, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document investigates the interworking between the Session		This document investigates the interworking between the Session
	Initiation Protocol (SIP) and the Host Identity Protocol (HIP) and		Initiation Protocol (SIP) and the Host Identity Protocol (HIP) and
	the benefits that may arise from their combined operation.		the benefits that may arise from their combined operation.
	The aspect of exchanging Host Identities (or Host Identity Tags) in		The aspect of exchanging Host Identities (or Host Identity Tags) in
	SIP/SDP for later usage with the Host Identity Protocol Protocol		SIP/SDP for later usage with the Host Identity Protocol Protocol
	(HIP) is described in more detail as an example of this interworking.		(HIP) is described in more detail as an example of this interworking.
	skipping to change at page 4, line 19 ¶		skipping to change at page 4, line 19 ¶
	transport protocols are not used in SIP user data flows.		transport protocols are not used in SIP user data flows.
	Middlebox Traversal:		Middlebox Traversal:
	The work on traversing Network Address Translators with SIP and		The work on traversing Network Address Translators with SIP and
	media traffic has focused on MIDCOM and the Interactive		media traffic has focused on MIDCOM and the Interactive
	Connectivity Establishment (ICE) methodology. ICE relies on other		Connectivity Establishment (ICE) methodology. ICE relies on other
	protocols, such as STUN [13] and TURN [14] in order to create a		protocols, such as STUN [13] and TURN [14] in order to create a
	NAT binding.		NAT binding.
	HIP might be better suited for the traversal of HIP-aware NATs,		HIP may provide an alternative way to traverse HIP-aware NATs,
	since, in this setting, the NATs can inspect the HIP signaling		since, in this setting, the NATs can inspect the HIP signaling
	exchange and create the necessary bindings. This approach is		exchange and create the necessary bindings. This approach is
	similar to the one proposed by the NSIS working group where a		similar to the one proposed by the NSIS working group where a
	path-coupled signaling protocol is used to interact with these		path-coupled signaling protocol is used to interact with these
	middleboxes to create NAT bindings (and firewall pin-holes). The		middleboxes to create NAT bindings (and firewall pin-holes). The
	NATFW-NSLP [15] is a protocol proposal that utilizes the NSIS		NATFW-NSLP [15] is a protocol proposal that utilizes the NSIS
	protocol suite. The travesal of HIP unaware NATs is detailed in		protocol suite. The travesal of HIP unaware NATs is detailed in
	[16] and a discussion about NAT and firewall traversal of HIP-		[16] and a discussion about NAT and firewall traversal of HIP-
	aware devices is given in [17].		aware devices is given in [17].
	skipping to change at page 26, line 9 ¶		skipping to change at page 26, line 9 ¶
	Murugaraj Shanmugam, Franz Muenz, Jochen Grimminger and Joachim Kross		Murugaraj Shanmugam, Franz Muenz, Jochen Grimminger and Joachim Kross
	for their feedback.		for their feedback.
	The content of the security consideration section is based on DTLS-		The content of the security consideration section is based on DTLS-
	SIP.		SIP.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,		[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
	Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:		Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
	Session Initiation Protocol", RFC 3261, June 2002.		Session Initiation Protocol", RFC 3261, June 2002.
	[2] Moskowitz, R. and P. Nikander, "Host Identity Protocol		[2] Moskowitz, R. and P. Nikander, "Host Identity Protocol
	Architecture", draft-ietf-hip-arch-03 (work in progress),		Architecture", draft-ietf-hip-arch-03 (work in progress),
	August 2005.		August 2005.
	[3] Moskowitz, R., "Host Identity Protocol", draft-ietf-hip-base-06		[3] Moskowitz, R., "Host Identity Protocol", draft-ietf-hip-base-08
	(work in progress), June 2006.		(work in progress), June 2007.
	[4] Schulzrinne, H. and E. Wedlund, "Application-Layer Mobility		[4] Schulzrinne, H. and E. Wedlund, "Application-Layer Mobility
	using SIP, ACM MC2R", , July 2000.		using SIP, ACM MC2R", , July 2000.
	[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", March 1997.		Levels", March 1997.
	[6] Andreasen, F., "Session Description Protocol Security		[6] Andreasen, F., "Session Description Protocol Security
	Descriptions for Media Streams",		Descriptions for Media Streams",
	draft-ietf-mmusic-sdescriptions-12 (work in progress),		draft-ietf-mmusic-sdescriptions-12 (work in progress),
	September 2005.		September 2005.
	[7] Arkko, J., "Key Management Extensions for Session Description		[7] Arkko, J., "Key Management Extensions for Session Description
	Protocol (SDP) and Real Time Streaming Protocol (RTSP)",		Protocol (SDP) and Real Time Streaming Protocol (RTSP)",
	draft-ietf-mmusic-kmgmt-ext-15 (work in progress), June 2005.		draft-ietf-mmusic-kmgmt-ext-15 (work in progress), June 2005.
	[8] Handley, M. and V. Jacobson, "SDP: Session Description		[8] Handley, M. and V. Jacobson, "SDP: Session Description
	Protocol", RFC 2327, April 1998.		Protocol", RFC 2327, April 1998.
	9.2. Informative References		9.2. Informative References
	[9] Sparks, R., "The Session Initiation Protocol (SIP) Refer		[9] Sparks, R., "The Session Initiation Protocol (SIP) Refer
	Method", RFC 3515, April 2003.		Method", RFC 3515, April 2003.
	[10] Shacham, R., "Session Initiation Protocol (SIP) Session		[10] Shacham, R., "Session Initiation Protocol (SIP) Session
	Mobility", draft-shacham-sipping-session-mobility-02 (work in		Mobility", draft-shacham-sipping-session-mobility-03 (work in
	progress), March 2006.		progress), November 2006.
	[11] Laganier, J. and L. Eggert, "Host Identity Protocol (HIP)		[11] Laganier, J. and L. Eggert, "Host Identity Protocol (HIP)
	Rendezvous Extension", draft-ietf-hip-rvs-05 (work in		Rendezvous Extension", draft-ietf-hip-rvs-05 (work in
	progress), June 2006.		progress), June 2006.
	[12] Nikander, P., "Host Identity Indirection Infrastructure (Hi3)",		[12] Nikander, P., "Host Identity Indirection Infrastructure (Hi3)",
	draft-nikander-hiprg-hi3-00 (work in progress), June 2004.		draft-nikander-hiprg-hi3-00 (work in progress), June 2004.
	[13] Rosenberg, J., "Simple Traversal Underneath Network Address		[13] Rosenberg, J., "Session Traversal Utilities for (NAT) (STUN)",
	Translators (NAT) (STUN)", draft-ietf-behave-rfc3489bis-04		draft-ietf-behave-rfc3489bis-06 (work in progress), March 2007.
	(work in progress), July 2006.
	[14] Rosenberg, J., "Traversal Using Relay NAT (TURN)",		[14] Rosenberg, J., "Obtaining Relay Addresses from Simple Traversal
	draft-rosenberg-midcom-turn-08 (work in progress),		Underneath NAT (STUN)", draft-ietf-behave-turn-03 (work in
	September 2005.		progress), March 2007.
	[15] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol		[15] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol
	(NSLP)", draft-ietf-nsis-nslp-natfw-12 (work in progress),		(NSLP)", draft-ietf-nsis-nslp-natfw-14 (work in progress),
	June 2006.		March 2007.
	[16] Stiemerling, M., "Middlebox Traversal Issues of Host Identity		[16] Schmitt, V., "HIP Extensions for the Traversal of Network
	Protocol (HIP) Communication", draft-stiemerling-hip-nat-05		Address Translators", draft-ietf-hip-nat-traversal-01 (work in
	(work in progress), July 2005.		progress), March 2007.
	[17] Tschofenig, H. and M. Shanmugam, "Traversing HIP-aware NATs and		[17] Tschofenig, H. and M. Shanmugam, "Traversing HIP-aware NATs and
	Firewalls: Problem Statement and Requirements",		Firewalls: Problem Statement and Requirements",
	draft-tschofenig-hiprg-hip-natfw-traversal-04 (work in		draft-tschofenig-hiprg-hip-natfw-traversal-05 (work in
	progress), March 2006.		progress), October 2006.
	[18] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A		[18] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A
	Methodology for Network Address Translator (NAT) Traversal for		Protocol for Network Address Translator (NAT) Traversal for
	Offer/Answer Protocols", draft-ietf-mmusic-ice-11 (work in		Offer/Answer Protocols", draft-ietf-mmusic-ice-16 (work in
	progress), October 2006.		progress), June 2007.
	[19] Jokela, P., "Using ESP transport format with HIP",		[19] Jokela, P., "Using ESP transport format with HIP",
	draft-ietf-hip-esp-04 (work in progress), October 2006.		draft-ietf-hip-esp-06 (work in progress), June 2007.
	[20] Tschofenig, H., "Using SRTP transport format with HIP",		[20] Tschofenig, H., "Using SRTP transport format with HIP",
	draft-tschofenig-hiprg-hip-srtp-01 (work in progress),		draft-tschofenig-hiprg-hip-srtp-02 (work in progress),
	October 2005.		October 2006.
	[21] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K.		[21] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K.
	Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830,		Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830,
	August 2004.		August 2004.
	[22] Handley, M., "SDP: Session Description Protocol",		[22] Handley, M., "SDP: Session Description Protocol",
	draft-ietf-mmusic-sdp-new-26 (work in progress), January 2006.		draft-ietf-mmusic-sdp-new-26 (work in progress), January 2006.
	[23] Peterson, J. and C. Jennings, "Enhancements for Authenticated		[23] Peterson, J. and C. Jennings, "Enhancements for Authenticated
	Identity Management in the Session Initiation Protocol (SIP)",		Identity Management in the Session Initiation Protocol (SIP)",
	draft-ietf-sip-identity-06 (work in progress), October 2005.		RFC 4474, August 2006.
	[24] Bradner, S., Mankin, A., and J. Schiller, "A Framework for		[24] Bradner, S., Mankin, A., and J. Schiller, "A Framework for
	Purpose-Built Keys (PBK)", draft-bradner-pbk-frame-06 (work in		Purpose-Built Keys (PBK)", draft-bradner-pbk-frame-06 (work in
	progress), June 2003.		progress), June 2003.
	[25] Jennings, C. and J. Peterson, "Certificate Management Service		[25] Jennings, C., "Certificate Management Service for The Session
	for The Session Initiation Protocol (SIP)",		Initiation Protocol (SIP)", draft-ietf-sip-certs-03 (work in
	draft-ietf-sipping-certs-03 (work in progress), March 2006.		progress), March 2007.
	Authors' Addresses		Authors' Addresses
	Hannes Tschofenig		Hannes Tschofenig
	Siemens Networks GmbH & Co KG		Nokia Siemens Networks
	Otto-Hahn-Ring 6		Otto-Hahn-Ring 6
	Munich, Bavaria 81739		Munich, Bavaria 81739
	Germany		Germany
	Phone: +49 89 636 40390		Phone: +49 89 636 40390
	Email: Hannes.Tschofenig@siemens.com		Email: Hannes.Tschofenig@nsn.com
	URI: http://www.tschofenig.com		URI: http://www.tschofenig.com
	Joerg Ott		Joerg Ott
	Helsinki University of Technology		Helsinki University of Technology
	Otakaari 5A		Otakaari 5A
	Espoo FI-02150		Espoo FI-02150
	Finland		Finland
	Email: jo@netlab.hut.fi		Email: jo@netlab.hut.fi
	skipping to change at page 31, line 7 ¶		skipping to change at page 31, line 7 ¶
	Gonzalo Camarillo		Gonzalo Camarillo
	Ericsson		Ericsson
	Hirsalantie 11		Hirsalantie 11
	Jorvas 02420		Jorvas 02420
	Finland		Finland
	Email: Gonzalo.Camarillo@ericsson.com		Email: Gonzalo.Camarillo@ericsson.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property		Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
End of changes. 29 change blocks.
	62 lines changed or deleted		61 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/