Re: [tsvwg] COMMENT PLEASE: Which DSCP value should we use for LE PHB?

<Ruediger.Geib@telekom.de> Tue, 01 August 2017 08:22 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D86F132B97 for <tsvwg@ietfa.amsl.com>; Tue, 1 Aug 2017 01:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 Jd_KU0uHo-JA for <tsvwg@ietfa.amsl.com>; Tue, 1 Aug 2017 01:22:24 -0700 (PDT)
Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64581127978 for <tsvwg@ietf.org>; Tue, 1 Aug 2017 01:22:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1501575743; x=1533111743; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=fLEpDXbAsJefvpUwgY4/mThkos3ph1PaIdaaKOVIeUo=; b=LTekYCksyCd2N8EXXNV9t2JkPkq/y0NaTNFDVzxMZBpdQpMMhq66dOYt haazXEwChwRVaJU7W4gLqtBUfbNpd1Se8v8NT/M5jEYSzQ87EwBLQMtQg aPciLUw3hkyl5xaEYT9ytVZ3uNtpgBAWd3Yt59vdyJAhW6bnzMnVldNAh 6OKN3qyREB1K2TIkIlVlxHJNZEB5NFEt5HxpwlMby0y41/SGs7PHft2p8 gxKSSTX0OFtbWtP8gPpzMus/klOVo0CKzx/rsCZ1iRaqnOUFO1KXoH0vM TVdPoYrr7HxLaTVwaJHTbRrA1jT0Y1m+ozbNJljpqS8VggrmFfJTU2fR8 g==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2017 10:22:19 +0200
X-IronPort-AV: E=Sophos;i="5.41,305,1498514400"; d="scan'208";a="710079479"
Received: from he105655.emea1.cds.t-internal.com ([10.169.118.87]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/AES256-SHA; 01 Aug 2017 10:22:18 +0200
Received: from HE105654.EMEA1.cds.t-internal.com (10.169.118.86) by HE105655.emea1.cds.t-internal.com (10.169.118.87) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 1 Aug 2017 10:22:18 +0200
Received: from HE105654.EMEA1.cds.t-internal.com ([fe80::44ef:d9e7:d2ca:97f6]) by HE105654.emea1.cds.t-internal.com ([fe80::44ef:d9e7:d2ca:97f6%26]) with mapi id 15.00.1263.000; Tue, 1 Aug 2017 10:22:17 +0200
From: Ruediger.Geib@telekom.de
To: gorry@erg.abdn.ac.uk
CC: fredbaker.ietf@gmail.com, David.Black@dell.com, roland.bless@kit.edu, tsvwg@ietf.org, brian.e.carpenter@gmail.com
Thread-Topic: [tsvwg] COMMENT PLEASE: Which DSCP value should we use for LE PHB?
Thread-Index: AQHS9w2o4prCs8a2Uk2hjK9vt7Sn6aJIEb4AgAAFrYCAAJ4pgIACg0cAgACbsYCAAAkhgIAADh6AgAAYQgCAAJFhAIAA00EAgAjBVYCAAK90gIAXOLgQgAAbQwCAADlBgIAAr3OAgAAl4JA=
Date: Tue, 01 Aug 2017 08:22:17 +0000
Message-ID: <aae889c27e49429db619d71b8c41a76b@HE105654.emea1.cds.t-internal.com>
References: <595F4D19.9030502@erg.abdn.ac.uk> <011e5fb5-6c83-bb38-e2cb-7fced2cb774a@kit.edu> <595F6F4F.20005@erg.abdn.ac.uk> <a97e114c-ca99-f0a3-76e6-784377a5fbe3@gmail.com> <C02205CB-7324-4C06-82CE-C8DA7D686F48@jisc.ac.uk> <74717821-30ae-203b-197b-2455cbf9d4a3@gmail.com> <66425AFB-A929-4A91-90F8-432F4FAE0520@jisc.ac.uk> <daf2d2c4-8a64-7cb3-ac80-3a46903f58f0@kit.edu> <b242faea-a3ca-6d5f-2eb3-85a9a08a6ea9@gmail.com> <59633402.9020907@erg.abdn.ac.uk> <d193232f-f28f-02a2-1171-53d6f0d4bf7b@gmail.com> <CE03DB3D7B45C245BCA0D243277949362FB76819@MX307CL04.corp.emc.com> <50f4b157-425e-a2cc-a924-5dd02345adef@gmail.com> <505f03a57bd4481b832bc22340c37316@HE105654.emea1.cds.t-internal.com> <BCF1D707-549C-4F6A-B493-BB5CA24A3E1F@gmail.com> <7af582df-6c55-a835-8156-50c9f322e4e9@gmail.com> <5980256F.7060100@erg.abdn.ac.uk>
In-Reply-To: <5980256F.7060100@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.160.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/krc_auJBklakuJ7QZ67u7AZtTok>
Subject: Re: [tsvwg] COMMENT PLEASE: Which DSCP value should we use for LE PHB?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 08:22:26 -0000

Gorry, 

Some new comments at the end.

Ruediger
RG>  DSCP 000001 might be an option. No other IETF recommended DSCP 
is re-marked to this one. It is to some extent RFC4594 compatible and 
RFC8100 could cope with it if default transport is applied.

Fred
FB> https://tools.ietf.org/html/rfc2474#section-6 indicates that 000001 
is experimental/local use, available for standards allocation only as necessary.
4597> "We RECOMMEND that the DSCP value(s) of the unsupported service class 
4597> be changed to 000xx1 on ingress and changed back to original value(s) 
4597> on egress..."

Brian
BC > That is a local use within a domain, completely compatible with both 
BC > pools 2 and 3 which are both defined as for local use. So 000001 is 
BC > really not suitable for standards track recommendation, until pool 1 
BC > is full.
....
BC> 000010 is just fine. Why are we still discussing this?

Gorry
GF>....there is reasonable doubt that a LE service can be safely deployed
across the Internet using a codepoint of 000010.

GF> There seems evidence that there are still even now deployed routers 
that have not adjusted their remarking behaviour after the IETF 
deprecated ToS Precedence bleaching. 

[RG2] True. I prefer a core-router to be able to re-mark DSCPs by bit-mask at  
interconnection interfaces rather than DSCP by DSCP. The config effort to customize 
re-marking on a DSCP by DSCP basis is high. An easy to configure alternative is to classify 
by bit-mask and re-mark to a single DSCP. Gorry, do you have any preference here?

GF>....A packet that uses AF marking and encounters ToS Precedence bleaching 
would expereince AF11, AF21, AF31, AF41 emerging remarked to a codepoint 
of 000010, and AF12, AF22, AF32, AF42, VA would emerge as 000100, etc.

GF> Because the LE PHB is a lower effort PHB, implementing a PHB with a codepoint 
of 000010 would result in some traffic originally marked as AFx1 being assigned a 
lower effort than AFx1 or AFx2. 

[RG2] That's a reasonable analysis. A network sending various DSCP into my domain 
without informing my NOC or setting up an SLA is not conservative with what it sends 
in my eyes. If receiving networks are expected to be supportive rather than liberal only 
in that case and are expected to maintain the original Diffserv coding sense of a 
non-cooperative sender, as described by Gorry, I think DSCP 000001 for LE is a good 
choice. That allows to maintain bit-mask based re-marking while maintaining the original 
Diffserv intent of non-cooperative networks, so I ignored the pools. 

Regards, Ruediger