[MMUSIC] Alexey Melnikov's Discuss on draft-ietf-mmusic-dtls-sdp-28: (with DISCUSS and COMMENT)
Alexey Melnikov <aamelnikov@fastmail.fm> Mon, 14 August 2017 10:09 UTC
Return-Path: <aamelnikov@fastmail.fm>
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 01AA41320E3; Mon, 14 Aug 2017 03:09:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-dtls-sdp@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150270539396.388.11652057713765142260.idtracker@ietfa.amsl.com>
Date: Mon, 14 Aug 2017 03:09:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DwqVx4WzXrQlsjajdaAcr0FchyQ>
Subject: [MMUSIC] Alexey Melnikov's Discuss on draft-ietf-mmusic-dtls-sdp-28: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 14 Aug 2017 10:09:54 -0000
Alexey Melnikov has entered the following ballot position for draft-ietf-mmusic-dtls-sdp-28: 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-dtls-sdp/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This is a fine document, but I have one [hopefully easy to answer] question and a couple of other minor ones: In Section 5.1. General Endpoints MUST support the cipher suites as defined in [RFC8122]. I don't see any ciphers specified in that RFC. Can you clarify what you mean? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- 8. TLS Considerations NOTE: Even though the SDP 'connection' attribute can be used to indicate whether a new TLS connection is to be established, the unique combination of SDP 'tls-id' attribute values can be used to identity a TLS connection. The unique value can be used e.g., within TLS protocol extensions to differentiate between multiple TLS connections and correlate those connections with specific offer/ answer exchanges. Are any such extensions defined or in the process of being standardized? If an offerer or answerer receives an offer/answer with conflicting attribute values, the offerer/answerer MUST process the offer/answer as misformed. I think a pointer to document and section where such handling is specified would be useful here.
- [MMUSIC] Alexey Melnikov's Discuss on draft-ietf-… Alexey Melnikov
- Re: [MMUSIC] Alexey Melnikov's Discuss on draft-i… Christer Holmberg
- Re: [MMUSIC] Alexey Melnikov's Discuss on draft-i… Alexey Melnikov