Re: [MMUSIC] [Technical Errata Reported] RFC4566 (5595)

worley@ariadne.com (Dale R. Worley) Wed, 09 January 2019 02:19 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F1512EB11 for <mmusic@ietfa.amsl.com>; Tue, 8 Jan 2019 18:19:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 r3Jg9YV-d1x8 for <mmusic@ietfa.amsl.com>; Tue, 8 Jan 2019 18:19:35 -0800 (PST)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33A8312008A for <mmusic@ietf.org>; Tue, 8 Jan 2019 18:19:35 -0800 (PST)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id h1YQgFsEp9VLoh3SvgirBG; Wed, 09 Jan 2019 02:19:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1547000374; bh=YNl4sVQPMCxTpyKjvEaWtiF7CG7jgbjaIfn3zSsO2WY=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=KtuUYEIHz+5gBuS943a4kA3m0Tj9rHArpKctlCFsciTiLCEtrBV/ehyuM5tnFgXZR 1mEehGfYIwudJ7bJ7NIQB/AcJ18JasJGSZ1secDdKUTm9sqp9gaMbDwSqoDn1FfJF8 QelmHZmI6wa/HwFxKyn3ZgtHa4n5oQk3szL3uYHAYMQE+MwMSk1wQVMirGdDQx55ww U/qsMeKKzoDAtGpoT7e6b0+jZFGi8vHfOjfpnQIj3FVCmAOw7mRY/gewwv4GpA8lyB OqrcTWzA4VO2kQn/MeC2ybwqrVUSkD9gXVWiHtQM7LROVuTcHkO91sRRsyUogQqD3u O7DMsHBCRKN+g==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-09v.sys.comcast.net with ESMTPA id h3SqgyeMGIqMhh3SrgiDBD; Wed, 09 Jan 2019 02:19:31 +0000
X-Xfinity-VMeta: sc=0;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x092JSU7008045; Tue, 8 Jan 2019 21:19:28 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x092JQ5R008036; Tue, 8 Jan 2019 21:19:26 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: M.Handley@cs.ucl.ac.uk, van@packetdesign.com, csp@csperkins.org, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, bo.burman@ericsson.com, fandreas@cisco.com, gscallan@vordis.com, mmusic@ietf.org, rfc-editor@rfc-editor.org
In-Reply-To: <20190108164321.D46ABB8087C@rfc-editor.org>
Sender: worley@ariadne.com
Date: Tue, 08 Jan 2019 21:19:25 -0500
Message-ID: <87d0p68tea.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mMdPHnigvQ8MmQthsRXmoNWzJgI>
Subject: Re: [MMUSIC] [Technical Errata Reported] RFC4566 (5595)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2019 02:19:38 -0000

RFC Errata System <rfc-editor@rfc-editor.org> writes:
> [...]  In section 5 it indicates that the SDP lines MUST appear in the
> exact order given at the top of Page 9.  The order that is shown
> indicates that the Session Attributes appear before the Time
> Description. [...]

The example is correct, but there's a subtle point about the text that
makes it vulnerable to misreading.  Viz., section 5 says:

   Some lines in each description are REQUIRED and some are OPTIONAL,
   but all MUST appear in exactly the order given here [...]

Followed by:

      Session description
         v=  (protocol version)
         o=  (originator and session identifier)
         s=  (session name)
         i=* (session information)
         u=* (URI of description)
         e=* (email address)
         p=* (phone number)
         c=* (connection information -- not required if included in
              all media)
         b=* (zero or more bandwidth information lines)
         One or more time descriptions ("t=" and "r=" lines; see below)
         z=* (time zone adjustments)
         k=* (encryption key)
         a=* (zero or more session attribute lines)
         Zero or more media descriptions

      Time description
         t=  (time the session is active)
         r=* (zero or more repeat times)

      Media description, if present
         m=  (media name and transport address)
         i=* (media title)
         c=* (connection information -- optional if included at
              session level)
         b=* (zero or more bandwidth information lines)
         k=* (encryption key)
         a=* (zero or more media attribute lines)

Look back on this and ask yourself, What is "the order given"?

It looks like the order is "session description" followed by "time
description" followed by "media descriptions, if present".  But it's
not.  "The order given" covers only the section titled "Session
description" -- "Time description" is included within it by reference in
the 10th item, and "Media description, if present" is included within it
multiply by reference in the 14th item.  (Compare with the grammar in
section 9.)

In particular, time descriptions come before session attributes.

So it would really help if this text was clarified in 4566bis.

Dale