From dna-owner@webcamserver.eng.monash.edu.au Sun Oct 02 21:38:53 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMFI5-0006cz-F1
	for dna-archive@megatron.ietf.org; Sun, 02 Oct 2005 21:38:53 -0400
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 VAA12985
	for <dna-archive@lists.ietf.org>; Sun, 2 Oct 2005 21:38:50 -0400 (EDT)
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 <01LTR9SHS4X099WZAA@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 03 Oct 2005 11:37:27 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0D450AB55C; Mon,
 03 Oct 2005 11:37:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 3C7004FB0A; Mon,
 03 Oct 2005 11:37:13 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j931ZUT04755	for dna-list; Mon, 03 Oct 2005 11:35:30 +1000
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 j931ZTd04751	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 03 Oct 2005 11:35:29 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTR9Q7OJ769FMMAG@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 03 Oct 2005 11:35:24 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id ADD3D8000D; Mon,
 03 Oct 2005 11:35:23 +1000 (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 92BCD3C00C; Mon,
 03 Oct 2005 11:35:23 +1000 (EST)
Date: Mon, 03 Oct 2005 11:35:18 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-F266BA856E429E94592508D938C0@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: dna@eng.monash.edu.au
Message-id: <43408AD6.6050605@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.4 (X11/20050908)
References: <BAY106-F266BA856E429E94592508D938C0@phx.gbl>
Content-Transfer-Encoding: 7BIT

Bernard Aboba wrote:
>> He thought that it is questionable to assume that:
>>
>>    1) Every network has a router.
>>    2) you can name a network using one of its prefixes.
> 
> There are certainly adhoc networks in which there is no router.   
> However, detecting attachment to such a network is quite difficult, 
> because nodes may join and leave and therefore there is no L3 
> invariant.  That is why the DNAv4 reachability test cannot be used to 
> detect attachment to adhoc networks, but rather adhoc attachment is 
> concluded after failiure of all other approaches (reachability test, 
> DHCPv4, etc.)

OK.

> I would also agree that there are situations in which a network cannot 
> be named using one of its prefixes.  In DNAv4, a private network is not 
> suitable for identification because it is not unique.

DNAv6 might have another option.  What do you think of requiring
the router(s) on such a link to configure a ULA prefix?  The prefix
need not necessarily be advertised in a PIO in an RA, but could be
used for link identification.

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Sun Oct 02 23:07:06 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMGfR-0007ub-QH
	for dna-archive@megatron.ietf.org; Sun, 02 Oct 2005 23:07:06 -0400
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 XAA14975
	for <dna-archive@lists.ietf.org>; Sun, 2 Oct 2005 23:07:02 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTRCWV8HLW9FMMNP@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 03 Oct 2005 13:06:56 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D2BFA80011; Mon,
 03 Oct 2005 13:06:15 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 6DF693C00C; Mon, 03 Oct 2005 13:06:15 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9335VI05972	for dna-list; Mon, 03 Oct 2005 13:05:31 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9335Ud05968	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 03 Oct 2005 13:05:30 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTRCVTYM7M9FMMNP@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 03 Oct 2005 13:05:29 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id E9EECAB559; Mon,
 03 Oct 2005 13:05:25 +1000 (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 BFFFE4FB03; Mon,
 03 Oct 2005 13:05:25 +1000 (EST)
Date: Mon, 03 Oct 2005 13:05:20 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <8A76136424391244A5CF016533708537AD6149@mvebe101.NOE.Nokia.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Michael.G.Williams@nokia.com
Cc: yohba@tari.toshiba.com, STDS-802-21@listserv.ieee.org,
        dna@eng.monash.edu.au
Message-id: <43409FF0.1010900@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.4 (X11/20050908)
References: <8A76136424391244A5CF016533708537AD6149@mvebe101.NOE.Nokia.com>
Content-Transfer-Encoding: 7BIT

In the IETF DNA group we have been using the term "link" in the sense
described in RFC 2460 and other IPv6 documents; that is:

    link        - a communication facility or medium over which nodes can
                  communicate at the link layer, i.e., the layer
                  immediately below IPv6.  Examples are Ethernets (simple
                  or bridged); PPP links; X.25, Frame Relay, or ATM
                  networks; and internet (or higher) layer "tunnels",
                  such as tunnels over IPv4 or IPv6 itself.

For DNA we are trying to allow a host to determine whether its existing
network-layer configuration is likely to be still valid or whether it
needs to initiate reconfiguration.  So whether we call it a "link" or
not, the above is the thing we are trying to identify, since it
represents the extent over which the configuration will be valid.

So far we have been using network prefix information for the
identification (not necessarily using a single prefix as a fixed
identifier because the prefixes used can change over time).  What
I am trying to work out is whether there is a good reason why we
need to be able to use non-prefix information to identify this "link".

Any thoughts?
Brett.

Michael.G.Williams@nokia.com wrote:
> Colleagues,
> 
> Please also continue on this discussion of the identification of "link"
> as relevant to the MIH header definition, especially for referring to
> the link in off-link ES/CS references vs. on-link references. Gabriel
> mentioned Ipv6 as a use case to consider for definition of L3 "link",
> and please note IPv6 ND perhaps even more deep use of the concept. Is it
> important that MIH and L3 have interrelated concepts of "link" for any
> reasons (QoS, Application awareness, security, link adaptation, resource
> management, ???)
> 
> The use case of cellular "link" is important, and indicates the
> definition of "link" at L2 needs to be flexible. Describing it in terms
> of MAC service neighbors might be viable within the 802. If the
> definition of L2 link for use in the MIH header is to be media specific,
> then might there be trouble intpreting its meaning/use in a remote MIH
> function? 
> 
> Best Regards,
> Michael
> 
> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@TARI.TOSHIBA.COM] 
> Sent: Friday, September 30, 2005 8:47 AM
> To: STDS-802-21@listserv.ieee.org
> Subject: Re: [DNA] Prefix information for link identification in DNA
> 
> Andrea,
> 
> The PoA definition below is going to the direction that the notion of
> PoA is less associated with the notion of "link", as opposed to what you
> made in your previous general statement which I have fully agreed.
> Or you may be introducing a new definition of "link" as "a specific type
> of communication relationship", which seems to be too ambiguous.
> 
> Yoshihiro Ohba
> 
> 
> 
> On Fri, Sep 30, 2005 at 11:25:04AM -0400, Andrea Francini wrote:
>> Trying to finalize one part of the ongoing discussion: the PoA
> definition.
>> I have the impression that some people consider the capability of 
>> supporting MIH as part of the definition of PoA, while other people 
>> don't, giving it only a network connectivity value.
>>
>> What about the following:
>>
>> 1. General definition of PoA:
>>
>> a. "PoA is the first point in the network that acts as the UE 
>> counterpart for a specific type of communication relationship (e.g.,
> L2, L3, MIH)."
>>
>> 2. Accordingly, the following three specific definitions could be
> added:
>> b. "L2 PoA is the network-side endpoint of the L2 link by which the UE
> 
>> connects to the network."
>>
>> c. "L3 PoA is the closest network counterpart for the UE that requires
> 
>> an L3 address to be identified in UE-generated messages."
>>
>> d. "MIH PoA is the closest network counterpart of the UE for MIH
> exchanges."
>>
>> Thanks,
>>
>> Andrea
>>
>>
>> "Stefano M. Faccin" wrote:
>>> Peretz, nobody denies that. The issue here is that what you have
> been saying doe not allow for deployments that do not use any MIH
> services at L2. Even if you may not believe these deployments will
> happen, there are vendors and operators that do believe that their
> networks will only use MIH services at L3, at least for the initial
> deployments. Thjerefore our model and definitions must allow for this.
> In this model, there is no MIH @ L2, and the PoA is in the subnet where
> the UE gets its IP address.
>>> Stefano
>>>
>>> ________________________________
>>>
>>> From: ext Peretz Feder [mailto:pfeder@LUCENT.COM]
>>> Sent: Fri 9/30/2005 10:06 AM
>>> To: STDS-802-21@listserv.ieee.org
>>> Subject: Re: [802.21] [DNA] Prefix information for link 
>>> identification in DNA
>>>
>>> "I do not understand how any one would conclude that the MIH
> services are only between UE and the AP/BS."
>>> The discussion is PoA and not services. The 1st PoA could be L2 for
> IS and CS. With no PoA at L2, the poor UE will have no MIH services
> until IP is established. The performance will be very different, not to
> mention a UE with a bridging only attributes, such as 802.16 terminal
> with only Ethernet CS (no IP CS).
>>> Nobody is saying MIH services are strictly between UE and BS.
> Performance will be better when PoA L2 MIH is established.
>>> Peretz
>>>
>>> On 9/30/2005 10:50 AM, Srinivas.Sreemanthula@nokia.com wrote:
>>>
>>>         The MIIS is provisioned between MIH in UE to a network
> counter part any
>>>         where in the network. This network node can either act as a
> proxy info
>>>         server or an info server. We also identified MIIS requires
> L3 and hence
>>>         the WG went through the exercise of identifying all the UL
> requirements
>>>         and establish coordination with IETF. However, in that
> discussion, there
>>>         was no reference to whether the AP/BS was MIH or non-MIH
> capable.
>>>         Even if we leave out the info services from the discussion,
> I do not
>>>         understand how any one would conclude that the MIH services
> are only
>>>         between UE and the AP/BS.
>>>
>>>
>>>
>>>                 -----Original Message-----
>>>                 From: ext Peretz Feder [mailto:pfeder@lucent.com]
>>>                 Sent: Friday, September 30, 2005 9:39 AM
>>>                 To: Sreemanthula Srinivas (Nokia-NRC/Dallas)
>>>                 Cc: STDS-802-21@listserv.ieee.org
>>>                 Subject: Re: [802.21] [DNA] Prefix information for
> link
>>>                 identification in DNA
>>>
>>>                 Are you indicating attaching to a non MIH enabled
> AP/BS and
>>>                 receiving MIH IS over R4 from a remote MIH info
> server?
>>>
>>>                 On 9/30/2005 10:27 AM,
> Srinivas.Sreemanthula@nokia.com wrote:
>>>
>>>
>>>                         Did we miss the whole discussion of MIH
> information services?
>>>
>>>                         ________________________________
>>>
>>>                                 From: ext Peretz Feder
> [mailto:pfeder@LUCENT.COM]
>>>                                 Sent: Friday, September 30, 2005
> 9:16 AM
>>>                                 To: STDS-802-21@LISTSERV.IEEE.ORG
>>>                                 Subject: Re: [802.21] [DNA] Prefix 
>>> information for link
>>>
>>>
>>>                 identification
>>>
>>>
>>>                         in DNA
>>>
>>>
>>>                                 "you have first to be very clear
> about what you're attaching"
>>>                                 I would think that in 802.21, we 
>>> first attach the UE's
>>>
>>>
>>>                 MIH to a BS/AP
>>>
>>>
>>>                         that supports MIH capability.
>>>
>>>                                 On 9/30/2005 8:55 AM, Stefano M.
> Faccin wrote:
>>>
>>>                                         Mike, well said!
>>>                                         Stefano
>>>
>>>                                         
>>> ________________________________
>>>
>>>                                         From: ext Mike Moreton
> [mailto:mm2006@MAILSNARE.NET]
>>>                                         Sent: Fri 9/30/2005 3:09 AM
>>>                                         To:
> STDS-802-21@listserv.ieee.org
>>>                                         Subject: Re: [802.21] [DNA]
> Prefix information for link
>>>                         identification in DNA
>>>
>>>
>>>
>>>                                         To extend (I think!) 
>>> Stefano's point, before
>>>
>>>
>>>                 determining what the PoA
>>>
>>>
>>>                         is, you have first to be very clear about 
>>> what you're
>>>
>>>
>>>                 attaching.  Just
>>>
>>>
>>>                         saying "the terminal" makes no sense,
> because different layers in the
>>>                         terminal's protocol stack attach to
> different places in the network.
>>>                                         For example, the PHY layer 
>>> attaches to the AP,
>>>
>>>
>>>                 but the TCP layer
>>>
>>>
>>>                         attaches to the destination host.
>>>
>>>                                         Mike.
>>>
>>>
>>>
>>>                                                 -----Original
> Message-----
>>>                                                 From: Stefano M.
> Faccin
>>>                         [mailto:stefano.faccin@NOKIA.COM]
>>>                                                 Sent: Friday,
> September 30, 2005 1:08 AM
>>>                                                 To:
> STDS-802-21@listserv.ieee.org
>>>                                                 Subject: Re: 
>>> [802.21] [DNA] Prefix
>>>
>>>
>>>                 information for link
>>>
>>>
>>>                                                 identification in 
>>> DNA
>>>
>>>
>>>                                                 Yoshihiro,
>>>                                                 I'm not sure why 
>>> should restrict the
>>>
>>>
>>>                 term PoA to have only a
>>>
>>>
>>>                                                 L2 meaning as you 
>>> suggest below. I
>>>
>>>
>>>                 think we should
>>>
>>>
>>>                                                 distinguish clearly
> between L2 PoA and L3 PoA.
>>>                         For me, the L3
>>>                                                 PoA is where the
> terminal gets IP conenctivity.
>>>                         E.g. for GPRS
>>>                                                 the L3 PoA is the IP
> 
>>> link on which the
>>>
>>>
>>>                 GGSN is located. In
>>>
>>>
>>>                                                 L2, PoA is the point
> where the access-specific
>>>                         L2 connection
>>>                                                 terminates (e.g. an
> AP in 802.11).
>>>                                                 Stefano



From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 03 12:23:06 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMT5m-000198-4s
	for dna-archive@megatron.ietf.org; Mon, 03 Oct 2005 12:23:06 -0400
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 MAA15895
	for <dna-archive@lists.ietf.org>; Mon, 3 Oct 2005 12:23:02 -0400 (EDT)
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 <01LTS4PLN52W99X14S@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 04 Oct 2005 02:22:13 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id E42FFAB558; Tue,
 04 Oct 2005 02:22:07 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id A2A394FB07; Tue,
 04 Oct 2005 02:22:07 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j93GKTT15114	for dna-list; Tue, 04 Oct 2005 02:20:29 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j93GKTd15110	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 04 Oct 2005 02:20:29 +1000
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 <01LTS4N8VZYA99X14S@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 04 Oct 2005 02:20:14 +1000
Received: by localhost (Postfix, from userid 510)	id 7581EAB557; Tue,
 04 Oct 2005 02:20:14 +1000 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 356144FB06	for
 <dna@eng.monash.edu.au>; Tue, 04 Oct 2005 02:20:11 +1000 (EST)
Received: by zproxy.gmail.com with SMTP id z3so1036150nzf for
 <dna@eng.monash.edu.au>; Mon, 03 Oct 2005 09:20:11 -0700 (PDT)
Received: by 10.36.79.19 with SMTP id c19mr316365nzb; Mon,
 03 Oct 2005 09:20:11 -0700 (PDT)
Received: by 10.36.3.3 with HTTP; Mon, 03 Oct 2005 09:20:10 -0700 (PDT)
Date: Tue, 04 Oct 2005 01:20:10 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <433B56BE.10107@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>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb0510030920nf977a61y563dbb838da45f62@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:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
 b=cFyfjJmpGog0nUyRte1G/8g37GquhGYkZH0T9DPR3OQcvvsp8ta8pvFiIrxQKIsxeIYmzv+h4jOvAQnymRhRHHEM0q3Glw5On02j88tUqXOycJIXd1n698rgjJemg8GYMOBHU0iN+MHrBnhZmy468jmtU4A//0v/rePwNVmxDYs=
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05)
References: <433B56BE.10107@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Dear Brett

Thanks for your trouble advancing DNA again.

> Though it was in reference to CPL, Keith Moore raised an issue that is
> relevant to both of the link-identification solution proposals (LinkID
> and CompleteRA).  He thought that it is questionable to assume that:
>
>    1) Every network has a router.
>    2) you can name a network using one of its prefixes.
>
> (I hope that's right Keith - I pulled it out of the minutes)
>
> Both of the proposed solutions use prefix information for link
> identification, though neither relies on using a single prefix as
> the link name for eternity.  Both allow the prefix(es) used to
> change over time and are designed so that hosts can cope with
> those changes.  However both also rely on routers to distribute
> this information to hosts which falls apart if assumption 1)
> above is invalid.
>
> So if a link has no router and no prefixes except the link-local
> prefix (which will be the same for all links) we have a problem.
>
> I'm not sure what we can reasonably do at layer 3 if there is(are)
> no router(s) present on the link to help the hosts identify the
> link.  (Any ideas?)

