Re: Some definitions (Was: Re: New issue 16: No packets from other end?)

Vijay Devarapalli <[email protected]>
Newsgroups gmane.ietf.mobike
Message-ID <[email protected]>
Hello Jari,

a nice writeup. thanks. one comment below.

Jari Arkko wrote:

> Details:
> 
> 1.  Available Addresses
> 
>    MOBIKE nodes need to be aware of what addresses they themselves have.
>    If a node loses the address it is currently using for communications,
>    another address must replace this address. And if a node loses an
>    address that the node's peer knows about, the peer must be informed.
>    Similarly, when a node acquires a new address it may generally wish
>    the peer to know about it.
> 
>    Definition. Available address. An address is said to be available if
>    the following conditions are fulfilled:
> 
>    o  The address has been assigned to an interface of the node.
> 
>    o  If the address is an IPv6 address, we additionally require that
>       (a) the address is valid in the sense of RFC 2461, and that
>       (b) the address is not tentative in the sense of RFC 2462.  In
>       other words, the address assignment is complete so that
>       communications can be started.
> 
>       Note this explicitly allows an address to be optimistic in the
>       sense of [draft-ietf-ipv6-optimistic-dad] even though
>       implementations are probably better off using other
>       addresses as long as there is an alternative.
> 
>    o  The address is a global unicast or unique site-local address
>       [draft-ietf-ipv6-unique-local-addr].
> 
>       That is, it is not an IPv6 link-local or site-local address.
>       Where IPv4 is considered, it is not an RFC 1918 address.
> 
>    Available addresses are discovered and monitored through mechanisms
>    outside the scope of MOBIKE.  These mechanisms include IPv6
>    Neighbor Discovery and Address Autoconfiguration [RFC 2461-2462],
>    DHCP [RFC 3315], enhanced network detection mechanisms detected by
>    the DNA working group, and corresponding IPv4 mechanisms, such as
>    [draft-ietf-dhc-dna-ipv4].

this doesnt take into account some addresses that satisfy the above
conditions, but are restricted by certain policies on the MN. for
example, in an earlier mail, I had explained a scenario where I didnt
want MOBIKE to use an address configured from a low bandwidth GPRS
link to download email through a VPN tunnel.

Vijay
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.