[AVTCORE] Alissa Cooper's Yes on draft-ietf-avtcore-5761-update-05: (with COMMENT)
"Alissa Cooper" <alissa@cooperw.in> Mon, 10 October 2016 15:57 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C9F129488; Mon, 10 Oct 2016 08:57:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147611502447.31457.3601719232248166526.idtracker@ietfa.amsl.com>
Date: Mon, 10 Oct 2016 08:57:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/lCJ3IGZ5Zq1Djip96CC-uFwJsVo>
Cc: avtcore-chairs@ietf.org, avt@ietf.org, draft-ietf-avtcore-5761-update@ietf.org
Subject: [AVTCORE] Alissa Cooper's Yes on draft-ietf-avtcore-5761-update-05: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2016 15:57:04 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-avtcore-5761-update-05: Yes 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-avtcore-5761-update/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- "If the answerer includes an "a=rtcp-mux" attribute in the answer, the offerer and answerer MUST multiplex RTP and RTCP packets on a single port. If the answer does not contain an "a=rtcp-mux" attribute, the offerer and answerer MUST NOT multiplex RTP and RTCP packets on a single port." The first of these says "the answerer" and the second says "the answer." This is also how the text appears in 5761, but the difference between them caught my eye here because of the other changes being made. Is the intended meaning different between "the answerer" and the "the answer"? That is, is the implication that if the answerer include a=rtcp-mux but that somehow gets modified such that when the answer arrives at the offerer, it no longer contains a=rtcp-mux, that neither side is supposed to multiplex? This made a little more sense to me in 5761 because it was only about what the offerer should do, but now it is about what both parties should do, so I think it would help to clarify whether these two statements are both about what the answerer puts in the answer.
- [AVTCORE] Alissa Cooper's Yes on draft-ietf-avtco… Alissa Cooper
- Re: [AVTCORE] Alissa Cooper's Yes on draft-ietf-a… Christer Holmberg