[Bloat] Three new diffserv codepoints suggested

[Dave Taht]

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 = 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.

-- 
Dave Täht
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'.