draft-ietf-shim6-multihome-shim-api-07.txt		draft-ietf-shim6-multihome-shim-api-08.txt
	SHIM6 Working Group M. Komu		SHIM6 Working Group M. Komu
	Internet-Draft HIIT		Internet-Draft HIIT
	Intended status: Informational M. Bagnulo		Intended status: Informational M. Bagnulo
	Expires: May 7, 2009 UC3M		Expires: November 8, 2009 UC3M
	K. Slavov		K. Slavov
	S. Sugimoto, Ed.		S. Sugimoto, Ed.
	Ericsson		Ericsson
	November 3, 2008		May 7, 2009
	Socket Application Program Interface (API) for Multihoming Shim		Socket Application Program Interface (API) for Multihoming Shim
	draft-ietf-shim6-multihome-shim-api-07		draft-ietf-shim6-multihome-shim-api-08
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		This Internet-Draft is submitted to IETF in full conformance with the
	applicable patent or other IPR claims of which he or she is aware		provisions of BCP 78 and BCP 79.
	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.
	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.
	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."
	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 May 7, 2009.		This Internet-Draft will expire on November 8, 2009.
			Copyright Notice
			Copyright (c) 2009 IETF Trust and the persons identified as the
			document authors. All rights reserved.
			This document is subject to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents in effect on the date of
			publication of this document (http://trustee.ietf.org/license-info).
			Please review these documents carefully, as they describe your rights
			and restrictions with respect to this document.
	Abstract		Abstract
	This document specifies sockets API extensions for the multihoming		This document specifies sockets API extensions for the multihoming
	shim layer. The API aims to enable interactions between applications		shim layer. The API aims to enable interactions between applications
	and the multihoming shim layer for advanced locator management, and		and the multihoming shim layer for advanced locator management, and
	access to information about failure detection and path exploration.		access to information about failure detection and path exploration.
	This document is based on an assumption that a multihomed host is		This document is based on an assumption that a multihomed host is
	equipped with a conceptual sub-layer (hereafter "shim") inside the IP		equipped with a conceptual sub-layer (hereafter "shim") inside the IP
	skipping to change at page 3, line 6		skipping to change at page 3, line 16
	Family . . . . . . . . . . . . . . . . . . . . . . . . . . 32		Family . . . . . . . . . . . . . . . . . . . . . . . . . . 32
	10.4. Handling of Unknown Locator Provided by Application . . . 32		10.4. Handling of Unknown Locator Provided by Application . . . 32
	11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 32		11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
	11.1. Changes from version 00 to version 01 . . . . . . . . . . 32		11.1. Changes from version 00 to version 01 . . . . . . . . . . 32
	11.2. Changes from version 01 to version 02 . . . . . . . . . . 33		11.2. Changes from version 01 to version 02 . . . . . . . . . . 33
	11.3. Changes from version 02 to version 03 . . . . . . . . . . 33		11.3. Changes from version 02 to version 03 . . . . . . . . . . 33
	11.4. Changes from version 03 to version 04 . . . . . . . . . . 33		11.4. Changes from version 03 to version 04 . . . . . . . . . . 33
	11.5. Changes from version 04 to version 05 . . . . . . . . . . 33		11.5. Changes from version 04 to version 05 . . . . . . . . . . 33
	11.6. Changes from version 05 to version 06 . . . . . . . . . . 33		11.6. Changes from version 05 to version 06 . . . . . . . . . . 33
	11.7. Changes from version 06 to version 07 . . . . . . . . . . 33		11.7. Changes from version 06 to version 07 . . . . . . . . . . 33
			11.8. Changes from version 07 to version 08 . . . . . . . . . . 33
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
	13. Security Considerations . . . . . . . . . . . . . . . . . . . 33		13. Security Considerations . . . . . . . . . . . . . . . . . . . 34
	14. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 34		14. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 34
	15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 34		15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 34
	16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34		16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34
	16.1. Normative References . . . . . . . . . . . . . . . . . . . 34		16.1. Normative References . . . . . . . . . . . . . . . . . . . 34
	16.2. Informative References . . . . . . . . . . . . . . . . . . 35		16.2. Informative References . . . . . . . . . . . . . . . . . . 35
	Appendix A. Context Forking . . . . . . . . . . . . . . . . . . . 35		Appendix A. Context Forking . . . . . . . . . . . . . . . . . . . 35
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
	Intellectual Property and Copyright Statements . . . . . . . . . . 40
	1. Introduction		1. Introduction
	HIP and SHIM6 have a commonality in their protocol design in the		HIP and SHIM6 have a commonality in their protocol design in the
	sense that the roles of an IP address as an identifier and a locator		sense that the roles of an IP address as an identifier and a locator
	are clearly distinguished. Hereafter this design principle is called		are clearly distinguished. Hereafter this design principle is called
	"identifier/locator separation" in this document. Both protocols aim		"identifier/locator separation" in this document. Both protocols aim
	to solve problems that are specific to multihoming environment in an		to solve problems that are specific to multihoming environment in an
	endhost centric approach. In these protocols, a sub-layer within the		endhost centric approach. In these protocols, a sub-layer within the
	IP layer maintains mappings of identifiers and locators.		IP layer maintains mappings of identifiers and locators.
	skipping to change at page 33, line 43		skipping to change at page 33, line 43
	11.6. Changes from version 05 to version 06		11.6. Changes from version 05 to version 06
	The followings are changes from version 04 to version 05:		The followings are changes from version 04 to version 05:
	o Updated references.		o Updated references.
	11.7. Changes from version 06 to version 07		11.7. Changes from version 06 to version 07
	The followings are changes from version 06 to version 07:		The followings are changes from version 06 to version 07:
	o Resolved editorial issues.		o Resolved editorial issues.
			11.8. Changes from version 07 to version 08
			No changes are made except for updates of the references.
	12. IANA Considerations		12. IANA Considerations
	This document contains no IANA consideration.		This document contains no IANA consideration.
	13. Security Considerations		13. Security Considerations
	This document does not specify any security mechanism for the shim		This document does not specify any security mechanism for the shim
	layer. Fundamentally, the shim layer has a potential to impose		layer. Fundamentally, the shim layer has a potential to impose
	security threats, as it changes the source and/or destination IP		security threats, as it changes the source and/or destination IP
	addresses of the IP packet being sent or received. Therefore, the		addresses of the IP packet being sent or received. Therefore, the
	skipping to change at page 35, line 4		skipping to change at page 35, line 8
	16.1. Normative References		16.1. Normative References
	[I-D.ietf-shim6-failure-detection]		[I-D.ietf-shim6-failure-detection]
	Arkko, J. and I. Beijnum, "Failure Detection and Locator		Arkko, J. and I. Beijnum, "Failure Detection and Locator
	Pair Exploration Protocol for IPv6 Multihoming",		Pair Exploration Protocol for IPv6 Multihoming",
	draft-ietf-shim6-failure-detection-13 (work in progress),		draft-ietf-shim6-failure-detection-13 (work in progress),
	June 2008.		June 2008.
	[I-D.ietf-shim6-proto]		[I-D.ietf-shim6-proto]
	Bagnulo, M. and E. Nordmark, "Level 3 multihoming shim		Bagnulo, M. and E. Nordmark, "Level 3 multihoming shim
	protocol", draft-ietf-shim6-proto-10 (work in progress),		protocol", draft-ietf-shim6-proto-12 (work in progress),
	February 2008.		February 2009.
	[POSIX] "IEEE Std. 1003.1-2001 Standard for Information Technology		[POSIX] "IEEE Std. 1003.1-2001 Standard for Information Technology
	-- Portable Operating System Interface (POSIX). Open group		-- Portable Operating System Interface (POSIX). Open group
	Technical Standard: Base Specifications, Issue 6,		Technical Standard: Base Specifications, Issue 6,
	http://www.opengroup.org/austin", December 2001.		http://www.opengroup.org/austin", December 2001.
	[RFC3542] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei,		[RFC3542] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei,
	"Advanced Sockets Application Program Interface (API) for		"Advanced Sockets Application Program Interface (API) for
	IPv6", RFC 3542, May 2003.		IPv6", RFC 3542, May 2003.
	skipping to change at page 40, line 4		skipping to change at line 1744
	Email: kristian.slavov@ericsson.com		Email: kristian.slavov@ericsson.com
	Shinta Sugimoto (editor)		Shinta Sugimoto (editor)
	Nippon Ericsson K.K.		Nippon Ericsson K.K.
	Koraku Mori Building		Koraku Mori Building
	1-4-14, Koraku, Bunkyo-ku		1-4-14, Koraku, Bunkyo-ku
	Tokyo 112-0004		Tokyo 112-0004
	Japan		Japan
	Phone: +81 3 3830 2241		Phone: +81 3 3830 2241
	Email: shinta.sugimoto@ericsson.com		Email: shinta.sugimoto@ericsson.com
	Full Copyright Statement
	Copyright (C) The IETF Trust (2008).
	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, THE IETF TRUST 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
	Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in
	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
	made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an
	attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.
End of changes. 11 change blocks.
	12 lines changed or deleted		25 lines changed or added
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/