Re: [AVTCORE] Draft new: draft-holmberg-avtcore-5761-update-00

"Roni Even" <ron.even.tlv@gmail.com> Wed, 22 June 2016 21:23 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3A1112D75A for <avt@ietfa.amsl.com>; Wed, 22 Jun 2016 14:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 94GGf8_H_Cxt for <avt@ietfa.amsl.com>; Wed, 22 Jun 2016 14:23:50 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF27412D90D for <avt@ietf.org>; Wed, 22 Jun 2016 14:23:49 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id f126so103158024wma.1 for <avt@ietf.org>; Wed, 22 Jun 2016 14:23:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=YJNYWtH/hh1YNF+uMWxEB8BjwahT+bp+E0rFhe1NNkM=; b=quBHDYA5MB7s5CJS1lbPfDKzhyyQuAxQWhuvdQQLpN62YbEMVijxMUhqyabM6cYRo9 nW1nX1aYYP9GVRzexiHetV2ScMOVA/8ruDclsdV8eiUrIlX4ci8ooaHMObad6UDnHRpV eZGlOglyCjn6oRaR5PC6oSMT8Zd3b9f0yAP7IFdIEFurf1+9Y8FeW4675v80i2rBczNC 5EIhMGguln/auY/Q7dTVRZWQsmogAytP3LepUAC1PDcNopXiz58Rb8OjTnqHICzQqv/C 2BkysC7861H2erqWqvUDVKc2hR3Mvj20N7RW/romJ9PygCVac9fM/5oMyI1KicnqwQXe An2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=YJNYWtH/hh1YNF+uMWxEB8BjwahT+bp+E0rFhe1NNkM=; b=Yt+uqEEOEJK1X7qYXkvEozPptSvBb5AjtqiSz0L/+Q6DXYUgBJseNrOn16A6IErHAC 9RxAh4r/Eeu3YrwBOIki3oj2xIcyMcfAe4PIAfchAvu7cO7EC9WQ7nIvWfEcqzlPNGij LEGWKI/ekcSDjyyM3kFAn5oPvhTXcCZrGszjR/EIVmxkaG3TrJKsXwN/mgXbm2sR+Iji z34u6Cu294JjTlsbw4EWd+HLvUf3nPbQ+X7/gjEW+J2pShZ+T24xpi3988YY/JgDCQdv 36QUYIzEohEhE8/1xpVyH8egFFNq0fatrCtoScLN8Uax761QmbDe2ktepMjlW4Z1VNAk ZyuQ==
X-Gm-Message-State: ALyK8tKUBTX7+loXCkoqJCrMWN6DcAC24tOIaC+uBVIsTGhQcvMT+uKpOLRAiKr8c7mieQ==
X-Received: by 10.28.71.28 with SMTP id u28mr10464050wma.47.1466630628065; Wed, 22 Jun 2016 14:23:48 -0700 (PDT)
Received: from RoniPC (bzq-79-179-194-235.red.bezeqint.net. [79.179.194.235]) by smtp.gmail.com with ESMTPSA id o10sm1127741wjz.37.2016.06.22.14.23.46 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Jun 2016 14:23:46 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, avt@ietf.org
References: <D386CB5E.AC1C%christer.holmberg@ericsson.com> <140601d1cc9d$9a49e1c0$cedda540$@gmail.com> <7594FB04B1934943A5C02806D1A2204B381009F3@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B381009F3@ESESSMB209.ericsson.se>
Date: Thu, 23 Jun 2016 00:22:22 +0300
Message-ID: <144401d1cccc$2b41eaf0$81c5c0d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_1445_01D1CCE5.5090A990"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHs7d2efKLvKW4410Ig489CHZ04VgG3ukw8Aph59nyfnTbZkA==
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/wJyvf77wba5U-1cygtqJa4plWuc>
Subject: Re: [AVTCORE] Draft new: draft-holmberg-avtcore-5761-update-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Wed, 22 Jun 2016 21:23:53 -0000

inline

 

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
Sent: Wednesday, June 22, 2016 8:27 PM
To: Roni Even; avt@ietf.org
Subject: RE: [AVTCORE] Draft new: draft-holmberg-avtcore-5761-update-00

 

Hi,

 

>I have a comment and a nit

> 

> Comment:  I am not sure what this sentence means "and the answerer MUST
NOT multiplex RTP and > RTCP packets on a single port"

> The answerer cannot send multiplex RTP and RTCP packets if the attribute
is not there, it can either 

> send RTCP to RTP port+1 or to the port specified by the a=rtcp attribute.

 

It means that the answerer must not multiple RTP and RTCP packets on a
single point. Not sure I understand the issue :)

[Roni Even]If you mean that  the answerer MUST not send multiplex RTP/RTCP
it is implied by the lack of the attribute and by the definition of where
RTCP should go to, so the sentence is not needed. Do you mean that the
answerer MUST not receive multiplex RTP/RTCP streams?

That is tied to my question about can the answerer use a=RTCP to receive
multiplex RTP and RTCP without explicitly using rtcp-mux attribute?

 

> Nit: "the rules in Section 4" add of RFC5761

 

Keep in mind that the text is actually new RFC 5671 text. Do we want the
text to refer to its own RFC, or could add "of this specification" inste

 

Regards,

 

Christer

 

 

 

Roni 

 

 

 

 

From: avt [mailto:avt-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Wednesday, June 15, 2016 9:04 AM
To: avt@ietf.org
Subject: [AVTCORE] Draft new: draft-holmberg-avtcore-5761-update-00

 

Hi,

 

I've submitted a new draft: draft-holmberg-avtcore-5761-update-00.

 

The draft clarifies that the a=rtcp-mux attribute is only allowed in an
answer if also present in the associated offer, and that the usage of
RTP/RTCP-mux is negotiated for both directions.

 

The need for this came from 3GPP, where people had different understandings
regarding the meaning of the current text.

 

For the GitHub fans: https://github.com/cdh4u/draft-5761-update (NOTE:
Personal repo)

 

Regards,

 

Christer