From: Brian Haley <brian.haley@hp•com>
To: Alexandre Cassen <acassen@freebox•fr>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH][RESEND] IPv6: 6rd tunnel mode
Date: Mon, 21 Sep 2009 22:39:45 -0400 [thread overview]
Message-ID: <4AB838F1.1090704@hp.com> (raw)
In-Reply-To: <20090922003956.GA19947@lnxos.staff.proxad.net>
Hi Alexandre,
Alexandre Cassen wrote:
> This patch add support to 6rd tunnel mode currently targetting
> standard track at the IETF.
>
> IPv6 rapid deployment (RFC5569) builds upon mechanisms of 6to4 (RFC3056)
> to enable a service provider to rapidly deploy IPv6 unicast service
> to IPv4 sites to which it provides customer premise equipment. Like
> 6to4, it utilizes stateless IPv6 in IPv4 encapsulation in order to
> transit IPv4-only network infrastructure. Unlike 6to4, a 6rd service
> provider uses an IPv6 prefix of its own in place of the fixed 6to4
> prefix.
I couldn't find RFC 5569 (delayed due to IPR rights?), although I did find
the latest 6rd draft, -03. It was showing as Informational, not Standards
track, is that right? Just curious.
> + case SIOCADD6RD:
> + case SIOCCHG6RD:
> + if (ip6rd.prefixlen >= 95) {
> + err = -EINVAL;
> + goto done;
> + }
> + t->ip6rd_prefix.addr = ip6rd.addr;
ipv6_addr_copy(&t->ip6rd_prefix.addr, &ip6rd.addr); is the preferred way to
copy the address.
-Brian
next prev parent reply other threads:[~2009-09-22 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 0:39 [PATCH][RESEND] IPv6: 6rd tunnel mode Alexandre Cassen
2009-09-22 2:39 ` Brian Haley [this message]
2009-09-22 6:59 ` Alexandre Cassen
2009-09-29 5:11 ` YOSHIFUJI Hideaki
[not found] ` <4AC19CD1.6060600@cisco.com>
2009-09-29 5:57 ` YOSHIFUJI Hideaki
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=4AB838F1.1090704@hp.com \
--to=brian.haley@hp$(echo .)com \
--cc=acassen@freebox$(echo .)fr \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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