DNA solution checks for link change to verify whether a host has valid
IP configuration so that the host can have Internet Connectivity
without disruption.

For example, a MIPv6 MN may use DNA procedure to determine that it's
CoA is no longer valid, so that it can quickly get a new CoA and send
a BU accordingly.

If we assume a link which doesn't have neither a router nor a (global)
prefix, I wonder whether a host can have Internet Connectivity in such
a link at all.

In general, for Internet Connectivity, i.e. to be able to send/
receive a packet to/ from off-link node, a hosts needs at least
1) a (partially) reachable default router
2) a valid (global) IP address

* In fact DNA tasks were originally to verify the above two
configurations as in the following first PS draft.

http://www.diffeo.com/drafts/draft-jinchoi-dna-dnav6-prob-00.txt

In a link without a router nor a prefix, I wonder which IP
configuration a host needs to change when it moves to a link. In fact,
in such a environment, it's not even clear to me either what
constitutes a link or DNA is needed at all.

So for the time being, IMHO, we'd better focus on a link with a router
and a prefix. I think that DNA is mostly needed in such a link.

> If there are routers present then I think that prefix information
> should be usable for identification.  If there are no global
> prefixes then maybe the solution can require that routers configure
> a ULA prefix (it might simply be used in an identifier and not
> advertised in a PIO)?

I wonder whether a host can have a global IP address in a link if
there is no global address assigned to the link.

> I guess I would like to find out:
>
> 1. Does anyone think we can come up with a reasonable solution at
>    layer 3 that can deal with links that have no routers?
>
> 1a. Should we?

I don't think we can design a meaningful DNA solution in such a link.

> 2. If we can't/won't, and thus we can make use of routers in
>    identifying other links, can anyone explain why prefix
>    information cannot/must not be used in some way for identifying
>    links?  (Note that using prefix information doesn't require
>    picking a single fixed prefix to act as the identifier)
>
> 2a. If it is *possible* to use prefix information in general to
>     identify links, then is there a good reason why we should
>     design an identification scheme that allows the use of non-
>     prefix information for link identification?

I think that it's ok to use a prefix for link identification.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 04 23:28:51 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMzxZ-00044V-Ls
	for dna-archive@megatron.ietf.org; Tue, 04 Oct 2005 23:28:51 -0400
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 XAA24972
	for <dna-archive@lists.ietf.org>; Tue, 4 Oct 2005 23:28:45 -0400 (EDT)
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 <01LTU69WA2HO9ARKI7@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 05 Oct 2005 13:28:23 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 90C3A8000D; Wed,
 05 Oct 2005 13:28:19 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 4AE073C003; Wed, 05 Oct 2005 13:28:19 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j953Qon07649	for dna-list; Wed, 05 Oct 2005 13:26:50 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j953Qnd07645	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 05 Oct 2005 13:26:49 +1000
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 <01LTU67UUF069ARLHQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 05 Oct 2005 13:26:41 +1000
Received: by localhost (Postfix, from userid 510)	id 0C7638000E; Wed,
 05 Oct 2005 13:26:40 +1000 (EST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	(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 A99613C005; Wed, 05 Oct 2005 13:26:39 +1000 (EST)
Received: from eamrcnt770.exu.ericsson.se (mail1att.ericy.com. [138.85.133.17])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id j953QaxN006599; Tue,
 04 Oct 2005 22:26:37 -0500
Received: from noah.lmc.ericsson.se ([142.133.1.1])
 by eamrcnt770.exu.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id S83T9KJ6; Tue, 04 Oct 2005 22:26:36 -0500
Received: from dhcp723-115.rnet.lmc.ericsson.se
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
	by noah.lmc.ericsson.se (8.12.10/8.12.10) with ESMTP id j953QZ6l022174; Tue,
 04 Oct 2005 23:26:35 -0400 (EDT)
Date: Tue, 04 Oct 2005 23:26:12 -0400 (EDT)
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] Call for agenda items dna WG IETF64
In-reply-to: 
 <8DA338857B4F404282EE2088005079EA0142561F@eammlex037-nb.lmc.ericsson.se>
Sender: owner-dna@ecselists.eng.monash.edu.au
X-X-Sender: suresh@dhcp723-115.rnet.lmc.ericsson.se
To: dna@eng.monash.edu.au
Cc: Greg Daley <greg.daley@eng.monash.edu.au>
Reply-to: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Message-id: <Pine.LNX.4.61.0510042325001.15494@dhcp723-115.rnet.lmc.ericsson.se>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-Sybari-Trust: af06efd1 856a4233 9092d233 00000139
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05)
References: 
 <8DA338857B4F404282EE2088005079EA0142561F@eammlex037-nb.lmc.ericsson.se>
Content-Transfer-Encoding: 7BIT

Hi Folks,
  We have a requested a slot for the dna wg at the IETF64 meeting in Vancouver.
We will be required to submit an agenda soon.
So here is a call for agenda items.  Please send a mail to Greg and me, letting
us know:

1. The name of the draft you wish to present.
2. Whether you intend to submit a new revision of the draft by IETF 64.
3. How much time you need to present the draft.
4. Whether this is a charter item (charter items get priority).

Thanks
Greg and Suresh



From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 04 23:29:55 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMzyd-0004Ot-12
	for dna-archive@megatron.ietf.org; Tue, 04 Oct 2005 23:29:55 -0400
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 XAA25034
	for <dna-archive@lists.ietf.org>; Tue, 4 Oct 2005 23:29:51 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTU6A35IO69FMXQV@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 05 Oct 2005 13:28:42 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 9B10C80010; Wed,
 05 Oct 2005 13:28:28 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 54E2D3C003; Wed, 05 Oct 2005 13:28:28 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j953Rhu07663	for dna-list; Wed, 05 Oct 2005 13:27:43 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j953Rhd07659	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 05 Oct 2005 13:27:43 +1000
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 <01LTU68XK8RQ9ARLHQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 05 Oct 2005 13:27:33 +1000
Received: by localhost (Postfix, from userid 510)	id 09D5A8000F; Wed,
 05 Oct 2005 13:27:32 +1000 (EST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	(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 09A8A3C010; Wed, 05 Oct 2005 13:27:31 +1000 (EST)
Received: from eamrcnt770.exu.ericsson.se (mail1att.ericy.com. [138.85.133.17])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id j953RUvZ006722; Tue,
 04 Oct 2005 22:27:30 -0500
Received: from noah.lmc.ericsson.se ([142.133.1.1])
 by eamrcnt770.exu.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id S83T9KLG; Tue, 04 Oct 2005 22:27:29 -0500
Received: from dhcp723-115.rnet.lmc.ericsson.se
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
	by noah.lmc.ericsson.se (8.12.10/8.12.10) with ESMTP id j953RR6l022185; Tue,
 04 Oct 2005 23:27:27 -0400 (EDT)
Date: Tue, 04 Oct 2005 23:27:04 -0400 (EDT)
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] WGLC for draft-ietf-dna-link-information-02.txt
In-reply-to: 
 <8DA338857B4F404282EE2088005079EA0142561E@eammlex037-nb.lmc.ericsson.se>
Sender: owner-dna@ecselists.eng.monash.edu.au
X-X-Sender: suresh@dhcp723-115.rnet.lmc.ericsson.se
To: dna@eng.monash.edu.au
Cc: Greg Daley <greg.daley@eng.monash.edu.au>,
        Alper Yegin <alper.yegin@yegin.org>
Reply-to: Suresh Krishnan <suresh.krishnan@ericsson.com>
Message-id: <Pine.LNX.4.61.0510042326230.15494@dhcp723-115.rnet.lmc.ericsson.se>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-Sybari-Trust: 7a6f0e14 856a4233 9092d233 00000139
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05)
References: 
 <8DA338857B4F404282EE2088005079EA0142561E@eammlex037-nb.lmc.ericsson.se>
Content-Transfer-Encoding: 7BIT

This mail starts a 2 week WG Last Call for comments for the following
dna working group document

draft-ietf-dna-link-information-02.txt

to be sent to the IESG for consideration as an INFORMATIONAL RFC.

Please review the document carefully, and send your feedback to the
list. Please also indicate whether or not you believe that this
document is ready to go to the IESG.

The last call will end on 2005/10/18. Please comment as early as
possible to allow the authors to incorporate the comments before the
internet draft cutoff deadline of 2005/10/24.

Thanks
Greg and Suresh
(dna chairs)



From dna-owner@webcamserver.eng.monash.edu.au Sat Oct 08 13:59:32 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EOIyq-0003YQ-JP
	for dna-archive@megatron.ietf.org; Sat, 08 Oct 2005 13:59:32 -0400
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 NAA04537
	for <dna-archive@lists.ietf.org>; Sat, 8 Oct 2005 13:59:30 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTZ7JQ3EQM9FNGZI@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sun, 09 Oct 2005 03:59:24 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0848CAB544; Sun,
 09 Oct 2005 03:59:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id B1E384FB05; Sun, 09 Oct 2005 03:59:13 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j98HtWg03476	for dna-list; Sun, 09 Oct 2005 03:55:32 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j98HtVd03472	for
 <dna@ecselists.eng.monash.edu.au>; Sun, 09 Oct 2005 03:55:31 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LTZ7F2SNMS9FNGZI@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sun,
 09 Oct 2005 03:55:29 +1000
Received: by localhost (Postfix, from userid 510)	id 5920180003; Sun,
 09 Oct 2005 03:55:29 +1000 (EST)
Received: from hotmail.com (bay106-f26.bay106.hotmail.com [65.54.161.36])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 05FE93C009; Sun,
 09 Oct 2005 03:55:27 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat,
 08 Oct 2005 10:55:26 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Sat,
 08 Oct 2005 17:55:26 +0000 (GMT)
Date: Sat, 08 Oct 2005 10:55:26 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <43408AD6.6050605@eng.monash.edu.au>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: brett.pentland@eng.monash.edu.au
Cc: dna@eng.monash.edu.au
Message-id: <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 08 Oct 2005 17:55:26.0669 (UTC)
 FILETIME=[76B0CFD0:01C5CC31]
Content-Transfer-Encoding: 7BIT

>There are certainly adhoc networks in which there is no router.   However, 
>detecting attachment to such a network is quite difficult, because nodes 
>may join and leave and therefore there is no L3 invariant.  That is why the 
>DNAv4 reachability test cannot be used to detect attachment to adhoc 
>networks, but rather adhoc attachment is concluded after failiure of all 
>other approaches (reachability test, DHCPv4, etc.)

James Carlson has recently pointed out that there really is no intrinsic 
reason why DNA cannot be applied to networks without a router, and has 
proposed modifications to DNAv4 to allow this.  James has proposed that DNA 
be able to use any peer that is known to be stable as an indicator of 
network attachment.  This could be a router, or it could be another device.  
About the only fundamental limitation is that "network anchor" probably 
shouldn't obtain its address dynamically.

>>I would also agree that there are situations in which a network cannot be 
>>named using one of its prefixes.  In DNAv4, a private network is not 
>>suitable for identification because it is not unique.

Along these lines, James has also proposed that confirmation of a "network 
anchor" enable the plumbing of all network configurations relating to that 
anchor.  The result of this is that networks are not named using their 
prefixes;  they are named based on the IP address/MAC address of the network 
anchor.

It seems to me that James' comments apply equally to both DNAv4 and DNAv6 
and call into question some of the fundamental assumptions that have been 
made relating to DNA.





