Index: [Article Count Order] [Thread]

Date: Thu, 14 Feb 2008 09:45:54 +0900
From: Yukiyo Akisada <akisada@tahi.org>
Subject: [users:00596] Re: vel support version
To: Yinghui.Yao@alcatel-lucent.com, yu-inoue@jp.fujitsu.com
Cc: users@tahi.org
Message-Id: <20080214094554.88aed534.akisada@tahi.org>
In-Reply-To: <47B33480.9000202@alcatel-lucent.com>
References: <20071221223737.17ED.YU-INOUE@jp.fujitsu.com>	<20080206092510.cb76357b.akisada@tahi.org>	<47A8FFBF.1000401@alcatel-lucent.com>	<20080206094955.e1a9e489.akisada@tahi.org>	<47B33480.9000202@alcatel-lucent.com>
X-Mail-Count: 00596

Hi, Yao.

FreeBSD, NetBSD, OpenBSD, BSD/OS and MacOS can be considerd as different.
Importance is difference of vendor which is developping current IPv6 stack.
They has the same root of history, but they are going their own way now by different vendors.

In addition,
every Linux is considerd as the same
because it is considerd that IPv6 stack in Linux is developped by kernel.org.
by IPv6 Ready Logo Committee.

Thinkng about KAME and USAGI,
they can be considerd as different from any BSD and any Linux
because vendor which is developping IPv6 stack is different from them.

For example, FreeBSD and KAME/FreeBSD can be considerd as differnt.
In this case vendors are The FreeBSD Project and The KAME project.
NetBSD and KAME/NetBSD can be also use the same rule.
So you can use any OS for KAME and USAGI.

But if you use KAME or USAGI,
description of OS name is also needed in application form.

Thanks,


On Wed, 13 Feb 2008 11:18:40 -0700
Yinghui Yao <Yinghui.Yao@alcatel-lucent.com> wrote:

> Thanks Yukiyo for a lot help. It seems I'm beating a dead horse here.
> 
> FreeBsd and NetBSD are considered different. How about openBSD, BSD/OS, 
> MacOS? The vel README also says that we can use KAME and USAGI? Aren't 
> they only stacks/projects? What OS should I use for KAME and USAGI?
> 
> Thanks again.
> Yinghui Yao
> Alcatel-Lucent
> 
> 
> Yukiyo Akisada wrote:
> > Hi, Yao.
> >
> > I don't prefer anything.
> >
> > It depends on your situation.
> > In this moment, there is the tradeoff
> > between cost and reducing mistakes when you re-run the test.
> >
> > Anyway, Akisada is my last name. :-)
> >
> > Thanks,
> >
> >
> > On Tue, 05 Feb 2008 17:30:55 -0700
> > Yinghui Yao <Yinghui.Yao@alcatel-lucent.com> wrote:
> >
> >   
> >> Hi Akisada-san,
> >>
> >> Does this mean "manual testing" is a preferred way for interoperability 
> >> at this time? (Is Akisada your last name?)
> >>
> >> Thanks,
> >> Yao
> >>
> >> Yukiyo Akisada wrote:
> >>     
> >>> Hi, Inoue-san.
> >>>
> >>> I'm sorry for having kept you waiting.
> >>>
> >>> vel-1.0.4 doesn't support test scenario v2.8.4.
> >>> I mean supported version is older.
> >>>
> >>> In this moment,
> >>> you must modify *.sc files if you use vel to obtain the logo.
> >>>
> >>> Updating vel still has been in our queue for developping,
> >>> but the next release may take several months.
> >>>
> >>> Thanks,
> >>>
> >>>
> >>> On Fri, 21 Dec 2007 22:39:22 +0900
> >>> inoue yu-ichi <yu-inoue@jp.fujitsu.com> wrote:
> >>>
> >>>   
> >>>       
> >>>> Hello All,
> >>>>
> >>>> We want to use vel(TAHI IPv6 Interoperability Test Suite) to get phase2.
> >>>>
> >>>> But vel README is
> >>>> ---
> >>>>     - example/interop_ph2_core/
> >>>>         Directory interop_ph2_core includes Interoperability test
> >>>>         scenario maker. It supports Phase-2 Test Interoperability
> >>>>         Specification Core Protocols version 2.8.0.
> >>>> ---
> >>>>
> >>>> latest interoperability specification revision is 2.8.4.
> >>>> vel support version is older than latest.
> >>>>
> >>>> Can We use vel to get phase2?
> >>>>
> >>>> Thanks,
> >>>> inoue
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>     
> >>>>         
> >>> ------------------------------------------------------------------------
> >>> Yukiyo Akisada <akisada@tahi.org>
> >>>
> >>>   
> >>>       
> >>
> >>     
> >
> >
> > ------------------------------------------------------------------------
> > Yukiyo Akisada <akisada@tahi.org>
> >   
> 
> 


------------------------------------------------------------------------
Yukiyo Akisada <akisada@tahi.org>