IETF Logo Mail Archive

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

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 03 April 2018 22:19 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 A116212D883 for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 15:19:08 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 Pv_WzI2WrQdS for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 15:19:06 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFB6C126C2F for <netconf@ietf.org>; Tue, 3 Apr 2018 15:19:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1719; q=dns/txt; s=iport; t=1522793946; x=1524003546; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=umHbSIIhHpdFtY1LL9f8Rg6fb3c2mr5Y2NfJbq906e8=; b=iN2GhArJb63I2mrKhMxjC+UscT7v0/7ZCEUHsX4Gk3PavHrv1QFvorRA n0j04+5GviZedXtNRZwtg6c+gYt0Fb9+ICzFbUgm5FjS/6jKzBDANYyAa 6w+MEDHLRHhl5Wz8pGr+wKgRsalKBFlxP9EiEMu/UXl9SWTNnv7VBbKU0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYAgAk/cNa/5RdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYMXK2FvKAqYWoF0gQ+SVYF6CxgLhBVLAoRCITUXAQIBAQEBAQECayiFIgEBAQECAQEBbAsFCwIBCBguJwslAQEEDgUIhH0ID694iESCIAWHYoFUP4EMgwSBQYFQAQECGIEfhXcCi3IzixYIAoVQiFWMP4kVhkECERMBgSQBHQE2gVJwFTqCQ4MxAQeNFG8BjSiBFwEB
X-IronPort-AV: E=Sophos;i="5.48,403,1517875200"; d="scan'208";a="93189228"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Apr 2018 22:19:06 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w33MJ53W030817 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Apr 2018 22:19:05 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 3 Apr 2018 18:19:05 -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; Tue, 3 Apr 2018 18:19:05 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] IETF 101 SN Question 3: DSCP as its own feature?
Thread-Index: AdPLiA0Fz07Ou+3RS7mSGBKIu+TPnQAIp62AAARJ+WA=
Date: Tue, 03 Apr 2018 22:19:05 +0000
Message-ID: <98db54a0f00f4144b68732a89ebdca6d@XCH-RTP-013.cisco.com>
References: <e84a00d0a68f4cf383cce7a5acbcf736@XCH-RTP-013.cisco.com> <e0538564-c9a8-cd5c-ffc2-358a25ee578c@joelhalpern.com>
In-Reply-To: <e0538564-c9a8-cd5c-ffc2-358a25ee578c@joelhalpern.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: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Kwj1Dtz47YVl0Si35-KGoHzzdD8>
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: Tue, 03 Apr 2018 22:19:09 -0000

Hi Joel,

I certainly have no issues with leaving it as dscp, and seeing if the IESG would rather it be renamed.

Eric

> DSCP and Priority are two different (related but distinct concepts).
> The field should be named according to what you want to manipulate.  The
> current text seems to have a meaning closer to DSCP than to Priority.
> 
> Yours,
> Joel
> 
> On 4/3/18 4:12 PM, Eric Voit (evoit) wrote:
> > 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?useMonospaceF
> > ont=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
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> >

v2.23.0 | Report a Bug | By Email