Re: [mif] mif route implementation
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 28 October 2011 11:52 UTC
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EB721F8B82 for <mif@ietfa.amsl.com>; Fri, 28 Oct 2011 04:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upb1vEWkAOKK for <mif@ietfa.amsl.com>; Fri, 28 Oct 2011 04:52:53 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2106121F8B70 for <mif@ietf.org>; Fri, 28 Oct 2011 04:52:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p9SBqoPs010936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <mif@ietf.org>; Fri, 28 Oct 2011 13:52:50 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p9SBqoPE001577 for <mif@ietf.org>; Fri, 28 Oct 2011 13:52:50 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p9SBqlr9016969 for <mif@ietf.org>; Fri, 28 Oct 2011 13:52:50 +0200
Message-ID: <4EAA978E.80609@gmail.com>
Date: Fri, 28 Oct 2011 13:52:46 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: mif@ietf.org
References: <4E88B6EF.9050800@gmail.com> <COL118-W23789C049B5BE989F7B721B1D20@phx.gbl> <4EA93870.4020302@gmail.com> <4EA94CB3.5090606@gmail.com> <4EA9654D.2010506@gmail.com> <4EA96BCA.204@gmail.com> <E6AE72A6-B520-475D-BC3C-27567745D1C0@nominum.com> <4EA98398.5010901@gmail.com>, <4EA98A0A.7090407@gmail.com> <COL118-W11C8CA9403D4E8A454FECDB1D30@phx.gbl>, <C19FDC2EB9C542E8BCD244D8863DD4B1@nex.west.ntt.co.jp> <COL118-W352F32E2841E6DB5E02C0CB1D30@phx.gbl>, <82965628686B49EEA46E9C2F7766C170@nex.west.ntt.co.jp> <COL118-W18815D2384C847DFD30EBDB1D30@phx.gbl>
In-Reply-To: <COL118-W18815D2384C847DFD30EBDB1D30@phx.gbl>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [mif] mif route implementation
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 11:52:58 -0000
Thank you for the information below, this is relevant support to route-option draft. Side remark: it says to support route-option-02, whereas now route-option is at its version 03. There is difference in message format which may impact implementation. Alex Le 28/10/2011 10:06, Hui Deng a écrit : > Hello all > > People are asking the implementation here, > thanks Okimoto-san about their information below, > > thanks a lot > > -Hui > ------------------------------------------------------------------------ > From: t.okimoto@rdc.west.ntt.co.jp > To: denghui02@hotmail.com; matsumoto.arifumi@lab.ntt.co.jp; > teemu.savolainen@nokia.com; margaretw42@gmail.com; jari.arkko@piuha.net; > rdroms@cisco.com; kato.junya@lab.ntt.co.jp > Subject: RE: mif route implementation > Date: Fri, 28 Oct 2011 17:01:44 +0900 > > Hi Teemu and Jun-ya, > How do you think about posting below information to MIF list? > # up to you. ;-) > Best Regards, > Tadahisa Okimoto > > ------------------------------------------------------------------------ > *From:* Hui Deng [mailto:denghui02@hotmail.com] > *Sent:* Friday, October 28, 2011 4:58 PM > *To:* 西研開 沖本 忠久; matsumoto.arifumi@lab.ntt.co.jp; Teemu > Savolainen; Margaret; Jari Arkko; ralph droms; kato.junya@lab.ntt.co.jp > *Subject:* RE: mif route implementation > > Hi Okimoto-san, > > Can you kindly help to forward this information to the mif mailing list? > thanks a lot for your help > > -Hui > > ------------------------------------------------------------------------ > From: t.okimoto@rdc.west.ntt.co.jp > To: denghui02@hotmail.com; matsumoto.arifumi@lab.ntt.co.jp; > teemu.savolainen@nokia.com; margaretw42@gmail.com; > jari.arkko@piuha.net; rdroms@cisco.com; kato.junya@lab.ntt.co.jp > Subject: RE: mif route implementation > Date: Fri, 28 Oct 2011 16:55:46 +0900 > > Hi Hui-san, > NTT lab shows demonstration with running codes at both IETF78 and > IETF79. > https://github.com/otroan/IETF-Non-Congruent-Multi-homing/wiki > Jun-ya is the guy. > Best Regards, > Tadahisa Okimoto > > ------------------------------------------------------------------------ > *From:* Hui Deng [mailto:denghui02@hotmail.com] > *Sent:* Friday, October 28, 2011 4:12 PM > *To:* 西研開 沖本 忠久; matsumoto.arifumi@lab.ntt.co.jp; Teemu > Savolainen; Margaret; Jari Arkko; ralph droms > *Subject:* mif route implementation > > Dear Okimoto-san > > MIF mailing list is discussing the implementation, I remeber > that NTT has showed this demonstration before. > Can you share this in the mailing list? > > thanks a lot > > -Hui > > > > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif
- Re: [mif] I won't be in Taipei for MIF WG Alexandru Petrescu
- Re: [mif] I won't be in Taipei for MIF WG Ted Lemon
- Re: [mif] I won't be in Taipei for MIF WG Alexandru Petrescu
- Re: [mif] I won't be in Taipei for MIF WG Alexandru Petrescu
- Re: [mif] mif route implementation Hui Deng
- Re: [mif] I won't be in Taipei for MIF WG teemu.savolainen
- Re: [mif] mif route implementation Alexandru Petrescu
- Re: [mif] route-option implementation Alexandru Petrescu