From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ia0-x22a.google.com (mail-ia0-x22a.google.com [IPv6:2607:f8b0:4001:c02::22a]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id D84FA21F1C5 for ; Wed, 8 May 2013 03:34:38 -0700 (PDT) Received: by mail-ia0-f170.google.com with SMTP id k20so1829262iak.29 for ; Wed, 08 May 2013 03:34:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=SfA6bnDlBvO6LnBD9yGIa/fP8vxWwK9P+eUAHLSs01s=; b=e0vvJx/ESCuiRovrKMgjrbJUKdq0IzJbqESRX31MdMbNStiDDvaQuL4Q8tgDYHO49O aN0HskJBlR75U3S+H3F4CthMt44/VnOsRxfO6+dzh6hdamqRrsfwYdh5YR7oLohFKOGT jde7Hm3o3GAlv5Z0wxPrZ3BiIH2VxrvMSwPu8m2uZz/pYrGFK3LqIL1GNAX7aixWQvgx esJdBmEVJZ1tuP2KDeBXEdryEvvY4mxDA14Fd2RzJomUDaRtG+fVU6mBl5xFLPew2HZZ s/25pt4c6y+c2pUG3VEm9ukWO1/jUyGnOHVcPAyMNyl5o3BI/MDOx3akP1rO0OVh6QZf 2BcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=SfA6bnDlBvO6LnBD9yGIa/fP8vxWwK9P+eUAHLSs01s=; b=Ci2H1USrW0I0XOYons2b+LZ9y61kZPeQP0Ouy+SxDHP3D5qmIyfcQeNBg+jIftFo+3 5rhFs94ylliWK1wMkZGp3IwNHK+AE1Dbg8Z8HaIIF8f4x5WocuvoihQMXGinMFknWHPo otpnc6fY1J7ObAwG79Uxz4ypmsEuseHLGDfAJVQdwh/1+wpS0GWByjYFjaGXBTjkWRgL hEdxCmSTvmPJ/olB1lk8g3Prwc+l1Z71I/9bQY+eN9a6WNzr0F8wozZkhla9WsJbaI+L qWS69XvWEAKHcuO0Lej8NLQ5Su4CfePI2JOEqJJbYbQjs/uJ9wLvecVk9OV77FoR7p2X dtSg== X-Received: by 10.50.170.36 with SMTP id aj4mr2214642igc.4.1368009278216; Wed, 08 May 2013 03:34:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.237.148 with HTTP; Wed, 8 May 2013 03:34:18 -0700 (PDT) In-Reply-To: <2A989A4A-4E89-4177-A6A7-92E0E91C39FF@iki.fi> References: <518A18FA.4030600@openwrt.org> <2A989A4A-4E89-4177-A6A7-92E0E91C39FF@iki.fi> From: Lorenzo Colitti Date: Wed, 8 May 2013 19:34:18 +0900 Message-ID: To: Markus Stenberg Content-Type: multipart/alternative; boundary=e89a8f234a5114075a04dc327be2 X-Gm-Message-State: ALoCoQm4cLrO+fJUsWpIpKU8WDNyCRu34Ev/TTVDOgL/udelD/gatKWSJd23y/s2sEIVqXmPkPVIb13MzcPw3vR+RP2TNDBVv1T3ay1wG+ari19RRZSRNAePZy6emIJqFVtDmeCYSGgDXxHHJMZ9Yxbnc/fkILDHzvBdj53X1CQrv5dmFI1g/gUVPc8pdR3TxvqqzyZ2CdSUSeSRqLScGaTurIJOoSFdEg== X-Mailman-Approved-At: Wed, 08 May 2013 03:38:16 -0700 Cc: "homenet@ietf.org" , cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] [homenet] pushing the bird faster X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 10:34:39 -0000 --e89a8f234a5114075a04dc327be2 Content-Type: text/plain; charset=ISO-8859-1 On Wed, May 8, 2013 at 7:28 PM, Markus Stenberg 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? --e89a8f234a5114075a04dc327be2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, May 8, 2013 at 7:28 PM, Markus Stenberg <ma= rkus.stenberg@iki.fi> wrote:
IANA application is applicable iff draft is about to go RFC; I= 9;m not related to that author in any shape or form, so no clue (not even s= ure 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 ven= dor option and then update it when/if the draft gets traction?
<= /div>
--e89a8f234a5114075a04dc327be2--