Re: [hackathon] [vpp-dev] IETF 96 hackathon registration, champions/projects, and format tweaks

Is there any possibility to participate remotely?

I'm not sure if Hongjun is planning on going or if he could attend remotely
but he has been doing work on NSH Proxy in the NSH_SFC project...

On Thu, Jun 30, 2016 at 6:38 AM Christophe FONTAINE <
Christophe.FONTAINE@qosmos.com> wrote:

> Hi all,
>
>
>
> I’ll will be with a colleague from Qosmos at the next IETF Hackathon in
> Berlin :-)
>
> We’d like to focus on VPP/NSH : creating a NSH Proxy is one possibility
> among other things.
>
>
>
> Who is interested ?
>
>
>
> See you there,
>
> Christophe
>
>
>
>
>
> *From:* vpp-dev-bounces@lists.fd.io [mailto:vpp-dev-bounces@lists.fd.io] *On
> Behalf Of *Charles Eckel (eckelcu)
> *Sent:* mardi 24 mai 2016 23:43
> *To:* Ole Troan; vpp-dev
> *Subject:* Re: [vpp-dev] IETF 96 hackathon registration,
> champions/projects, and format tweaks
>
>
>
> It would be great to have VPP in Berlin. I am running the hackathon and am
> happy to answer any questions and help you get started.
>
>
>
> Cheers,
>
> Charles
>
>
>
> *From: *Ole Troan <ot@cisco.com>
> *Date: *Monday, May 23, 2016 at 7:45 AM
> *To: *vpp-dev <vpp-dev@lists.fd.io>
> *Cc: *Charles Eckel <eckelcu@cisco.com>
> *Subject: *Fwd: IETF 96 hackathon registration, champions/projects, and
> format tweaks
>
>
>
> Anyone on the list going to the IETF in Berlin? Want to do something on
> VPP?
>
>
>
> We had great fun doing SADR for VPP in Buenos Aires. Second best in show,
> and we attracted a few external people who only showed up to the IETF
> because of VPP.
>
>
>
> This is where running code meets the IETF, so if someone has an active
> draft in the IETF they want to implement that would be a great fit.
>
>
>
> This is in the middle of my summer holiday, so I might not be able to
> champion, but I would certainly be very supportive (while on the beach. ;-))
>
>
>
> Best regards,
>
> Ole
>
>
>
> Begin forwarded message:
>
>
>
> *From: *"Charles Eckel (eckelcu)" <eckelcu@cisco.com>
>
> *Subject: IETF 96 hackathon registration, champions/projects, and format
> tweaks*
>
> *Date: *20 May 2016 at 23:53:40 GMT+2
>
> *To: *"hackathon@ietf.org" <hackathon@ietf.org>, IETF chairs <
> wgchairs@ietf.org>
>
>
>
> Hey Folks,
>
>
>
> IETF 96 is rapidly approaching. As usual, the hackathon will be the
> weekend before, July 16-17. Check out the info page and register today:
>
> https://www.ietf.org/hackathon/96-hackathon.html
>
>
>
> So far, we have only two confirmed technologies represented on the wiki:
>
> https://www.ietf.org/registration/MeetingWiki/wiki/96hackathon
>
>
>
> Many of you have expressed interest in championing something in Berlin.
> Now is the time to update the wiki and inform others of your intentions.
> You don’t need to put much, just enough to give others a reasonable idea of
> what you plan to do and links to where to go for more info, suggested
> reading, existing code, etc. Do this asap to help recruit others to join
> you and make their travel arrangements accordingly.
>
>
>
> In anticipation of the largest hackathon ever, we are considering
> adjusting the format a bit to reduce the amount of time spent sharing
> project overviews at the beginning and presenting results at the end. If
> you have suggestions for how we can improve the hackathon, now is the time
> to share those thoughts as well.
>
>
>
> Cheers,
>
> Charles
>
>
>
>
>
>
>
> This message and any attachments (the "message") are confidential,
> intended solely for the addressees. If you are not the intended recipient,
> please notify the sender immediately by e-mail and delete this message from
> your system. In this case, you are not authorized to use, copy this message
> and/or disclose the content to any other person. E-mails are susceptible to
> alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall
> be liable for the message if altered, changed or falsified.
>
> Ce message et toutes ses pièces jointes (ci-après le "message")sont
> confidentiels et établis à l'intention exclusive de ses destinataires. Si
> vous avez reçu ce message par erreur, merci d’en informer immédiatement son
> émetteur par courrier électronique et d’effacer ce message de votre
> système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier
> ce message et/ou en divulguer le contenu à un tiers. Tout message
> électronique est susceptible d'altération. Qosmos et ses filiales déclinent
> toute responsabilité au titre de ce message s'il a été altéré, déformé ou
> falsifié.
> _______________________________________________
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev