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

Alexander Clemm <alexander.clemm@huawei.com> Tue, 10 April 2018 23:30 UTC

Return-Path: <alexander.clemm@huawei.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 BA28E1205D3 for <netconf@ietfa.amsl.com>; Tue, 10 Apr 2018 16:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MVONhG1S_879 for <netconf@ietfa.amsl.com>; Tue, 10 Apr 2018 16:30:35 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 86E3C12D7F6 for <netconf@ietf.org>; Tue, 10 Apr 2018 16:30:35 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 9C61840674CE8 for <netconf@ietf.org>; Wed, 11 Apr 2018 00:30:31 +0100 (IST)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 11 Apr 2018 00:30:33 +0100
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.168]) by SJCEML701-CHM.china.huawei.com ([169.254.3.93]) with mapi id 14.03.0382.000; Tue, 10 Apr 2018 16:30:27 -0700
From: Alexander Clemm <alexander.clemm@huawei.com>
To: "Eric Voit (evoit)" <evoit@cisco.com>, "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+TPnQAO8QGAAAQoioABU9A9IA==
Date: Tue, 10 Apr 2018 23:30:25 +0000
Message-ID: <644DA50AFA8C314EA9BDDAC83BD38A2E0EAF84F9@sjceml521-mbs.china.huawei.com>
References: <e84a00d0a68f4cf383cce7a5acbcf736@XCH-RTP-013.cisco.com> <e0538564-c9a8-cd5c-ffc2-358a25ee578c@joelhalpern.com> <98db54a0f00f4144b68732a89ebdca6d@XCH-RTP-013.cisco.com>
In-Reply-To: <98db54a0f00f4144b68732a89ebdca6d@XCH-RTP-013.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.217.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/7E6bq8txI12OP37wW3-AGwljZfY>
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, 10 Apr 2018 23:30:38 -0000

So I guess this means option 2 on the slides.  Declare separate features for DSCP and QoS.  Works for me.  
--- Alex

> -----Original Message-----
> From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Eric Voit (evoit)
> Sent: Tuesday, April 03, 2018 3:19 PM
> To: Joel M. Halpern <jmh@joelhalpern.com>
> Cc: netconf@ietf.org
> Subject: Re: [Netconf] IETF 101 SN Question 3: DSCP as its own feature?
> 
> 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?useMonospac
> > > eF
> > > 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
> > >
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf