draft-ietf-shim6-multihome-shim-api-03.txt   draft-ietf-shim6-multihome-shim-api-04.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: January 10, 2008 UC3M Expires: August 10, 2008 UC3M
K. Slavov K. Slavov
S. Sugimoto, Ed. S. Sugimoto, Ed.
Ericsson Ericsson
July 9, 2007 February 7, 2008
Socket Application Program Interface (API) for Multihoming Shim Socket Application Program Interface (API) for Multihoming Shim
draft-ietf-shim6-multihome-shim-api-03 draft-ietf-shim6-multihome-shim-api-04
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 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 10, 2008. This Internet-Draft will expire on August 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document specifies a socket API for the multihoming shim layer. This document specifies a socket API for the multihoming shim layer.
The API aims to enable interactions between the applications and the The API aims to enable interactions between the applications and the
multihoming shim layer for advanced locator management and access to multihoming shim layer for advanced locator management and access to
information about failure detection and path exploration. 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 sublayer (here after "shim") inside the IP equipped with a conceptual sublayer (here after "shim") inside the IP
skipping to change at page 4, line 20 skipping to change at page 4, line 20
environment in a host centric approach. In these protocols, a sub- environment in a host centric approach. In these protocols, a sub-
layer within the IP layer maintains mappings of identifiers and layer within the IP layer maintains mappings of identifiers and
locators. locators.
The shim layer is useful in a sense that the IP layer can maintain The shim layer is useful in a sense that the IP layer can maintain
the mapping of an identifier to corresponding locators. Under a the mapping of an identifier to corresponding locators. Under a
multihomed environment, typically, a host has more than one IP multihomed environment, typically, a host has more than one IP
address at a time. During a given transaction, a host may be address at a time. During a given transaction, a host may be
required to switch the IP address used for the communication to required to switch the IP address used for the communication to
another IP address to preserve the communication. The protocol stack another IP address to preserve the communication. The protocol stack
should take care of isolating the upper layer from distruption by the should take care of isolating the upper layer from disruption by the
address update. The shim layer can make this locator update address update. The shim layer can make this locator update
transparent to the upper layer protocols. transparent to the upper layer protocols.
In a system which is based on identifier/locator separation, upper In a system which is based on identifier/locator separation, upper
layer protocols are expected to deal with identifiers for layer protocols are expected to deal with identifiers for
establishing and handling the communications. If an application establishing and handling the communications. If an application
wants to have a multihoming support by the shim layer, the IP wants to have a multihoming support by the shim layer, the IP
addresses specified as source and destination addresses must be addresses specified as source and destination addresses must be
identifiers. However, this does not necessarily mean that identifiers. However, this does not necessarily mean that
applications are prohibited to choose specific locators in its applications are prohibited to choose specific locators in its
skipping to change at page 15, line 35 skipping to change at page 15, line 35
getsockopt(fd, SOL_SHIM, SHIM_PATHEXPLORE, &pe, &len); getsockopt(fd, SOL_SHIM, SHIM_PATHEXPLORE, &pe, &len);
5.5. SHIM_LOC_LOCAL_PREF 5.5. SHIM_LOC_LOCAL_PREF
The SHIM_LOC_LOCAL_PREF option can be used to read or set preferred The SHIM_LOC_LOCAL_PREF option can be used to read or set preferred
locator on local side within a given context. Hence this option is locator on local side within a given context. Hence this option is
effective only when there is a shim context associated with the effective only when there is a shim context associated with the
socket. socket.
Data type of the option value is a pointer to the a specific data Data type of the option value is a pointer to the specific data
structure which stores the locator information. The data structure structure which stores the locator information. The data structure
is defined in Section 7. is defined in Section 7.
By default, the option value is set as NULL, meaning that the option By default, the option value is set as NULL, meaning that the option
is disabled. is disabled.
The preferred locator can be set by setsockopt(). Verification of The preferred locator can be set by setsockopt(). Verification of
the locator shall be done by the shim layer before updating the the locator shall be done by the shim layer before updating the
preferred locator. preferred locator.
skipping to change at page 16, line 42 skipping to change at page 16, line 42
getsockopt(fd, SOL_SHIM, SHIM_LOC_LOCAL_PREF, &lc, &len); getsockopt(fd, SOL_SHIM, SHIM_LOC_LOCAL_PREF, &lc, &len);
5.6. SHIM_LOC_PEER_PREF 5.6. SHIM_LOC_PEER_PREF
The SHIM_LOC_PEER_PREF option can be used to read or set preferred The SHIM_LOC_PEER_PREF option can be used to read or set preferred
locator on peer side within a given context. Hence this option is locator on peer side within a given context. Hence this option is
effective only when there is a shim context associated with the effective only when there is a shim context associated with the
socket. socket.
Data type of the option value is a pointer to the a specific data Data type of the option value is a pointer to the specific data
structure which stores the locator information. The data structure structure which stores the locator information. The data structure
is defined in Section 7. is defined in Section 7.
By default, the option value is set as NULL, meaning that the option By default, the option value is set as NULL, meaning that the option
is disabled. is disabled.
The preferred locator can be set by setsockopt(). Necessary The preferred locator can be set by setsockopt(). Necessary
verification of the locator shall be done by the shim layer before verification of the locator shall be done by the shim layer before
updating the preferred locator. updating the preferred locator.
skipping to change at page 30, line 38 skipping to change at page 30, line 38
Tatuya Jinmei who thoroughly reviewed the early version of this draft Tatuya Jinmei who thoroughly reviewed the early version of this draft
and provided detailed comments on socket API related issues. and provided detailed comments on socket API related issues.
16. References 16. References
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-07 (work in progress), draft-ietf-shim6-failure-detection-10 (work in progress),
December 2006. January 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-07 (work in progress), protocol", draft-ietf-shim6-proto-09 (work in progress),
December 2006. October 2007.
[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 31, line 21 skipping to change at page 31, line 21
16.2. Informative References 16.2. Informative References
[I-D.ietf-shim6-app-refer] [I-D.ietf-shim6-app-refer]
Nordmark, E., "Shim6 Application Referral Issues", Nordmark, E., "Shim6 Application Referral Issues",
draft-ietf-shim6-app-refer-00 (work in progress), draft-ietf-shim6-app-refer-00 (work in progress),
July 2005. July 2005.
[I-D.ietf-shim6-hba] [I-D.ietf-shim6-hba]
Bagnulo, M., "Hash Based Addresses (HBA)", Bagnulo, M., "Hash Based Addresses (HBA)",
draft-ietf-shim6-hba-02 (work in progress), October 2006. draft-ietf-shim6-hba-05 (work in progress), December 2007.
[RFC2765] Nordmark, E., "Stateless IP/ICMP Translation Algorithm [RFC2765] Nordmark, E., "Stateless IP/ICMP Translation Algorithm
(SIIT)", RFC 2765, February 2000. (SIIT)", RFC 2765, February 2000.
[RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)",
RFC 3972, March 2005. RFC 3972, March 2005.
Appendix A. Context Forking Appendix A. Context Forking
In this section, an issue concerning context forking and its relation In this section, an issue concerning context forking and its relation
skipping to change at page 35, line 7 skipping to change at page 35, line 7
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 Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 12 change blocks. 
14 lines changed or deleted 14 lines changed or added

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