[Spud] Additional SPUD use-cases
"Pal Martinsen (palmarti)" <palmarti@cisco.com> Mon, 16 March 2015 11:07 UTC
Return-Path: <palmarti@cisco.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 03F341A008A
for <spud@ietfa.amsl.com>; Mon, 16 Mar 2015 04:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5,
SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 B1K5iYu7PIuV for <spud@ietfa.amsl.com>;
Mon, 16 Mar 2015 04:07:28 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id D3D961A007C
for <spud@ietf.org>; Mon, 16 Mar 2015 04:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=9038; q=dns/txt; s=iport;
t=1426504047; x=1427713647;
h=from:to:subject:date:message-id:mime-version;
bh=DbZDUEmIULRCYE6mNIEMzRgV+zNHAbO+jre+CzuQZtA=;
b=j/IJJ3u+Mw7IHUMyu4yBkHLgaupiQ3b3GC6QJ7d1t05+P8DrkGWLfkfE
dRCQa03WIHxGwCLFJs4rSc5WfoVM1t+WQEXCuK2UOl2Z/LPX0AHeHphgR
YKf5UWcJFR5XjpN20LxGvmTmfNarV2Dk0VZaqaQvqRgHr1IbRAsb56mGM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CqBQAKuQZV/4YNJK1bgwZSWgSDCLtJhASBfYYSgQ5MAQEBAQEBfYQWI0QBDBcBSgIEMCcELogUDZl6j0qbAgEBCAEBAQEBHY8xg0YvgRYFkDqDa4FkhBeBVJJAI4NubwGBAkF/AQEB
X-IronPort-AV: E=Sophos;i="5.11,409,1422921600";
d="scan'208,217";a="404028196"
Received: from alln-core-12.cisco.com ([173.36.13.134])
by rcdn-iport-4.cisco.com with ESMTP; 16 Mar 2015 11:07:27 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86])
by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t2GB7QvV004045
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL)
for <spud@ietf.org>; Mon, 16 Mar 2015 11:07:27 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.40]) by xhc-rcd-x12.cisco.com
([173.37.183.86]) with mapi id 14.03.0195.001;
Mon, 16 Mar 2015 06:07:26 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: "spud@ietf.org" <spud@ietf.org>
Thread-Topic: Additional SPUD use-cases
Thread-Index: AQHQX9ljbTPSFHtRgkqtPZO67VoMRQ==
Date: Mon, 16 Mar 2015 11:07:26 +0000
Message-ID: <B57E4F68-A0C6-44D8-A729-47B1BED309C9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.210.128]
Content-Type: multipart/alternative;
boundary="_000_B57E4F68A0C644D8A72947B1BED309C9ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/WLzxzGrRuQk2gjV3oyVSS1fhVAM>
Subject: [Spud] Additional SPUD use-cases
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>,
<mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>,
<mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2015 11:07:30 -0000
Hi, I have a few additional SPUD use-cases I want to bring to the list before the BoF. Some of them have already been solved by using STUN as a signalling protocol (http://tools.ietf.org/id/draft-martinsen-tram-discuss-02.txt). I think SPUD is a more efficient carrier of the bits needed to solve some of the use-cases. But for now they are just use-cases, and discussions on how to solve them should probably be deferred to a later stage. * Rate Adaption With Confidence Todays delay sensing rate adaption mechanisms seems to be working very well and can potentially react within half a RTT (Is TT, Trip Time, more accurate or in use as a term?). Having explicit network feedback signalled back to endpoint enabled endpoints to pick a more reasonable starting value when sending media. Explicit signalling during the call enables the network as to signal information back to the endpoint before the problems occur (ECN). Up/down speeding could potentially be done in larger chunks with confidence. * First Come, First Serve In WiFi we have some lab tests that show when you hit a limit you hit it hard and everybody on that link suffers. If 9 people enjoy their video conversations going through the same WiFi AP, it is annoying if a 10th call is added causing everybody to get bad video. A possible solution is to let the network signal back to the 10th participants trying to send video that bandwidth is not available; “I will put you in worse than best effort queue if you try to send at that rate”. If bandwidth become available the network will notify the user. Note that this is not RSVP and resource allocation, just hints from the network that if you try, you will suffer. * Dynamic Per Type Packet Prioritisation (DPTPP *sigh*) The SPUD use case draft opens up for tube prioritisation. It is possible to prioritise among for example audio, video and data tubes when multiplexing (Bundle) is in use. It is important that the prioritisation is made dynamic. When running a video conference you might want to prioritise video packets, but suddenly there is a need to upload a large presentation to all the participants. In that case it might not make sense for participants having pristine 1080p60 video watching each other waiting for the slow uploading of the presentation to finish. And the packet type prioritisation does not necessarily stop at audio or video level. Video packets can have for example spatial layers where packets belonging to a temporal layer can be discarded by the network without to much impact on the video quality. Discarding an I-Frame would have much more impact on the quality. Comments, flames and what not are of course welcome. .-. Pål-Erik
- [Spud] Additional SPUD use-cases Pal Martinsen (palmarti)
- Re: [Spud] Additional SPUD use-cases Ted Hardie
- Re: [Spud] Additional SPUD use-cases Black, David
- Re: [Spud] Additional SPUD use-cases Pal Martinsen (palmarti)
- Re: [Spud] Additional SPUD use-cases Pal Martinsen (palmarti)
- Re: [Spud] Additional SPUD use-cases Black, David
- Re: [Spud] Additional SPUD use-cases Aaron Falk
- Re: [Spud] Additional SPUD use-cases gorry
- Re: [Spud] Additional SPUD use-cases Eggert, Lars
- Re: [Spud] Additional SPUD use-cases Aaron Falk
- Re: [Spud] Additional SPUD use-cases Black, David
- Re: [Spud] Additional SPUD use-cases Mirja Kühlewind
- Re: [Spud] Additional SPUD use-cases Richard Barnes
- Re: [Spud] Additional SPUD use-cases Joe Hildebrand (jhildebr)
- Re: [Spud] Additional SPUD use-cases Joe Hildebrand (jhildebr)
- Re: [Spud] Additional SPUD use-cases Richard Barnes
- Re: [Spud] Additional SPUD use-cases Mirja Kühlewind