From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 01 17:11:50 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EX4M9-0005VC-UQ
	for dna-archive@megatron.ietf.org; Tue, 01 Nov 2005 17:11:50 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20320
	for <dna-archive@lists.ietf.org>; Tue, 1 Nov 2005 17:11:27 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUX1CZX91W9I52A3@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 02 Nov 2005 09:10:55 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id EC9E6AB872; Wed,
 02 Nov 2005 09:06:45 +1100 (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 D591354BDB; Wed, 02 Nov 2005 06:33:14 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA1JVgQ18001	for dna-list; Wed, 02 Nov 2005 06:31:42 +1100
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 jA1JVed17997	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 02 Nov 2005 06:31:41 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUWVURZ46I9S3SEH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 02 Nov 2005 06:31:29 +1100
Received: by localhost (Postfix, from userid 510)	id DE189AB557; Wed,
 02 Nov 2005 06:31:28 +1100 (EST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 4E09E4FB06; Wed,
 02 Nov 2005 06:31:26 +1100 (EST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 7780F89842; Tue,
 01 Nov 2005 21:31:22 +0200 (EET)
Date: Tue, 01 Nov 2005 21:29:18 +0200
From: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <43664F5D.1040309@ericsson.ca>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>
Cc: suresh.krishnan@ericsson.ca, Dna <dna@eng.monash.edu.au>
Message-id: <4367C20E.8000904@kolumbus.fi>
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 (X11/20041206)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Spam-Level: *
References: <43664F5D.1040309@ericsson.ca>
Content-Transfer-Encoding: 7BIT

I have read the draft (draft-pentland-dna-protocol3-00.txt).
It looks pretty good! I was particularly impressed how well
it describes the overall solution, including address
assignment.

I do have some comments and questions
though. Please see below:

Technical:

>   Frequently, all routers on a link will advertise the same set of
>   prefixes and so this technique will incur no space penalty.  However,
>   on links where routers advertise different sets of prefixes, packets
>   may be larger.  To combat this, two optional mechanisms are defined.
>  
>
 From what I understand, Landmark RAs can actually be
shorter than regular RAs, even if all routers have the
same prefixes. If there's, say, three prefixes, then the
optimized unicast answer can include just the landmark
but not the other options. Or am I missing something?

>   One uses a technique called a "landmark", where the host chooses one
>   of the prefixes as a landmark prefix, and then includes this in the
>   Router Solicitation message in the form of a question "am I still
>   connected to the link which has this prefix?".  The landmark is
>   carried in a new option, called the Landmark Option.
>
>   A second mechanism for reducing packet sizes applies to unsolicited
>   Router Advertisements.  By selecting one prefix on the link to be the
>   "link identifier", and making sure that it is included in every
>   advertisement, it is possible to omit some prefixes.  Such
>   advertisements will not inform a host of all of the prefixes at once,
>   but in general these unsolicited advertisements will not be the first
>   advertisement received on a link.  Inclusion of the link identifier
>   prefix simply ensures that there is overlap between the sets of
>   prefixes advertised by each router on a link and that hosts will thus
>   not incorrectly interpret one of these incomplete RAs as an
>   indication of movement.
>  
>
I have two issues with this. One is that the optionality
should be defined in a stricter way (and as far as I can
see its not done later either, at least not in 6.1.5.1). It
seems obvious to me that if we are touching code in the
routers, we should at the same time make it mandatory
to support the optimized decision mechanism. Then it
can be optional for _hosts to use_. If router support
is optional then we end up in a situation where landmark
request may fail, which consumes time.

Secondly,it is unclear from the above explanations why
we need TWO optional mechanisms instead of just one.
What specifically is the case where one provides better
performance over the other? We don't need either when
complete RAs can be used. We don't need both mechanisms
when doing a solicited RA. What's left? Situations where
the set of prefixes is too long to fit one RA and at the
same time when too many hosts arrive to send unicast
RAs? But wouldn't LinkID be sufficient for that? Or is
this about support of non-DNA hosts? But this might
be fixed by sending landmark prefixes in the usual prefix
list instead of a special option.

>   Yes (Y)
>
>      The Yes (Y) bit, when included in a Landmark Option in a Router
>      Advertisement, indicates that the prefix referred to in the Prefix
>      field of this option is being advertised by one or more routers on
>      the current link.  In a Landmark Option in a Router Solicitation,
>      this bit MUST be set to zero and ignored by receivers.
>  
>
I'm not sure I understand the need for this particular bit.
If the host has sent a Landmark option, wouldn't the router
include this specific prefix in either the regular prefix list
or in the list of other router's prefixes on this link? If so,
the host should be able to determine that it can continue
to have the same prefix as already has.

>   No (N)
>
>      The No (N) bit, when included in a Landmark Option in a Router
>      Advertisement, indicates that the prefix referred to in the Prefix
>      field of this option is not being advertised by any router on the
>      current link.  In a Landmark Option in a Router Solicitation, this
>      bit MUST be set to zero and ignored by receivers.
>  
>
Hmm... maybe I now understand the need for Yes bit.
We need it to distinguish the case between No=1 and
the RA not taking our landmark into consideration at
all.

(I'm wondering though if a No Such Prefix option would
be another way of achieving this. You send a landmark RS
and get a response that contains the router's own prefixes,
other router's prefixes, and the set of restricted prefixes
that the router thinks are not on the link. This could
trivially be the set of landmarks that were requested
but are not on the link. But it could also be a union
of those, or the set of ALL prefixes that are known to not
be on the link...)

>6.1.5.1  Space Optimized Advertisements
>
This seems to cover only the Y=1 case.
What about Y=0? (Oh, now I see that it
comes in later. Maybe add a note to 6.1.5.1
about this.)

>      The prefix MUST be one the host is using for one of its non-link-
>      local IPv6 addresses.
>  
>
Using when, and for what? When the host arrives on this
link, it may not have any non-local traffic. And where
there are multiple prefixes, its quite possible that at
time t1 the host is using one prefix but at time t2 its
using another prefix (e.g., due to RFC 3484 rules).
Or do you mean "use in an address that is currently
configured?" Maybe you could say

   The prefix MUST be one of those that the hosts has
   used to assign a non-link-local address to itself.

Does scope matter?

Maybe you could also add something about the possibility
that the Landmark Prefix needs to change. (And it does,
if the prefix lifetime runs completely out.)

>If the previous state of an address was
>   "Preferred", whether or not the host initiates optimistic Duplicate
>   Address Detection depends on the configurable DNASameLinkDADFlag
>   flag.  A host MUST forgo sending an NS to confirm uniqueness if the
>   value of the DNASameLinkDAD flag is False.  If, however, the
>   DNASameLinkDAD flag is True, the host MUST perform optimistic
>   duplicate address detection on its unicast link local and unicast
>   global addresses to determine address uniqueness.
>
Why do we need to do this? I sense a possibility here
for frequent Link Ups caused by radio coverage issues,
leading to frequent DADding.

>6.2.6.4  Packet Delivery During DNA
>
>   The specification of packet delivery before, during, and immediately
>   after DNA when a change in point of attachment occurs is out of scope
>   for this document.  The details of how packets are delivered depends
>   on the mobility management protocols (if any) available to the host's
>   stack.
>  
>
This text is somewhat confusing. Are you talking about
what IP packets you can send on the link? Right after completion
of DNA you can send and receive anything. Or are you
talking about FMIP-like schemes? Or global mobility
protocols like MIPv6?

Suggestion: don't talk about the latter two at all. Change
text to talk about case 1.

>   such threats, DNAv6 hosts SHOULD deploy RFC 3971 (SEND) secure router
>
Deploy or support? Or maybe just say "may use".

Editorial:

>   RFC 2461 is difficult because of the flexibilities offered to routers
>
flexibility, I think

>   achieve fast RA.  In this memo, an integrated solution is presented.
>
Fast RA?

>1.  Contributors
>
Move at the end.

>2.  Introduction
>
Needs to be expanded to be useful for readers who are
not familiar with the history.

>The protocol
>   handles this quite well during graceful renumbering (when the valid
>
s/quite well//

>   removed and perhaps reassigned to a different link), however, it can
>   also cope with "flash" renumbering and reassignment but not in an
>   optimized fashion.
>  
>
Already in this section it would be useful to understand
whether the issue is non-optimality or if there's some
incorrectness issues as well (such as making a false
positive decision that we are on the same link).

>4.1  What Identifies a Link?
>
>
>4.2  Link Identification
>
Hmm...

>   DNA (D)
>
>      The DNA (D) bit indicates that the router sending the RA is
>      participating in the DNAv6 protocol.  Other routers should include
>      this router in calculating response delay tokens.
>  
>
If I have understood correctly, wouldn't "Fast RA (F)" be
more appropriate name?

>6.1.9  Scheduling Unsolicited Router Advertisements
>
Funny indentation in this section.

--Jari




From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 02 02:55:03 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EXDSY-0006Yt-Mi
	for dna-archive@megatron.ietf.org; Wed, 02 Nov 2005 02:55:03 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18443
	for <dna-archive@lists.ietf.org>; Wed, 2 Nov 2005 02:54:39 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LUXLTE0HAS9ASFQ8@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 02 Nov 2005 18:54:55 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4AFFDAB559; Wed,
 02 Nov 2005 18:54:49 +1100 (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 E451B4FB07; Wed,
 02 Nov 2005 18:54:48 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA27s8w26249	for dna-list; Wed, 02 Nov 2005 18:54:08 +1100
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 jA27s7d26245	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 02 Nov 2005 18:54:07 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LUXLS75U229ASAZL@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 02 Nov 2005 18:53:52 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BD15AAB542; Wed,
 02 Nov 2005 18:53:51 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 8FC044FB0E; Wed,
 02 Nov 2005 18:53:51 +1100 (EST)
Date: Wed, 02 Nov 2005 18:53:46 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <4367C20E.8000904@kolumbus.fi>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Jari Arkko <jari.arkko@kolumbus.fi>
Cc: suresh.krishnan@ericsson.ca, Dna <dna@eng.monash.edu.au>
Message-id: <4368708A.5040302@eng.monash.edu.au>
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.7-1.1.fc4 (X11/20050929)
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
Content-Transfer-Encoding: 7BIT

Hi Jari,

Thanks for your comments and the detailed review.  I'll respond
in-line.

Brett.

Jari Arkko wrote:
> I have read the draft (draft-pentland-dna-protocol3-00.txt).
> It looks pretty good! I was particularly impressed how well
> it describes the overall solution, including address
> assignment.
> 
> I do have some comments and questions
> though. Please see below:
> 
> Technical:
> 
>>   Frequently, all routers on a link will advertise the same set of
>>   prefixes and so this technique will incur no space penalty.  However,
>>   on links where routers advertise different sets of prefixes, packets
>>   may be larger.  To combat this, two optional mechanisms are defined.
>>  
>>
>  From what I understand, Landmark RAs can actually be
> shorter than regular RAs, even if all routers have the
> same prefixes. If there's, say, three prefixes, then the
> optimized unicast answer can include just the landmark
> but not the other options. Or am I missing something?

Yes, that's true.  This is one of the techniques offered below that can
reduce the RA size.

>>   One uses a technique called a "landmark", where the host chooses one
>>   of the prefixes as a landmark prefix, and then includes this in the
>>   Router Solicitation message in the form of a question "am I still
>>   connected to the link which has this prefix?".  The landmark is
>>   carried in a new option, called the Landmark Option.
>>
>>   A second mechanism for reducing packet sizes applies to unsolicited
>>   Router Advertisements.  By selecting one prefix on the link to be the
>>   "link identifier", and making sure that it is included in every
>>   advertisement, it is possible to omit some prefixes.  Such
>>   advertisements will not inform a host of all of the prefixes at once,
>>   but in general these unsolicited advertisements will not be the first
>>   advertisement received on a link.  Inclusion of the link identifier
>>   prefix simply ensures that there is overlap between the sets of
>>   prefixes advertised by each router on a link and that hosts will thus
>>   not incorrectly interpret one of these incomplete RAs as an
>>   indication of movement.
>>  
>>
> I have two issues with this. One is that the optionality
> should be defined in a stricter way (and as far as I can
> see its not done later either, at least not in 6.1.5.1). It
> seems obvious to me that if we are touching code in the
> routers, we should at the same time make it mandatory
> to support the optimized decision mechanism. Then it
> can be optional for _hosts to use_. If router support
> is optional then we end up in a situation where landmark
> request may fail, which consumes time.

You may be right, but I'm not sure.  The intent here is that the base
means for determining link change is the complete RA.  If both
the host and router support landmarks, then the smaller RA
is possible.  I can't think of a good reason why a router would
not want to support landmarks, but I don't think whether it does
or doesn't breaks anything.

   - If the RS has a landmark and the router recognizes it
     a short RA is possible.
   - If the RS has a landmark but the router doesn't
     understand it, the landmark is ignored and a complete RA is sent
     that the host can use to make an immediate decision.
   - If the RS has no landmark, then the router sends a
     complete RA that the host can again make use of immediately.

A reason for a host choosing not to include a landmark, is that
it may not wish to expose where it has been previously.

> 
> Secondly,it is unclear from the above explanations why
> we need TWO optional mechanisms instead of just one.
> What specifically is the case where one provides better
> performance over the other? We don't need either when
> complete RAs can be used. We don't need both mechanisms
> when doing a solicited RA. What's left? Situations where
> the set of prefixes is too long to fit one RA and at the
> same time when too many hosts arrive to send unicast
> RAs? But wouldn't LinkID be sufficient for that? Or is
> this about support of non-DNA hosts? But this might
> be fixed by sending landmark prefixes in the usual prefix
> list instead of a special option.

If it is unclear then clearly the text needs some tweaking :)
They are not meant to be compared with one another because
they apply in different situations.  Landmarks are useful
for the RS/unicast RA exchange.  LinkID allows unsolicited
RAs to be shortened.

In this draft, hosts have no notion of the LinkID.  They are
looking for RAs that have no prefixes in common with those that
they have already seen as an indication that they have moved to
a new link.  The LinkID is just a way to make sure that there
will always be overlap between the sets of prefixes in RAs that
are advertised on a link.

> 
>>   Yes (Y)
>>
>>      The Yes (Y) bit, when included in a Landmark Option in a Router
>>      Advertisement, indicates that the prefix referred to in the Prefix
>>      field of this option is being advertised by one or more routers on
>>      the current link.  In a Landmark Option in a Router Solicitation,
>>      this bit MUST be set to zero and ignored by receivers.
>>  
>>
> I'm not sure I understand the need for this particular bit.
> If the host has sent a Landmark option, wouldn't the router
> include this specific prefix in either the regular prefix list
> or in the list of other router's prefixes on this link? If so,
> the host should be able to determine that it can continue
> to have the same prefix as already has.
 >
>>   No (N)
>>
>>      The No (N) bit, when included in a Landmark Option in a Router
>>      Advertisement, indicates that the prefix referred to in the Prefix
>>      field of this option is not being advertised by any router on the
>>      current link.  In a Landmark Option in a Router Solicitation, this
>>      bit MUST be set to zero and ignored by receivers.
>>  
>>
> Hmm... maybe I now understand the need for Yes bit.
> We need it to distinguish the case between No=1 and
> the RA not taking our landmark into consideration at
> all.

Yes.  That was the idea.

> (I'm wondering though if a No Such Prefix option would
> be another way of achieving this. You send a landmark RS
> and get a response that contains the router's own prefixes,
> other router's prefixes, and the set of restricted prefixes
> that the router thinks are not on the link. This could
> trivially be the set of landmarks that were requested
> but are not on the link. But it could also be a union
> of those, or the set of ALL prefixes that are known to not
> be on the link...)

Are you talking about being able to send a multicast RA that
can NACK multiple Landmarks at once?  We did discuss this
idea a bit (multiple no-flagged landmark options) but in the
end thought that it was a bit complex and that for multicast
it was simpler to send a Complete RA that gives the necessary
information regardless of the question.

> 
>> 6.1.5.1  Space Optimized Advertisements
>>
> This seems to cover only the Y=1 case.
> What about Y=0? (Oh, now I see that it
> comes in later. Maybe add a note to 6.1.5.1
> about this.)

OK.  Will do.

> 
>>      The prefix MUST be one the host is using for one of its non-link-
>>      local IPv6 addresses.
>>  
>>
> Using when, and for what? When the host arrives on this
> link, it may not have any non-local traffic. And where
> there are multiple prefixes, its quite possible that at
> time t1 the host is using one prefix but at time t2 its
> using another prefix (e.g., due to RFC 3484 rules).
> Or do you mean "use in an address that is currently
> configured?" Maybe you could say
> 
>   The prefix MUST be one of those that the hosts has
>   used to assign a non-link-local address to itself.

Yes, that sounds a lot clearer.

> 
> Does scope matter?

Well, it must be greater than link-scope.  Beyond that, I guess
that uniqueness is more important than scope.  A ULA prefix,
for example, should be fine even though it has local scope.
Perhaps some explanatory text to this effect?  How about:

    The prefix MUST be one of those that the host has
    used to assign a non-link-local address to itself.
    While any scope greater than link-scope is acceptable,
    the prefix SHOULD be one that is unlikely to be advertised
    on another link.  Globally Aggregatable Unicast Address
    prefixes and Unique Local Address prefixes are examples
    of this.

> Maybe you could also add something about the possibility
> that the Landmark Prefix needs to change. (And it does,
> if the prefix lifetime runs completely out.)

OK.  How about an addition to the first point in that section?

From:

       The prefix MUST have a non-zero valid lifetime.

To:

       The prefix MUST have a non-zero valid lifetime.  If the
       valid lifetime of a previously selected Landmark Prefix
       expires, a new Landmark Prefix MUST be selected.
> 
>> If the previous state of an address was
>>   "Preferred", whether or not the host initiates optimistic Duplicate
>>   Address Detection depends on the configurable DNASameLinkDADFlag
>>   flag.  A host MUST forgo sending an NS to confirm uniqueness if the
>>   value of the DNASameLinkDAD flag is False.  If, however, the
>>   DNASameLinkDAD flag is True, the host MUST perform optimistic
>>   duplicate address detection on its unicast link local and unicast
>>   global addresses to determine address uniqueness.
>>
> Why do we need to do this? I sense a possibility here
> for frequent Link Ups caused by radio coverage issues,
> leading to frequent DADding.

Well, when connecting to a network, a host doesn't necessarily know how
long it was disconnected for, and so probably should check that its
address is still unique on the link.  Like you say this could lead a lot
of DADing, so we thought that there should be a knob to allow this
behaviour to be turned off.  Note that the default is for it
to be turned off.

> 
>> 6.2.6.4  Packet Delivery During DNA
>>
>>   The specification of packet delivery before, during, and immediately
>>   after DNA when a change in point of attachment occurs is out of scope
>>   for this document.  The details of how packets are delivered depends
>>   on the mobility management protocols (if any) available to the host's
>>   stack.
>>  
>>
> This text is somewhat confusing. Are you talking about
> what IP packets you can send on the link? Right after completion
> of DNA you can send and receive anything. Or are you
> talking about FMIP-like schemes? Or global mobility
> protocols like MIPv6?
> 
> Suggestion: don't talk about the latter two at all. Change
> text to talk about case 1.

I think this was getting at the latter two.  With case 1 were you
referring to the time between sending an RS and receiving an RA?
I don't think we have discussed that at all, so it's a good one to
discuss.  Should packets from upper layers be blocked until
completion of DNA (and possible address reconfiguration)?
I'm not sure about that one.  On one hand we don't want to lose
packets if we have actually moved, but on the other, we probably
don't want to sit around waiting for an RA when we're really still
on the same link (maybe there's only one router and the first RA
got lost).  I'd probably lean towards blocking.  Does anyone have
any suggestions?

>>   such threats, DNAv6 hosts SHOULD deploy RFC 3971 (SEND) secure router
>>
> Deploy or support? Or maybe just say "may use".

Probably support, I think.  DNA is suggesting that hosts abandon
existing configuration when movement takes place, so that makes
it a bigger target for faked advertisements.

> 
> Editorial:
> 
>>   RFC 2461 is difficult because of the flexibilities offered to routers
>>
> flexibility, I think

OK.

>>   achieve fast RA.  In this memo, an integrated solution is presented.
>>
> Fast RA?

How about "receive an RA quickly"?

> 
>> 1.  Contributors
>>
> Move at the end.

There was a mix-up with the authorship details.  I have posted an -01
draft, but it hasn't shown up in the repo yet.

> 
>> 2.  Introduction
>>
> Needs to be expanded to be useful for readers who are
> not familiar with the history.

OK, I'll see what I can come up with.

>> The protocol
>>   handles this quite well during graceful renumbering (when the valid
>>
> s/quite well//

OK.

>>   removed and perhaps reassigned to a different link), however, it can
>>   also cope with "flash" renumbering and reassignment but not in an
>>   optimized fashion.
>>  
>>
> Already in this section it would be useful to understand
> whether the issue is non-optimality or if there's some
> incorrectness issues as well (such as making a false
> positive decision that we are on the same link).

OK, I'll have a think about that.


>> 4.1  What Identifies a Link?
>>
>>
>> 4.2  Link Identification
>>
> Hmm...

:)  How about 4.1 becoming the first paragraph of 4.2?

> 
>>   DNA (D)
>>
>>      The DNA (D) bit indicates that the router sending the RA is
>>      participating in the DNAv6 protocol.  Other routers should include
>>      this router in calculating response delay tokens.
>>  
>>
> If I have understood correctly, wouldn't "Fast RA (F)" be
> more appropriate name?

Yes.

> 
>> 6.1.9  Scheduling Unsolicited Router Advertisements
>>
> Funny indentation in this section.

You're right.  I'll fix it.
> 
> --Jari
> 

Thanks again.
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 02 03:43:07 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EXED5-00070P-AN
	for dna-archive@megatron.ietf.org; Wed, 02 Nov 2005 03:43:07 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21161
	for <dna-archive@lists.ietf.org>; Wed, 2 Nov 2005 03:42:45 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LUXNHXTQIM99ZHAN@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 02 Nov 2005 19:42:56 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 477F5AB558; Wed,
 02 Nov 2005 19:42:51 +1100 (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 D2D534FB0B; Wed,
 02 Nov 2005 19:42:50 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA28gZd26776	for dna-list; Wed, 02 Nov 2005 19:42:35 +1100
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 jA28gZd26772	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 02 Nov 2005 19:42:35 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUXNHAGC6YA23BEN@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 02 Nov 2005 19:42:20 +1100
Received: by localhost (Postfix, from userid 510)	id 37B18AB557; Wed,
 02 Nov 2005 19:42:20 +1100 (EST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 9E92A4FB0B; Wed,
 02 Nov 2005 19:42:17 +1100 (EST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 939F689863; Wed,
 02 Nov 2005 10:42:13 +0200 (EET)
Date: Wed, 02 Nov 2005 10:40:08 +0200
From: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <4368708A.5040302@eng.monash.edu.au>
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: <43687B68.8070903@kolumbus.fi>
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 (X11/20041206)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Spam-Level: *
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Brett Pentland wrote:

>>>   Frequently, all routers on a link will advertise the same set of
>>>   prefixes and so this technique will incur no space penalty.  However,
>>>   on links where routers advertise different sets of prefixes, packets
>>>   may be larger.  To combat this, two optional mechanisms are defined.
>>>  
>>>
>>  From what I understand, Landmark RAs can actually be
>> shorter than regular RAs, even if all routers have the
>> same prefixes. If there's, say, three prefixes, then the
>> optimized unicast answer can include just the landmark
>> but not the other options. Or am I missing something?
>
>
> Yes, that's true.  This is one of the techniques offered below that can
> reduce the RA size.

Right. But the text in the draft seemed to be saying that
these optimizations are only for the situation where different
prefixes are advertised by different routers. Can we get that
fixed?

>>>   One uses a technique called a "landmark", where the host chooses one
>>>   of the prefixes as a landmark prefix, and then includes this in the
>>>   Router Solicitation message in the form of a question "am I still
>>>   connected to the link which has this prefix?".  The landmark is
>>>   carried in a new option, called the Landmark Option.
>>>
>>>   A second mechanism for reducing packet sizes applies to unsolicited
>>>   Router Advertisements.  By selecting one prefix on the link to be the
>>>   "link identifier", and making sure that it is included in every
>>>   advertisement, it is possible to omit some prefixes.  Such
>>>   advertisements will not inform a host of all of the prefixes at once,
>>>   but in general these unsolicited advertisements will not be the first
>>>   advertisement received on a link.  Inclusion of the link identifier
>>>   prefix simply ensures that there is overlap between the sets of
>>>   prefixes advertised by each router on a link and that hosts will thus
>>>   not incorrectly interpret one of these incomplete RAs as an
>>>   indication of movement.
>>>  
>>>
>> I have two issues with this. One is that the optionality
>> should be defined in a stricter way (and as far as I can
>> see its not done later either, at least not in 6.1.5.1). It
>> seems obvious to me that if we are touching code in the
>> routers, we should at the same time make it mandatory
>> to support the optimized decision mechanism. Then it
>> can be optional for _hosts to use_. If router support
>> is optional then we end up in a situation where landmark
>> request may fail, which consumes time.
>
>
> You may be right, but I'm not sure.  The intent here is that the base
> means for determining link change is the complete RA.  If both
> the host and router support landmarks, then the smaller RA
> is possible.  I can't think of a good reason why a router would
> not want to support landmarks, but I don't think whether it does
> or doesn't breaks anything.
>
>   - If the RS has a landmark and the router recognizes it
>     a short RA is possible.
>   - If the RS has a landmark but the router doesn't
>     understand it, the landmark is ignored and a complete RA is sent
>     that the host can use to make an immediate decision.
>   - If the RS has no landmark, then the router sends a
>     complete RA that the host can again make use of immediately.

Its agreed that if complete RAs can be used then there's
really no issue (other than perhaps loss of a little bit of
bandwidth, but I wouldn't worry about that). However, in
your second case above, what happens if the RS has a landmark,
the router doesn't implement them, and it can't fit all the
prefixes in the complete RA? It seems that the router will
make a "random" decision of what prefixes to include, and
since it doesn't recognize the landmark option, it may not
include the host's prefix. Will this cause a problem?

> A reason for a host choosing not to include a landmark, is that
> it may not wish to expose where it has been previously.

Sure. I'm not arguing that hosts should use landmarks
all the time.

> If it is unclear then clearly the text needs some tweaking :)
> They are not meant to be compared with one another because
> they apply in different situations.  Landmarks are useful
> for the RS/unicast RA exchange.  LinkID allows unsolicited
> RAs to be shortened.
>
> In this draft, hosts have no notion of the LinkID.  They are
> looking for RAs that have no prefixes in common with those that
> they have already seen as an indication that they have moved to
> a new link.  The LinkID is just a way to make sure that there
> will always be overlap between the sets of prefixes in RAs that
> are advertised on a link.

Your explanation makes sense, but I'm still unsure if
the arrangement has to be the way it is. For instance,
it would seem that if hosts picked landmark the same
way as routers pick linkid, then we would need just
one mechanism. Or if we used just Landmark... not
sure I see a big need to reduce packet sizes in unsolicited
RAs.

These alternatives have probably been explored in depth
already, sorry if I'm repeating questions that you guys have
worked on in the design teams etc. for a long time.

>> (I'm wondering though if a No Such Prefix option would
>> be another way of achieving this. You send a landmark RS
>> and get a response that contains the router's own prefixes,
>> other router's prefixes, and the set of restricted prefixes
>> that the router thinks are not on the link. This could
>> trivially be the set of landmarks that were requested
>> but are not on the link. But it could also be a union
>> of those, or the set of ALL prefixes that are known to not
>> be on the link...)
>
>
> Are you talking about being able to send a multicast RA that
> can NACK multiple Landmarks at once?  We did discuss this
> idea a bit (multiple no-flagged landmark options) but in the
> end thought that it was a bit complex and that for multicast
> it was simpler to send a Complete RA that gives the necessary
> information regardless of the question.

OK. (Assuming you can fit in a complete RA... not sure how
important the other case is.)

>>
>> Does scope matter?
>
>
> Well, it must be greater than link-scope.  Beyond that, I guess
> that uniqueness is more important than scope.  A ULA prefix,
> for example, should be fine even though it has local scope.
> Perhaps some explanatory text to this effect?  How about:
>
>    The prefix MUST be one of those that the host has
>    used to assign a non-link-local address to itself.
>    While any scope greater than link-scope is acceptable,
>    the prefix SHOULD be one that is unlikely to be advertised
>    on another link.  Globally Aggregatable Unicast Address
>    prefixes and Unique Local Address prefixes are examples
>    of this.

Your explanation above may be enough, not sure if you
need to add anything to the draft. Is there a prefix type
that is likely to be non-unique (other than link-local)?

> OK.  How about an addition to the first point in that section?
>
> From:
>
>       The prefix MUST have a non-zero valid lifetime.
>
> To:
>
>       The prefix MUST have a non-zero valid lifetime.  If the
>       valid lifetime of a previously selected Landmark Prefix
>       expires, a new Landmark Prefix MUST be selected.

Ok.

>>> If the previous state of an address was
>>>   "Preferred", whether or not the host initiates optimistic Duplicate
>>>   Address Detection depends on the configurable DNASameLinkDADFlag
>>>   flag.  A host MUST forgo sending an NS to confirm uniqueness if the
>>>   value of the DNASameLinkDAD flag is False.  If, however, the
>>>   DNASameLinkDAD flag is True, the host MUST perform optimistic
>>>   duplicate address detection on its unicast link local and unicast
>>>   global addresses to determine address uniqueness.
>>>
>> Why do we need to do this? I sense a possibility here
>> for frequent Link Ups caused by radio coverage issues,
>> leading to frequent DADding.
>
>
> Well, when connecting to a network, a host doesn't necessarily know how
> long it was disconnected for, and so probably should check that its
> address is still unique on the link.  Like you say this could lead a lot
> of DADing, so we thought that there should be a knob to allow this
> behaviour to be turned off.  Note that the default is for it
> to be turned off.

Ok.

>>
>> Suggestion: don't talk about the latter two at all. Change
>> text to talk about case 1.
>
>
> I think this was getting at the latter two.  With case 1 were you

Ok. Some clarification in the text is probably needed.

> referring to the time between sending an RS and receiving an RA?
> I don't think we have discussed that at all, so it's a good one to
> discuss.  Should packets from upper layers be blocked until
> completion of DNA (and possible address reconfiguration)?
> I'm not sure about that one.  On one hand we don't want to lose
> packets if we have actually moved, but on the other, we probably
> don't want to sit around waiting for an RA when we're really still
> on the same link (maybe there's only one router and the first RA
> got lost).  I'd probably lean towards blocking.  Does anyone have
> any suggestions?

No, but I'd note that there's both outgoing and incoming
packet issues.

>
> Probably support, I think.  DNA is suggesting that hosts abandon
> existing configuration when movement takes place, so that makes
> it a bigger target for faked advertisements.

Ok.

>
>>>   achieve fast RA.  In this memo, an integrated solution is presented.
>>>
>> Fast RA?
>
>
> How about "receive an RA quickly"?

I was simply reacting to the term being lowercase in one place
and upper case in another case.

>>
>>> 1.  Contributors
>>>
>> Move at the end.
>
>
> There was a mix-up with the authorship details.  I have posted an -01
> draft, but it hasn't shown up in the repo yet.

Ok.

>
>>> 4.1  What Identifies a Link?
>>>
>>>
>>> 4.2  Link Identification
>>>
>> Hmm...
>
>
> :)  How about 4.1 becoming the first paragraph of 4.2?

Works for me.

--Jari




From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 03 01:30:45 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EXYcW-0004bF-9x
	for dna-archive@megatron.ietf.org; Thu, 03 Nov 2005 01:30:45 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09800
	for <dna-archive@lists.ietf.org>; Thu, 3 Nov 2005 01:30:20 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUYX5P9AXM9I5E2G@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 03 Nov 2005 17:30:22 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B90CFAB549; Thu,
 03 Nov 2005 17:30:06 +1100 (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 7A6404FB02; Thu, 03 Nov 2005 17:30:06 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA36PPs08809	for dna-list; Thu, 03 Nov 2005 17:25:25 +1100
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 jA36POd08805	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 03 Nov 2005 17:25:24 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LUYWZIIAPK9ASME1@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 03 Nov 2005 17:25:08 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8FADFAB544; Thu,
 03 Nov 2005 17:25:07 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 6AACA4FB07; Thu,
 03 Nov 2005 17:25:07 +1100 (EST)
Date: Thu, 03 Nov 2005 17:24:59 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <43687B68.8070903@kolumbus.fi>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Jari Arkko <jari.arkko@kolumbus.fi>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <4369AD3B.1010203@eng.monash.edu.au>
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.7-1.1.fc4 (X11/20050929)
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
Content-Transfer-Encoding: 7BIT

Jari Arkko wrote:
> Brett Pentland wrote:
> 
>>>>   Frequently, all routers on a link will advertise the same set of
>>>>   prefixes and so this technique will incur no space penalty.  However,
>>>>   on links where routers advertise different sets of prefixes, packets
>>>>   may be larger.  To combat this, two optional mechanisms are defined.
>>>>  
>>>>
>>>  From what I understand, Landmark RAs can actually be
>>> shorter than regular RAs, even if all routers have the
>>> same prefixes. If there's, say, three prefixes, then the
>>> optimized unicast answer can include just the landmark
>>> but not the other options. Or am I missing something?
>>
>>
>>
>> Yes, that's true.  This is one of the techniques offered below that can
>> reduce the RA size.
> 
> 
> Right. But the text in the draft seemed to be saying that
> these optimizations are only for the situation where different
> prefixes are advertised by different routers. Can we get that
> fixed?

Ah, ok, I get it now.  I'll fix it up.  How about a change from:

    Frequently, all routers on a link will advertise the same set of
    prefixes and so this technique will incur no space penalty.  However,
    on links where routers advertise different sets of prefixes, packets
    may be larger.  To combat this, two optional mechanisms are defined.

to:

    Though frequently all routers on a link will advertise the same set
    of prefixes and thus experience no cost in making the RAs complete,
    there is potential for the RAs to be large when there are many
    prefixes advertised.  Two mechanisms are defined that allow certain
    RAs to be reduced in size.

> 
>>>>   One uses a technique called a "landmark", where the host chooses one
>>>>   of the prefixes as a landmark prefix, and then includes this in the
>>>>   Router Solicitation message in the form of a question "am I still
>>>>   connected to the link which has this prefix?".  The landmark is
>>>>   carried in a new option, called the Landmark Option.
>>>>
>>>>   A second mechanism for reducing packet sizes applies to unsolicited
>>>>   Router Advertisements.  By selecting one prefix on the link to be the
>>>>   "link identifier", and making sure that it is included in every
>>>>   advertisement, it is possible to omit some prefixes.  Such
>>>>   advertisements will not inform a host of all of the prefixes at once,
>>>>   but in general these unsolicited advertisements will not be the first
>>>>   advertisement received on a link.  Inclusion of the link identifier
>>>>   prefix simply ensures that there is overlap between the sets of
>>>>   prefixes advertised by each router on a link and that hosts will thus
>>>>   not incorrectly interpret one of these incomplete RAs as an
>>>>   indication of movement.
>>>>  
>>>>
>>> I have two issues with this. One is that the optionality
>>> should be defined in a stricter way (and as far as I can
>>> see its not done later either, at least not in 6.1.5.1). It
>>> seems obvious to me that if we are touching code in the
>>> routers, we should at the same time make it mandatory
>>> to support the optimized decision mechanism. Then it
>>> can be optional for _hosts to use_. If router support
>>> is optional then we end up in a situation where landmark
>>> request may fail, which consumes time.
>>
>>
>>
>> You may be right, but I'm not sure.  The intent here is that the base
>> means for determining link change is the complete RA.  If both
>> the host and router support landmarks, then the smaller RA
>> is possible.  I can't think of a good reason why a router would
>> not want to support landmarks, but I don't think whether it does
>> or doesn't breaks anything.
>>
>>   - If the RS has a landmark and the router recognizes it
>>     a short RA is possible.
>>   - If the RS has a landmark but the router doesn't
>>     understand it, the landmark is ignored and a complete RA is sent
>>     that the host can use to make an immediate decision.
>>   - If the RS has no landmark, then the router sends a
>>     complete RA that the host can again make use of immediately.
> 
> 
> Its agreed that if complete RAs can be used then there's
> really no issue (other than perhaps loss of a little bit of
> bandwidth, but I wouldn't worry about that). However, in
> your second case above, what happens if the RS has a landmark,
> the router doesn't implement them, and it can't fit all the
> prefixes in the complete RA? It seems that the router will
> make a "random" decision of what prefixes to include, and
> since it doesn't recognize the landmark option, it may not
> include the host's prefix. Will this cause a problem?

I don't think so.  The choice of prefixes to include is not quite
random, because the router is required to include the "LinkID" prefix.
That may not be the prefix that the host picked as a landmark, but
it will have been received by the host in any earlier RAs if movement
has not taken place.  Note that I removed the word optional in the
suggested text for the previous comment because the the language in
section 6 does not make the LinkID inclusion optional.

>> If it is unclear then clearly the text needs some tweaking :)
>> They are not meant to be compared with one another because
>> they apply in different situations.  Landmarks are useful
>> for the RS/unicast RA exchange.  LinkID allows unsolicited
>> RAs to be shortened.
>>
>> In this draft, hosts have no notion of the LinkID.  They are
>> looking for RAs that have no prefixes in common with those that
>> they have already seen as an indication that they have moved to
>> a new link.  The LinkID is just a way to make sure that there
>> will always be overlap between the sets of prefixes in RAs that
>> are advertised on a link.
> 
> 
> Your explanation makes sense, but I'm still unsure if
> the arrangement has to be the way it is. For instance,
> it would seem that if hosts picked landmark the same
> way as routers pick linkid, then we would need just
> one mechanism.

Hmm.  So the host selects the landmark the same way as the routers
pick the linkid and then rather than including a landmark
option in the RA the router just prepares to send its usual RA (which
must include the linkid) but if the landmark and linkid
match, then the router can omit everything except the linkid?
That might work.  Is it what you had in mind?

> Or if we used just Landmark... not
> sure I see a big need to reduce packet sizes in unsolicited
> RAs.

There's also the assurance of prefix overlap even when it is not
possible to fit all of the prefixes in a single RA.
> 
> These alternatives have probably been explored in depth
> already, sorry if I'm repeating questions that you guys have
> worked on in the design teams etc. for a long time.

No that's fine.  This partly comes up because of the attempt to
merge ideas from two previous proposals, and so is fairly recent.

>>>
>>> Does scope matter?
>>
>>
>>
>> Well, it must be greater than link-scope.  Beyond that, I guess
>> that uniqueness is more important than scope.  A ULA prefix,
>> for example, should be fine even though it has local scope.
>> Perhaps some explanatory text to this effect?  How about:
>>
>>    The prefix MUST be one of those that the host has
>>    used to assign a non-link-local address to itself.
>>    While any scope greater than link-scope is acceptable,
>>    the prefix SHOULD be one that is unlikely to be advertised
>>    on another link.  Globally Aggregatable Unicast Address
>>    prefixes and Unique Local Address prefixes are examples
>>    of this.
> 
> 
> Your explanation above may be enough, not sure if you
> need to add anything to the draft. Is there a prefix type
> that is likely to be non-unique (other than link-local)?

None that leap to mind.  I guess I was just allowing for the
possibility.

>>>
>>> Suggestion: don't talk about the latter two at all. Change
>>> text to talk about case 1.
>>
>>
>>
>> I think this was getting at the latter two.  With case 1 were you
> 
> 
> Ok. Some clarification in the text is probably needed.
> 
>> referring to the time between sending an RS and receiving an RA?
>> I don't think we have discussed that at all, so it's a good one to
>> discuss.  Should packets from upper layers be blocked until
>> completion of DNA (and possible address reconfiguration)?
>> I'm not sure about that one.  On one hand we don't want to lose
>> packets if we have actually moved, but on the other, we probably
>> don't want to sit around waiting for an RA when we're really still
>> on the same link (maybe there's only one router and the first RA
>> got lost).  I'd probably lean towards blocking.  Does anyone have
>> any suggestions?
> 
> 
> No, but I'd note that there's both outgoing and incoming
> packet issues.

So you don't think the draft should say one way or another, but should
note the issue, or it needs to discuss the issue and note that it
affects both outgoing and incoming packets?

Thanks again for your help.
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 04 16:03:09 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EY8iJ-0003HS-Dp
	for dna-archive@megatron.ietf.org; Fri, 04 Nov 2005 16:03:09 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13514
	for <dna-archive@lists.ietf.org>; Fri, 4 Nov 2005 16:02:39 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV15TLDPM69I5P35@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 05 Nov 2005 08:00:26 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8F7FEAB548; Sat,
 05 Nov 2005 08:00:01 +1100 (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 3FF164FB02; Sat, 05 Nov 2005 08:00:01 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA4Kqr801897	for dna-list; Sat, 05 Nov 2005 07:52:53 +1100
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 jA4Kqqd01893	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 05 Nov 2005 07:52:52 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV15KA8HNM9ASO61@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 05 Nov 2005 07:52:31 +1100
Received: by localhost (Postfix, from userid 510)	id 47840AB55F; Sat,
 05 Nov 2005 07:52:31 +1100 (EST)
Received: from mgw-ext01.nokia.com (mgw-ext01.nokia.com [131.228.20.93])
	(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 BA8BD4FB06	for <dna@eng.monash.edu.au>; Sat,
 05 Nov 2005 07:52:28 +1100 (EST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7)
 with ESMTP id jA4KqGld022241; Fri, 04 Nov 2005 22:52:24 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111])
 by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri,
 04 Nov 2005 22:52:22 +0200
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23])
 by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri,
 04 Nov 2005 14:52:11 -0600
Date: Fri, 04 Nov 2005 12:52:05 -0800
From: Mohan.Parthasarathy@nokia.com
Subject: RE: [DNA] IMPORTANT: Combined DNA Solution draft
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Message-id: <8A76136424391244A5CF016533708537D1CCDD@mvebe101.NOE.Nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] IMPORTANT: Combined DNA Solution draft
Thread-Index: AcXePgKVSrPJjyQnRmy6uUdgKkfktwDNEgMw
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 04 Nov 2005 20:52:11.0175 (UTC)
 FILETIME=[A09F4370:01C5E181]
Content-Transfer-Encoding: 7BIT

Hi,

Here are some comments and questions on the draft. This comes
from someone who has read the archives from time to time but
never been involved in the discussion here. Sorry if some
of them have been discussed/answered before.

The draft size was mere 26 pages and i thought this should
be an easy read. The draft is well written but the first
impression was that it had too many options.

	- Landmark Option
	- Complete RA
	- link-ID
	- Fast RA, rate control,ranking
	- Learned Prefix Option

It is not clear as to why you would need both Complete RA and link-ID ?
Link-ID is present in multicast RA (6.1.9) and also in unicast RA
(6.1.5).

	- Section 6.1.9 says "MAY" for complete RA when scheduling
	  unsolicited RA. So, one can avoid implementing complete RA if
       not for unicast part ? (which also means that you don't need
       LPO because LPO itself is used only by routers (hosts don't
       care where the prefixes appear i guess) to form a complete RA.

	- Section 6.1.5 says SHOULD for generating a complete RA. We
	  have Landmark option and link-ID. Why is this a SHOULD here ?

Some specific comments..

- Section 4.1

    The protocol handles this quite well during graceful renumbering 
   (when the valid lifetime of the prefix is allowed to decrease to
    zero before it is removed and perhaps reassigned to a different
    link), however, it can also cope with "flash" renumbering and
    reassignment but not in an optimized fashion.

  Is section 6.1.10 talking about "flash" renumbering ? Because this
  term is used here (without prior definition) and i could not find
  out whether the discussion in section 6.1.10 pertains to this ?

- section 5.1

	Complete (C)

      The Complete (C) bit indicates that the Router Advertisement
      contains PIOs for all prefixes explicitly configured on the
      sending router, and, if other routers on the link are advertising
      additional prefixes, a Learned Prefix Option containing all
      additional prefixes that the router has heard from other routers
      on the link.

  The definition only requires that if "C" is set, that
  the RA contains "additional" prefixes than what is configured on
  the router. Section 6.1.6 says "C" flag can be set when it includes
  all the leanred prefix in the LPO option. Section 6.1.3 talks about
  bootstrap where "DNA" options are omitted. There is no guidance on
  when the router can start setting the "C" bit. Can it set if it has
  learned at least one other prefix that is not configured on itself ?
  Can it set the "C" bit if all the routers have been configured with
  the same prefix ? (i guess no for this as per the definition).

  A related nit i have is that "Complete" is "Almost complete" because
  you may never know for *sure* when it is really complete i guess :-)

5.2  Landmark Option

  Do we really need two bits "Y" and "N" ? or just one bit that can
  be set to 1 or 0 ? 

5.3 Learned Prefix Option

    It is not clear to me whether a host itself cares whether a prefix
    appears in PIO or LPO. Routers care about it to create
    DNARouterPrefix list. Hosts do look at both (section 6.2.5) but
    do they care ? This is more of a clarification.

6.1.1 Data structures

	The list will be referred to in this
     document as "DNARouterPrefixList".  Prefixes are learned by their
     reception within Prefix Information Options [3] in Router
     Advertisements.  Prefixes in Learned Prefix Options (see Section
5.3)
     MUST NOT update the contents of DNARouterPrefixList

  Why is there a "MUST NOT" ? I understand that the LPO itself may
  contain the prefixes of the router processing the RA from a different
  router. But so does the PIO. As DNARouterPrefixList contains just
  the prefixes not configured on this router, you need to filter both
  from PIO and LPO, right ?

6.1.2

	MulticastRADelay

      The delay to be introduced when scheduling a multicast RA in
      response to a RS message when the token bucket is empty.

   You also schedule a multicast RA when the RS comes in with
unspecified
   address, not just when the token bucket is empty i guess.

6.1.5

   If a unicast send token is available AND the source address of the
   Router Solicitation is NOT the unspecified address (::), then a token
   is removed and the Router Advertisement is scheduled for transmission
   as specified in Section 6.1.8.

   If this is not the case AND there is no multicast RA scheduled for

"If this is not the case" means either the token is not available or
the RS has unspecified address i guess. Perhaps, need better wording
here.

   transmission in the next MulticastRADelay, then the RA MUST be sent
   to the link-scoped all-hosts multicast address at the current time
   plus MulticastRADelay.

   If neither of these conditions is true and there is already a

Also, here, what does "neither of these" refer to ?

   multicast RA scheduled for transmission in the next MulticastRADelay,
   then the Router Solicitation MUST be dropped.
    
Section 6.2.5

	 If the RA includes any prefixes in either a PIO or LPO then the
      host can conclude that no link change has occurred and current
      configuration can be assumed to still be current.

      should read

      "If the RA includes any prefixes in either a PIO or
      LPO that matches the prefix in DNAHostPrefixList, then..."

Section 7.0

	 why isn't there a discussion about DNA Router and non-DNA
      router coexisting ? Non-DNA routers behave as though the
      DNA routers don't exist or they still process the messages
      as per rfc 2461. I can't see how it can cause problems,
      but something should be said here i guess..

section 8.1

	With N routers on a link, each RS message sent on the link will
have
     N RA responses sent on the link within (N-1) * RASeparation time.
     The rate control mechanism specified by this memo only controls the
     rate of RA messages generated by each of the routers

  Section 6.1.8 talks about scheduling Fast RAs. FastRAThreshold
(defined
  to be 3) controls how many routers send unicast/Fast RA. And
  rest of the RA are multicast. Though the token bucket controls the
  individual router, doesn't FastRAThreshold control how many routers
  respond ? Even if there is a non-DNA router, it is controlled by
  multicast RA as per RFC 2461. What am i missing i.e how does this
  specification alter anything that is specified in rfc 2461 ?

-mohan

 





>-----Original Message-----
>From: owner-dna@ecselists.eng.monash.edu.au 
>[mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of 
>ext Suresh Krishnan
>Sent: Monday, October 31, 2005 9:08 AM
>To: Dna
>Subject: [DNA] IMPORTANT: Combined DNA Solution draft
>
>Hi Folks,
>   At the last dna WG meeting at IETF63 in Paris, the WG could 
>not achieve consensus on picking one of the two competing DNA 
>solution proposals. The proposals were described in
>
>*) draft-pentland-dna-protocol-00 : using Landmarks and Complete RA
>*) draft-jinchoi-dna-protocol2-00 : using Link ID
>
>The WG, however, achieved consensus that the proposals were 
>similar enough that the ideas from both the proposals could be 
>merged into a single combined solution which would combine the 
>positive aspects of both of the original proposals. The 
>authors of the above mentioned proposals have worked hard 
>together behind the scenes and have come up with a combined 
>solution. Thanks to Brett for volunteering to put together the 
>document and to the original authors for resolving their 
>differences. The combined solution has been submitted and is 
>available at
>
>http://www.ietf.org/internet-drafts/draft-pentland-dna-protocol3-00.txt
>
>Please take some time to read the document before the meeting 
>as we would like to call for consensus during the dna meeting 
>in Vancouver. 
>Direct any issues and/or comments to the mailing list. As 
>usual, if you think the draft is perfect and ready to go, 
>please say so explicitly as well.
>
>Thanks
>Suresh & Greg
>



From dna-owner@webcamserver.eng.monash.edu.au Sat Nov 05 02:46:57 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYIlK-0000mm-Av
	for dna-archive@megatron.ietf.org; Sat, 05 Nov 2005 02:46:57 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16103
	for <dna-archive@lists.ietf.org>; Sat, 5 Nov 2005 02:46:27 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV1SF488IY9ASJHG@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 05 Nov 2005 18:46:35 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8D6F480009; Sat,
 05 Nov 2005 18:46:31 +1100 (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 36E103C004; Sat, 05 Nov 2005 18:46:31 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA57jhO08833	for dna-list; Sat, 05 Nov 2005 18:45:43 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA57jhd08829	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 05 Nov 2005 18:45:43 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV1SE074EQ9I4T7H@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 05 Nov 2005 18:45:38 +1100
Received: by localhost (Postfix, from userid 510)	id E75FAAB543; Sat,
 05 Nov 2005 18:45:07 +1100 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by curly.its.monash.edu.au (Postfix) with ESMTP id B439A4FB05; Sat,
 05 Nov 2005 18:45:05 +1100 (EST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IPH00CW01J21W@mailout2.samsung.com>; Sat,
 05 Nov 2005 16:45:02 +0900 (KST)
Received: from subbareddy ([107.108.71.57])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTPA id <0IPH007QA1J18V@mmp1.samsung.com>; Sat,
 05 Nov 2005 16:45:02 +0900 (KST)
Date: Sat, 05 Nov 2005 13:08:15 +0530
From: Subba Reddy <subbareddy@samsung.com>
Subject: [DNA] Comments on Combined DNA Solution draft
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: <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43664F5D.1040309@ericsson.ca>
Content-Transfer-Encoding: 7BIT

Hi Brett,

        It is good to see combined solution.
Overall draft is good.

Here are few comments/questions.

1. Is the fast RA mechanism is applicable for all the RS's (not only
for DNA RS's) that a router receives
(with source address as unicast link local address)?

2. Consider the following case.
Router R1 (of Link1) is sending Prefix P1 whose life time is 15 seconds.
A host H came to Link1 and included P1 in DNAHostPrefixList.
P1 expired gracefully and assigned to Link2. If H moves to Link2 and
receives complete RA, it will find the match in DNAHostPrefixList and
will assume same link. Host will not delete P1 since expiry time for entries
in DNAHostPrefixList is 1.5 hours.

3. It may be better to mention, how to populate DNAHostPrefixList.
Only reference to this is, last paragraph of section 6.2.5

4. This comment is regarding "whether a host needs to know whether
a particulat prefix is common prefix (LinkID) or not?"
If a host stores all the prefixes of a link, it does not matter whether RA
has included LinkID or not. If a host cannot store all the prefixes
( may be because of maximum bound), there is a probability that host
may not store LinkID. In that case there may not be any use in including
LinkID without mentioning it as LinkID.  If the prefix is mentioned as
LinkID and if we mandate a host to store that common prefix,
this problem may not come.

Am I missing something?

5. From Section 2, Section 4.2 LinkID and Landmark are optional

Section 2,
" ... Aspects of prefix-based LinkID and
   Requested Landmark are optionally included to allow for a decrease in
   the packet sizes associated with Complete RA."

Section 4.2,
"   Frequently, all routers on a link will advertise the same set of
   prefixes and so this technique will incur no space penalty.  However,
   on links where routers advertise different sets of prefixes, packets
   may be larger.  To combat this, two optional mechanisms are defined."

But in some places, LinkID and Landmark are mentioned as MUST.

Section 6.1.5
"   In order to respond to a Router Solicitation, the router SHOULD
   generate a Complete RA as specified in Section 6.1.6.  The Router
   Advertisement MUST include the LinkID, as described in Section 6.1.7."

Section 6.1.6
"   Note that although it may not be possible to fit all of the prefixes
   into an RA, the LinkID prefix MUST be included."

Section 6.1.9
"      They MAY be Complete RAs or MAY include only a subset of the
      configured prefixes, but MUST include the LinkID prefix."

Section 6.2.1
"   Hosts MUST also maintain a "Landmark Prefix" as described in
   Section 6.2.3."

6. LinkID is sent in unsolicited RAs as per section 4.2  We may need to send
LinkID in solicited RAs also in case of incomplete RAs.

From Section 4.2
"  A second mechanism for reducing packet sizes applies to unsolicited
   Router Advertisements. By selecting one prefix on the link to be the
   "link identifier", and making sure that it is included in every
   advertisement, it is possible to omit some prefixes. "

LinkID is sent is solicited RAs as per section 6.1.5
From Section 6.1.5
"  In order to respond to a Router Solicitation, the router SHOULD
   generate a Complete RA as specified in Section 6.1.6.  The Router
   Advertisement MUST include the LinkID, as described in Section 6.1.7."

7. This is comment is raised by others also.
Do we need two bits Y and N in Landmark Option?
I think, one bit may serve the purpose.

8. From Section 6.1.5
"   In order to respond to a Router Solicitation, the router SHOULD
   generate a Complete RA as specified in Section 6.1.6.  The Router
   Advertisement MUST include the LinkID, as described in Section 6.1.7."

For RAs with Landmark option with "Y" bit set, we may not include
LinkId.

9. Since LinkID and Landmark are optional (Section 2),
different implementations are possible.
Router side:-
    a) Complete RA
    b) Complete RA + Landmark
    c) Complete RA + LinkID
    d) Complete RA + Landmark + LinkID

Host side:-
    a) Complete RA
    b) Complete RA + Landmark

As per my understanding all the combinations of router and host
implementations will co-work fine.
If Landmark & LinkID are also part of the solution
(instead of optional), these many possibilities may not be there. It may
be easy to understand and implement.  If this is already discussed by
design team, please ignore this comment.

Editorial:

1. From Section 6.1.5,
"   If this is not the case AND there is no multicast RA scheduled for
   transmission in the next MulticastRADelay, then the RA MUST be sent
   to the link-scoped *all-hosts multicast address* at the current time
   plus MulticastRADelay."

I think, generally we use the term "all-nodes multicast address" instead
of "all-hosts multicast address"

2. From Section 6.1.4
"   Regardless of the state of the DNA flag, each PIO in the RA is
   examined.  If the prefix is not in the router's DNARouterPrefixList
   *or* AdvPrefixList [3], it is added to the DNARouterPrefixList, and its
   expiry time is set."

From Section 6.1.6

"   If it is not possible to generate a Complete RA but the Router
   Solicitation that this Router Advertisement is in response to, if
   any, includes a Landmark Option containing a prefix that is not in
   DNARouterPrefixList *or* AdvPrefixList then the router SHOULD include a
   Landmark Option with the "N" flag set."

I think, "or" may need to be replaced with *and"

3. From Section 6.2.4
"   Hosts SHOULD include a Landmark Option (LO) in the RS message with
   the landmark prefix chosen based on the rules in *section*
   *Section* 6.2.3."

"section" is repeated.

Thanks & Regards,
Subba Reddy





From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 08:34:21 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYkf6-00064T-Kf
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 08:34:21 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26722
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 08:33:53 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3ISF72DE9ASQBS@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 00:32:39 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 1E601AB56D; Mon,
 07 Nov 2005 00:32:30 +1100 (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 9EA314FB06; Mon,
 07 Nov 2005 00:32:28 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6DUKQ31167	for dna-list; Mon, 07 Nov 2005 00:30:20 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA6DUJd31163	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 00:30:19 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3IPLBJS49I5UUH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 00:30:13 +1100
Received: by localhost (Postfix, from userid 510)	id 93261AB54B; Mon,
 07 Nov 2005 00:30:13 +1100 (EST)
Received: from iramx1.ira.uni-karlsruhe.de
 (iramx1.ira.uni-karlsruhe.de [141.3.10.80])
	(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 796354FB05; Mon, 07 Nov 2005 00:30:11 +1100 (EST)
Received: from i72ms2.tm.uni-karlsruhe.de
 ([141.3.70.17] helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps	id 1EYkan-00078I-7w; Sun,
 06 Nov 2005 14:29:56 +0100
Received: from [192.168.2.100] (p54A365DF.dip.t-dialin.net [84.163.101.223])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 3D85AB3E9; Sun,
 06 Nov 2005 14:29:52 +0100 (CET)
Date: Sun, 06 Nov 2005 14:29:52 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: [DNA] Comments on draft-pentland-dna-protocol3-00.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        DNA <dna@eng.monash.edu.au>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, Mark Doll <doll@tm.uka.de>
Message-id: <436E0550.2080803@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5)
 Gecko/20041206 Thunderbird/1.0 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.92.0.0
Content-Transfer-Encoding: 7BIT

Hi DT members,

I read draft-pentland-dna-protocol3-00.txt.  I think the document is
very solid!  It provides a good view on the problem of efficient
movement detection and gives you a clear understanding of how the
protocol works.

Nevertheless, a couple of comments from my side are below.

Section 6.2.6.2:

>    o  Addresses in the "Optimistic" state remain in the "Optimistic"
>       state, but the host defers sending out an NS to initiate Duplicate
>       Address Detection.

Note that OptiDAD may have already been in progress when the node moved,
so the process may have already been "inititated".  Also, OptiDAD allows
you to send more than one NS for increased robustness, whereas the text
above suggests that there is always a single NS.

Maybe, the text should read something like:

   o  Addresses in the "Optimistic" state remain in the "Optimistic"
      state, but the host defers sending out a pending NS if this has
      not yet been sent already.  If the host later concludes that a
      change in IP attachment occurred, it will have to re-initiate
      Optimistic Duplicate Address Detection on the new link.

>    o  No addresses should be in the "Tentative" state, since this state
>       is unnecessary for nodes that support optimistic Duplicate Address
>       Detection.

I don't think this is true.  The draft only says (in section 6.2.6.1)
that the host must *support* OptiDAD, not that it must use it.  E.g.,
the host may use OptiDAD for the link-local address and a Mobile IPv6
care-of address, but not for other addresses.  (I'm not saying there
would be a good reason for doing this.  I'm just saying this may happen
according to the requirements set forth in section 6.2.6.1.)

>    In order to perform the DNA transaction, the DNA host SHOULD select
>    one of the unicast link local addresses that was in the "Preferred"
>    state prior to switching to "Optimistic" and utilize that as the
>    source address on the DNA RS.  If the host had no "Preferred" unicast
>    link local address but did have an address in the "Optimistic" state,
>    it MUST utilize such an address as the source address.  If the host
>    currently has no unicast link local addresses, it MUST construct one
>    and put it into the "Optimistic" state and note this address as
>    having been in the "Optimistic" state previously, but defer sending
>    the NS to confirm.  Note that the presence of a duplicate unicast
>    link local address on the link will not interfere with the ability of
>    the link to route a unicast DNA RA from the router back to the host
>    nor will it result in corruption of the router's neighbor cache,
>    because the TSLLA option is included in the RS and is utilized by the
>    router on the RA frame without changing the neighbor cache.

This paragraph misses that an MLD Report must be sent for the
corresponding solicited-nodes multicast address prior to sending the NS.

RFC2462bis introduces a delay for this MLD Report in oder to
de-synchronize mulitple hosts configuring simultaneously.  But since the
DNA Protocol 3 is tailored to mobile nodes, and mobility already serves
to sufficiently de-synchronize operations IMO, you should be fine in
sending the MLD Report immediately.

>    When the host receives unicast or multicast RAs from the router, if
>    the host determines from the received RAs that it has moved to a new
>    link, the host MUST immediately move all unicast global addresses to
>    the "Deprecated" state and configure new addresses using the subnet
>    prefixes obtained from the RA.  For all unicast link local addresses,
>    the host MUST initiate NS signaling for optimistic Duplicate Address
>    Detection to confirm the uniqueness of the unicast link local
>    addresses on the new link.

Same here:  The host should register its solicited-nodes addresses
before it starts sending NS for OptiDAD.

>    If the host determines from the received RAs that it has not moved to
>    a new link (i.e. the link has not changed) ....

It's important to re-send MLD Reports for all solicited-nodes addresses
even if the host did not change IP attachment, because the host may have
moved to a different side of a snooping switch.  Failure to send MLD
Reports upon an L2 move that was not an L3 move could cause the host not
to receive further multicast messages (which could be a disaster for
things like DAD).

Regards,
- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/




From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 09:13:01 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYlGX-0004sR-EO
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 09:13:01 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28102
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 09:12:36 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3K793PW89ASPY1@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 01:12:44 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 5875FAB54A; Mon,
 07 Nov 2005 01:12:12 +1100 (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 12E4C4FB05; Mon, 07 Nov 2005 01:12:12 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6EBpX31692	for dna-list; Mon, 07 Nov 2005 01:11:51 +1100
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 jA6EBpd31688	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 01:11:51 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3K66PLDQ9A13KP@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 01:11:50 +1100
Received: by localhost (Postfix, from userid 510)	id D632880003; Mon,
 07 Nov 2005 01:11:50 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 6D41D3C00A; Mon,
 07 Nov 2005 01:11:48 +1100 (EST)
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 197714D5; Sun,
 06 Nov 2005 15:11:46 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun,
 06 Nov 2005 15:11:45 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun,
 06 Nov 2005 15:11:45 +0100
Received: from nomadiclab.lmf.ericsson.se
 (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix)
 with ESMTP id 9F1CE2819; Sun, 06 Nov 2005 16:11:45 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id AD5C61AB83C; Sun,
 06 Nov 2005 16:11:43 +0200 (EET)
Date: Sun, 06 Nov 2005 06:11:40 -0800
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: [DNA] A comment on draft-pentland-dna-protocol3-00.txt
In-reply-to: <436E0550.2080803@tm.uka.de>
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: <436E0F1C.2060804@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
References: <436E0550.2080803@tm.uka.de>
X-OriginalArrivalTime: 06 Nov 2005 14:11:45.0407 (UTC)
 FILETIME=[04F980F0:01C5E2DC]
Content-Transfer-Encoding: 7BIT

Hi Brett,

Hopefully this has not already been brought up in one of those mails on 
the mailing list. I tried to quickly look through the issues in other 
mails and the eye didn't catch this one.

We were discussing this on the design team mailing list sometime ago, 
but I don't remember what was the conclusion. Anyway, the case when the 
router is not advertising any prefixes, e.g. the case when stateful
autoconfiguration is applied, is not clearly stated in the specification 
how to proceed (i.e. obviously no landmark prefix can be picked, CPL 
list can't be constructed). Or is it enough just to state the following?

6.2.6.3  DNA and Statefully Configured Addresses

...
    signaling.  If, however, a non-DNA RA is received, the host SHOULD
    use the DHCPv6 CONFIRM message as described in RFC 3315 [8] rather
    than wait for additional RAs to perform CPL, since this will reduce
    the amount of time required for the host to confirm whether or not it
    has moved to a new link.


/Tero



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 09:39:38 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYlgI-00024H-1b
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 09:39:38 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00588
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 09:39:12 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3L4CVIHG9ASNE1@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 01:39:26 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 9D201AB546; Mon,
 07 Nov 2005 01:39:23 +1100 (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 37F8B4FB09; Mon, 07 Nov 2005 01:39:23 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6Ed0331983	for dna-list; Mon, 07 Nov 2005 01:39:00 +1100
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 jA6Ecxd31977	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 01:38:59 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3L3NQDT49A0XIY@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 01:38:50 +1100
Received: by localhost (Postfix, from userid 510)	id EA359AB55F; Mon,
 07 Nov 2005 01:38:19 +1100 (EST)
Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203])
	by moe.its.monash.edu.au (Postfix) with ESMTP id B762B4FB02	for
 <dna@eng.monash.edu.au>; Mon, 07 Nov 2005 01:38:18 +1100 (EST)
Received: by xproxy.gmail.com with SMTP id t5so215398wxc for
 <dna@eng.monash.edu.au>; Sun, 06 Nov 2005 06:38:17 -0800 (PST)
Received: by 10.64.209.3 with SMTP id h3mr4275774qbg; Sun,
 06 Nov 2005 06:38:17 -0800 (PST)
Received: by 10.65.191.4 with HTTP; Sun, 06 Nov 2005 06:38:17 -0800 (PST)
Date: Sun, 06 Nov 2005 20:08:17 +0530
From: Syam Madanapalli <smadanapalli@gmail.com>
Subject: Re: [DNA] Seeking WG input on Non-prefix link identifiers
In-reply-to: 
 <F08E178900F39344AC894077E6AF74D1010707DD@esealmw114.eemea.ericsson.se>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Cc: "Suresh Krishnan (QB/EMC)" <suresh.krishnan@ericsson.com>,
        dna@eng.monash.edu.au
Message-id: <10e14db20511060638x732a7e2eje6e0ab34aa32be9@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=hntF9yphnw7BVk4xKsjms8uxv6lKbxRnMx46hM6zZtKnW8/QcHnDV8PJfAjwmseSThcSd4JUhUsOU8ZernSimfV7vn6AciV/ZpJfprjMBsoyix/WEo86cG9cHhpEzdtwqUxoRTyeguO0L5I3af2LyWD+1Utwp9seDe1SDMa7CU4=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: 
 <F08E178900F39344AC894077E6AF74D1010707DD@esealmw114.eemea.ericsson.se>
Content-Transfer-Encoding: 7BIT

I think the case is routers with no prefixes in Router Advertisements.
But I am not sure if such case exists. In such cases, the routers can
include the non-prefix linkIDs for DNA purpose.

Non-Prefix based linkIDs can be defined later if required, however this
may cause mismatch in implementations some hosts not supporting t
he detection of Link Identity based on LinkIDs. It may be worth to work
on such solution as early as possible if required so that all DNA i
mplementations can include this.


Regards,
Syam


On 10/31
/05, Tero Kauppinen (JO/LMF) <tero.kauppinen@ericsson.com> wrote:
> I agree with Brett and JinHyeock.
>
> I don't see any especially important reason why we should do such a
> major change to the document at this point. The whole 'links with no
> routers' case is not perfectly clear to me but in my opinion shouldn't
> be that overwhelming to write an extension to the base draft if such a
> support is felt important later on; structure in Chapter 5.2, for
> example, talks about prefixes but includes also 'pref length' and can
> therefore be used to convey also non-prefix landmarks. This would of
> course require a node to actual response to RS messages, like Brett
> pointed out below.
>
> --
> Tero
>
> > -----Original Message-----
> > From: owner-dna@ecselists.eng.monash.edu.au [mailto:owner-
> > dna@ecselists.eng.monash.edu.au] On Behalf Of Brett Pentland
> > Sent: 29. lokakuuta 2005 5:01
> > To: Suresh Krishnan (QB/EMC)
> > Cc: dna@eng.monash.edu.au
> > Subject: Re: [DNA] Seeking WG input on Non-prefix link identifiers
> >
> > I don't think they are necessary.  If there's no global prefix
> > available to use for identification, then it seems that one ought
> > to be able to generate a ULA prefix just for identification purposes.
> >
> > There might be a problem with links with no routers.  Thinking on
> > the fly now... What about non-router devices being able to perform
> > the DNA functions of a router?  They might respond to RSs with an RA
> > with the M and O flags both set to zero, the router lifetime set to
> > zero, and a PIO with a ULA prefix and both the L and A flags set to
> > zero.  Would that cause any configuration problems?  The zero lifetime
> > would prevent hosts from putting the device in their default routers
> > list.  L=0 would not cause hosts to think the prefix is "on-link".
> > A=0 would prevent hosts from trying to generate addresses from the
> > prefix.  Any other show stoppers?
> >
> > Having non-prefix identifiers might make it possible to carry the
> > identifier in some layer 2 field as an optimization, and that might
> > be useful, but it would be specific to that l2 and so I'm not sure
> > that it's such a great idea.
> >
> > Brett.
> >
> > Suresh Krishnan wrote:
> > > Hi Folks,
> > >   Non-prefix link identifiers have a big effect on the DNA solution.
> > >
> > > - A protocol for agreeing on non-prefix link identifiers needs
> > >   to be specified.
> > >
> > > - Additional options are required for transport
> > >   (prefix linkids only require a flag).
> > >
> > > - Precedence between identifier types needs to be established.
> > >
> > > It's possible to undertake this work either now in the base draft,
> > > or as an extension if required.
> > >
> > > Further development of the current solution draft requires
> > > determination of which path to take.
> > >
> > > We'd like to make a consensus call starting
> > > 00:00 UTC Monday 17 October 2005
> > >
> > > and ending
> > > 00:00 UTC Monday 31 October 2005
> > >
> > > On the topic:
> > >
> > > Should the working group develop non-prefix link identifiers as
> > > part of the base DNA solution protocol?
> > >
> > > Regards
> > > Greg and Suresh
>
>



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 09:49:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYlpz-0004Vo-3e
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 09:49:39 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00969
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 09:49:13 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3LF95U2K9I627S@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 01:48:30 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B41B5AB544; Mon,
 07 Nov 2005 01:48:10 +1100 (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 724084FB04; Mon, 07 Nov 2005 01:48:10 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6Elp232148	for dna-list; Mon, 07 Nov 2005 01:47:51 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA6Elpd32144	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 01:47:51 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3LDR2GJO9I627S@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 01:46:58 +1100
Received: by localhost (Postfix, from userid 510)	id 40B32AB543; Mon,
 07 Nov 2005 01:46:28 +1100 (EST)
Received: from iramx1.ira.uni-karlsruhe.de
 (iramx1.ira.uni-karlsruhe.de [141.3.10.80])
	(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 D0B1C4FB05; Mon, 07 Nov 2005 01:46:25 +1100 (EST)
Received: from i72ms2.tm.uni-karlsruhe.de
 ([141.3.70.17] helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps	id 1EYlml-0001nN-Oa; Sun,
 06 Nov 2005 15:46:22 +0100
Received: from [192.168.2.100] (p54A365DF.dip.t-dialin.net [84.163.101.223])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 5F1528546; Sun,
 06 Nov 2005 15:46:18 +0100 (CET)
Date: Sun, 06 Nov 2005 15:46:18 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <4369AD3B.1010203@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        Jari Arkko <jari.arkko@kolumbus.fi>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <436E173A.6020703@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5)
 Gecko/20041206 Thunderbird/1.0 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.92.0.0
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
 <4369AD3B.1010203@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

>>> [...]
>>>
>>>   - If the RS has a landmark and the router recognizes it
>>>     a short RA is possible.
>>>   - If the RS has a landmark but the router doesn't
>>>     understand it, the landmark is ignored and a complete RA is sent
>>>     that the host can use to make an immediate decision.
>>>   - If the RS has no landmark, then the router sends a
>>>     complete RA that the host can again make use of immediately.
>>
>>
>> Its agreed that if complete RAs can be used then there's
>> really no issue (other than perhaps loss of a little bit of
>> bandwidth, but I wouldn't worry about that). However, in
>> your second case above, what happens if the RS has a landmark,
>> the router doesn't implement them, and it can't fit all the
>> prefixes in the complete RA? It seems that the router will
>> make a "random" decision of what prefixes to include, and
>> since it doesn't recognize the landmark option, it may not
>> include the host's prefix. Will this cause a problem?
>
>
> I don't think so.  The choice of prefixes to include is not quite
> random, because the router is required to include the "LinkID" prefix.
> That may not be the prefix that the host picked as a landmark, but
> it will have been received by the host in any earlier RAs if movement
> has not taken place.  Note that I removed the word optional in the
> suggested text for the previous comment because the the language in
> section 6 does not make the LinkID inclusion optional.


I thought you agreed earlier during your discussion that Landmark and
LinkID are optional for hosts only, but both mandatory for routers.

If you change the draft in this regard, a router not understanding the
Landmark option would consequently not support the DNA Protocol 3 at
all.  But such a router would not support LinkID either, and the host
would end up having to apply CPL logic anyway to arrive at a movement
decision.

The host recognizes that it must use CPL because it sent a Landmark
option with the RS, but the solicited RA neither includes a Landmark
option nor has the C flag set.

This said, I don't see a reason why "case 2" (i.e., the RS has a
landmark but the router doesn't understand it) need to be considered for
this protocol at all.

Am I missing something?

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Brett Pentland wrote:
> Jari Arkko wrote:
> 
>> Brett Pentland wrote:
>>
>>>>>   Frequently, all routers on a link will advertise the same set of
>>>>>   prefixes and so this technique will incur no space penalty. 
>>>>> However,
>>>>>   on links where routers advertise different sets of prefixes, packets
>>>>>   may be larger.  To combat this, two optional mechanisms are defined.
>>>>>  
>>>>>
>>>>  From what I understand, Landmark RAs can actually be
>>>> shorter than regular RAs, even if all routers have the
>>>> same prefixes. If there's, say, three prefixes, then the
>>>> optimized unicast answer can include just the landmark
>>>> but not the other options. Or am I missing something?
>>>
>>>
>>>
>>>
>>> Yes, that's true.  This is one of the techniques offered below that can
>>> reduce the RA size.
>>
>>
>>
>> Right. But the text in the draft seemed to be saying that
>> these optimizations are only for the situation where different
>> prefixes are advertised by different routers. Can we get that
>> fixed?
> 
> 
> Ah, ok, I get it now.  I'll fix it up.  How about a change from:
> 
>    Frequently, all routers on a link will advertise the same set of
>    prefixes and so this technique will incur no space penalty.  However,
>    on links where routers advertise different sets of prefixes, packets
>    may be larger.  To combat this, two optional mechanisms are defined.
> 
> to:
> 
>    Though frequently all routers on a link will advertise the same set
>    of prefixes and thus experience no cost in making the RAs complete,
>    there is potential for the RAs to be large when there are many
>    prefixes advertised.  Two mechanisms are defined that allow certain
>    RAs to be reduced in size.
> 
>>
>>>>>   One uses a technique called a "landmark", where the host chooses one
>>>>>   of the prefixes as a landmark prefix, and then includes this in the
>>>>>   Router Solicitation message in the form of a question "am I still
>>>>>   connected to the link which has this prefix?".  The landmark is
>>>>>   carried in a new option, called the Landmark Option.
>>>>>
>>>>>   A second mechanism for reducing packet sizes applies to unsolicited
>>>>>   Router Advertisements.  By selecting one prefix on the link to be
>>>>> the
>>>>>   "link identifier", and making sure that it is included in every
>>>>>   advertisement, it is possible to omit some prefixes.  Such
>>>>>   advertisements will not inform a host of all of the prefixes at
>>>>> once,
>>>>>   but in general these unsolicited advertisements will not be the
>>>>> first
>>>>>   advertisement received on a link.  Inclusion of the link identifier
>>>>>   prefix simply ensures that there is overlap between the sets of
>>>>>   prefixes advertised by each router on a link and that hosts will
>>>>> thus
>>>>>   not incorrectly interpret one of these incomplete RAs as an
>>>>>   indication of movement.
>>>>>  
>>>>>
>>>> I have two issues with this. One is that the optionality
>>>> should be defined in a stricter way (and as far as I can
>>>> see its not done later either, at least not in 6.1.5.1). It
>>>> seems obvious to me that if we are touching code in the
>>>> routers, we should at the same time make it mandatory
>>>> to support the optimized decision mechanism. Then it
>>>> can be optional for _hosts to use_. If router support
>>>> is optional then we end up in a situation where landmark
>>>> request may fail, which consumes time.
>>>
>>>
>>>
>>>
>>> You may be right, but I'm not sure.  The intent here is that the base
>>> means for determining link change is the complete RA.  If both
>>> the host and router support landmarks, then the smaller RA
>>> is possible.  I can't think of a good reason why a router would
>>> not want to support landmarks, but I don't think whether it does
>>> or doesn't breaks anything.
>>>
>>>   - If the RS has a landmark and the router recognizes it
>>>     a short RA is possible.
>>>   - If the RS has a landmark but the router doesn't
>>>     understand it, the landmark is ignored and a complete RA is sent
>>>     that the host can use to make an immediate decision.
>>>   - If the RS has no landmark, then the router sends a
>>>     complete RA that the host can again make use of immediately.
>>
>>
>>
>> Its agreed that if complete RAs can be used then there's
>> really no issue (other than perhaps loss of a little bit of
>> bandwidth, but I wouldn't worry about that). However, in
>> your second case above, what happens if the RS has a landmark,
>> the router doesn't implement them, and it can't fit all the
>> prefixes in the complete RA? It seems that the router will
>> make a "random" decision of what prefixes to include, and
>> since it doesn't recognize the landmark option, it may not
>> include the host's prefix. Will this cause a problem?
> 
> 
> I don't think so.  The choice of prefixes to include is not quite
> random, because the router is required to include the "LinkID" prefix.
> That may not be the prefix that the host picked as a landmark, but
> it will have been received by the host in any earlier RAs if movement
> has not taken place.  Note that I removed the word optional in the
> suggested text for the previous comment because the the language in
> section 6 does not make the LinkID inclusion optional.
> 
>>> If it is unclear then clearly the text needs some tweaking :)
>>> They are not meant to be compared with one another because
>>> they apply in different situations.  Landmarks are useful
>>> for the RS/unicast RA exchange.  LinkID allows unsolicited
>>> RAs to be shortened.
>>>
>>> In this draft, hosts have no notion of the LinkID.  They are
>>> looking for RAs that have no prefixes in common with those that
>>> they have already seen as an indication that they have moved to
>>> a new link.  The LinkID is just a way to make sure that there
>>> will always be overlap between the sets of prefixes in RAs that
>>> are advertised on a link.
>>
>>
>>
>> Your explanation makes sense, but I'm still unsure if
>> the arrangement has to be the way it is. For instance,
>> it would seem that if hosts picked landmark the same
>> way as routers pick linkid, then we would need just
>> one mechanism.
> 
> 
> Hmm.  So the host selects the landmark the same way as the routers
> pick the linkid and then rather than including a landmark
> option in the RA the router just prepares to send its usual RA (which
> must include the linkid) but if the landmark and linkid
> match, then the router can omit everything except the linkid?
> That might work.  Is it what you had in mind?
> 
>> Or if we used just Landmark... not
>> sure I see a big need to reduce packet sizes in unsolicited
>> RAs.
> 
> 
> There's also the assurance of prefix overlap even when it is not
> possible to fit all of the prefixes in a single RA.
> 
>>
>> These alternatives have probably been explored in depth
>> already, sorry if I'm repeating questions that you guys have
>> worked on in the design teams etc. for a long time.
> 
> 
> No that's fine.  This partly comes up because of the attempt to
> merge ideas from two previous proposals, and so is fairly recent.
> 
>>>>
>>>> Does scope matter?
>>>
>>>
>>>
>>>
>>> Well, it must be greater than link-scope.  Beyond that, I guess
>>> that uniqueness is more important than scope.  A ULA prefix,
>>> for example, should be fine even though it has local scope.
>>> Perhaps some explanatory text to this effect?  How about:
>>>
>>>    The prefix MUST be one of those that the host has
>>>    used to assign a non-link-local address to itself.
>>>    While any scope greater than link-scope is acceptable,
>>>    the prefix SHOULD be one that is unlikely to be advertised
>>>    on another link.  Globally Aggregatable Unicast Address
>>>    prefixes and Unique Local Address prefixes are examples
>>>    of this.
>>
>>
>>
>> Your explanation above may be enough, not sure if you
>> need to add anything to the draft. Is there a prefix type
>> that is likely to be non-unique (other than link-local)?
> 
> 
> None that leap to mind.  I guess I was just allowing for the
> possibility.
> 
>>>>
>>>> Suggestion: don't talk about the latter two at all. Change
>>>> text to talk about case 1.
>>>
>>>
>>>
>>>
>>> I think this was getting at the latter two.  With case 1 were you
>>
>>
>>
>> Ok. Some clarification in the text is probably needed.
>>
>>> referring to the time between sending an RS and receiving an RA?
>>> I don't think we have discussed that at all, so it's a good one to
>>> discuss.  Should packets from upper layers be blocked until
>>> completion of DNA (and possible address reconfiguration)?
>>> I'm not sure about that one.  On one hand we don't want to lose
>>> packets if we have actually moved, but on the other, we probably
>>> don't want to sit around waiting for an RA when we're really still
>>> on the same link (maybe there's only one router and the first RA
>>> got lost).  I'd probably lean towards blocking.  Does anyone have
>>> any suggestions?
>>
>>
>>
>> No, but I'd note that there's both outgoing and incoming
>> packet issues.
> 
> 
> So you don't think the draft should say one way or another, but should
> note the issue, or it needs to discuss the issue and note that it
> affects both outgoing and incoming packets?
> 
> Thanks again for your help.
> Brett.




From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 10:05:59 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYm5n-0007I8-EW
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 10:05:59 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01750
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 10:05:33 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3M1S93SI9ASN0G@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 02:05:35 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id ADCE8AB562; Mon,
 07 Nov 2005 02:05:33 +1100 (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 676914FB03; Mon,
 07 Nov 2005 02:05:33 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6F5OG32351	for dna-list; Mon, 07 Nov 2005 02:05:24 +1100
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 jA6F5Nd32347	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 02:05:23 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3M1BU9BU9ASN0G@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 02:05:11 +1100
Received: by localhost (Postfix, from userid 510)	id D02DFAB546; Mon,
 07 Nov 2005 02:05:11 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195])
	by curly.its.monash.edu.au (Postfix) with ESMTP id B2C464FB03	for
 <dna@eng.monash.edu.au>; Mon, 07 Nov 2005 02:05:10 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id j2so165103nzf for
 <dna@eng.monash.edu.au>; Sun, 06 Nov 2005 07:05:09 -0800 (PST)
Received: by 10.64.208.19 with SMTP id f19mr4345114qbg; Sun,
 06 Nov 2005 07:05:09 -0800 (PST)
Received: by 10.65.191.4 with HTTP; Sun, 06 Nov 2005 07:05:09 -0800 (PST)
Date: Sun, 06 Nov 2005 20:35:09 +0530
From: Syam Madanapalli <smadanapalli@gmail.com>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <436E173A.6020703@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        Jari Arkko <jari.arkko@kolumbus.fi>, Dna <dna@eng.monash.edu.au>
Message-id: <10e14db20511060705ja355dcxa5d109fe9011f99d@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=CAjZ7hL1J/Twkn+fILuYJd6WUafGJGJkGejPnU+fOe/vSiL3fE82J55aI2tOU/ws40+2WxpEjR1NUdlodnaQGn9Cn3tP7AwYLwfEboHSQ17SHLCs+ssvKwuPLSYDC2T1IH6a30rwuaA9/ixGL4YTLlU4kuMgQz74RZj81TmRyKs=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
 <4369AD3B.1010203@eng.monash.edu.au> <436E173A.6020703@tm.uka.de>
Content-Transfer-Encoding: 7BIT

On 11/6/05, Christian Vogt <chvogt@tm.uka.de> wrote:
> >>> [...]
> >>>
> >>>   - If the RS has a landmark and the router recognizes it
> >>>     a short RA is possible.
> >>>   - If the RS has a landmark but the router doesn't
> >>>     understand it, the landmark is ignored and a complete RA is sent
> >>>     that the host can use to make an immediate decision.
> >>>   - If the RS has no landmark, then the router sends a
> >>>     complete RA that the host can again make use of immediately.
> >>
> >>
> >> Its agreed that if complete RAs can be used then there's
> >> really no issue (other than perhaps loss of a little bit of
> >> bandwidth, but I wouldn't worry about that). However, in
> >> your second case above, what happens if the RS has a landmark,
> >> the router doesn't implement them, and it can't fit all the
> >> prefixes in the complete RA? It seems that the router will
> >> make a "random" decision of what prefixes to include, and
> >> since it doesn't recognize the landmark option, it may not
> >> include the host's prefix. Will this cause a problem?
> >
> >
> > I don't think so.  The choice of prefixes to include is not quite
> > random, because the router is required to include the "LinkID" prefix.
> > That may not be the prefix that the host picked as a landmark, but
> > it will have been received by the host in any earlier RAs if movement
> > has not taken place.  Note that I removed the word optional in the
> > suggested text for the previous comment because the the language in
> > section 6 does not make the LinkID inclusion optional.
>
>
> I thought you agreed earlier during your discussion that Landmark and
> LinkID are optional for hosts only, but both mandatory for routers.
>
> If you change the draft in this regard, a router not understanding the
> Landmark option would consequently not support the DNA Protocol 3 at
> all.  But such a router would not support LinkID either, and the host
> would end up having to apply CPL logic anyway to arrive at a movement
> decision.
>
> The host recognizes that it must use CPL because it sent a Landmark
> option with the RS, but the solicited RA neither includes a Landmark
> option nor has the C flag set.
>
> This said, I don't see a reason why "case 2" (i.e., the RS has a
> landmark but the router doesn't understand it) need to be considered for
> this protocol at all.
>

I think it is good to mandate the routers to support Landmark option and it is
optional for hosts to use it. This will ease the implemention on host side.

Regards,
Syam



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 10:14:48 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYmEJ-0008DB-TK
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 10:14:48 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02004
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 10:14:22 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3MBWX9Y69I60YL@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 02:13:56 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B5BB680003; Mon,
 07 Nov 2005 02:13:43 +1100 (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 6AF873C006; Mon, 07 Nov 2005 02:13:43 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6FDZi32449	for dna-list; Mon, 07 Nov 2005 02:13:35 +1100
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 jA6FDYd32445	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 02:13:34 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3MBJR4ZY9ASQYT@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 02:13:26 +1100
Received: by localhost (Postfix, from userid 510)	id AA767AB542; Mon,
 07 Nov 2005 02:12:55 +1100 (EST)
Received: from iramx1.ira.uni-karlsruhe.de
 (iramx1.ira.uni-karlsruhe.de [141.3.10.80])
	(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 3F5774FB08; Mon, 07 Nov 2005 02:12:54 +1100 (EST)
Received: from i72ms2.tm.uni-karlsruhe.de
 ([141.3.70.17] helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps	id 1EYmCL-0002nN-JY; Sun,
 06 Nov 2005 16:12:50 +0100
Received: from [192.168.2.100] (p54A365DF.dip.t-dialin.net [84.163.101.223])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id B44E9B3C3; Sun,
 06 Nov 2005 16:12:44 +0100 (CET)
Date: Sun, 06 Nov 2005 16:12:45 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <10e14db20511060705ja355dcxa5d109fe9011f99d@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Syam Madanapalli <smadanapalli@gmail.com>
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        Jari Arkko <jari.arkko@kolumbus.fi>, Dna <dna@eng.monash.edu.au>
Message-id: <436E1D6D.7030306@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5)
 Gecko/20041206 Thunderbird/1.0 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.92.0.0
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
 <4369AD3B.1010203@eng.monash.edu.au> <436E173A.6020703@tm.uka.de>
 <10e14db20511060705ja355dcxa5d109fe9011f99d@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

Hi Syam.

> I think it is good to mandate the routers to support Landmark option 
> and it is optional for hosts to use it. This will ease the 
> implemention on host side.

Yes, compliance to DNA should require routers to support both.  Then
hosts can choose what to use.  Jari brought this up initially.

Besides, support of LinkID on routers will help CPL-only nodes, because
false positives will no longer occur.  (If routers do not use Link ID,
CPL may give you false positives.)  Note that CPL-only nodes will not
know about the use of LinkID, but that doesn't matter.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Syam Madanapalli wrote:
> On 11/6/05, Christian Vogt <chvogt@tm.uka.de> wrote:
> 
>>>>> [...]
>>>>> 
>>>>> - If the RS has a landmark and the router recognizes it a 
>>>>> short RA is possible. - If the RS has a landmark but the 
>>>>> router doesn't understand it, the landmark is ignored and a 
>>>>> complete RA is sent that the host can use to make an 
>>>>> immediate decision. - If the RS has no landmark, then the 
>>>>> router sends a complete RA that the host can again make use 
>>>>> of immediately.
>>>> 
>>>> 
>>>> Its agreed that if complete RAs can be used then there's really
>>>>  no issue (other than perhaps loss of a little bit of
>>>> bandwidth, but I wouldn't worry about that). However, in your
>>>> second case above, what happens if the RS has a landmark, the
>>>> router doesn't implement them, and it can't fit all the
>>>> prefixes in the complete RA? It seems that the router will make
>>>> a "random" decision of what prefixes to include, and since it
>>>> doesn't recognize the landmark option, it may not include the
>>>> host's prefix. Will this cause a problem?
>>> 
>>> 
>>> I don't think so.  The choice of prefixes to include is not quite
>>>  random, because the router is required to include the "LinkID" 
>>> prefix. That may not be the prefix that the host picked as a 
>>> landmark, but it will have been received by the host in any 
>>> earlier RAs if movement has not taken place.  Note that I removed
>>>  the word optional in the suggested text for the previous comment
>>>  because the the language in section 6 does not make the LinkID 
>>> inclusion optional.
>> 
>> 
>> I thought you agreed earlier during your discussion that Landmark 
>> and LinkID are optional for hosts only, but both mandatory for 
>> routers.
>> 
>> If you change the draft in this regard, a router not understanding 
>> the Landmark option would consequently not support the DNA Protocol
>>  3 at all.  But such a router would not support LinkID either, and 
>> the host would end up having to apply CPL logic anyway to arrive at
>>  a movement decision.
>> 
>> The host recognizes that it must use CPL because it sent a Landmark
>>  option with the RS, but the solicited RA neither includes a 
>> Landmark option nor has the C flag set.
>> 
>> This said, I don't see a reason why "case 2" (i.e., the RS has a 
>> landmark but the router doesn't understand it) need to be 
>> considered for this protocol at all.
>> 
> 
> 
> I think it is good to mandate the routers to support Landmark option 
> and it is optional for hosts to use it. This will ease the 
> implemention on host side.
> 
> Regards, Syam




From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 10:29:16 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYmSJ-0002oi-TO
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 10:29:16 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02512
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 10:28:50 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3MURXSGM9A0Y9D@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 02:28:58 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 298A780003; Mon,
 07 Nov 2005 02:28:26 +1100 (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 DAB6D3C006; Mon, 07 Nov 2005 02:28:25 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6FSDd32614	for dna-list; Mon, 07 Nov 2005 02:28:13 +1100
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 jA6FSCd32610	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 02:28:12 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3MTK7Q3U9ASJNZ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 02:27:57 +1100
Received: by localhost (Postfix, from userid 510)	id 758D6AB561; Mon,
 07 Nov 2005 02:27:57 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 5F7F94FB04	for
 <dna@eng.monash.edu.au>; Mon, 07 Nov 2005 02:27:56 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id j2so166880nzf for
 <dna@eng.monash.edu.au>; Sun, 06 Nov 2005 07:27:55 -0800 (PST)
Received: by 10.64.208.19 with SMTP id f19mr4361075qbg; Sun,
 06 Nov 2005 07:27:55 -0800 (PST)
Received: by 10.65.191.4 with HTTP; Sun, 06 Nov 2005 07:27:55 -0800 (PST)
Date: Sun, 06 Nov 2005 20:57:55 +0530
From: Syam Madanapalli <smadanapalli@gmail.com>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <436E1D6D.7030306@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        Jari Arkko <jari.arkko@kolumbus.fi>, Dna <dna@eng.monash.edu.au>
Message-id: <10e14db20511060727u3afeb9uab472c9376b9e5e4@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=EH1li1/J8LfpXgc3028SQej1SZHnLEOFvqQtvnKBAJx6iKGaU+TM6Pfnt6XL+plmK+YusRs2UvEas1mUsLT8c4k7d6uXRTdOxHyzthUzaNHZavhEu6PAz3opz9w4SmrcMi2o/5RUeeGpGcidf/okOZP1WlU8ZtkPiCLqgNEZA9c=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
 <4369AD3B.1010203@eng.monash.edu.au> <436E173A.6020703@tm.uka.de>
 <10e14db20511060705ja355dcxa5d109fe9011f99d@mail.gmail.com>
 <436E1D6D.7030306@tm.uka.de>
Content-Transfer-Encoding: 7BIT

Hi Christian,

On 11/6/05, Christian Vogt <chvogt@tm.uka.de> wrote:
> Hi Syam.
>
> > I think it is good to mandate the routers to support Landmark option
> > and it is optional for hosts to use it. This will ease the
> > implemention on host side.
>
> Yes, compliance to DNA should require routers to support both.  Then
> hosts can choose what to use.  Jari brought this up initially.
>
> Besides, support of LinkID on routers will help CPL-only nodes, because
> false positives will no longer occur.  (If routers do not use Link ID,
> CPL may give you false positives.)  Note that CPL-only nodes will not
> know about the use of LinkID, but that doesn't matter.
>

The notion of "LinkID" in the current draft is for Routers only and it is just
a common prefix in RAs. The LinkID is not explicitly notified to hosts so
there is no optional behavior for hosts based on the linkID. But as you said
the common prefix is good for CPL for both DNA and non-DNA hosts.

Regards,
Syam



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 15:40:38 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYrJe-00068k-Bq
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 15:40:38 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18979
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 15:40:12 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3XPSFHHU9ASPLQ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 07:40:18 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 38407AB54A; Mon,
 07 Nov 2005 07:40:16 +1100 (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 AF06C4FB0C; Mon, 07 Nov 2005 07:40:15 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6KdXm03677	for dna-list; Mon, 07 Nov 2005 07:39:33 +1100
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 jA6KdWd03673	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 07:39:32 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3XONQR769A0UCP@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 07:39:22 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 90918AB548; Mon,
 07 Nov 2005 07:39:21 +1100 (EST)
Received: from [172.19.242.2]
 (vpn-student-242-2.its.monash.edu.au [172.19.242.2])	(user brett)
	(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 C8C484FB02; Mon, 07 Nov 2005 07:39:19 +1100 (EST)
Date: Mon, 07 Nov 2005 07:39:17 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <8A76136424391244A5CF016533708537D1CCDD@mvebe101.NOE.Nokia.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Mohan.Parthasarathy@nokia.com
Cc: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Message-id: <436E69F5.20106@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <8A76136424391244A5CF016533708537D1CCDD@mvebe101.NOE.Nokia.com>
Content-Transfer-Encoding: 7BIT

Hi Mohan,

Thanks for reviewing the draft.  I'll try to respond to your'
comments in-line:

Mohan.Parthasarathy@nokia.com wrote:
> Hi,
> 
> Here are some comments and questions on the draft. This comes
> from someone who has read the archives from time to time but
> never been involved in the discussion here. Sorry if some
> of them have been discussed/answered before.
> 
> The draft size was mere 26 pages and i thought this should
> be an easy read. The draft is well written but the first
> impression was that it had too many options.
> 
> 	- Landmark Option
> 	- Complete RA
> 	- link-ID
> 	- Fast RA, rate control,ranking
> 	- Learned Prefix Option
> 
> It is not clear as to why you would need both Complete RA and link-ID ?
> Link-ID is present in multicast RA (6.1.9) and also in unicast RA
> (6.1.5).
> 
> 	- Section 6.1.9 says "MAY" for complete RA when scheduling
> 	  unsolicited RA. So, one can avoid implementing complete RA if
>        not for unicast part ? (which also means that you don't need
>        LPO because LPO itself is used only by routers (hosts don't
>        care where the prefixes appear i guess) to form a complete RA.

Hosts need to understand the LPO in order to extract the prefixes from
it.  Regarding "if not for the unicast part", I think the unicast part
is the most important part.  Multicast RAs need to be separated by
MIN_DELAY_BETWEEN_RAS, so if a router has just sent an RA, it is then
unable to respond immediately to RSes for some time.

"LinkID" is perhaps a poor term for this draft since it is unused by
hosts and so may be misleading.  In a side conversation, Syam
suggested perhaps "Common Prefix".
> 
> 	- Section 6.1.5 says SHOULD for generating a complete RA. We
> 	  have Landmark option and link-ID. Why is this a SHOULD here ?

Sending a complete RA means that the host immediately has the complete
set of prefixes in use on the link.  This means that if the host then
subsequently moves to a link that has no DNA routers, it is prepared to
use CPL logic to make a correct movement decision based on the first RA
it receives.

> 
> Some specific comments..
> 
> - Section 4.1
> 
>     The protocol handles this quite well during graceful renumbering 
>    (when the valid lifetime of the prefix is allowed to decrease to
>     zero before it is removed and perhaps reassigned to a different
>     link), however, it can also cope with "flash" renumbering and
>     reassignment but not in an optimized fashion.
> 
>   Is section 6.1.10 talking about "flash" renumbering ? Because this
>   term is used here (without prior definition) and i could not find
>   out whether the discussion in section 6.1.10 pertains to this ?

OK.  I need to define that, and perhaps refine the text in 4.1 a liitle.
6.1.10 and 6.1.11 describe what needs to be done when renumbering and
reassigning respectively, in order to not cause any incorrect decisions
to be made.  If these are ignored then there may be some incorrect
movement decisions made, but within 90 minutes things will be restored
to the point where all is well again.
> 
> - section 5.1
> 
> 	Complete (C)
> 
>       The Complete (C) bit indicates that the Router Advertisement
>       contains PIOs for all prefixes explicitly configured on the
>       sending router, and, if other routers on the link are advertising
>       additional prefixes, a Learned Prefix Option containing all
>       additional prefixes that the router has heard from other routers
>       on the link.
> 
>   The definition only requires that if "C" is set, that
>   the RA contains "additional" prefixes than what is configured on
>   the router. Section 6.1.6 says "C" flag can be set when it includes
>   all the leanred prefix in the LPO option. Section 6.1.3 talks about
>   bootstrap where "DNA" options are omitted. There is no guidance on
>   when the router can start setting the "C" bit. Can it set if it has
>   learned at least one other prefix that is not configured on itself ?
>   Can it set the "C" bit if all the routers have been configured with
>   the same prefix ? (i guess no for this as per the definition).

Good point.  6.1.3 should say that the C flag MUST NOT be set during
bootstrap.  6.1.6 should also state that the C flag MUST NOT be set
if there are known to be prefixes that are not included in the RA.
> 
>   A related nit i have is that "Complete" is "Almost complete" because
>   you may never know for *sure* when it is really complete i guess :-)

The intent was "Complete to the best my knowledge" and only asserted
when the router is in a reasonable position to have that knowledge (i.e.
not during bootstrap).

> 
> 5.2  Landmark Option
> 
>   Do we really need two bits "Y" and "N" ? or just one bit that can
>   be set to 1 or 0 ? 

No, probably not.  It is useful to have an explicit "NO" for when a
complete RA is not possible, but I guess a single flag can still do
that.  We would need to explain that the flag has no meaning when the
option is in an RS.

> 5.3 Learned Prefix Option
> 
>     It is not clear to me whether a host itself cares whether a prefix
>     appears in PIO or LPO. Routers care about it to create
>     DNARouterPrefix list. Hosts do look at both (section 6.2.5) but
>     do they care ? This is more of a clarification.

 From a DNA perspective, hosts don't care - I should make this explicit.
Prefixes in an LPO can't be used for SAA, however.

> 6.1.1 Data structures
> 
> 	The list will be referred to in this
>      document as "DNARouterPrefixList".  Prefixes are learned by their
>      reception within Prefix Information Options [3] in Router
>      Advertisements.  Prefixes in Learned Prefix Options (see Section
> 5.3)
>      MUST NOT update the contents of DNARouterPrefixList
> 
>   Why is there a "MUST NOT" ? I understand that the LPO itself may
>   contain the prefixes of the router processing the RA from a different
>   router. But so does the PIO. As DNARouterPrefixList contains just
>   the prefixes not configured on this router, you need to filter both
>   from PIO and LPO, right ?

This is to make sure that when an administrator pulls a prefix out, that
it will in fact go away, and not just kept being readvertised by the
other routers on the link.  Basically we only want prefixes to be
learned by routers from routers where the prefix has been explicitly
configured.

> 6.1.2
> 
> 	MulticastRADelay
> 
>       The delay to be introduced when scheduling a multicast RA in
>       response to a RS message when the token bucket is empty.
> 
>    You also schedule a multicast RA when the RS comes in with
> unspecified
>    address, not just when the token bucket is empty i guess.

Yes, but that doesn't necessarily have to be delayed.  This delay is
there because if the token bucket is empty, a burst of RSes is
underway and it is likely that there are more to come, and so by
delaying, the multicast RA will answer all of those in one go.
> 
> 6.1.5
> 
>    If a unicast send token is available AND the source address of the
>    Router Solicitation is NOT the unspecified address (::), then a token
>    is removed and the Router Advertisement is scheduled for transmission
>    as specified in Section 6.1.8.
> 
>    If this is not the case AND there is no multicast RA scheduled for
> 
> "If this is not the case" means either the token is not available or
> the RS has unspecified address i guess. Perhaps, need better wording
> here.

OK.

>    transmission in the next MulticastRADelay, then the RA MUST be sent
>    to the link-scoped all-hosts multicast address at the current time
>    plus MulticastRADelay.
> 
>    If neither of these conditions is true and there is already a
> 
> Also, here, what does "neither of these" refer to ?

The conditions in the two paragraphs above.  It sounds like this
needs to be made explicit as well.  I'll do that.
> 
>    multicast RA scheduled for transmission in the next MulticastRADelay,
>    then the Router Solicitation MUST be dropped.
>     
> Section 6.2.5
> 
> 	 If the RA includes any prefixes in either a PIO or LPO then the
>       host can conclude that no link change has occurred and current
>       configuration can be assumed to still be current.
> 
>       should read
> 
>       "If the RA includes any prefixes in either a PIO or
>       LPO that matches the prefix in DNAHostPrefixList, then..."

Correct.  I'll fix that up.

> Section 7.0
> 
> 	 why isn't there a discussion about DNA Router and non-DNA
>       router coexisting ? Non-DNA routers behave as though the
>       DNA routers don't exist or they still process the messages
>       as per rfc 2461. I can't see how it can cause problems,
>       but something should be said here i guess..

Yes, good point.  I also don't see any problems with that, but it's
worth mentioning.

> 
> section 8.1
> 
> 	With N routers on a link, each RS message sent on the link will
> have
>      N RA responses sent on the link within (N-1) * RASeparation time.
>      The rate control mechanism specified by this memo only controls the
>      rate of RA messages generated by each of the routers
> 
>   Section 6.1.8 talks about scheduling Fast RAs. FastRAThreshold
> (defined
>   to be 3) controls how many routers send unicast/Fast RA. And
>   rest of the RA are multicast. Though the token bucket controls the
>   individual router, doesn't FastRAThreshold control how many routers
>   respond ? Even if there is a non-DNA router, it is controlled by
>   multicast RA as per RFC 2461. What am i missing i.e how does this
>   specification alter anything that is specified in rfc 2461 ?

Yes, you're right.  This was text from a version before that
FastRAThreshold was put in.

Thanks again for the detailed review.
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 15:50:56 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYrTc-000898-I9
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 15:50:56 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19344
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 15:50:31 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3Y3CKGEO9ASKA5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 07:50:30 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0C0D780005; Mon,
 07 Nov 2005 07:50:25 +1100 (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 C2BD23C008; Mon, 07 Nov 2005 07:50:24 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6KoIB03856	for dna-list; Mon, 07 Nov 2005 07:50:18 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA6KoHd03852	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 07:50:17 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3Y357O9C9I63BZ@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 07:50:16 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6D39080005; Mon,
 07 Nov 2005 07:49:45 +1100 (EST)
Received: from [172.19.242.2]
 (vpn-student-242-2.its.monash.edu.au [172.19.242.2])	(user brett)
	(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 EC2913C00C; Mon, 07 Nov 2005 07:49:43 +1100 (EST)
Date: Mon, 07 Nov 2005 07:49:41 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <436E173A.6020703@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Jari Arkko <jari.arkko@kolumbus.fi>, Dna <dna@eng.monash.edu.au>
Message-id: <436E6C65.5030205@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <43664F5D.1040309@ericsson.ca> <4367C20E.8000904@kolumbus.fi>
 <4368708A.5040302@eng.monash.edu.au> <43687B68.8070903@kolumbus.fi>
 <4369AD3B.1010203@eng.monash.edu.au> <436E173A.6020703@tm.uka.de>
Content-Transfer-Encoding: 7BIT

Hi Christian,

Christian Vogt wrote:
>>>>[...]
>>>>
>>>>  - If the RS has a landmark and the router recognizes it
>>>>    a short RA is possible.
>>>>  - If the RS has a landmark but the router doesn't
>>>>    understand it, the landmark is ignored and a complete RA is sent
>>>>    that the host can use to make an immediate decision.
>>>>  - If the RS has no landmark, then the router sends a
>>>>    complete RA that the host can again make use of immediately.
>>>
>>>
>>>Its agreed that if complete RAs can be used then there's
>>>really no issue (other than perhaps loss of a little bit of
>>>bandwidth, but I wouldn't worry about that). However, in
>>>your second case above, what happens if the RS has a landmark,
>>>the router doesn't implement them, and it can't fit all the
>>>prefixes in the complete RA? It seems that the router will
>>>make a "random" decision of what prefixes to include, and
>>>since it doesn't recognize the landmark option, it may not
>>>include the host's prefix. Will this cause a problem?
>>
>>
>>I don't think so.  The choice of prefixes to include is not quite
>>random, because the router is required to include the "LinkID" prefix.
>>That may not be the prefix that the host picked as a landmark, but
>>it will have been received by the host in any earlier RAs if movement
>>has not taken place.  Note that I removed the word optional in the
>>suggested text for the previous comment because the the language in
>>section 6 does not make the LinkID inclusion optional.
> 
> 
> 
> I thought you agreed earlier during your discussion that Landmark and
> LinkID are optional for hosts only, but both mandatory for routers.

I think we agreed that LinkID was mandatory for routers.
> 
> If you change the draft in this regard, a router not understanding the
> Landmark option would consequently not support the DNA Protocol 3 at
> all.  But such a router would not support LinkID either, and the host
> would end up having to apply CPL logic anyway to arrive at a movement
> decision.
> 
> The host recognizes that it must use CPL because it sent a Landmark
> option with the RS, but the solicited RA neither includes a Landmark
> option nor has the C flag set.

Yes, but the response for a DNA router that does not (for reasons of its
own) wish to send a landmark response, *is* to send a complete RA, which
will allow the host to correctly make a decision.
> 
> This said, I don't see a reason why "case 2" (i.e., the RS has a
> landmark but the router doesn't understand it) need to be considered for
> this protocol at all.
> 
> Am I missing something?

The point was that not including a landmark response does not actaully
break anything.  We can make its support a MUST if that's what people
prefer, but I didn't make a MUST so far because I thought MUSTs were
only supposed to be included where failing to take the recommended
action would break the protocol.

Cheers,
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 16:29:22 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYs4o-0001XT-FW
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 16:29:22 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21221
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 16:28:56 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV3ZEO1CWU99Z3P4@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 08:28:40 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id DA6C3AB54D; Mon,
 07 Nov 2005 08:28:29 +1100 (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 98A9F4FB07; Mon, 07 Nov 2005 08:28:29 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA6LSHv04264	for dna-list; Mon, 07 Nov 2005 08:28:17 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA6LSFd04260	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 08:28:15 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV3ZE4MZLQ9I5URL@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 08:28:08 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 290B6AB560; Mon,
 07 Nov 2005 08:28:08 +1100 (EST)
Received: from [172.19.242.2]
 (vpn-student-242-2.its.monash.edu.au [172.19.242.2])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 9C5ED4FB03; Mon, 07 Nov 2005 08:28:06 +1100 (EST)
Date: Mon, 07 Nov 2005 08:28:04 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Comments on Combined DNA Solution draft
In-reply-to: <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Subba Reddy <subbareddy@samsung.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <436E7564.9020303@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <43664F5D.1040309@ericsson.ca>
 <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
Content-Transfer-Encoding: 7BIT

Hi Subba,

Subba Reddy wrote:
> Hi Brett,
> 
>         It is good to see combined solution.
> Overall draft is good.

Thankyou.

> Here are few comments/questions.
> 
> 1. Is the fast RA mechanism is applicable for all the RS's (not only
> for DNA RS's) that a router receives
> (with source address as unicast link local address)?

All, including those with the unspecified address as the source - those
ones will all get their responses from routers in the same order.

> 2. Consider the following case.
> Router R1 (of Link1) is sending Prefix P1 whose life time is 15 seconds.
> A host H came to Link1 and included P1 in DNAHostPrefixList.
> P1 expired gracefully and assigned to Link2. If H moves to Link2 and
> receives complete RA, it will find the match in DNAHostPrefixList and
> will assume same link. Host will not delete P1 since expiry time for entries
> in DNAHostPrefixList is 1.5 hours.

No, the host will expire P1 at its expiry time as indicated by the
liftime it learned in the RA it received on Link1.  (see 6.2.1, para 3)
> 
> 3. It may be better to mention, how to populate DNAHostPrefixList.
> Only reference to this is, last paragraph of section 6.2.5

Yes, good point.  6.2.5 needs a paragraph that says when to add prefixes
to DNAHostPrefixList.

> 
> 4. This comment is regarding "whether a host needs to know whether
> a particulat prefix is common prefix (LinkID) or not?"
> If a host stores all the prefixes of a link, it does not matter whether RA
> has included LinkID or not. If a host cannot store all the prefixes
> ( may be because of maximum bound), there is a probability that host
> may not store LinkID. In that case there may not be any use in including
> LinkID without mentioning it as LinkID.  If the prefix is mentioned as
> LinkID and if we mandate a host to store that common prefix,
> this problem may not come.
> 
> Am I missing something?

What's a reasonable number of prefixes for a link?  Even if it's a few
tens, do we need to worry that hosts won't be able to store that many?
If so, I guess hosts could use the same logic as routers to pick the
LinkID prefix out of the advertised list.  I'm not sure that this is
necessary.  What do others think?

> 
> 5. From Section 2, Section 4.2 LinkID and Landmark are optional
> 
> Section 2,
> " ... Aspects of prefix-based LinkID and
>    Requested Landmark are optionally included to allow for a decrease in
>    the packet sizes associated with Complete RA."
> 
> Section 4.2,
> "   Frequently, all routers on a link will advertise the same set of
>    prefixes and so this technique will incur no space penalty.  However,
>    on links where routers advertise different sets of prefixes, packets
>    may be larger.  To combat this, two optional mechanisms are defined."
> 
> But in some places, LinkID and Landmark are mentioned as MUST.

Yes, in an earlier thread with Jari, I think we agreed that LinkID is
a MUST for routers.  I forgot about section 2.  I think I should just
remove the work "optionally" from there.  The only MUST I can see
related to Landmarks is that 6.2.1 says that hosts MUST maintain
a Landmark prefix.  Perhaps this should be a SHOULD since hosts aren't
REQUIRED to send a Landmark option.

> 
> Section 6.1.5
> "   In order to respond to a Router Solicitation, the router SHOULD
>    generate a Complete RA as specified in Section 6.1.6.  The Router
>    Advertisement MUST include the LinkID, as described in Section 6.1.7."
> 
> Section 6.1.6
> "   Note that although it may not be possible to fit all of the prefixes
>    into an RA, the LinkID prefix MUST be included."
> 
> Section 6.1.9
> "      They MAY be Complete RAs or MAY include only a subset of the
>       configured prefixes, but MUST include the LinkID prefix."
> 
> Section 6.2.1
> "   Hosts MUST also maintain a "Landmark Prefix" as described in
>    Section 6.2.3."
> 
> 6. LinkID is sent in unsolicited RAs as per section 4.2  We may need to send
> LinkID in solicited RAs also in case of incomplete RAs.
> 
> From Section 4.2
> "  A second mechanism for reducing packet sizes applies to unsolicited
>    Router Advertisements. By selecting one prefix on the link to be the
>    "link identifier", and making sure that it is included in every
>    advertisement, it is possible to omit some prefixes. "
> 
> LinkID is sent is solicited RAs as per section 6.1.5
> From Section 6.1.5
> "  In order to respond to a Router Solicitation, the router SHOULD
>    generate a Complete RA as specified in Section 6.1.6.  The Router
>    Advertisement MUST include the LinkID, as described in Section 6.1.7."
> 
> 7. This is comment is raised by others also.
> Do we need two bits Y and N in Landmark Option?
> I think, one bit may serve the purpose.

See my response to Mohan.

> 8. From Section 6.1.5
> "   In order to respond to a Router Solicitation, the router SHOULD
>    generate a Complete RA as specified in Section 6.1.6.  The Router
>    Advertisement MUST include the LinkID, as described in Section 6.1.7."
> 
> For RAs with Landmark option with "Y" bit set, we may not include
> LinkId.

Yes, this exception should be noted.

> 9. Since LinkID and Landmark are optional (Section 2),
> different implementations are possible.
> Router side:-
>     a) Complete RA
>     b) Complete RA + Landmark
>     c) Complete RA + LinkID
>     d) Complete RA + Landmark + LinkID
> 
> Host side:-
>     a) Complete RA
>     b) Complete RA + Landmark
> 
> As per my understanding all the combinations of router and host
> implementations will co-work fine.
> If Landmark & LinkID are also part of the solution
> (instead of optional), these many possibilities may not be there. It may
> be easy to understand and implement.  If this is already discussed by
> design team, please ignore this comment.

As mentioned earlier, LinkID is not optional for routers (I'll fix that
text) so there are not so many combinations.  There does seem to be
interest in making Landmark support manditory.
> 
> Editorial:
> 
> 1. From Section 6.1.5,
> "   If this is not the case AND there is no multicast RA scheduled for
>    transmission in the next MulticastRADelay, then the RA MUST be sent
>    to the link-scoped *all-hosts multicast address* at the current time
>    plus MulticastRADelay."
> 
> I think, generally we use the term "all-nodes multicast address" instead
> of "all-hosts multicast address"

OK.

> 2. From Section 6.1.4
> "   Regardless of the state of the DNA flag, each PIO in the RA is
>    examined.  If the prefix is not in the router's DNARouterPrefixList
>    *or* AdvPrefixList [3], it is added to the DNARouterPrefixList, and its
>    expiry time is set."
> 
> From Section 6.1.6
> 
> "   If it is not possible to generate a Complete RA but the Router
>    Solicitation that this Router Advertisement is in response to, if
>    any, includes a Landmark Option containing a prefix that is not in
>    DNARouterPrefixList *or* AdvPrefixList then the router SHOULD include a
>    Landmark Option with the "N" flag set."
> 
> I think, "or" may need to be replaced with *and"

I think that "or" is correct as it's written, but I see what you mean.
Maybe it would be clearer if it said:

"If the prefix is not in the router's DNARouterPrefixList and not in the
router's AdvPrefixList"...

How's that?

> 3. From Section 6.2.4
> "   Hosts SHOULD include a Landmark Option (LO) in the RS message with
>    the landmark prefix chosen based on the rules in *section*
>    *Section* 6.2.3."
> 
> "section" is repeated.

OK, I'll fix it.

Thanks for your review.
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 06 23:50:16 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EYyxU-0003Uy-9I
	for dna-archive@megatron.ietf.org; Sun, 06 Nov 2005 23:50:16 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13336
	for <dna-archive@lists.ietf.org>; Sun, 6 Nov 2005 23:49:49 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4ETNC8LA9ASM9P@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 15:49:50 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 28A59AB572; Mon,
 07 Nov 2005 15:49:45 +1100 (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 C4BC24FB02; Mon,
 07 Nov 2005 15:49:44 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA74mw809389	for dna-list; Mon, 07 Nov 2005 15:48:58 +1100
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 jA74mwd09385	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 15:48:58 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4ESO0M8K9A0MKW@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 15:48:58 +1100
Received: by localhost (Postfix, from userid 510)	id D957380015; Mon,
 07 Nov 2005 15:48:57 +1100 (EST)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 9DF0C3C008; Mon,
 07 Nov 2005 15:48:55 +1100 (EST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IPK006ZUIPG4R@mailout1.samsung.com>; Mon,
 07 Nov 2005 13:48:52 +0900 (KST)
Received: from subbareddy ([107.108.71.57])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTPA id <0IPK00453IPAEK@mmp1.samsung.com>; Mon,
 07 Nov 2005 13:48:52 +0900 (KST)
Date: Mon, 07 Nov 2005 10:11:57 +0530
From: Subba Reddy <subbareddy@samsung.com>
Subject: Re: [DNA] Comments on Combined DNA Solution draft
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: <031a01c5e355$98dc31e0$39476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43664F5D.1040309@ericsson.ca>
 <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
 <436E7564.9020303@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Brett,

> > 1. Is the fast RA mechanism is applicable for all the RS's (not only
> > for DNA RS's) that a router receives
> > (with source address as unicast link local address)?
>
> All, including those with the unspecified address as the source - those
> ones will all get their responses from routers in the same order.

ok

>
> > 2. Consider the following case.
> > Router R1 (of Link1) is sending Prefix P1 whose life time is 15 seconds.
> > A host H came to Link1 and included P1 in DNAHostPrefixList.
> > P1 expired gracefully and assigned to Link2. If H moves to Link2 and
> > receives complete RA, it will find the match in DNAHostPrefixList and
> > will assume same link. Host will not delete P1 since expiry time for
entries
> > in DNAHostPrefixList is 1.5 hours.
>
> No, the host will expire P1 at its expiry time as indicated by the
> liftime it learned in the RA it received on Link1.  (see 6.2.1, para 3)

If the prefix P1 is learned prefix for R1, then it will advertise P1 in LPO.
Host (H) will not be receiving life time in the RA sent by R1. If H has not
received
any RA with P1 in PIO within 15 seconds, it will not delete P1 from
DNAHostPrefixList for the next 1.5 hours.

> >
> > 3. It may be better to mention, how to populate DNAHostPrefixList.
> > Only reference to this is, last paragraph of section 6.2.5
>
> Yes, good point.  6.2.5 needs a paragraph that says when to add prefixes
> to DNAHostPrefixList.
>

ok

> >
> > 4. This comment is regarding "whether a host needs to know whether
> > a particulat prefix is common prefix (LinkID) or not?"
> > If a host stores all the prefixes of a link, it does not matter whether
RA
> > has included LinkID or not. If a host cannot store all the prefixes
> > ( may be because of maximum bound), there is a probability that host
> > may not store LinkID. In that case there may not be any use in including
> > LinkID without mentioning it as LinkID.  If the prefix is mentioned as
> > LinkID and if we mandate a host to store that common prefix,
> > this problem may not come.
> >
> > Am I missing something?
>
> What's a reasonable number of prefixes for a link?  Even if it's a few
> tens, do we need to worry that hosts won't be able to store that many?
> If so, I guess hosts could use the same logic as routers to pick the
> LinkID prefix out of the advertised list.  I'm not sure that this is
> necessary.  What do others think?

ok.

>
> >
> > 5. From Section 2, Section 4.2 LinkID and Landmark are optional
> >
> > Section 2,
> > " ... Aspects of prefix-based LinkID and
> >    Requested Landmark are optionally included to allow for a decrease in
> >    the packet sizes associated with Complete RA."
> >
> > Section 4.2,
> > "   Frequently, all routers on a link will advertise the same set of
> >    prefixes and so this technique will incur no space penalty.  However,
> >    on links where routers advertise different sets of prefixes, packets
> >    may be larger.  To combat this, two optional mechanisms are defined."
> >
> > But in some places, LinkID and Landmark are mentioned as MUST.
>
> Yes, in an earlier thread with Jari, I think we agreed that LinkID is
> a MUST for routers.  I forgot about section 2.  I think I should just
> remove the work "optionally" from there.  The only MUST I can see
> related to Landmarks is that 6.2.1 says that hosts MUST maintain
> a Landmark prefix.  Perhaps this should be a SHOULD since hosts aren't
> REQUIRED to send a Landmark option.

ok.

>
> >
> > Section 6.1.5
> > "   In order to respond to a Router Solicitation, the router SHOULD
> >    generate a Complete RA as specified in Section 6.1.6.  The Router
> >    Advertisement MUST include the LinkID, as described in Section
6.1.7."
> >
> > Section 6.1.6
> > "   Note that although it may not be possible to fit all of the prefixes
> >    into an RA, the LinkID prefix MUST be included."
> >
> > Section 6.1.9
> > "      They MAY be Complete RAs or MAY include only a subset of the
> >       configured prefixes, but MUST include the LinkID prefix."
> >
> > Section 6.2.1
> > "   Hosts MUST also maintain a "Landmark Prefix" as described in
> >    Section 6.2.3."
> >
> > 6. LinkID is sent in unsolicited RAs as per section 4.2  We may need to
send
> > LinkID in solicited RAs also in case of incomplete RAs.
> >
> > From Section 4.2
> > "  A second mechanism for reducing packet sizes applies to unsolicited
> >    Router Advertisements. By selecting one prefix on the link to be the
> >    "link identifier", and making sure that it is included in every
> >    advertisement, it is possible to omit some prefixes. "
> >
> > LinkID is sent is solicited RAs as per section 6.1.5
> > From Section 6.1.5
> > "  In order to respond to a Router Solicitation, the router SHOULD
> >    generate a Complete RA as specified in Section 6.1.6.  The Router
> >    Advertisement MUST include the LinkID, as described in Section
6.1.7."
> >
> > 7. This is comment is raised by others also.
> > Do we need two bits Y and N in Landmark Option?
> > I think, one bit may serve the purpose.
>
> See my response to Mohan.
>
> > 8. From Section 6.1.5
> > "   In order to respond to a Router Solicitation, the router SHOULD
> >    generate a Complete RA as specified in Section 6.1.6.  The Router
> >    Advertisement MUST include the LinkID, as described in Section
6.1.7."
> >
> > For RAs with Landmark option with "Y" bit set, we may not include
> > LinkId.
>
> Yes, this exception should be noted.

ok

>
> > 9. Since LinkID and Landmark are optional (Section 2),
> > different implementations are possible.
> > Router side:-
> >     a) Complete RA
> >     b) Complete RA + Landmark
> >     c) Complete RA + LinkID
> >     d) Complete RA + Landmark + LinkID
> >
> > Host side:-
> >     a) Complete RA
> >     b) Complete RA + Landmark
> >
> > As per my understanding all the combinations of router and host
> > implementations will co-work fine.
> > If Landmark & LinkID are also part of the solution
> > (instead of optional), these many possibilities may not be there. It may
> > be easy to understand and implement.  If this is already discussed by
> > design team, please ignore this comment.
>
> As mentioned earlier, LinkID is not optional for routers (I'll fix that
> text) so there are not so many combinations.  There does seem to be
> interest in making Landmark support manditory.

ok

> >
> > Editorial:
> >
> > 1. From Section 6.1.5,
> > "   If this is not the case AND there is no multicast RA scheduled for
> >    transmission in the next MulticastRADelay, then the RA MUST be sent
> >    to the link-scoped *all-hosts multicast address* at the current time
> >    plus MulticastRADelay."
> >
> > I think, generally we use the term "all-nodes multicast address" instead
> > of "all-hosts multicast address"
>
> OK.
>
> > 2. From Section 6.1.4
> > "   Regardless of the state of the DNA flag, each PIO in the RA is
> >    examined.  If the prefix is not in the router's DNARouterPrefixList
> >    *or* AdvPrefixList [3], it is added to the DNARouterPrefixList, and
its
> >    expiry time is set."
> >
> > From Section 6.1.6
> >
> > "   If it is not possible to generate a Complete RA but the Router
> >    Solicitation that this Router Advertisement is in response to, if
> >    any, includes a Landmark Option containing a prefix that is not in
> >    DNARouterPrefixList *or* AdvPrefixList then the router SHOULD include
a
> >    Landmark Option with the "N" flag set."
> >
> > I think, "or" may need to be replaced with *and"
>
> I think that "or" is correct as it's written, but I see what you mean.
> Maybe it would be clearer if it said:
>
> "If the prefix is not in the router's DNARouterPrefixList and not in the
> router's AdvPrefixList"...
>
> How's that?

This is fine.

Thanks & Regards,
Subba Reddy




From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 01:41:34 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZ0hC-0005mP-6w
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 01:41:34 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18024
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 01:41:01 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV4IKGHBS09I6972@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 17:37:29 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6C8EC80002; Mon,
 07 Nov 2005 17:36:52 +1100 (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 2E3023C009; Mon, 07 Nov 2005 17:36:52 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA76aRg10542	for dna-list; Mon, 07 Nov 2005 17:36:27 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA76aQd10538	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 17:36:26 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV4IJSAO429I64F1@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 17:36:20 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2A492AB55C; Mon,
 07 Nov 2005 17:36:20 +1100 (EST)
Received: from [172.19.242.6]
 (vpn-student-242-6.its.monash.edu.au [172.19.242.6])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 824494FB09; Mon, 07 Nov 2005 17:36:16 +1100 (EST)
Date: Mon, 07 Nov 2005 17:36:11 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Comments on Combined DNA Solution draft
In-reply-to: <031a01c5e355$98dc31e0$39476c6b@sisodomain.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Subba Reddy <subbareddy@samsung.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <436EF5DB.6050006@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <43664F5D.1040309@ericsson.ca>
 <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
 <436E7564.9020303@eng.monash.edu.au>
 <031a01c5e355$98dc31e0$39476c6b@sisodomain.com>
Content-Transfer-Encoding: 7BIT


>>>2. Consider the following case.
>>>Router R1 (of Link1) is sending Prefix P1 whose life time is 15 seconds.
>>>A host H came to Link1 and included P1 in DNAHostPrefixList.
>>>P1 expired gracefully and assigned to Link2. If H moves to Link2 and
>>>receives complete RA, it will find the match in DNAHostPrefixList and
>>>will assume same link. Host will not delete P1 since expiry time for
> 
> entries
> 
>>>in DNAHostPrefixList is 1.5 hours.
>>
>>No, the host will expire P1 at its expiry time as indicated by the
>>liftime it learned in the RA it received on Link1.  (see 6.2.1, para 3)
> 
> 
> If the prefix P1 is learned prefix for R1, then it will advertise P1 in LPO.
> Host (H) will not be receiving life time in the RA sent by R1. If H has not
> received
> any RA with P1 in PIO within 15 seconds, it will not delete P1 from
> DNAHostPrefixList for the next 1.5 hours.

Ah, ok in that case that case you have a point.  Usually, the host
would receive an RA from each of the routers on the link within 3
seconds but I guess one or more of those could be lost.  I'm not
sure how realistic such a short prefix lifetime is, but if folks think
this is an issue, we could recommend that if hosts have an entry
in their DNAHostPrefixList for which there has been no PIO received
after X seconds, that they send another RS.

My gut feeling is that this isn't worth worrying about.
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 03:01:54 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZ1ww-00043w-S3
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 03:01:54 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23563
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 03:01:27 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4LIIIUUS9A16X0@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 19:01:39 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id F047180005; Mon,
 07 Nov 2005 19:01:35 +1100 (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 A88633C012; Mon, 07 Nov 2005 19:01:35 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA780uB11467	for dna-list; Mon, 07 Nov 2005 19:00:56 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA780td11463	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 19:00:55 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV4LH44EMI9I69RS@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 19:00:43 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 36FDDAB55C; Mon,
 07 Nov 2005 19:00:28 +1100 (EST)
Received: from [172.19.242.6]
 (vpn-student-242-6.its.monash.edu.au [172.19.242.6])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 0243F4FB03; Mon, 07 Nov 2005 19:00:22 +1100 (EST)
Date: Mon, 07 Nov 2005 19:00:14 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: [DNA] Explicit link identifier
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Dna <dna@eng.monash.edu.au>
Message-id: <436F098E.5040709@eng.monash.edu.au>
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.6 (Windows/20050716)
Content-Transfer-Encoding: 7BIT

Hello DNAers,

draft-pentland-dna-protocol3-00.txt includes a concept of a link
identifier prefix that is implicit.  Routers know the LinkID prefix
and make sure they include it in RAs just to ensure that there is
always overlap between the prefix sets included in RAs on the link.
Hosts don't because they are just looking for an RA with no previously
seen prefixes to indicate movement.

 From a few recent conversations there does seem to be some interest
in having an explicit link identifier.

One way to do this might be to have a flag in the Learned Prefix
Option (LPO) that indicates that Prefix 1 in the option is the
LinkID prefix.

For now only prefix LinkIDs would be considered, but if hosts take
note of the LinkID, and use it as a further check on whether it is
still at the old link even when there are no matching prefixes in
the RA, then a future extension could make use of non-prefix
LinkIDs by having another flag that indicates that the "prefix 1"
is in fact *not* a prefix.  i.e. It is the LinkID, but should not
be added to DNAHostPrefixList.  That extension would also need to
define how routers would select a LinkID and how they would reach
agreement on it amongst themselves.

Here is a suggested LPO format.  The change from the existing draft
is to shift the Prefix Len fields by 8 bits, and to add the two
flags to the new space.  The rest is the same, but the first prefix
field may be interpreted differently, depending on the flags.

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |     Type      |    Length     |L|P| Reserved  | Prefix Len 1  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |      ...      | Prefix Len N  |            Padding            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     +                                                               +
     |                                                               |
     +                          Prefix 1                             +
     |                                                               |
     +                                                               +
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     +                                                               +
     |                                                               |
     +                          Prefix 2                             +
     |                                                               |
     +                                                               +
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ~ ...
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     +                                                               +
     |                                                               |
     +                          Prefix N                             +
     |                                                               |
     +                                                               +
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Some text would be needed to say how routers fill the flags, etc., and
what to do if the LinkID prefix is one that would normally be in a PIO.
Should we add a flag to the PIO format to indicate that that prefix is
the LinkID, or does that prefix just end up in both a PIO and the LPO?
There would also need to be some text in the Host Operations section
that explains how to interpret the LinkID since in the draft at present,
hosts don't know about the LinkID.

So what do folks think?  Is this a sensible way of including an
explicit identifier?  Is 128 bits enough for future non-prefix
identifiers?  Is this something worth pursuing?  If so, why?
Those that have expressed interest have said that having an explicit
identifier is important for mesh networks, but it would be useful to
hear more about that or if there are other reasons as well.

Cheers,
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 03:57:29 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZ2oi-0006bv-NZ
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 03:57:29 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26541
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 03:57:01 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4NFJZMHG9ARX6W@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 07 Nov 2005 19:56:32 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 9815F80003; Mon,
 07 Nov 2005 19:56:27 +1100 (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 4A88C3C004; Mon, 07 Nov 2005 19:56:27 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA78uBH12059	for dna-list; Mon, 07 Nov 2005 19:56:11 +1100
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 jA78uBd12055	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 07 Nov 2005 19:56:11 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4NF6L3WU99ZW8D@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 07 Nov 2005 19:56:11 +1100
Received: by localhost (Postfix, from userid 510)	id F276080002; Mon,
 07 Nov 2005 19:56:10 +1100 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 7AAC43C004; Mon,
 07 Nov 2005 19:56:09 +1100 (EST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IPK005TWU5JFX@mailout2.samsung.com>; Mon,
 07 Nov 2005 17:56:07 +0900 (KST)
Received: from subbareddy ([107.108.71.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0IPK00CW7U5FBN@mmp2.samsung.com>; Mon,
 07 Nov 2005 17:56:07 +0900 (KST)
Date: Mon, 07 Nov 2005 14:19:14 +0530
From: Subba Reddy <subbareddy@samsung.com>
Subject: Re: [DNA] Comments on Combined DNA Solution draft
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: <03ba01c5e378$23a406a0$39476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43664F5D.1040309@ericsson.ca>
 <024601c5e1db$e2e60520$39476c6b@sisodomain.com>
 <436E7564.9020303@eng.monash.edu.au>
 <031a01c5e355$98dc31e0$39476c6b@sisodomain.com>
 <436EF5DB.6050006@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Brett,

> >>>2. Consider the following case.
> >>>Router R1 (of Link1) is sending Prefix P1 whose life time is 15
seconds.
> >>>A host H came to Link1 and included P1 in DNAHostPrefixList.
> >>>P1 expired gracefully and assigned to Link2. If H moves to Link2 and
> >>>receives complete RA, it will find the match in DNAHostPrefixList and
> >>>will assume same link. Host will not delete P1 since expiry time for
> >
> > entries
> >
> >>>in DNAHostPrefixList is 1.5 hours.
> >>
> >>No, the host will expire P1 at its expiry time as indicated by the
> >>liftime it learned in the RA it received on Link1.  (see 6.2.1, para 3)
> >
> >
> > If the prefix P1 is learned prefix for R1, then it will advertise P1 in
LPO.
> > Host (H) will not be receiving life time in the RA sent by R1. If H has
not
> > received
> > any RA with P1 in PIO within 15 seconds, it will not delete P1 from
> > DNAHostPrefixList for the next 1.5 hours.
>
> Ah, ok in that case that case you have a point.  Usually, the host
> would receive an RA from each of the routers on the link within 3
> seconds but I guess one or more of those could be lost.  I'm not
> sure how realistic such a short prefix lifetime is, but if folks think
> this is an issue, we could recommend that if hosts have an entry
> in their DNAHostPrefixList for which there has been no PIO received
> after X seconds, that they send another RS.
>
> My gut feeling is that this isn't worth worrying about.

In the following cases the above scenario may occur
When a prefix is expiring (valid life time is about to become 0)
    1. A host coming up in that link
        or
    2. A host coming from other link to that link
and then moved to a new link where this prefix is being assigned.

But, as you mentioned the probability is very less.
I am also not sure, whether to worry about this.

Thanks & Regards,
Subba Reddy





From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 09:03:06 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZ7aT-0007yM-CF
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 09:03:06 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11357
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 09:02:37 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4Y4RH0SG9A08M5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 08 Nov 2005 01:02:28 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 06B02AB544; Tue,
 08 Nov 2005 01:02:20 +1100 (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 A3C504FB09; Tue, 08 Nov 2005 01:02:19 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA7E12E15439	for dna-list; Tue, 08 Nov 2005 01:01:02 +1100
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 jA7E12d15435	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 08 Nov 2005 01:01:02 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV4Y339OO69A0XI7@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 08 Nov 2005 01:01:00 +1100
Received: by localhost (Postfix, from userid 510)	id 6FD9FAB542; Tue,
 08 Nov 2005 01:01:00 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 1B2204FB09	for
 <dna@eng.monash.edu.au>; Tue, 08 Nov 2005 01:00:58 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id 18so303003nzp for
 <dna@eng.monash.edu.au>; Mon, 07 Nov 2005 06:00:58 -0800 (PST)
Received: by 10.65.193.17 with SMTP id v17mr5277943qbp; Mon,
 07 Nov 2005 06:00:58 -0800 (PST)
Received: by 10.65.191.4 with HTTP; Mon, 07 Nov 2005 06:00:58 -0800 (PST)
Date: Mon, 07 Nov 2005 19:30:58 +0530
From: Syam Madanapalli <smadanapalli@gmail.com>
Subject: Re: [DNA] Explicit link identifier
In-reply-to: <436F098E.5040709@eng.monash.edu.au>
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: <10e14db20511070600uac01046w1ccc636c5e20c2a3@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=GANmuCSOD/Ru37w6rRKurM3+WWsw5HnENo63flRLBGVb0Kx1EJprekyZ9vVOOD9npC0r5x5AOlUhsD0Jc6XN9UOS4FS1NOpezVfODC7pL2hcPKgipM6m3mKGQrh0EP0ky2M2Al709Z9Lj5vyA6Ku9WNjXsYuJ3rAqTJh6r3da50=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <436F098E.5040709@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Brett,

I think it is worth to relook into the Link Identifier option. Current
definition
is to have identifier flag in either PIO or LPIO. A host receives the LinkID
in PIO in one RA and LPIO in other RAs. PIO contains the life time of the
LinkID (prefix life time) and LPIO does not.

So I am wondering if it is good to have a seperate LinkID Option which
can carry any type Identifier with variable length and life time.

Regards,
Syam


On 11/7/05, Brett Pentland <brett.pentland@eng.monash.edu.au> wrote:
> Hello DNAers,
>
> draft-pentland-dna-protocol3-00.txt includes a concept of a link
> identifier prefix that is implicit.  Routers know the LinkID prefix
> and make sure they include it in RAs just to ensure that there is
> always overlap between the prefix sets included in RAs on the link.
> Hosts don't because they are just looking for an RA with no previously
> seen prefixes to indicate movement.
>
>  From a few recent conversations there does seem to be some interest
> in having an explicit link identifier.
>
> One way to do this might be to have a flag in the Learned Prefix
> Option (LPO) that indicates that Prefix 1 in the option is the
> LinkID prefix.
>
> For now only prefix LinkIDs would be considered, but if hosts take
> note of the LinkID, and use it as a further check on whether it is
> still at the old link even when there are no matching prefixes in
> the RA, then a future extension could make use of non-prefix
> LinkIDs by having another flag that indicates that the "prefix 1"
> is in fact *not* a prefix.  i.e. It is the LinkID, but should not
> be added to DNAHostPrefixList.  That extension would also need to
> define how routers would select a LinkID and how they would reach
> agreement on it amongst themselves.
>
> Here is a suggested LPO format.  The change from the existing draft
> is to shift the Prefix Len fields by 8 bits, and to add the two
> flags to the new space.  The rest is the same, but the first prefix
> field may be interpreted differently, depending on the flags.
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |     Type      |    Length     |L|P| Reserved  | Prefix Len 1  |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |      ...      | Prefix Len N  |            Padding            |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix 1                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix 2                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     ~ ...
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix N                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Some text would be needed to say how routers fill the flags, etc., and
> what to do if the LinkID prefix is one that would normally be in a PIO.
> Should we add a flag to the PIO format to indicate that that prefix is
> the LinkID, or does that prefix just end up in both a PIO and the LPO?
> There would also need to be some text in the Host Operations section
> that explains how to interpret the LinkID since in the draft at present,
> hosts don't know about the LinkID.
>
> So what do folks think?  Is this a sensible way of including an
> explicit identifier?  Is 128 bits enough for future non-prefix
> identifiers?  Is this something worth pursuing?  If so, why?
> Those that have expressed interest have said that having an explicit
> identifier is important for mesh networks, but it would be useful to
> hear more about that or if there are other reasons as well.
>
> Cheers,
> Brett.
>



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 12:59:26 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZBHC-0002GI-E1
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 12:59:26 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25926
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 12:58:58 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV56DWWI9C9I6D1H@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 08 Nov 2005 04:58:57 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B9CD2AB543; Tue,
 08 Nov 2005 04:58:47 +1100 (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 6AF864FB02; Tue, 08 Nov 2005 04:58:47 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA7HtwR18242	for dna-list; Tue, 08 Nov 2005 04:55:58 +1100
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 jA7Htvd18238	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 08 Nov 2005 04:55:57 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV56AD33A89APJ4P@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 08 Nov 2005 04:55:56 +1100
Received: by localhost (Postfix, from userid 510)	id 20FBCAB542; Tue,
 08 Nov 2005 04:55:56 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 7D5AA4FB02; Tue,
 08 Nov 2005 04:55:53 +1100 (EST)
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 36B435BE; Mon,
 07 Nov 2005 18:55:51 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon,
 07 Nov 2005 18:53:41 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon,
 07 Nov 2005 18:53:41 +0100
Received: from nomadiclab.lmf.ericsson.se
 (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix)
 with ESMTP id BF86B2823; Mon, 07 Nov 2005 19:53:41 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id AF23F1AB88C; Mon,
 07 Nov 2005 19:53:40 +0200 (EET)
Date: Mon, 07 Nov 2005 09:53:35 -0800
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: Re: [DNA] A comment on draft-pentland-dna-protocol3-00.txt
In-reply-to: <436E0F1C.2060804@ericsson.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        DNA <dna@eng.monash.edu.au>
Message-id: <436F949F.3090204@ericsson.com>
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.7 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
References: <436E0550.2080803@tm.uka.de> <436E0F1C.2060804@ericsson.com>
X-OriginalArrivalTime: 07 Nov 2005 17:53:41.0604 (UTC)
 FILETIME=[3075AA40:01C5E3C4]
Content-Transfer-Encoding: 7BIT

Brett,

I found this while digging into the DT mail archive. Erik educated me 
once with the following:

"Even if DHCP is used for address autoconfiguration, there is normally 
significant benefit of telling the hosts the on-link prefixes.

If the routers don't advertise any on-link prefixes, then the hosts will 
have to send all packets to a router (even when the destination is on 
the local link). RFC 2461 does have a redirect message which the routers 
can use in this case to tell a host "the destination is on link - at 
this L2 address". But for a normal broadcast medium, having the hosts 
know the on-link prefixes and using NS/NA to find the L2 addresses is 
more efficient."

However, it's still valid to have a network where the router advertises 
no prefix in the router advertisement but as pointed out above it is not 
an optimal way of configuring the network.

/Tero

Tero Kauppinen (JO/LMF) wrote:
> Hi Brett,
> 
> Hopefully this has not already been brought up in one of those mails on 
> the mailing list. I tried to quickly look through the issues in other 
> mails and the eye didn't catch this one.
> 
> We were discussing this on the design team mailing list sometime ago, 
> but I don't remember what was the conclusion. Anyway, the case when the 
> router is not advertising any prefixes, e.g. the case when stateful
> autoconfiguration is applied, is not clearly stated in the specification 
> how to proceed (i.e. obviously no landmark prefix can be picked, CPL 
> list can't be constructed). Or is it enough just to state the following?
> 
> 6.2.6.3  DNA and Statefully Configured Addresses
> 
> ...
>    signaling.  If, however, a non-DNA RA is received, the host SHOULD
>    use the DHCPv6 CONFIRM message as described in RFC 3315 [8] rather
>    than wait for additional RAs to perform CPL, since this will reduce
>    the amount of time required for the host to confirm whether or not it
>    has moved to a new link.
> 
> 
> /Tero




From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 13:42:07 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZBwU-00040i-Sl
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 13:42:06 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28370
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 13:41:39 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV57UU0IJ69I6D6Q@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 08 Nov 2005 05:41:38 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 9EFCBAB543; Tue,
 08 Nov 2005 05:41:27 +1100 (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 4FA7E4FB04; Tue, 08 Nov 2005 05:41:27 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA7If6r18749	for dna-list; Tue, 08 Nov 2005 05:41:06 +1100
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 jA7If6d18745	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 08 Nov 2005 05:41:06 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV57UB0OYC9A0PTR@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 08 Nov 2005 05:41:02 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2D00CAB559; Tue,
 08 Nov 2005 05:41:02 +1100 (EST)
Received: from [172.19.242.2]
 (vpn-student-242-2.its.monash.edu.au [172.19.242.2])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id E68B24FB0C; Tue, 08 Nov 2005 05:41:00 +1100 (EST)
Date: Tue, 08 Nov 2005 05:40:57 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] A comment on draft-pentland-dna-protocol3-00.txt
In-reply-to: <436F949F.3090204@ericsson.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Cc: DNA <dna@eng.monash.edu.au>
Message-id: <436F9FB9.2090706@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <436E0550.2080803@tm.uka.de> <436E0F1C.2060804@ericsson.com>
 <436F949F.3090204@ericsson.com>
Content-Transfer-Encoding: 7BIT

Hi Tero,

I'm not sure about that one.  If the host has been previously assigned
an address using DHCP, then it could easily extract a prefix from that
to use as a landmark.  The problem would be how the routers found out
about the prefixes.  I guess they have to know about them but I'm not
sure how DNA would be supposed to access them.  Would it be reasonable
to take them straight from the routing table?  I don't know if that's
a good idea.  Other than that, we could have an applicability statement
that just makes such configuations out-of-scope but that's not a very
satisfying answer.

Any thoughts?
Brett.

Tero Kauppinen (JO/LMF) wrote:
> Brett,
> 
> I found this while digging into the DT mail archive. Erik educated me 
> once with the following:
> 
> "Even if DHCP is used for address autoconfiguration, there is normally 
> significant benefit of telling the hosts the on-link prefixes.
> 
> If the routers don't advertise any on-link prefixes, then the hosts will 
> have to send all packets to a router (even when the destination is on 
> the local link). RFC 2461 does have a redirect message which the routers 
> can use in this case to tell a host "the destination is on link - at 
> this L2 address". But for a normal broadcast medium, having the hosts 
> know the on-link prefixes and using NS/NA to find the L2 addresses is 
> more efficient."
> 
> However, it's still valid to have a network where the router advertises 
> no prefix in the router advertisement but as pointed out above it is not 
> an optimal way of configuring the network.
> 
> /Tero
> 
> Tero Kauppinen (JO/LMF) wrote:
> 
>> Hi Brett,
>>
>> Hopefully this has not already been brought up in one of those mails 
>> on the mailing list. I tried to quickly look through the issues in 
>> other mails and the eye didn't catch this one.
>>
>> We were discussing this on the design team mailing list sometime ago, 
>> but I don't remember what was the conclusion. Anyway, the case when 
>> the router is not advertising any prefixes, e.g. the case when stateful
>> autoconfiguration is applied, is not clearly stated in the 
>> specification how to proceed (i.e. obviously no landmark prefix can be 
>> picked, CPL list can't be constructed). Or is it enough just to state 
>> the following?
>>
>> 6.2.6.3  DNA and Statefully Configured Addresses
>>
>> ...
>>    signaling.  If, however, a non-DNA RA is received, the host SHOULD
>>    use the DHCPv6 CONFIRM message as described in RFC 3315 [8] rather
>>    than wait for additional RAs to perform CPL, since this will reduce
>>    the amount of time required for the host to confirm whether or not it
>>    has moved to a new link.
>>
>>
>> /Tero
> 
> 



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 07 22:12:09 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZJu5-0002Qy-CW
	for dna-archive@megatron.ietf.org; Mon, 07 Nov 2005 22:12:09 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05441
	for <dna-archive@lists.ietf.org>; Mon, 7 Nov 2005 22:11:41 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV5PMDYEEW9ASPJY@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 08 Nov 2005 14:10:06 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B2D3FAB55C; Tue,
 08 Nov 2005 14:10:02 +1100 (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 5E1B24FB08; Tue,
 08 Nov 2005 14:10:01 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA839R224435	for dna-list; Tue, 08 Nov 2005 14:09:27 +1100
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 jA839Qd24431	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 08 Nov 2005 14:09:26 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV5PLE2Q549ASQXN@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 08 Nov 2005 14:09:14 +1100
Received: by localhost (Postfix, from userid 510)	id BB966AB543; Tue,
 08 Nov 2005 14:09:14 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 5EC134FB07; Tue,
 08 Nov 2005 14:09:13 +1100 (EST)
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9334A4B1; Tue,
 08 Nov 2005 04:09:11 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174])
 by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue,
 08 Nov 2005 04:09:11 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50])
 by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue,
 08 Nov 2005 04:09:10 +0100
Received: from nomadiclab.lmf.ericsson.se
 (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix)
 with ESMTP id ECD9E2823; Tue, 08 Nov 2005 05:09:10 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A63E61AB8B1; Tue,
 08 Nov 2005 05:09:09 +0200 (EET)
Date: Mon, 07 Nov 2005 19:09:04 -0800
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: Re: [DNA] A comment on draft-pentland-dna-protocol3-00.txt
In-reply-to: <436F9FB9.2090706@eng.monash.edu.au>
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: <437016D0.5060606@ericsson.com>
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.7 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
References: <436E0550.2080803@tm.uka.de> <436E0F1C.2060804@ericsson.com>
 <436F949F.3090204@ericsson.com> <436F9FB9.2090706@eng.monash.edu.au>
X-OriginalArrivalTime: 08 Nov 2005 03:09:10.0984 (UTC)
 FILETIME=[CA517480:01C5E411]
Content-Transfer-Encoding: 7BIT

Brett Pentland wrote:
> Hi Tero,
> 
> I'm not sure about that one.  If the host has been previously assigned
> an address using DHCP, then it could easily extract a prefix from that
> to use as a landmark.  The problem would be how the routers found out
> about the prefixes.  I guess they have to know about them but I'm not
> sure how DNA would be supposed to access them.  Would it be reasonable
> to take them straight from the routing table?  I don't know if that's
> a good idea.  

Maybe reasonable from programming point of view but I'm not sure from 
specification point of view.

Routers could listen to DHCP messages but I'm sure if that would be a 
good idea either.

> Other than that, we could have an applicability statement
> that just makes such configuations out-of-scope but that's not a very
> satisfying answer.

True. We should consider that as the last option.

> 
> Any thoughts?

Not that many at this moment.

/Tero

> Brett.
> 
> Tero Kauppinen (JO/LMF) wrote:
> 
>> Brett,
>>
>> I found this while digging into the DT mail archive. Erik educated me 
>> once with the following:
>>
>> "Even if DHCP is used for address autoconfiguration, there is normally 
>> significant benefit of telling the hosts the on-link prefixes.
>>
>> If the routers don't advertise any on-link prefixes, then the hosts 
>> will have to send all packets to a router (even when the destination 
>> is on the local link). RFC 2461 does have a redirect message which the 
>> routers can use in this case to tell a host "the destination is on 
>> link - at this L2 address". But for a normal broadcast medium, having 
>> the hosts know the on-link prefixes and using NS/NA to find the L2 
>> addresses is more efficient."
>>
>> However, it's still valid to have a network where the router 
>> advertises no prefix in the router advertisement but as pointed out 
>> above it is not an optimal way of configuring the network.
>>
>> /Tero
>>
>> Tero Kauppinen (JO/LMF) wrote:
>>
>>> Hi Brett,
>>>
>>> Hopefully this has not already been brought up in one of those mails 
>>> on the mailing list. I tried to quickly look through the issues in 
>>> other mails and the eye didn't catch this one.
>>>
>>> We were discussing this on the design team mailing list sometime ago, 
>>> but I don't remember what was the conclusion. Anyway, the case when 
>>> the router is not advertising any prefixes, e.g. the case when stateful
>>> autoconfiguration is applied, is not clearly stated in the 
>>> specification how to proceed (i.e. obviously no landmark prefix can 
>>> be picked, CPL list can't be constructed). Or is it enough just to 
>>> state the following?
>>>
>>> 6.2.6.3  DNA and Statefully Configured Addresses
>>>
>>> ...
>>>    signaling.  If, however, a non-DNA RA is received, the host SHOULD
>>>    use the DHCPv6 CONFIRM message as described in RFC 3315 [8] rather
>>>    than wait for additional RAs to perform CPL, since this will reduce
>>>    the amount of time required for the host to confirm whether or not it
>>>    has moved to a new link.
>>>
>>>
>>> /Tero
>>
>>
>>




From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 08 02:36:33 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZO1w-0005ko-Ul
	for dna-archive@megatron.ietf.org; Tue, 08 Nov 2005 02:36:33 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17613
	for <dna-archive@lists.ietf.org>; Tue, 8 Nov 2005 02:36:04 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV5YXC1C729ASPSM@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 08 Nov 2005 18:36:18 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id AABB280004; Tue,
 08 Nov 2005 18:36:10 +1100 (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 483453C003; Tue, 08 Nov 2005 18:36:10 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA87ZIr27332	for dna-list; Tue, 08 Nov 2005 18:35:18 +1100
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 jA87ZHd27328	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 08 Nov 2005 18:35:17 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV5YVYXCGU9A0LLH@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 08 Nov 2005 18:35:05 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id CA81280003; Tue,
 08 Nov 2005 18:35:04 +1100 (EST)
Received: from [172.19.242.38]
 (vpn-student-242-38.its.monash.edu.au [172.19.242.38])	(user brett)
	(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 AF3CF3C00E; Tue, 08 Nov 2005 18:34:59 +1100 (EST)
Date: Tue, 08 Nov 2005 18:34:53 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Comments on draft-pentland-dna-protocol3-00.txt
In-reply-to: <436E0550.2080803@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Christian Vogt <chvogt@tm.uka.de>
Cc: DNA <dna@eng.monash.edu.au>,
        Suresh Krishnan <suresh.krishnan@ericsson.com>,
        Mark Doll <doll@tm.uka.de>
Message-id: <4370551D.2030108@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
References: <436E0550.2080803@tm.uka.de>
Content-Transfer-Encoding: 7BIT

Hi Christian,

Sorry, somehow I missed replying to this one earlier.

Christian Vogt wrote:
> Hi DT members,
> 
> I read draft-pentland-dna-protocol3-00.txt.  I think the document is
> very solid!  It provides a good view on the problem of efficient
> movement detection and gives you a clear understanding of how the
> protocol works.
> 
> Nevertheless, a couple of comments from my side are below.
> 
> Section 6.2.6.2:
> 
> 
>>   o  Addresses in the "Optimistic" state remain in the "Optimistic"
>>      state, but the host defers sending out an NS to initiate Duplicate
>>      Address Detection.
> 
> 
> Note that OptiDAD may have already been in progress when the node moved,
> so the process may have already been "inititated".  Also, OptiDAD allows
> you to send more than one NS for increased robustness, whereas the text
> above suggests that there is always a single NS.
> 
> Maybe, the text should read something like:
> 
>    o  Addresses in the "Optimistic" state remain in the "Optimistic"
>       state, but the host defers sending out a pending NS if this has
>       not yet been sent already.  If the host later concludes that a
>       change in IP attachment occurred, it will have to re-initiate
>       Optimistic Duplicate Address Detection on the new link.

Sounds good.

> 
> 
>>   o  No addresses should be in the "Tentative" state, since this state
>>      is unnecessary for nodes that support optimistic Duplicate Address
>>      Detection.
> 
> 
> I don't think this is true.  The draft only says (in section 6.2.6.1)
> that the host must *support* OptiDAD, not that it must use it.  E.g.,
> the host may use OptiDAD for the link-local address and a Mobile IPv6
> care-of address, but not for other addresses.  (I'm not saying there
> would be a good reason for doing this.  I'm just saying this may happen
> according to the requirements set forth in section 6.2.6.1.)

In order to get a fast response, we need oDAD at least for the
link-local address.  Are you talking about, say a global address
that is using DAD?  I guess such an address should remain tentative
and then if link change is detected, DAD should be reinitiated.
If it's the link-local address itself that is doing full DAD, the host
has to either wait until DAD completes, or use the unspecified
address for a source address, and wait for a delayed multicast RA.
> 
> 
>>   In order to perform the DNA transaction, the DNA host SHOULD select
>>   one of the unicast link local addresses that was in the "Preferred"
>>   state prior to switching to "Optimistic" and utilize that as the
>>   source address on the DNA RS.  If the host had no "Preferred" unicast
>>   link local address but did have an address in the "Optimistic" state,
>>   it MUST utilize such an address as the source address.  If the host
>>   currently has no unicast link local addresses, it MUST construct one
>>   and put it into the "Optimistic" state and note this address as
>>   having been in the "Optimistic" state previously, but defer sending
>>   the NS to confirm.  Note that the presence of a duplicate unicast
>>   link local address on the link will not interfere with the ability of
>>   the link to route a unicast DNA RA from the router back to the host
>>   nor will it result in corruption of the router's neighbor cache,
>>   because the TSLLA option is included in the RS and is utilized by the
>>   router on the RA frame without changing the neighbor cache.
> 
> 
> This paragraph misses that an MLD Report must be sent for the
> corresponding solicited-nodes multicast address prior to sending the NS.
> 
> RFC2462bis introduces a delay for this MLD Report in oder to
> de-synchronize mulitple hosts configuring simultaneously.  But since the
> DNA Protocol 3 is tailored to mobile nodes, and mobility already serves
> to sufficiently de-synchronize operations IMO, you should be fine in
> sending the MLD Report immediately.
> 
> 
>>   When the host receives unicast or multicast RAs from the router, if
>>   the host determines from the received RAs that it has moved to a new
>>   link, the host MUST immediately move all unicast global addresses to
>>   the "Deprecated" state and configure new addresses using the subnet
>>   prefixes obtained from the RA.  For all unicast link local addresses,
>>   the host MUST initiate NS signaling for optimistic Duplicate Address
>>   Detection to confirm the uniqueness of the unicast link local
>>   addresses on the new link.
> 
> 
> Same here:  The host should register its solicited-nodes addresses
> before it starts sending NS for OptiDAD.
> 
> 
>>   If the host determines from the received RAs that it has not moved to
>>   a new link (i.e. the link has not changed) ....
> 
> 
> It's important to re-send MLD Reports for all solicited-nodes addresses
> even if the host did not change IP attachment, because the host may have
> moved to a different side of a snooping switch.  Failure to send MLD
> Reports upon an L2 move that was not an L3 move could cause the host not
> to receive further multicast messages (which could be a disaster for
> things like DAD).

It's definitely important to send the MLD reports and we need some
text for that.  I don't think they necessarily have to go out first.
I thought that when we had this discussion before Paris, we decided that
it was ok to send the RS first.  It will have a TSLLAO in it and so
no NS/NA is needed for the router to send back a unicast RA.  Does that
sound right?

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 08 13:06:34 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZXre-0001BF-34
	for dna-archive@megatron.ietf.org; Tue, 08 Nov 2005 13:06:34 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22826
	for <dna-archive@lists.ietf.org>; Tue, 8 Nov 2005 13:06:05 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV6KXJIYGE9I6L6D@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 05:06:26 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8AD8380003; Wed,
 09 Nov 2005 05:06:16 +1100 (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 2CDA73C008; Wed, 09 Nov 2005 05:06:16 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA8I4cM02099	for dna-list; Wed, 09 Nov 2005 05:04:38 +1100
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 jA8I4bd02093	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 05:04:37 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV6KV8V4W49A1CQ7@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 05:04:25 +1100
Received: by localhost (Postfix, from userid 510)	id 9C88280002; Wed,
 09 Nov 2005 05:04:25 +1100 (EST)
Received: from mgw-ext03.nokia.com (mgw-ext03.nokia.com [131.228.20.95])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)	by larry.its.monash.edu.au (Postfix)
 with ESMTP id CBF323C006; Wed, 09 Nov 2005 05:04:23 +1100 (EST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7)
 with ESMTP id jA8I1abP001439; Tue, 08 Nov 2005 20:01:39 +0200
Received: from daebh102.NOE.Nokia.com ([10.241.35.112])
 by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
 08 Nov 2005 20:04:18 +0200
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23])
 by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
 08 Nov 2005 12:04:15 -0600
Date: Tue, 08 Nov 2005 10:04:13 -0800
From: Mohan.Parthasarathy@nokia.com
Subject: RE: [DNA] IMPORTANT: Combined DNA Solution draft
Sender: owner-dna@ecselists.eng.monash.edu.au
To: brett.pentland@eng.monash.edu.au
Cc: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Message-id: <8A76136424391244A5CF016533708537D6C87F@mvebe101.NOE.Nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] IMPORTANT: Combined DNA Solution draft
Thread-Index: AcXjEj6uSNxJv68wQcO517V53Byb3ABetpyg
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 08 Nov 2005 18:04:15.0691 (UTC)
 FILETIME=[D4D169B0:01C5E48E]
Content-Transfer-Encoding: 7BIT

 
Brett,

A few comments below..

 
>> It is not clear as to why you would need both Complete RA 
>and link-ID ?
>> Link-ID is present in multicast RA (6.1.9) and also in unicast RA 
>> (6.1.5).
>> 
>> 	- Section 6.1.9 says "MAY" for complete RA when scheduling
>> 	  unsolicited RA. So, one can avoid implementing complete RA if
>>        not for unicast part ? (which also means that you don't need
>>        LPO because LPO itself is used only by routers (hosts don't
>>        care where the prefixes appear i guess) to form a complete RA.
>
>Hosts need to understand the LPO in order to extract the 
>prefixes from it.  Regarding "if not for the unicast part", I 
>think the unicast part is the most important part.  Multicast 
>RAs need to be separated by MIN_DELAY_BETWEEN_RAS, so if a 
>router has just sent an RA, it is then unable to respond 
>immediately to RSes for some time.
>
>"LinkID" is perhaps a poor term for this draft since it is 
>unused by hosts and so may be misleading.  In a side 
>conversation, Syam suggested perhaps "Common Prefix".
>> 
>> 	- Section 6.1.5 says SHOULD for generating a complete RA. We
>> 	  have Landmark option and link-ID. Why is this a SHOULD here ?
>
>Sending a complete RA means that the host immediately has the 
>complete set of prefixes in use on the link.  This means that 
>if the host then subsequently moves to a link that has no DNA 
>routers, it is prepared to use CPL logic to make a correct 
>movement decision based on the first RA it receives.
>
It might be useful to put this in the document. Perhaps, it is
there and i did not notice it. If there were only DNA routers,
then i don't need complete RA. Is that right ?
 
>
>> 6.1.1 Data structures
>> 
>> 	The list will be referred to in this
>>      document as "DNARouterPrefixList".  Prefixes are 
>learned by their
>>      reception within Prefix Information Options [3] in Router
>>      Advertisements.  Prefixes in Learned Prefix Options (see Section
>> 5.3)
>>      MUST NOT update the contents of DNARouterPrefixList
>> 
>>   Why is there a "MUST NOT" ? I understand that the LPO itself may
>>   contain the prefixes of the router processing the RA from 
>a different
>>   router. But so does the PIO. As DNARouterPrefixList contains just
>>   the prefixes not configured on this router, you need to filter both
>>   from PIO and LPO, right ?
>
>This is to make sure that when an administrator pulls a prefix 
>out, that it will in fact go away, and not just kept being 
>readvertised by the other routers on the link.  Basically we 
>only want prefixes to be learned by routers from routers where 
>the prefix has been explicitly configured.
>
I don't understand. Complete RA has both the configured and learned
prefixes. If an admin pulls a prefix out, it will stop appearing
in the RA from other routers, and eventually all routers will
converge with the prefixes that are configured across all routers.
Routers that learnt the prefix would stop putting it in the LPO
eventually. Are you concerned that it might take longer for this
to happen ? The motivation for "MUST NOT" is not obvious.

-mohan

 
  
  



From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 08 13:27:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZYC2-0006RS-Tl
	for dna-archive@megatron.ietf.org; Tue, 08 Nov 2005 13:27:39 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24119
	for <dna-archive@lists.ietf.org>; Tue, 8 Nov 2005 13:27:11 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV6LL6GGO69ASOAS@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 05:25:24 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8252EAB544; Wed,
 09 Nov 2005 05:25:19 +1100 (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 1E3B54FB05; Wed, 09 Nov 2005 05:25:19 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA8IP8a02376	for dna-list; Wed, 09 Nov 2005 05:25:08 +1100
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id jA8IP8d02372	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 05:25:08 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV6LKRZGIE9I6E3Y@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 05:25:02 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 673ECAB559; Wed,
 09 Nov 2005 05:25:00 +1100 (EST)
Received: from [172.19.242.2]
 (vpn-student-242-2.its.monash.edu.au [172.19.242.2])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 0DCB84FB06; Wed, 09 Nov 2005 05:24:57 +1100 (EST)
Date: Wed, 09 Nov 2005 05:24:49 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] IMPORTANT: Combined DNA Solution draft
In-reply-to: <8A76136424391244A5CF016533708537D6C87F@mvebe101.NOE.Nokia.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Mohan.Parthasarathy@nokia.com
Cc: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Message-id: <4370ED71.7020603@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <8A76136424391244A5CF016533708537D6C87F@mvebe101.NOE.Nokia.com>
Content-Transfer-Encoding: 7BIT

Mohan.Parthasarathy@nokia.com wrote:
 >
 > Brett,
 >
 > A few comments below..
 >
 >
 >
 >>>It is not clear as to why you would need both Complete RA
 >>
 >>and link-ID ?
 >>
 >>>Link-ID is present in multicast RA (6.1.9) and also in unicast RA
 >>>(6.1.5).
 >>>
 >>>	- Section 6.1.9 says "MAY" for complete RA when scheduling
 >>>	  unsolicited RA. So, one can avoid implementing complete RA if
 >>>       not for unicast part ? (which also means that you don't need
 >>>       LPO because LPO itself is used only by routers (hosts don't
 >>>       care where the prefixes appear i guess) to form a complete RA.
 >>
 >>Hosts need to understand the LPO in order to extract the
 >>prefixes from it.  Regarding "if not for the unicast part", I
 >>think the unicast part is the most important part.  Multicast
 >>RAs need to be separated by MIN_DELAY_BETWEEN_RAS, so if a
 >>router has just sent an RA, it is then unable to respond
 >>immediately to RSes for some time.
 >>
 >>"LinkID" is perhaps a poor term for this draft since it is
 >>unused by hosts and so may be misleading.  In a side
 >>conversation, Syam suggested perhaps "Common Prefix".
 >>
 >>>	- Section 6.1.5 says SHOULD for generating a complete RA. We
 >>>	  have Landmark option and link-ID. Why is this a SHOULD here ?
 >>
 >>Sending a complete RA means that the host immediately has the
 >>complete set of prefixes in use on the link.  This means that
 >>if the host then subsequently moves to a link that has no DNA
 >>routers, it is prepared to use CPL logic to make a correct
 >>movement decision based on the first RA it receives.
 >>
 >
 > It might be useful to put this in the document. Perhaps, it is
 > there and i did not notice it. If there were only DNA routers,
 > then i don't need complete RA. Is that right ?

Yes for the immediate decision, but the host doesn't know where
it will move to next.  If the host receives a Complete RA, then
it is ready to make an immediate decision even if it moves to a
new link and receives an RA from a non-DNA router.

 >>>6.1.1 Data structures
 >>>
 >>>	The list will be referred to in this
 >>>     document as "DNARouterPrefixList".  Prefixes are
 >>
 >>learned by their
 >>
 >>>     reception within Prefix Information Options [3] in Router
 >>>     Advertisements.  Prefixes in Learned Prefix Options (see Section
 >>>5.3)
 >>>     MUST NOT update the contents of DNARouterPrefixList
 >>>
 >>>  Why is there a "MUST NOT" ? I understand that the LPO itself may
 >>>  contain the prefixes of the router processing the RA from
 >>
 >>a different
 >>
 >>>  router. But so does the PIO. As DNARouterPrefixList contains just
 >>>  the prefixes not configured on this router, you need to filter both
 >>>  from PIO and LPO, right ?
 >>
 >>This is to make sure that when an administrator pulls a prefix
 >>out, that it will in fact go away, and not just kept being
 >>readvertised by the other routers on the link.  Basically we
 >>only want prefixes to be learned by routers from routers where
 >>the prefix has been explicitly configured.
 >>
 >
 > I don't understand. Complete RA has both the configured and learned
 > prefixes. If an admin pulls a prefix out, it will stop appearing
 > in the RA from other routers, and eventually all routers will
 > converge with the prefixes that are configured across all routers.
 > Routers that learnt the prefix would stop putting it in the LPO
 > eventually. Are you concerned that it might take longer for this
 > to happen ? The motivation for "MUST NOT" is not obvious.

Say a prefix is explicitly configured on only one out of three routers
on a link.  That prefix will be learned by both of the other routers
on the link and included in LPOs in RAs from those routers.  If the
administrator withdraws the prefix from the router on which it was
configured, the other two routers would continue to see the prefix in
each other's LPOs and in fact the original router would "learn" of the
prefix from the LPOs, and the prefix would never go away.  Does that
explain it adequately?

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 08 13:49:44 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZYXP-0004Es-JQ
	for dna-archive@megatron.ietf.org; Tue, 08 Nov 2005 13:49:44 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25322
	for <dna-archive@lists.ietf.org>; Tue, 8 Nov 2005 13:49:15 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV6MEQYGQU9ASQHU@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 05:48:26 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6EE18AB55C; Wed,
 09 Nov 2005 05:48:23 +1100 (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 270834FB08; Wed,
 09 Nov 2005 05:48:23 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA8Im5V02674	for dna-list; Wed, 09 Nov 2005 05:48:05 +1100
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 jA8Im4d02670	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 05:48:04 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV6ME3GTHQ9I6KPT@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 05:47:52 +1100
Received: by localhost (Postfix, from userid 510)	id C42A0AB542; Wed,
 09 Nov 2005 05:47:51 +1100 (EST)
Received: from mgw-ext04.nokia.com (mgw-ext04.nokia.com [131.228.20.96])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)	by curly.its.monash.edu.au (Postfix)
 with ESMTP id 46A1F4FB0C; Wed, 09 Nov 2005 05:47:49 +1100 (EST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7)
 with ESMTP id jA8IhPsG027410; Tue, 08 Nov 2005 20:43:29 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111])
 by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
 08 Nov 2005 20:47:46 +0200
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23])
 by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
 08 Nov 2005 12:47:43 -0600
Date: Tue, 08 Nov 2005 10:47:48 -0800
From: Mohan.Parthasarathy@nokia.com
Subject: RE: [DNA] IMPORTANT: Combined DNA Solution draft
Sender: owner-dna@ecselists.eng.monash.edu.au
To: brett.pentland@eng.monash.edu.au
Cc: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Message-id: <8A76136424391244A5CF016533708537D6C8C5@mvebe101.NOE.Nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] IMPORTANT: Combined DNA Solution draft
Thread-Index: AcXkkdnQjrhIblmoRRGwzhxWtmql9gAANazw
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 08 Nov 2005 18:47:43.0327 (UTC)
 FILETIME=[E71716F0:01C5E494]
Content-Transfer-Encoding: 7BIT

 

> >>>6.1.1 Data structures
> >>>
> >>>	The list will be referred to in this
> >>>     document as "DNARouterPrefixList".  Prefixes are
> >>
> >>learned by their
> >>
> >>>     reception within Prefix Information Options [3] in Router
> >>>     Advertisements.  Prefixes in Learned Prefix Options 
>(see Section
> >>>5.3)
> >>>     MUST NOT update the contents of DNARouterPrefixList
> >>>
> >>>  Why is there a "MUST NOT" ? I understand that the LPO 
>itself may  >>>  contain the prefixes of the router processing 
>the RA from  >>  >>a different  >>  >>>  router. But so does 
>the PIO. As DNARouterPrefixList contains just  >>>  the 
>prefixes not configured on this router, you need to filter 
>both  >>>  from PIO and LPO, right ?
> >>
> >>This is to make sure that when an administrator pulls a 
>prefix  >>out, that it will in fact go away, and not just kept 
>being  >>readvertised by the other routers on the link.  
>Basically we  >>only want prefixes to be learned by routers 
>from routers where  >>the prefix has been explicitly configured.
> >>
> >
> > I don't understand. Complete RA has both the configured and 
>learned  > prefixes. If an admin pulls a prefix out, it will 
>stop appearing  > in the RA from other routers, and eventually 
>all routers will  > converge with the prefixes that are 
>configured across all routers.
> > Routers that learnt the prefix would stop putting it in the 
>LPO  > eventually. Are you concerned that it might take longer 
>for this  > to happen ? The motivation for "MUST NOT" is not obvious.
>
>Say a prefix is explicitly configured on only one out of three 
>routers on a link.  That prefix will be learned by both of the 
>other routers on the link and included in LPOs in RAs from 
>those routers.  If the administrator withdraws the prefix from 
>the router on which it was configured, the other two routers 
>would continue to see the prefix in each other's LPOs and in 
>fact the original router would "learn" of the prefix from the 
>LPOs, and the prefix would never go away.  Does that explain 
>it adequately?
>
Yes, i can see the problem now. 
But section 6.1.10 says something about graceful removal
of the prefix where it adds to the DNARouterPrefixList and
sets it to expire in 1.5 hours. So, i would assume that
it would hear the same in the LPO from the other routers
(which should stop as per 6.1.4 as there is lifetime for
the learned prefixes also). I have to read a bit more
carefully...

-mohan


-mohan

>Brett.
>



From dna-owner@webcamserver.eng.monash.edu.au Tue Nov 08 20:01:08 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZeKq-0007PY-13
	for dna-archive@megatron.ietf.org; Tue, 08 Nov 2005 20:01:08 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00090
	for <dna-archive@lists.ietf.org>; Tue, 8 Nov 2005 20:00:39 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV6Z9EN9UC9ASMUL@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 11:56:44 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 471E880006; Wed,
 09 Nov 2005 11:56:42 +1100 (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 F1C193C003; Wed, 09 Nov 2005 11:56:41 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA90tqJ06931	for dna-list; Wed, 09 Nov 2005 11:55:52 +1100
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 jA90tpd06927	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 11:55:51 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV6Z872DGQ9I6N8I@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 11:55:44 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A7C01AB55D; Wed,
 09 Nov 2005 11:55:43 +1100 (EST)
Received: from [172.19.243.9]
 (vpn-student-243-9.its.monash.edu.au [172.19.243.9])	(user brett)
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 6E1744FB06; Wed, 09 Nov 2005 11:55:42 +1100 (EST)
Date: Wed, 09 Nov 2005 11:55:39 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Explicit link identifier
In-reply-to: <10e14db20511070600uac01046w1ccc636c5e20c2a3@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Syam Madanapalli <smadanapalli@gmail.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <4371490B.7080309@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <436F098E.5040709@eng.monash.edu.au>
 <10e14db20511070600uac01046w1ccc636c5e20c2a3@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

Hi Syam,

I looked into that when trying to work out how to put these things
together.  The problem I had was that if we have a separate option,
and we end up mostly just using prefix identifiers, then we'll either
have a prefix appearing twice in RAs (once in the LinkID option and
once in the PIO/LPO), or we continue to allow the LinkID prefix to be
indicated by a flag on the relevant prefix and then have the hosts 
having to look for the LinkID in either a PIO, or LPO, or LinkIDO.
Neither sounded too good.

The format I mentioned below does allow for a variable length
identifier, but with an upper limit of 128 bits.

Any thoughts?
Brett.

Syam Madanapalli wrote:
> Hi Brett,
> 
> I think it is worth to relook into the Link Identifier option. Current
> definition
> is to have identifier flag in either PIO or LPIO. A host receives the LinkID
> in PIO in one RA and LPIO in other RAs. PIO contains the life time of the
> LinkID (prefix life time) and LPIO does not.
> 
> So I am wondering if it is good to have a seperate LinkID Option which
> can carry any type Identifier with variable length and life time.
> 
> Regards,
> Syam
> 
> 
> On 11/7/05, Brett Pentland <brett.pentland@eng.monash.edu.au> wrote:
> 
>>Hello DNAers,
>>
>>draft-pentland-dna-protocol3-00.txt includes a concept of a link
>>identifier prefix that is implicit.  Routers know the LinkID prefix
>>and make sure they include it in RAs just to ensure that there is
>>always overlap between the prefix sets included in RAs on the link.
>>Hosts don't because they are just looking for an RA with no previously
>>seen prefixes to indicate movement.
>>
>> From a few recent conversations there does seem to be some interest
>>in having an explicit link identifier.
>>
>>One way to do this might be to have a flag in the Learned Prefix
>>Option (LPO) that indicates that Prefix 1 in the option is the
>>LinkID prefix.
>>
>>For now only prefix LinkIDs would be considered, but if hosts take
>>note of the LinkID, and use it as a further check on whether it is
>>still at the old link even when there are no matching prefixes in
>>the RA, then a future extension could make use of non-prefix
>>LinkIDs by having another flag that indicates that the "prefix 1"
>>is in fact *not* a prefix.  i.e. It is the LinkID, but should not
>>be added to DNAHostPrefixList.  That extension would also need to
>>define how routers would select a LinkID and how they would reach
>>agreement on it amongst themselves.
>>
>>Here is a suggested LPO format.  The change from the existing draft
>>is to shift the Prefix Len fields by 8 bits, and to add the two
>>flags to the new space.  The rest is the same, but the first prefix
>>field may be interpreted differently, depending on the flags.
>>
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |     Type      |    Length     |L|P| Reserved  | Prefix Len 1  |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |      ...      | Prefix Len N  |            Padding            |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +                          Prefix 1                             +
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +                          Prefix 2                             +
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    ~ ...
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +                          Prefix N                             +
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>Some text would be needed to say how routers fill the flags, etc., and
>>what to do if the LinkID prefix is one that would normally be in a PIO.
>>Should we add a flag to the PIO format to indicate that that prefix is
>>the LinkID, or does that prefix just end up in both a PIO and the LPO?
>>There would also need to be some text in the Host Operations section
>>that explains how to interpret the LinkID since in the draft at present,
>>hosts don't know about the LinkID.
>>
>>So what do folks think?  Is this a sensible way of including an
>>explicit identifier?  Is 128 bits enough for future non-prefix
>>identifiers?  Is this something worth pursuing?  If so, why?
>>Those that have expressed interest have said that having an explicit
>>identifier is important for mesh networks, but it would be useful to
>>hear more about that or if there are other reasons as well.
>>
>>Cheers,
>>Brett.
>>



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 01:38:49 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZjbd-0008B7-AY
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 01:38:49 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16889
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 01:38:21 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7B5DYSI89A0PIL@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 17:37:06 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C267180003; Wed,
 09 Nov 2005 17:37:03 +1100 (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 7EF0D3C004; Wed, 09 Nov 2005 17:37:03 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA96aJ211036	for dna-list; Wed, 09 Nov 2005 17:36:19 +1100
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 jA96aJd11032	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 17:36:19 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7B47HWGW9AQFZF@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 17:36:07 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C090480003; Wed,
 09 Nov 2005 17:36:06 +1100 (EST)
Received: from [172.19.242.22]
 (vpn-student-242-22.its.monash.edu.au [172.19.242.22])	(user brett)
	(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 EA8653C006; Wed, 09 Nov 2005 17:36:04 +1100 (EST)
Date: Wed, 09 Nov 2005 17:35:58 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: [DNA] Solution update
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Dna <dna@eng.monash.edu.au>
Message-id: <437198CE.1060809@eng.monash.edu.au>
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.6 (Windows/20050716)
Content-Transfer-Encoding: 7BIT

Hi folks,

I've been trying to incorporate the feedback I've had on the draft
over the last week.  I haven't made it through all of it yet, so it's
definitely work-in-progress, but if you are interested in where it's
at right now, a preview is available at:

http://www.ctie.monash.edu.au/dna-dt/draft-pentland-dna-protocol3-pre02.txt

A diff from the draft currently in the repository can be seen here:

http://www.ctie.monash.edu.au/dna-dt/draft-pentland-dna-protocol3-pre02-from-00.diff.html

The diff is unfortunately quite long because of section numbering
changes but is still fairly easy to scan through.

Cheers,
Brett.



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 06:29:33 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZo8v-0003tj-S4
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 06:29:33 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00527
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 06:29:02 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7LBNG3O099ZPDS@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 09 Nov 2005 22:28:41 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 7202780004; Wed,
 09 Nov 2005 22:28:26 +1100 (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 142C73C006; Wed, 09 Nov 2005 22:28:26 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA9BRfs14496	for dna-list; Wed, 09 Nov 2005 22:27:41 +1100
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 jA9BRfd14492	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 09 Nov 2005 22:27:41 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7LAGV93G9ASOLV@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 09 Nov 2005 22:27:29 +1100
Received: by localhost (Postfix, from userid 510)	id 87764AB542; Wed,
 09 Nov 2005 22:27:29 +1100 (EST)
Received: from thumper.research.telcordia.com
 (thumper.research.telcordia.com [128.96.41.1])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 8A8FE4FB06; Wed, 09 Nov 2005 22:27:28 +1100 (EST)
Received: from [128.96.59.14] (vpntnlB14.research.telcordia.com [128.96.59.14])
	by thumper.research.telcordia.com (8.12.9/8.12.9)
 with ESMTP id jA9BROKm015470; Wed, 09 Nov 2005 06:27:25 -0500 (EST)
Date: Wed, 09 Nov 2005 03:27:22 -0800
From: Raquel Morera <raquel@research.telcordia.com>
Subject: Re: [DNA] Explicit link identifier
In-reply-to: <436F098E.5040709@eng.monash.edu.au>
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: <4371DD1A.6020600@research.telcordia.com>
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.6 (Windows/20050716)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <436F098E.5040709@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Brett,

   I think having the option of an explicit link identifier is actually 
a very good idea.
In mesh/ad-hoc networks, adding an explicit link ID can help identifying 
the link (i.e. mesh) independently of the prefixes that connect the 
network to the internet.
I do not know yet how DNA and link identifier would fit in the protocols 
designed for these networks (not even sure if there is a consensus in 
the definition of a "link"), but having the option would be great as it 
gives us the flexibility to explore it when needed.

Thanks,
   Raquel


Brett Pentland wrote:

> Hello DNAers,
>
> draft-pentland-dna-protocol3-00.txt includes a concept of a link
> identifier prefix that is implicit.  Routers know the LinkID prefix
> and make sure they include it in RAs just to ensure that there is
> always overlap between the prefix sets included in RAs on the link.
> Hosts don't because they are just looking for an RA with no previously
> seen prefixes to indicate movement.
>
> From a few recent conversations there does seem to be some interest
> in having an explicit link identifier.
>
> One way to do this might be to have a flag in the Learned Prefix
> Option (LPO) that indicates that Prefix 1 in the option is the
> LinkID prefix.
>
> For now only prefix LinkIDs would be considered, but if hosts take
> note of the LinkID, and use it as a further check on whether it is
> still at the old link even when there are no matching prefixes in
> the RA, then a future extension could make use of non-prefix
> LinkIDs by having another flag that indicates that the "prefix 1"
> is in fact *not* a prefix.  i.e. It is the LinkID, but should not
> be added to DNAHostPrefixList.  That extension would also need to
> define how routers would select a LinkID and how they would reach
> agreement on it amongst themselves.
>
> Here is a suggested LPO format.  The change from the existing draft
> is to shift the Prefix Len fields by 8 bits, and to add the two
> flags to the new space.  The rest is the same, but the first prefix
> field may be interpreted differently, depending on the flags.
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |     Type      |    Length     |L|P| Reserved  | Prefix Len 1  |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |      ...      | Prefix Len N  |            Padding            |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix 1                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix 2                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     ~ ...
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +                          Prefix N                             +
>     |                                                               |
>     +                                                               +
>     |                                                               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Some text would be needed to say how routers fill the flags, etc., and
> what to do if the LinkID prefix is one that would normally be in a PIO.
> Should we add a flag to the PIO format to indicate that that prefix is
> the LinkID, or does that prefix just end up in both a PIO and the LPO?
> There would also need to be some text in the Host Operations section
> that explains how to interpret the LinkID since in the draft at present,
> hosts don't know about the LinkID.
>
> So what do folks think?  Is this a sensible way of including an
> explicit identifier?  Is 128 bits enough for future non-prefix
> identifiers?  Is this something worth pursuing?  If so, why?
> Those that have expressed interest have said that having an explicit
> identifier is important for mesh networks, but it would be useful to
> hear more about that or if there are other reasons as well.
>
> Cheers,
> Brett.
>




From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 09:26:03 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZqtn-00049I-Fe
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 09:26:03 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12329
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 09:25:34 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV7RIDJTA69I6QGF@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 01:25:53 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C7BDD80004; Thu,
 10 Nov 2005 01:25:39 +1100 (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 149233C00B; Thu, 10 Nov 2005 01:25:38 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA9EP2f16722	for dna-list; Thu, 10 Nov 2005 01:25:02 +1100
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 jA9EP2d16716	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 01:25:02 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7RHIVXMM9A0SGU@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 01:24:58 +1100
Received: by localhost (Postfix, from userid 510)	id C0F59AB559; Thu,
 10 Nov 2005 01:24:58 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 607794FB06; Thu,
 10 Nov 2005 01:24:56 +1100 (EST)
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 51828A88; Wed,
 09 Nov 2005 15:24:54 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed,
 09 Nov 2005 15:23:58 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed,
 09 Nov 2005 15:23:57 +0100
Received: from nomadiclab.lmf.ericsson.se
 (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix)
 with ESMTP id 08EB42836; Wed, 09 Nov 2005 16:23:58 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 228481AB88C; Wed,
 09 Nov 2005 16:23:56 +0200 (EET)
Date: Wed, 09 Nov 2005 06:23:52 -0800
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: Re: [DNA] A comment on draft-pentland-dna-protocol3-00.txt
In-reply-to: <437016D0.5060606@ericsson.com>
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: <43720678.3040107@ericsson.com>
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.7 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
References: <436E0550.2080803@tm.uka.de> <436E0F1C.2060804@ericsson.com>
 <436F949F.3090204@ericsson.com> <436F9FB9.2090706@eng.monash.edu.au>
 <437016D0.5060606@ericsson.com>
X-OriginalArrivalTime: 09 Nov 2005 14:23:57.0918 (UTC)
 FILETIME=[38D30FE0:01C5E539]
Content-Transfer-Encoding: 7BIT

Tero Kauppinen (JO/LMF) wrote:
> Brett Pentland wrote:
> 
>> Hi Tero,
>>
>> I'm not sure about that one.  If the host has been previously assigned
>> an address using DHCP, then it could easily extract a prefix from that
>> to use as a landmark.  The problem would be how the routers found out
>> about the prefixes.  I guess they have to know about them but I'm not
>> sure how DNA would be supposed to access them.  Would it be reasonable
>> to take them straight from the routing table?  I don't know if that's
>> a good idea.  
> 
> 
> Maybe reasonable from programming point of view but I'm not sure from 
> specification point of view.
> 
> Routers could listen to DHCP messages but I'm sure if that would be a 
> good idea either.

While browsing through the DHCPv6 specification in a hope of learning 
more, I realized that the DHCP advertisement message can also be sent 
directly to the client and thus the router "can't" listen to these 
messages. Not that it was a good idea in the first place anyway.

I'm not even sure if this issue is worth putting effort on, because I 
think it's once again one of those corner cases where the network has 
not been configured in an optimal way (Erik's mail) but still an 
optimization mechanism (DNA) would be applied.

/Tero



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 13:27:58 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZuft-0007GQ-Se
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 13:27:58 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28047
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 13:27:30 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV7ZYBEQGG9A1A49@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 05:27:37 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C53B780003; Thu,
 10 Nov 2005 05:27:34 +1100 (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 6A1F93C00E; Thu, 10 Nov 2005 05:27:34 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA9INbu19772	for dna-list; Thu, 10 Nov 2005 05:23:37 +1100
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 jA9INad19768	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 05:23:36 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV7ZTANWHE9I6SYT@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 05:23:32 +1100
Received: by localhost (Postfix, from userid 510)	id 1D1F1AB542; Thu,
 10 Nov 2005 05:23:32 +1100 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id DB7B24FB02	for <dna@eng.monash.edu.au>; Thu,
 10 Nov 2005 05:23:30 +1100 (EST)
Received: from redwood.research.panasonic.com
 (www.research.panasonic.com [150.169.3.2])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with ESMTP id jA9INTr1008326	for <dna@eng.monash.edu.au>; Wed,
 09 Nov 2005 13:23:29 -0500
Received: from redwood.research.panasonic.com
 (birch.research.pansonic.com [150.169.3.2])	by testing.research.panasonic.com
 (Postfix) with ESMTP id 5ADBE1EECED	for <dna@eng.monash.edu.au>; Wed,
 09 Nov 2005 13:11:37 -0500 (EST)
Received: from pintlmail.MITL.Research.Panasonic.COM
	(pintlmail.mitl.research.panasonic.com [150.169.1.62])
 by	redwood.research.panasonic.com (Postfix) with ESMTP id 51B241EEC99for
	<dna@eng.monash.edu.au>; Wed, 09 Nov 2005 13:11:37 -0500 (EST)
Received: from [209.52.105.111] by
	pintlmail.MITL.Research.Panasonic.COM(mshttpd); Wed, 09 Nov 2005 13:23:29 -0500
Date: Wed, 09 Nov 2005 13:23:29 -0500
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: [DNA] MLD JOIN Questions?
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Message-id: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:21 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Content-Transfer-Encoding: 7BIT

Before I forget, I just wanted to capture the questions and post them. The questions are:

1) When should the host do MLD join solicited node multicast group(s)?
  - After marking the IPv6 addresses as optimistic, or
  - Just before sending RS message or
  - someother time

2) Do we have to make any recommendation regarding MLD joins when layer-2 hints are received whether there is a link change or not? (due to the presence snooping switches)

Please comment.

thanks,
Sathya




From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 15:11:35 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZwIB-00064y-1D
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 15:11:35 -0500
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05614
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 15:11:06 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV83KHIDJI9I6KTV@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 07:11:09 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 88BAC80005; Thu,
 10 Nov 2005 07:10:57 +1100 (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 384D63C00B; Thu, 10 Nov 2005 07:10:57 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jA9KAMf21080	for dna-list; Thu, 10 Nov 2005 07:10:22 +1100
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 jA9KAMd21076	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 07:10:22 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV83JLXFRY9ASQCH@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 07:10:15 +1100
Received: by localhost (Postfix, from userid 510)	id 70EB4AB542; Thu,
 10 Nov 2005 07:10:15 +1100 (EST)
Received: from borg.st.net.au (zorg.st.net.au [203.16.233.9])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 47A754FB02	for
 <dna@eng.monash.edu.au>; Thu, 10 Nov 2005 07:10:14 +1100 (EST)
Received: from localhost (localhost [127.0.0.1])	by borg.st.net.au (Postfix)
 with ESMTP id 58B00394E9E	for <dna@eng.monash.edu.au>; Thu,
 10 Nov 2005 06:10:13 +1000 (EST)
Received: from borg.st.net.au ([203.16.233.9])
	by localhost (borg.st.net.au [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 16276-09 for <dna@eng.monash.edu.au>; Thu,
 10 Nov 2005 06:10:13 +1000 (EST)
Received: from anchovy.zoic.org
 (static-2.241.240.220.dsl.comindico.com.au [220.240.241.2])
	by borg.st.net.au (Postfix) with ESMTP id C9A04394E7A	for
 <dna@eng.monash.edu.au>; Thu, 10 Nov 2005 06:10:12 +1000 (EST)
Received: by anchovy.zoic.org (Postfix, from userid 1000)	id 1A3347079FD; Thu,
 10 Nov 2005 07:09:16 +1100 (EST)
X-URL: http://zoic.org/sharkey/
Date: Thu, 10 Nov 2005 07:09:15 +1100
From: "Nick 'Sharkey' Moore" <sharkey@zoic.org>
Subject: Re: [DNA] Comments on draft-pentland-dna-protocol3-00.txt
In-reply-to: <4370551D.2030108@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: DNA <dna@eng.monash.edu.au>
Message-id: <20051109200915.GA1842@zoic.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.5.9i
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at st.net.au
References: <436E0550.2080803@tm.uka.de> <4370551D.2030108@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

On 2005-11-08, Brett Pentland wrote:
> 
> In order to get a fast response, we need oDAD at least for the
> link-local address.  Are you talking about, say a global address
> that is using DAD?  I guess such an address should remain tentative
> and then if link change is detected, DAD should be reinitiated.

OptiDAD-06 3.1:
|
| * Optimistic DAD SHOULD only be used when the implementation is aware
| that the address is based on a most likely unique interface
| identifier (such as in [RFC2464]), generated randomly [RFC3041]
| or by a well-distributed hash function [RFC3972] or assigned by
| DHCPv6 [RFC3315].  Optimistic DAD SHOULD NOT be used for
| manually entered addresses.

So there may indeed be Tentative and Optimistic addresses on the same
host at the same time ...

-----Nick



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 20:41:47 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ea1Rj-0007cE-HZ
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 20:41:47 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25240
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 20:41:19 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8F2982OG9A17TV@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 12:39:58 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id AC8CE80004; Thu,
 10 Nov 2005 12:39:51 +1100 (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 6A2F23C004; Thu, 10 Nov 2005 12:39:51 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAA1dDw25178	for dna-list; Thu, 10 Nov 2005 12:39:13 +1100
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 jAA1dDd25174	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 12:39:13 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV8F1DRC3W9I6SRR@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 12:39:09 +1100
Received: by localhost (Postfix, from userid 510)	id 9939180002; Thu,
 10 Nov 2005 12:39:09 +1100 (EST)
Received: from laposte.rennes.enst-bretagne.fr
 (laposte.rennes.enst-bretagne.fr [192.44.77.17])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id BF1203C00B	for <dna@eng.monash.edu.au>; Thu,
 10 Nov 2005 12:39:07 +1100 (EST)
Received: from l1.rennes.enst-bretagne.fr
 (l1.rennes.enst-bretagne.fr [192.44.77.3])	by laposte.rennes.enst-bretagne.fr
 (8.11.6p2/8.11.6/2003.04.01) with ESMTP id jAA1cwu10485	for
 <dna@eng.monash.edu.au>; Thu, 10 Nov 2005 02:38:58 +0100
Received: from [209.52.106.196] (pp106-196.bctel.ca [209.52.106.196])
	(authenticated bits=0)	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1)
 with ESMTP id jAA1cuSC028647
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <dna@eng.monash.edu.au>; Thu, 10 Nov 2005 02:38:58 +0100
Date: Thu, 10 Nov 2005 02:38:43 +0100
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Subject: [DNA] SEND and router BCP
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <2ECEFC75-AF77-437D-8F0D-0F3E4270A894@enst-bretagne.fr>
MIME-version: 1.0
X-Mailer: Apple Mail (2.733)
Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7BIT

Hi,

We would like to remove the following sentence from draft-ietf-dna- 
routers-01.txt

"Routers supporting DNA SHOULD provide secured  router discovery  
services using SEND [4]."

While the section 4.1 gives hints or advices on how to use SEND for  
DNA, we believe that DNA does not have to recommend to use SEND.

Any objections?

Nicolas



From dna-owner@webcamserver.eng.monash.edu.au Wed Nov 09 22:22:22 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ea314-0008Ig-E1
	for dna-archive@megatron.ietf.org; Wed, 09 Nov 2005 22:22:22 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01223
	for <dna-archive@lists.ietf.org>; Wed, 9 Nov 2005 22:21:52 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8IMCGNQO9A1C40@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 14:21:38 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 20428AB544; Thu,
 10 Nov 2005 14:21:34 +1100 (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 C6F084FB07; Thu, 10 Nov 2005 14:21:33 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAA3KTY26421	for dna-list; Thu, 10 Nov 2005 14:20:29 +1100
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 jAA3KSd26417	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 14:20:28 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8IKPYO1C9AST4Y@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 14:20:15 +1100
Received: by localhost (Postfix, from userid 510)	id 8D55D80003; Thu,
 10 Nov 2005 14:20:15 +1100 (EST)
Received: from mout.perfora.net (mout.perfora.net [217.160.230.40])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 1D25F3C00A	for
 <dna@eng.monash.edu.au>; Thu, 10 Nov 2005 14:20:14 +1100 (EST)
Received: from [209.52.109.216] (helo=Alperyegin)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1Ea2yv30pv-0003hy; Wed, 09 Nov 2005 22:20:12 -0500
Date: Thu, 10 Nov 2005 05:20:05 +0200
From: Alper Yegin <alper.yegin@yegin.org>
Subject: RE: [DNA] SEND and router BCP
In-reply-to: <2ECEFC75-AF77-437D-8F0D-0F3E4270A894@enst-bretagne.fr>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'Nicolas Montavont'" <nicolas.montavont@enst-bretagne.fr>,
        "'Dna'" <dna@eng.monash.edu.au>
Message-id: <000e01c5e5a5$a93fea70$d86d34d1@Alperyegin>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Provags-ID: perfora.net abuse@perfora.net
 login:abf7a4bb310ea4dfc9b6841113e2970f
Content-Transfer-Encoding: 7BIT


Yes, I agree. [We had discussed this point in Paris.]

Alper



> -----Original Message-----
> From: owner-dna@ecselists.eng.monash.edu.au [mailto:owner-
> dna@ecselists.eng.monash.edu.au] On Behalf Of Nicolas Montavont
> Sent: Thursday, November 10, 2005 3:39 AM
> To: Dna
> Subject: [DNA] SEND and router BCP
> 
> Hi,
> 
> We would like to remove the following sentence from draft-ietf-dna-
> routers-01.txt
> 
> "Routers supporting DNA SHOULD provide secured  router discovery
> services using SEND [4]."
> 
> While the section 4.1 gives hints or advices on how to use SEND for
> DNA, we believe that DNA does not have to recommend to use SEND.
> 
> Any objections?
> 
> Nicolas




From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 10 02:52:13 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ea7EC-0003Hv-Sv
	for dna-archive@megatron.ietf.org; Thu, 10 Nov 2005 02:52:13 -0500
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14441
	for <dna-archive@lists.ietf.org>; Thu, 10 Nov 2005 02:51:43 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LV8S0JA6R89I6X1V@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 18:50:27 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D46E580003; Thu,
 10 Nov 2005 18:50:18 +1100 (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 8D1E63C003; Thu, 10 Nov 2005 18:50:18 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAA7nOt29649	for dna-list; Thu, 10 Nov 2005 18:49:24 +1100
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 jAA7nNd29645	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 18:49:23 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8RXZYJO09A1JDY@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 18:49:03 +1100
Received: by localhost (Postfix, from userid 510)	id 3806CAB542; Thu,
 10 Nov 2005 18:49:03 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(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 52B544FB02; Thu, 10 Nov 2005 18:48:59 +1100 (EST)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps	id 1Ea7Ay-0007pb-6G; Thu,
 10 Nov 2005 08:48:55 +0100
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by irams1.ira.uni-karlsruhe.de with esmtpsa	id 1Ea7Ax-0001ke-PD; Thu,
 10 Nov 2005 08:48:51 +0100
Date: Thu, 10 Nov 2005 08:48:51 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] Comments on draft-pentland-dna-protocol3-00.txt
In-reply-to: <4370551D.2030108@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>
Cc: DNA <dna@eng.monash.edu.au>,
        Suresh Krishnan <suresh.krishnan@ericsson.com>,
        Mark Doll <doll@tm.uka.de>
Message-id: <4372FB63.3080905@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
References: <436E0550.2080803@tm.uka.de> <4370551D.2030108@eng.monash.edu.au>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA14441

Hey Brett.

>>> o  No addresses should be in the "Tentative" state, since this
>>> state is unnecessary for nodes that support optimistic Duplicate
>>> Address Detection.
>>=20
>>=20
>> I don't think this is true.  The draft only says (in section
>> 6.2.6.1) that the host must *support* OptiDAD, not that it must use
>> it.  E.g., the host may use OptiDAD for the link-local address and
>> a Mobile IPv6 care-of address, but not for other addresses.  (I'm
>> not saying there would be a good reason for doing this.  I'm just
>> saying this may happen according to the requirements set forth in
>> section 6.2.6.1.)
>=20
>=20
 > In order to get a fast response, we need oDAD at least for the
 > link-local address. [....]

Right, we need OptiDAD for the link-local address.  But I think section
6.2.6.1 ("Duplicate Address Detection") should be explicit on this.
Specifically, how about...

OLD
    A DNA host MUST support optimistic Duplicate Address Detection [6]
    for autoconfiguring unicast link local addresses.  If a DNA host uses
    address autoconfiguration [7] for global unicast addresses, the DNA
    host MUST support optimistic Duplicate Address Detection for
    autoconfiguring global unicast addresses.

NEW
    A DNA host MUST support *and it MUST use* optimistic Duplicate
    Address Detection [6] for autoconfiguring unicast link local
    addresses.  If a DNA host uses address autoconfiguration [7] for
    global unicast addresses, the DNA host MUST support [and it MUST use]
    optimistic Duplicate Address Detection for autoconfiguring global
    unicast addresses.

The first modification (which I put within stars) is necessary given=20
that the DNA protocol wouldn't be of much use without it.

The second modification (which I put in square brackets) is not=20
necessary IMO and should be left up to the DNA host.  After all, you do=20
not know for which purpose the global unicast address is meant.  If it's=20
a Mobile IPv6 care-of address, OptiDAD would surely be preferable.  If=20
it's a less important address---e.g., a statelessly auto-configured=20
address on the home link that comes in addition to a statefully=20
configured home address---then OptiDAD may not be necessary (although=20
there would be no good reason for using standard DAD instead either).

Basically, there are three options:
- Leave it up to the DNA host.
- Explicitly differentiate between global unicast addresses where=20
OptiDAD is required and unicast addresses where it is not.
- Require OptiDAD for all unicast addresses.

Option 3 would interfere with stateful address configuration (DHCPv6).=20
Option 2 would probably make the draft a whole lot more complicated,=20
which is not so good either.  I'd go with option 1 therefore.

 > [....]    Are you talking about, say a global address that
 > is using DAD?  [....]

Yes, see above.

 > [....]   I guess such an address should remain tentative and
 > then if link change is detected, DAD should be reinitiated. [....]

It should be something equivalent to the case of optimistic addresses.=20
Something like...

    o  Addresses in the "Tentative" state remain in the "Tentative"
       state, but the host defers sending out a pending NS if this has
       not yet been sent already.  If the host later concludes that a
       change in IP attachment occurred, it will have to re-initiate
       Duplicate Address Detection on the new link.

 > [....]                                                      If it's
 > the link-local address itself that is doing full DAD, the host has to
 > either wait until DAD completes, or use the unspecified address for a
 > source address, and wait for a delayed multicast RA. [....]

Hmm, but I would really require link-local addresses to be configured=20
through OptiDAD.  After all, this protocol is about *fast* DNA.  So, if=20
a host claims to be DNA-compliant, it should behave that way.  ;)  That=20
includes using OptiDAD instead of standard DAD f=FCr link-local addresses.

 >> It's important to re-send MLD Reports for all solicited-nodes
 >> addresses even if the host did not change IP attachment, because
 >> the host may have moved to a different side of a snooping switch.
 >> Failure to send MLD Reports upon an L2 move that was not an L3 move
 >> could cause the host not to receive further multicast messages
 >> (which could be a disaster for things like DAD).
 >
 >
 > It's definitely important to send the MLD reports and we need some
 > text for that.  I don't think they necessarily have to go out first.
 > I thought that when we had this discussion before Paris, we decided
 > that it was ok to send the RS first.  It will have a TSLLAO in it and
 > so no NS/NA is needed for the router to send back a unicast RA.  Does
 > that sound right?

Oh yes, certainly, you can send out the RS first.  The MLD Report=20
becomes important during address configuration, not during router discove=
ry.

And here is some proposed text.  From section 6.2.6.2:

OLD
    When the host receives unicast or multicast RAs from the router, if
    the host determines from the received RAs that it has moved to a new
    link, the host MUST immediately move all unicast global addresses to
    the "Deprecated" state and configure new addresses using the subnet
    prefixes obtained from the RA.  For all unicast link local addresses,
    the host MUST initiate NS signaling for optimistic Duplicate Address
    Detection to confirm the uniqueness of the unicast link local
    addresses on the new link.

NEW
    When the host receives unicast or multicast RAs from the router, if
    the host determines from the received RAs that it has moved to a new
    link, the host MUST immediately move all unicast global addresses to
    the "Deprecated" state and configure new addresses using the subnet
    prefixes obtained from the RA.  For all unicast link local addresses,
    the host MUST transmit an MLD Report message for the corresponding
    solicited-nodes multicast address and then initiate NS signaling for
    optimistic Duplicate Address Detection to confirm the uniqueness of
    the unicast link local addresses on the new link.

Furthermore, also from section 6.2.6.2:

OLD
    If the host determines from the received RAs that it has not moved to
    a new link (i.e. the link has not changed) and the previous state of
    an address was "Optimistic", then the host MUST send an NS to confirm
    that the address is unique on the link.  This is required because
    optimistic Duplicate Address Detection may not have completed on the
    previous point of attachment, so the host may not have confirmed
    address uniqueness.  If the previous state of an address was
    "Preferred", whether or not the host initiates optimistic Duplicate
    Address Detection depends on the configurable DNASameLinkDADFlag
    flag.  A host MUST forgo sending an NS to confirm uniqueness if the
    value of the DNASameLinkDAD flag is False.  If, however, the
    DNASameLinkDAD flag is True, the host MUST perform optimistic
    duplicate address detection on its unicast link local and unicast
    global addresses to determine address uniqueness.

NEW
    If the host determines from the received RAs that it has not moved to
    a new link (i.e. the link has not changed), the host must still send
    MLD Report messages for all solicited-nodes multicast addresses that
    it is listening to.  Retransmission of the MLD Report messages
    ensures that the host continues to receive packets sent to one of
    these solicited-nodes multicast addresses in case it has moved to
    a different side of an MLD snooping switch on the same link.
    Furthermore, if the previous state of
    an address was "Optimistic", then the host MUST send an NS to confirm
    that the address is unique on the link.  This is required because
    optimistic Duplicate Address Detection may not have completed on the
    previous point of attachment, so the host may not have confirmed
    address uniqueness.  Similarly, if the previous state of
    an address was "Tentative", then the host MUST send an NS to confirm
    that the address is unique on the link.  If the previous state of an
    address was
    "Preferred", whether or not the host initiates optimistic Duplicate
    Address Detection depends on the configurable DNASameLinkDADFlag
    flag.  A host MUST forgo sending an NS to confirm uniqueness if the
    value of the DNASameLinkDAD flag is False.  If, however, the
    DNASameLinkDAD flag is True, the host MUST perform optimistic
    duplicate address detection on its unicast link local address and it
    MUST perform either duplicate address detection or optimistic
    duplicate address detection unicast on its global addresses to
    determine address uniqueness.

Note that I also added text to handle addresses in "Tentative" state,=20
which was not dealt with so far.  See our discussion on addresses in=20
"Tentative" state above.

Regards,
- Christian

--=20
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Brett Pentland wrote:
> Hi Christian,
>=20
> Sorry, somehow I missed replying to this one earlier.
>=20
> Christian Vogt wrote:
>=20
>> Hi DT members,
>>=20
>> I read draft-pentland-dna-protocol3-00.txt.  I think the document
>> is very solid!  It provides a good view on the problem of efficient
>>  movement detection and gives you a clear understanding of how the=20
>> protocol works.
>>=20
>> Nevertheless, a couple of comments from my side are below.
>>=20
>> Section 6.2.6.2:
>>=20
>>=20
>>> o  Addresses in the "Optimistic" state remain in the "Optimistic"
>>>  state, but the host defers sending out an NS to initiate
>>> Duplicate Address Detection.
>>=20
>>=20
>>=20
>> Note that OptiDAD may have already been in progress when the node
>> moved, so the process may have already been "inititated".  Also,
>> OptiDAD allows you to send more than one NS for increased
>> robustness, whereas the text above suggests that there is always a
>> single NS.
>>=20
>> Maybe, the text should read something like:
>>=20
>> o  Addresses in the "Optimistic" state remain in the "Optimistic"=20
>> state, but the host defers sending out a pending NS if this has not
>> yet been sent already.  If the host later concludes that a change
>> in IP attachment occurred, it will have to re-initiate Optimistic
>> Duplicate Address Detection on the new link.
>=20
>=20
> Sounds good.
>=20
>>=20
>>=20
>>> o  No addresses should be in the "Tentative" state, since this
>>> state is unnecessary for nodes that support optimistic Duplicate
>>> Address Detection.
>>=20
>>=20
>>=20
>> I don't think this is true.  The draft only says (in section
>> 6.2.6.1) that the host must *support* OptiDAD, not that it must use
>> it.  E.g., the host may use OptiDAD for the link-local address and
>> a Mobile IPv6 care-of address, but not for other addresses.  (I'm
>> not saying there would be a good reason for doing this.  I'm just
>> saying this may happen according to the requirements set forth in
>> section 6.2.6.1.)
>=20
>=20
> In order to get a fast response, we need oDAD at least for the=20
> link-local address.  Are you talking about, say a global address that
> is using DAD?  I guess such an address should remain tentative and
> then if link change is detected, DAD should be reinitiated. If it's
> the link-local address itself that is doing full DAD, the host has to
> either wait until DAD completes, or use the unspecified address for a
> source address, and wait for a delayed multicast RA.
>=20
>>=20
>>=20
>>> In order to perform the DNA transaction, the DNA host SHOULD
>>> select one of the unicast link local addresses that was in the
>>> "Preferred" state prior to switching to "Optimistic" and utilize
>>> that as the source address on the DNA RS.  If the host had no
>>> "Preferred" unicast link local address but did have an address in
>>> the "Optimistic" state, it MUST utilize such an address as the
>>> source address.  If the host currently has no unicast link local
>>> addresses, it MUST construct one and put it into the "Optimistic"
>>> state and note this address as having been in the "Optimistic"
>>> state previously, but defer sending the NS to confirm.  Note that
>>> the presence of a duplicate unicast link local address on the
>>> link will not interfere with the ability of the link to route a
>>> unicast DNA RA from the router back to the host nor will it
>>> result in corruption of the router's neighbor cache, because the
>>> TSLLA option is included in the RS and is utilized by the router
>>> on the RA frame without changing the neighbor cache.
>>=20
>>=20
>>=20
>> This paragraph misses that an MLD Report must be sent for the=20
>> corresponding solicited-nodes multicast address prior to sending
>> the NS.
>>=20
>> RFC2462bis introduces a delay for this MLD Report in oder to=20
>> de-synchronize mulitple hosts configuring simultaneously.  But
>> since the DNA Protocol 3 is tailored to mobile nodes, and mobility
>> already serves to sufficiently de-synchronize operations IMO, you
>> should be fine in sending the MLD Report immediately.
>>=20
>>=20
>>> When the host receives unicast or multicast RAs from the router,
>>> if the host determines from the received RAs that it has moved to
>>> a new link, the host MUST immediately move all unicast global
>>> addresses to the "Deprecated" state and configure new addresses
>>> using the subnet prefixes obtained from the RA.  For all unicast
>>> link local addresses, the host MUST initiate NS signaling for
>>> optimistic Duplicate Address Detection to confirm the uniqueness
>>> of the unicast link local addresses on the new link.
>>=20
>>=20
>>=20
>> Same here:  The host should register its solicited-nodes addresses=20
>> before it starts sending NS for OptiDAD.
>>=20
>>=20
>>> If the host determines from the received RAs that it has not
>>> moved to a new link (i.e. the link has not changed) ....
>>=20
>>=20
>>=20
>> It's important to re-send MLD Reports for all solicited-nodes
>> addresses even if the host did not change IP attachment, because
>> the host may have moved to a different side of a snooping switch.
>> Failure to send MLD Reports upon an L2 move that was not an L3 move
>> could cause the host not to receive further multicast messages
>> (which could be a disaster for things like DAD).
>=20
>=20
> It's definitely important to send the MLD reports and we need some=20
> text for that.  I don't think they necessarily have to go out first.=20
> I thought that when we had this discussion before Paris, we decided
> that it was ok to send the RS first.  It will have a TSLLAO in it and
> so no NS/NA is needed for the router to send back a unicast RA.  Does
> that sound right?
>=20
> Brett.




From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 10 03:33:15 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ea7ru-0007p9-SC
	for dna-archive@megatron.ietf.org; Thu, 10 Nov 2005 03:33:15 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16740
	for <dna-archive@lists.ietf.org>; Thu, 10 Nov 2005 03:32:41 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8TGPG9KI9ASQ8L@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 10 Nov 2005 19:32:30 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6EAEAAB543; Thu,
 10 Nov 2005 19:32:22 +1100 (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 1067D4FB05; Thu, 10 Nov 2005 19:32:22 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAA8WBm30148	for dna-list; Thu, 10 Nov 2005 19:32:11 +1100
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 jAA8WAd30144	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 10 Nov 2005 19:32:10 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LV8TGCEKQE9ASQ8L@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 10 Nov 2005 19:32:05 +1100
Received: by localhost (Postfix, from userid 510)	id 33FE6AB543; Thu,
 10 Nov 2005 19:32:05 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(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 888274FB0E; Thu, 10 Nov 2005 19:32:02 +1100 (EST)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps	id 1Ea7qe-0000iU-7c; Thu,
 10 Nov 2005 09:31:59 +0100
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by irams1.ira.uni-karlsruhe.de with esmtpsa	id 1Ea7qd-0001XO-Iv; Thu,
 10 Nov 2005 09:31:55 +0100
Date: Thu, 10 Nov 2005 09:31:54 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] Comments on draft-pentland-dna-protocol3-00.txt
In-reply-to: <4372FB63.3080905@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>,
        DNA <dna@eng.monash.edu.au>,
        Suresh Krishnan <suresh.krishnan@ericsson.com>,
        Mark Doll <doll@tm.uka.de>
Message-id: <4373057A.6070306@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
References: <436E0550.2080803@tm.uka.de> <4370551D.2030108@eng.monash.edu.au>
 <4372FB63.3080905@tm.uka.de>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA16740

Hi all,

a quick follow-up; Mark Doll pointed me to this:

> NEW (section 6.2.6.2)
 > If the host determines from the received RAs that it has not
> moved to a new link (i.e. the link has not changed), the host must
> still send MLD Report messages for all solicited-nodes multicast
> addresses that it is listening to.  Retransmission of the MLD Report
> messages ensures that the host continues to receive packets sent to
> one of these solicited-nodes multicast addresses in case it has moved
> to a different side of an MLD snooping switch on the same link.=20
> Furthermore, if the previous state of an address was "Optimistic",
> then the host MUST send an NS to confirm that the address is unique
> on the link.  This is required because optimistic Duplicate Address
> Detection may not have completed on the previous point of attachment,
> so the host may not have confirmed address uniqueness.  Similarly, if
> the previous state of an address was "Tentative", then the host MUST
> send an NS to confirm that the address is unique on the link.  If the
> previous state of an address was "Preferred", whether or not the host
> initiates optimistic Duplicate Address Detection depends on the
> configurable DNASameLinkDADFlag flag.  A host MUST forgo sending an
> NS to confirm uniqueness if the value of the DNASameLinkDAD flag is
> False.  If, however, the DNASameLinkDAD flag is True, the host MUST
> perform optimistic duplicate address detection on its unicast link
> local address and it MUST perform either duplicate address detection
> or optimistic duplicate address detection unicast on its global
> addresses to determine address uniqueness.

s/This is required because optimistic Duplicate Address Detection may=20
not have completed on the previous point of attachment, so the host may=20
not have confirmed address uniqueness./This is required because=20
optimistic Duplicate Address Detection did not complete on the previous=20
point of attachment, so the host has not yet confirmed address uniqueness=
./

After all, when the address is still in "Optimistic" state, then address=20
uniqueness did not fully complete yet (although we may already have sent=20
the NS and listened for responses for 0.999 seconds).

Regards,
- Christian

--=20
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Christian Vogt wrote:
> Hey Brett.
>=20
>>>> o  No addresses should be in the "Tentative" state, since this=20
>>>> state is unnecessary for nodes that support optimistic
>>>> Duplicate Address Detection.
>>>=20
>>>=20
>>>=20
>>> I don't think this is true.  The draft only says (in section=20
>>> 6.2.6.1) that the host must *support* OptiDAD, not that it must
>>> use it.  E.g., the host may use OptiDAD for the link-local
>>> address and a Mobile IPv6 care-of address, but not for other
>>> addresses.  (I'm not saying there would be a good reason for
>>> doing this.  I'm just saying this may happen according to the
>>> requirements set forth in section 6.2.6.1.)
>>=20
>>=20
>>=20
>> In order to get a fast response, we need oDAD at least for the=20
>> link-local address. [....]
>=20
> Right, we need OptiDAD for the link-local address.  But I think
> section 6.2.6.1 ("Duplicate Address Detection") should be explicit on
> this. Specifically, how about...
>=20
> OLD A DNA host MUST support optimistic Duplicate Address Detection
> [6] for autoconfiguring unicast link local addresses.  If a DNA host
> uses address autoconfiguration [7] for global unicast addresses, the
> DNA host MUST support optimistic Duplicate Address Detection for=20
> autoconfiguring global unicast addresses.
>=20
> NEW A DNA host MUST support *and it MUST use* optimistic Duplicate=20
> Address Detection [6] for autoconfiguring unicast link local=20
> addresses.  If a DNA host uses address autoconfiguration [7] for=20
> global unicast addresses, the DNA host MUST support [and it MUST use]
>  optimistic Duplicate Address Detection for autoconfiguring global=20
> unicast addresses.
>=20
> The first modification (which I put within stars) is necessary given
>  that the DNA protocol wouldn't be of much use without it.
>=20
> The second modification (which I put in square brackets) is not=20
> necessary IMO and should be left up to the DNA host.  After all, you
> do not know for which purpose the global unicast address is meant.
> If it's a Mobile IPv6 care-of address, OptiDAD would surely be
> preferable.  If it's a less important address---e.g., a statelessly
> auto-configured address on the home link that comes in addition to a
> statefully configured home address---then OptiDAD may not be
> necessary (although there would be no good reason for using standard
> DAD instead either).
>=20
> Basically, there are three options: - Leave it up to the DNA host. -
> Explicitly differentiate between global unicast addresses where=20
> OptiDAD is required and unicast addresses where it is not. - Require
> OptiDAD for all unicast addresses.
>=20
> Option 3 would interfere with stateful address configuration
> (DHCPv6). Option 2 would probably make the draft a whole lot more
> complicated, which is not so good either.  I'd go with option 1
> therefore.
>=20
>> [....]    Are you talking about, say a global address that is using
>> DAD?  [....]
>=20
> Yes, see above.
>=20
>> [....]   I guess such an address should remain tentative and then
>> if link change is detected, DAD should be reinitiated. [....]
>=20
> It should be something equivalent to the case of optimistic
> addresses. Something like...
>=20
> o  Addresses in the "Tentative" state remain in the "Tentative"=20
> state, but the host defers sending out a pending NS if this has not
> yet been sent already.  If the host later concludes that a change in
> IP attachment occurred, it will have to re-initiate Duplicate Address
> Detection on the new link.
>=20
>> [....]                                                      If it's
>>  the link-local address itself that is doing full DAD, the host has
>> to either wait until DAD completes, or use the unspecified address
>> for a source address, and wait for a delayed multicast RA. [....]
>=20
> Hmm, but I would really require link-local addresses to be configured
>  through OptiDAD.  After all, this protocol is about *fast* DNA.  So,
> if a host claims to be DNA-compliant, it should behave that way.  ;)
> That includes using OptiDAD instead of standard DAD f=FCr link-local
> addresses.
>=20
>>> It's important to re-send MLD Reports for all solicited-nodes=20
>>> addresses even if the host did not change IP attachment, because=20
>>> the host may have moved to a different side of a snooping switch.
>>>  Failure to send MLD Reports upon an L2 move that was not an L3
>>> move could cause the host not to receive further multicast
>>> messages (which could be a disaster for things like DAD).
>>=20
>>=20
>> It's definitely important to send the MLD reports and we need some=20
>> text for that.  I don't think they necessarily have to go out
>> first. I thought that when we had this discussion before Paris, we
>> decided that it was ok to send the RS first.  It will have a TSLLAO
>> in it and so no NS/NA is needed for the router to send back a
>> unicast RA.  Does that sound right?
>=20
> Oh yes, certainly, you can send out the RS first.  The MLD Report=20
> becomes important during address configuration, not during router=20
> discovery.
>=20
> And here is some proposed text.  From section 6.2.6.2:
>=20
> OLD When the host receives unicast or multicast RAs from the router,
> if the host determines from the received RAs that it has moved to a
> new link, the host MUST immediately move all unicast global addresses
> to the "Deprecated" state and configure new addresses using the
> subnet prefixes obtained from the RA.  For all unicast link local
> addresses, the host MUST initiate NS signaling for optimistic
> Duplicate Address Detection to confirm the uniqueness of the unicast
> link local addresses on the new link.
>=20
> NEW When the host receives unicast or multicast RAs from the router,
> if the host determines from the received RAs that it has moved to a
> new link, the host MUST immediately move all unicast global addresses
> to the "Deprecated" state and configure new addresses using the
> subnet prefixes obtained from the RA.  For all unicast link local
> addresses, the host MUST transmit an MLD Report message for the
> corresponding solicited-nodes multicast address and then initiate NS
> signaling for optimistic Duplicate Address Detection to confirm the
> uniqueness of the unicast link local addresses on the new link.
>=20
> Furthermore, also from section 6.2.6.2:
>=20
> OLD If the host determines from the received RAs that it has not
> moved to a new link (i.e. the link has not changed) and the previous
> state of an address was "Optimistic", then the host MUST send an NS
> to confirm that the address is unique on the link.  This is required
> because optimistic Duplicate Address Detection may not have completed
> on the previous point of attachment, so the host may not have
> confirmed address uniqueness.  If the previous state of an address
> was "Preferred", whether or not the host initiates optimistic
> Duplicate Address Detection depends on the configurable
> DNASameLinkDADFlag flag.  A host MUST forgo sending an NS to confirm
> uniqueness if the value of the DNASameLinkDAD flag is False.  If,
> however, the DNASameLinkDAD flag is True, the host MUST perform
> optimistic duplicate address detection on its unicast link local and
> unicast global addresses to determine address uniqueness.
>=20
> NEW If the host determines from the received RAs that it has not
> moved to a new link (i.e. the link has not changed), the host must
> still send MLD Report messages for all solicited-nodes multicast
> addresses that it is listening to.  Retransmission of the MLD Report
> messages ensures that the host continues to receive packets sent to
> one of these solicited-nodes multicast addresses in case it has moved
> to a different side of an MLD snooping switch on the same link.=20
> Furthermore, if the previous state of an address was "Optimistic",
> then the host MUST send an NS to confirm that the address is unique
> on the link.  This is required because optimistic Duplicate Address
> Detection may not have completed on the previous point of attachment,
> so the host may not have confirmed address uniqueness.  Similarly, if
> the previous state of an address was "Tentative", then the host MUST
> send an NS to confirm that the address is unique on the link.  If the
> previous state of an address was "Preferred", whether or not the host
> initiates optimistic Duplicate Address Detection depends on the
> configurable DNASameLinkDADFlag flag.  A host MUST forgo sending an
> NS to confirm uniqueness if the value of the DNASameLinkDAD flag is
> False.  If, however, the DNASameLinkDAD flag is True, the host MUST
> perform optimistic duplicate address detection on its unicast link
> local address and it MUST perform either duplicate address detection
> or optimistic duplicate address detection unicast on its global
> addresses to determine address uniqueness.
>=20
> Note that I also added text to handle addresses in "Tentative" state,
>  which was not dealt with so far.  See our discussion on addresses in
>  "Tentative" state above.
>=20
> Regards, - Christian





From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 11:59:45 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EbhgH-0000jo-86
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 11:59:45 -0500
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04500
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 11:59:11 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVEWCU291M9I7GI0@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 03:59:37 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0A5A380003; Tue,
 15 Nov 2005 03:59:31 +1100 (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 B8BE83C003; Tue, 15 Nov 2005 03:59:30 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAEGwPH18905	for dna-list; Tue, 15 Nov 2005 03:58:25 +1100
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 jAEGwPu18901	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 03:58:25 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVEWBFJCOC9ASS57@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 03:58:23 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2C02880002; Tue,
 15 Nov 2005 03:58:23 +1100 (EST)
Received: from [172.19.242.3]
 (vpn-student-242-3.its.monash.edu.au [172.19.242.3])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 7D4C93C00A; Tue,
 15 Nov 2005 03:58:22 +1100 (EST)
Date: Tue, 15 Nov 2005 03:58:19 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: [DNA] Some DNA Presentations online from IETF 64.
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: suresh.krishnan@ericsson.com
Message-id: <4378C22B.2090600@eng.monash.edu.au>
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.6 (Windows/20050716)
Content-Transfer-Encoding: 7BIT

Dear WG,

Here are some of the slides presented last week:

Detecting Network Attachment: Agenda and WG Status
(G. Daley, S. Krishnan).
http://www.ctie.monash.edu.au/dna/DNA64.ppt

Analysis of DNA relocation delays
(G.Daley, on behalf of C. Vogt).
http://www.ctie.monash.edu.au/dna/vogt-2005-ietf64-dna-analysis-of-ip6-relocation-delays.pdf

DNA Solution Proposal
(B.Pentland)
http://www.ctie.monash.edu.au/dna/IETF_64_-_DNA_draft-pentland-dna-protocol3-00.ppt

If you have additional presentation slides, please send them to the
chairs.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 12:00:35 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ebhh4-00013z-Lm
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 12:00:34 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04535
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 12:00:01 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVEWD02AEE9ASS57@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 03:59:43 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id E7314AB546; Tue,
 15 Nov 2005 03:59:38 +1100 (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 778514FB05; Tue, 15 Nov 2005 03:59:38 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAEGvpq18891	for dna-list; Tue, 15 Nov 2005 03:57:51 +1100
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 jAEGvou18887	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 03:57:50 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVEWAODI8A9I7GI0@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 03:57:47 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A1B3BAB559; Tue,
 15 Nov 2005 03:57:46 +1100 (EST)
Received: from [172.19.242.3]
 (vpn-student-242-3.its.monash.edu.au [172.19.242.3])
	by moe.its.monash.edu.au (Postfix) with ESMTP id CBD584FB03; Tue,
 15 Nov 2005 03:57:45 +1100 (EST)
Date: Tue, 15 Nov 2005 03:57:28 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Sathya Narayanan <sathya@research.panasonic.com>
Cc: dna@eng.monash.edu.au
Message-id: <4378C1F8.8090407@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
Content-Transfer-Encoding: 7BIT

Hi Sathya.

I've written some answers to your questions, in the rough
form of a text proposal:


Sathya Narayanan wrote:
> Before I forget, I just wanted to capture the questions and post them. The questions are:
> 
> 1) When should the host do MLD join solicited node multicast group(s)?
>   - After marking the IPv6 addresses as optimistic, or
>   - Just before sending RS message or
>   - someother time

The host SHOULD send the MLD group join report for the solicited node's
multicast group when it becomes optimistic.  Note that this may precede
transmission of the DAD NS probe by some time, although the optimistic
node's ability to receive DAD NS's is limited until it does so.

In any case, the MLD report message MUST be sent before transmission of
either an RS, otherwise responding routers may not be able to resolve
the host's link-layer address.

> 2) Do we have to make any recommendation regarding MLD joins when layer-2
 > hints are received whether there is a link change or not? (due to the
> presence snooping switches)

A host SHOULD always join MLD groups, after it receives a link-UP hint
on a new point-of-attachment.

Until it does so there is no guarantee that it can receive packets
addressed to its solicited nodes' addresses.  This means that it
may not be able to see DAD NS probes or neighbour resolution attempts
until it has done so.


Comments?

Greg



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 16:34:45 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EblyO-0007Fu-Nd
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 16:34:45 -0500
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02857
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 16:34:11 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVF5WXROGS9I7PHH@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 08:34:20 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B068BAB559; Tue,
 15 Nov 2005 08:33:48 +1100 (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 644284FB02; Tue,
 15 Nov 2005 08:33:48 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAELX7922365	for dna-list; Tue, 15 Nov 2005 08:33:07 +1100
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 jAELX6u22359	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 08:33:06 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVF5VYF7OW9ASWH1@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 08:33:01 +1100
Received: by localhost (Postfix, from userid 510)	id 606DBAB55C; Tue,
 15 Nov 2005 08:33:01 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 480A04FB0A; Tue, 15 Nov 2005 08:32:59 +1100 (EST)
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by iramx2.ira.uni-karlsruhe.de with esmtpsa	id 1EblwY-0007g1-TM; Mon,
 14 Nov 2005 22:32:55 +0100
Date: Mon, 14 Nov 2005 22:32:50 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <4378C1F8.8090407@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>,
        Sathya Narayanan <sathya@research.panasonic.com>
Cc: dna@eng.monash.edu.au
Message-id: <43790282.1030506@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
 <4378C1F8.8090407@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Sathya, hi Greg.

> The host SHOULD send the MLD group join report for the solicited
> node's multicast group when it becomes optimistic.  [...]

Note that Nick mentioned that he'll modify the OptiDAD draft so that the 
optimistic address will be available for use even before the initial NS, 
and thus the MLD report, is sent.  (See thread starting at [1].)

This would allow an RS with a TSLLAO option to be sent even before the 
mobile node joins the solicited-node multicast group corresponding to 
the optimistic address.

Does this have an impact on the DNA Protocol 3?

Regards,
- Christian


[1] http://www1.ietf.org/mail-archive/web/ipv6/current/msg05777.html

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Greg Daley wrote:
> Hi Sathya.
> 
> I've written some answers to your questions, in the rough form of a
> text proposal:
> 
> 
> Sathya Narayanan wrote:
> 
>> Before I forget, I just wanted to capture the questions and post
>> them. The questions are:
>> 
>> 1) When should the host do MLD join solicited node multicast
>> group(s)? - After marking the IPv6 addresses as optimistic, or -
>> Just before sending RS message or - someother time
> 
> 
> The host SHOULD send the MLD group join report for the solicited
> node's multicast group when it becomes optimistic.  Note that this
> may precede transmission of the DAD NS probe by some time, although
> the optimistic node's ability to receive DAD NS's is limited until it
> does so.
> 
> In any case, the MLD report message MUST be sent before transmission
> of either an RS, otherwise responding routers may not be able to
> resolve the host's link-layer address.
> 
>> 2) Do we have to make any recommendation regarding MLD joins when
>> layer-2
> 
>> hints are received whether there is a link change or not? (due to
>> the
> 
>> presence snooping switches)
> 
> 
> A host SHOULD always join MLD groups, after it receives a link-UP
> hint on a new point-of-attachment.
> 
> Until it does so there is no guarantee that it can receive packets 
> addressed to its solicited nodes' addresses.  This means that it may
> not be able to see DAD NS probes or neighbour resolution attempts 
> until it has done so.
> 
> 
> Comments?
> 
> Greg



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 18:20:58 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EbndC-0000D7-9A
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 18:20:58 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09860
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 18:20:24 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVF9MRG2RC9ASXE0@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 10:20:11 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 77186AB563; Tue,
 15 Nov 2005 10:20:08 +1100 (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 028F34FB07; Tue,
 15 Nov 2005 10:20:07 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAENJU723740	for dna-list; Tue, 15 Nov 2005 10:19:30 +1100
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 jAENJUu23736	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 10:19:30 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVF9LRJJH09ASV7P@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 10:19:20 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4B77080003; Tue,
 15 Nov 2005 10:19:20 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 1F3653C005; Tue,
 15 Nov 2005 10:19:20 +1100 (EST)
Date: Tue, 15 Nov 2005 10:19:22 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <4378C1F8.8090407@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Sathya Narayanan <sathya@research.panasonic.com>, dna@eng.monash.edu.au
Message-id: <43791B7A.7080907@eng.monash.edu.au>
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.7-1.1.fc4 (X11/20050929)
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
 <4378C1F8.8090407@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT


> In any case, the MLD report message MUST be sent before transmission of
> either an RS, otherwise responding routers may not be able to resolve
> the host's link-layer address.

s/either//

Brett



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 18:23:58 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ebng5-0000xr-1Z
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 18:23:58 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09960
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 18:23:23 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVF9Q1ZBPS9I7JTJ@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 10:23:07 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A6B24AB562; Tue,
 15 Nov 2005 10:22:47 +1100 (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 5A69E4FB03; Tue,
 15 Nov 2005 10:22:47 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAENMiV23815	for dna-list; Tue, 15 Nov 2005 10:22:44 +1100
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 jAENMhu23811	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 10:22:44 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVF9PKK7XK9BVHBE@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 10:22:24 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 587A5AB545; Tue,
 15 Nov 2005 10:22:24 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 3D8CE4FB05; Tue,
 15 Nov 2005 10:22:24 +1100 (EST)
Date: Tue, 15 Nov 2005 10:22:21 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <43790282.1030506@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Greg Daley <greg.daley@eng.monash.edu.au>,
        Sathya Narayanan <sathya@research.panasonic.com>,
        dna@eng.monash.edu.au
Message-id: <43791C2D.7020509@eng.monash.edu.au>
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.7-1.1.fc4 (X11/20050929)
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
 <4378C1F8.8090407@eng.monash.edu.au> <43790282.1030506@tm.uka.de>
Content-Transfer-Encoding: 7BIT

>> The host SHOULD send the MLD group join report for the solicited
>> node's multicast group when it becomes optimistic.  [...]
> 
> 
> Note that Nick mentioned that he'll modify the OptiDAD draft so that the 
> optimistic address will be available for use even before the initial NS, 
> and thus the MLD report, is sent.  (See thread starting at [1].)
> 
> This would allow an RS with a TSLLAO option to be sent even before the 
> mobile node joins the solicited-node multicast group corresponding to 
> the optimistic address.
> 
> Does this have an impact on the DNA Protocol 3?

I think it's the desired behaviour (being able to perform the RS/RA
exchange without the need for any prior or interleaved packets).

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 18:33:28 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EbnpI-0003c7-2R
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 18:33:28 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10282
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 18:32:56 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVFA2UKTEO9I7RQU@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 10:32:58 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B7D3CAB562; Tue,
 15 Nov 2005 10:32:19 +1100 (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 6DD104FB03; Tue,
 15 Nov 2005 10:32:19 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAENUAs23953	for dna-list; Tue, 15 Nov 2005 10:30:10 +1100
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 jAENUAu23949	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 10:30:10 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVF9YZL9YE9ASWTG@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 10:30:01 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8316AAB559; Tue,
 15 Nov 2005 10:29:59 +1100 (EST)
Received: from [172.19.242.23]
 (vpn-student-242-23.its.monash.edu.au [172.19.242.23])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 64CDC4FB06; Tue,
 15 Nov 2005 10:29:58 +1100 (EST)
Date: Tue, 15 Nov 2005 10:29:39 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <43791B7A.7080907@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>
Cc: Sathya Narayanan <sathya@research.panasonic.com>, dna@eng.monash.edu.au
Message-id: <43791DE3.3050603@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
 <4378C1F8.8090407@eng.monash.edu.au> <43791B7A.7080907@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Brett Pentland wrote:
> 
>> In any case, the MLD report message MUST be sent before transmission of
>> either an RS, otherwise responding routers may not be able to resolve
>> the host's link-layer address.
> 
> 
> s/either//
> 
> Brett

Oh Yeah...

I orignally had DAD NS in my text, and removed it but forgot to
remove the either.

Greg




From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 14 20:11:08 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EbpLn-0000Ax-U7
	for dna-archive@megatron.ietf.org; Mon, 14 Nov 2005 20:11:08 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15972
	for <dna-archive@lists.ietf.org>; Mon, 14 Nov 2005 20:10:35 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVFDGR7B129BVHRC@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 15 Nov 2005 12:09:54 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D8C44AB559; Tue,
 15 Nov 2005 12:09:49 +1100 (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 86A384FB02; Tue,
 15 Nov 2005 12:09:49 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAF19Cc25304	for dna-list; Tue, 15 Nov 2005 12:09:12 +1100
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 jAF19Bu25300	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 15 Nov 2005 12:09:11 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVFDFWZZHU9ASVIV@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 15 Nov 2005 12:09:09 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 564F280003; Tue,
 15 Nov 2005 12:09:09 +1100 (EST)
Received: from [172.19.242.3]
 (vpn-student-242-3.its.monash.edu.au [172.19.242.3])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 505293C00A; Tue,
 15 Nov 2005 12:09:08 +1100 (EST)
Date: Tue, 15 Nov 2005 12:08:49 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] MLD JOIN Questions?
In-reply-to: <43790282.1030506@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: Sathya Narayanan <sathya@research.panasonic.com>, dna@eng.monash.edu.au
Message-id: <43793521.3030809@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <28489285b3.285b328489@pintlmail.MITL.Research.Panasonic.COM>
 <4378C1F8.8090407@eng.monash.edu.au> <43790282.1030506@tm.uka.de>
Content-Transfer-Encoding: 7BIT

Christian Vogt wrote:
> Hi Sathya, hi Greg.
> 
>> The host SHOULD send the MLD group join report for the solicited
>> node's multicast group when it becomes optimistic.  [...]
> 
> 
> Note that Nick mentioned that he'll modify the OptiDAD draft so that the 
> optimistic address will be available for use even before the initial NS, 
> and thus the MLD report, is sent.  (See thread starting at [1].)
> 
> This would allow an RS with a TSLLAO option to be sent even before the 
> mobile node joins the solicited-node multicast group corresponding to 
> the optimistic address.
> 
> Does this have an impact on the DNA Protocol 3?

While this is ideal, there's a problem if the router doesn't
support TSLLAO, in that it will neighbour resolve (if it doesn't
multicastRA).

If there's no MLD message sent before the RS, then an NS back to
the host will be lost on a snooping network.

That's why the MUST is in the text I wrote.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 17 14:56:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ecps7-0002Hy-1e
	for dna-archive@megatron.ietf.org; Thu, 17 Nov 2005 14:56:39 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17009
	for <dna-archive@lists.ietf.org>; Thu, 17 Nov 2005 14:56:02 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJ9CQ9K4E9ASMQP@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 18 Nov 2005 06:55:15 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 3D350AB55C; Fri,
 18 Nov 2005 06:55:13 +1100 (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 E367D4FB08; Fri,
 18 Nov 2005 06:55:12 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAHJrUv04228	for dna-list; Fri, 18 Nov 2005 06:53:30 +1100
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 jAHJrTu04224	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 18 Nov 2005 06:53:29 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJ9AEXL549BVX2Q@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 18 Nov 2005 06:53:21 +1100
Received: by localhost (Postfix, from userid 510)	id 6F751AB542; Fri,
 18 Nov 2005 06:53:21 +1100 (EST)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 4E31F4FB04	for
 <dna@eng.monash.edu.au>; Fri, 18 Nov 2005 06:53:20 +1100 (EST)
Received: from sj-core-5.cisco.com ([171.71.177.238])
 by sj-iport-3.cisco.com with ESMTP; Thu, 17 Nov 2005 11:53:19 -0800
Received: from xbh-sjc-221.amer.cisco.com
 (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jAHJrCeW012968	for
 <dna@eng.monash.edu.au>; Thu, 17 Nov 2005 11:53:17 -0800 (PST)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85])
 by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu,
 17 Nov 2005 11:53:14 -0800
Date: Thu, 17 Nov 2005 11:53:13 -0800
From: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: [DNA] draft-ietf-dna-frd-00.txt clarification for RA trigger
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Message-id: <2979E38DD6FC6544B789C8DAD7BAFC52F46A74@xmb-sjc-235.amer.cisco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_lNdPjhCwj8rL3mj63IZ5EA)"
Thread-Topic: draft-ietf-dna-frd-00.txt clarification for RA trigger
Thread-Index: AcXrsItDMFzjWPSpTnCEPNU0M/0oNA==
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-IronPort-AV: i="3.97,343,1125903600"; d="scan'208,217";
 a="366861809:sNHT71090106"
X-OriginalArrivalTime: 17 Nov 2005 19:53:14.0226 (UTC)
 FILETIME=[8BCE6D20:01C5EBB0]

This is a multi-part message in MIME format.

--Boundary_(ID_lNdPjhCwj8rL3mj63IZ5EA)
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

 
Hi folks.  Just joined the alias.  Hope this has not been discussed
already.
 
This section says that the PoA can send RS to trigger RA from the AR.
What's not clear is what source link-layer address is put into the
TSLLAO option (maybe it's implicit)?  I'm assuming that the source
link-layer address of the RS is the PoA, and the address in TSLLAO is
the host so the RA can be unicasted directly to the host.
3.1  RA Triggering
   There are two ways for such a remote Link Up event notification.  We
   may use the MIES (Media Independent Event Service) defined in IEEE
   802.21 [21] or RS with TSLLAO (Tentative Source Link-Layer Address
   Option) [14].
In the 802.11 example below, no mention of RS method.  In this case, the
AP will send RS with source MAC 
address being AP's and the TSLLAO containing the host.
 
 
5.2.1  802.11

   In 802.11 Wireless LAN technology, when a new host arrives at an
   AP(Access Point), it should associate with the AP.  The host sends an
   Association Request Message with its MAC address.  Then the AP sends
   an Association Response Message to grant association.

   As soon as association is made, the AP sends a cached RA to the host
   in an unicast 802.11 frame with the MAC address from the Association
   Request message.  The host receives the unicast RA just after
   association is made, which is the earliest possible time in current
   standard.
 
 
What is the status of  draft-daley-ipv6-tsllao-02.txt?  Is this being
adopted 
in IPv6 or DNA WG?
 
Thanks for clarifying.
 
Kent

--Boundary_(ID_lNdPjhCwj8rL3mj63IZ5EA)
Content-type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=597442019-17112005>Hi folks.&nbsp; Just 
joined the alias.&nbsp; Hope this has not been discussed 
already.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=597442019-17112005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=597442019-17112005>This section says 
that the PoA can send RS to trigger RA from the AR.&nbsp; What's not clear is 
what source link-layer address is put into the TSLLAO option (maybe it's 
implicit)?&nbsp; I'm assuming that the source link-layer address of the RS is 
the PoA, and the address in TSLLAO is the host so the RA can be unicasted 
directly to the host.</SPAN></FONT></DIV>
<DIV><!--StartFragment --><!--StartFragment --><!--StartFragment --><PRE>3.1  RA Triggering</PRE><PRE>   There are two ways for such a remote Link Up event notification.  We
   may use the MIES (Media Independent Event Service) defined in IEEE
   802.21 [21] or RS with TSLLAO (Tentative Source Link-Layer Address
   Option) [14].</PRE><PRE><SPAN class=597442019-17112005><FONT face=Arial size=2>In the 802.11 example below, no mention of RS method.  In this case, the AP will send RS with source MAC </FONT></SPAN></PRE><PRE><SPAN class=597442019-17112005><FONT face=Arial size=2>address being AP's and the TSLLAO containing the host.</FONT></SPAN></PRE><PRE><SPAN class=597442019-17112005></SPAN>&nbsp;</PRE><PRE><!--StartFragment --> <PRE>5.2.1  802.11

   In 802.11 Wireless LAN technology, when a new host arrives at an
   AP(Access Point), it should associate with the AP.  The host sends an
   Association Request Message with its MAC address.  Then the AP sends
   an Association Response Message to grant association.

   As soon as association is made, the AP sends a cached RA to the host
   in an unicast 802.11 frame with the MAC address from the Association
   Request message.  The host receives the unicast RA just after
   association is made, which is the earliest possible time in current
   standard.</PRE><PRE>&nbsp;</PRE><PRE><SPAN class=597442019-17112005></SPAN>&nbsp;</PRE><PRE><SPAN class=597442019-17112005>What is the status of <!--StartFragment --> draft-daley-ipv6-tsllao-02.txt?  Is this being adopted </SPAN></PRE><PRE><SPAN class=597442019-17112005>in IPv6 or DNA WG?</PRE><PRE>&nbsp;</PRE></SPAN><PRE><SPAN class=597442019-17112005>Thanks for clarifying.</SPAN></PRE><PRE><SPAN class=597442019-17112005></SPAN>&nbsp;</PRE><PRE><SPAN class=597442019-17112005>Kent</SPAN></PRE></PRE></DIV></BODY></HTML>

--Boundary_(ID_lNdPjhCwj8rL3mj63IZ5EA)--



From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 17 18:31:26 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EctDy-0000Ly-Mu
	for dna-archive@megatron.ietf.org; Thu, 17 Nov 2005 18:31:26 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04515
	for <dna-archive@lists.ietf.org>; Thu, 17 Nov 2005 18:30:51 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVJGVRYFEW9I8DN4@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 18 Nov 2005 10:30:57 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 258F6AB547; Fri,
 18 Nov 2005 10:30:37 +1100 (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 D67A54FB05; Fri, 18 Nov 2005 10:30:36 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAHNTb306504	for dna-list; Fri, 18 Nov 2005 10:29:37 +1100
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 jAHNTau06500	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 18 Nov 2005 10:29:37 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJGU6L6WK9BVXWV@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 18 Nov 2005 10:29:20 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 1936880005; Fri,
 18 Nov 2005 10:29:20 +1100 (EST)
Received: from [172.19.242.34]
 (vpn-student-242-34.its.monash.edu.au [172.19.242.34])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 36EBB3C00C; Fri,
 18 Nov 2005 10:29:19 +1100 (EST)
Date: Fri, 18 Nov 2005 10:28:59 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] draft-ietf-dna-frd-00.txt clarification for RA trigger
In-reply-to: <2979E38DD6FC6544B789C8DAD7BAFC52F46A74@xmb-sjc-235.amer.cisco.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "Kent Leung (kleung)" <kleung@cisco.com>
Cc: dna@eng.monash.edu.au
Message-id: <437D123B.700@eng.monash.edu.au>
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.6 (Windows/20050716)
References: <2979E38DD6FC6544B789C8DAD7BAFC52F46A74@xmb-sjc-235.amer.cisco.com>
Content-Transfer-Encoding: 7BIT

Hi Kent,

Kent Leung (kleung) wrote:
>  
> Hi folks.  Just joined the alias.  Hope this has not been discussed already.
>  
> This section says that the PoA can send RS to trigger RA from the AR.  
> What's not clear is what source link-layer address is put into the 
> TSLLAO option (maybe it's implicit)?  I'm assuming that the source 
> link-layer address of the RS is the PoA, and the address in TSLLAO is 
> the host so the RA can be unicasted directly to the host.

Yes, I think that this is the intention.

> 3.1  RA Triggering
> 
>    There are two ways for such a remote Link Up event notification.  We
>    may use the MIES (Media Independent Event Service) defined in IEEE
>    802.21 [21] or RS with TSLLAO (Tentative Source Link-Layer Address
>    Option) [14].
> 
> In the 802.11 example below, no mention of RS method.  In this case, the
 > AP will send RS with source MAC address being AP's and the
 > TSLLAO containing the host.
> 

Yes, I think so.


> 5.2.1  802.11
> 
>    In 802.11 Wireless LAN technology, when a new host arrives at an
>    AP(Access Point), it should associate with the AP.  The host sends an
>    Association Request Message with its MAC address.  Then the AP sends
>    an Association Response Message to grant association.
> 
>    As soon as association is made, the AP sends a cached RA to the host
>    in an unicast 802.11 frame with the MAC address from the Association
>    Request message.  The host receives the unicast RA just after
>    association is made, which is the earliest possible time in current
>    standard.
>  
> 
> What is the status of  draft-daley-ipv6-tsllao-02.txt?
 > Is this being adopted in IPv6 or DNA WG?

It may be adopted in DNA working group.
That seemed to be the feel of the room at the session.

That said, the draft wasn't presented in a regular way
(not advertised in the agenda, and I was actually surprised
that Suresh asked me to make a presentation on-the-fly).
So we definitely need to make an on-list consensus call
as to whether the document should be adopted in DNA as a
WG document.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Thu Nov 17 19:34:41 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EcuDB-00023d-ND
	for dna-archive@megatron.ietf.org; Thu, 17 Nov 2005 19:34:41 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08264
	for <dna-archive@lists.ietf.org>; Thu, 17 Nov 2005 19:34:05 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJJ33WH769AT2DP@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 18 Nov 2005 11:33:51 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4462BAB564; Fri,
 18 Nov 2005 11:33:47 +1100 (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 D98EB4FB0E; Fri,
 18 Nov 2005 11:33:46 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAI0Wq107168	for dna-list; Fri, 18 Nov 2005 11:32:52 +1100
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 jAI0Wqu07164	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 18 Nov 2005 11:32:52 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJJ1MTEA09BVY58@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 18 Nov 2005 11:32:36 +1100
Received: by localhost (Postfix, from userid 510)	id 6DDBA80002; Fri,
 18 Nov 2005 11:32:36 +1100 (EST)
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 8D8F73C008; Fri,
 18 Nov 2005 11:32:34 +1100 (EST)
Received: from sj-core-2.cisco.com ([171.71.177.254])
 by sj-iport-1.cisco.com with ESMTP; Thu, 17 Nov 2005 16:32:34 -0800
Received: from xbh-sjc-231.amer.cisco.com
 (xbh-sjc-231.cisco.com [128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jAI0W2sQ024035; Thu,
 17 Nov 2005 16:32:31 -0800 (PST)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85])
 by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu,
 17 Nov 2005 16:32:26 -0800
Date: Thu, 17 Nov 2005 16:32:25 -0800
From: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: RE: [DNA] draft-ietf-dna-frd-00.txt clarification for RA trigger
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: dna@eng.monash.edu.au
Message-id: <2979E38DD6FC6544B789C8DAD7BAFC52F46C0F@xmb-sjc-235.amer.cisco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] draft-ietf-dna-frd-00.txt clarification for RA trigger
Thread-Index: AcXrzuDglPMPOUimSoOpq1Qh83XBlQACD4EQ
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-IronPort-AV: i="3.97,344,1125903600"; d="scan'208"; a="676353166:sNHT26743176"
X-OriginalArrivalTime: 18 Nov 2005 00:32:26.0675 (UTC)
 FILETIME=[8D0B4830:01C5EBD7]
Content-Transfer-Encoding: 7BIT

Hi Greg.  Thanks for the clarification.  I hope some new explanatory
text will introduced in the next version.

Kent 

> -----Original Message-----
> From: Greg Daley [mailto:greg.daley@eng.monash.edu.au] 
> Sent: Thursday, November 17, 2005 3:29 PM
> To: Kent Leung (kleung)
> Cc: dna@eng.monash.edu.au
> Subject: Re: [DNA] draft-ietf-dna-frd-00.txt clarification 
> for RA trigger
> 
> Hi Kent,
> 
> Kent Leung (kleung) wrote:
> >  
> > Hi folks.  Just joined the alias.  Hope this has not been 
> discussed already.
> >  
> > This section says that the PoA can send RS to trigger RA 
> from the AR.  
> > What's not clear is what source link-layer address is put into the 
> > TSLLAO option (maybe it's implicit)?  I'm assuming that the source 
> > link-layer address of the RS is the PoA, and the address in 
> TSLLAO is 
> > the host so the RA can be unicasted directly to the host.
> 
> Yes, I think that this is the intention.
> 
> > 3.1  RA Triggering
> > 
> >    There are two ways for such a remote Link Up event 
> notification.  We
> >    may use the MIES (Media Independent Event Service) 
> defined in IEEE
> >    802.21 [21] or RS with TSLLAO (Tentative Source 
> Link-Layer Address
> >    Option) [14].
> > 
> > In the 802.11 example below, no mention of RS method.  In 
> this case, 
> > the
>  > AP will send RS with source MAC address being AP's and the 
>  > TSLLAO containing the host.
> > 
> 
> Yes, I think so.
> 
> 
> > 5.2.1  802.11
> > 
> >    In 802.11 Wireless LAN technology, when a new host arrives at an
> >    AP(Access Point), it should associate with the AP.  The 
> host sends an
> >    Association Request Message with its MAC address.  Then 
> the AP sends
> >    an Association Response Message to grant association.
> > 
> >    As soon as association is made, the AP sends a cached RA 
> to the host
> >    in an unicast 802.11 frame with the MAC address from the 
> Association
> >    Request message.  The host receives the unicast RA just after
> >    association is made, which is the earliest possible time 
> in current
> >    standard.
> >  
> > 
> > What is the status of  draft-daley-ipv6-tsllao-02.txt?
>  > Is this being adopted in IPv6 or DNA WG?
> 
> It may be adopted in DNA working group.
> That seemed to be the feel of the room at the session.
> 
> That said, the draft wasn't presented in a regular way (not 
> advertised in the agenda, and I was actually surprised that 
> Suresh asked me to make a presentation on-the-fly).
> So we definitely need to make an on-list consensus call as to 
> whether the document should be adopted in DNA as a WG document.
> 
> Greg
> 



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 18 03:35:09 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ed1i9-0006JQ-6F
	for dna-archive@megatron.ietf.org; Fri, 18 Nov 2005 03:35:09 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01097
	for <dna-archive@lists.ietf.org>; Fri, 18 Nov 2005 03:34:31 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVJZSKBVDM9ASZNJ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 18 Nov 2005 19:32:30 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D7A0EAB544; Fri,
 18 Nov 2005 19:32:26 +1100 (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 75B224FB02; Fri, 18 Nov 2005 19:32:26 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAI8Tx212321	for dna-list; Fri, 18 Nov 2005 19:29:59 +1100
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 jAI8Twu12317	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 18 Nov 2005 19:29:58 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVJZPES0L69I8DXH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 18 Nov 2005 19:29:54 +1100
Received: by localhost (Postfix, from userid 510)	id 7A8B6AB542; Fri,
 18 Nov 2005 19:29:54 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 1D39F4FB05	for
 <dna@eng.monash.edu.au>; Fri, 18 Nov 2005 19:29:52 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id l1so143151nzf for
 <dna@eng.monash.edu.au>; Fri, 18 Nov 2005 00:29:50 -0800 (PST)
Received: by 10.65.196.17 with SMTP id y17mr870474qbp; Fri,
 18 Nov 2005 00:29:50 -0800 (PST)
Received: by 10.65.182.12 with HTTP; Fri, 18 Nov 2005 00:29:50 -0800 (PST)
Date: Fri, 18 Nov 2005 17:29:50 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] draft-ietf-dna-frd-00.txt clarification for RA trigger
In-reply-to: <2979E38DD6FC6544B789C8DAD7BAFC52F46A74@xmb-sjc-235.amer.cisco.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "Kent Leung (kleung)" <kleung@cisco.com>
Cc: dna@eng.monash.edu.au
Message-id: <92e919fb0511180029j7f00e08arb1fa36b23ceefbab@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=BB6W0Qm41M82XVLdIY8R/xmYzLEo8NF0ZwuLXK3UvhRO96P88MaMKCiAZRCAAkHhViNWHTnwdJZWtiexM2MlROdmDo526JkiPleDQvuXIX5YbEcFu6QYaXHjtVFAAKJegZttJOfoywBj0YXaPtv07ufgMzDZu2shVmAXOSdp2LU=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <2979E38DD6FC6544B789C8DAD7BAFC52F46A74@xmb-sjc-235.amer.cisco.com>
Content-Transfer-Encoding: 7BIT

Dear Kent

> This section says that the PoA can send RS to trigger RA from the AR.
> What's not clear is what source link-layer address is put into the TSLLAO
> option (maybe it's implicit)?  I'm assuming that the source link-layer
> address of the RS is the PoA, and the address in TSLLAO is the host so the
> RA can be unicasted directly to the host.

We intended that the RS (sent by PoA) carries
1) unspecified source address
2) the host's MAC address in TSLLAO.

It's not our intention that the RS carries PoA's MAC address in SLLAO.
We are worried that it might bring confusion if a packet carries
different MAC addresses in TSLLAO and SLLAO.

> 3.1 RA Triggering
>  There are two ways for such a remote Link Up event notification. We
 may
> use the MIES (Media Independent Event Service) defined in IEEE
 802.21 [21]
> or RS with TSLLAO (Tentative Source Link-Layer Address
 Option) [14].
> In the 802.11 example below, no mention of RS method. In this case, the AP
> will send RS with source MAC
> address being AP's and the TSLLAO containing the host.

Similarly in this case, the AP will sends an RS
1) with unspecified source address
2) with the host's MAC address in TSLLAO.
3) without AP's MAC address

Main difference between MN soliciting and AP soliciting is that, with
the latter, we can realize a scheme (similar to Hash based FastRA) in
a simpler way.

We can assume that an AP knows all the ARs in a link. So AP can send
UNICAST RS (to remove random delay) and solicit ARs in turns (for load
balancing).

When a new host is attached to the AP, AP can sends an unicast RS to a chosen AR
1) with unspecified source address
2) with the host's MAC address in TSLLAO.

Upon receiving the unicast RS, the AR can send an RA immediately
(because it is solicited in unicast). in unicast (using TSLLAO)

Also AP take turns to solicit ARs, such as this time AR1 next time AR2
to achieve load balancing.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 18 14:13:08 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdBfU-0003Gk-5y
	for dna-archive@megatron.ietf.org; Fri, 18 Nov 2005 14:13:08 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05115
	for <dna-archive@lists.ietf.org>; Fri, 18 Nov 2005 14:12:28 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKM5TK6FK9ASZQG@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 19 Nov 2005 06:12:19 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0C4D7AB55C; Sat,
 19 Nov 2005 06:12:17 +1100 (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 B98AB4FB04; Sat,
 19 Nov 2005 06:12:16 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAIJBDO19351	for dna-list; Sat, 19 Nov 2005 06:11:13 +1100
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 jAIJBCu19347	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 19 Nov 2005 06:11:12 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKM4E1IIE9BW1XB@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 19 Nov 2005 06:11:08 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D5D7D80002	for <dna@eng.monash.edu.au>;
 Sat, 19 Nov 2005 06:11:07 +1100 (EST)
Received: from [172.19.242.1]
 (vpn-student-242-1.its.monash.edu.au [172.19.242.1])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 59BC23C007	for
 <dna@eng.monash.edu.au>; Sat, 19 Nov 2005 06:11:07 +1100 (EST)
Date: Sat, 19 Nov 2005 06:10:46 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <437E2736.3010008@eng.monash.edu.au>
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.6 (Windows/20050716)
Content-Transfer-Encoding: 7BIT

Hi,

This is the start of a two week consensus call as
to whether the document draft-pentland-dna-protocol3
as a working group document.

The consensus call will end 12:01am Saturday 3rd December UTC

The sense of the room was fairly strong to adopt the
dna protocol proposal  (23 to nil)

The document can be found at:

http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt

Please send comments to the list.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 18 14:26:13 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdBsD-0001n3-F8
	for dna-archive@megatron.ietf.org; Fri, 18 Nov 2005 14:26:13 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05749
	for <dna-archive@lists.ietf.org>; Fri, 18 Nov 2005 14:25:37 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKMM8E57O9AT2XM@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 19 Nov 2005 06:25:34 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6CFC5AB543; Sat,
 19 Nov 2005 06:25:30 +1100 (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 1AD944FB07; Sat, 19 Nov 2005 06:25:30 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAIJPJ219518	for dna-list; Sat, 19 Nov 2005 06:25:19 +1100
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 jAIJPIu19514	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 19 Nov 2005 06:25:18 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKMLN2THC9BW2FK@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 19 Nov 2005 06:25:02 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 5637280002	for <dna@eng.monash.edu.au>;
 Sat, 19 Nov 2005 06:25:02 +1100 (EST)
Received: from [172.19.242.1]
 (vpn-student-242-1.its.monash.edu.au [172.19.242.1])
	by larry.its.monash.edu.au (Postfix) with ESMTP id C57653C007	for
 <dna@eng.monash.edu.au>; Sat, 19 Nov 2005 06:25:01 +1100 (EST)
Date: Sat, 19 Nov 2005 06:24:42 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: [DNA] Consensus call for adoption of TSLLAO as a working group item
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Message-id: <437E2A7A.5000808@eng.monash.edu.au>
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.6 (Windows/20050716)
Content-Transfer-Encoding: 7BIT


Hi,

This is the start of a two week consensus call as
to whether Tentative Source Link-Layer Address Options
should be adopted as a working group item in DNA WG.

These are currently documented in: draft-daley-ipv6-tsllao-02.txt

While there was some interest in this at the IETF64 session,
the chairs recognize that few people had prepared to discuss
this document before the session.

Any feedback or queries about this consensus call can be
sent to the chairs.

The consensus call will end 12:01am Saturday 3rd December UTC

The document can be found at:

http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt

Here's a (quick) summary of the discussion from the minutes
(from JAK, with some recollections added by GD.  Further
merged minutes will be available shortly).
---------
...

Suresh
TSLLAO

Normatively referenced by two documents, which are WG docs

IPv6 chairs want this done in DNA cause IPv6 WG is going into hibernation

Greg will present
(briefly summarizes draft)

Problem with SLLAO is that it overrides NC entry, would like to get
unicast back to an optimistic address

TSLLAO does not destroy NC entry

Implementation in Linux available from Greg

Suresh
RS can't be unicast without optoin, need to do NS. Necessary to have
this done, IANA allocation

Mohan
Solution all you need is Mac address for repsonse for RA, create NC
entry for packet. Optimistic DAD is written such that create an NC
entry if you don't have it.

Greg
Can send unicast packet back without a Neighbour Cache entry.

Mohan
Does create entry if no entry is there?

Greg
With oDAD, small chance of collision, if there's a collision, we want
operations to be safe for original address owner, advantage if temporary,
won't create or modify an entry (GD: if an entry exists). MAC binding will
be delivered to another destiantion if there is another NC entry.

Suresh
WG item - 8 hands
none against

confirm on the list.

Greg
Know it's a late agenda item, not trying to shove something through.

Suresh
Should this be in a separate document? 5 hands for
Part of solution document? 2

confirm on list

(discussion of whether separate or same)

---------



Please be aware that if adopted, further discussion on whether
the document should stand-alone or be merged into an existing
document will occur, with another consensus call.

Please send comments to the list.

Greg



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 18 14:33:54 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdBze-0002nU-3G
	for dna-archive@megatron.ietf.org; Fri, 18 Nov 2005 14:33:54 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06090
	for <dna-archive@lists.ietf.org>; Fri, 18 Nov 2005 14:33:17 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKMVHX5TM9BW2GC@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 19 Nov 2005 06:33:04 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0826880002; Sat,
 19 Nov 2005 06:32:59 +1100 (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 BDEE03C003; Sat, 19 Nov 2005 06:32:58 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAIJWoF19605	for dna-list; Sat, 19 Nov 2005 06:32:50 +1100
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 jAIJWnu19600	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 19 Nov 2005 06:32:49 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKMUZBB8W9BW2GC@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 19 Nov 2005 06:32:34 +1100
Received: by localhost (Postfix, from userid 510)	id 34D0EAB559; Sat,
 19 Nov 2005 06:32:34 +1100 (EST)
Received: from tayrelbas01.tay.hp.com (tayrelbas01.tay.hp.com [161.114.80.244])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 26B444FB06; Sat, 19 Nov 2005 06:32:32 +1100 (EST)
Received: from tayexg12.americas.cpqcorp.net
 (tayexg12.americas.cpqcorp.net [16.103.130.127])	by tayrelbas01.tay.hp.com
 (Postfix) with ESMTP id A12C0341EE; Fri, 18 Nov 2005 14:32:27 -0500 (EST)
Received: from tayexc14.americas.cpqcorp.net ([16.103.130.45])
 by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); Fri,
 18 Nov 2005 14:32:27 -0500
Date: Fri, 18 Nov 2005 14:32:26 -0500
From: "Bound, Jim" <Jim.Bound@hp.com>
Subject: RE: [DNA] Consensus call for adoption of TSLLAO as a working group item
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>, dna@eng.monash.edu.au
Message-id: 
 <936A4045C332714F975800409DE09240015AC09F@tayexc14.americas.cpqcorp.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] Consensus call for adoption of TSLLAO as a working group
 item
Thread-Index: AcXsdgH+pkpMIGSaTKam8Uyh7PZuegAAMZ4w
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 18 Nov 2005 19:32:27.0337 (UTC)
 FILETIME=[CF040390:01C5EC76]
Content-Transfer-Encoding: 7BIT

This should move to PS.
thx
/jim 

> -----Original Message-----
> From: owner-dna@ecselists.eng.monash.edu.au 
> [mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of Greg Daley
> Sent: Friday, November 18, 2005 2:25 PM
> To: dna@eng.monash.edu.au
> Subject: [DNA] Consensus call for adoption of TSLLAO as a 
> working group item
> 
> 
> Hi,
> 
> This is the start of a two week consensus call as
> to whether Tentative Source Link-Layer Address Options
> should be adopted as a working group item in DNA WG.
> 
> These are currently documented in: draft-daley-ipv6-tsllao-02.txt
> 
> While there was some interest in this at the IETF64 session,
> the chairs recognize that few people had prepared to discuss
> this document before the session.
> 
> Any feedback or queries about this consensus call can be
> sent to the chairs.
> 
> The consensus call will end 12:01am Saturday 3rd December UTC
> 
> The document can be found at:
> 
> http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt
> 
> Here's a (quick) summary of the discussion from the minutes
> (from JAK, with some recollections added by GD.  Further
> merged minutes will be available shortly).
> ---------
> ...
> 
> Suresh
> TSLLAO
> 
> Normatively referenced by two documents, which are WG docs
> 
> IPv6 chairs want this done in DNA cause IPv6 WG is going into 
> hibernation
> 
> Greg will present
> (briefly summarizes draft)
> 
> Problem with SLLAO is that it overrides NC entry, would like to get
> unicast back to an optimistic address
> 
> TSLLAO does not destroy NC entry
> 
> Implementation in Linux available from Greg
> 
> Suresh
> RS can't be unicast without optoin, need to do NS. Necessary to have
> this done, IANA allocation
> 
> Mohan
> Solution all you need is Mac address for repsonse for RA, create NC
> entry for packet. Optimistic DAD is written such that create an NC
> entry if you don't have it.
> 
> Greg
> Can send unicast packet back without a Neighbour Cache entry.
> 
> Mohan
> Does create entry if no entry is there?
> 
> Greg
> With oDAD, small chance of collision, if there's a collision, we want
> operations to be safe for original address owner, advantage 
> if temporary,
> won't create or modify an entry (GD: if an entry exists). MAC 
> binding will
> be delivered to another destiantion if there is another NC entry.
> 
> Suresh
> WG item - 8 hands
> none against
> 
> confirm on the list.
> 
> Greg
> Know it's a late agenda item, not trying to shove something through.
> 
> Suresh
> Should this be in a separate document? 5 hands for
> Part of solution document? 2
> 
> confirm on list
> 
> (discussion of whether separate or same)
> 
> ---------
> 
> 
> 
> Please be aware that if adopted, further discussion on whether
> the document should stand-alone or be merged into an existing
> document will occur, with another consensus call.
> 
> Please send comments to the list.
> 
> Greg
> 



From dna-owner@webcamserver.eng.monash.edu.au Fri Nov 18 19:47:52 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdGtU-0003O5-GV
	for dna-archive@megatron.ietf.org; Fri, 18 Nov 2005 19:47:52 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25217
	for <dna-archive@lists.ietf.org>; Fri, 18 Nov 2005 19:47:16 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKXU5NEOI9AT10H@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 19 Nov 2005 11:47:20 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 806A1AB542; Sat,
 19 Nov 2005 11:47:15 +1100 (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 3FD664FB05; Sat, 19 Nov 2005 11:47:15 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAJ0jkM22935	for dna-list; Sat, 19 Nov 2005 11:45:46 +1100
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 jAJ0jku22931	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 19 Nov 2005 11:45:46 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVKXRYWJ789BVZV1@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 19 Nov 2005 11:45:29 +1100
Received: by localhost (Postfix, from userid 510)	id CEE3680002; Sat,
 19 Nov 2005 11:45:29 +1100 (EST)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 8F4463C003; Sat,
 19 Nov 2005 11:45:28 +1100 (EST)
Received: from jurassic.eng.sun.com ([129.146.226.31])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id jAJ0jRD7010830; Fri,
 18 Nov 2005 17:45:27 -0700 (MST)
Received: from [129.146.228.81] (bobo.SFBay.Sun.COM [129.146.228.81])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id jAJ0jQ3Y016892
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri,
 18 Nov 2005 16:45:26 -0800 (PST)
Date: Fri, 18 Nov 2005 16:45:26 -0800
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Consensus call for adoption of TSLLAO as a working group item
In-reply-to: <437E2A7A.5000808@eng.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
Message-id: <437E75A6.4060900@sun.com>
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.6 (X11/20050720)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <437E2A7A.5000808@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Greg Daley wrote:
> 
> Hi,
> 
> This is the start of a two week consensus call as
> to whether Tentative Source Link-Layer Address Options
> should be adopted as a working group item in DNA WG.

It makes sense to adopt this as a WG document.

Furthermore, I think it makes sense to keep it as a separate document, 
because there might be cases when TSLLAO will be used in the future even 
though the DNA protocol isn't used. There doesn't seem much benefits of 
putting both of them in the same document.

So once the document has been accepted as a WG document, I think the 
chairs should last call it for PS, and move forward!

    Erik



From dna-owner@webcamserver.eng.monash.edu.au Sat Nov 19 11:32:38 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdVdm-0006fT-6l
	for dna-archive@megatron.ietf.org; Sat, 19 Nov 2005 11:32:38 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06008
	for <dna-archive@lists.ietf.org>; Sat, 19 Nov 2005 11:32:00 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVLUUQRWC69BW1KZ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 20 Nov 2005 03:32:21 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 14CC5AB55C; Sun,
 20 Nov 2005 03:32:14 +1100 (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 C7ADE4FB02; Sun,
 20 Nov 2005 03:32:13 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAJGOsp00338	for dna-list; Sun, 20 Nov 2005 03:24:54 +1100
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 jAJGOsu00334	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 20 Nov 2005 03:24:54 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVLULJLR5K9I8DRO@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 20 Nov 2005 03:24:49 +1100
Received: by localhost (Postfix, from userid 510)	id 2C2A480002; Sun,
 20 Nov 2005 03:24:49 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(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 093BF3C00F; Sun, 20 Nov 2005 03:24:47 +1100 (EST)
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by iramx2.ira.uni-karlsruhe.de with esmtpsa	id 1EdVW5-0002aS-IY; Sat,
 19 Nov 2005 17:24:43 +0100
Date: Sat, 19 Nov 2005 17:24:41 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: [DNA] CPL Required in draft-pentland-dna-protocol3-00.txt?
Sender: owner-dna@ecselists.eng.monash.edu.au
To: DNA <dna@eng.monash.edu.au>
Cc: Brett Pentland <brett.pentland@eng.monash.edu.au>
Message-id: <437F51C9.6090308@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT

All,

does the DNA Protocol 3 (draft-pentland-dna-protocol3-00.txt) require 
mobile nodes to implement CPL as a fall-back mechanism for non-DNA routers?

Section 7.2 seems to imply that CPL is required, where section 6.2.5 
suggests CPL is recommended only.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



From dna-owner@webcamserver.eng.monash.edu.au Sat Nov 19 16:17:02 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eda50-0006E0-Li
	for dna-archive@megatron.ietf.org; Sat, 19 Nov 2005 16:17:02 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16901
	for <dna-archive@lists.ietf.org>; Sat, 19 Nov 2005 16:16:25 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVM4S1XUVW9BW4EI@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 20 Nov 2005 08:16:29 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BB1CBAB543; Sun,
 20 Nov 2005 08:16:23 +1100 (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 76AD64FB03; Sun, 20 Nov 2005 08:16:23 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAJLCeT07357	for dna-list; Sun, 20 Nov 2005 08:12:40 +1100
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 jAJLCdu07353	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 20 Nov 2005 08:12:39 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVM4N2IRCO9BW81M@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 20 Nov 2005 08:12:22 +1100
Received: by localhost (Postfix, from userid 510)	id CC52FAB542; Sun,
 20 Nov 2005 08:12:22 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(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 CFD124FB02; Sun, 20 Nov 2005 08:12:20 +1100 (EST)
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by iramx2.ira.uni-karlsruhe.de with esmtpsa	id 1Eda0M-00046w-Sq; Sat,
 19 Nov 2005 22:12:18 +0100
Date: Sat, 19 Nov 2005 22:12:14 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] Consensus call for adoption of TSLLAO as a working group item
In-reply-to: <437E2A7A.5000808@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Cc: Greg Daley <greg.daley@eng.monash.edu.au>
Message-id: <437F952E.5010208@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
References: <437E2A7A.5000808@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

I think there is a good reason for moving this draft towards the 
standards track:

The draft specifies the use of a TSLLAO in Neighbor Solicitation 
messages, which is in particular useful in conjunction with Optimistic 
DAD.  This is something the DNA Protocol 3 does not cover, so it makes 
sense to publish the TSLLAO draft separately.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Greg Daley wrote:
> 
> Hi,
> 
> This is the start of a two week consensus call as
> to whether Tentative Source Link-Layer Address Options
> should be adopted as a working group item in DNA WG.
> 
> These are currently documented in: draft-daley-ipv6-tsllao-02.txt
> 
> While there was some interest in this at the IETF64 session,
> the chairs recognize that few people had prepared to discuss
> this document before the session.
> 
> Any feedback or queries about this consensus call can be
> sent to the chairs.
> 
> The consensus call will end 12:01am Saturday 3rd December UTC
> 
> The document can be found at:
> 
> http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt
> 
> Here's a (quick) summary of the discussion from the minutes
> (from JAK, with some recollections added by GD.  Further
> merged minutes will be available shortly).
> ---------
> ...
> 
> Suresh
> TSLLAO
> 
> Normatively referenced by two documents, which are WG docs
> 
> IPv6 chairs want this done in DNA cause IPv6 WG is going into hibernation
> 
> Greg will present
> (briefly summarizes draft)
> 
> Problem with SLLAO is that it overrides NC entry, would like to get
> unicast back to an optimistic address
> 
> TSLLAO does not destroy NC entry
> 
> Implementation in Linux available from Greg
> 
> Suresh
> RS can't be unicast without optoin, need to do NS. Necessary to have
> this done, IANA allocation
> 
> Mohan
> Solution all you need is Mac address for repsonse for RA, create NC
> entry for packet. Optimistic DAD is written such that create an NC
> entry if you don't have it.
> 
> Greg
> Can send unicast packet back without a Neighbour Cache entry.
> 
> Mohan
> Does create entry if no entry is there?
> 
> Greg
> With oDAD, small chance of collision, if there's a collision, we want
> operations to be safe for original address owner, advantage if temporary,
> won't create or modify an entry (GD: if an entry exists). MAC binding will
> be delivered to another destiantion if there is another NC entry.
> 
> Suresh
> WG item - 8 hands
> none against
> 
> confirm on the list.
> 
> Greg
> Know it's a late agenda item, not trying to shove something through.
> 
> Suresh
> Should this be in a separate document? 5 hands for
> Part of solution document? 2
> 
> confirm on list
> 
> (discussion of whether separate or same)
> 
> ---------
> 
> 
> 
> Please be aware that if adopted, further discussion on whether
> the document should stand-alone or be merged into an existing
> document will occur, with another consensus call.
> 
> Please send comments to the list.
> 
> Greg




From dna-owner@webcamserver.eng.monash.edu.au Sat Nov 19 16:30:33 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdaI5-0000IW-R1
	for dna-archive@megatron.ietf.org; Sat, 19 Nov 2005 16:30:33 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17372
	for <dna-archive@lists.ietf.org>; Sat, 19 Nov 2005 16:29:56 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVM58QIO3M9ASVIJ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 20 Nov 2005 08:29:52 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id CBB2080003; Sun,
 20 Nov 2005 08:29:50 +1100 (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 71EA43C006; Sun, 20 Nov 2005 08:29:50 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAJLRAC07513	for dna-list; Sun, 20 Nov 2005 08:27:10 +1100
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 jAJLR9u07508	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 20 Nov 2005 08:27:09 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVM552ZU4S9ASVIJ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 20 Nov 2005 08:26:54 +1100
Received: by localhost (Postfix, from userid 510)	id 2A85EAB55C; Sun,
 20 Nov 2005 08:26:54 +1100 (EST)
Received: from iramx2.ira.uni-karlsruhe.de
 (iramx2.ira.uni-karlsruhe.de [141.3.10.81])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by moe.its.monash.edu.au (Postfix)
 with ESMTP id EE78C4FB09; Sun, 20 Nov 2005 08:26:52 +1100 (EST)
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by iramx2.ira.uni-karlsruhe.de with esmtpsa	id 1EdaES-0004aG-KN; Sat,
 19 Nov 2005 22:26:50 +0100
Date: Sat, 19 Nov 2005 22:26:48 +0100
From: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
In-reply-to: <437E2736.3010008@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>, Dna <dna@eng.monash.edu.au>
Message-id: <437F9898.8050901@tm.uka.de>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: de-DE, de, en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923
 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
References: <437E2736.3010008@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

I wasn't in Vancouver, but count me in as the 24th person in favor of 
the proposal.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Greg Daley wrote:
> Hi,
> 
> This is the start of a two week consensus call as
> to whether the document draft-pentland-dna-protocol3
> as a working group document.
> 
> The consensus call will end 12:01am Saturday 3rd December UTC
> 
> The sense of the room was fairly strong to adopt the
> dna protocol proposal  (23 to nil)
> 
> The document can be found at:
> 
> http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
> 
> Please send comments to the list.
> 
> Greg




From dna-owner@webcamserver.eng.monash.edu.au Sat Nov 19 17:27:37 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdbBJ-0002Da-7M
	for dna-archive@megatron.ietf.org; Sat, 19 Nov 2005 17:27:37 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19137
	for <dna-archive@lists.ietf.org>; Sat, 19 Nov 2005 17:26:59 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVM78NTK909BW8D6@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 20 Nov 2005 09:27:06 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 207B8AB546; Sun,
 20 Nov 2005 09:27:03 +1100 (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 BC6674FB06; Sun, 20 Nov 2005 09:27:02 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAJMNdZ08117	for dna-list; Sun, 20 Nov 2005 09:23:39 +1100
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 jAJMNcu08113	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 20 Nov 2005 09:23:39 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVM74CV6JS9I8PJI@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 20 Nov 2005 09:23:35 +1100
Received: by localhost (Postfix, from userid 510)	id 014A5AB559; Sun,
 20 Nov 2005 09:23:34 +1100 (EST)
Received: from mgw-ext04.nokia.com (mgw-ext04.nokia.com [131.228.20.96])
	(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 90DCB4FB03; Sun, 20 Nov 2005 09:23:33 +1100 (EST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7)
 with ESMTP id jAJMIZKP032215; Sun, 20 Nov 2005 00:18:40 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111])
 by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sun,
 20 Nov 2005 00:23:26 +0200
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23])
 by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat,
 19 Nov 2005 16:23:24 -0600
Date: Sat, 19 Nov 2005 14:23:21 -0800
From: Mohan.Parthasarathy@nokia.com
Subject: RE: [DNA] Consensus call for adoption of TSLLAO as a working group item
Sender: owner-dna@ecselists.eng.monash.edu.au
To: greg.daley@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <8A76136424391244A5CF016533708537E4C507@mvebe101.NOE.Nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] Consensus call for adoption of TSLLAO as a working group
 item
Thread-Index: AcXsdmX1A9r2iIy0RIi7T+L/L95M6wA4WjLg
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 19 Nov 2005 22:23:24.0183 (UTC)
 FILETIME=[DAFC4270:01C5ED57]
Content-Transfer-Encoding: 7BIT

This should be accepted as a WG item.

-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, November 18, 2005 11:25 AM
>To: dna@eng.monash.edu.au
>Subject: [DNA] Consensus call for adoption of TSLLAO as a 
>working group item
>
>
>Hi,
>
>This is the start of a two week consensus call as to whether 
>Tentative Source Link-Layer Address Options should be adopted 
>as a working group item in DNA WG.
>
>These are currently documented in: draft-daley-ipv6-tsllao-02.txt
>
>While there was some interest in this at the IETF64 session, 
>the chairs recognize that few people had prepared to discuss 
>this document before the session.
>
>Any feedback or queries about this consensus call can be sent 
>to the chairs.
>
>The consensus call will end 12:01am Saturday 3rd December UTC
>
>The document can be found at:
>
>http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt
>
>Here's a (quick) summary of the discussion from the minutes 
>(from JAK, with some recollections added by GD.  Further 
>merged minutes will be available shortly).
>---------
>...
>
>Suresh
>TSLLAO
>
>Normatively referenced by two documents, which are WG docs
>
>IPv6 chairs want this done in DNA cause IPv6 WG is going into 
>hibernation
>
>Greg will present
>(briefly summarizes draft)
>
>Problem with SLLAO is that it overrides NC entry, would like 
>to get unicast back to an optimistic address
>
>TSLLAO does not destroy NC entry
>
>Implementation in Linux available from Greg
>
>Suresh
>RS can't be unicast without optoin, need to do NS. Necessary 
>to have this done, IANA allocation
>
>Mohan
>Solution all you need is Mac address for repsonse for RA, 
>create NC entry for packet. Optimistic DAD is written such 
>that create an NC entry if you don't have it.
>
>Greg
>Can send unicast packet back without a Neighbour Cache entry.
>
>Mohan
>Does create entry if no entry is there?
>
>Greg
>With oDAD, small chance of collision, if there's a collision, 
>we want operations to be safe for original address owner, 
>advantage if temporary, won't create or modify an entry (GD: 
>if an entry exists). MAC binding will be delivered to another 
>destiantion if there is another NC entry.
>
>Suresh
>WG item - 8 hands
>none against
>
>confirm on the list.
>
>Greg
>Know it's a late agenda item, not trying to shove something through.
>
>Suresh
>Should this be in a separate document? 5 hands for Part of 
>solution document? 2
>
>confirm on list
>
>(discussion of whether separate or same)
>
>---------
>
>
>
>Please be aware that if adopted, further discussion on whether 
>the document should stand-alone or be merged into an existing 
>document will occur, with another consensus call.
>
>Please send comments to the list.
>
>Greg
>



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 18:04:26 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdyEU-00068h-Kk
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 18:04:26 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18097
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 18:03:48 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNMSY7R8A9AT886@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 10:03:21 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2E78780003; Mon,
 21 Nov 2005 10:03:18 +1100 (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 AB3963C007; Mon, 21 Nov 2005 10:03:17 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAKMwh824180	for dna-list; Mon, 21 Nov 2005 09:58:43 +1100
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 jAKMwgu24176	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 09:58:42 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNMMYOWHS9I8RU6@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 09:58:29 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id E063EAB562; Mon,
 21 Nov 2005 09:58:28 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by moe.its.monash.edu.au (Postfix) with ESMTP id BDA2F4FB0C; Mon,
 21 Nov 2005 09:58:28 +1100 (EST)
Date: Mon, 21 Nov 2005 09:58:29 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] CPL Required in draft-pentland-dna-protocol3-00.txt?
In-reply-to: <437F51C9.6090308@tm.uka.de>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Christian Vogt <chvogt@tm.uka.de>
Cc: DNA <dna@eng.monash.edu.au>
Message-id: <4380FF95.8030507@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
References: <437F51C9.6090308@tm.uka.de>
Content-Transfer-Encoding: 7BIT

Hi Christian,

I think that implementing CPL should be a MUST for dealing with info
from non-DNA routers.  I guess 6.2.5 should have a MUST instead of a
SHOULD.  That section should probably also have a sentence about
changing the CPL state after receiving a CompleteRA - no need for
further solicitations.

Perhaps there should also be some text near the start of the spec
that says that CPL must be implemented by hosts for dealing with
non-DNA routers.

Cheers,
Brett.

Christian Vogt wrote:
> All,
> 
> does the DNA Protocol 3 (draft-pentland-dna-protocol3-00.txt) require 
> mobile nodes to implement CPL as a fall-back mechanism for non-DNA routers?
> 
> Section 7.2 seems to imply that CPL is required, where section 6.2.5 
> suggests CPL is recommended only.
> 
> - Christian
> 



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 18:07:19 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdyHH-0006V2-Hy
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 18:07:19 -0500
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18189
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 18:06:41 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNMXHX2209I8PH9@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 10:07:05 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 6825AAB559; Mon,
 21 Nov 2005 10:06:58 +1100 (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 107EF4FB02; Mon,
 21 Nov 2005 10:06:58 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAKN4nk24275	for dna-list; Mon, 21 Nov 2005 10:04:49 +1100
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 jAKN4nu24268	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 10:04:49 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNMUOM86I9ASO2T@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 10:04:42 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 521DE80002; Mon,
 21 Nov 2005 10:04:42 +1100 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 2E1E93C00A; Mon,
 21 Nov 2005 10:04:42 +1100 (EST)
Date: Mon, 21 Nov 2005 10:04:37 +1100
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
In-reply-to: <437E2736.3010008@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <43810105.2090907@eng.monash.edu.au>
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.7-1.1.fc4 (X11/20050929)
References: <437E2736.3010008@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Is this just asking for those who weren't at the Vancouver meeting?

If not, then I'm (still) in favour of adopting this as a working group
draft.

Brett.

Greg Daley wrote:
> Hi,
> 
> This is the start of a two week consensus call as
> to whether the document draft-pentland-dna-protocol3
> as a working group document.
> 
> The consensus call will end 12:01am Saturday 3rd December UTC
> 
> The sense of the room was fairly strong to adopt the
> dna protocol proposal  (23 to nil)
> 
> The document can be found at:
> 
> http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
> 
> Please send comments to the list.
> 
> Greg



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 19:31:59 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EdzbD-0001BD-GX
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 19:31:59 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22137
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 19:31:20 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNPV07V8S9I8UL1@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 11:31:32 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id F1191AB55C; Mon,
 21 Nov 2005 11:31:14 +1100 (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 9B3E94FB06; Mon,
 21 Nov 2005 11:31:14 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL0RgA25183	for dna-list; Mon, 21 Nov 2005 11:27:42 +1100
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 jAL0Rfu25178	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 11:27:42 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNPQ8VMRM9BW8Q4@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 11:27:25 +1100
Received: by localhost (Postfix, from userid 510)	id 24611AB55C; Mon,
 21 Nov 2005 11:27:25 +1100 (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 4923E4FB04; Mon, 21 Nov 2005 11:27:23 +1100 (EST)
Received: from redwood.research.panasonic.com
 (ftp.research.panasonic.com [150.169.3.2] (may be forged))
	by oak.research.panasonic.com (1.1.1/1.1.1) with ESMTP id jAL0RLmZ027763; Sun,
 20 Nov 2005 19:27:21 -0500
Received: from redwood.research.panasonic.com
 (birch.research.pansonic.com [150.169.3.2])	by testing.research.panasonic.com
 (Postfix) with ESMTP id A8F9D1F42FC; Sun, 20 Nov 2005 19:15:14 -0500 (EST)
Received: from [150.169.1.185] (unknown [150.169.1.185])
 by	redwood.research.panasonic.com (Postfix) with ESMTP id 816FB1E8188; Sun,
 20 Nov 2005 19:15:14 -0500 (EST)
Date: Sun, 20 Nov 2005 19:26:37 -0500
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: Re: [DNA] Consensus call for adoption of TSLLAO as a working	groupitem
In-reply-to: <437E2A7A.5000808@eng.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
Message-id: <4381143D.6010802@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.0 (2005-09-13)
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:22 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
References: <437E2A7A.5000808@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

I think this should be accepted as working group document and it should
be a separate document.

- Sathya

Greg Daley wrote:

>
> Hi,
>
> This is the start of a two week consensus call as
> to whether Tentative Source Link-Layer Address Options
> should be adopted as a working group item in DNA WG.
>
> These are currently documented in: draft-daley-ipv6-tsllao-02.txt
>
> While there was some interest in this at the IETF64 session,
> the chairs recognize that few people had prepared to discuss
> this document before the session.
>
> Any feedback or queries about this consensus call can be
> sent to the chairs.
>
> The consensus call will end 12:01am Saturday 3rd December UTC
>
> The document can be found at:
>
> http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt
>
> Here's a (quick) summary of the discussion from the minutes
> (from JAK, with some recollections added by GD.  Further
> merged minutes will be available shortly).
> ---------
> ...
>
> Suresh
> TSLLAO
>
> Normatively referenced by two documents, which are WG docs
>
> IPv6 chairs want this done in DNA cause IPv6 WG is going into hibernation
>
> Greg will present
> (briefly summarizes draft)
>
> Problem with SLLAO is that it overrides NC entry, would like to get
> unicast back to an optimistic address
>
> TSLLAO does not destroy NC entry
>
> Implementation in Linux available from Greg
>
> Suresh
> RS can't be unicast without optoin, need to do NS. Necessary to have
> this done, IANA allocation
>
> Mohan
> Solution all you need is Mac address for repsonse for RA, create NC
> entry for packet. Optimistic DAD is written such that create an NC
> entry if you don't have it.
>
> Greg
> Can send unicast packet back without a Neighbour Cache entry.
>
> Mohan
> Does create entry if no entry is there?
>
> Greg
> With oDAD, small chance of collision, if there's a collision, we want
> operations to be safe for original address owner, advantage if temporary,
> won't create or modify an entry (GD: if an entry exists). MAC binding
> will
> be delivered to another destiantion if there is another NC entry.
>
> Suresh
> WG item - 8 hands
> none against
>
> confirm on the list.
>
> Greg
> Know it's a late agenda item, not trying to shove something through.
>
> Suresh
> Should this be in a separate document? 5 hands for
> Part of solution document? 2
>
> confirm on list
>
> (discussion of whether separate or same)
>
> ---------
>
>
>
> Please be aware that if adopted, further discussion on whether
> the document should stand-alone or be merged into an existing
> document will occur, with another consensus call.
>
> Please send comments to the list.
>
> Greg





From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 19:35:38 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Edzek-0001gD-Pb
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 19:35:38 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22359
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 19:34:59 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNPV691T69AQT7V@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 11:31:31 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D9C31AB564; Mon,
 21 Nov 2005 11:31:22 +1100 (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 966EE4FB0B; Mon,
 21 Nov 2005 11:31:22 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL0Rug25192	for dna-list; Mon, 21 Nov 2005 11:27:56 +1100
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 jAL0Ruu25186	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 11:27:56 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNPQV50929BWE94@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 11:27:55 +1100
Received: by localhost (Postfix, from userid 510)	id F1E4A80003; Mon,
 21 Nov 2005 11:27:54 +1100 (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 1B77C3C004; Mon, 21 Nov 2005 11:27:53 +1100 (EST)
Received: from redwood.research.panasonic.com
 (ftp.research.panasonic.com [150.169.3.2] (may be forged))
	by oak.research.panasonic.com (1.1.1/1.1.1) with ESMTP id jAL0RqJj027767; Sun,
 20 Nov 2005 19:27:52 -0500
Received: from redwood.research.panasonic.com
 (birch.research.pansonic.com [150.169.3.2])	by testing.research.panasonic.com
 (Postfix) with ESMTP id 4BF751F4301; Sun, 20 Nov 2005 19:15:46 -0500 (EST)
Received: from [150.169.1.185] (unknown [150.169.1.185])
 by	redwood.research.panasonic.com (Postfix) with ESMTP id 3E8111F42FC; Sun,
 20 Nov 2005 19:15:46 -0500 (EST)
Date: Sun, 20 Nov 2005 19:27:13 -0500
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: Re: [DNA] Confirmation of sense of room	to
	adoptdraft-pentland-dna-protocol3
In-reply-to: <437E2736.3010008@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <43811461.2060007@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.0 (2005-09-13)
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:66.96335 C:22 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
References: <437E2736.3010008@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

I am in favor of adopting this as a working group document.

thanks,
Sathya

Greg Daley wrote:

> Hi,
>
> This is the start of a two week consensus call as
> to whether the document draft-pentland-dna-protocol3
> as a working group document.
>
> The consensus call will end 12:01am Saturday 3rd December UTC
>
> The sense of the room was fairly strong to adopt the
> dna protocol proposal  (23 to nil)
>
> The document can be found at:
>
> http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
>
> Please send comments to the list.
>
> Greg





From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 21:09:41 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee17l-00054R-KZ
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 21:09:41 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26065
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 21:09:04 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNT9EM3EO9I8JBD@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 13:08:31 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 64B23AB543; Mon,
 21 Nov 2005 13:08:22 +1100 (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 230F54FB07; Mon, 21 Nov 2005 13:08:22 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL24h126357	for dna-list; Mon, 21 Nov 2005 13:04:43 +1100
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 jAL24hu26353	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 13:04:43 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNT4JKQA49I8ZVM@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 13:04:27 +1100
Received: by localhost (Postfix, from userid 510)	id 0EA34AB543; Mon,
 21 Nov 2005 13:04:26 +1100 (EST)
Received: from neon.tcs.hut.fi (neon.tcs.hut.fi [130.233.215.20])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 4E8BA4FB0A; Mon,
 21 Nov 2005 13:04:25 +1100 (EST)
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP id 94C72800089; Mon,
 21 Nov 2005 04:04:22 +0200 (EET)
Date: Mon, 21 Nov 2005 04:04:22 +0200 (EET)
From: Wassim Haddad <whaddad@tcs.hut.fi>
Subject: Re: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
In-reply-to: <437E2736.3010008@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <Pine.LNX.4.58.0511210400260.10749@rhea.tcs.hut.fi>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <437E2736.3010008@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi,

I am in favor of adopting draft-pentland-dna-protocol3-00 as WG document.


Regards,

Wassim H.

On Sat, 19 Nov 2005, Greg Daley wrote:

> Hi,
>
> This is the start of a two week consensus call as
> to whether the document draft-pentland-dna-protocol3
> as a working group document.
>
> The consensus call will end 12:01am Saturday 3rd December UTC
>
> The sense of the room was fairly strong to adopt the
> dna protocol proposal  (23 to nil)
>
> The document can be found at:
>
> http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
>
> Please send comments to the list.
>
> Greg
>
>



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 23:25:44 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee3FQ-0000CE-JU
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 23:25:44 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02087
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 23:25:04 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNY12Z0NQ9ASTCK@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 15:24:30 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4451BAB559; Mon,
 21 Nov 2005 15:24:26 +1100 (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 054724FB03; Mon,
 21 Nov 2005 15:24:26 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL4Kmh27921	for dna-list; Mon, 21 Nov 2005 15:20:48 +1100
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 jAL4Klu27917	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 15:20:47 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVNXVI617O9I8HN6@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 15:20:43 +1100
Received: by localhost (Postfix, from userid 510)	id 62B28AB544; Mon,
 21 Nov 2005 15:20:43 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 28C0A4FB13	for
 <dna@eng.monash.edu.au>; Mon, 21 Nov 2005 15:20:41 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id o1so697237nzf for
 <dna@eng.monash.edu.au>; Sun, 20 Nov 2005 20:20:40 -0800 (PST)
Received: by 10.65.93.13 with SMTP id v13mr2464182qbl; Sun,
 20 Nov 2005 20:20:40 -0800 (PST)
Received: by 10.65.182.12 with HTTP; Sun, 20 Nov 2005 20:20:40 -0800 (PST)
Date: Mon, 21 Nov 2005 13:20:40 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Consensus call for adoption of TSLLAO as a working groupitem
In-reply-to: <4381143D.6010802@Research.Panasonic.COM>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Sathya Narayanan <sathya@research.panasonic.com>
Cc: Greg Daley <greg.daley@eng.monash.edu.au>, dna@eng.monash.edu.au
Message-id: <92e919fb0511202020h4c183596i3a6eb099dd7ddc45@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=pPCMVWbeLEFUFmoLzz+CExc26dT7P3hIMrGXtiAJgfowH8zyeEJfIGgOmNKvM86e3rjdSGu+733Vb61V8TF0EkLzRCCmvIyjSU+sbPrlNmQw+pQPtdpUryoDTJ5q4oGuKoz7aplZBJP1GapzK4QnIG3iK0OyONFDcEIGbDtwZ+Y=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <437E2A7A.5000808@eng.monash.edu.au>
 <4381143D.6010802@Research.Panasonic.COM>
Content-Transfer-Encoding: 7BIT

I am for TSLLAO to 1) be accepted as a WG I-D and 2) be advanced as a
separate document.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Sun Nov 20 23:56:26 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee3j8-0004gi-2C
	for dna-archive@megatron.ietf.org; Sun, 20 Nov 2005 23:56:26 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03316
	for <dna-archive@lists.ietf.org>; Sun, 20 Nov 2005 23:55:47 -0500 (EST)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNZ2NALKC9AT3N0@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 15:54:48 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 55900AB546; Mon,
 21 Nov 2005 15:54:43 +1100 (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 0D4864FB08; Mon, 21 Nov 2005 15:54:43 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL4pxh28307	for dna-list; Mon, 21 Nov 2005 15:51:59 +1100
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 jAL4pwu28303	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 15:51:58 +1100
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVNYYZZ2CA9AT0O5@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 15:51:47 +1100
Received: by localhost (Postfix, from userid 510)	id EDBFDAB55C; Mon,
 21 Nov 2005 15:51:46 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203])
	by moe.its.monash.edu.au (Postfix) with ESMTP id A8BCC4FB02	for
 <dna@eng.monash.edu.au>; Mon, 21 Nov 2005 15:51:45 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id o1so701518nzf for
 <dna@eng.monash.edu.au>; Sun, 20 Nov 2005 20:51:43 -0800 (PST)
Received: by 10.65.137.14 with SMTP id p14mr2477972qbn; Sun,
 20 Nov 2005 20:51:43 -0800 (PST)
Received: by 10.65.182.12 with HTTP; Sun, 20 Nov 2005 20:51:43 -0800 (PST)
Date: Mon, 21 Nov 2005 13:51:43 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
In-reply-to: <Pine.LNX.4.58.0511210400260.10749@rhea.tcs.hut.fi>
Sender: owner-dna@ecselists.eng.monash.edu.au
Cc: Greg Daley <greg.daley@eng.monash.edu.au>, Dna <dna@eng.monash.edu.au>
Message-id: <92e919fb0511202051i434bd6d4p2f6daeff120a97c5@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=Cv1PahxZsvctn2I3xuy44FTbD6QusPB5+CPmpc5jlWhp4uyWakoPJ/E+vEbp4LMGFY4lY0nhCCzKz75HGhC1rcAGM/EgOMyEAtTwRfbn93M9juR7M6M/yY8sXv4HIiEsOT3td0JVvBLlDJPky4+gdjEWR8Wl3YsKnmDqZ4Y6Nxo=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <437E2736.3010008@eng.monash.edu.au>
 <Pine.LNX.4.58.0511210400260.10749@rhea.tcs.hut.fi>
Content-Transfer-Encoding: 7BIT

I am in favor of adopting draft-pentland-dna-protocol3-00 as WG document.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 21 02:23:08 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee615-0006yc-Ut
	for dna-archive@megatron.ietf.org; Mon, 21 Nov 2005 02:23:08 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09974
	for <dna-archive@lists.ietf.org>; Mon, 21 Nov 2005 02:22:28 -0500 (EST)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVO48WEC7M9I91J7@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 18:22:50 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id CB0C8AB564; Mon,
 21 Nov 2005 18:22:31 +1100 (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 662FF4FB0A; Mon,
 21 Nov 2005 18:22:31 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL7LPZ29841	for dna-list; Mon, 21 Nov 2005 18:21:25 +1100
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 jAL7LPu29837	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 18:21:25 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVO479QS7G9ASS4J@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 18:21:13 +1100
Received: by localhost (Postfix, from userid 510)	id 9B4CF80002; Mon,
 21 Nov 2005 18:21:13 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 426F93C00B; Mon,
 21 Nov 2005 18:21:12 +1100 (EST)
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D92D31516; Mon,
 21 Nov 2005 08:21:01 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173])
 by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon,
 21 Nov 2005 08:20:50 +0100
Received: from esealmw114.eemea.ericsson.se ([153.88.200.5])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon,
 21 Nov 2005 08:20:49 +0100
Date: Mon, 21 Nov 2005 08:20:48 +0100
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: RE: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: 
 <F08E178900F39344AC894077E6AF74D101070814@esealmw114.eemea.ericsson.se>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
Thread-Index: AcXuQPRZ+VdIGE+0TKGiUxbqC2TOYgAKxVJg
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
X-OriginalArrivalTime: 21 Nov 2005 07:20:49.0394 (UTC)
 FILETIME=[190ABD20:01C5EE6C]
Content-Transfer-Encoding: 7BIT

I am in favor of adopting draft-pentland-dna-protocol3-00 as WG
document.

/Tero



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 21 04:13:54 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee7kH-0004Ml-Tj
	for dna-archive@megatron.ietf.org; Mon, 21 Nov 2005 04:13:54 -0500
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15202
	for <dna-archive@lists.ietf.org>; Mon, 21 Nov 2005 04:13:15 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVO84N0K309I923Q@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 20:13:47 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 150C080004; Mon,
 21 Nov 2005 20:13:38 +1100 (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 BA5C03C00B; Mon, 21 Nov 2005 20:13:37 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL9DUN31152	for dna-list; Mon, 21 Nov 2005 20:13:30 +1100
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 jAL9DUu31148	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 20:13:30 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVO846NSD89AT58J@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 20:13:16 +1100
Received: by localhost (Postfix, from userid 510)	id 402F380002; Mon,
 21 Nov 2005 20:13:16 +1100 (EST)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by larry.its.monash.edu.au (Postfix) with ESMTP id C1EB03C007; Mon,
 21 Nov 2005 20:13:14 +1100 (EST)
Received: from ep_ms13_bk (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IQA008Q9SA0W3@mailout1.samsung.com>; Mon,
 21 Nov 2005 18:13:12 +0900 (KST)
Received: from ep_spt02 (ms13.samsung.com [203.254.225.109])
 by ms13.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IQA00G4ESA0K6@ms13.samsung.com>; Mon,
 21 Nov 2005 18:13:12 +0900 (KST)
Content-return: prohibited
Date: Mon, 21 Nov 2005 09:13:05 +0000 (GMT)
From: SUBBA REDDYKOTA <subbareddy@samsung.com>
Subject: Re: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Reply-to: subbareddy@samsung.com
Message-id: <0IQA00G4FSA0K6@ms13.samsung.com>
MIME-version: 1.0
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: 7BIT
X-Priority: 3
Msgkey: 20051121091311452@subbareddy
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-MTR: 20051121091311452@subbareddy
X-EPLocale: en_US.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Generator: NamoMIME 6.0.0.1
Content-Transfer-Encoding: 7BIT

<HTML><HEAD>
<META http-equiv=Content-Type content='text/html; charset=windows-1252'>
<title>Samsung Enterprise Portal mySingle</title>
<style> P, td, li {font-family:Arial, arial; font-size:9pt; margin-top:5px;margin-bottom:5px;} body{font-family:Arial, arial; font-size:9pt;}</style>
</HEAD><BODY><p><p>&nbsp;Hi Greg,</p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I am in favor of adopting draft-pentland-dna-protocol3-00 as WG
document.

</p>
<p>&nbsp;</p>
<p>Thanks &amp; Regards,</p>
<p>Subba Reddy</p>
<p>&nbsp;</p><br><br>------- <b>Original Message</b> -------<br><b>Sender</b> : Greg Daley&lt;greg.daley@eng.monash.edu.au&gt;<br><b>Date</b>   : Nov 19, 2005 04:10<br><b>Title</b>  : [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3<br>Hi,
<br>
<br>This&nbsp;is&nbsp;the&nbsp;start&nbsp;of&nbsp;a&nbsp;two&nbsp;week&nbsp;consensus&nbsp;call&nbsp;as
<br>to&nbsp;whether&nbsp;the&nbsp;document&nbsp;draft-pentland-dna-protocol3
<br>as&nbsp;a&nbsp;working&nbsp;group&nbsp;document.
<br>
<br>The&nbsp;consensus&nbsp;call&nbsp;will&nbsp;end&nbsp;12:01am&nbsp;Saturday&nbsp;3rd&nbsp;December&nbsp;UTC
<br>
<br>The&nbsp;sense&nbsp;of&nbsp;the&nbsp;room&nbsp;was&nbsp;fairly&nbsp;strong&nbsp;to&nbsp;adopt&nbsp;the
<br>dna&nbsp;protocol&nbsp;proposal&nbsp;&nbsp;(23&nbsp;to&nbsp;nil)
<br>
<br>The&nbsp;document&nbsp;can&nbsp;be&nbsp;found&nbsp;at:
<br>
<br>http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
<br>
<br>Please&nbsp;send&nbsp;comments&nbsp;to&nbsp;the&nbsp;list.
<br>
<br>Greg
<br>
<br>
<br></BODY></HTML>



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 21 04:17:42 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee7ny-0004mj-N1
	for dna-archive@megatron.ietf.org; Mon, 21 Nov 2005 04:17:42 -0500
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15414
	for <dna-archive@lists.ietf.org>; Mon, 21 Nov 2005 04:17:04 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVO88ANSYM9BWGAQ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 20:16:40 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id F2E7880004; Mon,
 21 Nov 2005 20:16:34 +1100 (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 8A7DB3C012; Mon, 21 Nov 2005 20:16:34 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL9GWb31213	for dna-list; Mon, 21 Nov 2005 20:16:32 +1100
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 jAL9GVu31209	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 20:16:31 +1100
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVO87UZ9049BWGAQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 20:16:14 +1100
Received: by localhost (Postfix, from userid 510)	id 18C4DAB543; Mon,
 21 Nov 2005 20:16:14 +1100 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by curly.its.monash.edu.au (Postfix) with ESMTP id A69AE4FB15; Mon,
 21 Nov 2005 20:16:12 +1100 (EST)
Received: from ep_ms13_bk (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IQA009CDSEY9C@mailout2.samsung.com>; Mon,
 21 Nov 2005 18:16:10 +0900 (KST)
Received: from ep_spt02 (ms13.samsung.com [203.254.225.109])
 by ms13.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0IQA00FAGSEYS8@ms13.samsung.com>; Mon,
 21 Nov 2005 18:16:10 +0900 (KST)
Content-return: prohibited
Date: Mon, 21 Nov 2005 09:16:03 +0000 (GMT)
From: SUBBA REDDYKOTA <subbareddy@samsung.com>
Subject: Re: [DNA] Consensus call for adoption of TSLLAO as a working group item
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>
Cc: "dna@eng.monash.edu.au" <dna@eng.monash.edu.au>
Reply-to: subbareddy@samsung.com
Message-id: <0IQA00FAHSEYS8@ms13.samsung.com>
MIME-version: 1.0
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: 7BIT
X-Priority: 3
Msgkey: 20051121091609699@subbareddy
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-MTR: 20051121091609699@subbareddy
X-EPLocale: en_US.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Generator: NamoMIME 6.0.0.1
Content-Transfer-Encoding: 7BIT

<HTML><HEAD>
<META http-equiv=Content-Type content='text/html; charset=windows-1252'>
<title>Samsung Enterprise Portal mySingle</title>
<style> P, td, li {font-family:Arial, arial; font-size:9pt; margin-top:5px;margin-bottom:5px;} body{font-family:Arial, arial; font-size:9pt;}</style>
<style> P, td, li {font-family:Arial, arial; font-size:9pt; margin-top:5px;margin-bottom:5px;} body{font-family:Arial, arial; font-size:9pt;}</style>
</HEAD><BODY><p><p>Hi Greg,
<p>I am in favor of adopting draft-daley-ipv6-tsllao-02.txt

 as WG
document.
<p>Thanks &amp; Regards,</p>
<p>Subba Reddy</p>
<br><br>------- <b>Original Message</b> -------<br><b>Sender</b> : Greg Daley&lt;greg.daley@eng.monash.edu.au&gt;<br><b>Date</b>   : Nov 19, 2005 04:24<br><b>Title</b>  : [DNA] Consensus call for adoption of TSLLAO as a working group item<br>
<br>Hi,
<br>
<br>This&nbsp;is&nbsp;the&nbsp;start&nbsp;of&nbsp;a&nbsp;two&nbsp;week&nbsp;consensus&nbsp;call&nbsp;as
<br>to&nbsp;whether&nbsp;Tentative&nbsp;Source&nbsp;Link-Layer&nbsp;Address&nbsp;Options
<br>should&nbsp;be&nbsp;adopted&nbsp;as&nbsp;a&nbsp;working&nbsp;group&nbsp;item&nbsp;in&nbsp;DNA&nbsp;WG.
<br>
<br>These&nbsp;are&nbsp;currently&nbsp;documented&nbsp;in:&nbsp;draft-daley-ipv6-tsllao-02.txt
<br>
<br>While&nbsp;there&nbsp;was&nbsp;some&nbsp;interest&nbsp;in&nbsp;this&nbsp;at&nbsp;the&nbsp;IETF64&nbsp;session,
<br>the&nbsp;chairs&nbsp;recognize&nbsp;that&nbsp;few&nbsp;people&nbsp;had&nbsp;prepared&nbsp;to&nbsp;discuss
<br>this&nbsp;document&nbsp;before&nbsp;the&nbsp;session.
<br>
<br>Any&nbsp;feedback&nbsp;or&nbsp;queries&nbsp;about&nbsp;this&nbsp;consensus&nbsp;call&nbsp;can&nbsp;be
<br>sent&nbsp;to&nbsp;the&nbsp;chairs.
<br>
<br>The&nbsp;consensus&nbsp;call&nbsp;will&nbsp;end&nbsp;12:01am&nbsp;Saturday&nbsp;3rd&nbsp;December&nbsp;UTC
<br>
<br>The&nbsp;document&nbsp;can&nbsp;be&nbsp;found&nbsp;at:
<br>
<br>http://www.ietf.org/internet-drafts/draft-daley-ipv6-tsllao-02.txt
<br>
<br>Here&#39;s&nbsp;a&nbsp;(quick)&nbsp;summary&nbsp;of&nbsp;the&nbsp;discussion&nbsp;from&nbsp;the&nbsp;minutes
<br>(from&nbsp;JAK,&nbsp;with&nbsp;some&nbsp;recollections&nbsp;added&nbsp;by&nbsp;GD.&nbsp;&nbsp;Further
<br>merged&nbsp;minutes&nbsp;will&nbsp;be&nbsp;available&nbsp;shortly).
<br>---------
<br>...
<br>
<br>Suresh
<br>TSLLAO
<br>
<br>Normatively&nbsp;referenced&nbsp;by&nbsp;two&nbsp;documents,&nbsp;which&nbsp;are&nbsp;WG&nbsp;docs
<br>
<br>IPv6&nbsp;chairs&nbsp;want&nbsp;this&nbsp;done&nbsp;in&nbsp;DNA&nbsp;cause&nbsp;IPv6&nbsp;WG&nbsp;is&nbsp;going&nbsp;into&nbsp;hibernation
<br>
<br>Greg&nbsp;will&nbsp;present
<br>(briefly&nbsp;summarizes&nbsp;draft)
<br>
<br>Problem&nbsp;with&nbsp;SLLAO&nbsp;is&nbsp;that&nbsp;it&nbsp;overrides&nbsp;NC&nbsp;entry,&nbsp;would&nbsp;like&nbsp;to&nbsp;get
<br>unicast&nbsp;back&nbsp;to&nbsp;an&nbsp;optimistic&nbsp;address
<br>
<br>TSLLAO&nbsp;does&nbsp;not&nbsp;destroy&nbsp;NC&nbsp;entry
<br>
<br>Implementation&nbsp;in&nbsp;Linux&nbsp;available&nbsp;from&nbsp;Greg
<br>
<br>Suresh
<br>RS&nbsp;can&#39;t&nbsp;be&nbsp;unicast&nbsp;without&nbsp;optoin,&nbsp;need&nbsp;to&nbsp;do&nbsp;NS.&nbsp;Necessary&nbsp;to&nbsp;have
<br>this&nbsp;done,&nbsp;IANA&nbsp;allocation
<br>
<br>Mohan
<br>Solution&nbsp;all&nbsp;you&nbsp;need&nbsp;is&nbsp;Mac&nbsp;address&nbsp;for&nbsp;repsonse&nbsp;for&nbsp;RA,&nbsp;create&nbsp;NC
<br>entry&nbsp;for&nbsp;packet.&nbsp;Optimistic&nbsp;DAD&nbsp;is&nbsp;written&nbsp;such&nbsp;that&nbsp;create&nbsp;an&nbsp;NC
<br>entry&nbsp;if&nbsp;you&nbsp;don&#39;t&nbsp;have&nbsp;it.
<br>
<br>Greg
<br>Can&nbsp;send&nbsp;unicast&nbsp;packet&nbsp;back&nbsp;without&nbsp;a&nbsp;Neighbour&nbsp;Cache&nbsp;entry.
<br>
<br>Mohan
<br>Does&nbsp;create&nbsp;entry&nbsp;if&nbsp;no&nbsp;entry&nbsp;is&nbsp;there?
<br>
<br>Greg
<br>With&nbsp;oDAD,&nbsp;small&nbsp;chance&nbsp;of&nbsp;collision,&nbsp;if&nbsp;there&#39;s&nbsp;a&nbsp;collision,&nbsp;we&nbsp;want
<br>operations&nbsp;to&nbsp;be&nbsp;safe&nbsp;for&nbsp;original&nbsp;address&nbsp;owner,&nbsp;advantage&nbsp;if&nbsp;temporary,
<br>won&#39;t&nbsp;create&nbsp;or&nbsp;modify&nbsp;an&nbsp;entry&nbsp;(GD:&nbsp;if&nbsp;an&nbsp;entry&nbsp;exists).&nbsp;MAC&nbsp;binding&nbsp;will
<br>be&nbsp;delivered&nbsp;to&nbsp;another&nbsp;destiantion&nbsp;if&nbsp;there&nbsp;is&nbsp;another&nbsp;NC&nbsp;entry.
<br>
<br>Suresh
<br>WG&nbsp;item&nbsp;-&nbsp;8&nbsp;hands
<br>none&nbsp;against
<br>
<br>confirm&nbsp;on&nbsp;the&nbsp;list.
<br>
<br>Greg
<br>Know&nbsp;it&#39;s&nbsp;a&nbsp;late&nbsp;agenda&nbsp;item,&nbsp;not&nbsp;trying&nbsp;to&nbsp;shove&nbsp;something&nbsp;through.
<br>
<br>Suresh
<br>Should&nbsp;this&nbsp;be&nbsp;in&nbsp;a&nbsp;separate&nbsp;document?&nbsp;5&nbsp;hands&nbsp;for
<br>Part&nbsp;of&nbsp;solution&nbsp;document?&nbsp;2
<br>
<br>confirm&nbsp;on&nbsp;list
<br>
<br>(discussion&nbsp;of&nbsp;whether&nbsp;separate&nbsp;or&nbsp;same)
<br>
<br>---------
<br>
<br>
<br>
<br>Please&nbsp;be&nbsp;aware&nbsp;that&nbsp;if&nbsp;adopted,&nbsp;further&nbsp;discussion&nbsp;on&nbsp;whether
<br>the&nbsp;document&nbsp;should&nbsp;stand-alone&nbsp;or&nbsp;be&nbsp;merged&nbsp;into&nbsp;an&nbsp;existing
<br>document&nbsp;will&nbsp;occur,&nbsp;with&nbsp;another&nbsp;consensus&nbsp;call.
<br>
<br>Please&nbsp;send&nbsp;comments&nbsp;to&nbsp;the&nbsp;list.
<br>
<br>Greg
<br>
<br>
<br></BODY></HTML>



From dna-owner@webcamserver.eng.monash.edu.au Mon Nov 21 04:41:17 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ee8An-0008Vx-0V
	for dna-archive@megatron.ietf.org; Mon, 21 Nov 2005 04:41:17 -0500
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16728
	for <dna-archive@lists.ietf.org>; Mon, 21 Nov 2005 04:40:38 -0500 (EST)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
 with ESMTP id <01LVO7MODZZY9BWG91@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 21 Nov 2005 20:00:03 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 32F9180005; Mon,
 21 Nov 2005 19:59:56 +1100 (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 CAC3F3C00C; Mon, 21 Nov 2005 19:59:55 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id jAL8rMS30926	for dna-list; Mon, 21 Nov 2005 19:53:22 +1100
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 jAL8rMu30922	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 21 Nov 2005 19:53:22 +1100
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LVO7EAZWYK9I90G7@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 21 Nov 2005 19:53:11 +1100
Received: by localhost (Postfix, from userid 510)	id 5194C80002; Mon,
 21 Nov 2005 19:53:11 +1100 (EST)
Received: from dns1.tilab.com (dns1.tilab.com [163.162.42.4])
	by larry.its.monash.edu.au (Postfix) with ESMTP id DC5DB3C00A; Mon,
 21 Nov 2005 19:53:07 +1100 (EST)
Received: from iowa2k01a.cselt.it ([163.162.242.201])
 by dns1.cselt.it (PMDF V6.0-025 #38895)
 with ESMTP id <0IQA0054ARCHDC@dns1.cselt.it>; Mon,
 21 Nov 2005 09:53:05 +0100 (MET)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
 Microsoft SMTPSVC(6.0.3790.211); Mon, 21 Nov 2005 09:53:05 +0100
Date: Mon, 21 Nov 2005 09:53:04 +0100
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Greg Daley <greg.daley@eng.monash.edu.au>, Dna <dna@eng.monash.edu.au>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9E26@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
X-MIME-Autoconverted: from quoted-printable to 8bit by
 webcamserver.eng.monash.edu.au id jAL8rMu30923
Content-type: text/plain; charset=iso-8859-1
Importance: normal
Thread-Topic: [DNA] Confirmation of sense of room to adopt
 draft-pentland-dna-protocol3
thread-index: AcXsdDMLScMQxg6wTHCIznHm7Y4degCBLFuA
Content-Class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-OriginalArrivalTime: 21 Nov 2005 08:53:05.0187 (UTC)
 FILETIME=[FCA1B730:01C5EE78]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA16728

Hi Greg,

I'm in favor of adopting draft-pentland-dna-protocol3-00 as WG item.

Regards,
--Gerardo=20

> -----Original Message-----
> From: owner-dna@ecselists.eng.monash.edu.au=20
> [mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of Greg Daley
> Sent: venerd=EC 18 novembre 2005 20.11
> To: Dna
> Subject: [DNA] Confirmation of sense of room to adopt=20
> draft-pentland-dna-protocol3
>=20
> Hi,
>=20
> This is the start of a two week consensus call as
> to whether the document draft-pentland-dna-protocol3
> as a working group document.
>=20
> The consensus call will end 12:01am Saturday 3rd December UTC
>=20
> The sense of the room was fairly strong to adopt the
> dna protocol proposal  (23 to nil)
>=20
> The document can be found at:
>=20
> http://tools.ietf.org/wg/dna/draft-pentland-dna-protocol3-00.txt
>=20
> Please send comments to the list.
>=20
> Greg
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



