DNA BoF Agenda IETF58? (was Re: [DNA-BOF] DNA session in Minneapolis ?)

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

Hi Daniel,

I've applied for a session (tentatively approved), but
have not seen it scheduled yet.

Here is the session agenda.

Originally I'd hoped to discuss the
development of the terminology document too,
but there's not enough time if we're to keep
the session to an hour and still have time
to discuss the future of the group.

I've yet to discuss this with each potential
presenter in detail yet.

Please be aware that we may have a different
description by the time the session occurs,
if we arrive at agreement on-list.

Greg

Detecting Network Attachment (DNA) BOF:

AREA: Internet Area  (INT).

CONFLICTS:  ipv6, mip6, mipshop, mip4, send, dhc,
             zeroconf, magma, hip bof

SLOTS: 1

SLOT LENGTH: 1 hour

ATTENDANCE: Unsure, last time 50 < Attendance < 100

Chair:
------
Greg Daley ( greg.daley@eng.monash.edu.au )

Meeting Description:
--------------------

Network Attachment occurs when a link-layer connection is established 
and a node is able to send and receive some IP packets within a link, 
particularly those used for configuration purposes. 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.

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.

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.

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.

The following items are considered on-topic tasks for DNA group.

     * 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.


BoF WWW Page and Mailing list archive:
--------------------------------------
http://www.ctie.monash.edu.au/dna/




Session Agenda: (60 Minutes total)
===============

Intro and Agenda Bash (5 Minutes)
---------------------

Status Reports (45 Minutes total)
--------------
* Detection of Network Attachment (DNA) in IPv4 ( 5 + 5 Min)
        (Bernard Aboba) DHC WG Draft
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-03.txt

* Detecting Network Attachment in IPv6 Problem Statement  (5 + 5 Min)
        (JinHyeock Choi, Greg Daley) undergoing submission.
http://www.ctie.monash.edu.au/ipv6/draft-jinchoi-dna-dnav6-prob-00.txt

* IPv6 DAD Optimization Goals and Requirements (5 + 5 Min)
        (Soohong Daniel Park, Youn-Hee Han, Greg Daley)
http://www.ietf.org/internet-drafts/draft-park-dna-ipv6dadopt-requirement-01.txt

* Parameters for Link Hints (5 Min)
        (P. Bertin, T. Noel, N. Montavont)
http://www.ietf.org/internet-drafts/draft-bertin-hints-params-00.txt

* Link-layer Hints for Detecting Network Attachments (5 Min)
        (Alper Yegin (Ed) et al).
http://www.ietf.org/internet-drafts/draft-yegin-dna-l2-hints-00.txt

* Link Hints Discussion (5 Min)


BoF Status Discussion (Led by Greg Daley: 15 Minutes)
---------------------
   - Overview
   - Document Progress
   - Charter Discussion
   - Futures (2nd BoF!)