Re: [DNA-BOF] IETF 57 DNA BoF session summary

[JinHyeock Choi <athene@sait.samsung.co.kr>]

Dear Greg

Thanks for the nice job both during the meeting and afterwards. 
I guess we had a successful BoF and DNA is on the good track 
to WG. 

Your meeting summary is good. It presents all the decisions we 
made correctly and the necessary action points clearly. 

But I don't find any action point about DAD. Or does AP4 include
DAD work?

And I think it will be useful if we have a document which clarifying 
basic definitions of DNA. For example, 1) What does it mean that 
a node is attached to a network? 2) What should a node check to 
detect attachments? 

With clear definitions in hands, we can avoid unproductive confusion 
and unnecessary arguments.    

Kindly find my in line comments. 

> AP1. Develop a WG charter for Detecting Network Attachment.
>       AP owner <GD>
>       Target Date: BoF LC to be completed by late August.
> 
> AP5. Discuss whether cataloguing L2 Hints is useful
>       (consensus call?)
>       AP owner:     <TBA, initially GD>
>       Target date:  mid August

You put AP5 after AP1. Is this on intention? :-)

> AP2. Link Localv4/DHCPv4 interaction clarification
>       AP owner:     <GD, Zerconf, DHC WG Chairs>
>       Target date:  to completed before mid August
> 
> AP3. Link Localv4/DHCPv4 issues and guidelines document
>       (informational?)
>       AP owner:     <TBA, not discussed> (suggested by TN/BA)
>       Target date:  to completed before mid August
> 
> AP4. Mobile IPv6 Handover Delays Description Document
>       AP owner:     <TBA, initially GD> (suggested by TN)
>       Target date:  mid-late August

Basically MIPv6 Handover Delay consists of 1) MD Delay, 2) DAD Delay 
and 3) Signaling(BU/ BA) Delay. Will this document deal with all three 
delays? I think 'Signaling Delay' is out of DNA scope. 

And how about divide this AP like below

AP4.1 MD Delay in Mobile IPv6 Handover Description Document
AP4.2 DAD Delay in Mobile IPv6 Handover Description Document
 
In two short documents, I think we can finish this AP more easily. We 
can combine them later, if necessary. 

> AP6. Establish Liaison with IEEE ECSG
>       (? Not agreed, depends on L2 Hints in WG)
>       AP owner:     <TBA, intially GD>
>       Target date:  end of September
 
Another thanks for good job and I hope we will have a WG at Minneapolis.