Alper, This is a good architecture for an API. But if Samita and others are willing to build an API spec for Mobile IP in the IETF using base BSD sockets that is a good idea.
As far as your comment about src addr selection I don't buy it without seeing real code. That is why we need this api draft. /jim [Honor, Commitment, Integrity] > -----Original Message----- > From: Alper E. YEGIN [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 21, 2002 9:56 AM > To: Samita Chakrabarti; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: Proposal for MIPv6 APIs to switch default source > address selection > > > > > > > I am looking into possible MIPv6 APIs as an extension to > IPv6 Adv-API > > document. The following requirements in MIPv6 spec indicates that > > there is a need for Socket API which will allow the MIPv6 > applications > > to choose COA as mobile node's source address (in a visited > network), > > while default > > address selection draft prefers home address as the default source > > address > > (section 5 and 6 rule 4). The MIPV6 API should also take care of > > choosing > > temporary address and non-temporary address from the > application level. > > Hi Samita, > > Please see our Mobile IP API draft: > > http://www.ietf.org/internet-drafts/draft-yokote-mobileip-api-01.txt > > It allows the user of the API to determine home addresses and > the corresponding care-of addresses used on the host. Than, > it's the application's choice to pick one of them. It can > make an appropriate decision by using this knowledge. > > I think this selection logic should reside in the > application, not below. So, I'm not sure if this really > relates to draft-ietf-ipv6-default-addr-select draft. > > alper > > > > > Also, there is a need to choose link-local or site-local address as > > source address (depending on the scope) for the MN while > visiting (see > > below). > > > > My question is, if anybody in IPv6 working group is > currently working > > on such API for default address selection draft ? > > > > If not, I propose to add these APIs to the MIPv6 Advanced API > > document, as they are quite Mobile IP specific in usage. > > > > -Samita > > > > -------------------------------------------------------------------- > > > > > > > > Mobile IPv6 draft 19 Section 11.3.1 states, > > > > The mobile node MAY choose to directly use one of its care-of > > addresses as the source of the packet, not requiring the use > > of a Home Address option in the packet. This is particularly > > useful for short-term communication that may easily > be retried > > if it fails. An example of this type of communication might > > be DNS queries sent by the mobile node [27, 28]. Using the > > mobile node's care-of address as the source for such > queries will > > generally have a lower overhead than using the mobile node's > > home address, since no extra options need be used in either > > the query or its reply. Such packets can be routed normally, > > directly between their source and destination without relying > > on Mobile IPv6. If application running on the > mobile node has > > no particular knowledge that the communication being > sent fits > > within this general type of communication, however, > the mobile > > node SHOULD NOT use its care-of address as the source of the > > packet in this way. > > > > : : : > > > > While not at its home link, the mobile node MUST NOT > use its home > > address (or the home address destination option) in Neighbor > > Discovery messages on the visited link. The mobile node also > > MUST NOT use its home address when communicating > with link-local > > or site-local peers on the visited link, if the > scope of the home > > address is larger than the scope of the peer's address. > > -------------------------------------------------------------------- > > IETF IPng Working Group Mailing List > > IPng Home Page: http://playground.sun.com/ipng > > FTP archive: ftp://playground.sun.com/pub/ipng > > Direct all administrative requests to [EMAIL PROTECTED] > > -------------------------------------------------------------------- > > > > -------------------------------------------------------------------- > IETF IPng Working Group Mailing List > IPng Home Page: http://playground.sun.com/ipng > FTP archive: ftp://playground.sun.com/pub/ipng > Direct all administrative requests to [EMAIL PROTECTED] > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
