From: JF Tremblay <jean-francois.tremblay@viagenie.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [homenet] Routing protocol comparison document
Date: Tue, 3 Mar 2015 09:36:18 -0500 [thread overview]
Message-ID: <D9FFE432-B112-4D4C-AE26-1BED72621512@viagenie.ca> (raw)
In-Reply-To: <CAA93jw7JNLUt8-+VmDDWiuHr5x=aW=-jh07eDahR52FFFLLTyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
> On Mar 2, 2015, at 2:45 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I currently plan to enable some form of ipv6 translation by default in
> the next version of cerowrt - and make direct access optional - (or
> the reverse! I'm easy ) if somehow we get it together enough to
> actually have a way to do a cerowrt-scale effort again.
>
> Any objections here? Suggestions for how to make one of the ipv6
> translation techniques work right?
By IPv6 translation, do you mean a NAT66 stateless prefix translation as described in http://tools.ietf.org/html/rfc6296 <http://tools.ietf.org/html/rfc6296> ?
That could be useful for people like me behind a 6RD /60, I wouldn’t mind trying it with an internal ULA and see how it behaves. Not sure how current implementations behave though.
JF
[-- Attachment #2: Type: text/html, Size: 1563 bytes --]
prev parent reply other threads:[~2015-03-03 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54EE258E.8060302@gmail.com>
[not found] ` <201502272200.t1RM0Aru020484@maildrop31.somerville.occnc.com>
[not found] ` <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail.com>
[not found] ` <7ia8zvjkdq.wl-jch@pps.univ-paris-diderot.fr>
[not found] ` <CAA93jw6d+Fz3B24O9HWbgzKSX_z2KihkCSXkibbM+Zp0U8oxcQ@mail.gmail.com>
2015-03-02 19:45 ` [Cerowrt-devel] Fwd: " Dave Taht
2015-03-02 20:26 ` Toke Høiland-Jørgensen
2015-03-02 20:32 ` Aaron Wood
2015-03-02 20:45 ` Dave Taht
2015-03-03 14:36 ` JF Tremblay [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9FFE432-B112-4D4C-AE26-1BED72621512@viagenie.ca \
--to=jean-francois.tremblay@viagenie.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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