Subject: Two new DiffServ related drafts

From: "James M. Polk" <[email-masked]>
Date: Tue, 13 Mar 2012 19:21:09 -0500

TSVWG

(as author)

(long email alert)

I've submitted two new DiffServ drafts I'd like the WG to consider. 
These two drafts are intertwined.

The first is an update to RFC 4594 (DiffServ Guidelines) here:
http://www.ietf.org/internet-drafts/draft-polk-tsvwg-rfc4594-update-00.txt

The second is a request for 6 new DSCPs to match what is discussed in 
the 4594-update draft, here:
http://www.ietf.org/internet-drafts/draft-polk-tsvwg-new-dscp-assignments-00.txt

please DON'T FREAK OUT YET!!!!

let me explain...

In short, RFC 4594 set up guidelines for several DSCP markings to 
have different traffic characteristics. These included:

- Network Control
- Telephony
- Telephony Signaling
- Realtime-Interactive
- Multimedia-Conferencing
- Multimedia-Streaming
- Broadcast-Video
- Low-Latency Data
- OAM
- High-Throughput Data
- Low-Priority Data
- Default Forwarding (i.e., Best Effort)

RFC 5865 has since added a new EF PHB called Voice-Admit, which has a 
capacity-admission functional aspect involving per flow signaling 
using a protocol such as RSVP to ensure session awareness through a network.

The new RFC4594-update draft updates a few things, it

- separates Telephony into voice and video traffic
- add a new Hi-Res a/v label

  and builds on analogous treatments for

-Realtime-Interactive
-Multimedia-conferencing
-Broadcast-Video (without the '-Video' part of the label)

  to what Voice-Admit did for 'voice' (i.e., creates a
  capacity-admission marking for each).

The -new-dscp-assignments-00 draft merely creates these 6 new 
codepoints, and points heavily towards the RFC4594-update draft.

Thus, what the RFC4594-update draft ends up with are these classes 
(different than the one above):

- Network Control
- audio (admitted and non-admitted)
- video
- Hi-Res (admitted and non-admitted)
- Realtime-Interactive (admitted and non-admitted)
- Multimedia-Conferencing (admitted and non-admitted)
- Multimedia-Streaming
- Broadcast (admitted and non-admitted)
- Low-Latency Data
- Conversational Signaling (using new DSCP)
- OAM
- High-Throughput Data
- Low-Priority Data
- Default Forwarding (i.e., Best Effort)

The specifics about the unique traffic characteristics and such is 
all in the 4594-update draft - which is ~67 pages, so I go into great 
depth (including what are the expected traffic types to use which 
DSCP based on the requirements for a specific network handling based 
on the traffic characteristics for that application or protocol).

BTW - I envision this new RFC4594-update draft being a standards 
track effort, for reasons I'll discuss in our TSVWG session in Paris.

Comments are welcome

James