Home
Vendor
Project
  Phase I
Press
  Phase I
About
You Are Using IPv4 To Access This Site
Your IP Address is: 38.107.191.84

[>>> SPAM <<<] - RE: [>>> SPAM <<<] - [moonv6] Good MIPv6 Deployment Analysis via Masters Thesis - Email found in subject - Email found in subject

New Message Reply Date view Thread view Subject view Attachment view

From: Ed Remmell (eremmell@treck.com)
Date: 01/13/05


moonv6 post from "Ed Remmell" <eremmell@treck.com> Rodolfo -

I saw in your masters thesis that this was affiliated with Motorola/Freescale? We have a partnership with them, specifically with the team doing the NE64 processor. The Coldfire processor is a good target for our protocols to run on, we recently integrated Treck protocols with Quadros RTXC to run on that processor (for example).

> I've configured uClinux to use 1MB RAM in the evaluation
> board.
> In the future I plan to make it work with less memory.
> I'm going to generate the .map file and send it to you.

I'm looking forward to seeing the .map file. I expect your ROM footprint is pretty big, i.e. megabytes. We can easily fit all of the Treck MIPv6 MN functionality, including Treck Ipsec and IKE, with route optimization and some room left over for applications, in less than 200K bytes of ROM, and at run-time this configuration would require approximately 100K bytes of RAM.

So, I'd expect to see an order-of-magnitude difference in both RAM and ROM usage between our implementation (smaller) and your prototype (bigger) using uCLinux and LIVSIX.

> Regarding the interrupt latency, unfortunately I haven't
> taken any measurement about it but I could do it. If you need
> that information, please just tell me and I'll do it.

I'm just curious, from a competitive standpoint. Treck protocols are designed specifically for embedded systems, so of course they do support hard real-time since we have very short critical sections throughout our code (it is part of our coding standard that all of our products must comply with, designed in from the beginning). I'd expect that your prototype cannot support hard-real time, since large and variable interrupt latency is a characteristic of Linux (Linux wasn't designed for embedded systems).

Approximately how long does your prototype take to boot all of the way up, to the point where all of the uCLinux and LIVSIX services are running and you can actually use the chat application over MIPv6?  

> I'm very interested in knowing more
> about Treck's Mobile IPv6 stack (I've already read
> http://www.treck.com/PDF/Mobile_IPv6.pdf), I suppose it is
> related to the Voyager Mobile IPv6 stack announced by Elmic
> on June 2003, right?

It is the exact same product. Elmic Systems, USA, used to be Treck Inc. (a U.S. company, headquartered in Cincinnati Ohio) before it was bought by Elmic Systems, Japan in 2000. Then, at the end of 2004, Elmic Systems, Japan sold Elmic Systems, USA back to the original owner of Treck Inc. So, we are back to being Treck Inc. again (same as before: a U.S. company, headquartered in Cincinnati Ohio, but now with an additional engineering office in Riverside, CA).

> In my work, in page 38, there's a link
> to the Treck's web site, as an example of a Mobile IPv6 stack
> for embedded systems and RTOS. Do you have MIPv6
> implementations for routers and mobile agents?

We have an implementation of MIPv6 HA that we used for testing, but it wasn't designed to be a product. We sell it with our MIPv6 CN option. We also sell a MIPv6 MN option. We have full implementation of both IPv4 and IPv6 packet forwarding/routing, however we only have RIPv4 listener, we don't have many routing protocols.

If you are interested/curious, I can email you a copy of our MIPv6 user documentation (most of it is MN). It has some example code showing how to use our MIPv6 MN and Ipsec/IKE APIs. This same example code is part of our Treck Win32 dual stack demo, which has our MIPv6 MN functionality (you need to use it with a MIPv6 HA that supports DHAAD, the Cisco HA didn't when we participated in the phase 1 MoonV6 testing). Our Treck Win32 dual stack demo is available here:

http://www.treck.com/TreckDemo.zip

This version doesn't have the Ipsec encryption algorithms, due to U.S. export restrictions on encryption technology. The full version (with Ipsec encryption) is available to U.S. companies (and their subsidiaries) by sending a request to support@treck.com. It runs over winpcap - I just found out that the newer 3.1 version of winpcap won't work since they removed one of their public APIs in packet.dll (hopefully they will fix that), but it works with any other version of winpcap starting with 2.3 up to and including 3.0. 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 1/12/2005
 


---
Treck, Inc. -  Confidentiality Notice
 
This electronic transmission may contain information that is proprietary or confidential.  You are hereby notified that any dissemination, distribution or duplication of this electronic transmission to some other entity, without the expressed written consent of Treck, Inc.  is strictly prohibited, unless the contents of this electronic transmission specifically authorizes you to do so.  If your receipt of this electronic transmission is in error, please notify the corporate offices of Treck, Inc.  immediately by  calling (513) 528-5732, or by reply to this transmission.
New Message Reply Date view Thread view Subject view Attachment view

This archive was generated by hypermail 2.1.7 : 12/01/06 EST