From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 10 03:46:14 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EOsMQ-0005f5-1U
	for dna-archive@megatron.ietf.org; Mon, 10 Oct 2005 03:46:14 -0400
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 DAA22705
	for <dna-archive@lists.ietf.org>; Mon, 10 Oct 2005 03:46:11 -0400 (EDT)
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 <01LU1EPXJPKE99XUM2@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 10 Oct 2005 17:45:55 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BD404AB545; Mon,
 10 Oct 2005 17:45:51 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 5F7374FB04; Mon, 10 Oct 2005 17:45:51 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9A7iBZ01355	for dna-list; Mon, 10 Oct 2005 17:44:11 +1000
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 j9A7iAd01351	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 10 Oct 2005 17:44:10 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU1ENHAN1C8WYPCT@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 10 Oct 2005 17:43:53 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4F00F80002; Mon,
 10 Oct 2005 17:43:53 +1000 (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 2A79F3C00E; Mon,
 10 Oct 2005 17:43:53 +1000 (EST)
Date: Mon, 10 Oct 2005 17:43:47 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: dna@eng.monash.edu.au
Message-id: <434A1BB3.5040804@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.4 (X11/20050908)
References: <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
Content-Transfer-Encoding: 7BIT

Bernard Aboba wrote:
>> There are certainly adhoc networks in which there is no router.   
>> However, detecting attachment to such a network is quite difficult, 
>> because nodes may join and leave and therefore there is no L3 
>> invariant.  That is why the DNAv4 reachability test cannot be used to 
>> detect attachment to adhoc networks, but rather adhoc attachment is 
>> concluded after failiure of all other approaches (reachability test, 
>> DHCPv4, etc.)
> 
> James Carlson has recently pointed out that there really is no intrinsic 
> reason why DNA cannot be applied to networks without a router, and has 
> proposed modifications to DNAv4 to allow this.  James has proposed that 
> DNA be able to use any peer that is known to be stable as an indicator 
> of network attachment.  This could be a router, or it could be another 
> device.  About the only fundamental limitation is that "network anchor" 
> probably shouldn't obtain its address dynamically.

OK.

>>> I would also agree that there are situations in which a network 
>>> cannot be named using one of its prefixes.  In DNAv4, a private 
>>> network is not suitable for identification because it is not unique.
> 
> Along these lines, James has also proposed that confirmation of a 
> "network anchor" enable the plumbing of all network configurations 
> relating to that anchor.  The result of this is that networks are not 
> named using their prefixes;  they are named based on the IP address/MAC 
> address of the network anchor.

They might not need to be named that way either.  If there's some way
to select the network anchor then that device might be able to select
an identifier that is used for naming.  That way if the network anchor
goes away and is replaced by another, the name needn't go away with it.

> It seems to me that James' comments apply equally to both DNAv4 and 
> DNAv6 and call into question some of the fundamental assumptions that 
> have been made relating to DNA.

Decoupling DNA from both routers and prefixes has some attractions; 
stability of naming and reliance on routers, for example.  I guess we
need to look at the cost, and perhaps more importantly how a scheme
based on these network anchors would interoperate with devices/links
that don't have any support for such a scheme.

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 10 18:54:57 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EP6Xo-0006OP-U4
	for dna-archive@megatron.ietf.org; Mon, 10 Oct 2005 18:54:57 -0400
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 SAA00838
	for <dna-archive@lists.ietf.org>; Mon, 10 Oct 2005 18:54:52 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU2AG1C52U9FNN6P@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 11 Oct 2005 08:54:27 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id AC3C080003; Tue,
 11 Oct 2005 08:54:08 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 5DD963C007; Tue, 11 Oct 2005 08:54:08 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9AMpOP12319	for dna-list; Tue, 11 Oct 2005 08:51:24 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9AMpNd12315	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 11 Oct 2005 08:51:23 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU2ACBOG7Q8WYS15@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 11 Oct 2005 08:51:09 +1000
Received: by localhost (Postfix, from userid 510)	id 4CB9C80005; Tue,
 11 Oct 2005 08:51:09 +1000 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 891163C00A	for
 <dna@eng.monash.edu.au>; Tue, 11 Oct 2005 08:51:07 +1000 (EST)
Received: by zproxy.gmail.com with SMTP id z3so1554735nzf for
 <dna@eng.monash.edu.au>; Mon, 10 Oct 2005 15:51:06 -0700 (PDT)
Received: by 10.36.67.16 with SMTP id p16mr517576nza; Mon,
 10 Oct 2005 15:51:06 -0700 (PDT)
Received: by 10.36.3.3 with HTTP; Mon, 10 Oct 2005 15:51:06 -0700 (PDT)
Date: Tue, 11 Oct 2005 07:51:06 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <92e919fb0510101551q3788c455u3cd8a8e21541067d@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=Ih/nOwt9xvT2yK/nfy5BTArmRx22FeBhlAgFy/K+ajHnl31XbqrvtvLibsf2jg2d/ASgW9rW54im5LDP+lhgcaVxIfguXioxLEydKz9O4GZg9AHGNifT2O/IPtKrzFa0+HD51XCj9a19piKpLsk7Kr2vXczva2wcvyN6BPF5Ug4=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <43408AD6.6050605@eng.monash.edu.au>
 <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
Content-Transfer-Encoding: 7BIT

Dear Bernard

> >There are certainly adhoc networks in which there is no router.   However,
> >detecting attachment to such a network is quite difficult, because nodes
> >may join and leave and therefore there is no L3 invariant.  That is why the
> >DNAv4 reachability test cannot be used to detect attachment to adhoc
> >networks, but rather adhoc attachment is concluded after failiure of all
> >other approaches (reachability test, DHCPv4, etc.)
>
> James Carlson has recently pointed out that there really is no intrinsic
> reason why DNA cannot be applied to networks without a router, and has
> proposed modifications to DNAv4 to allow this. James has proposed that DNA
> be able to use any peer that is known to be stable as an indicator of
> network attachment.  This could be a router, or it could be another device.
> About the only fundamental limitation is that "network anchor" probably
> shouldn't obtain its address dynamically.

DNA aims to ascertain the validity of its IP configuration for
Internet connectivity, such as valid IP address or default router. So,
when a host's IP configuration is no longer valid, it can quickly
perform proper procedures, such as getting CoA and sending BU, to
re-establish IP connectivity.

However, in case of a link without a router, I wonder what IP
configuration parameter a host need to  verify for Internet
connectivity. Also I have difficulty finding out what is the use of
DNA in such a link.

> >>I would also agree that there are situations in which a network cannot be
> >>named using one of its prefixes.  In DNAv4, a private network is not
> >>suitable for identification because it is not unique.
>
> Along these lines, James has also proposed that confirmation of a "network
> anchor" enable the plumbing of all network configurations relating to that
> anchor.  The result of this is that networks are not named using their
> prefixes;  they are named based on the IP address/MAC address of the network
> anchor.

The notion of 'network anchor' is not clear to me yet. However, if we
ssume routers are network anchors, it may cause trouble to name a
network based on IP/ MAC address of routers, in case there are
multiple routers in a link.

Right now, CPL propose to name a link/ network with 'the set of all
prefixes on the link'. Similarly, we may name a link/ network with
'the set of all routers/ network anchors on the link'.

But it's difficult to identify a router in IP layer because there may
not be a global IP address for a router (interface).

> It seems to me that James' comments apply equally to both DNAv4 and DNAv6
> and call into question some of the fundamental assumptions that have been
> made relating to DNA.

According to DNA goals, RFC 4235,

   Detecting Network Attachment (DNA) is the process by which a host
   collects the appropriate information and detects the identity of its
   currently attached link to ascertain the validity of its IP
   configuration.

Do you want to re-investigate the above?

Thanks in advance for your kind consideration.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 11 03:17:57 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPEOb-0001zf-Ec
	for dna-archive@megatron.ietf.org; Tue, 11 Oct 2005 03:17:57 -0400
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 DAA04758
	for <dna-archive@lists.ietf.org>; Tue, 11 Oct 2005 03:17:51 -0400 (EDT)
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 <01LU2RYZMS1I9ARUV8@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 11 Oct 2005 17:16:43 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A459480004; Tue,
 11 Oct 2005 17:16:34 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 5BF163C00B; Tue, 11 Oct 2005 17:16:34 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9B7Fnf18384	for dna-list; Tue, 11 Oct 2005 17:15:49 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9B7Fmd18380	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 11 Oct 2005 17:15:48 +1000
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 <01LU2RXR589S99Y6GO@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 11 Oct 2005 17:15:35 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0747EAB542; Tue,
 11 Oct 2005 17:15:35 +1000 (EST)
Received: from [130.194.252.110] (knuth.eng.monash.edu.au [130.194.252.110])
	by curly.its.monash.edu.au (Postfix) with ESMTP id DEDE04FB09; Tue,
 11 Oct 2005 17:15:34 +1000 (EST)
Date: Tue, 11 Oct 2005 17:15:34 +1000
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434A1BB3.5040804@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brett Pentland <brett.pentland@eng.monash.edu.au>
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, dna@eng.monash.edu.au
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <434B6696.7070008@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en, en-us
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328
 Fedora/1.7.6-1.2.5
References: <BAY106-F2663CD26D8D40A8916A1C093870@phx.gbl>
 <434A1BB3.5040804@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Bernard,

I've got some ideas which may assist moving forward.
They're listed below.

Brett Pentland wrote:
> Bernard Aboba wrote:
> 
>>> There are certainly adhoc networks in which there is no router.   
>>> However, detecting attachment to such a network is quite difficult, 
>>> because nodes may join and leave and therefore there is no L3 
>>> invariant.  That is why the DNAv4 reachability test cannot be used to 
>>> detect attachment to adhoc networks, but rather adhoc attachment is 
>>> concluded after failiure of all other approaches (reachability test, 
>>> DHCPv4, etc.)
>>
>>
>> James Carlson has recently pointed out that there really is no 
>> intrinsic reason why DNA cannot be applied to networks without a 
>> router, and has proposed modifications to DNAv4 to allow this.  James 
>> has proposed that DNA be able to use any peer that is known to be 
>> stable as an indicator of network attachment.  This could be a router, 
>> or it could be another device.  About the only fundamental limitation 
>> is that "network anchor" probably shouldn't obtain its address 
>> dynamically.
> 
> 
> OK.
> 
>>>> I would also agree that there are situations in which a network 
>>>> cannot be named using one of its prefixes.  In DNAv4, a private 
>>>> network is not suitable for identification because it is not unique.
>>
>>
>> Along these lines, James has also proposed that confirmation of a 
>> "network anchor" enable the plumbing of all network configurations 
>> relating to that anchor.  The result of this is that networks are not 
>> named using their prefixes;  they are named based on the IP 
>> address/MAC address of the network anchor.
> 
> 
> They might not need to be named that way either.  If there's some way
> to select the network anchor then that device might be able to select
> an identifier that is used for naming.  That way if the network anchor
> goes away and is replaced by another, the name needn't go away with it.
> 
>> It seems to me that James' comments apply equally to both DNAv4 and 
>> DNAv6 and call into question some of the fundamental assumptions that 
>> have been made relating to DNA.
> 
> 
> Decoupling DNA from both routers and prefixes has some attractions; 
> stability of naming and reliance on routers, for example.  I guess we
> need to look at the cost, and perhaps more importantly how a scheme
> based on these network anchors would interoperate with devices/links
> that don't have any support for such a scheme.


James' idea of decoupling the link identification from both routers
and prefixes does sound like an interesting idea, but I think there
are some practical constraints which affect the performance of
such a system on non adhoc networks.

I guess that my primary interest is identifying change for hosts
with ongoing sessions on the Internet.   This change can then be
used to undertake mobility operations and re-establish packet flow.
Where no router exists, the primary value upon change is in
stopping packet transmissions (as they won't succeed), and notifying
applications.

Changes to how link-change detection works in adhoc networks
with routers depends on the IPv6 subnet model being used though.

Previously we looked at unicast reachability detection for
ND hosts, using NS/NA to a device which was known to be on-link.
This allowed fast checking when the addressing and routing
configuration were still valid, but required timeout to identify
that link-change had occurred.   From what I can tell,
any scheme which uses unicast reachability probing requires
timeout before detecting if change has occurred.

Therefore, it's necessary to make use of multicast discovery
mechanisms in order to rapidly detect change.

For non adhoc hosts, Router Discovery makes a good transportation
mechanism for the link-identification information, even if the
identifier is not associated with a prefix.  Its multicast discovery
capabilities allow any identifier advertiser to immediately
identify change.

For adhoc hosts, it may be possible to use a non-prefix identifier
associated with the link.  This would presuppose adhoc hosts participate
in a routing protocol discovery which could pass such an identifier
though.

In order to supply authorization for the link-identity, this
identifier may be tied to the Internet gateway, with adhoc nodes
readvertising the link identifier sent in RAs from the router.
Authorization information could either be sent by adhoc nodes
or refer the host directly to the router.

Where no router exists, the identifier could be supplied by
a network anchor, although this may not be able to provide
explicit authorization.

If we assume that it's OK to continue to operate with IPv6
Router Discovery for non adhoc nodes, it still makes sense
to allow for introduction of non-prefix link identifiers for
these and other purposes.

To that end I suggest that DNA WG:

* Identifies if the IPv6 Subnet model for adhocs
   requires non-prefix link identifiers.

* Allow for non-prefix link identifiers to be used and tracked
   by DNAv6 hosts

* Define message formats which allow non-prefix link identifiers
   to be sent in RAs.

* Investigate requirements for configuring non-prefix link identifiers
   as a (separate) extension to the DNAv6 specification.

* Investigate requirements for passing link identification in adhoc
   networks.

The second and third points can be done initially without
clarification of the other points, so non-adhoc hosts
can still detect change using these identifiers, even if they
don't understand the special meaning of these identifiers
from a routing protocol perspective.

Does this make sense?

Greg



From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 11 06:30:54 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPHPK-0002ln-9i
	for dna-archive@megatron.ietf.org; Tue, 11 Oct 2005 06:30:54 -0400
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 GAA12822
	for <dna-archive@lists.ietf.org>; Tue, 11 Oct 2005 06:30:50 -0400 (EDT)
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 <01LU2YQX2BB499Y09N@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 11 Oct 2005 20:30:10 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BCBE5AB558; Tue,
 11 Oct 2005 20:30:06 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 64A5B4FB09; Tue,
 11 Oct 2005 20:30:06 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9BASoQ20572	for dna-list; Tue, 11 Oct 2005 20:28:50 +1000
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 j9BASnd20568	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 11 Oct 2005 20:28:49 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU2YOXTJ1G9FNQR8@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 11 Oct 2005 20:28:31 +1000
Received: by localhost (Postfix, from userid 510)	id 1A05F80003; Tue,
 11 Oct 2005 20:28:30 +1000 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 05CB33C006; Tue,
 11 Oct 2005 20:28:29 +1000 (EST)
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D2433687; Tue,
 11 Oct 2005 12:28:26 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173])
 by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue,
 11 Oct 2005 12:27:18 +0200
Received: from esealmw114.eemea.ericsson.se ([153.88.200.5])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue,
 11 Oct 2005 12:27:18 +0200
Date: Tue, 11 Oct 2005 12:27:17 +0200
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: RE: [DNA] Prefix information for link identification in DNA
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@gmail.com>,
        Bernard Aboba <bernard_aboba@hotmail.com>
Cc: brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: 
 <F08E178900F39344AC894077E6AF74D10107075C@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] Prefix information for link identification in DNA
Thread-Index: AcXN7bYoR97e2yHeRf2lL3YSiIac5gAXrHyA
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
X-OriginalArrivalTime: 11 Oct 2005 10:27:18.0696 (UTC)
 FILETIME=[5B72FA80:01C5CE4E]
Content-Transfer-Encoding: 7BIT


> > James Carlson has recently pointed out that there really is no
intrinsic
> > reason why DNA cannot be applied to networks without a router, and
has
> > proposed modifications to DNAv4 to allow this. James has proposed
that
> DNA
> > be able to use any peer that is known to be stable as an indicator
of
> > network attachment.  This could be a router, or it could be another
> device.
> > About the only fundamental limitation is that "network anchor"
probably
> > shouldn't obtain its address dynamically.
> 
> DNA aims to ascertain the validity of its IP configuration for
> Internet connectivity, such as valid IP address or default router. So,
> when a host's IP configuration is no longer valid, it can quickly
> perform proper procedures, such as getting CoA and sending BU, to
> re-establish IP connectivity.
> 
> However, in case of a link without a router, I wonder what IP
> configuration parameter a host need to  verify for Internet
> connectivity. Also I have difficulty finding out what is the use of
> DNA in such a link.

How can it be made sure that if the node moves from one adhoc network to
another the "network anchor" identities won't happen to be the same?
After all there is no communication between these two networks. Surely
it can be made unlikely to happen by constructing the identity of
several components, but the probability would still exist. I can't stop
thinking the original simple idea of adding an identifier to the RA, but
unfortunately it had this shortcoming that it was not possible (other
than manually configuring) to make sure that adjacent networks don't use
the same identifier.

I'm also a bit worried about possible complications to the protocol if
transition from networks including a router to a network that doesn't
have a router will be supported. I would guess the transition other way
around is simpler, because when sending an RS upon detecting "link up"
the node will receive an RA.

Tero



From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 11 18:57:36 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPT3w-00013w-8c
	for dna-archive@megatron.ietf.org; Tue, 11 Oct 2005 18:57:36 -0400
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 SAA08556
	for <dna-archive@lists.ietf.org>; Tue, 11 Oct 2005 18:57:31 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU3OUDLX7U8WZ0PW@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 12 Oct 2005 08:57:32 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D2F44AB542; Wed,
 12 Oct 2005 08:57:21 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 92A364FB05; Wed, 12 Oct 2005 08:57:21 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9BMuXi29668	for dna-list; Wed, 12 Oct 2005 08:56:33 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9BMuWd29664	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 12 Oct 2005 08:56:32 +1000
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 <01LU3OT6JZEA99Y5HN@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 12 Oct 2005 08:56:24 +1000
Received: by localhost (Postfix, from userid 510)	id 1734FAB559; Wed,
 12 Oct 2005 08:56:24 +1000 (EST)
Received: from hotmail.com (bay106-dav16.bay106.hotmail.com [65.54.161.88])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 057BC4FB06; Wed,
 12 Oct 2005 08:56:21 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue,
 11 Oct 2005 15:56:20 -0700
Received: from 131.107.0.104 by BAY106-DAV16.phx.gbl with DAV; Tue,
 11 Oct 2005 22:56:20 +0000
Date: Tue, 11 Oct 2005 15:56:20 -0700
From: Bernard Aboba <Bernard_Aboba@hotmail.com>
Subject: RE: [DNA] Prefix information for link identification in DNA
In-reply-to: 
 <F08E178900F39344AC894077E6AF74D10107075C@esealmw114.eemea.ericsson.se>
X-Originating-IP: [131.107.0.104]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: "'Tero Kauppinen (JO/LMF)'" <tero.kauppinen@ericsson.com>,
        "'JinHyeock Choi'" <jinchoe@gmail.com>
Cc: brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <BAY106-DAV161715F07A42D90896653A93780@phx.gbl>
Message-id: <004301c5ceb6$fed07050$82091cac@ntdev.corp.microsoft.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Index: AcXN7bYoR97e2yHeRf2lL3YSiIac5gAXrHyAABp62yA=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 11 Oct 2005 22:56:20.0548 (UTC)
 FILETIME=[FEE16040:01C5CEB6]
Content-Transfer-Encoding: 7BIT

>How can it be made sure that if the node moves from one adhoc network to
>another the "network anchor" identities won't happen to be the same?

In DNAv4, the "network anchor" identities are defined to include both the IP
address and the MAC address, so that duplication of both would be required
to cause confusion. 

This works as long as the "network anchor" is actually an anchor, not a buoy
-- it cannot also be mobile.  

>I'm also a bit worried about possible complications to the protocol if
>transition from networks including a router to a network that doesn't
>have a router will be supported. 

At least with respect to DNAv4, it doesn't appear to matter whether the
"network anchor" is a router or not.  This is, I think an important
advantage of approaches that rely on ARP/ND vs. ones that rely on RS/RA. 



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 12 03:20:07 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPauF-00052C-65
	for dna-archive@megatron.ietf.org; Wed, 12 Oct 2005 03:20:07 -0400
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 DAA02211
	for <dna-archive@lists.ietf.org>; Wed, 12 Oct 2005 03:20:03 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU46E7ZRK89FNZUK@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 12 Oct 2005 17:19:58 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 1220CAB544; Wed,
 12 Oct 2005 17:19:44 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id C397D4FB04; Wed, 12 Oct 2005 17:19:43 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9C7Im803038	for dna-list; Wed, 12 Oct 2005 17:18:48 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9C7Imd03034	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 12 Oct 2005 17:18:48 +1000
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 <01LU46CZKYFG9ARWWS@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 12 Oct 2005 17:18:44 +1000
Received: by localhost (Postfix, from userid 510)	id 7D1D5AB542; Wed,
 12 Oct 2005 17:18:44 +1000 (EST)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 615274FB04; Wed,
 12 Oct 2005 17:18:43 +1000 (EST)
Received: from jurassic.eng.sun.com ([129.146.228.50])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j9C7IfvD022212; Wed,
 12 Oct 2005 01:18:42 -0600 (MDT)
Received: from [129.158.215.244]
 (dhcp-cbjs05-215-09.PRC.Sun.COM [129.158.215.244])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id j9C7IbtQ695987
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed,
 12 Oct 2005 00:18:39 -0700 (PDT)
Date: Wed, 12 Oct 2005 00:19:05 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-DAV161715F07A42D90896653A93780@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <Bernard_Aboba@hotmail.com>
Cc: "'Tero Kauppinen (JO/LMF)'" <tero.kauppinen@ericsson.com>,
        "'JinHyeock Choi'" <jinchoe@gmail.com>,
        brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <434CB8E9.8030401@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: <BAY106-DAV161715F07A42D90896653A93780@phx.gbl>
Content-Transfer-Encoding: 7BIT

Bernard Aboba wrote:
>>How can it be made sure that if the node moves from one adhoc network to
>>another the "network anchor" identities won't happen to be the same?
> 
> 
> In DNAv4, the "network anchor" identities are defined to include both the IP
> address and the MAC address, so that duplication of both would be required
> to cause confusion. 
> 
> This works as long as the "network anchor" is actually an anchor, not a buoy
> -- it cannot also be mobile.  

Can't it be confused in other cases?

Suppose I have a server with VLAN support that is part of multiple 
VLANs. The server uses the same MAC address on all its VLANs as is 
normal with VLAN capable network interfaces.

Suppose in addition the multiple VLANs are separate private address 
space domains - all using 10.0.0.0/8 addresses.

Now the server can have the same IP address on all its VLANs as well
(presumably requires running Xen or vmvare on the server to make sure 
the server doesn't get confused).

Thus on VLAN 1 the server has MAC address M1 and IP address 10.1.2.3.
The default routers on VLAN1 are 10.0.0.1 and 10.0.0.2.

On VLAN 2 the server has MAC address M1 and IP address 10.1.2.3.
The default routers on VLAN2 (different than on 1) are 10.0.1.1 and 
10.0.1.2.

In this case the fact that MAC address M1 can be reached at IP address 
10.1.2.3 does not mean that the IP configuration is the same; the host 
needs to get the different default routers when moving between the links.

    Erik




From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 12 11:05:29 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPiAY-0003Cd-Ld
	for dna-archive@megatron.ietf.org; Wed, 12 Oct 2005 11:05:29 -0400
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 LAA26844
	for <dna-archive@lists.ietf.org>; Wed, 12 Oct 2005 11:05:22 -0400 (EDT)
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 <01LU4MM9VNNU9AOS2K@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 13 Oct 2005 01:04:25 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 50C1C80002; Thu,
 13 Oct 2005 01:04:21 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id F05953C007; Thu, 13 Oct 2005 01:04:20 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9CF0Us08431	for dna-list; Thu, 13 Oct 2005 01:00:30 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9CF0Rd08425	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 13 Oct 2005 01:00:27 +1000
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 <01LU4MH4IPH699XVBL@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 13 Oct 2005 01:00:12 +1000
Received: by localhost (Postfix, from userid 510)	id 74AC2AB542; Thu,
 13 Oct 2005 01:00:12 +1000 (EST)
Received: from hotmail.com (bay106-f31.bay106.hotmail.com [65.54.161.41])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 4C1A64FB05; Thu,
 13 Oct 2005 01:00:11 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed,
 12 Oct 2005 08:00:09 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Wed,
 12 Oct 2005 15:00:09 +0000 (GMT)
Date: Wed, 12 Oct 2005 08:00:09 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434CB8E9.8030401@sun.com>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: erik.nordmark@sun.com
Cc: tero.kauppinen@ericsson.com, jinchoe@gmail.com,
        brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 12 Oct 2005 15:00:09.0757 (UTC)
 FILETIME=[A3C664D0:01C5CF3D]
Content-Transfer-Encoding: 7BIT

FYI, the text of James' comments on DNAv4 are included below:

Date: Wed, 12 Oct 2005 08:33:24 -0400
From: James Carlson <james.d.carlson@sun.com>
To: dhcwg@ietf.org
Cc: Margaret Wasserman <margaret@thingmagic.com>, Bernard Aboba 
<aboba@internaut.com>, cheshire@apple.com
Subject: proposed DNA update to remove "default gateway" references

As discussed with Bernard Aboba and the other authors, I feel that
this document ends up being a bit clearer and more general if the
references to "default gateways" are removed.  Though it's certainly
the case that many nodes do, there's no necessary reason that any IP
node must have a default gateway, and on networks where there isn't
such a gateway, the current draft makes it appear as though "only"
default routes need apply.

In fact, any test address on the network will serve the purpose,
though it seems likely that the best choice is to probe a local
router.

The changes below reflect that rewording.  I realize that time has
already run out for this draft, so if the consensus is to publish
as-is rather than consider any rewording, I'm happy enough with that.



--- dnav4.txt   Wed Oct 12 08:17:12 2005
+++ dnav4-new.txt       Wed Oct 12 08:23:57 2005
@@ -199,19 +199,20 @@
following parameters:

.nf
- [1] The IPv4 and MAC address of the default gateway(s)
+ [1] The IPv4 and MAC address of one or more other
+     ("test") nodes on the network.

  [2] The IPv4 configuration parameters, including
      the assigned address and lease expiration time
.fi

From the set of networks which have operable IPv4 address(es)
associated with them, the host selects a subset, and attempts
to confirm the configuration for each network, using
the reachability test described in Section 2.1.

If the reachability test is successful, verifying bi-directional
-connectivity to the default gateway(s),
+connectivity to the test nodes,
the host SHOULD continue to use the operable routable
IPv4 address associated with the confirmed network, without
needing to re-acquire it, allowing the host to bypass Duplicate
@@ -252,7 +253,7 @@
     confirm configuration of an IPv4 Link-Local
     address or a statically assigned IPv4 address.

-[b] The host does not know the default gateway(s) on
+[b] The host does not know the address of any test node on
     that network.  In this case, insufficient information
     is available to carry out the reachability test.

@@ -260,13 +261,15 @@
     The reachability test utilizes ARP which is insecure.
.fi

-For a particular network, the host MAY test reachability
-to the primary default gateway, or it MAY test reachability
-to both the primary
-and secondary default gateways, in series or in parallel.
+For a particular network, the host SHOULD use the addresses of
+local routers (preferably default gateways) as its test nodes,
+although any address on the target network will suffice.  If more than
+one address is known, those addresses may be tested in series or in
+parallel.
In order to ensure configuration
-validity,  the host SHOULD
-only configure default gateway(s) which pass the reachability test.
+validity, the host SHOULD
+only configure routes for which the next hop address passes the
+reachability test.  Other routes SHOULD be re-learned.

In situations where more than one network is available on a given link,
or the network configuration has changed,
@@ -283,10 +286,10 @@
.in +0.3i
The reachability test is performed by sending an ARP Request.
The host MUST set the target protocol address (ar$tpa) to the
-IPv4 address of the default gateway being tested, and the sender protocol
+IPv4 address of the address being tested, and the sender protocol
address field (ar$spa) to its own IPv4 address.

The ARP Request MUST use the
-host MAC address as the source, and the default gateway MAC
+host MAC address as the source, and the test node MAC
address as the destination.  The host includes its MAC address
in the sender hardware address field
(ar$sha), and sets the target hardware address field (ar$tha)
@@ -315,7 +318,7 @@
to confirming its IPv4 configuration, and MAY respond to ARP
Requests.

-Sending an ICMP Echo Request [RFC792] to the default gateway IPv4
+Sending an ICMP Echo Request [RFC792] to an IPv4
address does not provide the same level of assurance since this may
require an ARP Request/Reply exchange.  Where the host has moved
between two private networks, this could result in ARP cache
@@ -322,13 +325,13 @@
pollution.

Where a host moves from one private network to another, an ICMP Echo
-Request can result in an ICMP Echo Response even when the default
-gateway has changed, as long as the IPv4 address remains the same.
+Request can result in an ICMP Echo Response even when the MAC
+address has changed, as long as the IPv4 address remains the same.
This can occur,  for example, where a host moves from one home
network using prefix 192.168/16 to another one.  In addition, if the
ping is sent with TTL > 1, then an ICMP Echo Response can be received
from an off-link gateway.  As a result, if the MAC address of the
-default gateway is not checked, the host can mistakenly confirm
+test node is not checked, the host can mistakenly confirm
attachment, potentially resulting in an address conflict.
As a result, sending of an ICMP Echo Request SHOULD NOT be used as a
substitute for the reachability test.





From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 12 21:48:00 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPsCO-0003UU-Dn
	for dna-archive@megatron.ietf.org; Wed, 12 Oct 2005 21:48:00 -0400
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 VAA16868
	for <dna-archive@lists.ietf.org>; Wed, 12 Oct 2005 21:47:56 -0400 (EDT)
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 <01LU5905VPWA9ARYVL@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 13 Oct 2005 11:45:32 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id E2FB6AB548; Thu,
 13 Oct 2005 11:45:28 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 93D584FB06; Thu, 13 Oct 2005 11:45:28 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9D1iXa16196	for dna-list; Thu, 13 Oct 2005 11:44:33 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9D1iWd16192	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 13 Oct 2005 11:44:32 +1000
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 <01LU58YNPKUS9ARSR6@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 13 Oct 2005 11:44:16 +1000
Received: by localhost (Postfix, from userid 510)	id 4E03E80003; Thu,
 13 Oct 2005 11:44:16 +1000 (EST)
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 0FAE73C003; Thu,
 13 Oct 2005 11:44:14 +1000 (EST)
Received: from jurassic.eng.sun.com ([129.146.224.130])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j9D1iC1L008964; Wed,
 12 Oct 2005 19:44:13 -0600 (MDT)
Received: from [129.158.215.244]
 (dhcp-cbjs05-215-09.PRC.Sun.COM [129.158.215.244])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id j9D1i9Of235746
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed,
 12 Oct 2005 18:44:11 -0700 (PDT)
Date: Wed, 12 Oct 2005 18:44:37 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: tero.kauppinen@ericsson.com, jinchoe@gmail.com,
        brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <434DBC05.5090308@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: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
Content-Transfer-Encoding: 7BIT

Bernard Aboba wrote:

I don't have a problem with the desire to generalize things to not 
assume routers, but the devil is in the proverbial details.

> +For a particular network, the host SHOULD use the addresses of
> +local routers (preferably default gateways) as its test nodes,
> +although any address on the target network will suffice. 

As somebody else pointed out, you can't select any address as a test 
one, since that node might be mobile as well. So having the PDA in my 
left pocket pick the IP+MAC of the PDA in my right pocket would be 
catastrophic, since both of them are likely to move at the same time.
So we should change the above to
 > +For a particular network, the host SHOULD use the addresses of
 > +local routers (preferably default gateways) as its test nodes,
 > +although any address on the target network that is know to not be 
moving around will suffice.

This leads to the question of how can a host determine which test 
address can be safely used short of manual configuration.
If this is the case I think we should make this explicit in the 
document, for instance by saying:
	Unless the the host has been manually configured with a test
	node, or otherwise knows a test node which is it certain is not
	mobile, the host should select the default router(s) as the test
	node(s).

   Erik



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 12 23:30:12 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPtnI-0003lK-Oa
	for dna-archive@megatron.ietf.org; Wed, 12 Oct 2005 23:30:12 -0400
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 XAA20368
	for <dna-archive@lists.ietf.org>; Wed, 12 Oct 2005 23:30:08 -0400 (EDT)
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 <01LU5CNJ1YTW99Y6PQ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 13 Oct 2005 13:29:57 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C7AD6AB55C; Thu,
 13 Oct 2005 13:29:49 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 730C14FB04; Thu,
 13 Oct 2005 13:29:49 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9D3TGh17461	for dna-list; Thu, 13 Oct 2005 13:29:16 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9D3TFd17457	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 13 Oct 2005 13:29:15 +1000
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 <01LU5CMHQUR89ARQUM@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 13 Oct 2005 13:29:00 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id AAF49AB543; Thu,
 13 Oct 2005 13:28:59 +1000 (EST)
Received: from [130.194.252.110] (knuth.eng.monash.edu.au [130.194.252.110])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 8BB204FB0A; Thu,
 13 Oct 2005 13:28:59 +1000 (EST)
Date: Thu, 13 Oct 2005 13:28:59 +1000
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434DBC05.5090308@sun.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Erik Nordmark <erik.nordmark@sun.com>
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, tero.kauppinen@ericsson.com,
        jinchoe@gmail.com, brett.pentland@eng.monash.edu.au,
        dna@eng.monash.edu.au
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <434DD47B.1030406@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en, en-us
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328
 Fedora/1.7.6-1.2.5
References: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
 <434DBC05.5090308@sun.com>
Content-Transfer-Encoding: 7BIT

Hi Erik,

Erik Nordmark wrote:
> Bernard Aboba wrote:
[cut]
> 
> This leads to the question of how can a host determine which test 
> address can be safely used short of manual configuration.
> If this is the case I think we should make this explicit in the 
> document, for instance by saying:
>     Unless the the host has been manually configured with a test
>     node, or otherwise knows a test node which is it certain is not
>     mobile, the host should select the default router(s) as the test
>     node(s).

I'd like to know how you think that relates to DNA for IPv6 though.

I'm not sure this can be used to rapidly determine change like RS/RA
can (due to the solicitation going to all-routers).

Greg



From dna-owner@webcamserver.eng.monash.edu.au Thu Oct 13 02:52:00 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPwwa-0001n0-5n
	for dna-archive@megatron.ietf.org; Thu, 13 Oct 2005 02:52:00 -0400
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 CAA27698
	for <dna-archive@lists.ietf.org>; Thu, 13 Oct 2005 02:51:54 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU5JNC2V4S9FO05H@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 13 Oct 2005 16:50:41 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id BA1DFAB546; Thu,
 13 Oct 2005 16:50:29 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 743A14FB08; Thu, 13 Oct 2005 16:50:29 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9D6nl120055	for dna-list; Thu, 13 Oct 2005 16:49:47 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9D6nkd20051	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 13 Oct 2005 16:49:47 +1000
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 <01LU5JM54EVE9ARV6T@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 13 Oct 2005 16:49:32 +1000
Received: by localhost (Postfix, from userid 510)	id 26CC1AB545; Thu,
 13 Oct 2005 16:49:32 +1000 (EST)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by curly.its.monash.edu.au (Postfix) with ESMTP id D59344FB04; Thu,
 13 Oct 2005 16:49:30 +1000 (EST)
Received: from jurassic.eng.sun.com ([129.146.106.105])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j9D6nSvD012897; Thu,
 13 Oct 2005 00:49:29 -0600 (MDT)
Received: from [129.158.215.244]
 (dhcp-cbjs05-215-09.PRC.Sun.COM [129.158.215.244])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id j9D6nPC5355555
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed,
 12 Oct 2005 23:49:27 -0700 (PDT)
Date: Wed, 12 Oct 2005 23:49:52 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434DD47B.1030406@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: greg.daley@eng.monash.edu.au
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, tero.kauppinen@ericsson.com,
        jinchoe@gmail.com, brett.pentland@eng.monash.edu.au,
        dna@eng.monash.edu.au
Message-id: <434E0390.8090208@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: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
 <434DBC05.5090308@sun.com> <434DD47B.1030406@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Greg Daley wrote:

> I'd like to know how you think that relates to DNA for IPv6 though.

Good question.

For IPv6 we've been assuming that
  - we have global IPv6 prefixes (thus no confusion with 192.168.0.0/255 
being used in multiple places)
  - Router Solicitation/Advertisement being reasonably efficient (more 
efficient than sending to a DHCP server and getting a reply)

As a result of this, we can do better than IPv4 in that we can use a 
RS/RA exchange to both verify whether we are on the same link, and also 
get the new configuration information if we have moved to a different link.

So it doesn't seem that useful to follow the IPv4 model of first 
verifying that an IP+MAC address is still present on the link, since if 
we have moved we'd need to send additional packets.


*If* we want DNAv6 to handle the case when we don't have global IPv6 
prefixes, I'd suggest we do that by allowing something other than 
prefixes be used as the link identifier (as Keith Moore suggested).
This would still assume that something is sending out router 
advertisements; but a node can send a router advertisement without 
claiming to be a default router so this doesn't actually assume that 
there is a a router. One just need one or more nodes that will send out 
the RAs.

    Erik



From dna-owner@webcamserver.eng.monash.edu.au Thu Oct 13 13:34:27 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQ6yJ-00046N-He
	for dna-archive@megatron.ietf.org; Thu, 13 Oct 2005 13:34:27 -0400
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 NAA00641
	for <dna-archive@lists.ietf.org>; Thu, 13 Oct 2005 13:34:21 -0400 (EDT)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU664VLCZW9FO2I4@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 14 Oct 2005 03:34:14 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id DF89FAB558; Fri,
 14 Oct 2005 03:33:46 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 86FA44FB07; Fri,
 14 Oct 2005 03:33:46 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9DHW9K27273	for dna-list; Fri, 14 Oct 2005 03:32:09 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9DHW8d27269	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 14 Oct 2005 03:32:08 +1000
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 <01LU662HZCHK9ARXM0@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 14 Oct 2005 03:31:52 +1000
Received: by localhost (Postfix, from userid 510)	id 39C7BAB557; Fri,
 14 Oct 2005 03:31:52 +1000 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id D86D44FB02; Fri, 14 Oct 2005 03:31:50 +1000 (EST)
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with ESMTP id j9DHVn6p005984; Thu, 13 Oct 2005 13:31:49 -0400
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with ESMTP id 57CF13C817F; Thu,
 13 Oct 2005 12:13:20 -0400 (EDT)
Received: from [150.169.1.185] (unknown [150.169.1.185])
 by	redwood.research.panasonic.com (Postfix) with ESMTP id 4741B3C8176; Thu,
 13 Oct 2005 12:13:20 -0400 (EDT)
Date: Thu, 13 Oct 2005 13:31:10 -0400
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434E0390.8090208@sun.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Erik Nordmark <erik.nordmark@sun.com>
Cc: greg.daley@eng.monash.edu.au, Bernard Aboba <bernard_aboba@hotmail.com>,
        tero.kauppinen@ericsson.com, jinchoe@gmail.com,
        brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <434E99DE.6060401@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:68.03420 C:16 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
References: <BAY106-F31DA261AEF35D1BC618016937B0@phx.gbl>
 <434DD47B.1030406@eng.monash.edu.au> <434E0390.8090208@sun.com>
Content-Transfer-Encoding: 7BIT

Erik Nordmark wrote:

> *If* we want DNAv6 to handle the case when we don't have global IPv6
> prefixes, I'd suggest we do that by allowing something other than
> prefixes be used as the link identifier (as Keith Moore suggested).

I agree.

*If* we want to allow *something* other than prefix to be used as the
link identifier, the *something* must:

1) be agreed upon by all nodes that will send RA messages.
2) be unique for each link (Weak condition: atleast for links between
which hosts could possibly move).

Since we don't know what this *something* is going to be, we cannot
specify how these two conditions are met, we need to leave that to
future specifications.

AFAICT, the only think we can achieve today is forward compatability for
hosts by defining the syntax for using *something* as link identifier.
As Hesham suggested during the last meeting, syntax can be written as a
TLV and since variable length is allowed by L, new link identifiers will
be possible. In the router advertisement processing text, we should add
a condition to check for link identifier in the RA.

The only question is *whether* we want to allow for this possibility? We
need consensus on this question to proceed further.

Sathya



From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 14 02:26:20 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQJ1I-0001F0-4M
	for dna-archive@megatron.ietf.org; Fri, 14 Oct 2005 02:26:20 -0400
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 CAA20281
	for <dna-archive@lists.ietf.org>; Fri, 14 Oct 2005 02:26:14 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU6X1RCFZU8WZHEA@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 14 Oct 2005 16:25:17 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 5706080007; Fri,
 14 Oct 2005 16:24:45 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 143FA3C004; Fri, 14 Oct 2005 16:24:45 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9E6NhB04226	for dna-list; Fri, 14 Oct 2005 16:23:43 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9E6Nhd04222	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 14 Oct 2005 16:23:43 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU6X071W308WZHEA@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 14 Oct 2005 16:23:32 +1000
Received: by localhost (Postfix, from userid 510)	id C4B5BAB55F; Fri,
 14 Oct 2005 16:23:29 +1000 (EST)
Received: from hotmail.com (bay106-f27.bay106.hotmail.com [65.54.161.37])
	by moe.its.monash.edu.au (Postfix) with ESMTP id A5DEE4FB0D; Fri,
 14 Oct 2005 16:23:28 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu,
 13 Oct 2005 23:23:27 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Fri,
 14 Oct 2005 06:23:26 +0000 (GMT)
Date: Thu, 13 Oct 2005 23:23:26 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434E0390.8090208@sun.com>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: erik.nordmark@sun.com, greg.daley@eng.monash.edu.au
Cc: tero.kauppinen@ericsson.com, jinchoe@gmail.com,
        brett.pentland@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: <BAY106-F279BF0C84DA9AE3DB0B160937D0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 14 Oct 2005 06:23:27.0357 (UTC)
 FILETIME=[C9BB12D0:01C5D087]
Content-Transfer-Encoding: 7BIT

>So it doesn't seem that useful to follow the IPv4 model of first verifying 
>that an IP+MAC address is still present on the link, since if we have moved 
>we'd need to send additional packets.

DNAv4 is designed to be used in parallel with DHCP, so that multiple 
networks can be tested at the same time in addition to requesting 
configuration via DHCP.

For IPv6 this would be equivalent to using *both* ND and RS/RA in parallel.





From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 14 06:16:16 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQMbo-0006Qn-2u
	for dna-archive@megatron.ietf.org; Fri, 14 Oct 2005 06:16:16 -0400
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 GAA29932
	for <dna-archive@lists.ietf.org>; Fri, 14 Oct 2005 06:16:11 -0400 (EDT)
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 <01LU753EDOY89ANDWB@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 14 Oct 2005 20:15:14 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 82D9F80003; Fri,
 14 Oct 2005 20:15:08 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 386953C006; Fri, 14 Oct 2005 20:15:08 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9EAELS06889	for dna-list; Fri, 14 Oct 2005 20:14:21 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9EAEKd06885	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 14 Oct 2005 20:14:20 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU752CNELI9FOBOI@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 14 Oct 2005 20:14:18 +1000
Received: by localhost (Postfix, from userid 510)	id 0CC5FAB542; Fri,
 14 Oct 2005 20:14:18 +1000 (EST)
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 9F2924FB02; Fri,
 14 Oct 2005 20:14:15 +1000 (EST)
Received: from jurassic.eng.sun.com ([129.146.108.38])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j9EAED2B010035; Fri,
 14 Oct 2005 03:14:14 -0700 (PDT)
Received: from [129.158.215.244]
 (dhcp-cbjs05-215-09.PRC.Sun.COM [129.158.215.244])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id j9EAEAhm882681
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri,
 14 Oct 2005 03:14:11 -0700 (PDT)
Date: Fri, 14 Oct 2005 03:14:35 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <BAY106-F279BF0C84DA9AE3DB0B160937D0@phx.gbl>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Bernard Aboba <bernard_aboba@hotmail.com>
Cc: greg.daley@eng.monash.edu.au, tero.kauppinen@ericsson.com,
        jinchoe@gmail.com, brett.pentland@eng.monash.edu.au,
        dna@eng.monash.edu.au
Message-id: <434F850B.1040308@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: <BAY106-F279BF0C84DA9AE3DB0B160937D0@phx.gbl>
Content-Transfer-Encoding: 7BIT

Bernard Aboba wrote:
>> So it doesn't seem that useful to follow the IPv4 model of first 
>> verifying that an IP+MAC address is still present on the link, since 
>> if we have moved we'd need to send additional packets.
> 
> 
> DNAv4 is designed to be used in parallel with DHCP, so that multiple 
> networks can be tested at the same time in addition to requesting 
> configuration via DHCP.

ok

> For IPv6 this would be equivalent to using *both* ND and RS/RA in parallel.

Yes, but that would still imply 3 or 4 packets instead of 2, even if the 
latency isn't any longer.

    Erik




From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 14 09:22:48 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQPWK-0006bd-L3
	for dna-archive@megatron.ietf.org; Fri, 14 Oct 2005 09:22:48 -0400
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 JAA09303
	for <dna-archive@lists.ietf.org>; Fri, 14 Oct 2005 09:22:42 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU7BJJLQVK9FOCAJ@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 14 Oct 2005 23:20:11 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 88A2B80003; Fri,
 14 Oct 2005 23:19:57 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 480783C007; Fri, 14 Oct 2005 23:19:57 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9EDJHE08991	for dna-list; Fri, 14 Oct 2005 23:19:17 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9EDJGd08987	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 14 Oct 2005 23:19:16 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU7BII7GXE8WZKIH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 14 Oct 2005 23:19:07 +1000
Received: by localhost (Postfix, from userid 510)	id 665D9AB542; Fri,
 14 Oct 2005 23:19:07 +1000 (EST)
Received: from hotmail.com (bay106-f16.bay106.hotmail.com [65.54.161.26])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 69D5A4FB04; Fri,
 14 Oct 2005 23:19:06 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri,
 14 Oct 2005 06:19:05 -0700
Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Fri,
 14 Oct 2005 13:19:04 +0000 (GMT)
Date: Fri, 14 Oct 2005 06:19:04 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [DNA] Prefix information for link identification in DNA
In-reply-to: <434F850B.1040308@sun.com>
X-Originating-IP: [67.182.139.247]
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: bernard_aboba@hotmail.com
To: erik.nordmark@sun.com
Cc: greg.daley@eng.monash.edu.au, tero.kauppinen@ericsson.com,
        jinchoe@gmail.com, brett.pentland@eng.monash.edu.au,
        dna@eng.monash.edu.au
Message-id: <BAY106-F16FDDCEE8E10A016F2F9E5937D0@phx.gbl>
MIME-version: 1.0
Content-type: text/plain; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Originating-Email: [bernard_aboba@hotmail.com]
X-OriginalArrivalTime: 14 Oct 2005 13:19:05.0059 (UTC)
 FILETIME=[D9C26B30:01C5D0C1]
Content-Transfer-Encoding: 7BIT

>Yes, but that would still imply 3 or 4 packets instead of 2, even if the 
>latency isn't any longer.

At a minimum, it implies two packets -- but it also implies no need for 
additional protocol work.  This is something to keep in mind since DNAv4 is 
being widely implemented;  it will be tempting for those implementations may 
apply the same approach to DNAv6.

Sending more packets should not be a concern by itself; the issue is how 
many packets are sent within a given time interval.





