[DNA-BOF] Draft charter now online

[Greg Daley <greg.daley@eng.monash.edu.au>]

Hi,

A draft of the charter description is now
online.  Reference to current discussions
has been made, following the layout described
in a previous post.

Additionally, work-list items are listed here,
although maybe not in the final form.

The document is available at the URL:

http://www.ctie.monash.edu.au/dna/charter.htm

I'm also attaching a copy here for reference in
the mailing list archive, as well as for people
who are not conveniently situated to view this
on the web.

Please note that subsection titles are temporary
and for the purposes of text development.

Greg


Proposed Detecting network Attachment (DNA)
Working Group Description.

Overview

Network Attachment occurs when an interface
becomes ready to send and receive IP datagrams.
This process may occur when link-layer
authentication has completed, a host comes back
into range of a wireless cell, or a cable is plugged in.

Attachment Detection

While a host's network layer may initially be unaware
of the occurrence of attachment, it may already have
valid IP configuration for the link instance where it
is attached. A host determines that attachment has
occurred, as well as whether it needs additional
configuration by Detecting Network Attachment (DNA).

Rapid attachment detection is required when a host
has existing upper layer protocols sessions. This may
be the case if a host is connected intermittently, is
a mobile host or has urgent data to transmit upon
attachment to a link.

For these nodes, it is also important detect if an
acquired subnet or 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. For
example, there may be a requirement to to undertake
address configuration, network-layer authentication
and multicast group managment signalling, before
receiving packets from off-link.

Link Layer Hints

While it is a goal of DNA to provide network
attachment detection systems which do not rely upon
link-layer information, in some circumstances reception
of hint information from lower layers may be valuable
in speeding detection. In order to provide guidance to
implementors, the group will survey existing link-layer
hints and define general abstractions.  The mechanisms
developed by the WG will specify how these abstracted
hints are utilized when they are present.

The group will also undertake liaison opportunities with
link-layer standardization authorities, in an effort to
improve the quality of link indications for network
attachment detection in future wireless link
technologies.

DAD Optimization

There are some IPv6 subsystems which need to send or
receive packets, immediately after attaching to a new
network. Current address configuration strategies rely
upon hosts undertaking Duplicate Address Detection (DAD),
when they first configure an address. Current DAD
specifications prevent transmission and reception from a
newly configured address within the first second of
attachment. Therefore, some optimization may be desirable.

This group will specify how to optimize the existing
procedure for detection of IPv6 address collision. "DAD
optimization" aims to reduce delay due to the detection of
IPv6 address availability.

Goals

* Liaise with other working groups which perform attachment
   detection, to ensure their requirements for detecting
   network attachment are met.

* Describe existing attachment detection issues encountered
   in DHC, ZEROCONF, IPv6 and Mobileip WGs, documenting
   procedures which provide robust attachment detection for
   IPv4 and IPv6 hosts.

* Develop optimizations to network attachment detection for
   time-constrained systems, such as MobileIPv6.

* Document a useful subset of existing Link-Hint mechanisms
   for Detection of Network Attachment.

* Develop a DAD optimization protocol independent of link
   layer technology.


Work List

[This list is currently supposed to be everything we
could think of to do (in small achievable pieces).

Please comment on whether you think some of these
items are unnecessary.

I'm not sure whether we'll need to provide final
delivery dates yet. At this stage, I guess we'd
hope to have small, well written (and reviewed)
documents available by the next IETF after they're
presented as WG documents.

This may be far too optimistic...]

* DNA Terminology Definition ( goal: info, initial by IETF58)

* Catalogue Existing IPv4 Attachment Detection Systems
   (goal: info, initial by IETF58)

* Define IPv4 Attachment Detection Problem Scope
   (goal: info, initial by IETF58)

* Define IPv6 Attachment Detection Problem Scope
   (goal: info, initial by IETF58)

* Define IPv6 DAD optimization Problem Scope
   (goal: info, initial by IETF58)

* Existing Wireless Link Hints for Detecting Network Attachment
   (goal: info, initial by IETF58)

* Determine IPv6 DAD optimization Requirements
   (goal: info, initial by IETF58/59)

* Define IPv4 Attachment Detection Requirements
   (goal: info, initial by IETF59)

* Define IPv6 Attachment Detection Requirements
   (goal: info, initial by IETF59)

* Define IPv4 Basic Attachment Detection specification
   (goal: info/BCP, initial by IETF59)

* Define IPv6 Basic Attachment Detection specification
   (goal: PS/BCP, initial by IETF59)

* Define DAD Optimization Specification
   (goal: PS/upd 2462?, initial by IETF59/60)

* Investigate Feasibility of IPv4 DNA optimizations,
   (goal: WG internal?, by IETF60)

* Define IPv6 Optimized Attachment Detection procedures
   (goal: Exptl/PS, initial by IETF60)

* Define IPv4 Optimized Attachment Detection procedures
   (goal: Exptl/PS initial by IETF60/61)