[DNA-BOF] Re: [mobile-ip] Announce: BoF Proposal: Detecting Network Attachment

[Jari Arkko <jari.arkko@kolumbus.fi>]

Greg,

This looks like a great description for a BoF. Thanks!

Some inline comments below:

> There has been some interest in various IETF WGs
> regarding what to do when attaching to a network,
> and how to distinguish if a host has attached to
> a currently configured network or a new one.
> 
> In mobile-ip WG this is largely tackled because of
> the need to detect movement quickly.
> 
> There is currently a BoF proposed for IETF57 which
> aims to discuss issues uncovered in DHC, Mobile-IP
> and Zeroconf WGs.  The hope is that getting together
> people from these (and other) groups who are interested
> in the problems may lead to a unified approach
> to these problems (or at least only one approach each
> for IPv4 and IPv6).

I suspect v4 md and v6 md are parallel, mostly independent
processes. There might be some joint probing and l2 assist
going on, though. In any case, a roaming DHCP user should
be able to use md such that he gets either v4, v6, or both
depending on availability.

> Here is the proposed BoF's description:
> 
> 
> Detecting Network Attachment (DNA) Proposed BoF Description:
> 
> Network Attachment occurs when a host arrives on a new
> IP subnet.  When attaching to a network, a host either
> already has a valid configuration for this subnet or
> must configure addresses.  A host determines whether
> it requires additional configuration by Detecting Network
> Attachment.
> 
> When a host has existing upper layer protocols sessions,
> it is important to receive a timely indication that
> attachment has occurred.  This may be the case if a host
> is connected intermittently, is moving or has urgent data
> to transmit upon attachment to a link.
> 
> For these nodes, it is also important detect if an acquired
> link is new, or has already been visited. This information
> may be used to distinguish between events where
> configuration must be initiated, or a host already has
> valid configuration.

Interesting... For example, an address we used a while
ago on this link could be reused? Would DAD still
need to be run, or can we avoid that if we did it on the
first time we arrived at that link?

> This meeting hopes to providing a forum for those
> interested in developing generic attachment detection
> technologies for IPv4 and IPv6.
> 
> The BOF aims to:
> 
> * Describe existing issues encountered in DHC, ZEROCONF
>   and Mobileip WGs, which could benefit from work on
>   detecting network attachment.

Hmm... I don't see IPv6 WG mentioned above. Does this imply that
movement issues related to stateless autoconfiguration are
out of scope, but stateful autoconfiguration is in?

> * Define the problem scope, and environments where network
>   attachment detection is desirable.

Scope has to be defined. Can you give an example of
what "environment" would mean in this case? Some properties
of link layers perhaps?

> * Determine if sufficient interest exists to form a
>   Working Group on this topic.

Ok.

> * Reach consensus on the area of work for a potential WG,
>   including which problems are outside scope.

This is the interesting question.

--Jari