From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 14 20:35:23 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQa1D-0003Sz-L2
	for dna-archive@megatron.ietf.org; Fri, 14 Oct 2005 20:35:23 -0400
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 UAA06892
	for <dna-archive@lists.ietf.org>; Fri, 14 Oct 2005 20:35:17 -0400 (EDT)
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 <01LU7Z4PRPOY9ARX6F@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 15 Oct 2005 10:35:16 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id EC39580004; Sat,
 15 Oct 2005 10:35:11 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id A285A3C009; Sat, 15 Oct 2005 10:35:11 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9F0XpE17032	for dna-list; Sat, 15 Oct 2005 10:33:51 +1000
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 j9F0Xpd17028	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 15 Oct 2005 10:33:51 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LU7Z2UVSDI9FOEOW@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 15 Oct 2005 10:33:42 +1000
Received: by localhost (Postfix, from userid 510)	id 1C6F7AB557; Sat,
 15 Oct 2005 10:33:42 +1000 (EST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	(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 BE1E64FB02	for <dna@eng.monash.edu.au>; Sat,
 15 Oct 2005 10:33:40 +1000 (EST)
Received: from eamrcnt751.exu.ericsson.se
 (eamrcnt751.exu.ericsson.se [138.85.133.52])	by imr2.ericy.com (8.13.1/8.13.1)
 with ESMTP id j9F0YPLp009091	for <dna@eng.monash.edu.au>; Fri,
 14 Oct 2005 19:34:25 -0500
Received: from noah.lmc.ericsson.se ([142.133.1.1])
 by eamrcnt751.exu.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id SZDMNRHY; Fri, 14 Oct 2005 19:33:38 -0500
Received: from dhcp723-115.rnet.lmc.ericsson.se
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
	by noah.lmc.ericsson.se (8.12.10/8.12.10) with ESMTP id j9F0XZ6l014016	for
 <dna@eng.monash.edu.au>; Fri, 14 Oct 2005 20:33:37 -0400 (EDT)
Date: Fri, 14 Oct 2005 20:33:04 -0400 (EDT)
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] Seeking WG input on Non-prefix link identifiers
Sender: owner-dna@ecselists.eng.monash.edu.au
X-X-Sender: suresh@dhcp723-115.rnet.lmc.ericsson.se
To: dna@eng.monash.edu.au
Reply-to: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Message-id: <Pine.LNX.4.61.0510142025340.6734@dhcp723-115.rnet.lmc.ericsson.se>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Sybari-Trust: 99a054cc 856a4233 1424391a 00000139
Content-Transfer-Encoding: 7BIT

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 Mon Oct 17 15:03:11 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERaGN-0005eP-59
	for dna-archive@megatron.ietf.org; Mon, 17 Oct 2005 15:03:11 -0400
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 PAA01301
	for <dna-archive@lists.ietf.org>; Mon, 17 Oct 2005 15:03:03 -0400 (EDT)
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUBUDHDJL48X067Q@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 18 Oct 2005 05:02:21 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A3485AB558; Tue,
 18 Oct 2005 05:01:52 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 548374FB07; Tue,
 18 Oct 2005 05:01:52 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9HJ0Rh00860	for dna-list; Tue, 18 Oct 2005 05:00:27 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9HJ0Rd00856	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 18 Oct 2005 05:00:27 +1000
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 <01LUBUBNTL8G9AS3S4@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 18 Oct 2005 05:00:24 +1000
Received: by localhost (Postfix, from userid 510)	id B813AAB557; Tue,
 18 Oct 2005 05:00:24 +1000 (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 moe.its.monash.edu.au (Postfix)
 with ESMTP id 618E74FB02	for <dna@eng.monash.edu.au>; Tue,
 18 Oct 2005 05:00:23 +1000 (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 1ERaDQ-0005qa-Sx; Mon,
 17 Oct 2005 21:00:19 +0200
Received: from [141.3.71.115] (i72ibm03.tm.uni-karlsruhe.de [141.3.71.115])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 19EFEB361; Mon,
 17 Oct 2005 21:00:08 +0200 (CEST)
Date: Mon, 17 Oct 2005 21:00:07 +0200
From: Christian Vogt <chvogt@tm.uka.de>
Subject: [DNA] Interactions btw. MLD Report Delays and ODAD
Sender: owner-dna@ecselists.eng.monash.edu.au
To: DNA <dna@eng.monash.edu.au>
Cc: Mark Doll <doll@tm.uka.de>, Roland Bless <bless@tm.uka.de>
Message-id: <4353F4B7.7090304@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; us-US; 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 everybody,

a while back we had a discussion on this mailing list [1] about
interactions between delays imposed on MLD Report messages and
Optimistic DAD.

Since this issue doesn't seem to be resolved, but Optimistic DAD has
already made it quite far through the standardization process, I sent a
message to Nick and the IPv6 community today ("Comment on
draft-ietf-ipv6-optimistic-dad-06.txt").  Those of you
interested in this, please be referred to the IPv6 mailing list.

Kind regards,

- Christian


[1] "DAD and MLD Interaction", Discussion on the DNA mailing
list, June 13, 2005, <http://webcamserver.eng.monash.edu.au/
~warchive/dna/2005-06/msg00098.html>.

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





From dna-owner@webcamserver.eng.monash.edu.au Tue Oct 18 10:53:06 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERspu-0006oB-FR
	for dna-archive@megatron.ietf.org; Tue, 18 Oct 2005 10:53:06 -0400
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 KAA05551
	for <dna-archive@lists.ietf.org>; Tue, 18 Oct 2005 10:52:57 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUCZWF2BY69FORII@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 19 Oct 2005 00:51:37 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8308CAB544; Wed,
 19 Oct 2005 00:51:29 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 2E7E94FB0D; Wed, 19 Oct 2005 00:51:29 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9IEoKO13858	for dna-list; Wed, 19 Oct 2005 00:50:20 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9IEoJd13854	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 19 Oct 2005 00:50:19 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUCZUOR4DW9FORII@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 19 Oct 2005 00:50:06 +1000
Received: by localhost (Postfix, from userid 510)	id E7D2EAB557; Wed,
 19 Oct 2005 00:50:05 +1000 (EST)
Received: from newodin.ietf.org (unknown [132.151.6.50])
	(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 7C0EF4FB0F	for <dna@eng.monash.edu.au>; Wed,
 19 Oct 2005 00:50:04 +1000 (EST)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ERsmw-0003J4-1D; Tue, 18 Oct 2005 10:50:02 -0400
Date: Tue, 18 Oct 2005 10:50:02 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-frd-00.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <E1ERsmw-0003J4-1D@newodin.ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_umzBJ5KzV1WA6nplI3RRXQ)"
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)


--Boundary_(ID_umzBJ5KzV1WA6nplI3RRXQ)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

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

	Title		: Fast Router Discovery with L2 support
	Author(s)	: J. Choi, et al.
	Filename	: draft-ietf-dna-frd-00.txt
	Pages		: 20
	Date		: 2005-10-18
	
   For efficient DNA, a host should quickly receive an RA (Router
   Advertisement) upon a new link-layer connection.  This draft presents
   a quick RA acquisition scheme with the support of a link-layer
   entity, PoA (Point of Attachment).  Upon a new network attachment,
   the PoA may either trigger an AR (Access Router) to immediately send
   an unicast RA, "RA Triggering" or send such an RA for itself, "RA
   Proxying".  We may put "RA Triggering" or "RA Proxying" functionality
   on a PoA to get the optimized result without IPv6 standard change.

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

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


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

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


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

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

--Boundary_(ID_umzBJ5KzV1WA6nplI3RRXQ)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_S6lNLymHvCnGHZqkiAdehQ)"


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

Content-Type: text/plain
Content-ID:	<2005-10-18103011.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dna-frd-00.txt

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

Content-Type: text/plain
Content-ID:	<2005-10-18103011.I-D@ietf.org>

--Boundary_(ID_S6lNLymHvCnGHZqkiAdehQ)--

--Boundary_(ID_umzBJ5KzV1WA6nplI3RRXQ)--



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 19 06:55:06 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESBb8-0002fi-1p
	for dna-archive@megatron.ietf.org; Wed, 19 Oct 2005 06:55:06 -0400
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 GAA06812
	for <dna-archive@lists.ietf.org>; Wed, 19 Oct 2005 06:54:55 -0400 (EDT)
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 <01LUE5X7R8X89ARZWR@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 19 Oct 2005 20:54:47 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 90B4EAB546; Wed,
 19 Oct 2005 20:54:43 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 4AFB74FB03; Wed, 19 Oct 2005 20:54:43 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9JArKh27227	for dna-list; Wed, 19 Oct 2005 20:53:20 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9JArJd27223	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 19 Oct 2005 20:53:19 +1000
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 <01LUE5VCB7MO99Z1O8@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 19 Oct 2005 20:53:13 +1000
Received: by localhost (Postfix, from userid 510)	id 1ADC780002; Wed,
 19 Oct 2005 20:53:13 +1000 (EST)
Received: from [192.168.1.100] (cust1648.vic01.dataco.com.au [202.63.56.112])
	(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 3FB233C009	for <dna@eng.monash.edu.au>; Wed,
 19 Oct 2005 20:53:12 +1000 (EST)
Date: Wed, 19 Oct 2005 20:53:20 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: [DNA] Review of link info draft -02
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Dna <dna@eng.monash.edu.au>
Message-id: <435625A0.4000800@eng.monash.edu.au>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_z31mRdcncz6vndjkkir/Hg)"
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-Spam-Level: ***

This is a multi-part message in MIME format.

--Boundary_(ID_z31mRdcncz6vndjkkir/Hg)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7BIT


--Boundary_(ID_z31mRdcncz6vndjkkir/Hg)
Content-type: message/rfc822; name="Review of link info draft -02"

Return-path: <brett.pentland@eng.monash.edu.au>
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1]) by mail-store-1.its.monash.edu.au
 (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005))
 with ESMTP id <0IOL00C3ALEJFQ@mail-store-1.its.monash.edu.au> for
 BRETT@mail1.monash.edu.au; Wed, 19 Oct 2005 18:11:11 +1000 (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 <01LUE089OP2A8X0GJF@vaxc.its.monash.edu.au> for
 BRETT@mail1.monash.edu.au (ORCPT brett.pentland@eng.monash.edu.au); Wed,
 19 Oct 2005 18:11:04 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 8DDD6AB557; Wed,
 19 Oct 2005 18:11:03 +1000 (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 699CC4FB0B; Wed,
 19 Oct 2005 18:11:03 +1000 (EST)
Date: Wed, 19 Oct 2005 18:11:03 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Review of link info draft -02
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <4355FF97.3080907@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
Original-recipient: rfc822;brett.pentland@eng.monash.edu.au
Content-Transfer-Encoding: 7BIT

Hi Alper,

Sorry I'm just writing this now when the last call ended yesterday, but
I just found a few things you might want to consider.  The draft looks
very good but there are a few typos (listed below).  I'm not sure what
should be there, but I also wonder if the security considerations
section is too brief.

Regards,
Brett.

Intro, para 3, line 1
s/on/of/ OR perhaps s/on/to/

Intro, para 4, line 1
s/It be noted/It should be noted/

Intro, para 6, line 3
s/strenght/strength/

2.3, para 4
I think there's a mix up:

Disassociation <--> non-RSN
De-authentication and disassociation <--> RSN

rather than the other way around as written?

2.3, para 5, line 1, perhaps:
s/station/stations/
line 2
s/others/each other/

2.4, para 1, lines 3,4
probably should be either "... is specified by both a physical layer and
a medium access control (MAC) layer..." or "...is specified by a
physical layer/medium access control (MAC) layer..."
ie.  either remove "both" or remove the "/" (and replace it with "and
a").

2.4.2, para 1, line 2
s/Tranparent/Transparent/



--Boundary_(ID_z31mRdcncz6vndjkkir/Hg)--



From dna-owner@webcamserver.eng.monash.edu.au Thu Oct 20 18:44:10 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESj8s-0002Bl-7m
	for dna-archive@megatron.ietf.org; Thu, 20 Oct 2005 18:44:10 -0400
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 SAA19889
	for <dna-archive@lists.ietf.org>; Thu, 20 Oct 2005 18:43:59 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUG8YB47UC8X0SK5@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 21 Oct 2005 08:42:56 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D9A09AB545; Fri,
 21 Oct 2005 08:42:41 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 7F3C04FB04; Fri, 21 Oct 2005 08:42:41 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9KMcOm18234	for dna-list; Fri, 21 Oct 2005 08:38:24 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9KMcKd18230	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 21 Oct 2005 08:38:20 +1000
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 <01LUG8SL2QLO99ZA79@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 21 Oct 2005 08:38:05 +1000
Received: by localhost (Postfix, from userid 510)	id 4F590AB542; Fri,
 21 Oct 2005 08:38:05 +1000 (EST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	(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 2074D4FB04; Fri, 21 Oct 2005 08:38:02 +1000 (EST)
Received: from eamrcnt751.exu.ericsson.se
 (eamrcnt751.exu.ericsson.se [138.85.133.52])	by imr2.ericy.com (8.13.1/8.13.1)
 with ESMTP id j9KMd3g4003190; Thu, 20 Oct 2005 17:39:04 -0500
Received: by eamrcnt751.exu.ericsson.se with Internet Mail Service
 (5.5.2657.72)	id <SZDMWT10>; Thu, 20 Oct 2005 17:37:59 -0500
Received: from [142.133.72.115]
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
 by EAMMLEX034.lmc.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VAT9W66X; Thu, 20 Oct 2005 18:34:33 -0400
Date: Thu, 20 Oct 2005 18:35:31 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: Re: [DNA] Review of link info draft -02
In-reply-to: <435625A0.4000800@eng.monash.edu.au>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@yegin.org>,
        Brett Pentland <brett.pentland@eng.monash.edu.au>,
        Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>
Reply-to: suresh.krishnan@ericsson.ca
Message-id: <43581BB3.9050902@ericsson.ca>
Organization: Ericsson
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 (X11/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <435625A0.4000800@eng.monash.edu.au>
Content-Transfer-Encoding: 7BIT

Hi Alper,
	Since the comments are editorial, you can go ahead and make the 
changes(if you have no objections). Submit the new version by the I-D 
cutoff date, which is on Monday Oct 24th by 9AM EST. This will be the 
version which we will submit to the IESG for consideration.

Cheers
Suresh

Brett Pentland wrote:
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Review of link info draft -02
> From:
> Brett Pentland <brett.pentland@eng.monash.edu.au>
> Date:
> Wed, 19 Oct 2005 18:11:03 +1000
> To:
> Alper Yegin <alper.yegin@yegin.org>
> 
> To:
> Alper Yegin <alper.yegin@yegin.org>
> 
> 
> Hi Alper,
> 
> Sorry I'm just writing this now when the last call ended yesterday, but
> I just found a few things you might want to consider.  The draft looks
> very good but there are a few typos (listed below).  I'm not sure what
> should be there, but I also wonder if the security considerations
> section is too brief.
> 
> Regards,
> Brett.
> 
> Intro, para 3, line 1
> s/on/of/ OR perhaps s/on/to/
> 
> Intro, para 4, line 1
> s/It be noted/It should be noted/
> 
> Intro, para 6, line 3
> s/strenght/strength/
> 
> 2.3, para 4
> I think there's a mix up:
> 
> Disassociation <--> non-RSN
> De-authentication and disassociation <--> RSN
> 
> rather than the other way around as written?
> 
> 2.3, para 5, line 1, perhaps:
> s/station/stations/
> line 2
> s/others/each other/
> 
> 2.4, para 1, lines 3,4
> probably should be either "... is specified by both a physical layer and
> a medium access control (MAC) layer..." or "...is specified by a
> physical layer/medium access control (MAC) layer..."
> ie.  either remove "both" or remove the "/" (and replace it with "and
> a").
> 
> 2.4.2, para 1, line 2
> s/Tranparent/Transparent/
> 
> 



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 26 10:52:18 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmdW-0002xw-CH
	for dna-archive@megatron.ietf.org; Wed, 26 Oct 2005 10:52:18 -0400
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 KAA24836
	for <dna-archive@lists.ietf.org>; Wed, 26 Oct 2005 10:52:00 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUO69M850E9FPY68@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 27 Oct 2005 00:52:03 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C4A4780006; Thu,
 27 Oct 2005 00:51:51 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 722583C007; Thu, 27 Oct 2005 00:51:51 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9QEoHx12726	for dna-list; Thu, 27 Oct 2005 00:50:17 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9QEoGd12722	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 27 Oct 2005 00:50:16 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUO67FAFAG8X1SNJ@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 27 Oct 2005 00:50:06 +1000
Received: by localhost (Postfix, from userid 510)	id EC2A680002; Thu,
 27 Oct 2005 00:50:05 +1000 (EST)
Received: from newodin.ietf.org (unknown [132.151.6.50])
	(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 AD01C3C00B	for <dna@eng.monash.edu.au>; Thu,
 27 Oct 2005 00:50:04 +1000 (EST)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EUmbJ-0003W6-UR; Wed, 26 Oct 2005 10:50:01 -0400
Date: Wed, 26 Oct 2005 10:50:01 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-link-information-03.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <E1EUmbJ-0003W6-UR@newodin.ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_n2WBh5NjJyrZwOnTZ6CCJw)"
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)


--Boundary_(ID_n2WBh5NjJyrZwOnTZ6CCJw)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

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

	Title		: Link-layer Event Notifications for Detecting Network Attachments
	Author(s)	: A. Yegin
	Filename	: draft-ietf-dna-link-information-03.txt
	Pages		: 23
	Date		: 2005-10-26
	
Certain network access technologies are capable of providing various
   link-layer status information to IP.  Link-layer event notifications
   can help IP expeditiously detect configuration changes.  This
   document provides a non-exhaustive catalogue of information available
   from well-known access technologies.

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

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


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

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


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

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

--Boundary_(ID_n2WBh5NjJyrZwOnTZ6CCJw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Pxx0ioclaLfydOT1t4jVIQ)"


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

Content-Type: text/plain
Content-ID:	<2005-10-26103228.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2005-10-26103228.I-D@ietf.org>

--Boundary_(ID_Pxx0ioclaLfydOT1t4jVIQ)--

--Boundary_(ID_n2WBh5NjJyrZwOnTZ6CCJw)--



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 26 10:53:28 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmee-0003Be-Hn
	for dna-archive@megatron.ietf.org; Wed, 26 Oct 2005 10:53:28 -0400
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 KAA25079
	for <dna-archive@lists.ietf.org>; Wed, 26 Oct 2005 10:53:11 -0400 (EDT)
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 <01LUO69S4N8Y9AS9JD@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 27 Oct 2005 00:52:05 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B7D6DAB542; Thu,
 27 Oct 2005 00:51:59 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 7524F4FB08; Thu, 27 Oct 2005 00:51:59 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9QEoGM12720	for dna-list; Thu, 27 Oct 2005 00:50:16 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9QEoGd12714	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 27 Oct 2005 00:50:16 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LUO67F9WJK9FPY68@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 27 Oct 2005 00:50:06 +1000
Received: by localhost (Postfix, from userid 510)	id EE223AB557; Thu,
 27 Oct 2005 00:50:05 +1000 (EST)
Received: from newodin.ietf.org (unknown [132.151.6.50])
	(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 BA95F4FB05	for <dna@eng.monash.edu.au>; Thu,
 27 Oct 2005 00:50:04 +1000 (EST)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EUmbK-0003WI-12; Wed, 26 Oct 2005 10:50:02 -0400
Date: Wed, 26 Oct 2005 10:50:02 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-routers-01.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <E1EUmbK-0003WI-12@newodin.ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_Vrs06NaQLPBfxO8UkGjvVw)"
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)


--Boundary_(ID_Vrs06NaQLPBfxO8UkGjvVw)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

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

	Title		: Detecting Network Attachment in IPv6 - Best 
                          Current Practices for Routers
	Author(s)	: S. Narayanan, et al.
	Filename	: draft-ietf-dna-routers-01.txt
	Pages		: 19
	Date		: 2005-10-26
	
Hosts experiencing rapid link-layer changes may require to do
   configuration change detection procedures more frequently than
   traditional fixed hosts.  This document describes practices available
   to network deployers in order to support such hosts in Detecting
   Network Attachment in IPv6 networks.

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

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


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

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


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

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

--Boundary_(ID_Vrs06NaQLPBfxO8UkGjvVw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_AI8dPXaMCZGRvK2wdReB8Q)"


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

Content-Type: text/plain
Content-ID:	<2005-10-26104043.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dna-routers-01.txt

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

Content-Type: text/plain
Content-ID:	<2005-10-26104043.I-D@ietf.org>

--Boundary_(ID_AI8dPXaMCZGRvK2wdReB8Q)--

--Boundary_(ID_Vrs06NaQLPBfxO8UkGjvVw)--



From dna-owner@webcamserver.eng.monash.edu.au Wed Oct 26 10:53:30 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmeg-0003CE-8g
	for dna-archive@megatron.ietf.org; Wed, 26 Oct 2005 10:53:30 -0400
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 KAA25081
	for <dna-archive@lists.ietf.org>; Wed, 26 Oct 2005 10:53:13 -0400 (EDT)
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 <01LUO69Y2G1899YYID@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 27 Oct 2005 00:52:11 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id AFEDD80005; Thu,
 27 Oct 2005 00:52:07 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 703203C007; Thu, 27 Oct 2005 00:52:07 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9QEoKJ12733	for dna-list; Thu, 27 Oct 2005 00:50:20 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9QEoJd12729	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 27 Oct 2005 00:50:19 +1000
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 <01LUO67FCO3Q9AS9JD@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 27 Oct 2005 00:50:06 +1000
Received: by localhost (Postfix, from userid 510)	id 1324EAB543; Thu,
 27 Oct 2005 00:50:05 +1000 (EST)
Received: from newodin.ietf.org (unknown [132.151.6.50])
	(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 A4F164FB05	for <dna@eng.monash.edu.au>; Thu,
 27 Oct 2005 00:50:04 +1000 (EST)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EUmbJ-0003W2-TV; Wed, 26 Oct 2005 10:50:01 -0400
Date: Wed, 26 Oct 2005 10:50:01 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-hosts-02.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <E1EUmbJ-0003W2-TV@newodin.ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_YKBFbq0//7Yd1ayQBbrpIQ)"
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)


--Boundary_(ID_YKBFbq0//7Yd1ayQBbrpIQ)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

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

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

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

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


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

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


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

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

--Boundary_(ID_YKBFbq0//7Yd1ayQBbrpIQ)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_WWvNALeU2ojl6i30fhLEbQ)"


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

Content-Type: text/plain
Content-ID:	<2005-10-26103034.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2005-10-26103034.I-D@ietf.org>

--Boundary_(ID_WWvNALeU2ojl6i30fhLEbQ)--

--Boundary_(ID_YKBFbq0//7Yd1ayQBbrpIQ)--



From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 28 19:03:28 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVdFw-000458-GI
	for dna-archive@megatron.ietf.org; Fri, 28 Oct 2005 19:03:28 -0400
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 TAA25241
	for <dna-archive@lists.ietf.org>; Fri, 28 Oct 2005 19:03:10 -0400 (EDT)
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURFZ106J69FQFTW@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 09:03:10 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 120D7AB543; Sat,
 29 Oct 2005 09:02:49 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id C65AD4FB07; Sat, 29 Oct 2005 09:02:48 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9SN0qL18480	for dna-list; Sat, 29 Oct 2005 09:00:52 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9SN0pd18476	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 09:00:51 +1000
Received: from moe.its.monash.edu.au ([130.194.13.88])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURFWIR3FC9FQFTW@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 09:00:48 +1000
Received: by localhost (Postfix, from userid 510)	id D0730AB557; Sat,
 29 Oct 2005 09:00:47 +1000 (EST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	(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 DCD184FB0E; Sat, 29 Oct 2005 09:00:46 +1000 (EST)
Received: from eamrcnt750.exu.ericsson.se
 (eamrcnt750.exu.ericsson.se [138.85.133.51])	by imr2.ericy.com (8.13.1/8.13.1)
 with ESMTP id j9SN2CZS002580; Fri, 28 Oct 2005 18:02:12 -0500
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service
 (5.5.2656.59)	id <VNG49QJ6>; Fri, 28 Oct 2005 17:52:46 -0500
Received: from [142.133.72.115]
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
 by EAMMLEX034.lmc.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VAT9Z48N; Fri, 28 Oct 2005 18:58:18 -0400
Date: Fri, 28 Oct 2005 19:00:51 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Cc: greg daley <greg.daley@eng.monash.edu.au>,
        Alper Yegin <alper.yegin@yegin.org>
Reply-to: suresh.krishnan@ericsson.ca
Message-id: <4362ADA3.10504@ericsson.ca>
Organization: Ericsson
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 (X11/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
Content-Transfer-Encoding: 7BIT

Hi Folks,
    The last call period for this draft ended on 2005/10/18. Other than
the comments from Brett there was no other input on this draft. This
feedback is insufficient, and on a WGLC silence cannot be interpreted as

implicit support. So if the WG thinks that the draft is ready we can go
ahead and submit the draft to the IESG for consideration. In this
regard, we would like to poll the WG regarding the draft. Please choose
one of the following options on how you feel about this document

a) If you have issues with the draft
b) If you think the draft is ready to submit to the IESG
c) If you think that the draft is not interesting to the WG

as soon as possible. We will collect the responses and will make a final

decision on how to proceed at the dna WG meeting in Vancouver. Make your

voice heard!

Thanks
Suresh and Greg



From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 28 21:11:01 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVfFN-0001z7-4t
	for dna-archive@megatron.ietf.org; Fri, 28 Oct 2005 21:11:01 -0400
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 VAA00627
	for <dna-archive@lists.ietf.org>; Fri, 28 Oct 2005 21:10:42 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURKGE7XUO9FQ9Z8@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 11:10:54 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 000FB80005; Sat,
 29 Oct 2005 11:10:33 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id A3C313C006; Sat, 29 Oct 2005 11:10:33 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T19KQ19980	for dna-list; Sat, 29 Oct 2005 11:09:20 +1000
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 j9T19Kd19976	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 11:09:20 +1000
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURKEH6WSU9I44ZP@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 11:09:02 +1000
Received: by localhost (Postfix, from userid 510)	id 8F7CD80002; Sat,
 29 Oct 2005 11:09:01 +1000 (EST)
Received: from [192.168.1.100] (cust1648.vic01.dataco.com.au [202.63.56.112])
	(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 89ADF3C00B; Sat, 29 Oct 2005 11:09:00 +1000 (EST)
Date: Sat, 29 Oct 2005 11:09:15 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
In-reply-to: <4362ADA3.10504@ericsson.ca>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: suresh.krishnan@ericsson.ca
Cc: Dna <dna@eng.monash.edu.au>, greg daley <greg.daley@eng.monash.edu.au>,
        Alper Yegin <alper.yegin@yegin.org>
Message-id: <4362CBBB.9010707@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 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Spam-Level: *
References: <4362ADA3.10504@ericsson.ca>
Content-Transfer-Encoding: 7BIT


> b) If you think the draft is ready to submit to the IESG

I think the draft is a good description of the potential hinting
information available from various link technologies, particularly
the specific circumstances for generating link-up/link-down
signals.

Brett.



From dna-owner@webcamserver.eng.monash.edu.au Fri Oct 28 22:03:42 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVg4M-0007mB-RX
	for dna-archive@megatron.ietf.org; Fri, 28 Oct 2005 22:03:42 -0400
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 WAA03075
	for <dna-archive@lists.ietf.org>; Fri, 28 Oct 2005 22:03:23 -0400 (EDT)
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 <01LURMAULUJM99Y1ET@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 12:03:24 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id EBDBFAB543; Sat,
 29 Oct 2005 12:03:21 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP id 98B8A4FB06; Sat, 29 Oct 2005 12:03:21 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T21fe20722	for dna-list; Sat, 29 Oct 2005 12:01:41 +1000
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 j9T21ed20718	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 12:01:40 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURM86R3H69I4BFH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 12:01:14 +1000
Received: by localhost (Postfix, from userid 510)	id 4860CAB544; Sat,
 29 Oct 2005 12:01:13 +1000 (EST)
Received: from [192.168.1.100] (cust1648.vic01.dataco.com.au [202.63.56.112])
	(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 42DA94FB0B; Sat, 29 Oct 2005 12:01:12 +1000 (EST)
Date: Sat, 29 Oct 2005 12:01:27 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [DNA] Seeking WG input on Non-prefix link identifiers
In-reply-to: <Pine.LNX.4.61.0510142025340.6734@dhcp723-115.rnet.lmc.ericsson.se>
Sender: owner-dna@ecselists.eng.monash.edu.au
Approved: monash-smtp-auth
To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Cc: dna@eng.monash.edu.au
Message-id: <4362D7F7.8050507@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 (Windows/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <Pine.LNX.4.61.0510142025340.6734@dhcp723-115.rnet.lmc.ericsson.se>
Content-Transfer-Encoding: 7BIT

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 Sat Oct 29 01:03:11 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVis0-0004LW-Tb
	for dna-archive@megatron.ietf.org; Sat, 29 Oct 2005 01:03:11 -0400
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 BAA11040
	for <dna-archive@lists.ietf.org>; Sat, 29 Oct 2005 01:02:50 -0400 (EDT)
Received: from larry.its.monash.edu.au ([130.194.13.82])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURSK31Z1O9FQA1D@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 15:02:45 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 955ED80005; Sat,
 29 Oct 2005 15:02:36 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id 4DEEC3C005; Sat, 29 Oct 2005 15:02:36 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T50Xg22790	for dna-list; Sat, 29 Oct 2005 15:00:33 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9T50Xd22786	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 15:00:33 +1000
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 <01LURSHF23H69ASEGY@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 15:00:27 +1000
Received: by localhost (Postfix, from userid 510)	id AD19380002; Sat,
 29 Oct 2005 15:00:27 +1000 (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 larry.its.monash.edu.au (Postfix)
 with ESMTP id 3E45A3C007; Sat, 29 Oct 2005 15:00:23 +1000 (EST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7)
 with ESMTP id j9T50KLK017673; Sat, 29 Oct 2005 08:00:20 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183])
 by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat,
 29 Oct 2005 08:00:20 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118])
 by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat,
 29 Oct 2005 08:00:19 +0300
Date: Sat, 29 Oct 2005 08:00:18 +0300
From: john.loughney@nokia.com
Subject: RE: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca, dna@eng.monash.edu.au
Cc: greg.daley@eng.monash.edu.au, alper.yegin@yegin.org
Message-id: <1AA39B75171A7144A73216AED1D7478D013D4BBD@esebe100.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] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
Thread-Index: AcXcE8S+pXxjMNCnTMGacjZwFXPUQgAMd5kA
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Spam-Level: *
X-OriginalArrivalTime: 29 Oct 2005 05:00:19.0423 (UTC)
 FILETIME=[A8E2FEF0:01C5DC45]
Content-Transfer-Encoding: 7BIT

I've read the draft and I think its ready to go. 

>-----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: 29 October, 2005 02:01
>To: Dna
>Cc: greg daley; Alper Yegin
>Subject: [DNA] ACTION REQUIRED: End of WGLC for 
>draft-ietf-dna-link-information- 02.txt
>
>Hi Folks,
>    The last call period for this draft ended on 2005/10/18. 
>Other than the comments from Brett there was no other input on 
>this draft. This feedback is insufficient, and on a WGLC 
>silence cannot be interpreted as
>
>implicit support. So if the WG thinks that the draft is ready 
>we can go ahead and submit the draft to the IESG for 
>consideration. In this regard, we would like to poll the WG 
>regarding the draft. Please choose one of the following 
>options on how you feel about this document
>
>a) If you have issues with the draft
>b) If you think the draft is ready to submit to the IESG
>c) If you think that the draft is not interesting to the WG
>
>as soon as possible. We will collect the responses and will 
>make a final
>
>decision on how to proceed at the dna WG meeting in Vancouver. 
>Make your
>
>voice heard!
>
>Thanks
>Suresh and Greg
>



From dna-owner@webcamserver.eng.monash.edu.au Sat Oct 29 02:13:53 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVjyT-0008Sb-JY
	for dna-archive@megatron.ietf.org; Sat, 29 Oct 2005 02:13:53 -0400
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 CAA13696
	for <dna-archive@lists.ietf.org>; Sat, 29 Oct 2005 02:13:34 -0400 (EDT)
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 <01LURV16MT9E99ZRJ4@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 16:13:42 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id B5936AB558; Sat,
 29 Oct 2005 16:13:39 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 728084FB07; Sat,
 29 Oct 2005 16:13:39 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T6BmD23652	for dna-list; Sat, 29 Oct 2005 16:11:48 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9T6Bld23648	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 16:11:47 +1000
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 <01LURUYN6LXC99ZRJ4@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 16:11:37 +1000
Received: by localhost (Postfix, from userid 510)	id EC26180002; Sat,
 29 Oct 2005 16:11:36 +1000 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 737043C008	for
 <dna@eng.monash.edu.au>; Sat, 29 Oct 2005 16:11:33 +1000 (EST)
Received: by zproxy.gmail.com with SMTP id 13so641040nzp for
 <dna@eng.monash.edu.au>; Fri, 28 Oct 2005 23:11:32 -0700 (PDT)
Received: by 10.36.67.13 with SMTP id p13mr1068404nza; Fri,
 28 Oct 2005 23:11:32 -0700 (PDT)
Received: by 10.36.4.11 with HTTP; Fri, 28 Oct 2005 23:11:32 -0700 (PDT)
Date: Sat, 29 Oct 2005 15:11:32 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
In-reply-to: <4362ADA3.10504@ericsson.ca>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <92e919fb0510282311k664d8dd9vca08cd6692d80bf6@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=UhfqCLvR6WKGiYK2WqfQx64G0vWqjKdc+2ROW7BOd3MuAqTD3lxvXm1MP/aEDTv/XybJzw4YXLmX/AlwTwQDAn2KRIIala1MEQmAAxgpQydVxRS51CBpKcYWHW2fZFcRfSLmkJIHA0aKrPgH6aUKVfPqQsOPteVIr4bnQ6hCLZU=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <4362ADA3.10504@ericsson.ca>
Content-Transfer-Encoding: 7BIT

Dear DNA Group

We have incorporated WG feedback to update FRD draft to

Fast Router Discovery with L2 support
draft-ietf-dna-frd-00.txt

The draft is available at, we are glad to say, DNA web page.

http://www.ietf.org/internet-drafts/draft-ietf-dna-frd-00.txt

The changes are 1) we present a way for FRD to interoperate with SEND
in Section 7 Security considerations and 2) IPR announcement is made.

Kindly check the draft to see everything is ok. Your feedback will be
appreciated.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock Choi, DongYun. Shin and Wassim Haddad
(Authors)



From dna-owner@webcamserver.eng.monash.edu.au Sat Oct 29 02:18:03 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVk2V-0001V5-65
	for dna-archive@megatron.ietf.org; Sat, 29 Oct 2005 02:18:03 -0400
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 CAA13825
	for <dna-archive@lists.ietf.org>; Sat, 29 Oct 2005 02:17:44 -0400 (EDT)
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 <01LURV6CSXPK99ZVP5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 16:17:51 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id D4E2EAB557; Sat,
 29 Oct 2005 16:17:49 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 945CC4FB0C; Sat,
 29 Oct 2005 16:17:49 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T6GRd23747	for dna-list; Sat, 29 Oct 2005 16:16:27 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9T6GQd23743	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 16:16:26 +1000
Received: from curly.its.monash.edu.au ([130.194.13.87])
 by vaxc.its.monash.edu.au (PMDF V6.1 #31112)
 with ESMTP id <01LURV46Z3849I4CDW@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 16:16:05 +1000
Received: by localhost (Postfix, from userid 510)	id 67BFEAB542; Sat,
 29 Oct 2005 16:16:05 +1000 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 4170A4FB08	for
 <dna@eng.monash.edu.au>; Sat, 29 Oct 2005 16:16:04 +1000 (EST)
Received: by zproxy.gmail.com with SMTP id 13so641255nzp for
 <dna@eng.monash.edu.au>; Fri, 28 Oct 2005 23:16:03 -0700 (PDT)
Received: by 10.36.75.17 with SMTP id x17mr1070287nza; Fri,
 28 Oct 2005 23:16:03 -0700 (PDT)
Received: by 10.36.4.11 with HTTP; Fri, 28 Oct 2005 23:16:03 -0700 (PDT)
Date: Sat, 29 Oct 2005 15:16:03 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: [DNA] [Announce] FRD I-D
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <92e919fb0510282316w3aa7de9dh80897d13d49b2d2b@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:mime-version:content-type:content-transfer-encoding:content-disposition;
 b=qzx6zV4rL9sDMDiNjTHVaeL6MXtUsziSAbJhYf886Piu++6XdTzyZx8BGGC5ov2UryisMRmqIi8gMWYJ0N3UlUkjWRR+AOfOE7H46upAsuUZWbMOjPb4zsAHXnVU4Cdz08lw8DC43iaGi4Ts5UEJf5iFPtKl/KGs2rcY8XwwN8A=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
Content-Transfer-Encoding: 7BIT

Dear DNA Group

We have incorporated WG feedback to update FRD draft to

Fast Router Discovery with L2 support
draft-ietf-dna-frd-00.txt

The draft is available at, we are glad to say, DNA web page.

http://www.ietf.org/internet-drafts/draft-ietf-dna-frd-00.txt

The changes are 1) we present a way for FRD to interoperate with SEND
in Section 7 Security considerations and 2) IPR announcement is made.

