Re: [Lsr] LSR: Using DSCP for path/topology selection Q

Peter Psenak <ppsenak@cisco.com> Thu, 15 November 2018 07:21 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF2612872C for <lsr@ietfa.amsl.com>; Wed, 14 Nov 2018 23:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 r6lj93OZAzwf for <lsr@ietfa.amsl.com>; Wed, 14 Nov 2018 23:21:56 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E522127B92 for <lsr@ietf.org>; Wed, 14 Nov 2018 23:21:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1586; q=dns/txt; s=iport; t=1542266516; x=1543476116; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=l8uIL8mrADaHAc72cAERGPUDv1ZerEDUjiKCV7FtJrY=; b=JSDC4GceHfDzpbMD3eQYfkO287C7HS4E+V19s5X5eJaAPtWJ6Eyl7AFu MmwneHdHtKtP2tfdNJs+ZsbwAN3BbI0ee/Q8TJKjS48SBnXJDgkVnvoZY /ubRLF83hs+mE5I9CC3FQHCHZ/YZJedmGYqyt6e6ecyyb4lmDO2OKaBM+ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CpAAC7He1b/xbLJq1iHAEBAQQBAQcEAQGBVAQBAQsBgmlPIRInjG+NKJkwDRgLhEkCg2w3Cg0BAwEBAgEBAm0cDIU6AQEBAwEBATY2ChELDgoJFg8JAwIBAgEVMAYBDAYCAQGDHoF5CA+pJg6FQYReBYwcgUA/hCODGwEBhzwCiTWGF5ATCZEjGIFYiAGHHIldjiWBWyKBVTMaCBsVO4JsgicXiF6FPz4DMI4YAQE
X-IronPort-AV: E=Sophos;i="5.56,235,1539648000"; d="scan'208";a="8060026"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Nov 2018 07:21:54 +0000
Received: from [10.147.24.43] ([10.147.24.43]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id wAF7Lrt4022430; Thu, 15 Nov 2018 07:21:53 GMT
Message-ID: <5BED1E91.7030509@cisco.com>
Date: Thu, 15 Nov 2018 08:21:53 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Toerless Eckert <tte@cs.fau.de>, lsr@ietf.org
References: <20181115022918.pfgcztognsjeb37v@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20181115022918.pfgcztognsjeb37v@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.147.24.43, [10.147.24.43]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/E_au37GJ6BMgkEE1UKL1wHCpcd0>
Subject: Re: [Lsr] LSR: Using DSCP for path/topology selection Q
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2018 07:21:58 -0000

Toerless,

On 15/11/18 03:29 , Toerless Eckert wrote:
> Whats the current best guidance on using DSCP for selection of path,
> specifically for selection of topology with MTR (RFCs 4915, 5120, 7722) ?
>
> My understanding from history is that this looked like a good idea
> to customers first, but when implementations became available,
> customers really did not want to implement it because of the overloading
> of DSCP between QoS and routing and the resulting management complexity.
>
> Has the idea of using DSCP for path selection been re-introduced in any
> later work like flex-Algos ?

no, but if someone wanted to do so it can.
draft-ietf-lsr-flex-algo does not say anything about DHCP.

thanks,
Peter

>
> If there could be rough consensus that this is in general a bad idea, i wonder
> if it would be appropriate to have a short normative document from LSR
> defining that the use of DSCP for topology selection is historic and
> not recommended anymore and make this an update to above three RFCs,
> maybe also pointing out that there are other methods to select a
> topology and those remain viable:
>
> I specifically would not like to see the actual MTR RFCs to be changed
> in status, because MTR actually does work quite well and is supported
> in products and deployed with IP multicast, even with multiple
> topologies for IP multicast in live-live scenarios.
>
> Thanks!
>      Toerless
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> .
>