[ietf85-tech] Fwd: [Netconf] Netconf Interoperability Testing Nov 3-4, 2012 in Atlanta

James Dishongh jdishongh at verilan.com
Fri Sep 28 12:41:58 PDT 2012


Thanks for the heads up Chris.

On Sep 28, 2012, at 11:27 AM, Chris Elliott wrote:

> All,
> 
> Just a head's up. the NETCONF working group will be doing an 
> interoperability test event Saturday and Sunday. The IETF has 
> provided a room. They've asked for internet connectivity, and
> probably will want a small switch for wired in addition to 
> wireless.
> 
> I've stated that we can provide the same level of service on
> Saturday as we provide to the code sprint--basically best
> effort. I've also stated that they may be able to fall back
> to the hotel network if required, and that there will be
> restrictions on that network. They are OK with this
> service level.
> 
> This room should be on Marcia's provided list of rooms.
> 
> Chris.
> 
> ---------- Forwarded message ----------
> From: Bert Wijnen <bwijnen at ripe.net>
> Date: Wed, Sep 26, 2012 at 4:24 AM
> Subject: [Netconf] Netconf Interoperability Testing Nov 3-4, 2012 in Atlanta
> To: Netconf <netconf at ietf.org>
> 
> 
> Dear NETCONF implementers,
> 
> We have secured a room at the IETF85 Hotel (Atlanta Hilton)
> for 2 days for NETCONF interoperability testing.
> 
> This will be on
> - Saturday Nov. 3rd from 9:00-18:00
> - Sunday   Nov. 4th from 9:00-16:00
> 
> We are planning/trying to provide remote access for remote
> participants. We're not sure yet if we can have it for both days
> and how well it will work. We will focus on the participants
> that show up at the event (after all they travel and make
> expenses to be there) to maximize the high-bandwidth
> interaction we can have in the f2f event.
> 
> If you want to participate, you can register here:
>   http://doodle.com/nibe3k4c4zuq84mw
> 
> BUT, note that access to the event requires that you:
> - sign an NDA and
> - bring an implementation to test with the other participants
> - send us a list of what NETCONF features/capabilitues and
>   which YANG modules your server/client implements/supports.
> 
> The NDA we intend to use is attached. It is still called "draft",
> but unless someone detect a fatal flaw in it, this will be the
> one that we use.
> 
> Bert and Mehmet
> 
> _______________________________________________
> Netconf mailing list
> Netconf at ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 
> -- 
> Chris Elliott
> chelliot at pobox.com
> 
> <AtlantaNetconfInteropNDA-draft-02.pdf>_______________________________________________
> ietf85-tech mailing list
> ietf85-tech at daedelus.com
> http://www.daedelus.com/mailman/listinfo/ietf85-tech

James Dishongh
Engineering Project Manager

Verilan, Inc.
7327 SW Barnes Road #215
Portland, OR 97225
+1 360.907.9237
jdishongh at verilan.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daedelus.com/pipermail/ietf85-tech/attachments/20120928/b1e7d7ed/attachment.html 


More information about the ietf85-tech mailing list