From dna-owner@webcamserver.eng.monash.edu.au Fri May 12 20:08:27 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FehgJ-0002ot-Kd
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:08:27 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FehgH-00043v-Sg
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:08:27 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2DBDP0BVA8WXQUR@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 13 May 2006 10:08:12 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2D80EAB543; Sat,
 13 May 2006 10:08:08 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id D14584FB02; Sat,
 13 May 2006 10:08:07 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4D02wW29406	for dna-list; Sat, 13 May 2006 10:02:58 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4D02wu29402	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 13 May 2006 10:02:58 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DB76AMTA8X73Y1@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 13 May 2006 10:02:53 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C4724AB542; Sat,
 13 May 2006 10:02:52 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by moe.its.monash.edu.au (Postfix) with ESMTP id AC6B34FB06; Sat,
 13 May 2006 10:02:52 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Fri, 12 May 2006 20:02:51 -0400
Date: Fri, 12 May 2006 20:02:51 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: [DNA] Following up Dallas on how to structure documents
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <f5e925ad1078.1078f5e925ad@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

Hi,

During the last meeting there was a long discussion
as to how many documents the WG wanted to make
to create the DNA solution, and specify changes to
protocols for DNA purposes.

It was suggested that we look at ways to combine existing
documents with related purposes to see if any of the
combinations made sense, both so that the implementors
have few documents to follow, and clarity is maintained.

To get a rough idea of what the working group thinks is
appropriate, I'll post lists of Tables of contents from
existing documents, and VERY rough outline combinations
of Tables of contents for proposed merged documents.

These TOCs are aimed at not losing any information,
but clearly, there will be a chance later to review
documents' contents if we decide to commit to amalgamating
a set or subset of documents. 

Therefore, please don't be too concerned about duplication,
or subsections which don't flow smoothly.  The idea is to get
a set of documents which could work together, (and keeping
some existing documents is one option).

Assumptions:

The candidate documents are:
draft-ietf-dna-hosts-02.txt (-03 about to be submitted)
draft-ietf-dna-cpl-02.txt
draft-ietf-dna-protocol-00.txt
draft-ietf-tentative-00.txt

Other WG documents are out of scope at this stage,
because they do not propose protocol changes.

Please let me know if these assumptions are inappropriate.


There are (probably) 4 possible combinations for discussion
here. I'd like people to indicate what they like most, and
like least, and give some explanation.

They are (roughly):

1. Keep the same documents (Hosts), (CPL), (Proto), (Tent)
2. Combine all into one document (Hosts/CPL/Proto/Tent)
3. Make two documents: unmodified packets (Hosts/CPL), modified packets
(Proto/Tent)
4. Make two documents: Hosts Mods (Hosts/CPL/Proto/Tent), Router mods
(Proto/Tent)

We should be able to cull some ideas early, if we get good
discussion, and consensus.

