IETF Logo Mail Archive

Re: [Netconf] IETF 101 SN Question 3: DSCP as its own feature?

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 16 April 2018 21:14 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19D212704A for <netconf@ietfa.amsl.com>; Mon, 16 Apr 2018 14:14:55 -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_DKIMWL_WL_HIGH=-0.01, 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 OmADyKSi5UxS for <netconf@ietfa.amsl.com>; Mon, 16 Apr 2018 14:14:53 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFE34124B0A for <netconf@ietf.org>; Mon, 16 Apr 2018 14:14:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7262; q=dns/txt; s=iport; t=1523913293; x=1525122893; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Y+WeNJCaXFNTo6UvEDP0iWo2nvThrTy1QaGU3KLQsfg=; b=UVqcoJrQNsKRex9EKVEq2R2Ydi9Vp4jpyiyJakFDTnJJTEL+6H4EThrC JdzFg1+zPBW2yO5P1DeARENyobxZhk1gdj7pcwGTHlQ/uSGDnwVjy1AsF Cj0AMB9aY/x/hcLR+3wkQr1xjKggZRSTobJezy2CEfOecNRu2d5Vm4RCg g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BBCgBEEdVa/4MNJK1dHAEBAQQBAQoBAYJNSithF2MoCphzgXSBD41+hGqBewslhF4CgkQhNRcBAgEBAQEBAQJsHAELhSIBAQEBAy1cAgEIEQQBAS8yHQgBAQQTCIQhZA+oEYhBgiAFiAaBVD+BD4MLgUGBUAICAQEWgSOFdwKMBItgCAKFV4hajFOJLIZMAhETAYEkAR4BNYFScBU7gkODMQEHgSWGMoU+bwGNE4EXAQE
X-IronPort-AV: E=Sophos;i="5.48,460,1517875200"; d="scan'208,217";a="100038026"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Apr 2018 21:14:53 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w3GLEqdu015513 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <netconf@ietf.org>; Mon, 16 Apr 2018 21:14:52 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 16 Apr 2018 17:14:50 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Mon, 16 Apr 2018 17:14:50 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: IETF 101 SN Question 3: DSCP as its own feature?
Thread-Index: AdPLiA0Fz07Ou+3RS7mSGBKIu+TPnQKPvgzA
Date: Mon, 16 Apr 2018 21:14:50 +0000
Message-ID: <d4c868ca105c46f0ade9ca9414b3925c@XCH-RTP-013.cisco.com>
References: <e84a00d0a68f4cf383cce7a5acbcf736@XCH-RTP-013.cisco.com>
In-Reply-To: <e84a00d0a68f4cf383cce7a5acbcf736@XCH-RTP-013.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: multipart/alternative; boundary="_000_d4c868ca105c46f0ade9ca9414b3925cXCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/j3Gs9K3r87soGLL9a3vGnNh5P8o>
Subject: Re: [Netconf] IETF 101 SN Question 3: DSCP as its own feature?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2018 21:14:56 -0000

Alex and Martin expressed a preference for DSCP as its own separate feature.  And so that is the way it is reflected in the just posted v12 version of:
https://datatracker.ietf.org/doc/draft-ietf-netconf-subscribed-notifications

Unless anyone has a strong issue here, let's close Question 3.

Eric

From: Netconf <netconf-bounces@ietf.org> On Behalf Of Eric Voit (evoit)
Sent: Tuesday, April 3, 2018 4:13 PM
To: netconf@ietf.org
Subject: [Netconf] IETF 101 SN Question 3: DSCP as its own feature?

In London, we agreed to get feedback on the following question from the list:

In draft-ietf-netconf-subscribed-notifications, should 'dscp' be its own optional feature?  Or should it be mandatory to implement?

For more on the discussion (and to view the slide) see:
https://youtu.be/KJtg-J-6CZM?t=34m2s
https://etherpad.tools.ietf.org/p/notes-ietf-101-netconf?useMonospaceFont=true

I have no strong preference, but would default to mandatory-to-implement as we already have many optional features, and this is fairly simple.  Thoughts?

On a related discussion, I would like to propose renaming 'dscp' to 'priority'.   The reason is that I have received feedback that the object name 'dscp' will never make it through the IESG, as DSCP is a well-known object in the IP header.  And even though everyone in implementation will map to DSCP, applications are actually requesting a network priority rather than a DSCP.   So any objections to me making the change?

Eric

v2.23.0 | Report a Bug | By Email