Date: Thu, 13 Feb 2014 22:24:33 -0500 From: Jason Hellenthal <jhellenthal@dataix.net> To: Mark Martinec <Mark.Martinec+freebsd@ijs.si> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, "Wojciech A. Koszek" <wkoszek@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Merge ping+ping6 and traceroue+traceroute6 to single utilities? Message-ID: <05380FA6-4E24-4BFA-AB96-81665C867ABA@dataix.net> In-Reply-To: <3feb1ef62b087b8bf00f34c42c5c2954@mailbox.ijs.si> References: <1063008459.20140111160525@serebryakov.spb.ru> <52D14140.3090003@gibfest.dk> <20140111.143644.41639035.sthaug@nethelp.no> <52D15185.50802@gibfest.dk> <CAO2cuEM2qVu2PGOJ2WfFz-aiQKw8T6drGz4oxLkUAEnXptK8TQ@mail.gmail.com> <0c45208d87526a80f559ac09e28163c2.authenticated@ultimatedns.net> <EA9CBB60-05B6-4A7A-A904-7FCC791E8FB8@dataix.net> <DE9F510E-B9A5-4687-A364-8CD13D7F03F0@netgate.com> <CAF6rxgmOup-_%2B4=RAT-hD1cDfOUJ3F-6entDUDB7rgxjDXGkag@mail.gmail.com> <CAO2cuEMxu-ZSrq24y5jPBibCX8Fw10RKMMiGebK0zbiagdf_UA@mail.gmail.com> <CAN6yY1ssc9DzYDzfYA8BSTGRqR6TOdk%2BoB%2BadyMnrim8Vdoxig@mail.gmail.com> <3feb1ef62b087b8bf00f34c42c5c2954@mailbox.ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] > On Feb 13, 2014, at 20:40, Mark Martinec <Mark.Martinec+freebsd@ijs.si> wrote: > > 2014-02-11, Mark Martinec wrote: >> Remember the original PHK's story ( http://bikeshed.com/ ) ? >> It ended favourably for the sleep(1) command, it got its new feature. >> What can be learned there is: just needs someone to do it and be >> persistent enough to be accepted. >> Looks like a perfect task for Google Summer of Code 2014, >> time to apply is very near: >> http://www.google-melange.com/gsoc/homepage/google/gsoc2014 > > > 2014-02-12, Kevin Oberman wrote: >> For those who are new at IPv6, the ping6 and traceroute6 commands come from >> the WIDE KAME project. KAME developed one of the earliest IPv6 stacks and >> WIDE used FreeBSD. It became the FreeBSD IPv6 stack and the ping6 and >> traceroute6 utilities were brought in with the rest of the KAME code. >> When these tools were written, the IPv6 stack and the supporting libraries >> and APIs were very primitive. I suspect that it was quicker to write new >> tools than to try to integrate IPv6 into the existing standard tools and, >> when things were so rough, there was a clear effort to avoid changes to >> working IPv4 code. Separate IPv4 and IPv6 tools made sense then, but the >> need has long vanished... probably even before the KAME project ended. But >> the old, separate tools lived on through simple inertia. >> And so it is today. Inertia is NO reason that it should be this way forever. > > > I have submitted two entries for FreeBSD Google Summer of Code 2014: > > https://wiki.freebsd.org/SummerOfCode2014 > > (should show up there eventually after a review, I hope), > > one for a unified ping and ping6, the other for a unified traceroute > and traceroute6. My first impression was that it may be possible to do > both in a single 12 week GSoC job, although after checking existing > source code and writing the proposal it now looks to me more like > two full-time summer jobs, if they are to be done properly and with > attention to details. > > Looking for one, or preferably two, mentors for students for these tasks. > I wonder if Bjoern A. Zeeb wouldn't be the best man for the job ;) > Awesome, personally that would seem like the best route not only to have the focus on the tool itself but to put focus on achieving one or another either way it's progress. If we were voting I couldn't agree more with Bjoern if he would accept it.. Couldn't imagine someone more in depth to fit the task. [-- Attachment #2 --] 0 *H 010 + 0 *H 90000 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 130518085048Z 140519220947Z0H10Ujhellenthal@dataix.net1%0# *H jhellenthal@dataix.net0"0 *H 0 '`TmfkܨJ5u+c'Upb`zv)&ȸXZ*VN6JvLoVoh}g pQDŽKf/tZA˳("4Ԅ˻'d2h|IBl'^v^;'e8S99ۿVm|k8_UQtC"5l!kjZ]އQGn\Bh!FTsD%pV^Eӑd¨x"9 г"f 00 U0 0U0U%0++0UڔfmVʢ$䟓0U#0Sr풜\|~5NԸQ0!U0jhellenthal@dataix.net0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0 *H {0Ӹ,52W{Ey8b[{7 _+P"n["-,@ŽpJ-W$ݍjWA-6z( RdIZ.KzXє[K6}{s+v.Qh0PͅKhTw 0I73lz*Kv4Kkگ63;p1:ױ@)]ok>:W%XwC1þL/o8~#oP0400 *H 0}10 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o-we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&
