IETF Logo Mail Archive

Re: [Moq] Identifiers

Suhas Nandakumar <suhasietf@gmail.com> Thu, 23 February 2023 07:44 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 1D9E8C1526F7 for <moq@ietfa.amsl.com>; Wed, 22 Feb 2023 23:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 5DnLYxjQaGNG for <moq@ietfa.amsl.com>; Wed, 22 Feb 2023 23:44:16 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 73AD4C1526FF for <moq@ietf.org>; Wed, 22 Feb 2023 23:44:16 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id c18so3145452wmr.3 for <moq@ietf.org>; Wed, 22 Feb 2023 23:44:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hBSdPuc2UR0cTxs1oUGcGNuEOpokADM67D0p4T2tHCQ=; b=SDgO/FUfc4o819naYLlI7arSOZisofbouPRROPjJTRJmpXie1EQJ9DbrajtnVf0aKj GikSPJtHSwBgy0nkr/08idhI9xiF35etkkK5IbDzchGgjqLcfYtcRJDVKPbreogz8klc BrWDR509GCLpjiJF+HjD+TaMMvnTnCBUpn9zKbwOq7AmKC8wUDMXe65uxr5Qz4exjdxJ LXFQu+gBYQHlxBniqYGNsDxUiEBZGdugHM9dg8CxG8nQ0B+ftC0Oj6jHDM9DRsAdtUJA sA2BkUVov1zK6oEiMK4oyBlR1gxzb4ju1ZB13XwSe3KHeJ//iHM3MwFx3G89WLjab6pR qIaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hBSdPuc2UR0cTxs1oUGcGNuEOpokADM67D0p4T2tHCQ=; b=A0NnNGO8iW/oLArOvDWIsVI3+1ZCXOlNMEwjtlDL9clx1ZNIlxvwqxU0OHvLZ3i2Su u0P9ttYuPTWjUHDz8F6atqFyiVaCRkN8o08fRhBNHlOzuFKvBjCW7dTe9nrIn1xFzqjD D8yvFKuwJ6Dm1gG531QpF/SVccz1+cVvFhodOkx6g/WzbdxvxterFvWhX9y+reQc15UH YZVZpHKLoxXhSaXGC6yYEEyDuqVbmnzpQf0OFElPV7RV2lv01GKxABeW+iC5n8eLXVMp 6oBeBRRIoAz3WdgtACqKHP54lqPQHeF8uavduEZM93L+Z3hEMLuvPfXIZmRmlJXrwJnA 8W3w==
X-Gm-Message-State: AO0yUKW5RKuapJG5EKzFACjlwoOP8lZKRCFelOICnJAC1WE+k4kLqTJb OHUvMwD9+Qdo7FFme5tTF5EhdTK0Q/pnNVRbBm0=
X-Google-Smtp-Source: AK7set+XciU7Lqi/7ELV9Kmz5Vr+6cnhvS2hieZgAllqtrgjyp+Ee23ED5HX3Sa6fBj8krb/bL7ZuYfkg/cOs3KZAtU=
X-Received: by 2002:a05:600c:4ed2:b0:3e8:28d:5b53 with SMTP id g18-20020a05600c4ed200b003e8028d5b53mr667471wmq.70.1677138254397; Wed, 22 Feb 2023 23:44:14 -0800 (PST)
MIME-Version: 1.0
References: <CA+9kkMBR1Q84LudGZrYqsABYsQbr9cdyKkGHWzVs22dD-yxG4w@mail.gmail.com> <CA+9kkMBWi9zxocpvjsAw_kpZBqQn7JZxE0nC2minBvW7YH4uew@mail.gmail.com> <CAHVo=Zn8prPeSoom=2B+dwcALjcpDXENCFaHwXT5LM_zYRHAjw@mail.gmail.com> <CAKKJt-dgN4dEOABOjx2TQ7+=kCODuL=s1vrRFRc+15Z+cHfD6g@mail.gmail.com> <MW5PR15MB5145F2ED07653826BBFDB60FD4AA9@MW5PR15MB5145.namprd15.prod.outlook.com>
In-Reply-To: <MW5PR15MB5145F2ED07653826BBFDB60FD4AA9@MW5PR15MB5145.namprd15.prod.outlook.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 22 Feb 2023 23:44:03 -0800
Message-ID: <CAMRcRGQwvK0O=XsA0+DhpZQnzokhc5dhYo+ghzgCWWeVAOS7EQ@mail.gmail.com>
To: Roberto Peon <fenix=40meta.com@dmarc.ietf.org>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Luke Curley <kixelated@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e4854c05f5592dd2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/HnY3RBRO-97duZnldMCkVSXbceM>
Subject: Re: [Moq] Identifiers
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, 23 Feb 2023 07:44:17 -0000

Since the identifiers and their relationships are central concepts for the
data model,  I went ahead and updated the data model and relay PR inspired
by the discussions in this thread, discussions over interim and text
proposals from Christian.

Here is the link: https://github.com/kixelated/warp-draft/pull/95

Love to get feedback here or on github.

Cheers
Suhas

On Wed, Feb 22, 2023 at 9:10 AM Roberto Peon <fenix=
40meta.com@dmarc.ietf.org> wrote:

> I think both are interesting.
>
> The non-bit-identical “redundant” ingest is a fascinating case study,
> though, and one that I’ve run across a number of times.
>
> -=R
>
>
>
> *From: *Moq <moq-bounces@ietf.org> on behalf of Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com>
> *Date: *Wednesday, February 22, 2023 at 1:21 AM
> *To: *Luke Curley <kixelated@gmail.com>
> *Cc: *Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
> *Subject: *Re: [Moq] Identifiers
>
> I was hoping someone else would poke at this, but that hasn't happened so
> far.   Among the other excellent discussion starters Luke and Ted included
> in their first two posts in this thread,  On Tue, Feb 14, 2023 at 9: 06 PM
> Luke Curley <kixelated@ gmail. com>
>
> I was hoping someone else would poke at this, but that hasn't happened so
> far.
>
>
>
> Among the other excellent discussion starters Luke and Ted included in
> their first two posts in this thread,
>
>
>
> On Tue, Feb 14, 2023 at 9:06 PM Luke Curley <kixelated@gmail.com> wrote:
>
> Hey Ted,
>
>
>
>
>
> You bring up a good use-case: redundant ingest. It's not quite multi-path
> but it's similar and it's absolutely a requirement.
>
>
>
> Luke,
>
>
>
> Are you thinking about multiple paths managed at the application layer, or
> within the MOQ protocol layer?
>
>
>
> (I'm creating
> https://github.com/fiestajetsam/draft-gruessing-moq-requirements/issues/88
> on "redundant ingest", just so I don't lose track of it!)
>
>
>
> Best,
>
>
>
> Spencer
>
>
>
> Best,
>
>
>
> Spencer
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>

v2.23.0 | Report a Bug | By Email