Re: [Moq] Charter adjustment

Suhas Nandakumar <suhasietf@gmail.com> Thu, 21 July 2022 16:03 UTC

Return-Path: <suhasietf@gmail.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 300EFC13C513 for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 09:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pwPNZ9Qm9FCv for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 09:03:32 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 673E7C1527B7 for <moq@ietf.org>; Thu, 21 Jul 2022 09:03:32 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id d7-20020a17090a564700b001f209736b89so5735686pji.0 for <moq@ietf.org>; Thu, 21 Jul 2022 09:03:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zuc5E+hNUPtkoJ3s22mnXSFxYstOevxd19L/iGJf9yE=; b=lTYHxTWYdbviB1BOTRbjNEjziu03BkTMxeQe1w555RvRxknW00tGc+IJfeO1JttsKv gFvJaVpXaT2rQgJGYUC2O6wNCAU1vgns7aw+MOJoL9hBr2RyNcaqzRP37RKas266iwbD X9YSBQVBNow6C0+KLHBu7JvsClLT3ZUj/0ypels9kX8vGkeA2aOG0H1iyXleXq54rVqT KWFKe0HUPlaPeRXueV14sWIdkOCgllmKPdNa3wMUsoNqkDipJDs7EGLUrBQW4Wccdf+K gSsCUGhhQaBw9H6TZxxjxo+D74547rSWJP2lNIlHje4ZZyCf2Z74ZOjeKsg58PSXbNlw YP7Q==
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=zuc5E+hNUPtkoJ3s22mnXSFxYstOevxd19L/iGJf9yE=; b=BR3+Nm1NoXicdFIQm9BtbrtF8vesbgnsBXcThwNl0/QjPry3B8/d2qSwZhcw38pFE0 iw1UMgqSl8e9ZOhQlY1IQZeUSjQMy6yKQ8G47OyeohHXCIaGUbz+t5Bgef4uNSeqau+e AynfxUyhwXpIz9G+PsbadjGjZcnW3P0LReQiEOURbSeHlenaa1Rt5nWvFS3NvuKPvII/ VUyy5mKUDbqESZDP9KyUHimEshaXhVNDcdp7EOEnhU4SQ9rLyQuSY9MZoar+1f1bmilI AJT5o069mu6aMgXpx4NwIAJGd+481v5u0s5WpX7gyoQVUSjM519R6Z0wv9NikpiOcN29 2jkQ==
X-Gm-Message-State: AJIora9x2tUv8lndQXuVB1qkHsmzyRrxptqRA/AomJbYceQe26D7L2zf FzAt72wikzvX/V0yQC4rXbtg0eYL0j2kLVWFin0=
X-Google-Smtp-Source: AGRyM1su0QXPqOD+xR7RSSSWSpbyj9t8aEilrs6TC/6ofHIyLgU5/ntTyVjoUzDaf27FLzfTY763DaxCbLnXznb/OT4=
X-Received: by 2002:a17:903:20b:b0:16d:3d79:d56e with SMTP id r11-20020a170903020b00b0016d3d79d56emr393489plh.140.1658419411586; Thu, 21 Jul 2022 09:03:31 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMAr=dMSg9efcYBd5QZquvDhYcQi_gibyttxjqcxvWZKMw@mail.gmail.com> <511BF9AE-C84B-4AC2-9430-B268979078B4@networked.media>
In-Reply-To: <511BF9AE-C84B-4AC2-9430-B268979078B4@networked.media>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 21 Jul 2022 09:03:20 -0700
Message-ID: <CAMRcRGRGR3bXroZch4DAgeN65GodUp2J4=44pvB-6_ieGLKDTg@mail.gmail.com>
To: "Ali C. Begen" <ali.begen=40networked.media@dmarc.ietf.org>
Cc: Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ea978005e452db80"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/6QuCFRzklrtR_YPgw5OBi13NhM0>
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: Thu, 21 Jul 2022 16:03:36 -0000

On Thu, Jul 21, 2022 at 2:16 AM Ali C. Begen <ali.begen=
40networked.media@dmarc.ietf.org> wrote:

> Ted,
>
> My suggestion still stands as follows:
>
> The working group will define MoQ so that the media publication protocol
> can leverage middleboxes such as relays, caches and replication points
> wherever applicable to improve the delivery performance.
>
> Again, “on-path” is not needed IMO. Further, I still dont want to limit
> ourselves to only relays.
>

Ali, just to clarify , doesn't "wherever applicable" cover all the cases
where there might not be a middlebox (overloaded term :-) ) on the path
between MOQ media peers.


>
> -acbegen
>
> > On Jul 21, 2022, at 12:09 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> >
> > Folks seemed fairly happy with the idea of adjusting this text:
> >
> > "The MOQ architecture will allow for the use of optional relays as first
> class elements of the design.  The media publication protocol can leverage
> on-path relays/caches wherever applicable to improve the media quality."
> >
> > to this text:
> >
> > "The working group will define MoQ so that the media publication
> protocol can leverage on-path relays/caches wherever applicable to improve
> the delivery performance."
> >
> > If anyone objects to this change, please say so on the list; otherwise,
> I will adjust in the copy of the charter we review at the BoF (currently
> https://github.com/moq-wg/moq-charter/pull/49).
> >
> > regards,
> >
> > Ted
> > --
> > Moq mailing list
> > Moq@ietf.org
> > https://www.ietf.org/mailman/listinfo/moq
>
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>