IETF Logo Mail Archive

Re: [Moq] Charter adjustment

Ian Swett <ianswett@google.com> Fri, 22 July 2022 16:52 UTC

Return-Path: <ianswett@google.com>
X-Original-To: moq@ietfa.amsl.com
Delivered-To: moq@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE18C14CF18 for <moq@ietfa.amsl.com>; Fri, 22 Jul 2022 09:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.607
X-Spam-Level:
X-Spam-Status: No, score=-22.607 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etv24_cdhxpt for <moq@ietfa.amsl.com>; Fri, 22 Jul 2022 09:52:39 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926A4C14F75F for <moq@ietf.org>; Fri, 22 Jul 2022 09:52:39 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id m17so7004445wrw.7 for <moq@ietf.org>; Fri, 22 Jul 2022 09:52:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MQJ6mAQNY90hHb7WiDjEYy/Cx2kcrkM3QYp52NXoCQ0=; b=KzoBJKdvPvziSn3uV+frqIM1eZhypMPIdVrc2//rOC5LO9KpazrrHt4d/e8vWMGpAq ES9mxL8B0nS6pmKsUSw+uGXsdEuDPCtfTG6QWCB7hnnjsAAcZBaJT1ghz+lB9chrlVC1 Q8R2wyI3X9GLanRdnXUWYL8reRzFiobEmVq0i/L6rzt8mPJXknhK3hzBeSLFeE25BO6V KaP0uudLKe9hLvfnyiWV0BBA0GTGSAAt0LERI77BMbp1de3RtEYNNqRWYf8bo9P/w74Q xr72S0gsd0d2FQQa8WAZcCXs22BN7GGXJ6khOxhOsXnWkSeeQu+/Ae1UhdjcVrxWooRt PVTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MQJ6mAQNY90hHb7WiDjEYy/Cx2kcrkM3QYp52NXoCQ0=; b=kVVuIAufp/nMNTs107F/hlKxTnTVHeVqEEglAFLHSwckgyMXpsimOYucGD7M8C/Xrt 0ed1m0NBGscisVkqebH+zsfCUUKERKFhsRYwObYu0GYIDfoQej8dSR3Kh8ZuzUiR4diw EV/C4BRU96a/xel+Y1QF4urUeVlG0TEPHPBwQvxXrOhuZSMkdOFIGE7YonFjPIznBfbm nAnnHJbRKF5vpkm04aYo8Ag5Hiwizxws+o7sdd4+qTYbqTpd+vwRR52jb3ghS7MyR7FG maYwqkgpL/eKXQoIo4k5+TXlab6Z5nETLbxCjVNoLJTcbBNAMLl0UvFY/3L20kmTVHyP 6YwA==
X-Gm-Message-State: AJIora8YKFzKWBZb6kUh4y88fsGtxsmx4Y9H+UDMF75plr+7mZapkYYA v5Ypcn3uVuQdRfQgIBbZy9dN8TfIZ3mnsTSiD5Ikrw==
X-Google-Smtp-Source: AGRyM1uP7bIVGKChgVJxmvK9vjYjzHTZaFH4UQFb7OPoK2cey3FDeTPip4zW6sTsCspBj2ssk15UZHOm7WPg6E1r1NE=
X-Received: by 2002:adf:d1c4:0:b0:21d:76e1:bf2c with SMTP id b4-20020adfd1c4000000b0021d76e1bf2cmr559868wrd.576.1658508757629; Fri, 22 Jul 2022 09:52:37 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMAr=dMSg9efcYBd5QZquvDhYcQi_gibyttxjqcxvWZKMw@mail.gmail.com> <511BF9AE-C84B-4AC2-9430-B268979078B4@networked.media> <CAMRcRGRGR3bXroZch4DAgeN65GodUp2J4=44pvB-6_ieGLKDTg@mail.gmail.com> <BN7PR11MB275378CDC1463041BB4E71CEB4919@BN7PR11MB2753.namprd11.prod.outlook.com> <CALGR9oaFWKvjaHg_bjoTFFMavpwAWLLe2FEGyLzNcYFqxWHswg@mail.gmail.com> <CAMRcRGTs8UPLHzw9PiJB2rOh8MwE402LvBi+xRXbnVdrx2sSwA@mail.gmail.com> <CAMRcRGRdTk_kXnd=s5ZB0XuHTRtTH0xPir3hJkBprAV70dtsTw@mail.gmail.com> <CAKcm_gMbWtbJe=kcbCXxAphLpiaiGHQPcm=00Tqoioh2SC6VZA@mail.gmail.com> <CAOW+2dvwEr3uZ0BKJeOO9eYHJhYZsZ4w_hWVckG5n4F6bSJ_2g@mail.gmail.com> <b2312817-f859-53f8-0fba-307c71ac05e7@huitema.net> <CAOW+2ds02i_MUJoBP0L7-3R5GfCtgmXhTpES6Da_LE-c_+ZZUw@mail.gmail.com> <d9d0ca62-e3e6-15fc-9f5a-fd29640aad46@huitema.net> <YT2PR01MB59336F54BD433E901637D22EB2909@YT2PR01MB5933.CANPRD01.PROD.OUTLOOK.COM> <CA+9kkMAkV51Sc9QNqSe8oWVOJ_br_Z0T1sZwuy2XwtSuqTrAXw@mail.gmail.com> <CALGR9oYYx3f8XpwhRghN4z=UfrSDU4HJdVpz9DjUFjMD2NkAAw@mail.gmail.com>
In-Reply-To: <CALGR9oYYx3f8XpwhRghN4z=UfrSDU4HJdVpz9DjUFjMD2NkAAw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 22 Jul 2022 12:52:25 -0400
Message-ID: <CAKcm_gNDUzsJ9p2-raiVYoEDnbOfb2D0mFgwkdaZ0t37X6ZGcw@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005b8dc505e467a9c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/PhX94haV9MAHggs2B8FMKmAfuS4>
Subject: Re: [Moq] Charter adjustment
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media over QUIC <moq.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/moq>, <mailto:moq-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq/>
List-Post: <mailto:moq@ietf.org>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/moq>, <mailto:moq-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2022 16:52:40 -0000

LGTM as well, thanks Ted.

On Fri, Jul 22, 2022 at 10:09 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Hi Ted
>
> On Fri, 22 Jul 2022, 06:47 Ted Hardie, <ted.ietf@gmail.com> wrote:
>
>> While I appreciate all the additional thinking in this thread, I think I
>> still need to have a clear answer on what to do about the charter text
>> (sorry, BoF chair priorities).  We can:
>>
>> Leave on-path in
>> Change on-path to something that does not have the same lower-layer
>> implications, but does retain the implication of a coordinated set through
>> whom the data flows
>> Remove it entirely.
>>
>> Based on the discussion so far, my proposal is to adjust this to:
>>
>> "The working group will define MoQ so that the media publication protocol
>> can leverage coordinating relays/caches wherever applicable to improve the delivery
>> performance."
>>
>> I think that addresses Ali's initial concern, removes my concern that we
>> will be signing up to unrelated work (like DNS query traffic), leaves the
>> CDNI problem space outside, and generally goes along with the discussion to
>> date.
>>
>> Any thoughts before I update the PR?
>>
>
> That text works for me. Thank you.
>
> Cheers
> Lucas
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>

v2.23.0 | Report a Bug | By Email