Re: [codec] Eric Rescorla's No Objection on draft-ietf-codec-ambisonics-07: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Fri, 24 August 2018 22:30 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4BB7130DEC for <codec@ietfa.amsl.com>; Fri, 24 Aug 2018 15:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id td3FGUROHn3e for <codec@ietfa.amsl.com>; Fri, 24 Aug 2018 15:30:43 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21810130DEB for <codec@ietf.org>; Fri, 24 Aug 2018 15:30:41 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id l15-v6so8002727lji.6 for <codec@ietf.org>; Fri, 24 Aug 2018 15:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LeH2OKXvjPn4re9vdgpmkpNeo9n15o1OX6HNTHJMk24=; b=JwO/HkNJL+wKLNdnC4H4aiQVzXmgsIEZsvgmbsdCOb4NeF0Tea5mceSxyvO/v4gpi+ JuWAHE4qQpyVLA3Pw+yKMKEh0SSLadQIDmG9CpH5c1CkQn8nGSeE0KKejhuCCCpbXt3q FeAqNNyhr8gJYft0YRwYvHuf5N779ddEBLtG5GTkSJ9/Nfpc5nxHRYQ+N4VIyFsTPsi7 uUPGQbRLjOO87ty4//8MCT5VvcMbg5hH2U42g5QASOKTQnu/v9fMOR207LsQ5w2bRqlC ooMWhIWNsBLFgi8r9pmEEwNiCykJ+5xuyzq/esTMvuGwMgFhcFPJaJO5DsTUBmypEZ/P WJzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LeH2OKXvjPn4re9vdgpmkpNeo9n15o1OX6HNTHJMk24=; b=YuaeOCdqIru6+fZYrnssnt+3mm4cBo8KaKmoK1Zxra3syWqWSn8tUDxoi9vbFMnvrk +kDZpb1ONiUyskw1OFyB5E3DRcfhWxvGv2ZEVfsxDrSNs39IyRudhzV8pLx+SJGSGAqS DQvaVCgkGh1CFnSqx3R9FCM/7odufC8jvsm37uRIoH7tH3LVFwoZGoygeqNkNFqUHcm+ kuE4EOxxZh7WHyuWvBzJaBZYPUhUWQuuZxwSPbzauJ19/6RlaRYQTn64ZhcHBQdB48Of 0wgMjU38TTiKZiYURfm1bcXK2slkb20NIlx7IilHZfpR7C2fG7suLicRIf46zM6QC0UK 0j/Q==
X-Gm-Message-State: APzg51B6CwZdGbS30hc23ct1sBjxE+Bp6uB+sH4JC7Uh2t01Y6yLP+TS q669ObGlQ/vC3G92/Yr4JvTpDoEFU32Ym5ocrKjl5Q==
X-Google-Smtp-Source: ANB0VdagcacQZprQZ/bzSmAMHk1uS7UD49wTaB/ZaQt1lrwt8OXvRVrSb44iBniZ1hQwRhEAv9krdraHtEheXJ0tZjs=
X-Received: by 2002:a2e:954e:: with SMTP id t14-v6mr2445396ljh.68.1535149839304; Fri, 24 Aug 2018 15:30:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:4091:0:0:0:0:0 with HTTP; Fri, 24 Aug 2018 15:29:58 -0700 (PDT)
In-Reply-To: <79B0D7AD-8F65-4E9A-A0D6-02473ED1899A@nostrum.com>
References: <153295358610.1069.2720875646830940452.idtracker@ietfa.amsl.com> <CA+KMCSWg366hoC+kit+NCLDU33YR7UBY-mv0Xyh9oXUNsM55eA@mail.gmail.com> <CABcZeBN_59DtVZz7K8x7Q4D_2RMeG15-sxeMAc6neR=HCHE9mw@mail.gmail.com> <79B0D7AD-8F65-4E9A-A0D6-02473ED1899A@nostrum.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 24 Aug 2018 15:29:58 -0700
Message-ID: <CABcZeBMi2QTG9QKHbtcPMjTPq_kcZ9scPcYFKH8tUTh7spK5Sw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Jan Skoglund <jks@google.com>, Tim Terriberry <tterriberry@mozilla.com>, codec-chairs@ietf.org, draft-ietf-codec-ambisonics@ietf.org, codec@ietf.org, The IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d95f2f057435ec34"
Archived-At: <https://mailarchive.ietf.org/arch/msg/codec/54wIiDXRJ8dOvi0kBQ2gQhZgT2I>
Subject: Re: [codec] Eric Rescorla's No Objection on draft-ietf-codec-ambisonics-07: (with COMMENT)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codec/>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2018 22:30:45 -0000

It's a comment on my side, so I leave it to your discretion

On Fri, Aug 24, 2018 at 1:51 PM, Ben Campbell <ben@nostrum.com> wrote:

>
>
> > On Aug 10, 2018, at 2:33 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> >
> >
> > S 5.2.
> > >         The remaining channel mapping families (2...254) are
> reserved.  A
> > >         demuxer implementation encountering a 'channel mapping family'
> > >         value that it does not recognize SHOULD NOT attempt to decode
> the
> > >         packets and SHOULD NOT use any information except for the
> first 19
> > >         octets of the ID header packet (Fig. 2) and the comment header
> > >         (Fig. 10).
> >
> > What is the rationale for this change? Also, why are you doing it in
> > this document? This seems like it's going to be extremely hard for
> > implementors to find in future.
> >
> > These paragraphs are updates to RFC 7845, which needed to be revised to
> accommodate the proposed channel mapping families in this draft.
> >
> > Sorry, I don't understand. Why did they need to be revised to have this
> change?
> >
> >
> > The authors of RFC 7845 and RFC 6716 suggested that the necessary
> updates to RFC 7845 should be included in this draft.
> >
> > I understand, but my point is that people are likely to ignore this
> draft if they don't care about ambisonics and thereby miss out on a
> relevant information. In any case, I'll defer to the WG and AD.
> >
>
> Closing the loop on this point:
>
> We have commonly put updates to RFCs in the documents that create the need
> for the updates, even if the update is generally applicable. We have the
> “Updates/Updated by” relationships to track this sort of thing.
>
> I am sympathetic to Ekr’s argument, in that I agree it would be more
> convenient for the reader to find the update in a smaller, dedicated draft.
> But at this point in the process, I highly doubt the wg has the energy to
> do that sort of restructuring. Therefore I am inclined to leave this the
> way it is.
>
> Thanks,
>
> Ben.
>
>
>
>
>