RE: [Diffserv-interest] Re: draft-baker-diffserv-basic-classes-01 .txt

"Jozef Babiarz" <babiarz@nortelnetworks.com> Sun, 02 November 2003 21:54 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26629 for <diffserv-interest-archive@odin.ietf.org>; Sun, 2 Nov 2003 16:54:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGQAe-0006Ty-1W for diffserv-interest-archive@odin.ietf.org; Sun, 02 Nov 2003 16:54:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA2Ls463024914 for diffserv-interest-archive@odin.ietf.org; Sun, 2 Nov 2003 16:54:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGQAb-0006TN-9j; Sun, 02 Nov 2003 16:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGQ9j-0006SU-7m for diffserv-interest@optimus.ietf.org; Sun, 02 Nov 2003 16:53:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26617 for <diffserv-interest@ietf.org>; Sun, 2 Nov 2003 16:52:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGQ9h-0003DA-00 for diffserv-interest@ietf.org; Sun, 02 Nov 2003 16:53:05 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AGQ9g-0003C5-00 for diffserv-interest@ietf.org; Sun, 02 Nov 2003 16:53:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA2LqJM04696; Sun, 2 Nov 2003 16:52:19 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <VRTP1R46>; Sun, 2 Nov 2003 16:52:19 -0500
Message-ID: <E380A44D523BD5118EAE0002A52CE5C40944D19C@zcard0k8.ca.nortel.com>
From: "Jozef Babiarz" <babiarz@nortelnetworks.com>
To: Brian E Carpenter <brc@zurich.ibm.com>, "John H. Shuler" <johnshuler@mac.com>
Cc: diffserv-interest@ietf.org
Subject: RE: [Diffserv-interest] Re: draft-baker-diffserv-basic-classes-01 .txt
Date: Sun, 2 Nov 2003 16:52:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A18B.95C970DE"
Sender: diffserv-interest-admin@ietf.org
Errors-To: diffserv-interest-admin@ietf.org
X-BeenThere: diffserv-interest@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=unsubscribe>
List-Id: Differentiated services general discussion <diffserv-interest.ietf.org>
List-Post: <mailto:diffserv-interest@ietf.org>
List-Help: <mailto:diffserv-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=subscribe>

Brian E Carpenter wrote:
John, I guess your comment refers to the draft so I changed the subject.

If you want to be sure the authors see your comments, you might want to
write to them directly. My reactions inserted below.

   Brian

"John H. Shuler" wrote:
> 
> Why make a distinction between "Standard Service Class" and "Low Priority
> Data"?

There is a kitchen sink aspect to this draft that worries me. Rather than
starting simple, with three or four generic service classes, the authors
have chosen to present the union of a number of diffserv deployment models.
I think that risks confusing operators by giving them too much complexity
to choose from.

[[Joe] The draft tries to address the service differentiation that is needed
in carriers and enterprise networks including access networks. I agree that
network administrators both in carrier and enterprise should start off with
only the service differentiation level (service classes) that are required
for their business. Let me provide some examples that I worked on so that
you can understand why we have defined the number of service classes.

Carriers wanted to use IP technology for provide telephony service, plus
provide IP VPN service with CIR as well basic Internet connectivity service.
This scenario can be address by configuring the network using the following
service classes define in the draft.
- Standard service class for Internet connectivity
- High Throughput Data service class of IP VPN and collection of network
data for billing
- Telephony service class for VoIP and signaling between voice gateways
- Network Control service classes for routing, etc.

This simple example used four of the defined service classes.

A different operator is deploying the services listed above plus new
multimedia IP services like desktop video conferencing to go along with
telephony, instant massaging plus other "workflow" applications.
This operator needs: 
- Standard 
- High Throughput Data 
- Low Latency Data 
- Multimedia Conferencing 
- Telephony 
- Network Control

Another operator has plans to offer broadcast TV service, pay-per-view,
telephony, two different SLAs for IP VPN services and basic Internet
connectivity. They will need:
- Standard 
- High Throughput Data 
- Low Latency Data 
- Multimedia Streaming 
- Telephony 
- Network Control

A large enterprise is currently configuring their network to support the
flowing service classes (using the drafts terminology). Most location will
have a subset of services available with migration to network wide service
transparency in the future. 
- Standard 
- High Throughput Data 
- Low Latency Data 
- Multimedia Streaming 
- Multimedia Conferencing
- Telephony 
- Network Control
- Administration

I can go through more scenarios that I have come across over the years. 
I agree that two or three user service classes is what many operators start
off with, however they are not always the same three and they always like to
know how they can evolve in the future.]

Regards, Joe.
Jozef Babiarz
QoS and Network Architecture
Nortel Networks
email: babiarz@nortelnetworks.com
Tel: (613) 763-6098 ESN:393-6098