Re: [Moq] Charter adjustment

Ted Hardie <ted.ietf@gmail.com> Thu, 21 July 2022 09:40 UTC

Return-Path: <ted.ietf@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 A184CC14F73F for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 02:40:50 -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_ZEN_BLOCKED_OPENDNS=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 soryp0fsh9_k for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 02:40:50 -0700 (PDT)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 0F260C14F72E for <moq@ietf.org>; Thu, 21 Jul 2022 02:40:50 -0700 (PDT)
Received: by mail-io1-xd30.google.com with SMTP id q14so933037iod.3 for <moq@ietf.org>; Thu, 21 Jul 2022 02:40:50 -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=rA+BtcXhTQsD9qEtMKGtlFOqT0ri6csPAAX0cfgOu3g=; b=frlOh5eydVxk9/ileMGRfm+X5EA3A0YOMhjBTk3UGgY42IbXmaspJPXeG3Zx8MwHuh 6Z+E/ADEvOF9KtawVt+y4v+85yy9fKTIAg7GPZ2X4WOPgxnSSpvAcSc9kEPsxw8koyhx 7Pv7rHNDgehriPW6glhFQDotIcvM+5Fqd8/EjLdF2thSJEop/SZwsCow2si49zQ+PZNQ 030J9lpsJZDj5G0cscbH88m7knnOQfyibooea40DZYN5p5+F3GZlGHuc/36yl1Runuik YKGuzkXsmy4vGrIXrWoVK5ABse3eLgQX2m6+ZvbLAYgRhDvvp8iVyiqBaa/BwxqZrH9c 3YIg==
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=rA+BtcXhTQsD9qEtMKGtlFOqT0ri6csPAAX0cfgOu3g=; b=lsT0Zuce7DVmak65A6f2sOhDFwjFCJ+k6d6v6EuWFcAXBb3J0xEkDEEuLFfC2u76a3 0wb2dC20RsSJp8v6qOVtttEJFFr1V/GMWnmIJQ4WW18GYd6Hxlq65C3PlHoH1h7WINm/ Nim3Knrohy7MgJFCCUwbsEUF65HbxJAlHVXQ/zpq5D4vEFVRHv+r32oUmyfYfrzT8MMO l2OWbiFeX8HOCQzAwQnCSbAJ1owU7ekyjlMq1gDJ2G5nM6sURUZKT5by8Y+8ll46lNMP QG4MFXBogrh9TVXRtv9DrBaH8tZUoLaI511LbK9KYX9xaXULSm8zNU70mBK8zpLPdrl3 DVdQ==
X-Gm-Message-State: AJIora8uAKgdkffqv/s6joQKdFnYXcbRgUIrNHdSNi4MHXOMLgOm/izj 4c2UqQZpVrzXNuEuIwxYKTyxaNAwQw7zSQoxlvW9Sf5EEChOCQ==
X-Google-Smtp-Source: AGRyM1txaajuyq+hNFz20zcg8OThJhl63QXc4Vy3YPjCwU3zRDeJpwZ+a/zu9f9vSHhA/PGufnvjnCpo7Dzy3OOgjz4=
X-Received: by 2002:a05:6638:35aa:b0:341:610d:5a44 with SMTP id v42-20020a05663835aa00b00341610d5a44mr12633355jal.37.1658396449022; Thu, 21 Jul 2022 02:40:49 -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: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 21 Jul 2022 10:40:23 +0100
Message-ID: <CA+9kkMBzZ0ardTkJ43VzKqz3XD=SKK99Sgcw2yrzT+QMvKyBbQ@mail.gmail.com>
To: "Ali C. Begen" <ali.begen@networked.media>
Cc: MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003daa9f05e44d837a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/hpbpJHeOwnKSx0hE9dcu_vwa9Yk>
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 09:40:50 -0000

Hi Ali,

On Thu, Jul 21, 2022 at 10:16 AM Ali C. Begen <ali.begen@networked.media>
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.
>
>
I think the point of "on-path" is to indicate that we're talking about the
boxes through which some or all of the flow delivered to the recipient will
pass.  It may not be the same set of boxes for the whole flow (depending on
cache fill properties or client mobility).  We're not talking about, say,
making the relevant DNS look-ups faster.  If you have a different phrase
that captures that, I think we can discuss that, but I think for scope
reasons that we need something there.

The current text already says relays and caches, so your forumation adds
"replication points"--can you say in more detail what you mean there and
how it would differ from the other two?

For the same scope reason, I would not suggest having "leverage
middleboxes" as a bare statement--there's too much disagreement on what
that set might contain and what "leverage" might mean in practice (as the
discussion about transcoding showed).  I think we're better off narrowing
the set that we are aiming to include as design elements (even optional
ones), while recognizing that there will be other boxes in play in some
deployments no matter what we do.

regards,

Ted




> -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
>
>