From: Alexandre Cassen <acassen@freebox.fr>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH][RESEND 3] IPv6: 6rd tunnel mode
Date: Wed, 23 Sep 2009 13:07:27 +0200 [thread overview]
Message-ID: <1253704047.17175.48.camel@lnxos-dev> (raw)
In-Reply-To: <20090923184314.a2a2701d.yoshfuji@linux-ipv6.org>
On Wed, 2009-09-23 at 18:43 +0900, YOSHIFUJI Hideaki wrote:
> Hello.
>
> First of all, thank you for this work.
>
> On Wed, 23 Sep 2009 00:02:51 +0200
> Alexandre Cassen <acassen@freebox.fr> wrote:
>
> > This patch add support to 6rd tunnel mode as described into
> > draft-despres-6rd-03.
> >
> > Patch history :
> > * http://patchwork.ozlabs.org/patch/26870/
> > * http://patchwork.ozlabs.org/patch/34026/
> > * http://patchwork.ozlabs.org/patch/34045/
> >
> > IPv6 rapid deployment (draft-despres-6rd-03) builds upon mechanisms
>
> Well, I was confused. I think draft-softwire-ipv6-6rd
> is the latest one, no?
draft-despres-6rd-03 : targeting informational RFC
(=> currently pending)
draft-softwire-ipv6-6rd : targeting standard track
after last IETF meeting previous draft-townsley-ipv6-6rd as been pushed
to IETG softwires WG.
So you right, ref should be set to draft-softwire-ipv6-6rd.
> Another comment is that we should combine 6to4
> and 6rd.
Completly agree. 6to4 is a special case of 6rd.
Okay, so I stop producing (fixing according to last comments) and
resending new patch for 6rd.
regs,
Alexandre
next prev parent reply other threads:[~2009-09-23 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 22:02 [PATCH][RESEND 3] IPv6: 6rd tunnel mode Alexandre Cassen
2009-09-22 22:18 ` Eric Dumazet
2009-09-23 6:07 ` Alexandre Cassen
2009-09-22 23:06 ` Joe Perches
2009-09-23 1:47 ` Brian Haley
2009-09-23 9:43 ` YOSHIFUJI Hideaki
2009-09-23 11:07 ` Alexandre Cassen [this message]
2009-10-07 8:24 ` David Miller
2009-10-07 14:18 ` Steffen Klassert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1253704047.17175.48.camel@lnxos-dev \
--to=acassen@freebox.fr \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).