Re: [Rtg-open-source] rtg-open-source list and meeting at IETF 98

Alia Atlas <akatlas@gmail.com> Wed, 08 February 2017 19:59 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtg-open-source@ietfa.amsl.com
Delivered-To: rtg-open-source@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE8A12A02E for <rtg-open-source@ietfa.amsl.com>; Wed, 8 Feb 2017 11:59:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jMwXNTye-zRw for <rtg-open-source@ietfa.amsl.com>; Wed, 8 Feb 2017 11:59:32 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A469612A02A for <rtg-open-source@ietf.org>; Wed, 8 Feb 2017 11:59:31 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id v77so203539719wmv.0 for <rtg-open-source@ietf.org>; Wed, 08 Feb 2017 11:59:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TGPm/8LqRVgqcG5Ugf4HWyejAZVMdcHeOJQ76QSCRlc=; b=Ehudkco/uAxzdwmfX8qjUI1LkNaqit+FHkuyTxRHLwNLR5z1JQ7YBdB7n2A3mWtPll Bag+Em0HUNcGoK2chbNOmilT/ACEPcMO5tpFwQLySkeK1BLTlAZCmw0BM/I1+cdreuUM cq6EpgSCR28HnXTlDiICNmHH0i/5su0shG3jYGVRvmeopbkf20iX20m/zn8Ed0kgUJri I0U3awll8nBOBl7oP1fePIAnq4UnMJkouvaJJlZQnqdkOgbw9kr5YkG7V1WyFahtb7s+ 8MI3PivDghSfoZDJ6GJj9HvfrcciGb6+m4PktA2FoVF2oD6Y9o51IN3W6Ki8PhN6lWv6 PoFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TGPm/8LqRVgqcG5Ugf4HWyejAZVMdcHeOJQ76QSCRlc=; b=WYvSXUZiJWwWGR5k+wOljIzd1uItXkg6LiD/REclk1QjEmLwkaGocCtxyu2Wvl8ezx xhUEBRdWrc0tASvOMBlc17d1hJ7z+PLjTHvfg1cwivCs4fzMRAKBMDrIqSi/RqB18Xfl bukYEaERYlcCMNHLuq8XyXeXehEKuSt/2SzdbK6SHh6uIKobvpn5qzsdo0szKWS/G98V N9Rz0gl+CQh8ocUe8UEgtlm7rx7ZBf5VA96JF1UVgj1vVGrme7Sc5Wup/YxQ6uHC3JWs k6m/Om8z7ChbH4qKeqF1KcY1mfHdOGbTuWYw9IWZTsnb7PCeNblesVH7IxKQyf95kJsX 8ABg==
X-Gm-Message-State: AMke39m5jQ4euWx9NWlkTxV8e6KUd+VH6AgRWiAofZaqTeObzw23XXrRDT74cC05TKN7K6FcJHl8xOwBpXwzmw==
X-Received: by 10.28.30.79 with SMTP id e76mr18411385wme.96.1486583970095; Wed, 08 Feb 2017 11:59:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.142.108 with HTTP; Wed, 8 Feb 2017 11:59:29 -0800 (PST)
In-Reply-To: <0EB481B0-E8E9-49B3-AA95-E97C669A7A23@cisco.com>
References: <CAG4d1rdoxiB+NDO9CN6xCRja1VUu=m8E57zds-iRscszd02hww@mail.gmail.com> <0EB481B0-E8E9-49B3-AA95-E97C669A7A23@cisco.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 8 Feb 2017 14:59:29 -0500
Message-ID: <CAG4d1rdHq+WrdK-PfxdsqgqnGTHVFAhfPMLx2bZQo8F6KwiYKA@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: multipart/alternative; boundary=001a114b2de4776b8105480a4d31
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-open-source/WhGVfu8cmdra1XTatE3Wdb7Vqu0>
Cc: "rtg-open-source@ietf.org" <rtg-open-source@ietf.org>
Subject: Re: [Rtg-open-source] rtg-open-source list and meeting at IETF 98
X-BeenThere: rtg-open-source@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion and collaboration for Open Source efforts related to the Routing Area <rtg-open-source.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-open-source>, <mailto:rtg-open-source-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-open-source/>
List-Post: <mailto:rtg-open-source@ietf.org>
List-Help: <mailto:rtg-open-source-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-open-source>, <mailto:rtg-open-source-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 19:59:33 -0000

Hi Charles,

Thanks for the feedback.   The last couple we've just gone around the room
and done introductions.
I'd rather see something more useful/interactive this time as well.  I'm
happy to approve (or request)
a room and assume that Thursday breakfast would be the time, again.

I'd be delighted to see some self-organization on the list around what
would be useful to do or discuss.

I'm happy to attend and listen and think about what can be usefully done
for better integration, but
I don't think that I can personally drive this community or the meetings
and have them be beneficial.

Regards,
Alia

On Wed, Feb 8, 2017 at 2:32 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com>;
wrote:

> Hi Alia,
>
>
>
> I think an in person meeting would be useful and will prioritize it in my
> schedule if it occurs.
>
> I found our brief meeting at IETF 97 informative and a good use of time.
>
>
>
> Cheers,
>
> Charles
>
>
>
>
>
> *From: *Rtg-open-source <rtg-open-source-bounces@ietf.org>; on behalf of
> Alia Atlas <akatlas@gmail.com>;
> *Date: *Friday, February 3, 2017 at 12:49 PM
> *To: *"rtg-open-source@ietf.org"; <rtg-open-source@ietf.org>;
> *Subject: *[Rtg-open-source] rtg-open-source list and meeting at IETF 98
>
>
>
> There hasn't been substantial discussion or coordination on the
> rtg-opens-source mailing list.  We did meet in person at IETF 97 and there
> was a suggestion for having a more general meeting (non-WG forming BoF type
> thing) that would discuss different open source projects, their maturity,
> and deployed state and use.  The BOF deadline is February 10 and I haven't
> heard of motion on this idea yet.
>
>
>
> Is it useful to consider meeting in person again at IETF 98?  Is it
> sufficient to simply have this mailing list for discussion and coordination
> when necessary?
>
>
>
> Without enthusiasm expressed here, I'm not anticipating having a meeting
> at IETF 98.
>
>
>
> Regards,
>
> Alia
>
>