Re: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02

gorry@erg.abdn.ac.uk Thu, 14 August 2014 13:06 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: dart@ietfa.amsl.com
Delivered-To: dart@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6371A06EE for <dart@ietfa.amsl.com>; Thu, 14 Aug 2014 06:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level:
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 U2nk8iYw4UIt for <dart@ietfa.amsl.com>; Thu, 14 Aug 2014 06:06:27 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 7E40E1A0AF1 for <dart@ietf.org>; Thu, 14 Aug 2014 06:05:39 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9455A2B436A; Thu, 14 Aug 2014 14:05:35 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Thu, 14 Aug 2014 14:05:36 +0100
Message-ID: <7dbc0254bcbb80771a8e36d2cc255512.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F502DE559734@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <53EBCB82.9010901@erg.abdn.ac.uk> <CA7A7C64CC4ADB458B74477EA99DF6F502DE559734@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Date: Thu, 14 Aug 2014 14:05:36 +0100
From: gorry@erg.abdn.ac.uk
To: Ruediger.Geib@telekom.de
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/Smp4ExR0fwvJkNJrk-g-oy-3j0s
Cc: gorry@erg.abdn.ac.uk, dart@ietf.org
Subject: Re: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02
X-BeenThere: dart@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <dart.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dart>, <mailto:dart-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dart/>
List-Post: <mailto:dart@ietf.org>
List-Help: <mailto:dart-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dart>, <mailto:dart-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Aug 2014 13:06:30 -0000

Thanks

When I said "transport" I was thinking of the algorithms to be used in the
end-host to figure out what was operational and where congestion and delay
were experienced. But what you say is all an import part. I expect what
you discuss, could go into the tsvwg intercom draft.


Gorry
> Hi Gorry,
>
> the following text will likely appear in the next version of my
> diffserv-intercon draft. The more DSCPs appear in a flow which aren't
> deployed end-to-end for the corresponding PHB, the more often one of the
> scenarios will be encountered.
>
> The following scenarios start from a domain sending
> IP traffic using a PHB and a corresponding DSCP to an interconnected
> domain. The receiving domain may
> -	Support the PHB and offer the same corresponding DSCP
> -	Not support the PHB and use the DSCP for a different PHB
> -	Not support the PHB and not use the DSCP
> -	Support the PHB with a differing DSCP, and the DSCP of the
>        sending domain is not used for another PHB
> -	Support the PHB with a differing DSCP, and the DSCP of the
>        sending domain is used for another PHB
>
> Another question to be answered then is how a network provider will treat
> unrecognized or unexpected DSCPs received at network boundaries.
>
> Regards,
>
> Ruediger
>
>
> -----Ursprüngliche Nachricht-----
> Von: Dart [mailto:dart-bounces@ietf.org] Im Auftrag von Gorry Fairhurst
> Gesendet: Mittwoch, 13. August 2014 22:33
> An: dart@ietf.org
> Betreff: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02
>
>
> I can see good points raised on the details, instead I have some questions
> about the overall document strcuture:
>
> [snip]
>
> (2) I don't know if the document's goal is also to make transport
> recommendations for using multiple code points - i.e.things such as must
> be robust to the network changing a DSCP; needs to independently verify
> that a particular DCSP is not being black-holed, needs to not imply
> relative precedence when interpreting loss or marking of packets for a
> flow using multiple DCSPs etc. ???
>
> If these are out of scope, then maybe the document should say that this
> particular document does not provide this sort of guidance.
>
> Gorry
>
> _______________________________________________
> Dart mailing list
> Dart@ietf.org
> https://www.ietf.org/mailman/listinfo/dart
>