IETF Logo Mail Archive

Re: [rtcweb] DSCP marking for STUN packets

Justin Uberti <juberti@google.com> Mon, 10 March 2014 05:16 UTC

Return-Path: <juberti@google.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 778121A0385 for <rtcweb@ietfa.amsl.com>; Sun, 9 Mar 2014 22:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 cmP-25Y0qHr4 for <rtcweb@ietfa.amsl.com>; Sun, 9 Mar 2014 22:16:49 -0700 (PDT)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id CBBFC1A02B3 for <rtcweb@ietf.org>; Sun, 9 Mar 2014 22:16:48 -0700 (PDT)
Received: by mail-vc0-f177.google.com with SMTP id if17so3679145vcb.22 for <rtcweb@ietf.org>; Sun, 09 Mar 2014 22:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Li9KWaAVSxphzefBT0ZAQ7EwxVqnGKwmfThmEiWMAa0=; b=ZwxJwBJ+vcX43KDcHAk9MpPXcVyxWpqZV1bPIqBHr9Tg5rMS3bP0ESqBVzYBKnzLYk yPRxoW1+/jtUzUvOTahj4EyoEnsOBxIfmsn6FkvUxueuA/DqeUOy53Vxvy0ivq4ev7n5 E3XFv4fK26BzzmJ1zo7NtHPHWc5NKPwOnuNivAlxc48jwp3i8Mc1E89ihRpB845OSxAH 208EB4hSFdfvCJQyo5/8uwfgMEpRwIwRyjLp+A/J0WWsZYeZbK6vo9uKMsloVv2lZoYx rNIjuch55t5y+iwSeC+aKMnzmVCW9rwZRmDsw4o4WWW0AkRarEx1bA/zcgw/aEeMPG8G +tZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Li9KWaAVSxphzefBT0ZAQ7EwxVqnGKwmfThmEiWMAa0=; b=O3lgO5XNWGwoH3+cYFQlLQwjkvoG4o3iJvAbcKd/vPwtxM1dR6AwyEypKSTIbSRClr NiY005KXnaTGTkczmbzHubL5WHEOLuyV3d0lKxq7KftvdP2CIxxSCd9Pmi5okbF6r93S 7nftq1sGfdoGAzcdvuV3f7GKffP72pyk4YGsl0tGD6dNPWFjYsZ+Hg3g87a8rPvex9Gn 3D0fTg1rOA7Yzidx0TCrpQ1KyKIpIlCQU2wjeZro8FYDwbE6eEiYNXtdd9ksZrLnkR3t EMpj4GChog/Fk5+iyg/gvQYlsbJleBRt0OZEWlSfeKPPB8NIOay1/CdWUlzDTgiR1cXS YIDg==
X-Gm-Message-State: ALoCoQncHGgsbRUHt/mdvFaovsYpwYD7eGvjCRzG1jh8udlhBGZ1XAUBfq2Tc+ytz++JJvjFrD4/75oqeL8D9qasrWj87AgLaEAMImWdq3T9WpnjjNDnNjZZ0UcrFIiM7ekskIRoN3RMhbpR2RicOXeN+TIZHzymxDZWfQx8Rhm8A11Kx0l+YA8i+yCj7uUn+t2jUuhakn6/
X-Received: by 10.52.37.161 with SMTP id z1mr1521303vdj.29.1394428603377; Sun, 09 Mar 2014 22:16:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Sun, 9 Mar 2014 22:16:23 -0700 (PDT)
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE22E30E33C@xmb-rcd-x02.cisco.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE22E30E33C@xmb-rcd-x02.cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 10 Mar 2014 05:16:23 +0000
Message-ID: <CAOJ7v-2jnBAPEhkxjgRtNyntWPL6KBB-PQSLkUPUu91QHoPr3g@mail.gmail.com>
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
Content-Type: multipart/alternative; boundary="bcaec51d25b491cc6904f439b5c9"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/L1BeCCEb5Ck8O8SOTp1-79Gm6hc
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 05:16:51 -0000

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.


On Fri, Mar 7, 2014 at 4:35 AM, Muthu Arul Mozhi Perumal (mperumal) <
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
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email