Re: [rtcweb] DSCP marking for STUN packets

James Polk <jmpolk@cisco.com> Mon, 10 March 2014 20:57 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0208F1A04B0 for <rtcweb@ietfa.amsl.com>; Mon, 10 Mar 2014 13:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level:
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 ro-sTTOewfNe for <rtcweb@ietfa.amsl.com>; Mon, 10 Mar 2014 13:57:17 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 104811A04A6 for <rtcweb@ietf.org>; Mon, 10 Mar 2014 13:57:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1748; q=dns/txt; s=iport; t=1394485032; x=1395694632; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=ZkCjE+ZRd6BMfuCQTz6rtQUZi4tG9I08uzTnaVtY5FA=; b=OpohU+xo6L/LeUTbnzeYULn5bKlGddpy2BgDADwCsHooZ+5suJ0WDwRO MvoLbxTNUo3DoKf+lmfBu+/AvNMp/iwqYuCB14xFoP5KZuroNuKHE7Ebv k7dpOIsWNFq0cdDOO/C8ScVmViaOi5E3PJ/geze0t1yYbIY/sEJJ1aU+X 4=;
X-IronPort-AV: E=Sophos;i="4.97,626,1389744000"; d="scan'208";a="309281505"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 10 Mar 2014 20:57:11 +0000
Received: from jmpolk-WS.cisco.com ([10.21.78.182]) (authenticated bits=0) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2AKv90t026761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Mar 2014 20:57:11 GMT
Message-Id: <201403102057.s2AKv90t026761@rcdn-core-5.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 10 Mar 2014 15:57:09 -0500
To: Justin Uberti <juberti@google.com>, "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <CAOJ7v-2jnBAPEhkxjgRtNyntWPL6KBB-PQSLkUPUu91QHoPr3g@mail.g mail.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE22E30E33C@xmb-rcd-x02.cisco.com> <CAOJ7v-2jnBAPEhkxjgRtNyntWPL6KBB-PQSLkUPUu91QHoPr3g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/HH0qztqt4UtfZdpuxHTVcg7hZdE
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DSCP marking for STUN packets
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 20:57:19 -0000

At 12:16 AM 3/10/2014, Justin Uberti wrote:
>I think that the existing guidance should be sufficient in 
>non-multiplexing cases (i.e. BUNDLE). For consent checks, I think 
>the same DSCP markings as any other ICE connectivity checks should 
>be used; for ICE-for-SCTP checks, the same DSCP markings as media 
>packets (i.e. the SCTP traffic) should be used.
>
>If multiplexing is being performed, the connectivity checks probably 
>should use the highest DSCP value being used by the multiplexed media.

why is (seemingly) everyone's default position "use the highest DSCP 
available" for signaling packets?

You just need to make sure the packets aren't starved or dropped 
by/at congestion points.

James



>On Fri, Mar 7, 2014 at 4:35 AM, Muthu Arul Mozhi Perumal (mperumal) 
><<mailto:mperumal@cisco.com>mperumal@cisco.com> wrote:
>
>ICE says that an endpoint SHOULD apply the same DSCP marking as 
>media packets to connectivity checks. This looks insufficient for 
>RTCWEB, since it doesn't cover (at least) the following:
>
>- connectivity checks performed for a stream using different drop 
>pecedences (draft-dhesikan-tsvwg-rtcweb-qos).
>
>- connectivity checks performed for non-media/data-channel traffic.
>
>- DSCP markings for consent checks.
>
>
>
>Comments on where we need to specify them? The last one can probably 
>go into draft-ietf-rtcweb-stun-consent-freshness?
>
>
>
>Muthu
>
>_______________________________________________
>rtcweb mailing list
><mailto:rtcweb@ietf.org>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb