Re: [AVTCORE] IANAs payload type number registry and RFC 5761

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 05 March 2014 17:09 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8D541A012A for <avt@ietfa.amsl.com>; Wed, 5 Mar 2014 09:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 fISvSHaOAzNE for <avt@ietfa.amsl.com>; Wed, 5 Mar 2014 09:09:56 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 46E9F1A01A7 for <avt@ietf.org>; Wed, 5 Mar 2014 09:09:56 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-cd-53175a5f11f7
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 12.D7.04249.F5A57135; Wed, 5 Mar 2014 18:09:52 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.2.347.0; Wed, 5 Mar 2014 18:09:47 +0100
Message-ID: <53175A5A.7090805@ericsson.com>
Date: Wed, 05 Mar 2014 17:09:46 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Kevin Gross <kevin.gross@avanw.com>
References: <52E132E5.40207@ericsson.com> <CALw1_Q0=jmmxmwGkmfLmrz4i6PFhnMWjzC+KB=dj2jsgSpxs5Q@mail.gmail.com> <530D9EE0.80600@ericsson.com> <CALw1_Q3DwU05=bDqU_rgtn71cF8q9NPvBgF89VKt3+TtkvgbAw@mail.gmail.com> <5315E873.3030304@ericsson.com>
In-Reply-To: <5315E873.3030304@ericsson.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM+JvjW5ClHiwwe3N3BYve1ayW7w41M7m wOTx7+p2Zo8lS34yBTBFcdmkpOZklqUW6dslcGXsvPOdsWCVYMXx7gdsDYyPebsYOTkkBEwk 3m35zAphi0lcuLeerYuRi0NI4AijxITJV1khnGWMEi3rnjKBVPEKaEt8X9HJAmKzCKhI3Fr5 jhnEZhOwkLj5o5ENxBYVCJbYeeA3I0S9oMTJmU/A6kUE1CUe7XoINodZQEli7tLXYL3CAm4S Sxd/h9r8kVHiwfTVQEUcHJwCOhIPP2mCmBIC4hI9jUEQrXoSU662MELY8hLNW2eDjRECOq2h qYN1AqPQLCSbZyFpmYWkZQEj8ypGjuLU4qTcdCODTYzAYD245bfFDsbLf20OMUpzsCiJ8358 6xwkJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgXFrbd22TXNkb/RVHXBY8/6JP29QidaDc6uU 7bUu6ET8bzih/cfp8aQlf6wPz9gb6R98uFur/TLDQpmFyz5c7OHxj04Tiv+yrl5owrIeUdu5 jLMP/fNYxvhk3b5jB7weVF5UnOnK7u/jF+alv2NeuW7K4wC2ZYskpSXzz/+eKHZDhfGOV+dG 6XVKLMUZiYZazEXFiQDomwUmJAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/671oGc_lAfuzmRlLReqA_nLGAy8
Cc: IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] IANAs payload type number registry and RFC 5761
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 05 Mar 2014 17:09:59 -0000

WG,

I received some feedback on this from Stephen Casner, so I have proposed
some changes. This merges the first and second paragraph and addresses
the tenses.

AVTCORE WG requests that IANA adds the below note to the registry:

RTP Payload types (PT) for standard audio and video encodings
http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1

The current note reads:

Note

    The RFC "RTP Profile for Audio and Video Conferences with Minimal
    Control" [RFC3551] specifies an initial set "payload types".  This
    list maintains and extends that list.

The WG requests that this is change to:

Note

    The RFC "RTP Profile for Audio and Video Conferences with Minimal
    Control" [RFC3551] specified an initial set "payload types".  This
    registry maintained that list. The registry is now closed, see
    RFC 3551. No additional registrations will be done. The payload
    types that have a static mapping are the below ones (0-34).

    The "Reserved for RTCP conflict avoidance" in this table is not up
    to date. [RTCP Control Packet types (PT)] below lists the RTCP
    types that has actually been registered. Subtract 128 from the
    RTCP Packet Type value to find the corresponding PT value with
    collision risk. For further information see RFC 5761.

    If you seek guidance on which PT values to use for assigning
    dynamic payload types, then that is present in RFC 3551 (Section 3)
    and RFC 5761 (Section 4).


Note, if possible I would request that "[RTCP Control Packet types
(PT)]" is made into ling with the following URL:

http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-4


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------