Kindly check the draft to see everything is ok. Your feedback will be
appreciated.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock Choi, DongYun. Shin and Wassim Haddad
(Authors)



From dna-owner@webcamserver.eng.monash.edu.au Sat Oct 29 02:25:41 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVk9C-0004Ip-5U
	for dna-archive@megatron.ietf.org; Sat, 29 Oct 2005 02:25:41 -0400
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 CAA14123
	for <dna-archive@lists.ietf.org>; Sat, 29 Oct 2005 02:24:39 -0400 (EDT)
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 <01LURVEW2THY99ZVP5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 29 Oct 2005 16:24:47 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C005BAB557; Sat,
 29 Oct 2005 16:24:42 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 820554FB0B; Sat,
 29 Oct 2005 16:24:42 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9T6NGp23851	for dna-list; Sat, 29 Oct 2005 16:23:16 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id j9T6NGd23847	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 29 Oct 2005 16:23:16 +1000
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 <01LURVCOADYQ99ZVP5@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 29 Oct 2005 16:22:55 +1000
Received: by localhost (Postfix, from userid 510)	id A513AAB557; Sat,
 29 Oct 2005 16:22:55 +1000 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203])
	by moe.its.monash.edu.au (Postfix) with ESMTP id C55324FB0B	for
 <dna@eng.monash.edu.au>; Sat, 29 Oct 2005 16:22:54 +1000 (EST)
Received: by zproxy.gmail.com with SMTP id 13so641656nzp for
 <dna@eng.monash.edu.au>; Fri, 28 Oct 2005 23:22:53 -0700 (PDT)
Received: by 10.36.222.42 with SMTP id u42mr614196nzg; Fri,
 28 Oct 2005 23:22:53 -0700 (PDT)
Received: by 10.36.4.11 with HTTP; Fri, 28 Oct 2005 23:22:53 -0700 (PDT)
Date: Sat, 29 Oct 2005 15:22:53 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
In-reply-to: <4362ADA3.10504@ericsson.ca>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca
Cc: Dna <dna@eng.monash.edu.au>, greg daley <greg.daley@eng.monash.edu.au>,
        Alper Yegin <alper.yegin@yegin.org>
