IETF Logo Mail Archive

Re: Asking for a slot in IETF101

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 02 March 2018 19:58 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96307126C25 for <rtgwg@ietfa.amsl.com>; Fri, 2 Mar 2018 11:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 YNq3Fv5RjsGQ for <rtgwg@ietfa.amsl.com>; Fri, 2 Mar 2018 11:58:57 -0800 (PST)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 94C49124217 for <rtgwg@ietf.org>; Fri, 2 Mar 2018 11:58:57 -0800 (PST)
Received: by mail-yb0-x22c.google.com with SMTP id v8-v6so3764000ybk.6 for <rtgwg@ietf.org>; Fri, 02 Mar 2018 11:58:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version; bh=hvyJ9xFpKMLmta4735i6vH+S6e0uF+VnQo4StR3CbLo=; b=aZ1Gey4aEh8F2Xc+P52fWJUMwOfBSCaaYvFvqKp/qUA2pxqD5H13Ic6np+4lnV9FNb n9KmficAxt6E+o3j0sIHmQORDxnpZSgsS/V/38dDRtiLOK8xFQzbca/VRY2y2AJcTikN rFpqtJRA57GvsstgHxoc6TMLT6WPOdc3cTsgwDpHoZ5CvHIpSIaA0XlA7w6M/56S4dzZ iakFg2Cf8l27QqQZEY5SWHo8RRK1zPQ37UiUeZHFZSmyJWYttNRPkh1MGqaR2+OTeBoj j0voK72/oBEA0fhkcz1lXXT9gSp/y31U4Zvra/X01Z+X/O+DD3Mwba8V4rgKYqBoNvw2 h9MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version; bh=hvyJ9xFpKMLmta4735i6vH+S6e0uF+VnQo4StR3CbLo=; b=jhkabF4iJEx40Kj3JGPDmH/kHOKfIElIPbSFGZu10n8b+DcpOULmx+AvJS3oywvnc6 VMdtWOduveMyJ0TFbEDHdXFELqaH1BXl9WpOSS0Tvgx6lnGM/+u/IcuXSWDLf3ZHoCXH KZpnScO8qM87MeBMU8wZ2Uu0SeZEPj/GZexo4zU3cMwb8wQJ1Z49Yi9RFcCbVkVNeG0i uN8HGchiltoWTOR0ZAXSwn3cmLyJRK0AEyS82BzMiqXOeumoZtg4wr98Yh0kiGVtc3iw oYyuvSxDkrqdisybAg6nj9Wi5ouXXaaDBExtnAOqoEzjAZZgwArjMovhxSTqVh8uUAup hbWw==
X-Gm-Message-State: APf1xPANXT4K5htuhnwrY+UF3giNQbr5YYisrGT/9MHOaWe6O7Uf6i4L 5Uqir1zpEvfduueke+K76hA=
X-Google-Smtp-Source: AG47ELulNegs2Lx2uUA2wRoYMM3aNg0bJfK1HqWT/+BeL5uQLcSPp7WTyaHnr9XBjg1LQivyDgIItg==
X-Received: by 2002:a25:1f86:: with SMTP id f128-v6mr4325092ybf.255.1520020736774; Fri, 02 Mar 2018 11:58:56 -0800 (PST)
Received: from [135.227.239.108] ([66.201.62.254]) by smtp.gmail.com with ESMTPSA id o133sm1405866ywd.102.2018.03.02.11.58.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 11:58:56 -0800 (PST)
User-Agent: Microsoft-MacOutlook/10.a.0.180210
Date: Fri, 02 Mar 2018 11:58:53 -0800
Subject: Re: Asking for a slot in IETF101
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Haoyu song <haoyu.song@huawei.com>, "Acee Lindem (acee)" <acee@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Message-ID: <9D5AF138-B595-4C4C-8898-4260A89A3B2A@gmail.com>
Thread-Topic: Asking for a slot in IETF101
References: <78A2745BE9B57D4F9D27F86655EB87F937491B20@SJCEML521-MBB.china.huawei.com> <26128175-7BF7-42E3-B0C2-AC3D124CE889@cisco.com> <78A2745BE9B57D4F9D27F86655EB87F937491B76@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <78A2745BE9B57D4F9D27F86655EB87F937491B76@SJCEML521-MBB.china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3602836735_1915488414"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/GxGkxZvz_JLHa5eccgVlQYczrzU>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 19:59:00 -0000

/RTGWG chair hat off

 

I find this work rather useful and support its presentation to routing folks (in combination with presentation in OPS)

 

Cheers,

Jeff

From: rtgwg <rtgwg-bounces@ietf.org> on behalf of Haoyu song <haoyu.song@huawei.com>
Date: Friday, March 2, 2018 at 11:56
To: "Acee Lindem (acee)" <acee@cisco.com>, RTGWG <rtgwg@ietf.org>
Subject: RE: Asking for a slot in IETF101

 

Hi Acee,

 

We also apply a slot in OPSAWG. Since the audience may be different for the two groups, we’d like to present in both. Thanks!

 

Haoyu

 

From: Acee Lindem (acee) [mailto:acee@cisco.com] 
Sent: Friday, March 02, 2018 11:54 AM
To: Haoyu song <haoyu.song@huawei.com>; rtgwg@ietf.org
Subject: Re: Asking for a slot in IETF101

 

Why aren’t you presenting in an OPS area group?

 

Acee

 

From: rtgwg <rtgwg-bounces@ietf.org> on behalf of Haoyu song <haoyu.song@huawei.com>
Date: Friday, March 2, 2018 at 2:50 PM
To: Routing WG <rtgwg@ietf.org>
Subject: Asking for a slot in IETF101

 

Dear RTGWG Chairs, 

I’m writing to ask for a presentation slot for the draft of “Toward a Network Telemetry Framework” (https://datatracker.ietf.org/doc/draft-song-ntf/)

Thank you very much for the consideration!

Best regards,

Haoyu Song

 

_______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email