Re: [DNA-BOF] Draft charter now online

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

Hi JinHyeock,

Thanks for commenting.

I'll try to talk through some of the
decisions I was making while putting this all
together, and see whether we can come up
with improved text.

JinHyeock Choi wrote:
> Dear Greg
> 
> Thanks for nice job. I am glad DNA is progressing to a real WG. 
> 
> Kindly find my on line comments for Attachment Detection. 
> 
> 
> 
>>Proposed Detecting network Attachment (DNA)
>>Working Group Description.
>>
>>Overview
>>
>>Network Attachment occurs when an interface
>>becomes ready to send and receive IP datagrams.
> 
> 
> What do you mean by 'interface becomes ready'?  I think that Network 
> Attachment occurs when a node has completed a link layer connection, 
> whether Ethernet or WLAN. We'd better clarify this. 

This seems to be the problematic section.
I've tried to make this reflect previous comments
from the list.

Maybe we need to be explicit though...

How about:

"Network Attachment occurs when an interface
has completed link-layer connection procedures
and becomes ready to send and receive IP datagrams."

I think that any more information than this in
the initial description is likely to be too much, though.


> 
>>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. 
> 
> 
> Would you elaborate more about 'valid IP configuration'. What I can think 
> of are 'IP address', 'default router information' and 'on-link prefix information' 

I can provide this information to the list,
but do we want to elaborate on each of these things
in the charter?

I was also thinking of multicast group membership,
off-link communications authorization (from PANA..),
DHC parameters such as name servers, as well as those
things which you mentioned.

When we start talking about DHC the possibilities
become very broad.

I was trying to steer away from providing details,
except in the example provided (2 1/2) paragraphs
further on.   Do you think we have to be more
explicit early on in the description?

> 
>>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.
> 
>  
> I think that the brief description of group goal will be nice. 

Can you please clarify what you mean?

Do you mean:
Would be nice (meaning we need to have more work),
or
Will be nice (meaning it looks roughly sufficient).

I was not exactly sure, and I don't want to
miss anything.

Thanks very much for the feedback.

Greg