[T2TRG] Towards edge to edge communication
Anant Shah <anant.shah@verizondigitalmedia.com> Tue, 20 August 2019 03:32 UTC
Return-Path: <anant.shah@verizondigitalmedia.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBE86120288 for <t2trg@ietfa.amsl.com>; Mon, 19 Aug 2019 20:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.37
X-Spam-Level:
X-Spam-Status: No, score=-0.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizondigitalmedia.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 cSnKkb4nvo6d for <t2trg@ietfa.amsl.com>; Mon, 19 Aug 2019 20:32:38 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 1AA171200FB for <t2trg@irtf.org>; Mon, 19 Aug 2019 20:32:38 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id s19so2952032lfb.9 for <t2trg@irtf.org>; Mon, 19 Aug 2019 20:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizondigitalmedia.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=Q8OebfurZNXUn0oS8ebXEp8JGZ6mFzgmRQrQRpylH/s=; b=Lz6T/iAlt9avJjH+fHBV50tyBitGFGDl8mnHKhbjfdpXdRFCV53tItQu9hbqj2bQnL OZmXpOTdayi7k3+vE0hmB2EJbpunrapyHY66eCoOOjG0DfVNd4RDsVGNoWAhHCXTKYEw 4auMnNN2fdQacnf+PMM2O5LqcoPiEJbleY4cE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Q8OebfurZNXUn0oS8ebXEp8JGZ6mFzgmRQrQRpylH/s=; b=PFJmLjCHMJp0F6BRh8nqxusAgy4/l456QQ4jdDhn2ok9t28zaB78h5u0N9NZaad10C 3FqBEywMVnDU4NFCAHLvLgpMHu2DqrxECW2bP2s+uw/Dm976Auwy0D9lHqRrMKL3pk/3 3T4wkvoDoqLoQFtKkmhY5wvrV0NbDVyoQgEIzPcJ1aOhAjFEO2u61VYatDb+/BX3brmm n70Z5iWhGNJ18fjoBHiJ8ytDh/6V0cWVidpdPzfvYJUoTBiYA22nO2cupZaoffzMKqAy a5sRPYhDlUwl/W5vyEU22ZnUZoPaE43mYzw7eMYAp120XReibc7N+Uk1+UmEbGDXT1ML Aj+w==
X-Gm-Message-State: APjAAAWtfQl7wi6TWY+L5z4mQr/Y0+I6gIL44QXoNIiHm8DnwfMPUnaG cwdi7GZpXYNPIwodo3hCrthF9gH/thlSWbXnBNtFPANj
X-Google-Smtp-Source: APXvYqzmiIprZApl/QuvBe2bHETziPaIyhakmK/QcBxui/O5EzzaN5tL8oIGgVHdJi1g5wkUA+alWht2JNfxN+QIkXE=
X-Received: by 2002:a05:6512:244:: with SMTP id b4mr14914599lfo.114.1566271955679; Mon, 19 Aug 2019 20:32:35 -0700 (PDT)
MIME-Version: 1.0
From: Anant Shah <anant.shah@verizondigitalmedia.com>
Date: Mon, 19 Aug 2019 20:32:24 -0700
Message-ID: <CA+XbCHU+_R_iCnzXf0ShGCBaO1xBhpekF9K2e+FjSjiTKbBSdg@mail.gmail.com>
To: t2trg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000008a5d0c0590841b50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/eLLNFByrn-kog3ktHoBIy9-VRSM>
Subject: [T2TRG] Towards edge to edge communication
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2019 03:32:40 -0000
Hi all, I am wondering if there are any research drafts that focus on requirements, specifications, and BCPs for scenarios where multiple edges are used by a device. For example, a high latency-sensitive task is performed on a 5G MEC vs something that can work with 10s of ms of latency at a CDN vs cloud. As we've seen the caching world evolve into a multi-cdn architecture and usually a webpage can fetch content from different CDNs, I assume compute at the edge will evolve the same way. Please let me know your thoughts or related drafts I should read, and if this is not the right RG for this topic, I apologize in advance. Thanks! -- *Anant Shah, PhD* | Research Scientist Verizon CDN [image: vz-sig-verizon] <https://www.verizondigitalmedia.com>
- [T2TRG] Towards edge to edge communication Anant Shah