Re: [Trigtran] FW: [dhcwg] Announce: BoF Proposal: Detecting Network Attachment

Greg Daley <greg.daley@eng.monash.edu.au> Tue, 17 June 2003 09:23 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04549 for <trigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 05:23:17 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H9MnO10072 for trigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 05:22:49 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H9Mnm10069 for <trigtran-web-archive@optimus.ietf.org>; Tue, 17 Jun 2003 05:22:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04537 for <trigtran-web-archive@ietf.org>; Tue, 17 Jun 2003 05:22:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SCdj-0004LR-00 for trigtran-web-archive@ietf.org; Tue, 17 Jun 2003 05:20:31 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19SCdi-0004LO-00 for trigtran-web-archive@ietf.org; Tue, 17 Jun 2003 05:20:30 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H5L0a07509; Tue, 17 Jun 2003 01:21:00 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H5K0m07454 for <trigtran@optimus.ietf.org>; Tue, 17 Jun 2003 01:20:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17307 for <trigtran@ietf.org>; Tue, 17 Jun 2003 01:19:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S8qk-0002hy-00 for trigtran@ietf.org; Tue, 17 Jun 2003 01:17:42 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx with esmtp (Exim 4.12) id 19S8qj-0002hs-00 for trigtran@ietf.org; Tue, 17 Jun 2003 01:17:41 -0400
Received: from thwack.its.monash.edu.au ([130.194.1.72]) by vaxh.its.monash.edu.au (PMDF V5.2-31 #39306) with ESMTP id <01KX7EVQ99BU9B73M6@vaxh.its.monash.edu.au> for trigtran@ietf.org; Tue, 17 Jun 2003 15:14:13 +1000
Received: from thwack.its.monash.edu.au (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id E8F4B12C029; Tue, 17 Jun 2003 15:14:12 +1000 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110]) by thwack.its.monash.edu.au (Postfix) with ESMTP id 0C55B12C025; Tue, 17 Jun 2003 15:14:10 +1000 (EST)
Date: Tue, 17 Jun 2003 15:14:09 +1000
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Trigtran] FW: [dhcwg] Announce: BoF Proposal: Detecting Network Attachment
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: john.loughney@nokia.com, spencer@mcsr-labs.org, trigtran@ietf.org
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <3EEEA3A1.8070102@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="US-ASCII"
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en, en-us
References: <BB13DDBE.36F9%alper@docomolabs-usa.com>
Content-Transfer-Encoding: 7bit
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

Sorry for this non-member posting.

Alper Yegin wrote:
>>Hi Spencer,
>>
>>
>>>I'm trading e-mail with Greg Daley, and I do believe there is a linkage,
>>>although DNA is focused below transport - they are more about address
>>>management, for instance, than about transport notification. I look forward
>>>to sitting in on their BoF in Vienna.
>>
>>Definately some relations, esp. when viewing the (sordid) history
>>of Trigtran (aka l2 triggers).
> 
> 
> It'd be useful to separate some of the terms here. TRRIGTRAN is not same as
> l2 triggers.
> 
> The linkage between TRIGTRAN and DNA is the link-layer triggers. Both are
> (potential) consumers of link-layer triggers. TRIGTRAN uses link-layer
> triggers for enhancing transport protocols. DNA can use these triggers to
> expedite the network attachment discovery (with increased confidence).
> Another consumer of the triggers if the FMIP work.

I think that if we're interested in maintaining the distinction
between Link-Layer and Network-Layer triggers, then TRIGTRAN
work (like spencers) may become a client for Network Layer triggers
instead.   This allows decisions to be made based on
network layer information (possibly relayed in some cases
from the link-layer).

For example, it would allow simple distinction between
"Attached to New network" and "Reattached to Old network"
triggers.  This information is able to be determined
using such techniques as router discovery or DHC at the
network layer.

While this may not be the most efficient delivery mechanism
available, it simplifies interfaces to L2/L3 and L3/L4.

Greg Daley

_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran