Re: [hackathon] IETF 109 Hackathon webpage and wiki are now live

[Alexandre PETRESCU <[e-mail]>]

Michael, colleagues,

It is worth considering in detail how a hackathon could happen in a 
remote manner.

I fully agree with you when you say 'look over the shoulder, share 
caffeine, see packets' is very necessary, and impossible in a remote 
hackathon.

It is also difficult to support a hackathon activity by sendind devices 
via post.  A package sent to me by US Post in April arrived in July. 
Another one in August took 1 month.

I am interested in SLAAC trials; these are needing indeed both parties 
to be together on a local link.  To separate them and put Internet 
between them there might need VPN.  I suspect L2-VPN-bridge is that. But 
some linux devices are so small they might not implement VPN at all, or 
might lack some kernel features that might be required for that.  So 
again, this is hard to realize.

For my SLAAC activity, I am looking for testers of a SLAAC extension in 
the kernel. This extension, in linux, makes it possible to run plens 
like 65 and IIDs of length eg 63 (currently only 64/64 is possible in 
linux).  I think we would like this tested more prior to submission to 
the mainline kernel.  There is also opportunity to propose extensions 
(there are so many possible ways in which to form IIDs) and to author 
Internet Drafts.   The proposed code for this 'variable-slaac' is in 
github at https://github.com/dmytroshytyi/variable-slaac

Finally, the hackathon activity could be maintained alive by a few other 
things, such as advocacy, maybe just temporarily.  For my part I still 
advocate the use of IPv6 on sites who dont yet (eg github.com, and maybe 
dev.cisco.com);  maybe that advocacy could be used locally by the 
webserver admins to configure IPv6, without a need to interact with 
coffee and look at packets and over shoulder.  They could install it and 
I could browse it over the Internet.

Yours,

--
Alexandre Petrescu
[e-mail], tél [phone]

Le 11/09/2020 à 22:37, Michael Richardson a écrit :
> Charles, availability of the RPI based L2-VPN-bridges changes things
> significantly for me.  I was previously rather blase about remote hackathons.
>
> As long as I can't see your network traffic, and look over your shoulder, and
> share caffeinated beverages with you, then I might as well just stick to
> efforts to run stuff over the Internet.
>
> I learnt of the bridge option late, and that would have changed my opinion.
> I suggest that you mention this option on the
>     https://www.ietf.org/how/runningcode/hackathons/109-hackathon/
> page.
>
> How soon are we able to test things?   I might even want to prep devices and
> mail them to people.
>
> Right now, it's a bit buried on the wiki.
>
>     The NOC team has been working to allow you to join the IETF network while
>     attending the meeting remotely. With a Raspberry Pi 2 or newer the NOC has
>     a recipe that will allow your team to be virtually connected to the IETF
>     network with IPv4 and IPv6 addresses and many options (IPv6ONLY, a closed
>     user group, NAT64, IPv6PD, and more) for you to use for your
>     projects. Your project champion can request getting access by sending a
>     message to ietf109virtualnetwork @ noc.ietf.org. Please include your
>     project name and members. The NOC will provide you with the recipe.
>
> (oops, it seems that the email address does not yet work)
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
> ]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [
>
>
>
>
> _______________________________________________
> hackathon mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/hackathon