I'll post follow ups with TOCs for each option.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Fri May 12 20:44:08 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeiEq-0000LD-9I
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:44:08 -0400
Received: from alpha6.its.monash.edu.au ([130.194.1.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeiEp-0005q4-E9
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:44:08 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DCMF2N3U8YD1EI@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 13 May 2006 10:43:41 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 7D56A80003; Sat,
 13 May 2006 10:43:24 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 36F963C007; Sat, 13 May 2006 10:43:24 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4D0gpQ29781	for dna-list; Sat, 13 May 2006 10:42:51 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4D0gou29777	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 13 May 2006 10:42:50 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DCLDN96M8YD1EI@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 13 May 2006 10:42:34 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 56D38AB542; Sat,
 13 May 2006 10:42:34 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 439574FB0C; Sat,
 13 May 2006 10:42:34 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Fri, 12 May 2006 20:42:33 -0400
Date: Fri, 12 May 2006 20:42:33 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: [DNA] Merger: Existing Tables of contents
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <f62dc5fa20ac.20acf62dc5fa@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Score: 1.3 (+)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96

Hi, 

To enable discussion of mergers of documents, here
are the tables of contents of the existing set of
documents which has been submitted to the repository
for DNA.

HOSTS-03: draft-ietf-dna-hosts-03.txt
CPL-02: draft-ietf-dna-cpl-02.txt
PROTO-00: draft-ietf-dna-protocol-00.txt
TENT-00: draft-ietf-dna-tentative-00.txt

These short names are used in later combinations
of documents to indicate where sections come from.

Keeping these documents separate is considered 
Option 1, as previously related.

Greg

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
HOSTS-03: draft-ietf-dna-hosts-03.txt
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.  Introduction  HOSTS-03
     1.1   Structure of this Document HOSTS-03

2.  Terms and Abbreviations  HOSTS-03

3.  Background & Motivation for DNA HOSTS-03
  3.1   Issues HOSTS-03

4.  Detecting Network Attachment Steps HOSTS-03
  4.1   Making use of Prior Information HOSTS-03
  4.2   Link identification HOSTS-03
    4.2.1   Same link HOSTS-03
    4.2.2   Link change HOSTS-03
  4.3   IP Hosts Configuration HOSTS-03
  4.4   Duplicate Address Detection HOSTS-03
  4.5   Multicast Listener State HOSTS-03
  4.6   Reachability detection HOSTS-03

5.  Initiation of DNA Procedures HOSTS-03
  5.1   Actions Upon Hint Reception HOSTS-03
  5.2   Hints Due to Network Layer Messages HOSTS-03
  5.3   Handling Hints from Other Layers HOSTS-03
  5.4   Timer and Loss Based Hints HOSTS-03
  5.5   Simultaneous Hints HOSTS-03
  5.6   Hint Management for Inactive Hosts HOSTS-03

6.  Complications to Detecting Network Attachment HOSTS-03
  6.1   Packet Loss HOSTS-03
  6.2   Router Configurations HOSTS-03
  6.3   Overlapping Coverage HOSTS-03
  6.4   Multicast Snooping HOSTS-03
  6.5   Link Partition HOSTS-03

7.  Security Considerations HOSTS-03
  7.1   Authorization and Detecting Network Attachment HOSTS-03
  7.2   Addressing HOSTS-03

8.  Constants HOSTS-03
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
CPL-02: draft-ietf-dna-cpl-02.txt
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.   Introduction CPL-02

2.   Prefix list based approach CPL-02 
  2.1  Approach CPL-02 
  2.2  Assumptions CPL-02 
  2.3  Overview CPL-02 

3.   DNA based on the Complete Prefix List CPL-02 
  3.1  Complete Prefix List generation CPL-02 
  3.2  Erroneous Prefix Lists CPL-02  
  3.3  Link identity detection CPL-02  
  3.4  Renumbering CPL-02  

4.   Protocol Specification CPL-02 
  4.1  Conceptual data structures CPL-02 
  4.2  Merging Candidate Link objects CPL-02 
  4.3  Timer handling and Garbage Collection CPL-02  
  4.4  Receiving link UP notifications CPL-02 
  4.5  Receiving valid Router Advertisements CPL-02 
  4.6  Changing the link in Neighbor Discovery CPL-02 

5.   CPL without a 'link UP' notification CPL-02 

6.   IANA Considerations CPL-02  

7.   Security Considerations CPL-02 

8.   Examples CPL-02 
  8.1  Example CPL-02 
  8.2  Example CPL-02  

9.   Protocol Constants CPL-02

10.  Acknowledgements CPL-02

11.  Performance Analysis CPL-02

12.  Change Log CPL-02

13.  Open Issues CPL-02

14.  References CPL-02
  14.1   Normative References CPL-02 
  14.2   Informative References CPL-02 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
PROTO-00: draft-ietf-dna-protocol-00.txt
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.   Introduction PROTO-00

2.   Terms and Abbreviations PROTO-00

3.   Overview PROTO-00
  3.1  Link Identification PROTO-00
  3.2  Fast Router Advertisement PROTO-00

4.   Message Formats PROTO-00
  4.1  Router Advertisement PROTO-00
  4.2  Prefix Information Option LinkID Bit PROTO-00
  4.3  Landmark Option PROTO-00
  4.4  Learned Prefix Option PROTO-00

5.   DNA Operation PROTO-00
  5.1  DNA Router Operation PROTO-00
    5.1.1  Data Structures PROTO-00
    5.1.2  Router Configuration Variables PROTO-00
    5.1.3  Bootstrapping DNA Data Structures PROTO-00
    5.1.4  Processing Router Advertisements PROTO-00
    5.1.5  Processing Router Solicitations PROTO-00
    5.1.6  Complete Router Advertisements PROTO-00
    5.1.7  LinkID PROTO-00
    5.1.8  Scheduling Fast Router Advertisements PROTO-00
    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
    5.1.10   Removing a Prefix from an Interface PROTO-00
    5.1.11   Prefix Reassignment PROTO-00
  5.2  DNA Host Operation PROTO-00
    5.2.1  Data Structures PROTO-00
    5.2.2  Host Configuration Variables PROTO-00
    5.2.3  Selection of a Landmark Prefix PROTO-00
    5.2.4  Sending Router Solicitations PROTO-00
    5.2.5  Processing Router Advertisements PROTO-00
    5.2.6  DNA and Address Configuration PROTO-00

6.   Backward Compatibility PROTO-00
  6.1  Non-DNA Host with DNA Routers PROTO-00
  6.2  DNA Host with Non-DNA Routers PROTO-00

7.   Security Considerations PROTO-00
  7.1  Attacks on the Token Bucket PROTO-00
  7.2  Attacks on DNA Hosts PROTO-00

8.   IANA Considerations PROTO-00

9.   Acknowledgments PROTO-00

10.  References PROTO-00
  10.1   Normative References PROTO-00
  10.2   Informative References PROTO-00

A.   How the Goals are Met? PROTO-00
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TENT-00:  draft-ietf-dna-tentative-00.txt
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.  Introduction TENT-00
  1.1   Tentative Option format TENT-00
  1.2   Tentative Option semantics TENT-00

2.  Sending solicitations containing Tentative Options TENT-00 
  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
  2.2   Sending Router Solicitations with Tentative Options TENT-00

3.  Receiving Tentative Options TENT-00
  3.1   Handling Tentative Options TENT-00 
  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
        Options TENT-00
  3.3   Receiving Router Solicitations containing Tentative TENT-00
        Options TENT-00

4.  IANA Considerations TENT-00 

5.  Security Considerations TENT-00

6.  Acknowledgments TENT-00

7.  References TENT-00
  7.1   Normative References TENT-00
  7.2   Informative References TENT-00

A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
  A.1   Constraints on Neighbour Solicitations TENT-00
  A.2   Constraints on Router Solicitations TENT-00

B.  Interactions with legacy nodes TENT-00
  B.1   Legacy Neighbour Solicitation processing TENT-00 
  B.2   Legacy Router Solicitation processing TENT-00 

C.  Sending directed advertisements without the neighbour cache TENT-00


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX




From dna-owner@webcamserver.eng.monash.edu.au Fri May 12 20:47:24 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeiI0-0001oy-HU
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:47:24 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeiHz-000650-Ez
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:47:24 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2DCR1YB6M8WXR2S@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 13 May 2006 10:47:11 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id DB47980005; Sat,
 13 May 2006 10:47:08 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 976553C005; Sat, 13 May 2006 10:47:08 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4D0l2R29893	for dna-list; Sat, 13 May 2006 10:47:02 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4D0l2u29887	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 13 May 2006 10:47:02 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DCQRQQTM8X74VQ@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 13 May 2006 10:46:56 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C26FBAB542; Sat,
 13 May 2006 10:46:55 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by curly.its.monash.edu.au (Postfix) with ESMTP id AF33A4FB03; Sat,
 13 May 2006 10:46:55 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Fri, 12 May 2006 20:46:54 -0400
Date: Fri, 12 May 2006 20:46:54 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: [DNA] Merger: All Documents together (2)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <f67cb78543ca.43caf67cb785@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8

Hi,

This is an amalgamation of the DNA documents together
in a form roughly inspired by RFC2461 Neighbor Discovery.

This embodies an example of option 2 for document merger.

Please note that there are duplicate section names, and
each actual section may cover overlapping topics with 
other protocols.  Please try to ignore this fact initially,
and concentrate on the overall structure of the document.

When Referring to this proposal, it may be useful to describe
it at COMBO2.

Greg

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
COMBO2: All combined
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.  Introduction HOSTS-03
1.  Introduction CPL-02
1.  Introduction PROTO-00
1.  Introduction TENT-00


     1.1   Structure of this Document HOSTS-03

2.  Terms and Abbreviations  HOSTS-03
2.   Terms and Abbreviations PROTO-00



3.  Background & Motivation for DNA HOSTS-03
  3.1   Issues HOSTS-03

#
# Conceptual Overview...???
#
#
3.   Overview PROTO-00
  3.1  Link Identification PROTO-00
  3.2  Fast Router Advertisement PROTO-00

#
# Procedural Overview...???
#
#
4.  Detecting Network Attachment Steps HOSTS-03
  4.1   Making use of Prior Information HOSTS-03
  4.2   Link identification HOSTS-03
    4.2.1   Same link HOSTS-03
    4.2.2   Link change HOSTS-03
  4.3   IP Hosts Configuration HOSTS-03
  4.4   Duplicate Address Detection HOSTS-03
  4.5   Multicast Listener State HOSTS-03
  4.6   Reachability detection HOSTS-03


#
# Link Identification
#
#
2.   Prefix list based approach CPL-02 
  2.1  Approach CPL-02 
  2.2  Assumptions CPL-02 
  2.3  Overview CPL-02 
#
#  Cut down on some protocol explanations if shift
#  conceptual text here.
#
#
#

#
# Message Formats
#
#
4.   Message Formats PROTO-00
  4.1  Router Advertisement PROTO-00
  4.2  Prefix Information Option LinkID Bit PROTO-00
  4.3  Landmark Option PROTO-00
  4.4  Learned Prefix Option PROTO-00

  1.1   Tentative Option format TENT-00
  1.2   Tentative Option semantics TENT-00


#
#   Host Operations
#
#
  5.2  DNA Host Operation PROTO-00
    5.2.1  Data Structures PROTO-00
    5.2.2  Host Configuration Variables PROTO-00
4.   Protocol Specification CPL-02 
  4.1  Conceptual data structures CPL-02 

5.  Initiation of DNA Procedures HOSTS-03
  4.4  Receiving link UP notifications CPL-02 
  5.1   Actions Upon Hint Reception HOSTS-03
  5.2   Hints Due to Network Layer Messages HOSTS-03
  5.3   Handling Hints from Other Layers HOSTS-03
  5.4   Timer and Loss Based Hints HOSTS-03
  5.5   Simultaneous Hints HOSTS-03
  5.6   Hint Management for Inactive Hosts HOSTS-03



# Sending RSs
    5.2.4  Sending Router Solicitations PROTO-00
    5.2.3  Selection of a Landmark Prefix PROTO-00
2.  Sending solicitations containing Tentative Options TENT-00 
  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
  2.2   Sending Router Solicitations with Tentative Options TENT-00

# Receiving RAs.
  4.5  Receiving valid Router Advertisements CPL-02 
    5.2.5  Processing Router Advertisements PROTO-00
  3.3  Link identity detection CPL-02  
  3.   DNA based on the Complete Prefix List CPL-02 
  3.1  Complete Prefix List generation CPL-02 
  4.2  Merging Candidate Link objects CPL-02 

  4.6  Changing the link in Neighbor Discovery CPL-02 
    5.2.6  DNA and Address Configuration PROTO-00



# Timers?????
  3.2  Erroneous Prefix Lists CPL-02  
  3.4  Renumbering CPL-02  
  4.3  Timer handling and Garbage Collection CPL-02  

#
#  Router Operations
#
#
  5.1  DNA Router Operation PROTO-00
    5.1.1  Data Structures PROTO-00
    5.1.2  Router Configuration Variables PROTO-00
    5.1.3  Bootstrapping DNA Data Structures PROTO-00
    5.1.4  Processing Router Advertisements PROTO-00
    5.1.5  Processing Router Solicitations PROTO-00
    5.1.6  Complete Router Advertisements PROTO-00
    5.1.7  LinkID PROTO-00
    5.1.8  Scheduling Fast Router Advertisements PROTO-00
    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
    5.1.10   Removing a Prefix from an Interface PROTO-00
    5.1.11   Prefix Reassignment PROTO-00
3.  Receiving Tentative Options TENT-00
  3.1   Handling Tentative Options TENT-00 
  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
        Options TENT-00
  3.3   Receiving Router Solicitations containing Tentative TENT-00
        Options TENT-00

#
# Limitations of DNA
#
#
6.  Complications to Detecting Network Attachment HOSTS-03
  6.1   Packet Loss HOSTS-03
  6.2   Router Configurations HOSTS-03
  6.3   Overlapping Coverage HOSTS-03
  6.4   Multicast Snooping HOSTS-03
  6.5   Link Partition HOSTS-03


#
# Backward compatability
#
6.   Backward Compatibility PROTO-00
  6.1  Non-DNA Host with DNA Routers PROTO-00
  6.2  DNA Host with Non-DNA Routers PROTO-00
5.   CPL without a 'link UP' notification CPL-02 
  #
# Constants
#
#
8.  Constants HOSTS-03
9.  Protocol Constants CPL-02


#
# IANA Considerations
#
#
6.   IANA Considerations CPL-02  
8.   IANA Considerations PROTO-00
4.   IANA Considerations TENT-00 



#
# Security Considerations
#
#
7.  Security Considerations CPL-02 
7.  Security Considerations HOSTS-03
7.  Security Considerations PROTO-00
5.  Security Considerations TENT-00
  7.1  Attacks on the Token Bucket PROTO-00
  7.2  Attacks on DNA Hosts PROTO-00
  7.1   Authorization and Detecting Network Attachment HOSTS-03
  7.2   Addressing HOSTS-03

#
# Appendices
#
#
A.   How the Goals are Met? PROTO-00

11.  Performance Analysis CPL-02

8.   Examples CPL-02 
  8.1  Example CPL-02 
  8.2  Example CPL-02  

A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
  A.1   Constraints on Neighbour Solicitations TENT-00
  A.2   Constraints on Router Solicitations TENT-00

B.  Interactions with legacy nodes TENT-00
  B.1   Legacy Neighbour Solicitation processing TENT-00 
  B.2   Legacy Router Solicitation processing TENT-00 

C.  Sending directed advertisements without the neighbour cache TENT-00





From dna-owner@webcamserver.eng.monash.edu.au Fri May 12 20:51:21 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeiLp-0002yP-Cj
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:51:21 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeiLo-0006E5-Ix
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 20:51:21 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2DCW36RXS91X4FX@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 13 May 2006 10:51:14 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6854580004; Sat,
 13 May 2006 10:51:12 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 2393C3C00C; Sat, 13 May 2006 10:51:12 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4D0p2s29981	for dna-list; Sat, 13 May 2006 10:51:02 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4D0p2u29977	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 13 May 2006 10:51:02 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DCVJHC368X74VQ@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 13 May 2006 10:50:47 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A416C80002; Sat,
 13 May 2006 10:50:46 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 90EB23C007; Sat,
 13 May 2006 10:50:46 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Fri, 12 May 2006 20:50:45 -0400
Date: Fri, 12 May 2006 20:50:45 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: [DNA] Merger: Unmodified Messages/Modified Messages (3)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <f64eb23a3625.3625f64eb23a@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48

Hi,

Here's another proposal for merging the documents.
Essentially, this takes CPL and HOSTS and puts
them together (COMBO3A), while putting the other documents
which modify message formats together PROTO and Tentative
(COMBO3B).

As an aside, there's clearly a lot of overlap between Hosts
and CPL, which can be reduced.

Greg

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
COMBO3A:  Unmodified Messages.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.   Introduction CPL-02
1.  Introduction  HOSTS-03
     1.1   Structure of this Document HOSTS-03

2.  Terms and Abbreviations  HOSTS-03

3.  Background & Motivation for DNA HOSTS-03
  3.1   Issues HOSTS-03
2.   Prefix list based approach CPL-02 
  2.1  Approach CPL-02 
  2.2  Assumptions CPL-02 
  2.3  Overview CPL-02 

4.  Detecting Network Attachment Steps HOSTS-03
  4.1   Making use of Prior Information HOSTS-03
  4.2   Link identification HOSTS-03
    4.2.1   Same link HOSTS-03
    4.2.2   Link change HOSTS-03
  4.3   IP Hosts Configuration HOSTS-03
  4.4   Duplicate Address Detection HOSTS-03
  4.5   Multicast Listener State HOSTS-03
  4.6   Reachability detection HOSTS-03


3.   DNA based on the Complete Prefix List CPL-02 
  3.1  Complete Prefix List generation CPL-02 
  3.2  Erroneous Prefix Lists CPL-02  
  3.3  Link identity detection CPL-02  
  3.4  Renumbering CPL-02  

4.   Protocol Specification CPL-02 
  4.1  Conceptual data structures CPL-02 
  4.2  Merging Candidate Link objects CPL-02 
  4.3  Timer handling and Garbage Collection CPL-02  
  4.4  Receiving link UP notifications CPL-02 
  4.5  Receiving valid Router Advertisements CPL-02 
  4.6  Changing the link in Neighbor Discovery CPL-02 

5.  Initiation of DNA Procedures HOSTS-03
  5.1   Actions Upon Hint Reception HOSTS-03
  5.2   Hints Due to Network Layer Messages HOSTS-03
  5.3   Handling Hints from Other Layers HOSTS-03
  5.4   Timer and Loss Based Hints HOSTS-03
  5.5   Simultaneous Hints HOSTS-03
  5.6   Hint Management for Inactive Hosts HOSTS-03

6.  Complications to Detecting Network Attachment HOSTS-03
  6.1   Packet Loss HOSTS-03
  6.2   Router Configurations HOSTS-03
  6.3   Overlapping Coverage HOSTS-03
  6.4   Multicast Snooping HOSTS-03
  6.5   Link Partition HOSTS-03
5.   CPL without a 'link UP' notification CPL-02 

6.   IANA Considerations CPL-02  

7.   Security Considerations CPL-02 
7.  Security Considerations HOSTS-03
  7.1   Authorization and Detecting Network Attachment HOSTS-03
  7.2   Addressing HOSTS-03

8.  Constants HOSTS-03
9.   Protocol Constants CPL-02

#
# Appendixes
#


8.   Examples CPL-02 
  8.1  Example CPL-02 
  8.2  Example CPL-02  

11.  Performance Analysis CPL-02





XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
COMBO3B: Modified Messages
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.   Introduction PROTO-00
1.  Introduction TENT-00

2.   Terms and Abbreviations PROTO-00

3.   Overview PROTO-00
  3.1  Link Identification PROTO-00
  3.2  Fast Router Advertisement PROTO-00

4.   Message Formats PROTO-00
  4.1  Router Advertisement PROTO-00
  4.2  Prefix Information Option LinkID Bit PROTO-00
  4.3  Landmark Option PROTO-00
  4.4  Learned Prefix Option PROTO-00
  1.1   Tentative Option format TENT-00
  1.2   Tentative Option semantics TENT-00


5.   DNA Operation PROTO-00
  5.1  DNA Router Operation PROTO-00
    5.1.1  Data Structures PROTO-00
    5.1.2  Router Configuration Variables PROTO-00
    5.1.3  Bootstrapping DNA Data Structures PROTO-00
    5.1.4  Processing Router Advertisements PROTO-00
    5.1.5  Processing Router Solicitations PROTO-00
3.  Receiving Tentative Options TENT-00
  3.1   Handling Tentative Options TENT-00 
  3.3   Receiving Router Solicitations containing Tentative TENT-00
        Options TENT-00

    5.1.6  Complete Router Advertisements PROTO-00
    5.1.7  LinkID PROTO-00
    5.1.8  Scheduling Fast Router Advertisements PROTO-00
    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
    5.1.10   Removing a Prefix from an Interface PROTO-00
    5.1.11   Prefix Reassignment PROTO-00
  5.2  DNA Host Operation PROTO-00
    5.2.1  Data Structures PROTO-00
    5.2.2  Host Configuration Variables PROTO-00
    5.2.3  Selection of a Landmark Prefix PROTO-00
    5.2.4  Sending Router Solicitations PROTO-00
2.  Sending solicitations containing Tentative Options TENT-00 
  2.2   Sending Router Solicitations with Tentative Options TENT-00

    5.2.5  Processing Router Advertisements PROTO-00
    5.2.6  DNA and Address Configuration PROTO-00

6.   Backward Compatibility PROTO-00
  6.1  Non-DNA Host with DNA Routers PROTO-00
  6.2  DNA Host with Non-DNA Routers PROTO-00

7.   Security Considerations PROTO-00
  7.1  Attacks on the Token Bucket PROTO-00
  7.2  Attacks on DNA Hosts PROTO-00
5.  Security Considerations TENT-00

8.   IANA Considerations PROTO-00
4.  IANA Considerations TENT-00 


A.   How the Goals are Met? PROTO-00


  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
        Options TENT-00

A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
  A.1   Constraints on Neighbour Solicitations TENT-00
  A.2   Constraints on Router Solicitations TENT-00

B.  Interactions with legacy nodes TENT-00
  B.1   Legacy Neighbour Solicitation processing TENT-00 
  B.2   Legacy Router Solicitation processing TENT-00 

C.  Sending directed advertisements without the neighbour cache TENT-00




From dna-owner@webcamserver.eng.monash.edu.au Fri May 12 21:00:48 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeiUy-0006c1-PQ
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 21:00:48 -0400
Received: from alpha1.its.monash.edu.au ([130.194.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeiUx-0006iX-MR
	for dna-archive@lists.ietf.org; Fri, 12 May 2006 21:00:48 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DD7ALTL28YD6N3@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 13 May 2006 11:00:32 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 45D0FAB545; Sat,
 13 May 2006 11:00:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id EFEB94FB09; Sat,
 13 May 2006 11:00:13 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4D100q30102	for dna-list; Sat, 13 May 2006 11:00:00 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4D100u30093	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 13 May 2006 11:00:00 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2DD6YPTV08YD6N3@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 13 May 2006 10:59:59 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 7F214AB542; Sat,
 13 May 2006 10:59:58 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 647A24FB06; Sat,
 13 May 2006 10:59:58 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Fri, 12 May 2006 20:59:57 -0400
Date: Fri, 12 May 2006 20:59:57 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: [DNA] Merger: Host Modifications, Router Modifications (4)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <f5fdacad11b4.11b4f5fdacad@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3

Hi,

Here is a set of documents, which people mentioned
would be useful in that separate documents are described
for each of the hosts and routers implementors.

In order to reduce the documents each has to read, there
is overlap in that the message formats would be described
in both documents.

Essentially, Router only components of DNA protocol and Tentative
Options are grouped together in one document (COMBO4A).
Parts of the DNA protocol and tentative options which relate to
hosts only are placed in a document with CPL and HOSTS-03 elements
(COMBO4B).

Greg

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
COMBO4A (How routers are modified for DNA)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.  Introduction PROTO-00
1.  Introduction TENT-00


2.   Terms and Abbreviations PROTO-00


#
# Conceptual Overview...???
#
#
3.   Overview PROTO-00
  3.1  Link Identification PROTO-00
  3.2  Fast Router Advertisement PROTO-00

#
# Message Formats
#
#
4.   Message Formats PROTO-00
  4.1  Router Advertisement PROTO-00
  4.2  Prefix Information Option LinkID Bit PROTO-00
  4.3  Landmark Option PROTO-00
  4.4  Learned Prefix Option PROTO-00

  1.1   Tentative Option format TENT-00
  1.2   Tentative Option semantics TENT-00


#
#  Router Operations
#
#
  5.1  DNA Router Operation PROTO-00
    5.1.1  Data Structures PROTO-00
    5.1.2  Router Configuration Variables PROTO-00
    5.1.3  Bootstrapping DNA Data Structures PROTO-00
    5.1.4  Processing Router Advertisements PROTO-00
    5.1.5  Processing Router Solicitations PROTO-00
    5.1.6  Complete Router Advertisements PROTO-00
    5.1.7  LinkID PROTO-00
    5.1.8  Scheduling Fast Router Advertisements PROTO-00
    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
    5.1.10   Removing a Prefix from an Interface PROTO-00
    5.1.11   Prefix Reassignment PROTO-00
3.  Receiving Tentative Options TENT-00
  3.1   Handling Tentative Options TENT-00 
  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
        Options TENT-00
  3.3   Receiving Router Solicitations containing Tentative TENT-00
        Options TENT-00

#
# Backward compatability
#
6.   Backward Compatibility PROTO-00
  6.1  Non-DNA Host with DNA Routers PROTO-00

#
# IANA Considerations
#
#
8.   IANA Considerations PROTO-00
4.   IANA Considerations TENT-00 



#
# Security Considerations
#
#
7.  Security Considerations PROTO-00
5.  Security Considerations TENT-00
  7.1  Attacks on the Token Bucket PROTO-00

#
# Appendices
#
#
A.   How the Goals are Met? PROTO-00


C.  Sending directed advertisements without the neighbour cache TENT-00
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
COMBO4B (How hosts are modified)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

1.  Introduction HOSTS-03
1.  Introduction CPL-02
1.  Introduction PROTO-00
1.  Introduction TENT-00


     1.1   Structure of this Document HOSTS-03

2.  Terms and Abbreviations  HOSTS-03
2.   Terms and Abbreviations PROTO-00



3.  Background & Motivation for DNA HOSTS-03
  3.1   Issues HOSTS-03

#
# Conceptual Overview...???
#
#
3.   Overview PROTO-00
  3.1  Link Identification PROTO-00

#
# Procedural Overview...???
#
#
4.  Detecting Network Attachment Steps HOSTS-03
  4.1   Making use of Prior Information HOSTS-03
  4.2   Link identification HOSTS-03
    4.2.1   Same link HOSTS-03
    4.2.2   Link change HOSTS-03
  4.3   IP Hosts Configuration HOSTS-03
  4.4   Duplicate Address Detection HOSTS-03
  4.5   Multicast Listener State HOSTS-03
  4.6   Reachability detection HOSTS-03


#
# Link Identification
#
#
2.   Prefix list based approach CPL-02 
  2.1  Approach CPL-02 
  2.2  Assumptions CPL-02 
  2.3  Overview CPL-02 
#
#  Cut down on some protocol explanations if shift
#  conceptual text here.
#
#
#

#
# Message Formats
#
#
4.   Message Formats PROTO-00
  4.1  Router Advertisement PROTO-00
  4.2  Prefix Information Option LinkID Bit PROTO-00
  4.3  Landmark Option PROTO-00
  4.4  Learned Prefix Option PROTO-00

  1.1   Tentative Option format TENT-00
  1.2   Tentative Option semantics TENT-00


#
#   Host Operations
#
#
  5.2  DNA Host Operation PROTO-00
    5.2.1  Data Structures PROTO-00
    5.2.2  Host Configuration Variables PROTO-00
4.   Protocol Specification CPL-02 
  4.1  Conceptual data structures CPL-02 

5.  Initiation of DNA Procedures HOSTS-03
  4.4  Receiving link UP notifications CPL-02 
  5.1   Actions Upon Hint Reception HOSTS-03
  5.2   Hints Due to Network Layer Messages HOSTS-03
  5.3   Handling Hints from Other Layers HOSTS-03
  5.4   Timer and Loss Based Hints HOSTS-03
  5.5   Simultaneous Hints HOSTS-03
  5.6   Hint Management for Inactive Hosts HOSTS-03



# Sending RSs
    5.2.4  Sending Router Solicitations PROTO-00
    5.2.3  Selection of a Landmark Prefix PROTO-00
2.  Sending solicitations containing Tentative Options TENT-00 
  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
  2.2   Sending Router Solicitations with Tentative Options TENT-00

# Receiving RAs.
  4.5  Receiving valid Router Advertisements CPL-02 
    5.2.5  Processing Router Advertisements PROTO-00
  3.3  Link identity detection CPL-02  
  3.   DNA based on the Complete Prefix List CPL-02 
  3.1  Complete Prefix List generation CPL-02 
  4.2  Merging Candidate Link objects CPL-02 

  4.6  Changing the link in Neighbor Discovery CPL-02 
    5.2.6  DNA and Address Configuration PROTO-00



# Timers?????
  3.2  Erroneous Prefix Lists CPL-02  
  3.4  Renumbering CPL-02  
  4.3  Timer handling and Garbage Collection CPL-02  

#
# Limitations of DNA
#
#
6.  Complications to Detecting Network Attachment HOSTS-03
  6.1   Packet Loss HOSTS-03
  6.2   Router Configurations HOSTS-03
  6.3   Overlapping Coverage HOSTS-03
  6.4   Multicast Snooping HOSTS-03
  6.5   Link Partition HOSTS-03


#
# Backward compatability
#
6.   Backward Compatibility PROTO-00
  6.2  DNA Host with Non-DNA Routers PROTO-00
#
# Constants
#
#
8.  Constants HOSTS-03
9.  Protocol Constants CPL-02


#
# IANA Considerations
#
#
6.   IANA Considerations CPL-02  
8.   IANA Considerations PROTO-00
4.   IANA Considerations TENT-00 



#
# Security Considerations
#
#
7.  Security Considerations CPL-02 
7.  Security Considerations HOSTS-03
7.  Security Considerations PROTO-00
5.  Security Considerations TENT-00
  7.2  Attacks on DNA Hosts PROTO-00
  7.1   Authorization and Detecting Network Attachment HOSTS-03
  7.2   Addressing HOSTS-03

#
# Appendices
#
#
A.   How the Goals are Met? PROTO-00

11.  Performance Analysis CPL-02

8.   Examples CPL-02 
  8.1  Example CPL-02 
  8.2  Example CPL-02  

A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
  A.1   Constraints on Neighbour Solicitations TENT-00
  A.2   Constraints on Router Solicitations TENT-00

B.  Interactions with legacy nodes TENT-00
  B.1   Legacy Neighbour Solicitation processing TENT-00 
  B.2   Legacy Router Solicitation processing TENT-00 




From dna-owner@webcamserver.eng.monash.edu.au Sat May 13 15:46:24 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ff04G-0004zD-94
	for dna-archive@lists.ietf.org; Sat, 13 May 2006 15:46:24 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ff04E-0007wr-72
	for dna-archive@lists.ietf.org; Sat, 13 May 2006 15:46:24 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2EGJ5ETAW8WXC7Q@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 14 May 2006 05:46:08 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 04709AB543; Sun,
 14 May 2006 05:46:06 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id AFDD54FB04; Sun,
 14 May 2006 05:46:05 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4DJidX10774	for dna-list; Sun, 14 May 2006 05:44:39 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4DJicu10770	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 14 May 2006 05:44:38 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2EGH110V68WXC7Q@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 14 May 2006 05:44:23 +1000
Received: by localhost (Postfix, from userid 510)	id 80E13AB542; Sun,
 14 May 2006 05:44:23 +1000 (EST)
Received: from fridge.docomolabs-usa.com
 (key1.docomolabs-usa.com [216.98.102.225])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id BB8324FB02; Sun, 14 May 2006 05:44:21 +1000 (EST)
Date: Sat, 13 May 2006 12:45:00 -0700
From: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [DNA] Merger: All Documents together (2)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <Greg.Daley@eng.monash.edu.au>, dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <005401c676c5$b915db10$626015ac@dcml.docomolabsusa.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level: *
References: <f67cb78543ca.43caf67cb785@monash.edu.au>
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa

I like COMBO2. As I've said in the past, I believe having seperate documents 
that deal with micro-pieces of a protocol make it more difficult for 
implementors to follow given the primitive state of IETF's documentation 
technology.

            jak

----- Original Message ----- 
From: "Greg Daley" <Greg.Daley@eng.monash.edu.au>
To: <dna@eng.monash.edu.au>
Cc: <narten@us.ibm.com>
Sent: Friday, May 12, 2006 5:46 PM
Subject: [DNA] Merger: All Documents together (2)


> Hi,
>
> This is an amalgamation of the DNA documents together
> in a form roughly inspired by RFC2461 Neighbor Discovery.
>
> This embodies an example of option 2 for document merger.
>
> Please note that there are duplicate section names, and
> each actual section may cover overlapping topics with
> other protocols.  Please try to ignore this fact initially,
> and concentrate on the overall structure of the document.
>
> When Referring to this proposal, it may be useful to describe
> it at COMBO2.
>
> Greg
>
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> COMBO2: All combined
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
> 1.  Introduction HOSTS-03
> 1.  Introduction CPL-02
> 1.  Introduction PROTO-00
> 1.  Introduction TENT-00
>
>
>     1.1   Structure of this Document HOSTS-03
>
> 2.  Terms and Abbreviations  HOSTS-03
> 2.   Terms and Abbreviations PROTO-00
>
>
>
> 3.  Background & Motivation for DNA HOSTS-03
>  3.1   Issues HOSTS-03
>
> #
> # Conceptual Overview...???
> #
> #
> 3.   Overview PROTO-00
>  3.1  Link Identification PROTO-00
>  3.2  Fast Router Advertisement PROTO-00
>
> #
> # Procedural Overview...???
> #
> #
> 4.  Detecting Network Attachment Steps HOSTS-03
>  4.1   Making use of Prior Information HOSTS-03
>  4.2   Link identification HOSTS-03
>    4.2.1   Same link HOSTS-03
>    4.2.2   Link change HOSTS-03
>  4.3   IP Hosts Configuration HOSTS-03
>  4.4   Duplicate Address Detection HOSTS-03
>  4.5   Multicast Listener State HOSTS-03
>  4.6   Reachability detection HOSTS-03
>
>
> #
> # Link Identification
> #
> #
> 2.   Prefix list based approach CPL-02
>  2.1  Approach CPL-02
>  2.2  Assumptions CPL-02
>  2.3  Overview CPL-02
> #
> #  Cut down on some protocol explanations if shift
> #  conceptual text here.
> #
> #
> #
>
> #
> # Message Formats
> #
> #
> 4.   Message Formats PROTO-00
>  4.1  Router Advertisement PROTO-00
>  4.2  Prefix Information Option LinkID Bit PROTO-00
>  4.3  Landmark Option PROTO-00
>  4.4  Learned Prefix Option PROTO-00
>
>  1.1   Tentative Option format TENT-00
>  1.2   Tentative Option semantics TENT-00
>
>
> #
> #   Host Operations
> #
> #
>  5.2  DNA Host Operation PROTO-00
>    5.2.1  Data Structures PROTO-00
>    5.2.2  Host Configuration Variables PROTO-00
> 4.   Protocol Specification CPL-02
>  4.1  Conceptual data structures CPL-02
>
> 5.  Initiation of DNA Procedures HOSTS-03
>  4.4  Receiving link UP notifications CPL-02
>  5.1   Actions Upon Hint Reception HOSTS-03
>  5.2   Hints Due to Network Layer Messages HOSTS-03
>  5.3   Handling Hints from Other Layers HOSTS-03
>  5.4   Timer and Loss Based Hints HOSTS-03
>  5.5   Simultaneous Hints HOSTS-03
>  5.6   Hint Management for Inactive Hosts HOSTS-03
>
>
>
> # Sending RSs
>    5.2.4  Sending Router Solicitations PROTO-00
>    5.2.3  Selection of a Landmark Prefix PROTO-00
> 2.  Sending solicitations containing Tentative Options TENT-00
>  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00
>  2.2   Sending Router Solicitations with Tentative Options TENT-00
>
> # Receiving RAs.
>  4.5  Receiving valid Router Advertisements CPL-02
>    5.2.5  Processing Router Advertisements PROTO-00
>  3.3  Link identity detection CPL-02
>  3.   DNA based on the Complete Prefix List CPL-02
>  3.1  Complete Prefix List generation CPL-02
>  4.2  Merging Candidate Link objects CPL-02
>
>  4.6  Changing the link in Neighbor Discovery CPL-02
>    5.2.6  DNA and Address Configuration PROTO-00
>
>
>
> # Timers?????
>  3.2  Erroneous Prefix Lists CPL-02
>  3.4  Renumbering CPL-02
>  4.3  Timer handling and Garbage Collection CPL-02
>
> #
> #  Router Operations
> #
> #
>  5.1  DNA Router Operation PROTO-00
>    5.1.1  Data Structures PROTO-00
>    5.1.2  Router Configuration Variables PROTO-00
>    5.1.3  Bootstrapping DNA Data Structures PROTO-00
>    5.1.4  Processing Router Advertisements PROTO-00
>    5.1.5  Processing Router Solicitations PROTO-00
>    5.1.6  Complete Router Advertisements PROTO-00
>    5.1.7  LinkID PROTO-00
>    5.1.8  Scheduling Fast Router Advertisements PROTO-00
>    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
>    5.1.10   Removing a Prefix from an Interface PROTO-00
>    5.1.11   Prefix Reassignment PROTO-00
> 3.  Receiving Tentative Options TENT-00
>  3.1   Handling Tentative Options TENT-00
>  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
>        Options TENT-00
>  3.3   Receiving Router Solicitations containing Tentative TENT-00
>        Options TENT-00
>
> #
> # Limitations of DNA
> #
> #
> 6.  Complications to Detecting Network Attachment HOSTS-03
>  6.1   Packet Loss HOSTS-03
>  6.2   Router Configurations HOSTS-03
>  6.3   Overlapping Coverage HOSTS-03
>  6.4   Multicast Snooping HOSTS-03
>  6.5   Link Partition HOSTS-03
>
>
> #
> # Backward compatability
> #
> 6.   Backward Compatibility PROTO-00
>  6.1  Non-DNA Host with DNA Routers PROTO-00
>  6.2  DNA Host with Non-DNA Routers PROTO-00
> 5.   CPL without a 'link UP' notification CPL-02
>  #
> # Constants
> #
> #
> 8.  Constants HOSTS-03
> 9.  Protocol Constants CPL-02
>
>
> #
> # IANA Considerations
> #
> #
> 6.   IANA Considerations CPL-02
> 8.   IANA Considerations PROTO-00
> 4.   IANA Considerations TENT-00
>
>
>
> #
> # Security Considerations
> #
> #
> 7.  Security Considerations CPL-02
> 7.  Security Considerations HOSTS-03
> 7.  Security Considerations PROTO-00
> 5.  Security Considerations TENT-00
>  7.1  Attacks on the Token Bucket PROTO-00
>  7.2  Attacks on DNA Hosts PROTO-00
>  7.1   Authorization and Detecting Network Attachment HOSTS-03
>  7.2   Addressing HOSTS-03
>
> #
> # Appendices
> #
> #
> A.   How the Goals are Met? PROTO-00
>
> 11.  Performance Analysis CPL-02
>
> 8.   Examples CPL-02
>  8.1  Example CPL-02
>  8.2  Example CPL-02
>
> A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
>  A.1   Constraints on Neighbour Solicitations TENT-00
>  A.2   Constraints on Router Solicitations TENT-00
>
> B.  Interactions with legacy nodes TENT-00
>  B.1   Legacy Neighbour Solicitation processing TENT-00
>  B.2   Legacy Router Solicitation processing TENT-00
>
> C.  Sending directed advertisements without the neighbour cache TENT-00
>
>
> 





From dna-owner@webcamserver.eng.monash.edu.au Sat May 13 16:22:07 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ff0cp-0001OV-DV
	for dna-archive@lists.ietf.org; Sat, 13 May 2006 16:22:07 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ff0cm-0000lj-B5
	for dna-archive@lists.ietf.org; Sat, 13 May 2006 16:22:07 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2EHRL11F88WXC7Q@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 14 May 2006 06:21:57 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 668A7AB543; Sun,
 14 May 2006 06:21:55 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 228044FB07; Sun, 14 May 2006 06:21:55 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4DKLan11155	for dna-list; Sun, 14 May 2006 06:21:36 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4DKLZu11151	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 14 May 2006 06:21:35 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2EHR5PX8091X3M2@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 14 May 2006 06:21:35 +1000
Received: by localhost (Postfix, from userid 510)	id F17C6AB542; Sun,
 14 May 2006 06:21:34 +1000 (EST)
Received: from fridge.docomolabs-usa.com
 (key1.docomolabs-usa.com [216.98.102.225])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 65F4D4FB09	for <dna@eng.monash.edu.au>; Sun,
 14 May 2006 06:21:33 +1000 (EST)
Date: Sat, 13 May 2006 13:22:09 -0700
From: James Kempf <kempf@docomolabs-usa.com>
Subject: [DNA] Text on Router Reachability for DNA Protocol Specification
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Cc: Kempf <kempf@docomolabs-usa.com>
Message-id: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level: *
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976

In line with Greg's posting about combining drafts, I'm reposting a proposal 
I made after the Dallas IETF about adding some text about router 
reachability to the DNA protocol draft. The text would go into whichever 
draft dealt with host specifications. The problem is that in the current 
DNAv6 solution draft (draft-ietf-dna-protocol-00.txt), address reachability 
is discussed in Section 5.2.6 but there is no text discussing router 
reachablity after a potential Layer 2 handover. This in contrast to the 
DNAv4 draft:

http://www.drizzle.com/~aboba/DNA/draft-ietf-dhc-dna-ipv4-18.txt

which specifies the use of unicast ARP to the mobile node's current default
router in order to confirm bidirectional reachability and discusses router
reachability extensively. Bernard Abboba's draft on architectural link
indications:

http://www.iab.org/documents/drafts/draft-iab-link-indications-04.txt

contains an excellent discussion of why bidirectional reachability tests at
the IP layer are necessary for 802.11-like protocols (they aren't for
cellular, but that is a different story).

Since the current draft says nothing about router reachability detection,
the mobile node would fall back to the NUD procedure described in Section
7.3 of RFC 2461, which does not distinguish between routers and other nodes.
This procedure is likely to be lengthy, and is completely unnnecesary
because the mobile node has already confirmed reachability through the
multicast DNA RS/unicast DNA RA. So the need is for some text in
draft-ietf-dna-protocol-00.txt to specify how the mobile node uses this
information to update its Default Router List.

Below is some proposed text for this (thanx to Christian Vogt for help in
formulating it). If anybody has suggestions for improvement, please
send them so we can have a discussion. I would like to propose
to the WG that this text be accepted into the merged protocol document
when it is decided.

                jak

-----------------------------

Remove the last paragraph in Section 5.2.5, put in the following new section
after Section 5.2.5.1.

5.2.5.2 Router Reachability Detection and Default Router Selection

The receipt of a unicast RA from a router in response to a multicast RS
indicates that the host has bi-directional reachability with the routers
that responded. Such reachability is necessary for the host to use a router
as a default router, in order to have packets routed off the host's current
link. If the destination address of the received RA is a unicast address,
the host knows the router heard its RS, and therefore that the host
has reachability with the router.

Prior to sending a DNA RS in response to an indication of link change,
the host SHOULD set all Neighbor Cache entries for routers on its Default
Router List to STALE. When the host receives an RS in reply to the RA, the
host SHOULD mark that router's Neighbor Cache Entry [3] as REACHABLE,
or add a Neighbor Cache Entry in the REACHABLE state if one does not
currently exist.

The host SHOULD also update its Default Router List in the following
fashion. If any of the routers returning RAs are already on the default
router list, the host SHOULD use the information in the RA to update the
Default Route List entry with the new information. The host SHOULD
add entries to the Default Router List for any routers returning RAs that
are not on the list.The host SHOULD confine selection of a router from the
Default Router List to those routers whose Neighbor Cache entries are in the
REACHABLE state. Note that the Default Router List SHOULD be updated as
described here regardless of whether the RA indicates that the host has
changed to a new IP link, since changes in router reachability are possible
on some link types even if the host remains on the same IP link.

Note that this procedure does not prevent a MN from sending packets to its
current default router while the RA solicitation is in progress and if
reachability with the current default router is unchanged, there should
be no change in default router after the RA solicitation completes. If the
current default router is still reachable, it will forward the packets.






From dna-owner@webcamserver.eng.monash.edu.au Sun May 14 17:43:46 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfONO-0003DO-NR
	for dna-archive@lists.ietf.org; Sun, 14 May 2006 17:43:46 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FfONL-0000Bf-BW
	for dna-archive@lists.ietf.org; Sun, 14 May 2006 17:43:46 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2FYWW7XGM91XEIZ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 15 May 2006 07:43:25 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2860AAB543; Mon,
 15 May 2006 07:43:22 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id E80854FB03; Mon, 15 May 2006 07:43:21 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4ELeck24069	for dna-list; Mon, 15 May 2006 07:40:38 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4ELebu24065	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 15 May 2006 07:40:37 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2FYTETDPI8WXTH4@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 15 May 2006 07:40:35 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id DD35FAB542; Mon,
 15 May 2006 07:40:34 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by moe.its.monash.edu.au (Postfix) with ESMTP id C9F504FB09; Mon,
 15 May 2006 07:40:34 +1000 (EST)
Received: from [68.36.162.17] by mail-store-2.its.monash.edu.au (mshttpd); Sun,
 14 May 2006 17:40:33 -0400
Date: Sun, 14 May 2006 17:40:33 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: Re: [DNA] Text on Router Reachability for DNA Protocol Specification
In-reply-to: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: James Kempf <kempf@docomolabs-usa.com>
Cc: Dna <dna@eng.monash.edu.au>, Kempf <kempf@docomolabs-usa.com>
Message-id: <f5ff834e3d.3df5ff834e@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
References: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003


Hi James,

thanks for that.

There's been some text on reachability detection in the
hosts draft.   IMO, if we're combining documents, this may
give us text which suffice for the same purpose, matched
to the -protocol- document style.

Greg

----- Original Message -----
From: James Kempf <kempf@docomolabs-usa.com>
Date: Saturday, May 13, 2006 4:22 pm
Subject: [DNA] Text on Router Reachability for DNA Protocol Specification
To: Dna <dna@eng.monash.edu.au>
Cc: Kempf <kempf@docomolabs-usa.com>

> In line with Greg's posting about combining drafts, I'm reposting a 
> proposal 
> I made after the Dallas IETF about adding some text about router 
> reachability to the DNA protocol draft. The text would go into 
> whichever 
> draft dealt with host specifications. The problem is that in the 
> current 
> DNAv6 solution draft (draft-ietf-dna-protocol-00.txt), address 
> reachability 
> is discussed in Section 5.2.6 but there is no text discussing 
> router 
> reachablity after a potential Layer 2 handover. This in contrast to 
> the 
> DNAv4 draft:
> 
> http://www.drizzle.com/~aboba/DNA/draft-ietf-dhc-dna-ipv4-18.txt
> 
> which specifies the use of unicast ARP to the mobile node's current 
> defaultrouter in order to confirm bidirectional reachability and 
> discusses router
> reachability extensively. Bernard Abboba's draft on architectural link
> indications:
> 
> http://www.iab.org/documents/drafts/draft-iab-link-indications-04.txt
> 
> contains an excellent discussion of why bidirectional reachability 
> tests at
> the IP layer are necessary for 802.11-like protocols (they aren't for
> cellular, but that is a different story).
> 
> Since the current draft says nothing about router reachability 
> detection,the mobile node would fall back to the NUD procedure 
> described in Section
> 7.3 of RFC 2461, which does not distinguish between routers and 
> other nodes.
> This procedure is likely to be lengthy, and is completely unnnecesary
> because the mobile node has already confirmed reachability through the
> multicast DNA RS/unicast DNA RA. So the need is for some text in
> draft-ietf-dna-protocol-00.txt to specify how the mobile node uses 
> thisinformation to update its Default Router List.
> 
> Below is some proposed text for this (thanx to Christian Vogt for 
> help in
> formulating it). If anybody has suggestions for improvement, please
> send them so we can have a discussion. I would like to propose
> to the WG that this text be accepted into the merged protocol document
> when it is decided.
> 
>                jak
> 
> -----------------------------
> 
> Remove the last paragraph in Section 5.2.5, put in the following 
> new section
> after Section 5.2.5.1.
> 
> 5.2.5.2 Router Reachability Detection and Default Router Selection
> 
> The receipt of a unicast RA from a router in response to a 
> multicast RS
> indicates that the host has bi-directional reachability with the 
> routersthat responded. Such reachability is necessary for the host 
> to use a router
> as a default router, in order to have packets routed off the host's 
> currentlink. If the destination address of the received RA is a 
> unicast address,
> the host knows the router heard its RS, and therefore that the host
> has reachability with the router.
> 
> Prior to sending a DNA RS in response to an indication of link change,
> the host SHOULD set all Neighbor Cache entries for routers on its 
> DefaultRouter List to STALE. When the host receives an RS in reply 
> to the RA, the
> host SHOULD mark that router's Neighbor Cache Entry [3] as REACHABLE,
> or add a Neighbor Cache Entry in the REACHABLE state if one does not
> currently exist.
> 
> The host SHOULD also update its Default Router List in the following
> fashion. If any of the routers returning RAs are already on the 
> defaultrouter list, the host SHOULD use the information in the RA 
> to update the
> Default Route List entry with the new information. The host SHOULD
> add entries to the Default Router List for any routers returning 
> RAs that
> are not on the list.The host SHOULD confine selection of a router 
> from the
> Default Router List to those routers whose Neighbor Cache entries 
> are in the
> REACHABLE state. Note that the Default Router List SHOULD be 
> updated as
> described here regardless of whether the RA indicates that the host 
> haschanged to a new IP link, since changes in router reachability 
> are possible
> on some link types even if the host remains on the same IP link.
> 
> Note that this procedure does not prevent a MN from sending packets 
> to its
> current default router while the RA solicitation is in progress and if
> reachability with the current default router is unchanged, there 
> shouldbe no change in default router after the RA solicitation 
> completes. If the
> current default router is still reachable, it will forward the 
> packets.
> 
> 
> 



From dna-owner@webcamserver.eng.monash.edu.au Mon May 15 10:11:20 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffdn6-000898-D2
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 10:11:20 -0400
Received: from alpha6.its.monash.edu.au ([130.194.1.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ffdn5-00056r-4b
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 10:11:20 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2GXEA1L7S8YDNC1@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 16 May 2006 00:11:05 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 7E4DAAB545; Tue,
 16 May 2006 00:10:54 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 3CE1E4FB04; Tue, 16 May 2006 00:10:54 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4FE6mX32372	for dna-list; Tue, 16 May 2006 00:06:48 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4FE6lu32368	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 16 May 2006 00:06:47 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2GX8THZFS91XI4K@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 16 May 2006 00:06:31 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 636C7AB542; Tue,
 16 May 2006 00:06:31 +1000 (EST)
Received: from [192.168.1.100] (cust1648.vic01.dataco.com.au [202.63.56.112])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	(Authenticated sender: brett)
	by moe.its.monash.edu.au (Postfix) with ESMTP id CD39A4FB06; Tue,
 16 May 2006 00:06:30 +1000 (EST)
Date: Tue, 16 May 2006 00:06:37 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Text on Router Reachability for DNA Protocol Specification
In-reply-to: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: James Kempf <kempf@docomolabs-usa.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <44688AED.7090107@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
References: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c

Hi James,

The proposed text looks very good (except for a swapped RS/RA - see
below).

An observation I have is that it seems that a single lost RA from the
default router that is "currently" being used would cause the host to
swap to a new default router, since the current one would be STALE and
there may be new ones that are REACHABLE.  Presumably this causes some
sort of (minor) disruption to the packet flow.

Would there be any value in having some sort of configuration variable
on the host to specify the number of missed RAs before switching to a
new default router when DNA otherwise indicates no movement?

Regards,
Brett.

James Kempf wrote:
> -----------------------------
> 
> Remove the last paragraph in Section 5.2.5, put in the following new 
> section
> after Section 5.2.5.1.
> 
> 5.2.5.2 Router Reachability Detection and Default Router Selection
> 
> The receipt of a unicast RA from a router in response to a multicast RS
> indicates that the host has bi-directional reachability with the routers
> that responded. Such reachability is necessary for the host to use a router
> as a default router, in order to have packets routed off the host's current
> link. If the destination address of the received RA is a unicast address,
> the host knows the router heard its RS, and therefore that the host
> has reachability with the router.
> 
> Prior to sending a DNA RS in response to an indication of link change,
> the host SHOULD set all Neighbor Cache entries for routers on its Default
> Router List to STALE. When the host receives an RS in reply to the RA, the
                                                   ^^                 ^^

> host SHOULD mark that router's Neighbor Cache Entry [3] as REACHABLE,
> or add a Neighbor Cache Entry in the REACHABLE state if one does not
> currently exist.
> 
> The host SHOULD also update its Default Router List in the following
> fashion. If any of the routers returning RAs are already on the default
> router list, the host SHOULD use the information in the RA to update the
> Default Route List entry with the new information. The host SHOULD
> add entries to the Default Router List for any routers returning RAs that
> are not on the list.The host SHOULD confine selection of a router from the
> Default Router List to those routers whose Neighbor Cache entries are in 
> the
> REACHABLE state. Note that the Default Router List SHOULD be updated as
> described here regardless of whether the RA indicates that the host has
> changed to a new IP link, since changes in router reachability are possible
> on some link types even if the host remains on the same IP link.
> 
> Note that this procedure does not prevent a MN from sending packets to its
> current default router while the RA solicitation is in progress and if
> reachability with the current default router is unchanged, there should
> be no change in default router after the RA solicitation completes. If the
> current default router is still reachable, it will forward the packets.
> 
> 
> 




From dna-owner@webcamserver.eng.monash.edu.au Mon May 15 13:07:25 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfgXV-0001GJ-P3
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 13:07:25 -0400
Received: from alpha1.its.monash.edu.au ([130.194.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FfgXS-0007Hn-Mt
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 13:07:25 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2H3JJ7KQ08X7EXF@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 16 May 2006 03:07:14 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A508E80003; Tue,
 16 May 2006 03:06:56 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 5E9233C007; Tue, 16 May 2006 03:06:56 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4FH6A301534	for dna-list; Tue, 16 May 2006 03:06:10 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4FH69u01530	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 16 May 2006 03:06:09 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2H3I8SXRW8X7EXF@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 16 May 2006 03:05:54 +1000
Received: by localhost (Postfix, from userid 510)	id 85E0FAB542; Tue,
 16 May 2006 03:05:54 +1000 (EST)
Received: from fridge.docomolabs-usa.com
 (key1.docomolabs-usa.com [216.98.102.225])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 3C0994FB03; Tue, 16 May 2006 03:05:53 +1000 (EST)
Date: Mon, 15 May 2006 10:06:31 -0700
From: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [DNA] Text on Router Reachability for DNA Protocol Specification
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <012401c67841$ea634720$626015ac@dcml.docomolabsusa.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level: *
References: <00a501c676ca$e9fd22b0$626015ac@dcml.docomolabsusa.com>
 <44688AED.7090107@eng.monash.edu.au>
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

Brett,

I have no problem with the configuration variable.

Regarding the missed RA, you are right but I think this is likely to be a 
relatively infrequent event on a single link, somewhat equivalent to 
handover but even more infrequent. However, I agree that some kind of 
configuratable variable for lazy v.s. eager switching should be OK.

            jak

----- Original Message ----- 
From: "Brett Pentland" <brett.pentland@eng.monash.edu.au>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Dna" <dna@eng.monash.edu.au>
Sent: Monday, May 15, 2006 7:06 AM
Subject: Re: [DNA] Text on Router Reachability for DNA Protocol 
Specification


> Hi James,
>
> The proposed text looks very good (except for a swapped RS/RA - see
> below).
>
> An observation I have is that it seems that a single lost RA from the
> default router that is "currently" being used would cause the host to
> swap to a new default router, since the current one would be STALE and
> there may be new ones that are REACHABLE.  Presumably this causes some
> sort of (minor) disruption to the packet flow.
>
> Would there be any value in having some sort of configuration variable
> on the host to specify the number of missed RAs before switching to a
> new default router when DNA otherwise indicates no movement?
>
> Regards,
> Brett.
>
> James Kempf wrote:
>> -----------------------------
>>
>> Remove the last paragraph in Section 5.2.5, put in the following new 
>> section
>> after Section 5.2.5.1.
>>
>> 5.2.5.2 Router Reachability Detection and Default Router Selection
>>
>> The receipt of a unicast RA from a router in response to a multicast RS
>> indicates that the host has bi-directional reachability with the routers
>> that responded. Such reachability is necessary for the host to use a 
>> router
>> as a default router, in order to have packets routed off the host's 
>> current
>> link. If the destination address of the received RA is a unicast address,
>> the host knows the router heard its RS, and therefore that the host
>> has reachability with the router.
>>
>> Prior to sending a DNA RS in response to an indication of link change,
>> the host SHOULD set all Neighbor Cache entries for routers on its Default
>> Router List to STALE. When the host receives an RS in reply to the RA, 
>> the
>                                                   ^^                 ^^
>
>> host SHOULD mark that router's Neighbor Cache Entry [3] as REACHABLE,
>> or add a Neighbor Cache Entry in the REACHABLE state if one does not
>> currently exist.
>>
>> The host SHOULD also update its Default Router List in the following
>> fashion. If any of the routers returning RAs are already on the default
>> router list, the host SHOULD use the information in the RA to update the
>> Default Route List entry with the new information. The host SHOULD
>> add entries to the Default Router List for any routers returning RAs that
>> are not on the list.The host SHOULD confine selection of a router from 
>> the
>> Default Router List to those routers whose Neighbor Cache entries are in 
>> the
>> REACHABLE state. Note that the Default Router List SHOULD be updated as
>> described here regardless of whether the RA indicates that the host has
>> changed to a new IP link, since changes in router reachability are 
>> possible
>> on some link types even if the host remains on the same IP link.
>>
>> Note that this procedure does not prevent a MN from sending packets to 
>> its
>> current default router while the RA solicitation is in progress and if
>> reachability with the current default router is unchanged, there should
>> be no change in default router after the RA solicitation completes. If 
>> the
>> current default router is still reachable, it will forward the packets.
>>
>>
>>
>
> 





From dna-owner@webcamserver.eng.monash.edu.au Mon May 15 16:47:12 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfjyC-0001ob-S2
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 16:47:12 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FfjN5-0000Vo-9z
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 16:08:51 -0400
Received: from alpha6.its.monash.edu.au ([130.194.1.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Ffj8b-0003FE-Qk
	for dna-archive@lists.ietf.org; Mon, 15 May 2006 15:53:55 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2H9CWFQDA8YD7XQ@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 16 May 2006 05:53:39 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B7A94AB543; Tue,
 16 May 2006 05:53:23 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 7A6004FB03; Tue, 16 May 2006 05:53:23 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4FJoPY03236	for dna-list; Tue, 16 May 2006 05:50:25 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4FJoPu03232	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 16 May 2006 05:50:25 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2H98X8WLM91XJ28@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 16 May 2006 05:50:12 +1000
Received: by localhost (Postfix, from userid 510)	id 18121AB542; Tue,
 16 May 2006 05:50:12 +1000 (EST)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by curly.its.monash.edu.au (Postfix)
 with ESMTP id CEE694FB0B	for <dna@eng.monash.edu.au>; Tue,
 16 May 2006 05:50:10 +1000 (EST)
Received: from stiedprstage1.ietf.org
 (stiedprstage1.va.neustar.com [10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k4FJo2et004538
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon,
 15 May 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Ffj4s-0007VO-FS; Mon, 15 May 2006 15:50:02 -0400
Date: Mon, 15 May 2006 15:50:02 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-hosts-03.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <E1Ffj4s-0007VO-FS@stiedprstage1.ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_U7T7YUlkwJ+Cz/z5veCPbg)"
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168


--Boundary_(ID_U7T7YUlkwJ+Cz/z5veCPbg)
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Detecting Network Attachment Working Group of the IETF.

	Title		: Detecting Network Attachment in IPv6 - Best Current Practices for hosts.
	Author(s)	: S. Narayanan, et al.
	Filename	: draft-ietf-dna-hosts-03.txt
	Pages		: 21
	Date		: 2006-5-15
	
Hosts experiencing rapid link-layer changes may require efficient IP
configuration change detection procedures than traditional fixed
hosts.  DNA is defined as the process by which a host collects
appropriate information and detects the identity of its currently
attached link to ascertain the validity of its IP configuration.
This document details best current practice for Detecting Network
Attachment in IPv6 hosts using existing Neighbor Discovery
procedures.  Since there is no explicit link identification mechanism
in the existing Neighbor Discovery for IP Version 6, the document
describes implicit mechanisms for identifying the current link.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dna-hosts-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dna-hosts-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dna-hosts-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_U7T7YUlkwJ+Cz/z5veCPbg)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_gmaU9YIRO29QpDWDVeKThw)"


--Boundary_(ID_gmaU9YIRO29QpDWDVeKThw)
Content-type: Message/External-body; access-type=mail-server;
 server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2006-5-15111230.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dna-hosts-03.txt

--Boundary_(ID_gmaU9YIRO29QpDWDVeKThw)
Content-type: Message/External-body; name=draft-ietf-dna-hosts-03.txt;
 site=ftp.ietf.org; access-type=anon-ftp; directory=internet-drafts
Content-disposition: attachment; filename=draft-ietf-dna-hosts-03.txt

Content-Type: text/plain
Content-ID:	<2006-5-15111230.I-D@ietf.org>

--Boundary_(ID_gmaU9YIRO29QpDWDVeKThw)--

--Boundary_(ID_U7T7YUlkwJ+Cz/z5veCPbg)--



From dna-owner@webcamserver.eng.monash.edu.au Tue May 16 00:21:27 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffr3n-0004gX-Ph
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 00:21:27 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ffr3j-0005pf-EA
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 00:21:27 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2HR2UY8RQ8WXWLV@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 16 May 2006 14:20:50 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 87AD080003; Tue,
 16 May 2006 14:20:47 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 34FA93C003; Tue, 16 May 2006 14:20:47 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4G4Gjj07964	for dna-list; Tue, 16 May 2006 14:16:45 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4G4Gju07960	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 16 May 2006 14:16:45 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2HQXM2YXQ8WY0CR@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 16 May 2006 14:16:29 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2DFC680003; Tue,
 16 May 2006 14:16:29 +1000 (EST)
Received: from monash.edu.au (balamb.its.monash.edu.au [130.194.11.237])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 1AEB73C003; Tue,
 16 May 2006 14:16:29 +1000 (EST)
Received: from [147.76.180.135] by mail-store-1.its.monash.edu.au (mshttpd)
 ; Tue, 16 May 2006 14:16:28 +1000
Date: Tue, 16 May 2006 14:16:28 +1000
From: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
Subject: Re: [DNA] Merger: All Documents together (2)
In-reply-to: <f67cb78543ca.43caf67cb785@monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <Greg.Daley@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au, narten@us.ibm.com
Message-id: <f44331444eb7.4eb7f4433144@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
References: <f67cb78543ca.43caf67cb785@monash.edu.au>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b

I like COMBO2.

The PROTO document is already dependent on both TENT and CPL and there
are synergies with what's in HOSTS as well.  If they were simple self
contained ideas (TENT is) then it might be good to keep them separate
but I don't think they are and the array of documents at the minute is
probably more confusing than helpful.

Combining them won't be trivial, and will require a really good
introduction to make it clear how the pieces go together, but it's
probably worth the effort.

One difficulty I see is that PROTO describes router behaviour, as well
as host behaviour, and I don't think it makes sense to separate them as
the protocol modifications only make sense when both sides are considered.

So do we pull the ROUTERS document in as well?  That I'm not sure about.
 Any thoughts, anyone?

Brett.

----- Original Message -----
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Date: Saturday, May 13, 2006 10:47 am
Subject: [DNA] Merger: All Documents together (2)
To: dna@eng.monash.edu.au
Cc: narten@us.ibm.com

> Hi,
> 
> This is an amalgamation of the DNA documents together
> in a form roughly inspired by RFC2461 Neighbor Discovery.
> 
> This embodies an example of option 2 for document merger.
> 
> Please note that there are duplicate section names, and
> each actual section may cover overlapping topics with 
> other protocols.  Please try to ignore this fact initially,
> and concentrate on the overall structure of the document.
> 
> When Referring to this proposal, it may be useful to describe
> it at COMBO2.
> 
> Greg
> 
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> COMBO2: All combined
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> 
> 1.  Introduction HOSTS-03
> 1.  Introduction CPL-02
> 1.  Introduction PROTO-00
> 1.  Introduction TENT-00
> 
> 
>     1.1   Structure of this Document HOSTS-03
> 
> 2.  Terms and Abbreviations  HOSTS-03
> 2.   Terms and Abbreviations PROTO-00
> 
> 
> 
> 3.  Background & Motivation for DNA HOSTS-03
>  3.1   Issues HOSTS-03
> 
> #
> # Conceptual Overview...???
> #
> #
> 3.   Overview PROTO-00
>  3.1  Link Identification PROTO-00
>  3.2  Fast Router Advertisement PROTO-00
> 
> #
> # Procedural Overview...???
> #
> #
> 4.  Detecting Network Attachment Steps HOSTS-03
>  4.1   Making use of Prior Information HOSTS-03
>  4.2   Link identification HOSTS-03
>    4.2.1   Same link HOSTS-03
>    4.2.2   Link change HOSTS-03
>  4.3   IP Hosts Configuration HOSTS-03
>  4.4   Duplicate Address Detection HOSTS-03
>  4.5   Multicast Listener State HOSTS-03
>  4.6   Reachability detection HOSTS-03
> 
> 
> #
> # Link Identification
> #
> #
> 2.   Prefix list based approach CPL-02 
>  2.1  Approach CPL-02 
>  2.2  Assumptions CPL-02 
>  2.3  Overview CPL-02 
> #
> #  Cut down on some protocol explanations if shift
> #  conceptual text here.
> #
> #
> #
> 
> #
> # Message Formats
> #
> #
> 4.   Message Formats PROTO-00
>  4.1  Router Advertisement PROTO-00
>  4.2  Prefix Information Option LinkID Bit PROTO-00
>  4.3  Landmark Option PROTO-00
>  4.4  Learned Prefix Option PROTO-00
> 
>  1.1   Tentative Option format TENT-00
>  1.2   Tentative Option semantics TENT-00
> 
> 
> #
> #   Host Operations
> #
> #
>  5.2  DNA Host Operation PROTO-00
>    5.2.1  Data Structures PROTO-00
>    5.2.2  Host Configuration Variables PROTO-00
> 4.   Protocol Specification CPL-02 
>  4.1  Conceptual data structures CPL-02 
> 
> 5.  Initiation of DNA Procedures HOSTS-03
>  4.4  Receiving link UP notifications CPL-02 
>  5.1   Actions Upon Hint Reception HOSTS-03
>  5.2   Hints Due to Network Layer Messages HOSTS-03
>  5.3   Handling Hints from Other Layers HOSTS-03
>  5.4   Timer and Loss Based Hints HOSTS-03
>  5.5   Simultaneous Hints HOSTS-03
>  5.6   Hint Management for Inactive Hosts HOSTS-03
> 
> 
> 
> # Sending RSs
>    5.2.4  Sending Router Solicitations PROTO-00
>    5.2.3  Selection of a Landmark Prefix PROTO-00
> 2.  Sending solicitations containing Tentative Options TENT-00 
>  2.1   Sending Neighbour Solicitations with Tentative Options TENT-
> 00 
>  2.2   Sending Router Solicitations with Tentative Options TENT-00
> 
> # Receiving RAs.
>  4.5  Receiving valid Router Advertisements CPL-02 
>    5.2.5  Processing Router Advertisements PROTO-00
>  3.3  Link identity detection CPL-02  
>  3.   DNA based on the Complete Prefix List CPL-02 
>  3.1  Complete Prefix List generation CPL-02 
>  4.2  Merging Candidate Link objects CPL-02 
> 
>  4.6  Changing the link in Neighbor Discovery CPL-02 
>    5.2.6  DNA and Address Configuration PROTO-00
> 
> 
> 
> # Timers?????
>  3.2  Erroneous Prefix Lists CPL-02  
>  3.4  Renumbering CPL-02  
>  4.3  Timer handling and Garbage Collection CPL-02  
> 
> #
> #  Router Operations
> #
> #
>  5.1  DNA Router Operation PROTO-00
>    5.1.1  Data Structures PROTO-00
>    5.1.2  Router Configuration Variables PROTO-00
>    5.1.3  Bootstrapping DNA Data Structures PROTO-00
>    5.1.4  Processing Router Advertisements PROTO-00
>    5.1.5  Processing Router Solicitations PROTO-00
>    5.1.6  Complete Router Advertisements PROTO-00
>    5.1.7  LinkID PROTO-00
>    5.1.8  Scheduling Fast Router Advertisements PROTO-00
>    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
>    5.1.10   Removing a Prefix from an Interface PROTO-00
>    5.1.11   Prefix Reassignment PROTO-00
> 3.  Receiving Tentative Options TENT-00
>  3.1   Handling Tentative Options TENT-00 
>  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
>        Options TENT-00
>  3.3   Receiving Router Solicitations containing Tentative TENT-00
>        Options TENT-00
> 
> #
> # Limitations of DNA
> #
> #
> 6.  Complications to Detecting Network Attachment HOSTS-03
>  6.1   Packet Loss HOSTS-03
>  6.2   Router Configurations HOSTS-03
>  6.3   Overlapping Coverage HOSTS-03
>  6.4   Multicast Snooping HOSTS-03
>  6.5   Link Partition HOSTS-03
> 
> 
> #
> # Backward compatability
> #
> 6.   Backward Compatibility PROTO-00
>  6.1  Non-DNA Host with DNA Routers PROTO-00
>  6.2  DNA Host with Non-DNA Routers PROTO-00
> 5.   CPL without a 'link UP' notification CPL-02 
>  #
> # Constants
> #
> #
> 8.  Constants HOSTS-03
> 9.  Protocol Constants CPL-02
> 
> 
> #
> # IANA Considerations
> #
> #
> 6.   IANA Considerations CPL-02  
> 8.   IANA Considerations PROTO-00
> 4.   IANA Considerations TENT-00 
> 
> 
> 
> #
> # Security Considerations
> #
> #
> 7.  Security Considerations CPL-02 
> 7.  Security Considerations HOSTS-03
> 7.  Security Considerations PROTO-00
> 5.  Security Considerations TENT-00
>  7.1  Attacks on the Token Bucket PROTO-00
>  7.2  Attacks on DNA Hosts PROTO-00
>  7.1   Authorization and Detecting Network Attachment HOSTS-03
>  7.2   Addressing HOSTS-03
> 
> #
> # Appendices
> #
> #
> A.   How the Goals are Met? PROTO-00
> 
> 11.  Performance Analysis CPL-02
> 
> 8.   Examples CPL-02 
>  8.1  Example CPL-02 
>  8.2  Example CPL-02  
> 
> A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
>  A.1   Constraints on Neighbour Solicitations TENT-00
>  A.2   Constraints on Router Solicitations TENT-00
> 
> B.  Interactions with legacy nodes TENT-00
>  B.1   Legacy Neighbour Solicitation processing TENT-00 
>  B.2   Legacy Router Solicitation processing TENT-00 
> 
> C.  Sending directed advertisements without the neighbour cache 
> TENT-00
> 
> 
> 



From dna-owner@webcamserver.eng.monash.edu.au Tue May 16 11:04:46 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg16L-00071o-WB
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 11:04:46 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fg16I-0002qk-Ie
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 11:04:45 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IDJ4RVYU8WXXEJ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 17 May 2006 01:03:53 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B9E2EAB543; Wed,
 17 May 2006 01:03:43 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 621444FB08; Wed, 17 May 2006 01:03:43 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4GF26p13514	for dna-list; Wed, 17 May 2006 01:02:06 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4GF25u13510	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 17 May 2006 01:02:05 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IDGRYFN691XNDR@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 17 May 2006 01:01:51 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BAE49AB542; Wed,
 17 May 2006 01:01:50 +1000 (EST)
Received: from monash.edu.au (dollet.its.monash.edu.au [130.194.11.236])
	by curly.its.monash.edu.au (Postfix) with ESMTP id A539A4FB09; Wed,
 17 May 2006 01:01:50 +1000 (EST)
Received: from [150.169.1.225] by mail-store-2.its.monash.edu.au (mshttpd)
 ; Tue, 16 May 2006 11:01:49 -0400
Date: Tue, 16 May 2006 11:01:49 -0400
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Subject: Re: [DNA] Merger: All Documents together (2)
In-reply-to: <f44331444eb7.4eb7f4433144@monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au, narten@us.ibm.com
Message-id: <f3baa9812dab.2dabf3baa981@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
References: <f67cb78543ca.43caf67cb785@monash.edu.au>
 <f44331444eb7.4eb7f4433144@monash.edu.au>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb


Hi Brett,

I guess the idea with leaving the 'routers' document
(which is being renamed network considerations) is that
it is solely a configuration guide for deployers
of existing equipment.

As it has a separate audience, perhaps it would be
best separate?

Greg


----- Original Message -----
From: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
Date: Tuesday, May 16, 2006 0:20 am
Subject: Re: [DNA] Merger: All Documents together (2)
To: Greg Daley <Greg.Daley@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au, narten@us.ibm.com

> I like COMBO2.
> 
> The PROTO document is already dependent on both TENT and CPL and there
> are synergies with what's in HOSTS as well.  If they were simple self
> contained ideas (TENT is) then it might be good to keep them separate
> but I don't think they are and the array of documents at the minute is
> probably more confusing than helpful.
> 
> Combining them won't be trivial, and will require a really good
> introduction to make it clear how the pieces go together, but it's
> probably worth the effort.
> 
> One difficulty I see is that PROTO describes router behaviour, as well
> as host behaviour, and I don't think it makes sense to separate 
> them as
> the protocol modifications only make sense when both sides are 
> considered.
> So do we pull the ROUTERS document in as well?  That I'm not sure 
> about. Any thoughts, anyone?
> 
> Brett.
> 
> ----- Original Message -----
> From: Greg Daley <Greg.Daley@eng.monash.edu.au>
> Date: Saturday, May 13, 2006 10:47 am
> Subject: [DNA] Merger: All Documents together (2)
> To: dna@eng.monash.edu.au
> Cc: narten@us.ibm.com
> 
> > Hi,
> > 
> > This is an amalgamation of the DNA documents together
> > in a form roughly inspired by RFC2461 Neighbor Discovery.
> > 
> > This embodies an example of option 2 for document merger.
> > 
> > Please note that there are duplicate section names, and
> > each actual section may cover overlapping topics with 
> > other protocols.  Please try to ignore this fact initially,
> > and concentrate on the overall structure of the document.
> > 
> > When Referring to this proposal, it may be useful to describe
> > it at COMBO2.
> > 
> > Greg
> > 
> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > COMBO2: All combined
> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > 
> > 1.  Introduction HOSTS-03
> > 1.  Introduction CPL-02
> > 1.  Introduction PROTO-00
> > 1.  Introduction TENT-00
> > 
> > 
> >     1.1   Structure of this Document HOSTS-03
> > 
> > 2.  Terms and Abbreviations  HOSTS-03
> > 2.   Terms and Abbreviations PROTO-00
> > 
> > 
> > 
> > 3.  Background & Motivation for DNA HOSTS-03
> >  3.1   Issues HOSTS-03
> > 
> > #
> > # Conceptual Overview...???
> > #
> > #
> > 3.   Overview PROTO-00
> >  3.1  Link Identification PROTO-00
> >  3.2  Fast Router Advertisement PROTO-00
> > 
> > #
> > # Procedural Overview...???
> > #
> > #
> > 4.  Detecting Network Attachment Steps HOSTS-03
> >  4.1   Making use of Prior Information HOSTS-03
> >  4.2   Link identification HOSTS-03
> >    4.2.1   Same link HOSTS-03
> >    4.2.2   Link change HOSTS-03
> >  4.3   IP Hosts Configuration HOSTS-03
> >  4.4   Duplicate Address Detection HOSTS-03
> >  4.5   Multicast Listener State HOSTS-03
> >  4.6   Reachability detection HOSTS-03
> > 
> > 
> > #
> > # Link Identification
> > #
> > #
> > 2.   Prefix list based approach CPL-02 
> >  2.1  Approach CPL-02 
> >  2.2  Assumptions CPL-02 
> >  2.3  Overview CPL-02 
> > #
> > #  Cut down on some protocol explanations if shift
> > #  conceptual text here.
> > #
> > #
> > #
> > 
> > #
> > # Message Formats
> > #
> > #
> > 4.   Message Formats PROTO-00
> >  4.1  Router Advertisement PROTO-00
> >  4.2  Prefix Information Option LinkID Bit PROTO-00
> >  4.3  Landmark Option PROTO-00
> >  4.4  Learned Prefix Option PROTO-00
> > 
> >  1.1   Tentative Option format TENT-00
> >  1.2   Tentative Option semantics TENT-00
> > 
> > 
> > #
> > #   Host Operations
> > #
> > #
> >  5.2  DNA Host Operation PROTO-00
> >    5.2.1  Data Structures PROTO-00
> >    5.2.2  Host Configuration Variables PROTO-00
> > 4.   Protocol Specification CPL-02 
> >  4.1  Conceptual data structures CPL-02 
> > 
> > 5.  Initiation of DNA Procedures HOSTS-03
> >  4.4  Receiving link UP notifications CPL-02 
> >  5.1   Actions Upon Hint Reception HOSTS-03
> >  5.2   Hints Due to Network Layer Messages HOSTS-03
> >  5.3   Handling Hints from Other Layers HOSTS-03
> >  5.4   Timer and Loss Based Hints HOSTS-03
> >  5.5   Simultaneous Hints HOSTS-03
> >  5.6   Hint Management for Inactive Hosts HOSTS-03
> > 
> > 
> > 
> > # Sending RSs
> >    5.2.4  Sending Router Solicitations PROTO-00
> >    5.2.3  Selection of a Landmark Prefix PROTO-00
> > 2.  Sending solicitations containing Tentative Options TENT-00 
> >  2.1   Sending Neighbour Solicitations with Tentative Options 
> TENT-
> > 00 
> >  2.2   Sending Router Solicitations with Tentative Options TENT-00
> > 
> > # Receiving RAs.
> >  4.5  Receiving valid Router Advertisements CPL-02 
> >    5.2.5  Processing Router Advertisements PROTO-00
> >  3.3  Link identity detection CPL-02  
> >  3.   DNA based on the Complete Prefix List CPL-02 
> >  3.1  Complete Prefix List generation CPL-02 
> >  4.2  Merging Candidate Link objects CPL-02 
> > 
> >  4.6  Changing the link in Neighbor Discovery CPL-02 
> >    5.2.6  DNA and Address Configuration PROTO-00
> > 
> > 
> > 
> > # Timers?????
> >  3.2  Erroneous Prefix Lists CPL-02  
> >  3.4  Renumbering CPL-02  
> >  4.3  Timer handling and Garbage Collection CPL-02  
> > 
> > #
> > #  Router Operations
> > #
> > #
> >  5.1  DNA Router Operation PROTO-00
> >    5.1.1  Data Structures PROTO-00
> >    5.1.2  Router Configuration Variables PROTO-00
> >    5.1.3  Bootstrapping DNA Data Structures PROTO-00
> >    5.1.4  Processing Router Advertisements PROTO-00
> >    5.1.5  Processing Router Solicitations PROTO-00
> >    5.1.6  Complete Router Advertisements PROTO-00
> >    5.1.7  LinkID PROTO-00
> >    5.1.8  Scheduling Fast Router Advertisements PROTO-00
> >    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
> >    5.1.10   Removing a Prefix from an Interface PROTO-00
> >    5.1.11   Prefix Reassignment PROTO-00
> > 3.  Receiving Tentative Options TENT-00
> >  3.1   Handling Tentative Options TENT-00 
> >  3.2   Receiving Neighbour Solicitations containing Tentative 
> TENT-00
> >        Options TENT-00
> >  3.3   Receiving Router Solicitations containing Tentative TENT-00
> >        Options TENT-00
> > 
> > #
> > # Limitations of DNA
> > #
> > #
> > 6.  Complications to Detecting Network Attachment HOSTS-03
> >  6.1   Packet Loss HOSTS-03
> >  6.2   Router Configurations HOSTS-03
> >  6.3   Overlapping Coverage HOSTS-03
> >  6.4   Multicast Snooping HOSTS-03
> >  6.5   Link Partition HOSTS-03
> > 
> > 
> > #
> > # Backward compatability
> > #
> > 6.   Backward Compatibility PROTO-00
> >  6.1  Non-DNA Host with DNA Routers PROTO-00
> >  6.2  DNA Host with Non-DNA Routers PROTO-00
> > 5.   CPL without a 'link UP' notification CPL-02 
> >  #
> > # Constants
> > #
> > #
> > 8.  Constants HOSTS-03
> > 9.  Protocol Constants CPL-02
> > 
> > 
> > #
> > # IANA Considerations
> > #
> > #
> > 6.   IANA Considerations CPL-02  
> > 8.   IANA Considerations PROTO-00
> > 4.   IANA Considerations TENT-00 
> > 
> > 
> > 
> > #
> > # Security Considerations
> > #
> > #
> > 7.  Security Considerations CPL-02 
> > 7.  Security Considerations HOSTS-03
> > 7.  Security Considerations PROTO-00
> > 5.  Security Considerations TENT-00
> >  7.1  Attacks on the Token Bucket PROTO-00
> >  7.2  Attacks on DNA Hosts PROTO-00
> >  7.1   Authorization and Detecting Network Attachment HOSTS-03
> >  7.2   Addressing HOSTS-03
> > 
> > #
> > # Appendices
> > #
> > #
> > A.   How the Goals are Met? PROTO-00
> > 
> > 11.  Performance Analysis CPL-02
> > 
> > 8.   Examples CPL-02 
> >  8.1  Example CPL-02 
> >  8.2  Example CPL-02  
> > 
> > A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
> >  A.1   Constraints on Neighbour Solicitations TENT-00
> >  A.2   Constraints on Router Solicitations TENT-00
> > 
> > B.  Interactions with legacy nodes TENT-00
> >  B.1   Legacy Neighbour Solicitation processing TENT-00 
> >  B.2   Legacy Router Solicitation processing TENT-00 
> > 
> > C.  Sending directed advertisements without the neighbour cache 
> > TENT-00
> > 
> > 
> > 
> 



From dna-owner@webcamserver.eng.monash.edu.au Tue May 16 13:07:52 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg31U-0001v3-AK
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 13:07:52 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fg31S-0001zz-Ts
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 13:07:52 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IHUCEFXW8WXZ1E@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 17 May 2006 03:07:25 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0E8C980003; Wed,
 17 May 2006 03:07:19 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id B28D63C007; Wed, 17 May 2006 03:07:18 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4GH1gW14523	for dna-list; Wed, 17 May 2006 03:01:42 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4GH1fu14519	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 17 May 2006 03:01:41 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IHN1SIG491XNSB@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 17 May 2006 03:01:26 +1000
Received: by localhost (Postfix, from userid 510)	id C787880002; Wed,
 17 May 2006 03:01:26 +1000 (EST)
Received: from laposte.rennes.enst-bretagne.fr
 (laposte.rennes.enst-bretagne.fr [192.44.77.17])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by larry.its.monash.edu.au (Postfix)
 with ESMTP id B117F3C003; Wed, 17 May 2006 03:01:24 +1000 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03)
 with ESMTP id k4GH1Iea010775; Tue, 16 May 2006 19:01:18 +0200
Received: from l2.rennes.enst-bretagne.fr
 (l2.rennes.enst-bretagne.fr [192.44.77.4])	by laposte.rennes.enst-bretagne.fr
 (8.13.4/8.13.4/2004.09.01) with ESMTP id k4GH1De8010766; Tue,
 16 May 2006 19:01:13 +0200
Received: from [192.44.77.137] (nik [192.44.77.137])	(authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id k4GH1CLD022271
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue,
 16 May 2006 19:01:13 +0200
Date: Tue, 16 May 2006 18:59:27 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Subject: Re: [DNA] Merger: All Documents together (2)
In-reply-to: <f3baa9812dab.2dabf3baa981@monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <Greg.Daley@eng.monash.edu.au>
Cc: Brett Pentland <Brett.Pentland@eng.monash.edu.au>, dna@eng.monash.edu.au,
 narten@us.ibm.com
Message-id: <446A04EF.3040608@enst-bretagne.fr>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
References: <f67cb78543ca.43caf67cb785@monash.edu.au>
 <f44331444eb7.4eb7f4433144@monash.edu.au>
 <f3baa9812dab.2dabf3baa981@monash.edu.au>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9e5c23589e6cce06555030c0194c9e2b

Hi,

I also prefer combo02, it makes more sense to have all options for hosts 
into a single document.

About the router document, we could add a section on network 
configuration / consideration into the combo02, but I would prefer to 
keep it separate. As you said, it is really about network configuration 
only, and it would be better to have a short narrowed document.

Nicolas

Greg Daley wrote:

>Hi Brett,
>
>I guess the idea with leaving the 'routers' document
>(which is being renamed network considerations) is that
>it is solely a configuration guide for deployers
>of existing equipment.
>
>As it has a separate audience, perhaps it would be
>best separate?
>
>Greg
>
>
>----- Original Message -----
>From: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
>Date: Tuesday, May 16, 2006 0:20 am
>Subject: Re: [DNA] Merger: All Documents together (2)
>To: Greg Daley <Greg.Daley@eng.monash.edu.au>
>Cc: dna@eng.monash.edu.au, narten@us.ibm.com
>
>  
>
>>I like COMBO2.
>>
>>The PROTO document is already dependent on both TENT and CPL and there
>>are synergies with what's in HOSTS as well.  If they were simple self
>>contained ideas (TENT is) then it might be good to keep them separate
>>but I don't think they are and the array of documents at the minute is
>>probably more confusing than helpful.
>>
>>Combining them won't be trivial, and will require a really good
>>introduction to make it clear how the pieces go together, but it's
>>probably worth the effort.
>>
>>One difficulty I see is that PROTO describes router behaviour, as well
>>as host behaviour, and I don't think it makes sense to separate 
>>them as
>>the protocol modifications only make sense when both sides are 
>>considered.
>>So do we pull the ROUTERS document in as well?  That I'm not sure 
>>about. Any thoughts, anyone?
>>
>>Brett.
>>
>>----- Original Message -----
>>From: Greg Daley <Greg.Daley@eng.monash.edu.au>
>>Date: Saturday, May 13, 2006 10:47 am
>>Subject: [DNA] Merger: All Documents together (2)
>>To: dna@eng.monash.edu.au
>>Cc: narten@us.ibm.com
>>
>>    
>>
>>>Hi,
>>>
>>>This is an amalgamation of the DNA documents together
>>>in a form roughly inspired by RFC2461 Neighbor Discovery.
>>>
>>>This embodies an example of option 2 for document merger.
>>>
>>>Please note that there are duplicate section names, and
>>>each actual section may cover overlapping topics with 
>>>other protocols.  Please try to ignore this fact initially,
>>>and concentrate on the overall structure of the document.
>>>
>>>When Referring to this proposal, it may be useful to describe
>>>it at COMBO2.
>>>
>>>Greg
>>>
>>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>>COMBO2: All combined
>>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>>
>>>1.  Introduction HOSTS-03
>>>1.  Introduction CPL-02
>>>1.  Introduction PROTO-00
>>>1.  Introduction TENT-00
>>>
>>>
>>>    1.1   Structure of this Document HOSTS-03
>>>
>>>2.  Terms and Abbreviations  HOSTS-03
>>>2.   Terms and Abbreviations PROTO-00
>>>
>>>
>>>
>>>3.  Background & Motivation for DNA HOSTS-03
>>> 3.1   Issues HOSTS-03
>>>
>>>#
>>># Conceptual Overview...???
>>>#
>>>#
>>>3.   Overview PROTO-00
>>> 3.1  Link Identification PROTO-00
>>> 3.2  Fast Router Advertisement PROTO-00
>>>
>>>#
>>># Procedural Overview...???
>>>#
>>>#
>>>4.  Detecting Network Attachment Steps HOSTS-03
>>> 4.1   Making use of Prior Information HOSTS-03
>>> 4.2   Link identification HOSTS-03
>>>   4.2.1   Same link HOSTS-03
>>>   4.2.2   Link change HOSTS-03
>>> 4.3   IP Hosts Configuration HOSTS-03
>>> 4.4   Duplicate Address Detection HOSTS-03
>>> 4.5   Multicast Listener State HOSTS-03
>>> 4.6   Reachability detection HOSTS-03
>>>
>>>
>>>#
>>># Link Identification
>>>#
>>>#
>>>2.   Prefix list based approach CPL-02 
>>> 2.1  Approach CPL-02 
>>> 2.2  Assumptions CPL-02 
>>> 2.3  Overview CPL-02 
>>>#
>>>#  Cut down on some protocol explanations if shift
>>>#  conceptual text here.
>>>#
>>>#
>>>#
>>>
>>>#
>>># Message Formats
>>>#
>>>#
>>>4.   Message Formats PROTO-00
>>> 4.1  Router Advertisement PROTO-00
>>> 4.2  Prefix Information Option LinkID Bit PROTO-00
>>> 4.3  Landmark Option PROTO-00
>>> 4.4  Learned Prefix Option PROTO-00
>>>
>>> 1.1   Tentative Option format TENT-00
>>> 1.2   Tentative Option semantics TENT-00
>>>
>>>
>>>#
>>>#   Host Operations
>>>#
>>>#
>>> 5.2  DNA Host Operation PROTO-00
>>>   5.2.1  Data Structures PROTO-00
>>>   5.2.2  Host Configuration Variables PROTO-00
>>>4.   Protocol Specification CPL-02 
>>> 4.1  Conceptual data structures CPL-02 
>>>
>>>5.  Initiation of DNA Procedures HOSTS-03
>>> 4.4  Receiving link UP notifications CPL-02 
>>> 5.1   Actions Upon Hint Reception HOSTS-03
>>> 5.2   Hints Due to Network Layer Messages HOSTS-03
>>> 5.3   Handling Hints from Other Layers HOSTS-03
>>> 5.4   Timer and Loss Based Hints HOSTS-03
>>> 5.5   Simultaneous Hints HOSTS-03
>>> 5.6   Hint Management for Inactive Hosts HOSTS-03
>>>
>>>
>>>
>>># Sending RSs
>>>   5.2.4  Sending Router Solicitations PROTO-00
>>>   5.2.3  Selection of a Landmark Prefix PROTO-00
>>>2.  Sending solicitations containing Tentative Options TENT-00 
>>> 2.1   Sending Neighbour Solicitations with Tentative Options 
>>>      
>>>
>>TENT-
>>    
>>
>>>00 
>>> 2.2   Sending Router Solicitations with Tentative Options TENT-00
>>>
>>># Receiving RAs.
>>> 4.5  Receiving valid Router Advertisements CPL-02 
>>>   5.2.5  Processing Router Advertisements PROTO-00
>>> 3.3  Link identity detection CPL-02  
>>> 3.   DNA based on the Complete Prefix List CPL-02 
>>> 3.1  Complete Prefix List generation CPL-02 
>>> 4.2  Merging Candidate Link objects CPL-02 
>>>
>>> 4.6  Changing the link in Neighbor Discovery CPL-02 
>>>   5.2.6  DNA and Address Configuration PROTO-00
>>>
>>>
>>>
>>># Timers?????
>>> 3.2  Erroneous Prefix Lists CPL-02  
>>> 3.4  Renumbering CPL-02  
>>> 4.3  Timer handling and Garbage Collection CPL-02  
>>>
>>>#
>>>#  Router Operations
>>>#
>>>#
>>> 5.1  DNA Router Operation PROTO-00
>>>   5.1.1  Data Structures PROTO-00
>>>   5.1.2  Router Configuration Variables PROTO-00
>>>   5.1.3  Bootstrapping DNA Data Structures PROTO-00
>>>   5.1.4  Processing Router Advertisements PROTO-00
>>>   5.1.5  Processing Router Solicitations PROTO-00
>>>   5.1.6  Complete Router Advertisements PROTO-00
>>>   5.1.7  LinkID PROTO-00
>>>   5.1.8  Scheduling Fast Router Advertisements PROTO-00
>>>   5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
>>>   5.1.10   Removing a Prefix from an Interface PROTO-00
>>>   5.1.11   Prefix Reassignment PROTO-00
>>>3.  Receiving Tentative Options TENT-00
>>> 3.1   Handling Tentative Options TENT-00 
>>> 3.2   Receiving Neighbour Solicitations containing Tentative 
>>>      
>>>
>>TENT-00
>>    
>>
>>>       Options TENT-00
>>> 3.3   Receiving Router Solicitations containing Tentative TENT-00
>>>       Options TENT-00
>>>
>>>#
>>># Limitations of DNA
>>>#
>>>#
>>>6.  Complications to Detecting Network Attachment HOSTS-03
>>> 6.1   Packet Loss HOSTS-03
>>> 6.2   Router Configurations HOSTS-03
>>> 6.3   Overlapping Coverage HOSTS-03
>>> 6.4   Multicast Snooping HOSTS-03
>>> 6.5   Link Partition HOSTS-03
>>>
>>>
>>>#
>>># Backward compatability
>>>#
>>>6.   Backward Compatibility PROTO-00
>>> 6.1  Non-DNA Host with DNA Routers PROTO-00
>>> 6.2  DNA Host with Non-DNA Routers PROTO-00
>>>5.   CPL without a 'link UP' notification CPL-02 
>>> #
>>># Constants
>>>#
>>>#
>>>8.  Constants HOSTS-03
>>>9.  Protocol Constants CPL-02
>>>
>>>
>>>#
>>># IANA Considerations
>>>#
>>>#
>>>6.   IANA Considerations CPL-02  
>>>8.   IANA Considerations PROTO-00
>>>4.   IANA Considerations TENT-00 
>>>
>>>
>>>
>>>#
>>># Security Considerations
>>>#
>>>#
>>>7.  Security Considerations CPL-02 
>>>7.  Security Considerations HOSTS-03
>>>7.  Security Considerations PROTO-00
>>>5.  Security Considerations TENT-00
>>> 7.1  Attacks on the Token Bucket PROTO-00
>>> 7.2  Attacks on DNA Hosts PROTO-00
>>> 7.1   Authorization and Detecting Network Attachment HOSTS-03
>>> 7.2   Addressing HOSTS-03
>>>
>>>#
>>># Appendices
>>>#
>>>#
>>>A.   How the Goals are Met? PROTO-00
>>>
>>>11.  Performance Analysis CPL-02
>>>
>>>8.   Examples CPL-02 
>>> 8.1  Example CPL-02 
>>> 8.2  Example CPL-02  
>>>
>>>A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
>>> A.1   Constraints on Neighbour Solicitations TENT-00
>>> A.2   Constraints on Router Solicitations TENT-00
>>>
>>>B.  Interactions with legacy nodes TENT-00
>>> B.1   Legacy Neighbour Solicitation processing TENT-00 
>>> B.2   Legacy Router Solicitation processing TENT-00 
>>>
>>>C.  Sending directed advertisements without the neighbour cache 
>>>TENT-00
>>>
>>>
>>>
>>>      
>>>




From dna-owner@webcamserver.eng.monash.edu.au Tue May 16 19:53:44 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg9MG-0001WQ-MT
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 19:53:44 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fg9MF-0008Ks-0V
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 19:53:44 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IW1FHAJ08WXWFB@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 17 May 2006 09:53:10 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B10F7AB543; Wed,
 17 May 2006 09:53:06 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 721F94FB07; Wed, 17 May 2006 09:53:06 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4GNpx418244	for dna-list; Wed, 17 May 2006 09:51:59 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4GNpxu18240	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 17 May 2006 09:51:59 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2IVYWJJVI8WXWFB@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 17 May 2006 09:51:52 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6EEFEAB543; Wed,
 17 May 2006 09:51:51 +1000 (EST)
Received: from monash.edu.au (balamb.its.monash.edu.au [130.194.11.237])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 57B5D4FB02; Wed,
 17 May 2006 09:51:51 +1000 (EST)
Received: from [147.76.180.135] by mail-store-1.its.monash.edu.au (mshttpd)
 ; Wed, 17 May 2006 09:51:50 +1000
Date: Wed, 17 May 2006 09:51:50 +1000
From: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
Subject: Re: [DNA] Merger: All Documents together (2)
In-reply-to: <f3baa9812dab.2dabf3baa981@monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <Greg.Daley@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au, narten@us.ibm.com
Message-id: <f541964a496d.496df541964a@monash.edu.au>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.09 (built Nov 18 2005)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
References: <f67cb78543ca.43caf67cb785@monash.edu.au>
 <f44331444eb7.4eb7f4433144@monash.edu.au>
 <f3baa9812dab.2dabf3baa981@monash.edu.au>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4515df9441674711565101d9d5c4f63f

Yes, that sounds reasonable.

Brett.

----- Original Message -----
From: Greg Daley <Greg.Daley@eng.monash.edu.au>
Date: Wednesday, May 17, 2006 1:04 am
Subject: Re: [DNA] Merger: All Documents together (2)
To: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au, narten@us.ibm.com

> 
> Hi Brett,
> 
> I guess the idea with leaving the 'routers' document
> (which is being renamed network considerations) is that
> it is solely a configuration guide for deployers
> of existing equipment.
> 
> As it has a separate audience, perhaps it would be
> best separate?
> 
> Greg
> 
> 
> ----- Original Message -----
> From: Brett Pentland <Brett.Pentland@eng.monash.edu.au>
> Date: Tuesday, May 16, 2006 0:20 am
> Subject: Re: [DNA] Merger: All Documents together (2)
> To: Greg Daley <Greg.Daley@eng.monash.edu.au>
> Cc: dna@eng.monash.edu.au, narten@us.ibm.com
> 
> > I like COMBO2.
> > 
> > The PROTO document is already dependent on both TENT and CPL and 
> there> are synergies with what's in HOSTS as well.  If they were 
> simple self
> > contained ideas (TENT is) then it might be good to keep them 
> separate> but I don't think they are and the array of documents at 
> the minute is
> > probably more confusing than helpful.
> > 
> > Combining them won't be trivial, and will require a really good
> > introduction to make it clear how the pieces go together, but it's
> > probably worth the effort.
> > 
> > One difficulty I see is that PROTO describes router behaviour, as 
> well> as host behaviour, and I don't think it makes sense to 
> separate 
> > them as
> > the protocol modifications only make sense when both sides are 
> > considered.
> > So do we pull the ROUTERS document in as well?  That I'm not sure 
> > about. Any thoughts, anyone?
> > 
> > Brett.
> > 
> > ----- Original Message -----
> > From: Greg Daley <Greg.Daley@eng.monash.edu.au>
> > Date: Saturday, May 13, 2006 10:47 am
> > Subject: [DNA] Merger: All Documents together (2)
> > To: dna@eng.monash.edu.au
> > Cc: narten@us.ibm.com
> > 
> > > Hi,
> > > 
> > > This is an amalgamation of the DNA documents together
> > > in a form roughly inspired by RFC2461 Neighbor Discovery.
> > > 
> > > This embodies an example of option 2 for document merger.
> > > 
> > > Please note that there are duplicate section names, and
> > > each actual section may cover overlapping topics with 
> > > other protocols.  Please try to ignore this fact initially,
> > > and concentrate on the overall structure of the document.
> > > 
> > > When Referring to this proposal, it may be useful to describe
> > > it at COMBO2.
> > > 
> > > Greg
> > > 
> > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > > COMBO2: All combined
> > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > > 
> > > 1.  Introduction HOSTS-03
> > > 1.  Introduction CPL-02
> > > 1.  Introduction PROTO-00
> > > 1.  Introduction TENT-00
> > > 
> > > 
> > >     1.1   Structure of this Document HOSTS-03
> > > 
> > > 2.  Terms and Abbreviations  HOSTS-03
> > > 2.   Terms and Abbreviations PROTO-00
> > > 
> > > 
> > > 
> > > 3.  Background & Motivation for DNA HOSTS-03
> > >  3.1   Issues HOSTS-03
> > > 
> > > #
> > > # Conceptual Overview...???
> > > #
> > > #
> > > 3.   Overview PROTO-00
> > >  3.1  Link Identification PROTO-00
> > >  3.2  Fast Router Advertisement PROTO-00
> > > 
> > > #
> > > # Procedural Overview...???
> > > #
> > > #
> > > 4.  Detecting Network Attachment Steps HOSTS-03
> > >  4.1   Making use of Prior Information HOSTS-03
> > >  4.2   Link identification HOSTS-03
> > >    4.2.1   Same link HOSTS-03
> > >    4.2.2   Link change HOSTS-03
> > >  4.3   IP Hosts Configuration HOSTS-03
> > >  4.4   Duplicate Address Detection HOSTS-03
> > >  4.5   Multicast Listener State HOSTS-03
> > >  4.6   Reachability detection HOSTS-03
> > > 
> > > 
> > > #
> > > # Link Identification
> > > #
> > > #
> > > 2.   Prefix list based approach CPL-02 
> > >  2.1  Approach CPL-02 
> > >  2.2  Assumptions CPL-02 
> > >  2.3  Overview CPL-02 
> > > #
> > > #  Cut down on some protocol explanations if shift
> > > #  conceptual text here.
> > > #
> > > #
> > > #
> > > 
> > > #
> > > # Message Formats
> > > #
> > > #
> > > 4.   Message Formats PROTO-00
> > >  4.1  Router Advertisement PROTO-00
> > >  4.2  Prefix Information Option LinkID Bit PROTO-00
> > >  4.3  Landmark Option PROTO-00
> > >  4.4  Learned Prefix Option PROTO-00
> > > 
> > >  1.1   Tentative Option format TENT-00
> > >  1.2   Tentative Option semantics TENT-00
> > > 
> > > 
> > > #
> > > #   Host Operations
> > > #
> > > #
> > >  5.2  DNA Host Operation PROTO-00
> > >    5.2.1  Data Structures PROTO-00
> > >    5.2.2  Host Configuration Variables PROTO-00
> > > 4.   Protocol Specification CPL-02 
> > >  4.1  Conceptual data structures CPL-02 
> > > 
> > > 5.  Initiation of DNA Procedures HOSTS-03
> > >  4.4  Receiving link UP notifications CPL-02 
> > >  5.1   Actions Upon Hint Reception HOSTS-03
> > >  5.2   Hints Due to Network Layer Messages HOSTS-03
> > >  5.3   Handling Hints from Other Layers HOSTS-03
> > >  5.4   Timer and Loss Based Hints HOSTS-03
> > >  5.5   Simultaneous Hints HOSTS-03
> > >  5.6   Hint Management for Inactive Hosts HOSTS-03
> > > 
> > > 
> > > 
> > > # Sending RSs
> > >    5.2.4  Sending Router Solicitations PROTO-00
> > >    5.2.3  Selection of a Landmark Prefix PROTO-00
> > > 2.  Sending solicitations containing Tentative Options TENT-00 
> > >  2.1   Sending Neighbour Solicitations with Tentative Options 
> > TENT-
> > > 00 
> > >  2.2   Sending Router Solicitations with Tentative Options TENT-00
> > > 
> > > # Receiving RAs.
> > >  4.5  Receiving valid Router Advertisements CPL-02 
> > >    5.2.5  Processing Router Advertisements PROTO-00
> > >  3.3  Link identity detection CPL-02  
> > >  3.   DNA based on the Complete Prefix List CPL-02 
> > >  3.1  Complete Prefix List generation CPL-02 
> > >  4.2  Merging Candidate Link objects CPL-02 
> > > 
> > >  4.6  Changing the link in Neighbor Discovery CPL-02 
> > >    5.2.6  DNA and Address Configuration PROTO-00
> > > 
> > > 
> > > 
> > > # Timers?????
> > >  3.2  Erroneous Prefix Lists CPL-02  
> > >  3.4  Renumbering CPL-02  
> > >  4.3  Timer handling and Garbage Collection CPL-02  
> > > 
> > > #
> > > #  Router Operations
> > > #
> > > #
> > >  5.1  DNA Router Operation PROTO-00
> > >    5.1.1  Data Structures PROTO-00
> > >    5.1.2  Router Configuration Variables PROTO-00
> > >    5.1.3  Bootstrapping DNA Data Structures PROTO-00
> > >    5.1.4  Processing Router Advertisements PROTO-00
> > >    5.1.5  Processing Router Solicitations PROTO-00
> > >    5.1.6  Complete Router Advertisements PROTO-00
> > >    5.1.7  LinkID PROTO-00
> > >    5.1.8  Scheduling Fast Router Advertisements PROTO-00
> > >    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
> > >    5.1.10   Removing a Prefix from an Interface PROTO-00
> > >    5.1.11   Prefix Reassignment PROTO-00
> > > 3.  Receiving Tentative Options TENT-00
> > >  3.1   Handling Tentative Options TENT-00 
> > >  3.2   Receiving Neighbour Solicitations containing Tentative 
> > TENT-00
> > >        Options TENT-00
> > >  3.3   Receiving Router Solicitations containing Tentative TENT-00
> > >        Options TENT-00
> > > 
> > > #
> > > # Limitations of DNA
> > > #
> > > #
> > > 6.  Complications to Detecting Network Attachment HOSTS-03
> > >  6.1   Packet Loss HOSTS-03
> > >  6.2   Router Configurations HOSTS-03
> > >  6.3   Overlapping Coverage HOSTS-03
> > >  6.4   Multicast Snooping HOSTS-03
> > >  6.5   Link Partition HOSTS-03
> > > 
> > > 
> > > #
> > > # Backward compatability
> > > #
> > > 6.   Backward Compatibility PROTO-00
> > >  6.1  Non-DNA Host with DNA Routers PROTO-00
> > >  6.2  DNA Host with Non-DNA Routers PROTO-00
> > > 5.   CPL without a 'link UP' notification CPL-02 
> > >  #
> > > # Constants
> > > #
> > > #
> > > 8.  Constants HOSTS-03
> > > 9.  Protocol Constants CPL-02
> > > 
> > > 
> > > #
> > > # IANA Considerations
> > > #
> > > #
> > > 6.   IANA Considerations CPL-02  
> > > 8.   IANA Considerations PROTO-00
> > > 4.   IANA Considerations TENT-00 
> > > 
> > > 
> > > 
> > > #
> > > # Security Considerations
> > > #
> > > #
> > > 7.  Security Considerations CPL-02 
> > > 7.  Security Considerations HOSTS-03
> > > 7.  Security Considerations PROTO-00
> > > 5.  Security Considerations TENT-00
> > >  7.1  Attacks on the Token Bucket PROTO-00
> > >  7.2  Attacks on DNA Hosts PROTO-00
> > >  7.1   Authorization and Detecting Network Attachment HOSTS-03
> > >  7.2   Addressing HOSTS-03
> > > 
> > > #
> > > # Appendices
> > > #
> > > #
> > > A.   How the Goals are Met? PROTO-00
> > > 
> > > 11.  Performance Analysis CPL-02
> > > 
> > > 8.   Examples CPL-02 
> > >  8.1  Example CPL-02 
> > >  8.2  Example CPL-02  
> > > 
> > > A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
> > >  A.1   Constraints on Neighbour Solicitations TENT-00
> > >  A.2   Constraints on Router Solicitations TENT-00
> > > 
> > > B.  Interactions with legacy nodes TENT-00
> > >  B.1   Legacy Neighbour Solicitation processing TENT-00 
> > >  B.2   Legacy Router Solicitation processing TENT-00 
> > > 
> > > C.  Sending directed advertisements without the neighbour cache 
> > > TENT-00
> > > 
> > > 
> > > 
> > 
> 



From dna-owner@webcamserver.eng.monash.edu.au Tue May 16 20:23:43 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg9pH-0004Qq-T5
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 20:23:43 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fg9pH-0002NY-QK
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 20:23:43 -0400
Received: from alpha1.its.monash.edu.au ([130.194.1.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fg9aO-00061D-K3
	for dna-archive@lists.ietf.org; Tue, 16 May 2006 20:08:23 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2IWJIITAQ8X7MBI@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 17 May 2006 10:07:59 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 87D8CAB544; Wed,
 17 May 2006 10:07:41 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 4B65C4FB0B; Wed,
 17 May 2006 10:07:41 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4H07M418394	for dna-list; Wed, 17 May 2006 10:07:22 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4H07Mu18388	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 17 May 2006 10:07:22 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2IWIXKW0Y8X7MBI@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 17 May 2006 10:07:14 +1000
Received: by localhost (Postfix, from userid 510)	id 41772AB542; Wed,
 17 May 2006 10:07:14 +1000 (EST)
Received: from mgw-ext14.nokia.com (mgw-ext14.nokia.com [131.228.20.173])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 5FB1C4FB07; Wed, 17 May 2006 10:07:12 +1000 (EST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7)
 with ESMTP id k4H06waF030712; Wed, 17 May 2006 03:07:03 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111])
 by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed,
 17 May 2006 03:06:22 +0300
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23])
 by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
 16 May 2006 19:06:21 -0500
Date: Tue, 16 May 2006 17:06:18 -0700
From: Mohan.Parthasarathy@nokia.com
Subject: RE: [DNA] Merger: Unmodified Messages/Modified Messages (3)
In-reply-to: <f64eb23a3625.3625f64eb23a@monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg.Daley@eng.monash.edu.au, dna@eng.monash.edu.au
Cc: narten@us.ibm.com
Message-id: <8A76136424391244A5CF0165337085370193C4D6@mvebe101.NOE.Nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] Merger: Unmodified Messages/Modified Messages (3)
Thread-Index: AcZ2J2PuGuhYrvUCTIiI+vQojo6o4wDHY1XQ
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 17 May 2006 00:06:21.0021 (UTC)
 FILETIME=[BA3270D0:01C67945]
X-Spam-Score: -0.4 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb

Greg,

I would vote for this. I don't see any overlap in 3A and 3B
and hence COMBO2 (option of putting them all together) does
not make sense to me.

-mohan
 

>-----Original Message-----
>From: owner-dna@ecselists.eng.monash.edu.au 
>[mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of 
>ext Greg Daley
>Sent: Friday, May 12, 2006 5:51 PM
>To: dna@eng.monash.edu.au
>Cc: narten@us.ibm.com
>Subject: [DNA] Merger: Unmodified Messages/Modified Messages (3)
>
>Hi,
>
>Here's another proposal for merging the documents.
>Essentially, this takes CPL and HOSTS and puts them together 
>(COMBO3A), while putting the other documents which modify 
>message formats together PROTO and Tentative (COMBO3B).
>
>As an aside, there's clearly a lot of overlap between Hosts 
>and CPL, which can be reduced.
>
>Greg
>
>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>COMBO3A:  Unmodified Messages.
>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
>1.   Introduction CPL-02
>1.  Introduction  HOSTS-03
>     1.1   Structure of this Document HOSTS-03
>
>2.  Terms and Abbreviations  HOSTS-03
>
>3.  Background & Motivation for DNA HOSTS-03
>  3.1   Issues HOSTS-03
>2.   Prefix list based approach CPL-02 
>  2.1  Approach CPL-02
>  2.2  Assumptions CPL-02
>  2.3  Overview CPL-02 
>
>4.  Detecting Network Attachment Steps HOSTS-03
>  4.1   Making use of Prior Information HOSTS-03
>  4.2   Link identification HOSTS-03
>    4.2.1   Same link HOSTS-03
>    4.2.2   Link change HOSTS-03
>  4.3   IP Hosts Configuration HOSTS-03
>  4.4   Duplicate Address Detection HOSTS-03
>  4.5   Multicast Listener State HOSTS-03
>  4.6   Reachability detection HOSTS-03
>
>
>3.   DNA based on the Complete Prefix List CPL-02 
>  3.1  Complete Prefix List generation CPL-02
>  3.2  Erroneous Prefix Lists CPL-02
>  3.3  Link identity detection CPL-02
>  3.4  Renumbering CPL-02  
>
>4.   Protocol Specification CPL-02 
>  4.1  Conceptual data structures CPL-02
>  4.2  Merging Candidate Link objects CPL-02
>  4.3  Timer handling and Garbage Collection CPL-02
>  4.4  Receiving link UP notifications CPL-02
>  4.5  Receiving valid Router Advertisements CPL-02
>  4.6  Changing the link in Neighbor Discovery CPL-02 
>
>5.  Initiation of DNA Procedures HOSTS-03
>  5.1   Actions Upon Hint Reception HOSTS-03
>  5.2   Hints Due to Network Layer Messages HOSTS-03
>  5.3   Handling Hints from Other Layers HOSTS-03
>  5.4   Timer and Loss Based Hints HOSTS-03
>  5.5   Simultaneous Hints HOSTS-03
>  5.6   Hint Management for Inactive Hosts HOSTS-03
>
>6.  Complications to Detecting Network Attachment HOSTS-03
>  6.1   Packet Loss HOSTS-03
>  6.2   Router Configurations HOSTS-03
>  6.3   Overlapping Coverage HOSTS-03
>  6.4   Multicast Snooping HOSTS-03
>  6.5   Link Partition HOSTS-03
>5.   CPL without a 'link UP' notification CPL-02 
>
>6.   IANA Considerations CPL-02  
>
>7.   Security Considerations CPL-02 
>7.  Security Considerations HOSTS-03
>  7.1   Authorization and Detecting Network Attachment HOSTS-03
>  7.2   Addressing HOSTS-03
>
>8.  Constants HOSTS-03
>9.   Protocol Constants CPL-02
>
>#
># Appendixes
>#
>
>
>8.   Examples CPL-02 
>  8.1  Example CPL-02
>  8.2  Example CPL-02  
>
>11.  Performance Analysis CPL-02
>
>
>
>
>
>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>COMBO3B: Modified Messages
>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
>1.   Introduction PROTO-00
>1.  Introduction TENT-00
>
>2.   Terms and Abbreviations PROTO-00
>
>3.   Overview PROTO-00
>  3.1  Link Identification PROTO-00
>  3.2  Fast Router Advertisement PROTO-00
>
>4.   Message Formats PROTO-00
>  4.1  Router Advertisement PROTO-00
>  4.2  Prefix Information Option LinkID Bit PROTO-00
>  4.3  Landmark Option PROTO-00
>  4.4  Learned Prefix Option PROTO-00
>  1.1   Tentative Option format TENT-00
>  1.2   Tentative Option semantics TENT-00
>
>
>5.   DNA Operation PROTO-00
>  5.1  DNA Router Operation PROTO-00
>    5.1.1  Data Structures PROTO-00
>    5.1.2  Router Configuration Variables PROTO-00
>    5.1.3  Bootstrapping DNA Data Structures PROTO-00
>    5.1.4  Processing Router Advertisements PROTO-00
>    5.1.5  Processing Router Solicitations PROTO-00 3.  
>Receiving Tentative Options TENT-00
>  3.1   Handling Tentative Options TENT-00 
>  3.3   Receiving Router Solicitations containing Tentative TENT-00
>        Options TENT-00
>
>    5.1.6  Complete Router Advertisements PROTO-00
>    5.1.7  LinkID PROTO-00
>    5.1.8  Scheduling Fast Router Advertisements PROTO-00
>    5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
>    5.1.10   Removing a Prefix from an Interface PROTO-00
>    5.1.11   Prefix Reassignment PROTO-00
>  5.2  DNA Host Operation PROTO-00
>    5.2.1  Data Structures PROTO-00
>    5.2.2  Host Configuration Variables PROTO-00
>    5.2.3  Selection of a Landmark Prefix PROTO-00
>    5.2.4  Sending Router Solicitations PROTO-00 2.  Sending 
>solicitations containing Tentative Options TENT-00 
>  2.2   Sending Router Solicitations with Tentative Options TENT-00
>
>    5.2.5  Processing Router Advertisements PROTO-00
>    5.2.6  DNA and Address Configuration PROTO-00
>
>6.   Backward Compatibility PROTO-00
>  6.1  Non-DNA Host with DNA Routers PROTO-00
>  6.2  DNA Host with Non-DNA Routers PROTO-00
>
>7.   Security Considerations PROTO-00
>  7.1  Attacks on the Token Bucket PROTO-00
>  7.2  Attacks on DNA Hosts PROTO-00
>5.  Security Considerations TENT-00
>
>8.   IANA Considerations PROTO-00
>4.  IANA Considerations TENT-00 
>
>
>A.   How the Goals are Met? PROTO-00
>
>
>  2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
>  3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
>        Options TENT-00
>
>A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
>  A.1   Constraints on Neighbour Solicitations TENT-00
>  A.2   Constraints on Router Solicitations TENT-00
>
>B.  Interactions with legacy nodes TENT-00
>  B.1   Legacy Neighbour Solicitation processing TENT-00 
>  B.2   Legacy Router Solicitation processing TENT-00 
>
>C.  Sending directed advertisements without the neighbour cache TENT-00
>
>



From dna-owner@webcamserver.eng.monash.edu.au Wed May 17 11:46:07 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgODv-0001is-DH
	for dna-archive@lists.ietf.org; Wed, 17 May 2006 11:46:07 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FgODu-0008S2-1X
	for dna-archive@lists.ietf.org; Wed, 17 May 2006 11:46:07 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2JTA70ECU91XNPP@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 18 May 2006 01:45:31 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 47A6580005; Thu,
 18 May 2006 01:45:27 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id D04C13C00B; Thu, 18 May 2006 01:45:26 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4HFhcZ26450	for dna-list; Thu, 18 May 2006 01:43:38 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4HFhbu26446	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 18 May 2006 01:43:37 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2JT7OCXLK8X84IW@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 18 May 2006 01:43:26 +1000
Received: by localhost (Postfix, from userid 510)	id 0951C80003; Thu,
 18 May 2006 01:43:25 +1000 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 5B7953C00C; Thu, 18 May 2006 01:43:23 +1000 (EST)
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with ESMTP id k4HFhCCf012636; Wed, 17 May 2006 11:43:12 -0400
Received: from [150.169.1.185] ([150.169.1.185])
	by redwood.research.panasonic.com (MOS 3.7.4b-GA)	with ESMTP id AFN16984; Wed,
 17 May 2006 11:41:41 -0400 (EDT)
Date: Wed, 17 May 2006 11:42:11 -0400
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: Re: [DNA] Merger: Unmodified Messages/Modified Messages (3)
In-reply-to: <8A76136424391244A5CF0165337085370193C4D6@mvebe101.NOE.Nokia.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Mohan.Parthasarathy@nokia.com
Cc: Greg.Daley@eng.monash.edu.au, dna@eng.monash.edu.au, narten@us.ibm.com
Message-id: <446B4453.5040904@Research.Panasonic.COM>
Organization: Panasonic Technologies Company
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
References: <8A76136424391244A5CF0165337085370193C4D6@mvebe101.NOE.Nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96

Greg -

I like COMBO3 too. I agree with Mohan that COMBO2 doesn't necessarily
make that much sense. IMHO, the issue here is not only which combination
is the best but also which combination is doable in a reasonable time
frame. Ofcourse, I understand how much weight each should take is a
matter of opinion - I am concerned about the workload involved in
creating COMBO2 and the possible confusion that can result, while
providing very little or no benefit.

And as you mentioned, I think the merger of hosts and CPL can be done
with a significant reduction in the overall text.

- Sathya

Mohan.Parthasarathy@nokia.com wrote:

>Greg,
>
>I would vote for this. I don't see any overlap in 3A and 3B
>and hence COMBO2 (option of putting them all together) does
>not make sense to me.
>
>-mohan
> 
>
>  
>
>>-----Original Message-----
>>From: owner-dna@ecselists.eng.monash.edu.au 
>>[mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of 
>>ext Greg Daley
>>Sent: Friday, May 12, 2006 5:51 PM
>>To: dna@eng.monash.edu.au
>>Cc: narten@us.ibm.com
>>Subject: [DNA] Merger: Unmodified Messages/Modified Messages (3)
>>
>>Hi,
>>
>>Here's another proposal for merging the documents.
>>Essentially, this takes CPL and HOSTS and puts them together 
>>(COMBO3A), while putting the other documents which modify 
>>message formats together PROTO and Tentative (COMBO3B).
>>
>>As an aside, there's clearly a lot of overlap between Hosts 
>>and CPL, which can be reduced.
>>
>>Greg
>>
>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>COMBO3A:  Unmodified Messages.
>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>
>>1.   Introduction CPL-02
>>1.  Introduction  HOSTS-03
>>    1.1   Structure of this Document HOSTS-03
>>
>>2.  Terms and Abbreviations  HOSTS-03
>>
>>3.  Background & Motivation for DNA HOSTS-03
>> 3.1   Issues HOSTS-03
>>2.   Prefix list based approach CPL-02 
>> 2.1  Approach CPL-02
>> 2.2  Assumptions CPL-02
>> 2.3  Overview CPL-02 
>>
>>4.  Detecting Network Attachment Steps HOSTS-03
>> 4.1   Making use of Prior Information HOSTS-03
>> 4.2   Link identification HOSTS-03
>>   4.2.1   Same link HOSTS-03
>>   4.2.2   Link change HOSTS-03
>> 4.3   IP Hosts Configuration HOSTS-03
>> 4.4   Duplicate Address Detection HOSTS-03
>> 4.5   Multicast Listener State HOSTS-03
>> 4.6   Reachability detection HOSTS-03
>>
>>
>>3.   DNA based on the Complete Prefix List CPL-02 
>> 3.1  Complete Prefix List generation CPL-02
>> 3.2  Erroneous Prefix Lists CPL-02
>> 3.3  Link identity detection CPL-02
>> 3.4  Renumbering CPL-02  
>>
>>4.   Protocol Specification CPL-02 
>> 4.1  Conceptual data structures CPL-02
>> 4.2  Merging Candidate Link objects CPL-02
>> 4.3  Timer handling and Garbage Collection CPL-02
>> 4.4  Receiving link UP notifications CPL-02
>> 4.5  Receiving valid Router Advertisements CPL-02
>> 4.6  Changing the link in Neighbor Discovery CPL-02 
>>
>>5.  Initiation of DNA Procedures HOSTS-03
>> 5.1   Actions Upon Hint Reception HOSTS-03
>> 5.2   Hints Due to Network Layer Messages HOSTS-03
>> 5.3   Handling Hints from Other Layers HOSTS-03
>> 5.4   Timer and Loss Based Hints HOSTS-03
>> 5.5   Simultaneous Hints HOSTS-03
>> 5.6   Hint Management for Inactive Hosts HOSTS-03
>>
>>6.  Complications to Detecting Network Attachment HOSTS-03
>> 6.1   Packet Loss HOSTS-03
>> 6.2   Router Configurations HOSTS-03
>> 6.3   Overlapping Coverage HOSTS-03
>> 6.4   Multicast Snooping HOSTS-03
>> 6.5   Link Partition HOSTS-03
>>5.   CPL without a 'link UP' notification CPL-02 
>>
>>6.   IANA Considerations CPL-02  
>>
>>7.   Security Considerations CPL-02 
>>7.  Security Considerations HOSTS-03
>> 7.1   Authorization and Detecting Network Attachment HOSTS-03
>> 7.2   Addressing HOSTS-03
>>
>>8.  Constants HOSTS-03
>>9.   Protocol Constants CPL-02
>>
>>#
>># Appendixes
>>#
>>
>>
>>8.   Examples CPL-02 
>> 8.1  Example CPL-02
>> 8.2  Example CPL-02  
>>
>>11.  Performance Analysis CPL-02
>>
>>
>>
>>
>>
>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>COMBO3B: Modified Messages
>>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>
>>1.   Introduction PROTO-00
>>1.  Introduction TENT-00
>>
>>2.   Terms and Abbreviations PROTO-00
>>
>>3.   Overview PROTO-00
>> 3.1  Link Identification PROTO-00
>> 3.2  Fast Router Advertisement PROTO-00
>>
>>4.   Message Formats PROTO-00
>> 4.1  Router Advertisement PROTO-00
>> 4.2  Prefix Information Option LinkID Bit PROTO-00
>> 4.3  Landmark Option PROTO-00
>> 4.4  Learned Prefix Option PROTO-00
>> 1.1   Tentative Option format TENT-00
>> 1.2   Tentative Option semantics TENT-00
>>
>>
>>5.   DNA Operation PROTO-00
>> 5.1  DNA Router Operation PROTO-00
>>   5.1.1  Data Structures PROTO-00
>>   5.1.2  Router Configuration Variables PROTO-00
>>   5.1.3  Bootstrapping DNA Data Structures PROTO-00
>>   5.1.4  Processing Router Advertisements PROTO-00
>>   5.1.5  Processing Router Solicitations PROTO-00 3.  
>>Receiving Tentative Options TENT-00
>> 3.1   Handling Tentative Options TENT-00 
>> 3.3   Receiving Router Solicitations containing Tentative TENT-00
>>       Options TENT-00
>>
>>   5.1.6  Complete Router Advertisements PROTO-00
>>   5.1.7  LinkID PROTO-00
>>   5.1.8  Scheduling Fast Router Advertisements PROTO-00
>>   5.1.9  Scheduling Unsolicited Router Advertisements PROTO-00
>>   5.1.10   Removing a Prefix from an Interface PROTO-00
>>   5.1.11   Prefix Reassignment PROTO-00
>> 5.2  DNA Host Operation PROTO-00
>>   5.2.1  Data Structures PROTO-00
>>   5.2.2  Host Configuration Variables PROTO-00
>>   5.2.3  Selection of a Landmark Prefix PROTO-00
>>   5.2.4  Sending Router Solicitations PROTO-00 2.  Sending 
>>solicitations containing Tentative Options TENT-00 
>> 2.2   Sending Router Solicitations with Tentative Options TENT-00
>>
>>   5.2.5  Processing Router Advertisements PROTO-00
>>   5.2.6  DNA and Address Configuration PROTO-00
>>
>>6.   Backward Compatibility PROTO-00
>> 6.1  Non-DNA Host with DNA Routers PROTO-00
>> 6.2  DNA Host with Non-DNA Routers PROTO-00
>>
>>7.   Security Considerations PROTO-00
>> 7.1  Attacks on the Token Bucket PROTO-00
>> 7.2  Attacks on DNA Hosts PROTO-00
>>5.  Security Considerations TENT-00
>>
>>8.   IANA Considerations PROTO-00
>>4.  IANA Considerations TENT-00 
>>
>>
>>A.   How the Goals are Met? PROTO-00
>>
>>
>> 2.1   Sending Neighbour Solicitations with Tentative Options TENT-00 
>> 3.2   Receiving Neighbour Solicitations containing Tentative TENT-00
>>       Options TENT-00
>>
>>A.  Constraints imposed by IPv6 Neighbour Discovery TENT-00
>> A.1   Constraints on Neighbour Solicitations TENT-00
>> A.2   Constraints on Router Solicitations TENT-00
>>
>>B.  Interactions with legacy nodes TENT-00
>> B.1   Legacy Neighbour Solicitation processing TENT-00 
>> B.2   Legacy Router Solicitation processing TENT-00 
>>
>>C.  Sending directed advertisements without the neighbour cache TENT-00
>>
>>
>>    
>>




From dna-owner@webcamserver.eng.monash.edu.au Mon May 22 16:31:17 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiH3d-0000qA-Ba
	for dna-archive@lists.ietf.org; Mon, 22 May 2006 16:31:17 -0400
Received: from alpha1.its.monash.edu.au ([130.194.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FiH3a-0003LF-CP
	for dna-archive@lists.ietf.org; Mon, 22 May 2006 16:31:17 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2R2PHQM4A8X91WK@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 23 May 2006 06:30:53 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D732580003; Tue,
 23 May 2006 06:30:38 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 95AD43C005; Tue, 23 May 2006 06:30:38 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4MKSnT30605	for dna-list; Tue, 23 May 2006 06:28:49 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4MKSmu30601	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 23 May 2006 06:28:48 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2R2MWF1NC8YCTWO@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 23 May 2006 06:28:34 +1000
Received: by localhost (Postfix, from userid 510)	id F12EFAB542; Tue,
 23 May 2006 06:28:33 +1000 (EST)
Received: from hotmail.com (bay106-f12.bay106.hotmail.com [65.54.161.22])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 52CF34FB04	for
 <dna@eng.monash.edu.au>; Tue, 23 May 2006 06:28:32 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon,
 22 May 2006 13:28:29 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Mon,
 22 May 2006 20:28:26 +0000 (GMT)
Date: Mon, 22 May 2006 13:28:26 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: [DNA] Review of draft-ietf-dna-link-information-03.txt
X-Originating-IP: [131.107.0.72]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: dna@eng.monash.edu.au
Message-id: <BAY106-F1206590EE585819FC01B0D939A0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 22 May 2006 20:28:29.0595 (UTC)
 FILETIME=[497F9EB0:01C67DDE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783

Review of draft-ietf-dna-link-information-03.txt

Overall, I think this document has some issues:

a. The document appears to apply to both IPv4 and IPv6, but it makes a 
number of statements that do not reflect the operation of DNAv4 as defined 
in RFC 4436.  For example, DNAv4 does not utilize "link down" events or make 
use of link layer "hints".

b. A terminology section is needed, and terminology
consistency needs to be improved.  For example the terms
"event notifications" and "link layer events" are used. It
is not clear to me if these are synonymous with terms such
as "triggers" or "link indications" used in other documents.
Similarly, the term "link layer connection" is
used, which may or may not correspond to the term
"link up" used in this and other documents.

c. Normative language is used relating to events without
a tie to the DNA spec.  For example, the document requires
that "link down" events be generated prior to a "link up" without
indicating why such events would be helpful.  In fact, in DNAv4 these
events will be ignored, and generating such events would actually be
harmful to operating systems or applications that tear down connections on
receipt of "link down" events.

Abstract:

"  Certain network access technologies are capable of providing various
    link-layer status information to IP.  Link-layer event notifications
    can help IP expeditiously detect configuration changes.  This
    document provides a non-exhaustive catalogue of information available
    from well-known access technologies."

This abstract does not clearly indicate the purpose of the document.  It
would be helpful to state that the primary purpose is to address
events relating to DNAv6 (since the document does not appear to apply to
DNAv4).

Section 1

"  Detecting the subnet change can usually use
    network-layer indications such as a change in the advertised prefixes
    (i.e., appearance and disappearance of prefixes)."

Is this document solely focussed on DNAv6? If IPv4 is in scope, then since
router advertisement is not widely implemented, it should be made clear
that prefixes are just an example. For example, you can change the text
to:

"  Detecting the subnet change can usually use
    network-layer indications (such as a change in the advertised
    prefixes for IPv6)."

   "Establishment and
    tear down of a link-layer connection are two basic events types.
    Additional information can be conveyed in addition to the event type,
    such as the identifier of the network attachment point (e.g., IEEE
    802.11 BSSID and SSID), or network-layer configuration parameters
    obtained via the link-layer attachment process if available.  It is
    envisaged that such event notifications can in certain circumstances
    be used to expedite the inter-subnet movement detection and
    reconfiguration process.  For example, the notification indicating
    that the node has established a new link-layer connection MAY be used
    for immediately probing the network for a possible configuration
    change.  In the absence of such a notification from the link-layer,
    IP has to wait for indications that are not immediately available,
    such as receipt of next scheduled router advertisement,
    unreachability of the default gateway, etc."

The term "link layer connection" is used here, but is not defined.
I am not sure whether this only relates to connection-oriented
link layers, or whether this is synonymous with "link up".

What are "network layer configuration parameters obtained via the
link-layer attachment process"?  Perhaps an example would help (e.g. PPP
IPCP)

"   Two basic link-layer events are considered potentially useful to DNA
    process: link up and link down."

This contradicts RFC 4436, Section 1.3:
"DNAv4 does not utilize "Link Down" indications."

   "Each time the interface changes its point of attachment, a
    link down event with the previous attachment point MUST be followed
    by a link up event with the new one.  Finally, when the network
    interface is disabled, this MUST generate a link down event.  Each
    one of these events MUST generate a notification in the order they
    occur."

I don't understand the use of normative language here.  Given that
link down is not used by DNAv4, why is it relevant to require that
link down events be generated on handoff?  Existing operating systems
do not necessarily generate these events because they can be disruptive
to applications.

    "While
    merely knowing that a new link-layer connection is established may
    prompt DNA process to immediately seek other clues for detecting
    network configuration change, auxiliary information may constitute
    further clues (and even the final answers sometimes)."

DNAv4 does not utilize link-layer information this way.   Rather than
utilizing link-layer "hints", in DNAv4, all the active configurations
are probed via ARP.

Section 2.3

   "A station (STA) MUST establish
    a IEEE 802.11 link with an AP in order to send and receive IP
    packets."

I'm not clear why the term "link" is used here (I think this refers to
Association) or why it is normative (presumably the ability to send
data frames is determined by the 802.11 specification, not this document).

"  BSSID and SSID MUST be provided as auxiliary information
    along with the link up notification.  Unfortunately this information
    does not provide a deterministic indication of whether the IP-layer
    configuration MUST be changed upon movement."

Given the limitations of the BSSID and SSID, why the
normative language?  DNAv4 implementations will not use this
information.

   "If authentication is performed, a link up indication can be
    generated upon authentication, and a link down indication can be
    generated upon deauthentication."

What if authentication is not performed?  How are "link up"
and "link down" determined?

Section 2.4.2

"   Ethernet networks commonly consist of LANs joined together by
    transparent bridges (usually implemented as switches).  Transparent
    bridges require the active topology to be loop free.  The Spanning
    Tree Protocol (STP) achieves this by the exchange of Bridge Protocol
    Data Unit (BPDU), as defined in [IEEE-802.1D], which leads to, where
    required, the blocking of ports (i.e., not forwarding)."

I think you need to mention RSTP here as well.

"   Most hosts today do not listen to BPDU frames.  For these hosts,
    connectivity to the a port which is potentially bridged (any Ethernet
    port) carries the potential of frame loss if transmissions occur
    before any bridges' ForwardDelay timers have expired twice."

"to the a port" - "to the port"

"   If no bridge configuration messages are received within the
    Bridge_Max_Age interval (default 20s), then it is likely that there
    is no visible bridge whose port is enabled for bridging (S8.4.5 of
    [IEEE-802.1D]), since at least two BPDU hello messages would have
    been lost.  Upon this timeout, a link up notification MUST be
    generated.

    It is not easy for a non-STP host to distinguish between Disabled
    bridge ports and non-bridge ports with no IP nodes on them, as
    Disabled ports will have no traffic on them, and incur 100% sender
    loss.

    Upon this Bridge_Max_Age timeout, a link up notification must be
    generated.  If an earlier link up was generated with the R-flag set,
    this new one MUST set the A-flag showing that packets sent within the
    prior interval were likely to have traversed the forwarding path
    (unless the port is disabled)."

The next section talks about when to enable the delay, but I think you
could be more clear about this here as well.  For example, are you
recommending that hosts listen for STP/RSTP messages, or use 802.1AB
in order to decide on the appropriate delay?  Delaying for 20 seconds
by default probably isn't a good idea now that RSTP is becoming more
common.

"  Due to the protocol's newness and lack of deployment, it is unclear
    how this protocol will eventually affect DNA in IPv4 or IPv6
    networks."

DNAv4 does not utilize 802.1AB "hints", so this could be clarified.

Section 2.4.4

"   Link-Layer indications in Ethernet-like networks are complicated by
    additional unadvertised delays due to Spanning Tree calculations.
    This may cause re-indication (link up with A-flag) or retraction
    (link up with B-flag) of indications previously sent to upper layer
    protocols."

What are the A and B flags?  Is this an artifact of a previous revision?





From dna-owner@webcamserver.eng.monash.edu.au Tue May 23 09:48:35 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiXFT-0008QM-VJ
	for dna-archive@lists.ietf.org; Tue, 23 May 2006 09:48:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FiXFT-0000AM-TL
	for dna-archive@lists.ietf.org; Tue, 23 May 2006 09:48:35 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FiXFM-0007GB-Rv
	for dna-archive@lists.ietf.org; Tue, 23 May 2006 09:48:33 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2S2XU01PM91YD6D@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 23 May 2006 23:48:13 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 76293AB543; Tue,
 23 May 2006 23:48:11 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 2F5F34FB05; Tue,
 23 May 2006 23:48:11 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4NDl0n07219	for dna-list; Tue, 23 May 2006 23:47:00 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4NDkxu07215	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 23 May 2006 23:46:59 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2S2W7HZDG91YD6D@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 23 May 2006 23:46:51 +1000
Received: by localhost (Postfix, from userid 510)	id 5AF10AB544; Tue,
 23 May 2006 23:46:51 +1000 (EST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130])
	by curly.its.monash.edu.au (Postfix) with ESMTP id CC0044FB06	for
 <dna@eng.monash.edu.au>; Tue, 23 May 2006 23:46:49 +1000 (EST)
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 7DCBD89852; Tue,
 23 May 2006 16:46:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4158E89832; Tue,
 23 May 2006 16:46:44 +0300 (EEST)
Date: Tue, 23 May 2006 16:47:38 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt
In-reply-to: <BAY106-F1206590EE585819FC01B0D939A0@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: dna@eng.monash.edu.au
Message-id: <4473127A.9060205@kolumbus.fi>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Virus-Scanned: ClamAV using ClamSMTP
References: <BAY106-F1206590EE585819FC01B0D939A0@phx.gbl>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8

FWIW, I agree with most of Bernard's comments. Some further
discussion below:

> a. The document appears to apply to both IPv4 and IPv6, but it makes a
> number of statements that do not reflect the operation of DNAv4 as
> defined in RFC 4436.  For example, DNAv4 does not utilize "link down"
> events or make use of link layer "hints".

> This abstract does not clearly indicate the purpose of the document.  It
> would be helpful to state that the primary purpose is to address
> events relating to DNAv6 (since the document does not appear to apply to
> DNAv4). 

If we take a strict interpretation of the charter, the DNA WG is
only chartered to look at IPv6. Having said that, a version
agnostic document would in my opinion be useful, assuming
we could make it acceptable. I'm not sure why there would
be a need for the v4 and v6 case to differ much, since *this*
document should not describe the actual DNA process -- just
input for the process, such as the "link up" event.

Also, I can not see where the "link down" event is used
even in DNAv6 -- draft-ietf-dna-protocol uses "link up"
only, just as DNAv4. But is it used somewhere else? If
not, perhaps the right thing to do is to focus only on the
"link up" in this document.

>
> "  BSSID and SSID MUST be provided as auxiliary information
>    along with the link up notification.  Unfortunately this information
>    does not provide a deterministic indication of whether the IP-layer
>    configuration MUST be changed upon movement."
>
> Given the limitations of the BSSID and SSID, why the
> normative language?  DNAv4 implementations will not use this
> information.

I agree that the BSSID and SSID may be of limited value. If they
are needed, at least MUST seems inappropriate.

> "   Link-Layer indications in Ethernet-like networks are complicated by
>    additional unadvertised delays due to Spanning Tree calculations.
>    This may cause re-indication (link up with A-flag) or retraction
>    (link up with B-flag) of indications previously sent to upper layer
>    protocols."
>
> What are the A and B flags?  Is this an artifact of a previous revision?

Defined earlier in Section 2.

Anyway, I have a question for you Bernard: draft-iab-link-indications
talks about the importance of damping and hysterisis -- has that
been sufficiently addressed in the wireless parts of the
dna-link-information document?

--Jari




From dna-owner@webcamserver.eng.monash.edu.au Tue May 23 13:55:02 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fib5y-0006Tz-Rg
	for dna-archive@lists.ietf.org; Tue, 23 May 2006 13:55:02 -0400
Received: from alpha6.its.monash.edu.au ([130.194.1.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fib5x-0002hJ-9c
	for dna-archive@lists.ietf.org; Tue, 23 May 2006 13:55:02 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2SBIZ7OS28YEHA2@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 24 May 2006 03:54:37 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C00F5AB543; Wed,
 24 May 2006 03:54:20 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 7735E4FB02; Wed,
 24 May 2006 03:54:20 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4NHrJB09385	for dna-list; Wed, 24 May 2006 03:53:19 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4NHrIu09381	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 24 May 2006 03:53:18 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2SBHKSNHG8WY3CQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 24 May 2006 03:53:09 +1000
Received: by localhost (Postfix, from userid 510)	id F0FB7AB542; Wed,
 24 May 2006 03:53:08 +1000 (EST)
Received: from hotmail.com (bay106-f3.bay106.hotmail.com [65.54.161.13])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 4D1944FB0C	for
 <dna@eng.monash.edu.au>; Wed, 24 May 2006 03:53:08 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue,
 23 May 2006 10:53:04 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Tue,
 23 May 2006 17:52:59 +0000 (GMT)
Date: Tue, 23 May 2006 10:52:59 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt
In-reply-to: <4473127A.9060205@kolumbus.fi>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: jari.arkko@kolumbus.fi
Cc: dna@eng.monash.edu.au
Message-id: <BAY106-F3F7969C459F58263E3740939B0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 23 May 2006 17:53:04.0460 (UTC)
 FILETIME=[BDB2B0C0:01C67E91]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

>Anyway, I have a question for you Bernard: draft-iab-link-indications
>talks about the importance of damping and hysterisis -- has that
>been sufficiently addressed in the wireless parts of the
>dna-link-information document?

Damping & hystersis need to be addressed in the DNA specifications 
themselves, so that DNA can be immune to driver malfunctions.  As an 
example, RFC 4436 rate limits DNAv4 exchanges, so that a jittering driver 
would not cause a flood of DNAv4 probes.

I do think this document creates a problem by mandating that a "link down" 
event be sent on each handoff.  It is possible for a handoff to occur with 
minimal connectivity loss, so that the link was never "down", at least not 
long enough for an application to care about it.  Requiring "link down" 
events will cause harm in situations where the TCP stack or applications 
tear down connections on receipt of a "link down".   Because of the downside 
to sending a "link down" event, these events are often damped, and if a 
"link up" occurs prior to expiration of the damping timer, then a "link 
down" event may not be sent.





From dna-owner@webcamserver.eng.monash.edu.au Wed May 24 01:32:46 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FilzC-00078U-0Y
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 01:32:46 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Filz7-0001wC-NL
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 01:32:45 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2SZVB1C5I8WY8IU@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 24 May 2006 15:31:36 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 959E5AB547; Wed,
 24 May 2006 15:31:22 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 2F2274FB0C; Wed,
 24 May 2006 15:31:22 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4O5SRj15776	for dna-list; Wed, 24 May 2006 15:28:27 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4O5SQu15772	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 24 May 2006 15:28:26 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2SZRHCKW28X97TN@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 24 May 2006 15:28:20 +1000
Received: by localhost (Postfix, from userid 510)	id A29BF80003; Wed,
 24 May 2006 15:28:19 +1000 (EST)
Received: from fridge.docomolabs-usa.com
 (key1.docomolabs-usa.com [216.98.102.225])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 98CD63C007	for <dna@eng.monash.edu.au>; Wed,
 24 May 2006 15:28:18 +1000 (EST)
Date: Tue, 23 May 2006 22:29:10 -0700
From: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>, jari.arkko@kolumbus.fi
Cc: dna@eng.monash.edu.au
Message-id: <007d01c67ef2$ff54f0e0$496015ac@dcml.docomolabsusa.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level: *
References: <BAY106-F3F7969C459F58263E3740939B0@phx.gbl>
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

I believe the DNAv6 protocol spec says that RS probes occur upon a hint from 
L2 that the link has changed. The nature of the hint is left as an exercise 
to the implementor, and may, in fact, be quite different depending on the 
nature of the L2 protocol. Is that acceptable?

Regarding jitter, I don't recall whether that is dealt with on the host side 
in DNAv6, but there is an extensive discussion of a token bucket algorithm 
on the router to protect the routers and other hosts on the link against 
flooding. IHO, regardless of what the spec says about the host side, 
someobody could always hack the driver to flood the link. The DT was 
primarily concerned with protecting against such attacks, but I suppose it 
might be appropriate to include some text in the spec to protect against 
malfunctions as well.

            jak

----- Original Message ----- 
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <jari.arkko@kolumbus.fi>
Cc: <dna@eng.monash.edu.au>
Sent: Tuesday, May 23, 2006 10:52 AM
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt


> >Anyway, I have a question for you Bernard: draft-iab-link-indications
>>talks about the importance of damping and hysterisis -- has that
>>been sufficiently addressed in the wireless parts of the
>>dna-link-information document?
>
> Damping & hystersis need to be addressed in the DNA specifications 
> themselves, so that DNA can be immune to driver malfunctions.  As an 
> example, RFC 4436 rate limits DNAv4 exchanges, so that a jittering driver 
> would not cause a flood of DNAv4 probes.
>
> I do think this document creates a problem by mandating that a "link down" 
> event be sent on each handoff.  It is possible for a handoff to occur with 
> minimal connectivity loss, so that the link was never "down", at least not 
> long enough for an application to care about it.  Requiring "link down" 
> events will cause harm in situations where the TCP stack or applications 
> tear down connections on receipt of a "link down".   Because of the 
> downside to sending a "link down" event, these events are often damped, 
> and if a "link up" occurs prior to expiration of the damping timer, then a 
> "link down" event may not be sent.
>
>
> 





From dna-owner@webcamserver.eng.monash.edu.au Wed May 24 09:29:10 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FitQE-0008JR-Gv
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 09:29:10 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FitQA-0006uO-O8
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 09:29:10 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2TGK7UU6I8WY5OA@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 24 May 2006 23:28:55 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8CF2CAB545; Wed,
 24 May 2006 23:28:50 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 208074FB0E; Wed, 24 May 2006 23:28:50 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4ODRo319841	for dna-list; Wed, 24 May 2006 23:27:50 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4ODRmu19837	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 24 May 2006 23:27:48 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2TGIMM1YC91YLCD@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 24 May 2006 23:27:33 +1000
Received: by localhost (Postfix, from userid 510)	id BA860AB542; Wed,
 24 May 2006 23:27:33 +1000 (EST)
Received: from hotmail.com (bay106-f26.bay106.hotmail.com [65.54.161.36])
	by moe.its.monash.edu.au (Postfix) with ESMTP id C739B4FB0A	for
 <dna@eng.monash.edu.au>; Wed, 24 May 2006 23:27:32 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed,
 24 May 2006 06:27:30 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Wed,
 24 May 2006 13:27:27 +0000 (GMT)
Date: Wed, 24 May 2006 06:27:27 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt
In-reply-to: <007d01c67ef2$ff54f0e0$496015ac@dcml.docomolabsusa.com>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: kempf@docomolabs-usa.com, jari.arkko@kolumbus.fi
Cc: dna@eng.monash.edu.au
Message-id: <BAY106-F26D50238E7BE23E7F4C8D693980@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 24 May 2006 13:27:30.0506 (UTC)
 FILETIME=[CEBC02A0:01C67F35]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

>I believe the DNAv6 protocol spec says that RS probes occur upon a hint 
>from L2 that the link has changed. The nature of the hint is left as an 
>exercise to the implementor, and may, in fact, be quite different depending 
>on the nature of the L2 protocol. Is that acceptable?

Since it doesn't make sense to send out RS probes on a "Link Down" 
indication, or as the result of events such as rate negotiation, I assume 
that "changed" means "Link Up", no?

>IHO, regardless of what the spec says about the host side, somebody could 
>always hack the driver to flood the link. The DT was primarily concerned 
>with protecting against such attacks, but I suppose it might be appropriate 
>to include some text in the spec to protect against malfunctions as well.

The issue isn't so much DoS (since as you point out, attacks don't have to 
implement the spec), as protecting against malfunctioning drivers.  For 
example, I have seen drivers that don't damp "Link Up" and so it is possible 
to receive ~10 indications per second in some circumstances.   If a number 
of hosts all had the same problem (e.g. if such a malfunctioning driver made 
its way into a mass-market handset), DNA implementations without built-in 
damping could cause serious problems.





From dna-owner@webcamserver.eng.monash.edu.au Wed May 24 09:46:46 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FithG-00072q-PU
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 09:46:46 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FithF-0007oO-AD
	for dna-archive@lists.ietf.org; Wed, 24 May 2006 09:46:46 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2TH65LI9U8WY6GA@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 24 May 2006 23:46:39 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 266A1AB543; Wed,
 24 May 2006 23:46:35 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id DD9E94FB05; Wed,
 24 May 2006 23:46:34 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4ODkK620064	for dna-list; Wed, 24 May 2006 23:46:20 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4ODkKu20060	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 24 May 2006 23:46:20 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2TH5VP0CC8X8W5Z@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 24 May 2006 23:46:18 +1000
Received: by localhost (Postfix, from userid 510)	id 9890B80002; Wed,
 24 May 2006 23:46:18 +1000 (EST)
Received: from fridge.docomolabs-usa.com
 (key1.docomolabs-usa.com [216.98.102.225])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id B15ED3C006	for <dna@eng.monash.edu.au>; Wed,
 24 May 2006 23:46:17 +1000 (EST)
Date: Wed, 24 May 2006 06:47:14 -0700
From: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [DNA] Review of draft-ietf-dna-link-information-03.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>, jari.arkko@kolumbus.fi
Cc: dna@eng.monash.edu.au
Message-id: <016c01c67f38$91e248a0$496015ac@dcml.docomolabsusa.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level: *
References: <BAY106-F26D50238E7BE23E7F4C8D693980@phx.gbl>
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

> Since it doesn't make sense to send out RS probes on a "Link Down" 
> indication, or as the result of events such as rate negotiation, I assume 
> that "changed" means "Link Up", no?
>
>>IHO, regardless of what the spec says about the host side, somebody could 
>>always hack the driver to flood the link. The DT was primarily concerned 
>>with protecting against such attacks, but I suppose it might be 
>>appropriate to include some text in the spec to protect against 
>>malfunctions as well.
>

Yes.

> The issue isn't so much DoS (since as you point out, attacks don't have to 
> implement the spec), as protecting against malfunctioning drivers.  For 
> example, I have seen drivers that don't damp "Link Up" and so it is 
> possible to receive ~10 indications per second in some circumstances.   If 
> a number of hosts all had the same problem (e.g. if such a malfunctioning 
> driver made its way into a mass-market handset), DNA implementations 
> without built-in damping could cause serious problems.
>

Certainly from the host side that is true.

            jak 





From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 02:10:01 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fj92n-0005QW-7T
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 02:10:01 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fj92n-0001PQ-4R
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 02:10:01 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fj8le-00049P-6W
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 01:52:21 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2UETA2MLK91YUD5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 25 May 2006 15:49:58 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 623BEAB543; Thu,
 25 May 2006 15:49:55 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 2A53F4FB03; Thu,
 25 May 2006 15:49:55 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4P5luT29616	for dna-list; Thu, 25 May 2006 15:47:56 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4P5ltu29611	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 25 May 2006 15:47:55 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2UEQTFYG091YUD5@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 25 May 2006 15:47:41 +1000
Received: by localhost (Postfix, from userid 510)	id 7BDA5AB544; Thu,
 25 May 2006 15:47:41 +1000 (EST)
Received: from mout.perfora.net (mout.perfora.net [217.160.230.40])
	by moe.its.monash.edu.au (Postfix) with ESMTP id CDC834FB08; Thu,
 25 May 2006 15:47:37 +1000 (EST)
Received: from [24.7.38.250] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1Fj8gv2ceu-0006SC; Thu, 25 May 2006 01:47:31 -0400
Date: Wed, 24 May 2006 22:46:11 -0700
From: Alper Yegin <alper.yegin@yegin.org>
Subject: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <4471F4F7.4090608@piuha.net>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: 'Jari Arkko' <jari.arkko@piuha.net>
Cc: 'Greg Daley' <Greg.Daley@eng.monash.edu.au>, Suresh.Krishnan@ericsson.com,
 gregdaley@ieee.org, dna@eng.monash.edu.au
Message-id: <0MKoyl-1Fj8gv2ceu-0006SC@mrelay.perfora.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Index: AcZ9xSbSfpYRaXo3Tsq8lCg9c1cZyQBxg74Q
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Provags-ID: perfora.net abuse@perfora.net
 login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: -2.1 (--)
X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b


CC: DNA WG ML.

Thanks Jari for your review and comments.

Please see my inlined response below.

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: Monday, May 22, 2006 10:29 AM
> To: alper.yegin@yegin.org
> Cc: Greg Daley; Suresh.Krishnan@ericsson.com; gregdaley@ieee.org
> Subject: Re: draft-ietf-dna-link-information-03
> 
> Here are my initial AD review comments. I'm not
> completely done yet, because I want to re-read
> the IAB link indications document to see if there's
> something else that should be taken into account.
> 
> Btw, Bernard reviewed this document at some
> point. Where is that review, and did you implement
> all of his suggestions?

We had done done per his earlier review. I'll respond to his new review
comments as well.


> Substantial:
> 
> >    Two basic link-layer events are considered potentially useful to DNA
> >    process: link up and link down.  Both of these events are
> >    deterministic, and their notifications are provided to IP-layer after
> >    the events successfully conclude.
> 
> I wonder how deterministic these events are in a wireless
> network.

I think it is best if we hadn't used that term. I'd rewrite:

Two basic link-layer events are considered potentially useful to DNA
process: link up and link down.  Associated notifications can be
provided to the IP-layer after the events conclude successfully.

 
> >    A GPRS MT that wants to establish IP-level connections MUST first
> >    perform a GPRS attach to the SGSN.  This MUST be followed by a
> 
> This reads like normative language for the implementation of
> GPRS L2 operations. I would suggest that such language be
> left to the SDOs in question. (May apply to other parts of
> the document, too. Go over the MUSTs and SHOULDs and check
> that they apply only to the up/down indications, not the
> rest of the L2 operation.)

I'll take care of them all.


> 
> >    A GPRS MT that wants to establish IP-level connections MUST first
> >    perform a GPRS attach to the SGSN.  This MUST be followed by a
> >    request to the GPRS network to settle the necessary soft state
> >    mechanism (GPRS tunneling protocol) between its serving SGSN and the
> >    GGSN.  The soft state maintained between the MT, the SGSN and the
> >    GGSN is called a PDP Context.  It is used for guaranteeing a
> >    negotiated quality of service for the IP flows exchanged between the
> >    GPRS MT and an external Packet Data Network such as Internet.
> 
> Hmm... there's more to a PDP context than QoS state. I would simply
> replace the entire text above with:
> 
> "A GPRS MT that wants to establish IP connectivity establishes
> first a connection to the GPRS network and one or more PDP
> Context associations between the MT and the GGSN."

Sounds reasonable to me. Unless Eric, the author of that text, has any
comments, I'd go with your suggestion.


> 
> >    An MT has the possibility to establish a secondary PDP Context while
> >    re-using the IP configuration acquired from a previously established
> >    and active PDP Context.  Establishment of a secondary PDP Context
> >    does not provide additional information to IP-layer.  Such a second
> >    PDP Context would basically have a different QoS profile so that a
> >    different type of application can be served.  In that case,
> >    activation of the secondary PDP Context MUST NOT generate another
> >    link up event notification.  However, a secondary PDP Context
> >    establishment that triggers a new IP configuration is to be treated
> >    from the IP layer as indicated above.
> 
> Rewrite as
> 
>  "An MT has the possibility to establish a secondary PDP Context while
>    re-using the IP configuration acquired from a previously established
>    and active PDP Context.  Such a secondary PDP Context
>    does not provide additional information to IP-layer and only
>    allows another QoS profile to be used.  The activiation of a such
>    secondary PDP Context MUST NOT generate another
>    link up event notification.  However, other additional PDP Context
>    activiations are to be treated as indicated earlier."

My response is same as the previous one.

> 
> >    In a WiFi network that supports Robust Secure Network (RSN
> >    [IEEE-802.11i]), successful completion of 4-way handshake between the
> >    STA and AP commences the availability of IP service.
> 
> Presumably mere support is not the key factor here -- the question
> is whether the RSN operation has been turned on or not; my RSN-capable
> network works fine even without 4-way handshake.

I'd rewrite this as:

In a WiFi network that uses Robust Secure Network (RSN
[IEEE-802.11i]), successful completion of 4-way handshake between the
STA and AP commences the availability of IP service.


> 
> > 2.3  IEEE 802.11/WiFi
> 
> Does the document provide any guidance on what the link up/down
> events should be for preauthentication or fast handoff (802.11r)
> situations? Or is it too early to specify these?

It does not. I am not inclined to get into those areas, unless there is
popular demand :-)

> > 4.  Security Considerations
> >
> >    A faked link-layer event notification can be used to launch a
> >    denial-of service attack on the node and the associated network.
> >    Secure generation and delivery of these notifications MUST be
> >    ensured.  This is a subject for link-layer and network stack designs
> >    and therefore it is outside the scope of this document.
> 
> This paragraph appears to define a MUST requirement for
> something that is commonly not available. It would be useful
> to describe the vulnerability and discuss in turn each
> mitigating mechanism. You may also wish to take a look
> at Section 5.4,  Spoofing Network Connectivity Indications,
> in draft-ietf-mobike-protocol-08.txt.
> 
> For instance, the mitigating mechanisms include
> - link layer security (but should note that it can never fully
>   protect against DoS-type attacks, and link-down could
>   still be generated)
> - security mechanisms in the IP layer configuration,
>   including DHCP security and SEND security for ND/RD;
>   these can be used by
> 
> And yes, there's no complete protection today for this.

I think it is best if we didn't get into solving this problem in this
document. I am not sure if we can really get away with few lines of text to
suggest some solutions. A thorough solution (set) is likely to be pretty
comprehensive -- possible an I-D on its own. 

I think acknowledging the threat and declaring its solution out-of scope is
what we should be doing. 

As for the "MUST", I understand that there are currently deployed systems
that do not deploy appropriate security to handle this threat. That fact
should not take anything away from what a secure system MUST be doing. I
think that fact just makes them insecure in this sense, hence vulnerable to
spoofed link ups and downs. For that, I'm inclined to keep the MUST in
there. 



> 
> Editorial:
> 
> >    accomodate implementations that desire to indicate the link is up but
> 
> Typo.
> 
> >               specific ations - Media access control (MAC) Bridges"
> 
> Typo.
> 
> Line 355 has weird spacing: '...ss, but  the i...'
> 
> Missing Reference: [DNA4] is mentioned on line 404, but not defined
> 
> >   Certain network access technologies are capable of providing various
> >   link-layer status information to IP.
> 
> Maybe s/various// or s/various/various types of/
> 
> 
> >   layer cannot make a determination about the faith of these packets,
> 
> s/faith/fate/
> 
> >   GPRS is an enhancement to the GSM data transmission architecture and
> >   capabilities, designed to allow for packet switching in user data
> >   transmission within the GPRS network as well as for higher quality of
> >   service for the IP traffic of Mobile Terminals with external Packets
> >   Data Networks such as the Internet or corporate LANs [GPRS][GPRS-
> >   LINK].
> 
> I would replace this complicated sentence with this:
> 
> "GSM Packet Radio System (GPRS) provides packet switched data transmission
> over a cellular network."

Thanks for catching these as well.

Alper


> 
> --Jari
> 






From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 04:02:11 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjAnL-0008W3-7c
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 04:02:11 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fj9MP-0002WF-E6
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 02:30:17 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fj985-0004M9-Ka
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 02:15:32 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2UFOL3RDA91YUD4@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 25 May 2006 16:15:05 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0A71F80002; Thu,
 25 May 2006 16:15:02 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id C1F033C003; Thu, 25 May 2006 16:15:01 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4P6Em529885	for dna-list; Thu, 25 May 2006 16:14:48 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4P6Emu29881	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 25 May 2006 16:14:48 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2UFOE0BNK8WXMHY@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 25 May 2006 16:14:47 +1000
Received: by localhost (Postfix, from userid 510)	id 37A0AAB545; Thu,
 25 May 2006 16:14:47 +1000 (EST)
Received: from hotmail.com (bay106-f27.bay106.hotmail.com [65.54.161.37])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 80E864FB0E; Thu,
 25 May 2006 16:14:46 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed,
 24 May 2006 23:14:43 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Thu,
 25 May 2006 06:14:40 +0000 (GMT)
Date: Wed, 24 May 2006 23:14:40 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: RE: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <0MKoyl-1Fj8gv2ceu-0006SC@mrelay.perfora.net>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: alper.yegin@yegin.org, jari.arkko@piuha.net
Cc: Greg.Daley@eng.monash.edu.au, Suresh.Krishnan@ericsson.com,
 gregdaley@ieee.org, dna@eng.monash.edu.au
Message-id: <BAY106-F2789349714CDB734D5B24893990@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 25 May 2006 06:14:43.0925 (UTC)
 FILETIME=[83DBF050:01C67FC2]
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

>Does the document provide any guidance on what the link up/down
>events should be for preauthentication or fast handoff (802.11r)
>situations? Or is it too early to specify these?

EAP pre-authentication can only occur if the host is already connected (e.g. 
link is in the "up" state), so this is not relevant to DNA.  IEEE 802.11r is 
a somewhat complicated because initial authentication uses the 802.11i model 
(e.g. no IP connectivity prior to post-EAP handshake completion), but 
handoffs are more like the original 802.11 model ("link up" on completion of 
authenticated re-association).  Given that 11r isn't done yet, it is 
probably best not to try to cover it in this document.





From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 10:06:55 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjGUJ-0001gZ-5I
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 10:06:55 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FjGUH-0004Xr-E5
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 10:06:55 -0400
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2UW3VYSOA91YJ5V@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 26 May 2006 00:04:39 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 57FC0AB545; Fri,
 26 May 2006 00:04:36 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 1D31A4FB04; Fri, 26 May 2006 00:04:36 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4PE3SF01874	for dna-list; Fri, 26 May 2006 00:03:28 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4PE3Ru01870	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 26 May 2006 00:03:27 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31276)
 with ESMTP id <01M2UW2452KA8X8VF4@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 26 May 2006 00:03:18 +1000
Received: by localhost (Postfix, from userid 510)	id 4BBF6AB542; Fri,
 26 May 2006 00:03:18 +1000 (EST)
Received: from web60322.mail.yahoo.com
 (web60322.mail.yahoo.com [209.73.178.130])	by curly.its.monash.edu.au
 (Postfix) with SMTP id 32A704FB05	for <dna@eng.monash.edu.au>; Fri,
 26 May 2006 00:03:16 +1000 (EST)
Received: (qmail 38328 invoked by uid 60001); Thu, 25 May 2006 14:03:13 +0000
Date: Thu, 25 May 2006 07:03:13 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <0MKoyl-1Fj8gv2ceu-0006SC@mrelay.perfora.net>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@yegin.org>
Cc: dna@eng.monash.edu.au
Reply-to: Behcet Sarikaya <sarikaya@ieee.org>
Message-id: <20060525140313.38326.qmail@web60322.mail.yahoo.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_QPtLkuExmQ9Jvn2k4ejZzg)"
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
 h=Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
 b=LpZt8FZkCyait0ME697SZci7ZJZuAGTHuzcHiF8qNIjfUJJK8+sRS5KGFG3S80oq061qk2SFFTYTg0t1Imx+mrrFv4vQDUW0n8Q1VKPj4/fuhyGpn7er0IkzSVof0JZ0S//shwcZp8DSflatxu7M1Ry3V7M9WwfzCq/Gc2lQxGE=  ;
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Spam-Score: 2.3 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3


--Boundary_(ID_QPtLkuExmQ9Jvn2k4ejZzg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Alper,
  It seems like this whole document is related to IEEE 802.21 D.01 standard on Media Independent Handover (MIH). Link Up and Link Down are among the Link Events defined in 802.21 which are part of the Event Services (ES). 802.21 also treats mappings from individual link layers like 802.11, 3GPP, etc. like you have it in your draft.
  My question is if you have any new message that 802.21 does not have? 
My suggestion is at least to reference this document.

Regards,

Behcet






--Boundary_(ID_QPtLkuExmQ9Jvn2k4ejZzg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>Hi Alper,<br>&nbsp; It seems like this whole document is related to IEEE 802.21 D.01 standard on Media Independent Handover (MIH). Link Up and Link Down are among the Link Events defined in 802.21 which are part of the Event Services (ES). 802.21 also treats mappings from individual link layers like 802.11, 3GPP, etc. like you have it in your draft.<br>&nbsp; My question is if you have any new message that 802.21 does not have? <br>My suggestion is at least to reference this document.<br><br>Regards,<br><br>Behcet<br><br><div><br></div></div></div></div></body></html>

--Boundary_(ID_QPtLkuExmQ9Jvn2k4ejZzg)--



From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 15:18:17 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjLLd-0005Ur-Tm
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 15:18:17 -0400
Received: from alpha8.its.monash.edu.au ([130.194.1.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FjLLc-0005xB-5L
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 15:18:17 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2V70JK0D28WY4JM@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 26 May 2006 05:17:19 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 89B19AB545; Fri,
 26 May 2006 05:17:15 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 34AB14FB03; Fri,
 26 May 2006 05:17:15 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4PJG8Z05219	for dna-list; Fri, 26 May 2006 05:16:08 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4PJG7u05215	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 26 May 2006 05:16:07 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2V6YO4K248WY54Q@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 26 May 2006 05:15:52 +1000
Received: by localhost (Postfix, from userid 510)	id AFF2AAB542; Fri,
 26 May 2006 05:15:52 +1000 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 7C68E4FB05	for <dna@eng.monash.edu.au>; Fri,
 26 May 2006 05:15:51 +1000 (EST)
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with ESMTP id k4PJFph8015257; Thu, 25 May 2006 15:15:51 -0400
Received: from [150.169.1.225] ([150.169.1.225])
	by redwood.research.panasonic.com (MOS 3.7.4b-GA)	with ESMTP id AFS10943; Thu,
 25 May 2006 15:14:10 -0400 (EDT)
Date: Thu, 25 May 2006 15:15:45 -0400
From: Greg Daley <gregd@research.panasonic.com>
Subject: Re: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <20060525140313.38326.qmail@web60322.mail.yahoo.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: Alper Yegin <alper.yegin@yegin.org>, dna@eng.monash.edu.au
Message-id: <44760261.5060507@research.panasonic.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
References: <20060525140313.38326.qmail@web60322.mail.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Hi Behcet,

I think you've got it the other way around ;)

802.21 linke layer notifications are related
to this.

But seriously,  this is about guidance for
network layer components, for classes of events.
802.21 provides a particularly rich and
media independent set of features for this
purpose, but we'll need these hints for DNA
even on devices which do not support 802.21.

An informative reference is an option.

Greg

Behcet Sarikaya wrote:
> Hi Alper,
>   It seems like this whole document is related to IEEE 802.21 D.01 
> standard on Media Independent Handover (MIH). Link Up and Link Down are 
> among the Link Events defined in 802.21 which are part of the Event 
> Services (ES). 802.21 also treats mappings from individual link layers 
> like 802.11, 3GPP, etc. like you have it in your draft.
>   My question is if you have any new message that 802.21 does not have?
> My suggestion is at least to reference this document.
> 
> Regards,
> 
> Behcet
> 
> 




From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 19:00:31 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjOoh-0003Ef-I7
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 19:00:31 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FjOof-0002kC-1X
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 19:00:31 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2VESDFMK88WY7AW@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 26 May 2006 09:00:01 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 07FF7AB545; Fri,
 26 May 2006 08:59:58 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id B6DC84FB06; Fri,
 26 May 2006 08:59:57 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4PMx5t07344	for dna-list; Fri, 26 May 2006 08:59:05 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4PMx4u07340	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 26 May 2006 08:59:04 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2VER4Y9DK91YXL8@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 26 May 2006 08:58:47 +1000
Received: by localhost (Postfix, from userid 510)	id 8BEDBAB542; Fri,
 26 May 2006 08:58:47 +1000 (EST)
Received: from mail.globalsuite.net (mail.globalsuite.net [69.46.103.201])
	by curly.its.monash.edu.au (Postfix) with ESMTP id F05324FB06; Fri,
 26 May 2006 08:58:46 +1000 (EST)
Received: from PCLA-DAVE-W4.timefactor.com
 (host154.seagh.hyatthsiagx.com [206.165.183.154])
	by mail.globalsuite.net (Symantec Mail Security) with ESMTP id 4105E545; Thu,
 25 May 2006 16:58:41 -0600 (MDT)
Date: Thu, 25 May 2006 15:58:17 -0700
From: David Hunter <hunter@timefactor.com>
Subject: RE: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <BAY106-F2789349714CDB734D5B24893990@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>, alper.yegin@yegin.org,
 jari.arkko@piuha.net
Cc: Greg.Daley@eng.monash.edu.au, Suresh.Krishnan@ericsson.com,
 gregdaley@ieee.org, dna@eng.monash.edu.au, hunter@timefactor.com
Message-id: <7.0.1.0.0.20060525153935.01c9ea08@timefactor.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Brightmail-Tracker: AAAAAA==
References: <0MKoyl-1Fj8gv2ceu-0006SC@mrelay.perfora.net>
 <BAY106-F2789349714CDB734D5B24893990@phx.gbl>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Agree with Bernard on the antecedents, but not on the 
conclusions.  Bad news:  to work with 802.11, 802.21 is going to have 
to accommodate 802.11r (just a fact of the market).   Good 
news:  802.11r is much further along than 802.21.  *If* no major 
glitches happen, 802.11r will be complete and passed through as a 
standard by the time 802.21 hits sponsor ballot.  So it's pretty safe 
to include 802.11r accommodations in a document that is also trying 
to take 802.21 into account.

Hunter

At 11:14 PM 5/24/2006, Bernard Aboba wrote:
>>Does the document provide any guidance on what the link up/down
>>events should be for preauthentication or fast handoff (802.11r)
>>situations? Or is it too early to specify these?
>
>EAP pre-authentication can only occur if the host is already 
>connected (e.g. link is in the "up" state), so this is not relevant 
>to DNA.  IEEE 802.11r is a somewhat complicated because initial 
>authentication uses the 802.11i model (e.g. no IP connectivity prior 
>to post-EAP handshake completion), but handoffs are more like the 
>original 802.11 model ("link up" on completion of authenticated 
>re-association).  Given that 11r isn't done yet, it is probably best 
>not to try to cover it in this document.





From dna-owner@webcamserver.eng.monash.edu.au Thu May 25 22:05:09 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjRhM-000552-Uw
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 22:05:08 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FjRhJ-0001ze-Tc
	for dna-archive@lists.ietf.org; Thu, 25 May 2006 22:05:08 -0400
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2VL856PR48Y4WTK@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 26 May 2006 12:04:24 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id CF2B1AB544; Fri,
 26 May 2006 12:04:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 6C5DD4FB0F; Fri,
 26 May 2006 12:04:14 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id k4Q23HH09128	for dna-list; Fri, 26 May 2006 12:03:17 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id k4Q23Gu09124	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 26 May 2006 12:03:16 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276)
 with ESMTP id <01M2VL6KJ3FK8Y4WUR@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 26 May 2006 12:03:03 +1000
Received: by localhost (Postfix, from userid 510)	id BE31380007; Fri,
 26 May 2006 12:03:03 +1000 (EST)
Received: from hotmail.com (bay106-f19.bay106.hotmail.com [65.54.161.29])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 0A4B43C005; Fri,
 26 May 2006 12:03:02 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu,
 25 May 2006 19:03:00 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Fri,
 26 May 2006 02:02:58 +0000 (GMT)
Date: Thu, 25 May 2006 19:02:58 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: RE: [DNA] RE: draft-ietf-dna-link-information-03
In-reply-to: <7.0.1.0.0.20060525153935.01c9ea08@timefactor.com>
X-Originating-IP: [131.107.0.72]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: hunter@timefactor.com, alper.yegin@yegin.org, jari.arkko@piuha.net
Cc: Greg.Daley@eng.monash.edu.au, Suresh.Krishnan@ericsson.com,
 gregdaley@ieee.org, dna@eng.monash.edu.au
Message-id: <BAY106-F19FDEE02B0F46DE3CDD9AE939E0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10)
X-Spam-Level:
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 26 May 2006 02:03:00.0711 (UTC)
 FILETIME=[840E1F70:01C68068]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

I didn't realize this document was trying to take 802.21 into account.   I 
had assumed that it was targeting a relatively short-term completion date, 
so that it was not feasible to wait until 802.11r completed sponsor ballot 
later this year. But given that the gears of the IETF grind slowly indeed, 
perhaps there is little reason not to add new text.

>From: David Hunter <hunter@timefactor.com>
>To: Bernard Aboba <bernard_aboba@hotmail.com>,alper.yegin@yegin.org, 
>jari.arkko@piuha.net
>CC: Greg.Daley@eng.monash.edu.au,Suresh.Krishnan@ericsson.com, 
>gregdaley@ieee.org,dna@eng.monash.edu.au,hunter@timefactor.com
>Subject: RE: [DNA] RE: draft-ietf-dna-link-information-03
>Date: Thu, 25 May 2006 15:58:17 -0700
>
>Agree with Bernard on the antecedents, but not on the conclusions.  Bad 
>news:  to work with 802.11, 802.21 is going to have to accommodate 802.11r 
>(just a fact of the market).   Good news:  802.11r is much further along 
>than 802.21.  *If* no major glitches happen, 802.11r will be complete and 
>passed through as a standard by the time 802.21 hits sponsor ballot.  So 
>it's pretty safe to include 802.11r accommodations in a document that is 
>also trying to take 802.21 into account.
>
>Hunter
>
>At 11:14 PM 5/24/2006, Bernard Aboba wrote:
>>>Does the document provide any guidance on what the link up/down
>>>events should be for preauthentication or fast handoff (802.11r)
>>>situations? Or is it too early to specify these?
>>
>>EAP pre-authentication can only occur if the host is already connected 
>>(e.g. link is in the "up" state), so this is not relevant to DNA.  IEEE 
>>802.11r is a somewhat complicated because initial authentication uses the 
>>802.11i model (e.g. no IP connectivity prior to post-EAP handshake 
>>completion), but handoffs are more like the original 802.11 model ("link 
>>up" on completion of authenticated re-association).  Given that 11r isn't 
>>done yet, it is probably best not to try to cover it in this document.
>
>





