Re: RTP and UDP checksum=0

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 18 April 2011 08:02 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ipv6@ietfc.amsl.com
Delivered-To: ipv6@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1A392E07B0; Mon, 18 Apr 2011 01:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level:
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 dGjGGnz2r+My; Mon, 18 Apr 2011 01:02:26 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfc.amsl.com (Postfix) with ESMTP id C2781E0790; Mon, 18 Apr 2011 01:02:25 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-51-4dabf010adb7
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F7.41.09202.010FBAD4; Mon, 18 Apr 2011 10:02:25 +0200 (CEST)
Received: from [147.214.183.89] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Mon, 18 Apr 2011 10:02:24 +0200
Message-ID: <4DABF00F.6080600@ericsson.com>
Date: Mon, 18 Apr 2011 10:02:23 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: RTP and UDP checksum=0
References: <012101cbfb81$84a04500$8de0cf00$@com>
In-Reply-To: <012101cbfb81$84a04500$8de0cf00$@com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-6man-udpchecksums@tools.ietf.org" <draft-ietf-6man-udpchecksums@tools.ietf.org>, "draft-ietf-6man-udpzero@tools.ietf.org" <draft-ietf-6man-udpzero@tools.ietf.org>, "avt@ietf.org" <avt@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 08:02:30 -0000

Dan Wing skrev 2011-04-15 17:26:
> Observation:  tunneled packets have two elements actively 
> deciding checksum=0 is okay.  Those elements are the 
> tunnel encap and tunnel decap.
> 
> Question: Should non-tunneled UDP flows, *established with 
> explicit signaling*, also be allowed to decide that checksum=0 
> is okay?  For example, an RTP-over-UDP flow established 
> with RTSP or SIP signaling.  Some RTP traffic includes its
> own checksum at the application layer (e.g., SRTP authentication)
> and gains little or no benefit to a UDP checksum.  Near as I
> can discern, SIP-signaled flows meet all of the constraints
> discussed in 
> http://tools.ietf.org/html/draft-ietf-6man-udpzero-02#section-5.1

Dan,

I agree that SRTP would be safe to use without checksum also in v6.
However, using non-secured RTP without checksums are "a very bad idea"
(TM).

Also, if you are an end-point generating RTP flows then the UDP checksum
overhead is generally not that big of an issue compared to all media
processing. I think the only node that where this could make any
significant difference are in a transport translator, which only relays
an incoming packets to a number of other unicast addresses.

I do however, see a need for a number of additional mechanisms, at least
signalling if one wants do do this for RTP with SRTP integrity
protection enabled. SIP/SDP signalling and maybe also an additional ICE
STUN check to verify the capability prior to using it to avoid loss due
to middleboxes that doesn't handle zero UDP checksum with v6.

My general fear is that the usage of zero checksum for IPv6 is done
without thinking and that it is similar in behavior to IPv4 which it
clearly is not, but I guess that is difficult to ensure. Soo frankly, is
it really worth it for RTP?

I guess what you say comes down to if we should ensure that the text is
generalized enough that it doesn't only apply to tunnel applications. To
me the new specification text before the bullet list appears ok. If only
give tunnels as an example. The bullet list also appears ok from a
non-tunnel application perspective. So it is likely only the title and
some of the introduction text that needs to be ensured that it doesn't
only speak of tunneling.

I think the authors should ensure this as it appears to be minor
modifications and clearly we didn't mean this to only be applicable to
one type of applications, but all that meets the considerations.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------