a sdcpe package 'feed' request

[Dave Taht]

On Tue, Mar 13, 2012 at 3:22 PM, Francis Dupont <fdupont at isc.org> wrote:
>> > My concern is the stable aka backfire 10.03.1
>> > is still 2.6.32.
>>
>> Stable is totally useless for ipv6 work.
>
> => totally useless is a bit strong but I agree this must be improved.

After being involved in fixing multiple ipv6 related bugs over the past
year, and seeing the depths of "lack in the stack", I'm impressed that ever
worked at all. 'totally' useless is a bit strong, I agree, but there is
a long way to go before ipv6 is generally useful.

Things are looking brighter on the kernel side since 2.6.39 (.32? hopeless),
but the tools and integration of such is something an ongoing
nightmare. Also all the
main AQMs have no ipv6 support in them. Etc.

>
>> >> However I don't know to what dslite MTU code you're referring to?
>> >
>> > target/linux/generic-2.6/patches-2.6.32/1014-dslite-ipv4.patch
>>
>> thx. I'll look.
>
> => note I don't say you have to integrate it. IMHO the ipv6tunnel
> is far more interesting, in particular the GUI part.

k.

>
>> I understand, it was me puzzling over why you mentioned 6rd
>> in the first place as to why I mentioned this.
>
> => in fact 6rd was in the Comcast plan so the dslite-6rd got both.

Yes, I deployed 6rd in conjunction with their testing last year. Due to
the brain-dead deployment of such (only a /64) I reverted to using
6to4 which was at a 'just working' state at least until recently, and
their 6to4 gateways were excellent.

They plan another brain-dead deployment of native ipv6, a /64 only
because only one of the cpe gear they have can even do that with pd.

With wide-dhcp PD I have users in new zealand that are dealing  with /48s
and /56s just fine. With dibbler I had problems with anything not on a /8
boundry, and a problem with the client running away chewing up 100%
of cpu after a day...

(there were several other problems, now resolved, I simply haven't
 had time to get back on these others)

> Today 6rd is included in kernels (at the exception of OpenWRT stable)
> so there is even less need for it (:-).

free.fr?

>> >> It would be helpful if you were to get a wndr3800 via amazon.fr...
>> >
>> > => it is not in my schedule.
>>
>> ?
>
> => yes, it is not in my plan to buy another CPE I'll use 2 days per
> year (or less now the AFTR netbook is nearly dead).
> And from the beginning I raised a concern about using CPE hardware
> for development.

I to this day have zero problems with not actually using the cpe
hardware to be the cpe on this crazy first deadline. It had been
pitched to me as a 'really nice to have' feature, and as my own
project was nearing it's ship date, seemed doable.

I do note that I have no plans to be at this ietf meeting, nor do I
think it is possible,due to my visa being over-extended.

>
>> > => I work at home so I have no infrastructure.
>>
>> The latter question (what hours do you keep) was more relevant.
>
> => I am at partial time (1/3 so 12 hours per week officially) and
> I work at any hour at the exception of early morning in my timezone
> (UTC+1, UTC+2 since the end of the month).


> And should add my phone is in another room (so I don't write code
> when I am at the phone).

Well, I setup a chat room for this project to possibly make it easier
to interact in real time. Would that work?

I try not to do phone calls myself, being partially deaf, and when I
do, try to use something of reasonable quality, like skype.
>
> Regards
>
> Francis Dupont <fdupont at isc.org>
>
> PS: going to the other room for a phone call



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net