Re: [MMUSIC] 4566bis-36: Minor editorial comments regarding line descriptions in section 5

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 26 July 2019 17:08 UTC

Return-Path: <pkyzivat@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 B99C8120077 for <mmusic@ietfa.amsl.com>; Fri, 26 Jul 2019 10:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3KZgXXDuwYYt for <mmusic@ietfa.amsl.com>; Fri, 26 Jul 2019 10:08:08 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (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 087D7120047 for <mmusic@ietf.org>; Fri, 26 Jul 2019 10:08:07 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x6QH83A9019284 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 26 Jul 2019 13:08:04 -0400
To: Adam Roach <adam@nostrum.com>, "Christer.Holmberg@ericsson.com" <Christer.Holmberg@ericsson.com>
References: <0A9693E7-E320-421B-9AF0-54EB95128C2D@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: mmusic@ietf.org
Message-ID: <25508498-98a6-eeeb-3b3d-9b3a8f5f4295@alum.mit.edu>
Date: Fri, 26 Jul 2019 13:08:03 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <0A9693E7-E320-421B-9AF0-54EB95128C2D@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FwW0U63A2S9Cewo3RmJoOHgnt2w>
Subject: Re: [MMUSIC] 4566bis-36: Minor editorial comments regarding line descriptions in section 5
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: Fri, 26 Jul 2019 17:08:10 -0000

Christer,

It seems to me that these are all minor editorial things. Since the 
document has already had its IESG review I am reluctant to make such 
optional changes. If I were to start I can imagine some further back and 
forth on the details of the wording. But I can do these if Adam wants them.

	Thanks,
	Paul

On 7/24/19 6:13 AM, Christer Holmberg wrote:
> Hi,
> 
> I had a look at section 5, and I have a couple of minor editorial comments:
> 
> Q1:
> 
> Section 5.6. says:
> 
>     “If an email address or phone number is present, it MUST be 
> specified before the first media description.”
> 
> I don’t think we need that statement. We define elsewhere (both in 
> Section 5 and in the syntax) the order of the letters.
> 
> ---
> 
> Q2:
> 
> Section 5.4 says:
> 
> “At most one "i=" line can be used for each media description.”
> 
> …while section 5.5 says:
> 
> “This line is OPTIONAL. No more than one "u=" line is allowed per 
> session description.”
> 
> …while section 5.6 says:
> 
> “Inclusion of an email address or phone number is OPTIONAL.”
> 
> I assume “at most one” and “no more than one” means the same thing, and 
> if we want to explicitly indicate that something is OPTIONAL we should 
> use it in all places where it applies. So, I think it would be good to 
> have aligned terminology, e.g.,:
> 
> “This X line is OPTIONAL, and at most one X line can be included in a 
> media/session description”
> 
> ---
> 
> Q3:
> 
> In section 5.4 the text says twice that there can be at most one “i=” 
> line in a media description. Do we need to repeat?
> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>