From: Lorenzo Colitti <lorenzo@google.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Cc: "homenet@ietf.org" <homenet@ietf.org>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [homenet] pushing the bird faster
Date: Wed, 8 May 2013 19:34:18 +0900 [thread overview]
Message-ID: <CAKD1Yr0-im+hT1Zz0QZv7_qmNRutowz_4SYgP3o+9UwHKjYAFg@mail.gmail.com> (raw)
In-Reply-To: <2A989A4A-4E89-4177-A6A7-92E0E91C39FF@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
On Wed, May 8, 2013 at 7:28 PM, Markus Stenberg <markus.stenberg@iki.fi>wrote:
> IANA application is applicable iff draft is about to go RFC; I'm not
> related to that author in any shape or form, so no clue (not even sure if
> draft is going anywhere, in IETF86 there was muted response at best to it
> if I remember right).
>
What about the non-prefix colouring work, like source-based routing, prefix
allocation, basic DHCPv6 fixes, etc.? Could that be merged upstream?
For the prefix-colouring work, you could always commit the code using a
vendor option and then update it when/if the draft gets traction?
[-- Attachment #2: Type: text/html, Size: 1040 bytes --]
prev parent reply other threads:[~2013-05-08 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw7Tz49OQ884k3ZRWk66iNqoPpYSpDj9Oy_9ztZutz-RKA@mail.gmail.com>
[not found] ` <loom.20130507T131132-321@post.gmane.org>
2013-05-08 9:07 ` Dave Taht
2013-05-08 9:20 ` Steven Barth
2013-05-08 9:23 ` Dave Taht
2013-05-08 9:27 ` Markus Stenberg
2013-05-08 9:32 ` Steven Barth
2013-05-08 10:22 ` Dave Taht
2013-05-08 10:28 ` Markus Stenberg
2013-05-08 10:34 ` Lorenzo Colitti [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=CAKD1Yr0-im+hT1Zz0QZv7_qmNRutowz_4SYgP3o+9UwHKjYAFg@mail.gmail.com \
--to=lorenzo@google.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=homenet@ietf.org \
--cc=markus.stenberg@iki.fi \
/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