< draft-tschofenig-hiprg-host-identities-03.txt		draft-tschofenig-hiprg-host-identities-04.txt >
	HIPRG H. Tschofenig		HIPRG H. Tschofenig
	Internet-Draft Siemens		Internet-Draft Siemens Networks GmbH & Co KG
	Expires: September 7, 2006 J. Ott		Intended status: Informational J. Ott
	Helsinki University of Technology		Expires: April 26, 2007 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
	March 6, 2006		October 23, 2006
	Interaction between SIP and HIP		Interaction between SIP and HIP
	draft-tschofenig-hiprg-host-identities-03.txt		draft-tschofenig-hiprg-host-identities-04.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 September 7, 2006.		This Internet-Draft will expire on April 26, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	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.
	skipping to change at page 7, line 43 ¶		skipping to change at page 7, line 43 ¶
	+-----------+ SIP and HIP +-----------+		+-----------+ SIP and HIP +-----------+
	|SIP | <---------------------------------> |SIP |		|SIP | <---------------------------------> |SIP |
	|User Agent | RTP |User Agent |		|User Agent | RTP |User Agent |
	|Alice | <=================================> |Bob |		|Alice | <=================================> |Bob |
	+-----------+ +-----------+		+-----------+ +-----------+
	Legend:		Legend:
	<--->: Signaling Traffic		<--->: Signaling Traffic
	<===>: Data Traffic		<===>: Data Traffic
	Figure 1: SIP Trapezoid		Figure 1: SIP Trapezoid
	The initial SIP signaling messages between Alice and Bob often take		The initial SIP signaling messages between Alice and Bob often take
	place via the proxy servers. This exchange may be protected with TLS		place via the proxy servers. This exchange may be protected with TLS
	(between SIP proxies but also between SIP UAs and SIP proxies) or		(between SIP proxies but also between SIP UAs and SIP proxies) or
	with SIP digest authentication between SIP UAs and the outbound		with SIP digest authentication between SIP UAs and the outbound
	proxy. Further SIP security mechanisms should be used in combination		proxy. Further SIP security mechanisms should be used in combination
	with this proposal. The security consideration section, see		with this proposal. The security consideration section, see
	Section 4, provides a discussion about the possible approaches to		Section 4, provides a discussion about the possible approaches to
	secure the Host Identity Tag and to relate it ongoing session.		secure the Host Identity Tag and to relate it ongoing session.
	skipping to change at page 26, line 17 ¶		skipping to change at page 26, line 17 ¶
	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-05		[3] Moskowitz, R., "Host Identity Protocol", draft-ietf-hip-base-06
	(work in progress), March 2006.		(work in progress), June 2006.
	[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),
	skipping to change at page 26, line 44 ¶		skipping to change at page 26, line 44 ¶
	[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-01 (work in		Mobility", draft-shacham-sipping-session-mobility-02 (work in
	progress), July 2005.		progress), March 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-04 (work in		Rendezvous Extension", draft-ietf-hip-rvs-05 (work in
	progress), October 2005.		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 of UDP Through Network Address		[13] Rosenberg, J., "Simple Traversal Underneath Network Address
	Translators (NAT) (STUN)", draft-ietf-behave-rfc3489bis-02		Translators (NAT) (STUN)", draft-ietf-behave-rfc3489bis-04
	(work in progress), July 2005.		(work in progress), July 2006.
	[14] Rosenberg, J., "Traversal Using Relay NAT (TURN)",		[14] Rosenberg, J., "Traversal Using Relay NAT (TURN)",
	draft-rosenberg-midcom-turn-08 (work in progress),		draft-rosenberg-midcom-turn-08 (work in progress),
	September 2005.		September 2005.
	[15] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol		[15] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol
	(NSLP)", draft-ietf-nsis-nslp-natfw-09 (work in progress),		(NSLP)", draft-ietf-nsis-nslp-natfw-12 (work in progress),
	February 2006.		June 2006.
	[16] Stiemerling, M., "Middlebox Traversal Issues of Host Identity		[16] Stiemerling, M., "Middlebox Traversal Issues of Host Identity
	Protocol (HIP) Communication", draft-stiemerling-hip-nat-05		Protocol (HIP) Communication", draft-stiemerling-hip-nat-05
	(work in progress), July 2005.		(work in progress), July 2005.
	[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-03 (work in		draft-tschofenig-hiprg-hip-natfw-traversal-04 (work in
	progress), October 2005.		progress), March 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		Methodology for Network Address Translator (NAT) Traversal for
	Offer/Answer Protocols", draft-ietf-mmusic-ice-06 (work in		Offer/Answer Protocols", draft-ietf-mmusic-ice-11 (work in
	progress), October 2005.		progress), October 2006.
	[19] Jokela, P., "Using ESP transport format with HIP",		[19] Jokela, P., "Using ESP transport format with HIP",
	draft-ietf-hip-esp-02 (work in progress), March 2006.		draft-ietf-hip-esp-04 (work in progress), October 2006.
	[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-01 (work in progress),
	October 2005.		October 2005.
	[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",
	skipping to change at page 28, line 7 ¶		skipping to change at page 28, line 7 ¶
	[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.		draft-ietf-sip-identity-06 (work in progress), October 2005.
	[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. and J. Peterson, "Certificate Management Service
	for The Session Initiation Protocol (SIP)",		for The Session Initiation Protocol (SIP)",
	draft-ietf-sipping-certs-02 (work in progress), July 2005.		draft-ietf-sipping-certs-03 (work in progress), March 2006.
	Authors' Addresses		Authors' Addresses
	Hannes Tschofenig		Hannes Tschofenig
	Siemens		Siemens Networks GmbH & Co KG
	Otto-Hahn-Ring 6		Otto-Hahn-Ring 6
	Munich, Bavaria 81739		Munich, Bavaria 81739
	Germany		Germany
			Phone: +49 89 636 40390
	Email: Hannes.Tschofenig@siemens.com		Email: Hannes.Tschofenig@siemens.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
	Henning Schulzrinne		Henning Schulzrinne
	skipping to change at page 31, line 5 ¶		skipping to change at page 31, line 5 ¶
	Email: thomas.r.henderson@boeing.com		Email: thomas.r.henderson@boeing.com
	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
	Intellectual Property Statement		Full Copyright Statement
			Copyright (C) The Internet Society (2006).
			This document is subject to the rights, licenses and restrictions
			contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
			This document and the information contained herein are provided on an
			"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
			OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
			ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
			INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
			INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
			WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			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
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 31, line 29 ¶		skipping to change at page 31, line 45 ¶
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement
	Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 20 change blocks.
	42 lines changed or deleted		44 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/