Re: [CDNi] [E] Re: Is there a working group meeting planned at IETF104?

sanjay.mishra@verizon.com Fri, 08 February 2019 03:28 UTC

Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD69128B01 for <cdni@ietfa.amsl.com>; Thu, 7 Feb 2019 19:28:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com header.b=IW+jeUka; dkim=pass (1024-bit key) header.d=verizon.com header.b=ObTLUO5r; dkim=pass (1024-bit key) header.d=verizon.com header.b=fGyiVEEZ
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 6AYWH1_PSL96 for <cdni@ietfa.amsl.com>; Thu, 7 Feb 2019 19:28:51 -0800 (PST)
Received: from omzsmtpe03.verizonbusiness.com (omzsmtpe03.verizonbusiness.com [199.249.25.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98EF4130F1D for <cdni@ietf.org>; Thu, 7 Feb 2019 19:28:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1549596531; x=1581132531; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZQf7gbJQSPDHpiNGOzq6Yag7a58Oa8/vorRrirNoV00=; b=IW+jeUkatqOKM/OpKSsie+yLGB/euFMAGBeoFPSrGs0lOnssDSYU1Slq 5ITSpHa7b4euGNlZT+8tZNTDE88+WY2om34Jkui37f6xzkKo5GfAIa1pU IwDdnUvUtc6JjUt0tkz1UXIRHQdQdINaKZ24NxuhZMo6iu7p45qc1Q1b4 w=;
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by omzsmtpe03.verizonbusiness.com with ESMTP; 08 Feb 2019 03:28:49 +0000
Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO atlantis.verizonwireless.com) ([10.255.192.101]) by fldsmtpi02.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Feb 2019 03:28:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1549596498; x=1581132498; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZQf7gbJQSPDHpiNGOzq6Yag7a58Oa8/vorRrirNoV00=; b=ObTLUO5rxpkJSAH1nWo3H1rG0LxqD4Iw/K7O03Syfa7BhcQWuufoozEN f5kZkH1UTRBPHz89OfzznInGk1aHr5vwhIKuts6E1YB5JfT/F6YdGlniA W+njstIhTWIUD9qJSzO9FEvaxoFMmSelQ27TQgdHktr3zNNsRyeyGgP34 4=;
Received: from surveyor.tdc.vzwcorp.com (HELO eris.verizonwireless.com) ([10.254.88.83]) by atlantis.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Feb 2019 22:28:18 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1549596498; x=1581132498; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=ZQf7gbJQSPDHpiNGOzq6Yag7a58Oa8/vorRrirNoV00=; b=fGyiVEEZAVDH8989QX7D93iV6GEyPQV3CoS4NFsvSL1TxsXlgWpN5NYj xar2Jij4N107p3W/4gngJ6nwAQu9i9RcQqpU1i+BezXHUtFMdW8t/ZwGh RFQQCU53j+6n+TloI9LlpbhX21U08dIvXUxXH5Sz5LbDEC0end3YR2oTW A=;
From: sanjay.mishra@verizon.com
X-Host: surveyor.tdc.vzwcorp.com
Received: from ohtwi1exh002.uswin.ad.vzwcorp.com ([10.144.218.44]) by eris.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 08 Feb 2019 03:28:18 +0000
Received: from tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) by OHTWI1EXH002.uswin.ad.vzwcorp.com (10.144.218.44) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 7 Feb 2019 22:28:18 -0500
Received: from tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) by tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 7 Feb 2019 22:28:17 -0500
Received: from tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) by tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) with mapi id 15.00.1395.000; Thu, 7 Feb 2019 22:28:17 -0500
To: Phil Sorber <sorber@apache.org>
CC: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [E] Re: [CDNi] Is there a working group meeting planned at IETF104?
Thread-Index: AdS/Kusf+UnDBOGTQ/aFAQ26TJ3FvAALMp2AAAFgN9A=
Date: Fri, 08 Feb 2019 03:28:17 +0000
Message-ID: <4787030ede3642748fca229aab94a244@tbwexch02apd.uswin.ad.vzwcorp.com>
References: <dc47846f926a428a9eea81dbb7c85d27@tbwexch02apd.uswin.ad.vzwcorp.com> <CABF6JR3jH-QXQaG39r-RFxMNN-V8ttRtSJ+WK00n6WAZEP-QSQ@mail.gmail.com>
In-Reply-To: <CABF6JR3jH-QXQaG39r-RFxMNN-V8ttRtSJ+WK00n6WAZEP-QSQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.144.60.250]
Content-Type: multipart/alternative; boundary="_000_4787030ede3642748fca229aab94a244tbwexch02apduswinadvzwc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/BZy_eGXit-e5J4VZGuHOqBgvx9o>
Subject: Re: [CDNi] [E] Re: Is there a working group meeting planned at IETF104?
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2019 03:28:54 -0000

I can volunteer, if there is broader interest in the mailing list seeking for the group to meet.  Speaking personally, there is no pressing matter for which I see a need for meeting in Prague, though, it would be good to plan to meet in Montreal. From my perspective (and co-authors), there are three working group drafts (see below) where it would be good to get some feedback on the mailing list.


1.       https://datatracker.ietf.org/doc/draft-ietf-cdni-interfaces-https-delegation/

2.       https://datatracker.ietf.org/doc/draft-ietf-cdni-request-routing-extensions/

3.       https://datatracker.ietf.org/doc/draft-ietf-cdni-triggers-extensions/

-Sanjay


From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of Phil Sorber
Sent: Thursday, February 07, 2019 4:41 PM
To: sanjay.mishra=40verizon.com@dmarc.ietf.org
Cc: cdni@ietf.org
Subject: [E] Re: [CDNi] Is there a working group meeting planned at IETF104?

I am not able to make this meeting in person. AFAIK Kevin is also unable to attend. If the group feels having an in person meeting is important then I would like to ask for a volunteer to proxy the meeting. Kevin or I will be available remotely to run things, but someone needs to be there to do blue sheets and handle in any room issues, etc.

Thanks.

On Thu, Feb 7, 2019 at 2:24 PM <sanjay.mishra=40verizon.com@dmarc.ietf.org<mailto:40verizon.com@dmarc.ietf.org>> wrote:
I am wondering if the CDNI chairs plan to schedule a working group meeting at IETF 104. Last day to request the meeting is Friday, Feb 8, 2019.


Thanks
Sanjay
_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_cdni&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=3C6rU4tKDRlmIXG_UlAg-ETR7qq1nlpomkcOK4QeOwQ&s=NLJg0UbBn6P53-NGrtGHpDcZpXSu3cHHcS9ZsYRZOp4&e=>