From nobody Tue Jan 29 14:14:39 2019 Return-Path: X-Original-To: ggie@ietfa.amsl.com Delivered-To: ggie@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1148113107A for ; Tue, 29 Jan 2019 14:14:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=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 (1024-bit key) header.d=thinkingcat.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 m0h5PXdUI2JX for ; Tue, 29 Jan 2019 14:14:30 -0800 (PST) Received: from insect.birch.relay.mailchannels.net (insect.birch.relay.mailchannels.net [23.83.209.93]) (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 BF4B713104F for ; Tue, 29 Jan 2019 14:14:29 -0800 (PST) X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 96C665C4A10; Tue, 29 Jan 2019 22:14:28 +0000 (UTC) Received: from pdx1-sub0-mail-a35.g.dreamhost.com (unknown [100.96.36.160]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 2E31B5C49CB; Tue, 29 Jan 2019 22:14:28 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net Received: from pdx1-sub0-mail-a35.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Tue, 29 Jan 2019 22:14:28 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|leslie@oceanpurl.net X-MailChannels-Auth-Id: dreamhost X-Coil-Arch: 0775ba8a71392d35_1548800068384_1893046435 X-MC-Loop-Signature: 1548800068384:2181628033 X-MC-Ingress-Time: 1548800068384 Received: from pdx1-sub0-mail-a35.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTP id B52FD7ED36; Tue, 29 Jan 2019 14:14:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=RBSV+SYbOCsWsb LvDwb1i/q78fU=; b=EeseftOYjGC69FJqY4vEtI9cMJnNvh+VXXZdPxAAgGi2YL nKHFPF0nxd1Wh2ndlOEkyieaQud/1sOb/94Gef5in/QkUuh2uQLm1jF2b6arxQks x44DnnEocQC4pYIZBd0SslBmwR/17VOZ+fvxPIjpJjjjgWQZO6P6q2gUZR1uc= Received: from [192.168.1.94] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 797C67F645; Tue, 29 Jan 2019 14:14:26 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a35 From: "Leslie Daigle" To: ggie@ietf.org Date: Tue, 29 Jan 2019 17:14:07 -0500 X-Mailer: MailMate (1.12.4r5594) Message-ID: <3568F24B-3740-4E04-92C6-8C71375E7776@thinkingcat.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_FAFFCA86-5E54-4F2B-A7E7-6FF8972EAAD1_=" X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: 0 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtledrjedvgdduheelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfggtgfgsegrkehmreertdejnecuhfhrohhmpedfnfgvshhlihgvucffrghighhlvgdfuceolhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomheqnecukfhppedvudeirdeiiedruddtvddrkeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopegludelvddrudeikedruddrleegngdpihhnvghtpedvudeirdeiiedruddtvddrkeefpdhrvghtuhhrnhdqphgrthhhpedfnfgvshhlihgvucffrghighhlvgdfuceolhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomheqpdhmrghilhhfrhhomheplhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomhdpnhhrtghpthhtoheplhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomhenucevlhhushhtvghrufhiiigvpedt Content-Transfer-Encoding: 7bit Archived-At: Subject: [GGIE] Meeting in Prague, IETF 104 X-BeenThere: ggie@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 22:14:37 -0000 --=_MailMate_FAFFCA86-5E54-4F2B-A7E7-6FF8972EAAD1_= Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable Hi, I don=E2=80=99t think we reached any kind of closure on our discussion, a= fter=20 IETF 103, about the form or function of this group within the IETF. =20 And, it seems like it might be helpful to have a broader audience weigh=20 in on those questions, than just the folks subscribed here and still=20 reading this. So, I propose 2 separate sessions at IETF 104: 1/ We=E2=80=99ll find a slot to talk about options for formalizing this g= roup=20 within the IETF universe (or decide not to). 2/ We=E2=80=99ll have our regular get together to talk through technical=20 topics of interest. Suggestions for technical topics of interest are hereby solicited! Leslie. --=20 ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises ldaigle@thinkingcat.com ------------------------------------------------------------------- --=_MailMate_FAFFCA86-5E54-4F2B-A7E7-6FF8972EAAD1_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi,

I don=E2=80=99t think we reached any kind of closure on o= ur discussion, after IETF 103, about the form or function of this group w= ithin the IETF. And, it seems like it might be helpful to have a broader= audience weigh in on those questions, than just the folks subscribed her= e and still reading this.

So, I propose 2 separate sessions at IETF 104:

1/ We=E2=80=99ll find a slot to talk about options for fo= rmalizing this group within the IETF universe (or decide not to).

2/ We=E2=80=99ll have our regular get together to talk th= rough technical topics of interest.

Suggestions for technical topics of interest are hereby s= olicited!

Leslie.

--

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com

--=_MailMate_FAFFCA86-5E54-4F2B-A7E7-6FF8972EAAD1_=-- From nobody Wed Jan 30 05:02:33 2019 Return-Path: X-Original-To: ggie@ietfa.amsl.com Delivered-To: ggie@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 215B312D4E7 for ; Wed, 30 Jan 2019 05:02:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.04 X-Spam-Level: X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 kxCjrEumkohS for ; Wed, 30 Jan 2019 05:02:28 -0800 (PST) Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 57F381294FA for ; Wed, 30 Jan 2019 05:02:28 -0800 (PST) Received: by mail-yw1-xc32.google.com with SMTP id d190so9577879ywb.5 for ; Wed, 30 Jan 2019 05:02:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TH5I+w526t8i2UQ7s7RI+J/vYQlGsCYfSDm30TaQknc=; b=cXneQKw7KfusAexYFldSemEFBJTjNAxRvWketeRrApLbtBBN3/mzZ/ViqKpoKCWoAN GMKDIW5A8sRYFwbkcpSxt6o9QyXHsOw0SPsXNz73FNR/YIvqCC7T2kWZbprN9dcjiJUC WPG2twFREFt8LL3clcrj0eG+G0TbPEdEp1971pxB+IkwR1vRKeKrfGzCniV42OvT6IXr 4YEnZ1GMWGIuOpz+y06ljL5a/2v+FRdLNr4fKkWFqetk1IuM2tg+J8StfMPXyW6llaEE mkTsfZj9T8jy1EaOQVA9BpjFkevlM9us2SHm2KUWcyV0oPqiyKfRs5HxAu9UqGc7ZDgj WQIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TH5I+w526t8i2UQ7s7RI+J/vYQlGsCYfSDm30TaQknc=; b=FT+P8rrkF3wv1cLvdL4xP1mwJNvqy1ib/OqE5cic+jKdCWkVzRPGxlD1A1LkYdjcPG KgUadpufoAtAOvRkSCjF/Ku/P2DVaCp6K23D1tIQG5lYVBLeTA3tWjsoehTjFjdRLoEG 4F2srIF2J/8w7D4Sai6mX6ssZIsC1VAHDjN4bCsNIlZKpM872tpCMELqruze30n3ncwv vyFy5ax4RiepYVyWEnCX2IYyWkjkqofdXHF0m+dk582hg+tbdOuTdeekgOPVjZbkclXX lw7GZCLWktM1uoA7rJDbAjayjWG8arEMchj2vrws58bbkWmsSAV1PWjZ9vyeIQFDXyCu Xv1w== X-Gm-Message-State: AJcUukdeZk0oQT6q95UG8oGARDegB93Kv1bOLNgR9YmxWubTP0JuGZ6/ srjolqGga4gMORmvqKsVPrnp6PV44Ez9c1BFzAM/Ocf5jW0= X-Google-Smtp-Source: ALg8bN5ghv/q+L+bdTXFkEec7hALGTt2YPGlKbd4yMGFfphmxfKi7J8ng3VJuwI60ha6EnITQa3LR236HZ2idgUTJD0= X-Received: by 2002:a81:6246:: with SMTP id w67mr29025154ywb.60.1548853347129; Wed, 30 Jan 2019 05:02:27 -0800 (PST) MIME-Version: 1.0 References: <3568F24B-3740-4E04-92C6-8C71375E7776@thinkingcat.com> In-Reply-To: <3568F24B-3740-4E04-92C6-8C71375E7776@thinkingcat.com> From: "Ali C. Begen" Date: Wed, 30 Jan 2019 16:02:16 +0300 Message-ID: To: Leslie Daigle Cc: ggie@ietf.org Content-Type: multipart/alternative; boundary="00000000000090b1470580ac855c" Archived-At: Subject: Re: [GGIE] Meeting in Prague, IETF 104 X-BeenThere: ggie@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 13:02:31 -0000 --00000000000090b1470580ac855c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Unfortunately, IETF is in the same week as MPEG in Geneva. There was a topic I wanted to bring up in this group and I will share a write up if I get the time. But at the higher level, I still stand behind what I said earlier in terms of forming a research group for our subject. Still interested in hearing the feedback from the larger group. Just want to mention that the MPEG folks might also provide some input. I asked whether it would be possible to have a GGIE meeting colocated with MPEG before, but that never happened. So maybe at least this group will consider making an input contribution to MPEG that could be presented in the plenary and/or mailing list. This way, some feedback might be received. On Wed, Jan 30, 2019 at 1:14 AM Leslie Daigle wrote: > Hi, > > I don=E2=80=99t think we reached any kind of closure on our discussion, a= fter IETF > 103, about the form or function of this group within the IETF. And, it > seems like it might be helpful to have a broader audience weigh in on tho= se > questions, than just the folks subscribed here and still reading this. > > So, I propose 2 separate sessions at IETF 104: > > 1/ We=E2=80=99ll find a slot to talk about options for formalizing this g= roup > within the IETF universe (or decide not to). > > 2/ We=E2=80=99ll have our regular get together to talk through technical = topics of > interest. > > Suggestions for technical topics of interest are hereby solicited! > > Leslie. > > -- > ------------------------------ > > Leslie Daigle > Principal, ThinkingCat Enterprises > ldaigle@thinkingcat.com > _______________________________________________ > GGIE mailing list > GGIE@ietf.org > https://www.ietf.org/mailman/listinfo/ggie > --00000000000090b1470580ac855c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Unfortunately, IETF is in the same week as MPEG in Geneva.= There was a topic I wanted to bring up in this group and I will share a wr= ite up if I get the time.

But at the higher level, I sti= ll stand behind what I said earlier in terms of forming a research group fo= r our subject. Still interested in hearing the feedback from the larger=C2= =A0group. Just want to mention that the MPEG folks might also provide some = input. I asked whether it would be possible to have a GGIE meeting colocate= d with MPEG before, but that never happened. So maybe at least this group w= ill consider making an input contribution to MPEG that could be presented i= n the plenary and/or mailing list. This way, some feedback might be receive= d.=C2=A0

On Wed, Jan 30, 2019 at 1:14 AM Leslie Daigle <ldaigle@thinkingcat.com> wrote:<= br>

Hi,

I don=E2=80=99t think we reached any kind of closure on our= discussion, after IETF 103, about the form or function of this group withi= n the IETF. And, it seems like it might be helpful to have a broader audie= nce weigh in on those questions, than just the folks subscribed here and st= ill reading this.

So, I propose 2 separate sessions at IETF 104:

1/ We=E2=80=99ll find a slot to talk about options for form= alizing this group within the IETF universe (or decide not to).

2/ We=E2=80=99ll have our regular get together to talk thro= ugh technical topics of interest.

Suggestions for technical topics of interest are hereby sol= icited!

Leslie.

--

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com=

_______________________________________________
GGIE mailing list
GGIE@ietf.org
https://www.ietf.org/mailman/listinfo/ggie
--00000000000090b1470580ac855c-- From nobody Wed Jan 30 09:25:39 2019 Return-Path: X-Original-To: ggie@ietfa.amsl.com Delivered-To: ggie@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5305B1312A6 for ; Wed, 30 Jan 2019 09:25:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thinkingcat.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 xhqIJYs1TS8t for ; Wed, 30 Jan 2019 09:25:35 -0800 (PST) Received: from insect.birch.relay.mailchannels.net (insect.birch.relay.mailchannels.net [23.83.209.93]) (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 0287E13128E for ; Wed, 30 Jan 2019 09:25:34 -0800 (PST) X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3F96F3E55E6; Wed, 30 Jan 2019 17:25:31 +0000 (UTC) Received: from pdx1-sub0-mail-a35.g.dreamhost.com (unknown [100.96.33.121]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id D9ACF3E57EC; Wed, 30 Jan 2019 17:25:30 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net Received: from pdx1-sub0-mail-a35.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Wed, 30 Jan 2019 17:25:31 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|leslie@oceanpurl.net X-MailChannels-Auth-Id: dreamhost X-Decisive-White: 5d2090a0151ea246_1548869131070_3929378987 X-MC-Loop-Signature: 1548869131070:2233409930 X-MC-Ingress-Time: 1548869131070 Received: from pdx1-sub0-mail-a35.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTP id 7695A7F240; Wed, 30 Jan 2019 09:25:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=h PxgAU2yt5PFCqI7A7h1G2p7tkM=; b=cyQlzQF6UoHN9X6FMMtKRiOzbVc+cEL8V MZZmmhfVuM97LxttDE9qbbwfGEI27/9PZs1ZNjYLTzSIzGkCTHu36BFvff8XNa6q /f8I12E/vCopZ/lzyztN5ChGwJIX5Rh7MgNkAg3Ta8qsEcOJt9V6ZDCVNEFA//yt +y/xeuj16k= Received: from [169.254.135.137] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTPSA id E9C6C7F5D4; Wed, 30 Jan 2019 09:25:28 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a35 From: "Leslie Daigle" To: "Ali C. Begen" Cc: ggie@ietf.org Date: Wed, 30 Jan 2019 12:25:09 -0500 X-Mailer: MailMate (1.12.4r5594) Message-ID: In-Reply-To: References: <3568F24B-3740-4E04-92C6-8C71375E7776@thinkingcat.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_F1E94B5D-339B-4564-8F4A-4FC424C6D927_=" Embedded-HTML: [{"HTML":[1429, 2691], "plain":[823, 1765], "uuid":"3CD7027C-5FA3-4ADC-A2EA-91792590FADA"}] X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: -100 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtledrjeeggddutdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffoffkjghfgggtgfesrgekmherredtjeenucfhrhhomhepfdfnvghslhhivgcuffgrihhglhgvfdcuoehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmqeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppedvudeirdeiiedruddtvddrkeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopegludeiledrvdehgedrudefhedrudefjegnpdhinhgvthepvdduiedrieeirddutddvrdekfedprhgvthhurhhnqdhprghthhepfdfnvghslhhivgcuffgrihhglhgvfdcuoehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmqedpmhgrihhlfhhrohhmpehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmpdhnrhgtphhtthhopehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [GGIE] Meeting in Prague, IETF 104 X-BeenThere: ggie@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 17:25:38 -0000 --=_MailMate_F1E94B5D-339B-4564-8F4A-4FC424C6D927_= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi Ali, Well, we=E2=80=99ll miss you in Prague. Would love to have the write up = of=20 your topic, if you have time. WRT the larger picture =E2=80=94 right now, I=E2=80=99m focused on corral= ling video=20 interests at and within the IETF. What are the topics people are=20 working at the IETF, and how can we best form ourselves to continue to=20 have those conversations in an ongoing fashion. There is, indeed, a separate conversation to be had about coordination=20 in the industry, and maybe an eventual meeting co-located with MPEG. =20 But, that=E2=80=99s a separate conversation. Leslie. --=20 ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises ldaigle@thinkingcat.com ------------------------------------------------------------------- On 30 Jan 2019, at 8:02, Ali C. Begen wrote: > Unfortunately, IETF is in the same week as MPEG in Geneva. There was a > topic I wanted to bring up in this group and I will share a write up=20 > if I > get the time. > > But at the higher level, I still stand behind what I said earlier in=20 > terms > of forming a research group for our subject. Still interested in=20 > hearing > the feedback from the larger group. Just want to mention that the MPEG > folks might also provide some input. I asked whether it would be=20 > possible > to have a GGIE meeting colocated with MPEG before, but that never=20 > happened. > So maybe at least this group will consider making an input=20 > contribution to > MPEG that could be presented in the plenary and/or mailing list. This=20 > way, > some feedback might be received. > > On Wed, Jan 30, 2019 at 1:14 AM Leslie Daigle=20 > > wrote: > >> Hi, >> >> I don=E2=80=99t think we reached any kind of closure on our discussion= ,=20 >> after IETF >> 103, about the form or function of this group within the IETF. And,=20 >> it >> seems like it might be helpful to have a broader audience weigh in on=20 >> those >> questions, than just the folks subscribed here and still reading=20 >> this. >> >> So, I propose 2 separate sessions at IETF 104: >> >> 1/ We=E2=80=99ll find a slot to talk about options for formalizing thi= s=20 >> group >> within the IETF universe (or decide not to). >> >> 2/ We=E2=80=99ll have our regular get together to talk through technic= al=20 >> topics of >> interest. >> >> Suggestions for technical topics of interest are hereby solicited! >> >> Leslie. >> >> -- >> ------------------------------ >> >> Leslie Daigle >> Principal, ThinkingCat Enterprises >> ldaigle@thinkingcat.com >> _______________________________________________ >> GGIE mailing list >> GGIE@ietf.org >> https://www.ietf.org/mailman/listinfo/ggie >> > _______________________________________________ > GGIE mailing list > GGIE@ietf.org > https://www.ietf.org/mailman/listinfo/ggie --=_MailMate_F1E94B5D-339B-4564-8F4A-4FC424C6D927_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi Ali,

Well, we=E2=80=99ll miss you in Prague. Would love to ha= ve the write up of your topic, if you have time.

WRT the larger picture =E2=80=94 right now, I=E2=80=99m f= ocused on corralling video interests at and within the IETF. What are = the topics people are working at the IETF, and how can we best form ourse= lves to continue to have those conversations in an ongoing fashion.

There is, indeed, a separate conversation to be had about= coordination in the industry, and maybe an eventual meeting co-located w= ith MPEG. But, that=E2=80=99s a separate conversation.

Leslie.

--

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com

On 30 Jan 2019, at 8:02, Ali C. Begen wrote:

Unfortunately, IETF is in the same week as MPEG in Geneva.= There was a topic I wanted to bring up in this group and I will share a = write up if I get the time.

But at the higher level, I= still stand behind what I said earlier in terms of forming a research gr= oup for our subject. Still interested in hearing the feedback from the la= rger=C2=A0group. Just want to mention that the MPEG folks might also prov= ide some input. I asked whether it would be possible to have a GGIE meeti= ng colocated with MPEG before, but that never happened. So maybe at least= this group will consider making an input contribution to MPEG that could= be presented in the plenary and/or mailing list. This way, some feedback= might be received.=C2=A0

On Wed, Jan 30, 2019 at 1:14 AM Leslie D= aigle <ldaigle@thinkingcat.= com> wrote:

Hi,

I don=E2=80=99t think we reached any kind of closure on o= ur discussion, after IETF 103, about the form or function of this group w= ithin the IETF. And, it seems like it might be helpful to have a broader= audience weigh in on those questions, than just the folks subscribed her= e and still reading this.

So, I propose 2 separate sessions at IETF 104:

1/ We=E2=80=99ll find a slot to talk about options for fo= rmalizing this group within the IETF universe (or decide not to).

2/ We=E2=80=99ll have our regular get together to talk th= rough technical topics of interest.

Suggestions for technical topics of interest are hereby s= olicited!

Leslie.

--

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com=

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

______________________= _________________________
GGIE mailing list
GGIE@ietf.org
https://www.ietf.org/mailman/listinfo/ggie

--=_MailMate_F1E94B5D-339B-4564-8F4A-4FC424C6D927_=--