IETF Logo Mail Archive

Re: [Moq] References for CMAF in the WARP draft, etc.

Cyril Concolato <cconcolato@netflix.com> Thu, 08 February 2024 22:07 UTC

Return-Path: <cconcolato@netflix.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 93B80C1C64DA for <moq@ietfa.amsl.com>; Thu, 8 Feb 2024 14:07:30 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=netflix.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 OqmJhyIxIyTI for <moq@ietfa.amsl.com>; Thu, 8 Feb 2024 14:07:26 -0800 (PST)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 DE379C1516EB for <moq@ietf.org>; Thu, 8 Feb 2024 14:07:26 -0800 (PST)
Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2d0d7985dfdso5562781fa.2 for <moq@ietf.org>; Thu, 08 Feb 2024 14:07:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google; t=1707430045; x=1708034845; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PxV7Olc3yicRwVQ3vDdEDYsScSOybko6R+ead4CyypQ=; b=hJIZGem3WyopQVEJfIRFidBW53eVx8xbi1rnbkWxMaFspIh/UnV9KqhhWCcnXqwW6r a1yfUstIEpw1FF2eK/BfyU1LptjDJH2ApiPkTvXspB0Uc908DCMxCNNxnCZDlJxJuE6g wyDXx7smIUA1nIaEy4qTW6jD0i01HJ964u26w=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707430045; x=1708034845; 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=PxV7Olc3yicRwVQ3vDdEDYsScSOybko6R+ead4CyypQ=; b=mT/6XPd4+nY5F17PmPYliT9XmFB00Ur9JPzIexx2kEjDrTqnHouMJFtO+ZclyEk5Ap 3wUwLrT7jYKRVIy5ew7nooJ0jwq9Vf+LwJfwKplarsKpNqcgGiqSJawH6WAKgE6+Z9gk Wet6E6ovzevLf/MtL/vxG6/+IczFzJarZG4jYnRGietVk4dzA9wUC+vSS7pgMhNwRI53 6mrlHpXvfxwJZywESL5/26UDi/yjYbCAn+ty7BvUsZrGyBlOVkPPH6rCYeY91WQ5tNSQ YnXOb5eYv44toWOdSnrK00rjM/JSTPd2tKIJEgsZLgc2N1TlAOsyxj9ox5oqQUCaCFLk bXLA==
X-Forwarded-Encrypted: i=1; AJvYcCWlyJtZCWLBMgkkgR+90RqbrE7urkThdh0I5d0yeO12D0QVpoqZi1gT6NSxPXwGef1Jjc/+bZGQZuoC7ZI=
X-Gm-Message-State: AOJu0YzeejXAOEmhqIJ2krQM7Wvtrc9mhFdHsCRxmZ+Abdm9LJucNXDt v5XrKASe6UFJwICG4gWialaNCAbODrrrPH+Eb5qvNG9fxJ8XtKgjxuD725Y8nnIXnyzxPJTjnZY blu6lFGgEhT4VBFxDDapPmPV7Uvmaf/5AV6op0g==
X-Google-Smtp-Source: AGHT+IErOriGxgsxv/KCpw8zRqqNSj18MAciRJ+QtUtjX8QPoAkXKqxuhBlkdAw7At44OhNqSSMojWLefv6UW0xHj2k=
X-Received: by 2002:a2e:910f:0:b0:2d0:a35d:4418 with SMTP id m15-20020a2e910f000000b002d0a35d4418mr435544ljg.16.1707430044906; Thu, 08 Feb 2024 14:07:24 -0800 (PST)
MIME-Version: 1.0
References: <CAKKJt-e4Jps9VepMQPAtgkOoHAVUmK_U+ymsakJk2w92RqH7Gw@mail.gmail.com>
In-Reply-To: <CAKKJt-e4Jps9VepMQPAtgkOoHAVUmK_U+ymsakJk2w92RqH7Gw@mail.gmail.com>
From: Cyril Concolato <cconcolato@netflix.com>
Date: Thu, 08 Feb 2024 14:07:13 -0800
Message-ID: <CAMiyXwDtkAUdRGU8qvSgimmdvOBna6W68Sa-FXPq-6hXLhG96g@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: moq-chairs@ietf.org, MOQ Mailing List <moq@ietf.org>, moq-ads@ietf.org, Stephan Wenger <stewe@stewe.org>, Thomas Stockhammer <tsto@qti.qualcomm.com>, Krasimir Kolarov <kolarov@apple.com>
Content-Type: multipart/alternative; boundary="0000000000004e979f0610e60917"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/yE6BmwKnwjn9MUfj9HUtk0U9who>
Subject: Re: [Moq] References for CMAF in the WARP draft, etc.
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, 08 Feb 2024 22:07:30 -0000

Hi all,

Adding Krasimir who is the main chair of CMAF group. I'm co-chair together
with Thomas (also editor).

You can certainly use official liaisons to ask your questions. You can also
contact us directly for quick, non-official responses.

Can you clarify (in a private email if you prefer) what are your "questions
about "available normative references""?

Is it about what is the official reference to the latest CMAF
specification? In that case, the 3rd edition of the specification has been
sent to ISO and should be published soon. If it helps, the group maintains
a public GitHub page documenting the status of the various editions and
amendments of the specification: https://github.com/MPEGGroup/CMAF/

Is it about having access to a free-of-charge version of the standard? MPEG
members have access to the Final Draft International Standard which is
technically equivalent to the version published by ISO, through MPEG's
document management system: https://dms.mpeg.expert/. You can obtain
credentials through your ISO National Body.

HTH,
Cyril

On Thu, Feb 8, 2024 at 12:43 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Dear MOQ,
>
> There was some discussion about using CMAF in WARP, and questions about
> "available normative references", etc.
>
> My suggestion would be that the chairs contact Stephan Wenger (copied),
> who is the current IETF liaison to ISO/IEC JTC1 SC29. He is well familiar
> with the path between IETF and ISO, especially for access to ISO references
> for use by IETF reviewers.
>
> He is also fresh off helping to make this connection happen for IESG
> review of SCIP
> <https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/>from
> AVTCORE. A quick(?) peek at
> https://mailarchive.ietf.org/arch/search/?q=draft-ietf-avtcore-rtp-scip
> shows what can go wrong if a working group isn't proactive.
>
> The other question for the working group is whether implementers will be
> willing to use the CMAF specification from ISO versus ITU-T or DASH-IF, but
> that's another question.
>
> Best,
>
> Spencer
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>

v2.23.0 | Report a Bug | By Email