Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 25 February 2015 20:54 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C321A8840 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 12:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12mzyGL9VGTa for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 12:54:29 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34A001A1EFF for <ietf@ietf.org>; Wed, 25 Feb 2015 12:54:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2506; q=dns/txt; s=iport; t=1424897669; x=1426107269; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=s18f9fKuL4V1G4nXaAbcZ0ZKRBNAr21AgbsrGoyU8dU=; b=egxVFUo1si1bCy3UMEEwUkeom3EgtklmPttbZBOVXgarVIqU2FoWOYab P7dy0lGbulrgMDoeR9aWVmn/zIlytRkS70ffy/cocOR41ZT1LmBc7TwvS 3lakAIX9W9403Xj6+vU31o3V+vZBdPmYGCRIcbXJ22PyoxQlHb7t7MHDU 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AlBgAFNu5U/5hdJa1bgwJSWgSDBboohXKFcAIcgQxDAQEBAQEBfIQQAQEENEUQAgEIGAQRAQEVAgIfESUCBA4FFIgHAxENn3ucZAaTaA2FOAEBAQEBAQEBAQEBAQEBAQEBAQEBARMEgRuJeIE9gQeBdxgbBwoIAYJPgUkFj1yDYINgP4FGjTeGByKCD4FfbwGBAwcXIn8BAQE
X-IronPort-AV: E=Sophos;i="5.09,647,1418083200"; d="scan'208";a="126944398"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP; 25 Feb 2015 20:54:28 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t1PKsSao017588 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Feb 2015 20:54:28 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.45]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Wed, 25 Feb 2015 14:54:28 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Topic: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Index: AQHQUFOkH7HlE1Nn2E6m2YbduHXwrZ0AmaaAgADYLwD///PXAIAAihQAgAAMnACAAAG1gIAACV+AgAAH3oD//51dgIAAh2iA//98MAAAEM/CAP//gYsA
Date: Wed, 25 Feb 2015 20:54:27 +0000
Message-ID: <D1137564.3E89E%eckelcu@cisco.com>
References: <20150224170152.6224.60832.idtracker@ietfa.amsl.com> <09B0A2B7-7D6B-4365-B58C-AAD97C3BE73D@lucidvision.com> <B32A64D5-0B07-4E01-92B1-DEAF21002EE7@netapp.com> <D1132FAF.3E752%eckelcu@cisco.com> <54EDF486.20000@gmail.com> <D275D180-272B-43C7-BDF0-FE2B438DEB60@lucidvision.com> <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.com> <54EE0865.4090101@gmail.com> <CAHw9_iKA7bgZH6iJLw1y7=qz6MJDePgUbCeOtHXnaajCKshRnw@mail.gmail.com> <D1136BA7.3E85D%eckelcu@cisco.com> <54EE2DD7.1030408@gmail.com> <D1136F2B.3E87C%eckelcu@cisco.com> <54EE3016.3040106@gmail.com>
In-Reply-To: <54EE3016.3040106@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.24.213.76]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <2BA81007324AA347B13154622EED47D4@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_VzTVQj5uw2qYmoJTBu8-qd23qc>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 20:54:31 -0000

We are using the Cisco community page to host the ongoing discussion
forum. Here is the info found there as to how IETF and Cisco are both
involved in the Hackathon (sorry for poor formatting resulting from
copy/paste).

IETF is providing the room and the network for the event.
Cisco DevNet is running the Hackathon, paying for food, prizes, etc.
* Hackathon information is hosted on the DevNet site: Cisco DevNet: IETF
Hackathon at IETF 92, March 21-22
<https://developer.cisco.com/site/ietf-hackathon/>
* Ongoing discussion is encourage, and is hosted within the Cisco
developer community page: IETF Hackathon
<https://communities.cisco.com/community/developer/ietf-hackathon>

All interested parties click to a reg form on the IETF site: IETF
Hackathon 2015 Dallas
<https://www.ietf.org/meeting/92/hackathon-signup.html>
* Registration is handled entirely by the IETF, in accordance with IETF
privacy requirements.
*  Registered attendees will not need to have become DevNet members.
* Registered attendees will be shown and reminded that their participation
is subject to the IETF Note Well: Note Well
<https://www.ietf.org/about/note-well.html>

A link to the same info is:
https://communities.cisco.com/message/175271#175271 (and yes, there is the
hassle of getting a CCO account if you do not have one).

Cheers,

Charles

On 2/25/15, 12:27 PM, "Melinda Shore" <melinda.shore@gmail.com> wrote:

>On 2/25/15 11:25 AM, Charles Eckel (eckelcu) wrote:
>> Perhaps, but I¹m trying to scale better, and keeping things in once
>>place
>> helps. Similar questions have come from other IETF aliases as well as
>>from
>> people outside of the IETF entirely.
>
>Why does the "community" page require a Cisco login?  I really
>don't understand what you're doing, here.
>
>Melinda
>
>