IETF Logo Mail Archive

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

Joel Halpern Direct <jmh.direct@joelhalpern.com> Tue, 03 April 2018 22:25 UTC

Return-Path: <jmh.direct@joelhalpern.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 D710D12D887 for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 15:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 N3nuy_UsinCa for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 15:24:59 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 6A2FB12D886 for <netconf@ietf.org>; Tue, 3 Apr 2018 15:24:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 523E7240D94; Tue, 3 Apr 2018 15:24:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1522794291; bh=IrCvKTw+M4ZdBWvdwkMEFapPKzCOmH4bcX2dHLqJ9cs=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=SIfgHwjZy5y6xUWKMK7+v4zJQeu4YRayYrumhRGqADlbzrYqZ2nyS7j2Xc9zsKsfp cUpoYyTsHtul8FczjKln24IUiFu/rVILc+8UWr3p/raMS9Vt0hiBIq+6POuWmS4K7n 9fwr1LbLAMopSM/EDo9iaZd5yIb70tP+fyoStwdc=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id C2302240452; Tue, 3 Apr 2018 15:24:50 -0700 (PDT)
To: "Eric Voit (evoit)" <evoit@cisco.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
References: <e84a00d0a68f4cf383cce7a5acbcf736@XCH-RTP-013.cisco.com> <e0538564-c9a8-cd5c-ffc2-358a25ee578c@joelhalpern.com> <98db54a0f00f4144b68732a89ebdca6d@XCH-RTP-013.cisco.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <c0d195ae-8820-08cd-7ca9-01e252e72e2f@joelhalpern.com>
Date: Tue, 03 Apr 2018 18:24:49 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <98db54a0f00f4144b68732a89ebdca6d@XCH-RTP-013.cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/tX2Z6whq6iOSSv81b8oTfDiEFTo>
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:25:01 -0000

Leaving it as DSCP has the advantage that it becomes there problem to 
come up with another name for it.

Yours,
Joel

On 4/3/18 6:19 PM, Eric Voit (evoit) wrote:
> 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