Message-id: <92e919fb0510282322r39a440cbpe313b555672552bb@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=PgLdKtznn0xL90Dk0ufyFus8uXdpNfvrD3uR+SdiVZw5WC7TwDb5bgSrRh0qwGtj4RvSroNluT1DdoBnlIStTx8So/C0EHxWdL0wx7yif709PAKFxFbXn0/pOFJitiUTw/HUGQvrCXGk73qZ6kh2OYzRQfU1/6cY1+1GQg+wbHc=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <4362ADA3.10504@ericsson.ca>
Content-Transfer-Encoding: 7BIT

Dear Suresh and Greg

> b) If you think the draft is ready to submit to the IESG

I think the draft is ready.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Sun Oct 30 21:30:20 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWPRE-0006OF-0p
	for dna-archive@megatron.ietf.org; Sun, 30 Oct 2005 21:30:20 -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 VAA04393
	for <dna-archive@lists.ietf.org>; Sun, 30 Oct 2005 21:29:58 -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 <01LUUHVND5EC9I4OAU@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 31 Oct 2005 13:30:02 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 25DEC80006; Mon,
 31 Oct 2005 13:29:44 +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 C661A3C009; Mon, 31 Oct 2005 13:29:43 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9V2PM223392	for dna-list; Mon, 31 Oct 2005 13:25: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 j9V2PMd23388	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 31 Oct 2005 13:25: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 <01LUUHPUDC4Y9I4OAU@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 31 Oct 2005 13:25:04 +1100
Received: by localhost (Postfix, from userid 510)	id 4D78F80004; Mon,
 31 Oct 2005 13:25:03 +1100 (EST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 6EE7D3C00B	for
 <dna@eng.monash.edu.au>; Mon, 31 Oct 2005 13:25:02 +1100 (EST)
Received: by zproxy.gmail.com with SMTP id 13so859708nzp for
 <dna@eng.monash.edu.au>; Sun, 30 Oct 2005 18:25:01 -0800 (PST)
Received: by 10.36.222.80 with SMTP id u80mr1036000nzg; Sun,
 30 Oct 2005 18:25:00 -0800 (PST)
Received: by 10.36.4.11 with HTTP; Sun, 30 Oct 2005 18:25:00 -0800 (PST)
Date: Mon, 31 Oct 2005 11:25:00 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Seeking WG input on Non-prefix link identifiers
In-reply-to: <Pine.LNX.4.61.0510142025340.6734@dhcp723-115.rnet.lmc.ericsson.se>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Cc: dna@eng.monash.edu.au
Message-id: <92e919fb0510301825x4d41f412s4277ec908c0cd509@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=oVW9YMoqHCDV+cmFpTnvK05A6sDN3hI6pCiV0n0AKt5yxkgkTBRvgIN+psW6w7n16paabOHT5hjiCZndBKX/raaQ3bN3HtqEhDuv8lR/hIBEaHpZZXTzoErhRumTM278K+TdsQ5NVtcKnzyZ0fDilDu8wV1m5w4aKkgJD8sgrPA=
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
References: <Pine.LNX.4.61.0510142025340.6734@dhcp723-115.rnet.lmc.ericsson.se>
Content-Transfer-Encoding: 7BIT

Dear Greg & Suresh

> On the topic:
>
> Should the working group develop non-prefix link identifiers as
> part of the base DNA solution protocol?

I don't think it's necessary to include non-prefix link identifier as
part of the base DNA solution protocol.

IMHO, prefix based DNA solution will work for most of the cases. The
only exception I can think of is Ad-hoc network and I am not sure
whether DNA is needed at all in such an environment.

DNA detects the identity of the currently attached link to ascertain
the validity of IP configuration for Internet Connectivity. Whereas
it's not clear either what constitutes a Ad-Hoc link nor how Ad-Hoc
nodes will be connected to Internet.

Recently Autoconf WG is created to assign Ad-Hoc nodes a valid IP
address (and it may also consider Internet Gateway), so if we want to
work on DNA for Ad-Hoc network, we may need to wait till Autoconf
works are reasonably clarified.

So we'd better develop base DNA solution protocol based on prefix link
identifier and may develop non-prefix link identifier as an extension
if needs arise.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock



From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 31 07:38:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWYvu-0004ko-Vx
	for dna-archive@megatron.ietf.org; Mon, 31 Oct 2005 07:38: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 HAA03188
	for <dna-archive@lists.ietf.org>; Mon, 31 Oct 2005 07:38:19 -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 <01LUV34PH1H29I4RKR@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 31 Oct 2005 23:38:19 +1100
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id A2DD580002; Mon,
 31 Oct 2005 23:37: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 656183C011; Mon, 31 Oct 2005 23:37:56 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9VCb8h29922	for dna-list; Mon, 31 Oct 2005 23:37:08 +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 j9VCb8d29918	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 31 Oct 2005 23:37:08 +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 <01LUV33EH1GY9A0ETW@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 31 Oct 2005 23:36:53 +1100
Received: by localhost (Postfix, from userid 510)	id 9523480002; Mon,
 31 Oct 2005 23:36:53 +1100 (EST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 272D83C00F; Mon,
 31 Oct 2005 23:36:50 +1100 (EST)
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id AD0894FE; Mon,
 31 Oct 2005 13:36:45 +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,
 31 Oct 2005 13:36:25 +0100
Received: from esealmw114.eemea.ericsson.se ([153.88.200.5])
 by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon,
 31 Oct 2005 13:36:24 +0100
Date: Mon, 31 Oct 2005 13:36:22 +0100
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: RE: [DNA] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "Suresh Krishnan (QB/EMC)" <suresh.krishnan@ericsson.com>
Cc: greg.daley@eng.monash.edu.au, dna@eng.monash.edu.au
Message-id: 
 <F08E178900F39344AC894077E6AF74D1010707DC@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] ACTION REQUIRED: End of WGLC for
 draft-ietf-dna-link-information- 02.txt
Thread-Index: AcXcE8S+pXxjMNCnTMGacjZwFXPUQgAMd5kAAHP45rA=
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
X-OriginalArrivalTime: 31 Oct 2005 12:36:24.0758 (UTC)
 FILETIME=[B4B93D60:01C5DE17]
Content-Transfer-Encoding: 7BIT

> >b) If you think the draft is ready to submit to the IESG

I think it is ready.

I once asked if someone felt that Bluetooth should be included in the
document but it seemed that no one cared. I guess if there is need the
document can later on be extended.

/Tero



From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 31 08:04:58 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWZLN-00071X-DJ
	for dna-archive@megatron.ietf.org; Mon, 31 Oct 2005 08:04:57 -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 IAA06281
	for <dna-archive@lists.ietf.org>; Mon, 31 Oct 2005 08:04:37 -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 <01LUV41DHQUG9I4RMH@vaxc.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 01 Nov 2005 00:03:37 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id DFF01AB562; Tue,
 01 Nov 2005 00:03:29 +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 9125A4FB0A; Tue,
 01 Nov 2005 00:03:29 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9VD3H330264	for dna-list; Tue, 01 Nov 2005 00:03: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 j9VD3Gd30259	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 01 Nov 2005 00:03:16 +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 <01LUV40RDPHY9I4RMH@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 01 Nov 2005 00:03:00 +1100
Received: by localhost (Postfix, from userid 510)	id 5F0EA8000C; Tue,
 01 Nov 2005 00:02:30 +1100 (EST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by larry.its.monash.edu.au (Postfix) with ESMTP id BAE8C3C00E	for
 <dna@eng.monash.edu.au>; Tue, 01 Nov 2005 00:02:28 +1100 (EST)
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id CAAFCAE8	for
 <dna@eng.monash.edu.au>; Mon, 31 Oct 2005 14:02:26 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174])
 by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon,
 31 Oct 2005 14:00:11 +0100
Received: from esealmw114.eemea.ericsson.se ([153.88.200.5])
 by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon,
 31 Oct 2005 14:00:11 +0100
Date: Mon, 31 Oct 2005 14:00:08 +0100
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: RE: [DNA] Seeking WG input on Non-prefix link identifiers
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "Suresh Krishnan (QB/EMC)" <suresh.krishnan@ericsson.com>
Cc: dna@eng.monash.edu.au
Message-id: 
 <F08E178900F39344AC894077E6AF74D1010707DD@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] Seeking WG input on Non-prefix link identifiers
Thread-Index: AcXcLQDl12KO8Ke5QxCFC66UQ81DUQB6xOMw
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Brightmail-Tracker: AAAAAA==
X-OriginalArrivalTime: 31 Oct 2005 13:00:11.0001 (UTC)
 FILETIME=[06D4A690:01C5DE1B]
Content-Transfer-Encoding: 7BIT

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 Mon Oct 31 10:52:48 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWbxo-00043Z-EM
	for dna-archive@megatron.ietf.org; Mon, 31 Oct 2005 10:52:48 -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 KAA15483
	for <dna-archive@lists.ietf.org>; Mon, 31 Oct 2005 10:52:27 -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 <01LUV9WQG8FY9ASGB8@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 01 Nov 2005 02:52:24 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 4FA1AAB548; Tue,
 01 Nov 2005 02:52: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 F268B4FB15; Tue, 01 Nov 2005 02:52:19 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9VFpgu32145	for dna-list; Tue, 01 Nov 2005 02:51: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 j9VFpdd32141	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 01 Nov 2005 02:51:39 +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 <01LUV9VVIY3Q9A0F5W@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 01 Nov 2005 02:51:38 +1100
Received: by localhost (Postfix, from userid 510)	id BBFF08000D; Tue,
 01 Nov 2005 02:51:38 +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 82B943C010; Tue, 01 Nov 2005 02:51:37 +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 j9VFpZZD008988; Mon, 31 Oct 2005 10:51:35 -0500
Received: from redwood.research.panasonic.com
 (birch.research.pansonic.com [150.169.3.2])	by testing.research.panasonic.com
 (Postfix) with ESMTP id BFE6E1E818F; Mon, 31 Oct 2005 11:40:35 -0500 (EST)
Received: from [150.169.1.185] (unknown [150.169.1.185])
 by	redwood.research.panasonic.com (Postfix) with ESMTP id A9BB91E8188; Mon,
 31 Oct 2005 11:40:35 -0500 (EST)
Date: Mon, 31 Oct 2005 10:50:53 -0500
From: Sathya Narayanan <sathya@research.panasonic.com>
Subject: Re: [DNA] ACTION REQUIRED: End of	WGLC
	fordraft-ietf-dna-link-information-02.txt
In-reply-to: <4362ADA3.10504@ericsson.ca>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: suresh.krishnan@ericsson.ca
Cc: Dna <dna@eng.monash.edu.au>, greg daley <greg.daley@eng.monash.edu.au>,
        Alper Yegin <alper.yegin@yegin.org>
Message-id: <43663D5D.3070204@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:30.26935 C:22 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
References: <4362ADA3.10504@ericsson.ca>
Content-Transfer-Encoding: 7BIT


> b) If you think the draft is ready to submit to the IESG


I think the draft is useful and ready to be submitted to the IESG.

- Sathya



From dna-owner@webcamserver.eng.monash.edu.au Mon Oct 31 12:09:16 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWd9n-0000P6-K1
	for dna-archive@megatron.ietf.org; Mon, 31 Oct 2005 12:09: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 MAA21000
	for <dna-archive@lists.ietf.org>; Mon, 31 Oct 2005 12:08:54 -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 <01LUVCLMK4OO9AS9G4@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 01 Nov 2005 04:08:58 +1100
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 78006AB567; Tue,
 01 Nov 2005 04:08:53 +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 3523F4FB0A; Tue,
 01 Nov 2005 04:08:53 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9VH8Mt00779	for dna-list; Tue, 01 Nov 2005 04:08:22 +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 j9VH8Md00775	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 01 Nov 2005 04:08: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 <01LUVCKWN6209ASF6D@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 01 Nov 2005 04:08:18 +1100
Received: by localhost (Postfix, from userid 510)	id C07FBAB544; Tue,
 01 Nov 2005 04:07:48 +1100 (EST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	(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 9EE484FB15	for <dna@eng.monash.edu.au>; Tue,
 01 Nov 2005 04:07:47 +1100 (EST)
Received: from eamrcnt750.exu.ericsson.se
 (eamrcnt750.exu.ericsson.se [138.85.133.51])	by imr2.ericy.com (8.13.1/8.13.1)
 with ESMTP id j9VH9LEU000324	for <dna@eng.monash.edu.au>; Mon,
 31 Oct 2005 11:09:21 -0600
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service
 (5.5.2656.59)	id <VNG4999Y>; Mon, 31 Oct 2005 10:59:43 -0600
Received: from [142.133.72.115]
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
 by EAMMLEX034.lmc.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VAT956AR; Mon, 31 Oct 2005 12:04:54 -0500
Date: Mon, 31 Oct 2005 12:07:41 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] IMPORTANT: Combined DNA Solution draft
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Reply-to: suresh.krishnan@ericsson.ca
Message-id: <43664F5D.1040309@ericsson.ca>
Organization: Ericsson
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 (X11/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
Content-Transfer-Encoding: 7BIT

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 Mon Oct 31 13:13:48 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWeAG-0007BD-7c
	for dna-archive@megatron.ietf.org; Mon, 31 Oct 2005 13:13:48 -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 NAA25145
	for <dna-archive@lists.ietf.org>; Mon, 31 Oct 2005 13:13:28 -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 <01LUVETPMP8Y9A0A92@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 01 Nov 2005 05:12:43 +1100
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 96706AB542; Tue,
 01 Nov 2005 05:12:40 +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 52A694FB06; Tue, 01 Nov 2005 05:12:40 +1100 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id j9VIC9M01537	for dna-list; Tue, 01 Nov 2005 05:12:09 +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 j9VIC8d01533	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 01 Nov 2005 05:12:08 +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 <01LUVESS62SI9I4T6L@vaxc.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 01 Nov 2005 05:11:55 +1100
Received: by localhost (Postfix, from userid 510)	id 9DBEF80005; Tue,
 01 Nov 2005 05:11:55 +1100 (EST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	(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 A789D3C009	for <dna@eng.monash.edu.au>; Tue,
 01 Nov 2005 05:11:54 +1100 (EST)
Received: from eamrcnt751.exu.ericsson.se
 (eamrcnt751.exu.ericsson.se [138.85.133.52])	by imr2.ericy.com (8.13.1/8.13.1)
 with ESMTP id j9VIDST9006640	for <dna@eng.monash.edu.au>; Mon,
 31 Oct 2005 12:13:28 -0600
Received: by eamrcnt751.exu.ericsson.se with Internet Mail Service
 (5.5.2657.72)	id <VNHBBPZA>; Mon, 31 Oct 2005 12:11:52 -0600
Received: from [142.133.72.115]
 (dhcp723-115.rnet.lmc.ericsson.se [142.133.72.115])
 by EAMMLEX034.lmc.ericsson.se with SMTP
 (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VAT956ML; Mon, 31 Oct 2005 13:09:06 -0500
Date: Mon, 31 Oct 2005 13:11:54 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Subject: [DNA] Proposed agenda for IETF64
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Reply-to: suresh.krishnan@ericsson.ca
Message-id: <43665E6A.6010601@ericsson.ca>
Organization: Ericsson
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 (X11/20050923)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
Content-Transfer-Encoding: 7BIT

Hi Folks,
   Here is the proposed agenda for the dna wg meeting at IETF64 in 
Vancouver. If you think this needs to be modified in any way please feel 
free to comment. You can also find the latest version of the agenda at

http://www3.ietf.org/proceedings/05nov/agenda/dna.txt

Thanks
Suresh & Greg

Agenda for DNA wg at IETF64
===========================
Vancouver BC
Wednesday 2005/11/09 9:00am-11:30am

5 mins  - Agenda Bashing

10 mins - WG documents status and summary

15 mins - DNA hosts draft
           draft-ietf-dna-hosts-02.txt
  	  - Updates
  	  - Call for reviews

15 mins - DNA routers draft
           draft-ietf-dna-routers-01.txt
  	  - Updates
  	  - Call for reviews

15 mins - DNA Relocation delays
	  draft-vogt-dna-relocation-01.txt

15 mins - FMIPv6 Usage with DNA Protocol
	  draft-koodli-dna-fmip-00.txt

60 mins - Combined solution discussion
	  draft-pentland-dna-protocol3-00.txt
	  - Document desctription
	  - Open issues
	  - Consensus call



