[AVT] RTP padding
"daniele renzi \(bsoft\)" <daniele@bsoft.info> Wed, 14 November 2007 09:58 UTC
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsF0q-0002kc-Oq; Wed, 14 Nov 2007 04:58:24 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsF0o-0002b8-EF for avt@ietf.org; Wed, 14 Nov 2007 04:58:22 -0500
Received: from smtpd3.aruba.it ([62.149.128.208] helo=smtp4.aruba.it) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IsF0n-0002Yu-PW for avt@ietf.org; Wed, 14 Nov 2007 04:58:22 -0500
Received: (qmail 7159 invoked by uid 89); 14 Nov 2007 09:58:14 -0000
Received: by simscan 1.1.0 ppid: 7115, pid: 7140, t: 0.2388s scanners: clamav: 0.88.4/m:40/d:1722
Received: from unknown (HELO bsoft015) (daniele@bsoft.info@151.71.167.113) by smtp4.aruba.it with SMTP; 14 Nov 2007 09:58:13 -0000
Message-ID: <003c01c826a4$e090d7e0$33010a0a@bsoft015>
From: "daniele renzi (bsoft)" <daniele@bsoft.info>
To: avt@ietf.org
Date: Wed, 14 Nov 2007 10:58:15 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Rating: smtp4.aruba.it 1.6.2 0/1000/N
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Subject: [AVT] RTP padding
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1798322411=="
Errors-To: avt-bounces@ietf.org
Dear Experts, I have a question concerning RFC1889 "RTP: A Transport Protocol for Real-Time Applications". In section 4 - "Byte Order, Alignment, and Time Format" - I found the following sentence: "Octets designated as padding have the value zero.". a) Does this mean that we are forced to use only zero-bytes for padding? Or... b) can the above sentence be intepreted as an example on the specific use of padding for byte alignment? If the latter one is correct and assuming that the padding bit is set to 1 and that the last padding octect correctly indicate how many padding octects are present, are we allowed to use non-zero bytes as padding (e.g. to carry additional - proprietary - information in the RTP packet, which would be simply discarded by any standard receiver)? Does this scenario anyhow violate the standard? Thanks. Best regards, Daniele Daniele Renzi bSoft -- www.bsoft.info +39-0733-57707 (tel/fax)
_______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- Re: [AVT] RTP padding Tom Taylor
- [AVT] RTP padding daniele renzi (bsoft)
- Re: [AVT] RTP padding daniele renzi (bsoft)
- RE: [AVT] RTP padding SOLLAUD Aurelien RD-TECH-LAN