Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 26 June 2015 06:37 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2DD1B3401 for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 23:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 WHjbZGGURw2u for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 23:37:17 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531C51B3400 for <tsvwg@ietf.org>; Thu, 25 Jun 2015 23:37:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2C0AEA1; Fri, 26 Jun 2015 08:37:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435300635; bh=+DdOC2vXh8bU+D7/l6KnXb8SwFM5OPfzpOSiF52pgog=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=QV0Pryr1Ew66+4JBotif7Ea0OSnn0/T1T/CObchHrFvUhC7hBFZtfVxCtT/LxI1pC h7eRNOnv4ozHTzHdLbDkscdfb6PtfJgWLwOWJfUvkxigKjELI0xP7816zqr2PtyWrT APV3ZOqWQTVpvNgmK8q4ep3PNddqG41tyJnubHKo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 22BD29F; Fri, 26 Jun 2015 08:37:15 +0200 (CEST)
Date: Fri, 26 Jun 2015 08:37:15 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: gorry@erg.abdn.ac.uk
In-Reply-To: <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk>
Message-ID: <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/b5Nceh5AzEl4eOBsQ_LTyq5wioE>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2015 06:37:19 -0000

On Wed, 17 Jun 2015, gorry@erg.abdn.ac.uk wrote:

> As co-chair: I think the short separate standards-track draft would then 
> be the appropriate thing to do. This could be done quickly ***IF*** we 
> get a firm consensus from the community to do this.

If you want to reach out to the "community", I would suggest to for 
instance reach out to the nanog (https://www.nanog.org/list) mailing list 
and ask for feedback there. You'd be more likely to find people who will 
actually implement this there, than on this mailing list. You'd get a much 
wider audience who will tell you if this is deployable in the real world 
with real world equipment and real world configuration, and asking real 
world operators if this is something they could imagine implementing.

Those are the people who will decide what DSCP bit bleaching is done at 
peering borders and customer connections for instance, which is key to 
getting this deployed.

It would also be interesting to hear from equipment vendors, especially 
ones that make BNGs, which kind of bleaching functionality is available in 
existing equipment. Is it possible to just bleach precedence bits on most 
platforms? I'd imagine it is, but it would be interesting to know.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se