[MMUSIC] Alexey Melnikov's Discuss on draft-ietf-mmusic-ice-sip-sdp-38: (with DISCUSS)

Alexey Melnikov via Datatracker <noreply@ietf.org> Fri, 09 August 2019 14:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D011200B4; Fri, 9 Aug 2019 07:41:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-ice-sip-sdp@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <156536166262.15946.384757988181068904.idtracker@ietfa.amsl.com>
Date: Fri, 09 Aug 2019 07:41:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-a-Lzm-4N9B0WeJjAiI6sCNJdgU>
Subject: [MMUSIC] Alexey Melnikov's Discuss on draft-ietf-mmusic-ice-sip-sdp-38: (with DISCUSS)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Aug 2019 14:41:03 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-mmusic-ice-sip-sdp-38: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This is a fine document and I only found a few minor things that should be easy
to fix.

Thank you for addressing my comments. Unfortunately it doesn't look like my
DISCUSS point was addressed yet. Also, your IANA change introduced another
issue.

1) In 5.1:

   The candidate attribute can itself be extended.  The grammar allows
   for new name/value pairs to be added at the end of the attribute.

   Such extensions MUST be made through IETF Review or IESG Approval
   [RFC8126] and the assignments MUST contain the specific extension and
   a reference to the document defining the usage of the extension.

This is effectively creating a new registry, but this information is not
present in the IANA Considerations section. So you need to do one of the
following:

a) Remove the last sentence
b) Reword it to only talk about IETF stream documents for defining extensions
(IESG can't really do what you ask, unless you have an IANA registry
established for these.) c) Move this text to the IANA considerations and update
it to properly define a new IANA registry.

2) In 10.2:

You removed the following text:

   o  Name, Email, and Address of a contact person for the registration

   o  Organization or individuals having the change control

I think removing (postal) Address is a good thing. However the rest of this is
still needed, as IANA uses this information to decide whether a
person/organization is allowed to update an existing registry entry. So please
consider adding it back or explain why this information is not needed for a
registry where external organizations can add value (without publishing an RFC).