IETF Logo Mail Archive

[Tsv-art] DCSP mapping

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Thu, 20 September 2018 10:43 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2E6129385 for <tsv-art@ietfa.amsl.com>; Thu, 20 Sep 2018 03:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 DqzbffFEz5-a for <tsv-art@ietfa.amsl.com>; Thu, 20 Sep 2018 03:43:00 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28A88127133 for <tsv-art@ietf.org>; Thu, 20 Sep 2018 03:43:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=v0DwbiQsQ7U5z7yfxCpzt56wB15jKAUjnEt7yDCZf90cGvovBQCGUbUFoK4PX9q4caUoEWACEgTl3nVJxAC7gNVjB2HboFTQn4YLPhwiHpHnv6QQDc+IlYjK1GbkyPGpndQI2mB1QYcEvAH7+IFbasp4tP5VYHEhZXWsfbPnJ8M=; h=Received:Received:From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 18047 invoked from network); 20 Sep 2018 12:41:56 +0200
Received: from mue-88-130-61-247.dsl.tropolys.de (HELO ?192.168.178.24?) (88.130.61.247) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 20 Sep 2018 12:41:56 +0200
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <81F8CC39-469C-45AA-A01C-3142C9439605@kuehlewind.net>
Date: Thu, 20 Sep 2018 12:41:54 +0200
To: TSV-ART <tsv-art@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-PPP-Message-ID: <20180920104156.18043.3048@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/d-OeUF_VEVNTaocHiVX4Z-1id7Y>
Subject: [Tsv-art] DCSP mapping
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2018 10:43:03 -0000

Hi all,

while reviewing lisp (rfc6830bis) I wasn’t really able to find guidance on what to do with DSCP for IP in IP tunnels. rfc6830bis say "SHOULD be copied from the inner-header DSCP field“ on encapsulation and decapsulation. Other docs even say MUST (e.g. rfc6333 section-7.1). rfc2474 section-7.2 say that for IPsec it MUST NOT be copied on decapsulation. So I guess, at least for decapsulation, it might not alway make sense to overwrite the inner DSCP with the changed outer DSCP and I would think that in most cases this is rather a local policy question. Do we have any more guidance on this in any RFC that I couldn’t find, or is further guidance needed here?

Mirja

P.S: For rfc6830bis I would like the author to add a sentence that this SHOULD may depend on local policy. („In absence of a different local policy for use of DCSP, the DCSP field SHOULD be copied..“ or something like this)

v2.23.0 | Report a Bug | By Email