From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iw0-f171.google.com (mail-iw0-f171.google.com [209.85.214.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id CA09D2003E8 for ; Sat, 11 Jun 2011 05:53:49 -0700 (PDT) Received: by iwn8 with SMTP id 8so4281766iwn.16 for ; Sat, 11 Jun 2011 06:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=lqUjRkUn+1KwS2f3Ax7syJTqHxgIleJ941LfesZaYvQ=; b=WUjSr0+tV+PyMl0+CVpMEomCMU2QEkeMmoXSyH3XNOv0B1s5Nvi/oM7mutSbd2m4mW HfYnMUN33xK/FfcEU+sQyeaL5fsos2IUKgIkGqU98fJ6uMyV6qAVWD/qVL1oNHR95552 5pOTLGtSP08FHiyWc4JF2/KAWk6uyKfmKEyts= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=G6V7Ye6dDRBIL1LUj9BsBaSixwggWBpDrk9HG4GZSqqjnnPvZv1pefQYtZNSab0TGm vD7Pj+V83JEzqWWueErCVCdz383YzAjXWrMr2yqw3vufIzg/hxM2JOSV8cyn7if4q/n2 a4pk8zobZNvzWWr/irlL2vg2uieSgFNTaxE44= MIME-Version: 1.0 Received: by 10.231.68.202 with SMTP id w10mr3518189ibi.63.1307798141837; Sat, 11 Jun 2011 06:15:41 -0700 (PDT) Received: by 10.231.13.76 with HTTP; Sat, 11 Jun 2011 06:15:41 -0700 (PDT) Date: Sat, 11 Jun 2011 07:15:41 -0600 Message-ID: From: Dave Taht To: bloat Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Bloat] Three new diffserv codepoints suggested X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 12:53:50 -0000 Before I go to the trouble of writing up an RFC, I thought perhaps here (and the end-to-end list) would be a good place to discuss some ideas towards adding 3 new codepoints to diffserv, in an enhancement to rfc4594[1] - http://tools.ietf.org/html/rfc4594 I've named them with something of a sense of humor, in a ha-ha only serious manner. They are 'Information, Text', 'Large Bandwidth', and 'mice'[2]. 1) The 'IT' codepoint would be suitable for interactive ssh and textual chat (irc,jabber,etc), and merely codify existing practice that uses the 'immediate' TOS field for this purpose in ssh. The OAM codepoint seems unsuitable for this. 2) The 'LB' codepoint =3D 0x63 is an indicator that as soon as a packet marked in this way arrives at a downstream site, it should be immediately reclassified and shaped to fit the available bandwidth of the downstream site. (a suitable nickname for 'LB' would also be 'Lying Bastard', as there exist many sites that set all the diffserv bits in the hope of getting better service from elsewhere) 3) The 'MICE' codepoint consists of small, infrequent, but system critical packets such as ARP, DHCP, various forms of ICMP needed for ipv6 ND and RA to work, and DNS. Arguably the MICE codepoint could be CS6 - the RFC recomends that NTP be an EF service and says that (in section 4.9 of the standard) that DNS, DHCP, and bootp must be 'best effort' services classes. I will certainly argue that wireless is showing that the latter 3 packet types - and ARP, ND, RA, etc - deserve a class of their own. CS6 could be used to wedge most of these together, except for the elephant in its room, BGP, and the conflation with longer-haul protocols. NTP consistently treated as EF would be nice, too. thoughts? What other unofficial codepoints are in use? Does anyone still care about diffserv marking? is the core all MPLS? The edges are certainly not using anything at the moment. --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://the-edge.blogspot.com 1: it was nice to run across at least two members of this list that authored this RFC, and the idea of a MICE class comes from kathie nichols pounding into my head that the mice are a problem. 2: I was unable to come up with a back-acronym for 'mice'. I got as far as 'majorly important' before getting stuck on the 'c'.