Re: [AVTCORE] Proposed text for draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01

Glen Zorn <gwz@net-zen.net> Thu, 14 April 2011 12:15 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: avt@ietfc.amsl.com
Delivered-To: avt@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 94962E08BE for <avt@ietfc.amsl.com>; Thu, 14 Apr 2011 05:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYvnIz2qltjI for <avt@ietfc.amsl.com>; Thu, 14 Apr 2011 05:15:36 -0700 (PDT)
Received: from smtpauth18.prod.mesa1.secureserver.net (smtpauth18.prod.mesa1.secureserver.net [64.202.165.31]) by ietfc.amsl.com (Postfix) with SMTP id E7F1FE0700 for <avt@ietf.org>; Thu, 14 Apr 2011 05:15:35 -0700 (PDT)
Received: (qmail 12146 invoked from network); 14 Apr 2011 12:15:34 -0000
Received: from unknown (110.168.101.239) by smtpauth18.prod.mesa1.secureserver.net (64.202.165.31) with ESMTP; 14 Apr 2011 12:15:33 -0000
Message-ID: <4DA6E560.8060702@net-zen.net>
Date: Thu, 14 Apr 2011 19:15:28 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D540ECB1024@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540ECB1024@xmb-sjc-215.amer.cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------070803000008090205020005"
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Proposed text for draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01
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: Thu, 14 Apr 2011 12:15:36 -0000

On 4/14/2011 6:36 PM, Ali C. Begen (abegen) wrote:

,,,

> While a 16-bit length allows for Tokens with a size of up to 65535
bytes, using Tokens larger than 1000 bytes is generally a bad idea since
this can easily cause IP fragmentation. Note that a Token has to be
transmitted in an RTCP compound packet within a UDP packet, which often
has an MTU of 1500 bytes.

How bad of an idea is it?  SHOULD NOT?  MUST NOT?  Whatever?

...