[dispatch] Fwd: [GGIE] DRAFT bof proposal for IETF 98 in Chicago
"Leslie Daigle" <ldaigle@thinkingcat.com> Wed, 08 February 2017 21:46 UTC
Return-Path: <ldaigle@thinkingcat.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36AD4129408 for <dispatch@ietfa.amsl.com>; Wed, 8 Feb 2017 13:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.176
X-Spam-Level:
X-Spam-Status: No, score=-3.176 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" 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 DRCvo_pD8bz7 for <dispatch@ietfa.amsl.com>; Wed, 8 Feb 2017 13:46:19 -0800 (PST)
Received: from homiemail-a109.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D213C1293FB for <dispatch@ietf.org>; Wed, 8 Feb 2017 13:46:19 -0800 (PST)
Received: from homiemail-a109.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTP id 8C53D20047601; Wed, 8 Feb 2017 13:46:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:references:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=B/RUUhOn5gpi3W z9q17xSd0ag3M=; b=l9qgOXpj/zFgLHSupZMszZZRNQGCMGLoO+2DGGNDI5Lb3t 3yjjblrRNSGCEjE5CUbD7dyBU08IgL5WXq46YBhCuS/eselwpLKhE6kWnjn0GkUV FT+VyAn7EMiH9sL7ruCMzY1gK/cUJEoT2GA4VNyxerhLeWjdHta99OzsGKuLc=
Received: from [192.168.1.5] (pool-71-171-98-61.clppva.fios.verizon.net [71.171.98.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTPSA id F035520047607; Wed, 8 Feb 2017 13:46:18 -0800 (PST)
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: dispatch@ietf.org
Date: Wed, 08 Feb 2017 16:46:17 -0500
Message-ID: <7CF5BF4F-7410-4FBE-BE36-8577E4F90C17@thinkingcat.com>
References: <3F95E981-D341-4FAB-8C25-4A018A9761A7@thinkingcat.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_8C7BEC80-37B0-401D-8054-687C36B02084_="
X-Mailer: MailMate (1.9.6r5319)
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/dCWU3piAID-PbdlFYOIEwp2BoCU>
Subject: [dispatch] Fwd: [GGIE] DRAFT bof proposal for IETF 98 in Chicago
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 21:46:22 -0000
Hi, Following up the discussion of GGIE at the last 2 DISPATCH meetings, we are going to propose a BoF for IETF 98. Please see below for 1/ information about the GGIE mailing list [*] where it’s being discussed, and 2/ the draft BoF proposal. As noted in the message, we are happy to have suggestions on how to improve the proposal/move the work forward. Thanks, Leslie. [*] Subscription and other info here: https://www.ietf.org/mailman/listinfo/ggie/ -- ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises LLC ldaigle@thinkingcat.com ------------------------------------------------------------------- Forwarded message: > From: Leslie Daigle <ldaigle@thinkingcat.com> > To: ggie@ietf.org > Cc: Deen, Glenn <glenn.deen@nbcuni.com> > Subject: DRAFT bof proposal for IETF 98 in Chicago > Date: Wed, 08 Feb 2017 16:32:16 -0500 > > Hi, > > Please find below a proposal for a GGIE BoF (WG-forming) at IETF 98 in > Chicago. We will be submitting the proposal by the deadline this > Friday, but would be happy to have suggestions to improve the proposal > before then. > > One of the things we’ve beed advised is that > GGIE-proponents-other-than-Glenn-and-Leslie are pretty invisible to > the IESG. If there doesn’t seem to be other interest, there won’t > be much justification for a BoF. > > Now is the time, and here is the place, to voice your support for > furthering this discussion! > > Thanks, > Leslie. > > —8<——8<——8<—— > > Name: Glass to Glass Internet Ecosystem (GGIE) > > Description: > > Video is without rival the top use of Internet bandwidth, and its ever > growing demand for more bandwidth easily out paces the new capacity > being added both globally and regionally with no let up in sight. > Users are frustrated by quality, buffering, and stuttering problems. > Video providers and access networks are investing heavily to keep up > with demand. Significant work has be done at the application layer > producing more efficient codecs and innovative adaptive bitrate > transports like MPEG-DASH. These access investments and application > layer work have helped but they alone have not been enough. > > This BoF will introduce the Glass to Glass Internet Ecosystem (GGIE) > which focuses on network level innovations to compliment the efforts > at the application layer and access networks. The proposed GGIE work > includes enabling adaptive bitrate transports like MPEG-DASH to use > IPv6 as their video segment addressing scheme which in turn permits > use of advanced IPv6 network features such as Segment Routing. A GGIE > goal is to enabling video and network routing and management to work > more cooperatively and efficiently to transport video, and to do so in > a backward compatible ways to permit exiting devices and players to > take advantage of the improved network efficiencies. > > > > Agenda > Agenda bash, scribe, minute taker [10min] > > Context setting [15min] > Highlights of the Internet Video Scaling Problem > Specific aims of the GGIE work > Relationship to other IETF activity > Relationship to work in other fora > > Overview of existing GGIE work — Network level proposals, > demo [50min] > - IPv6 Prefix addressing of MPEG-DASH packaged video > - Content identifier to content address mapping using > MARS > - GGIE prototype demo > > Where from here? [45min] > Known open questions > Potential for IETF work — is there interest to pursue? > If applicable: Discussion of draft charter for WG > > > Demo of GGIE prototype > Q&A & Discussion > > Status: WG Forming > Responsible AD: Ben Campbell > BoF proponents: Glenn Deen / Leslie Daigle > BoF chairs: TBD > Number of people expected to attend: TBD > Length of session (1, 1.5, 2, or 2.5 hours): 2 hours > Conflicts to avoid (whole Areas and/or WGs): DISPATCH WG and TBD > Links to the mailing list, draft charter if any, relevant > Internet-Drafts, etc. > Mailing List: https://www.ietf.org/mailman/listinfo/ggie > Draft charter: see below > Relevant drafts: > draft-deen-daigle-ggie-02 : Glass to Glass Internet > Ecosystem Introduction > draft-rose-deen-ggie-use-cases-00 : GGIE Internet Video Use > Cases > draft-daigle-deen-ggie-uri-snaptr-00 : Glass to Glass Internet > Ecosystem URI and S-NAPTR Use > draft-deen-naik-ggie-men-mpeg-dash-00 : Using Media Encoding > Networks to address MPEG-DASH video (This is expired, but we can > easily re-spin, or wait for WG input). > > > > > Glass to Glass Internet Ecosystem (GGIE) -- Draft Charter > > Due to its size and sensitivity to network conditions, the transport > of video over the Internet has highlighted a significant scalability > problem for the Internet. Addressing this scalability problem > requires better integration between application transport and > networking technologies and leveraging IPv6. The GGIE working group > will define a set of fundamental building blocks bridging video > application use of the network and core network services of > addressing, routing, and naming. Through standardization, of such > fundamentals, a common base platform for new interoperable innovation > on video transport efficiency and scalability will be enabled. > > The scalability problem is driven by both professional and user > generated content, fortunately both types of content use the same > transport technologies which permits the working group’s output to > apply equally to them. Likewise, in addition to the use the network to > transport video for viewing, the network is extensively used in video > creation workflows of capture and editing, and distribution workflows > of encoding, packaging, and distribution to edge caches for playback. > The working group will address both viewing and creation/distribution > workflows. > > To that end, the GGIE working group will define missing pieces of > Internet technology standards, as well as provide pointers to use of > existing standards. > > Specifically, the GGIE working group will: > > + complete an overview document outlining the GGIE problem statement > and general solution approach > + develop a set of use cases representative of GGIE problem scope > + develop a standardized URI for referring to specific media objects > within a domain > + develop a standardized means for mapping IPv6 addresses to video > data > + develop a media address resolution service protocol (MARS) to map > URIs and addresses for video > + provide a mechanism for discovering media address resolution > services > + document integration methods with lower level fundamental network > services (eg. routing) > + develop media encoding network (MEN) definitions for video packaging > such as MPEG-DASH > + illustrate how these technologies address the use cases already > developed for GGIE > > Out of scope are: video technologies including codecs, digital rights > management, and DRM enforcement technologies. > > > > -- > > ------------------------------------------------------------------- > Leslie Daigle > Principal, ThinkingCat Enterprises LLC > ldaigle@thinkingcat.com > -------------------------------------------------------------------
- [dispatch] Fwd: [GGIE] DRAFT bof proposal for IET… Leslie Daigle