Re: [AVTCORE] Should we update the IANA registry to reflect RFC 5761?

"Roni Even" <ron.even.tlv@gmail.com> Tue, 10 September 2013 20:18 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 9E3A921E80BE for <avt@ietfa.amsl.com>; Tue, 10 Sep 2013 13:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rv0RfZlm7S2w for <avt@ietfa.amsl.com>; Tue, 10 Sep 2013 13:18:55 -0700 (PDT)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5DCCF21E80C7 for <avt@ietf.org>; Tue, 10 Sep 2013 13:18:52 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id h14so4165852eak.15 for <avt@ietf.org>; Tue, 10 Sep 2013 13:18:40 -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 :content-type:content-transfer-encoding:thread-index :content-language; bh=sdxJScSSq2vzLKFEMyppF++HW79wsdFGSKs/PhsW75Y=; b=Pcgf5AwvdOlgh/CKTqK2SMo4vJmKujFDFqxtDXCKssGw5Wr+sE36EEUjTrFaAaWal2 Xrg06O3l6fWFwjwY/3+Nnjiz0wJt+bldejDLekUmXsRzzyxXntTcI+7brVrnjAKUf8vU jMktI6xnx9+iNnPlquDMBjGpkdknqkCs0ZWE4MaxKnxdte0FgziNlK716i1wbjd15sE+ cej4K/SBqa802SQURV++3y6fZmYIcL9qmeRlZF0mWGYUcodMfcfW6gwpw/u9XlpvKakC 6nMEf50fn0gu2iNgKdAvB3+Zk6eE0luwQuWm1xWHjYzxR3pDIYQC8lJsroEkOJlY0Grx 9AhQ==
X-Received: by 10.14.180.73 with SMTP id i49mr6098817eem.55.1378844320748; Tue, 10 Sep 2013 13:18:40 -0700 (PDT)
Received: from RoniE (bzq-79-181-232-77.red.bezeqint.net. [79.181.232.77]) by mx.google.com with ESMTPSA id a43sm34263186eep.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 10 Sep 2013 13:18:40 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Dale R. Worley'" <worley@ariadne.com>, <avt@ietf.org>
References: <201309101932.r8AJWOBj916357@shell01.TheWorld.com>
In-Reply-To: <201309101932.r8AJWOBj916357@shell01.TheWorld.com>
Date: Tue, 10 Sep 2013 23:15:55 +0300
Message-ID: <026301ceae62$8ff6d770$afe48650$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIvIRJJEjptctUNL7cAbcvxymJj+5j+gjEA
Content-Language: en-us
Subject: Re: [AVTCORE] Should we update the IANA registry to reflect RFC 5761?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Sep 2013 20:18:55 -0000

Hi Dale,
We started working in it see
http://tools.ietf.org/html/draft-wu-avtcore-dynamic-pt-usage-01 
Please review
Roni Even

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Dale R. Worley
> Sent: 10 September, 2013 10:32 PM
> To: avt@ietf.org
> Subject: [AVTCORE] Should we update the IANA registry to reflect RFC 5761?
> 
> Back in April, there was a discussion on the Mmusic mailing list regarding
> updating the IANA registry for RTP payload types.
> Primarily, this involves recording RFC 5761 as the primary defining
document,
> and updating the table of payload type ranges to match the usages assigned
> by RFC 5761.  The proposal (as revised during the
> discussion) is:
> 
>     http://www.ietf.org/mail-archive/web/mmusic/current/msg10809.html
> 
>     1) The "Reference" section should be changed from "[RFC3551]" to
>     "[RFC5761][RFC3551]".
> 
>     2) The final rows should be changed to
> 
> 	35-63   Unassigned/secondary dynamic area       [RFC5761]
> 	64-71   Reserved for RTCP conflict avoidance    [RFC5761]
> 	72-76   Reserved for RTCP conflict avoidance    [RFC3551]
> 	77-95   Reserved for RTCP conflict avoidance    [RFC5761]
> 	96-127  Dynamic                                 [RFC3551]
> 
> The discussion is (currently) indexed at http://www.ietf.org/mail-
> archive/web/mmusic/current/thrd3.html,
> starting at "Should we update the IANA registry to reflect RFC 5761?".
> Eight people participated in the discussion (not counting myself).  It
appeared
> to me that there was agreement from all parties that it would be
beneficial to
> update the registry as proposed.  (Disagreement concerned whether further
> information should be added to the registry describing further payload
types
> that could be used in situations where confusion with RTCP was not a
> concern.)
> 
> At the Berlin IETF, the Avtcore chairs presented this slide:
> 
>     http://www.ietf.org/proceedings/87/slides/slides-87-mmusic-7.pdf
>     page 13
> 
>     RTP Payload Types Registry
> 
>     Result of discussion on MMUSIC list:
> 
>     * The "Reference" section should be changed from "[RFC3551]" to
>       "[RFC5761][RFC3551]".
>       - RFC5761: Multiplexing RTP Data and Control Packets on a Single
>       Port
>       - RFC3551: RTP Profile for Audio and Video Conferences
> 
>     * The final rows should be changed to
>         35-63 Unassigned/secondary dynamic area [RFC5761]
>         64-71 Reserved for RTCP conflict avoidance [RFC5761]
>         72-76 Reserved for RTCP conflict avoidance [RFC3551]
>         77-95 Reserved for RTCP conflict avoidance [RFC5761]
>         96-127 Dynamic [RFC3551]
> 
>     * To be reviewed by AVTCORE
> 
> Consequently, I'd like to start the discussion of whether the registry
should
> be updated to mention RFC 5761.
> 
> Dale
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt