[Ieprep] Diffserv Code Point for Emergency calls

"Reinaldo Penno" <rpenno@juniper.net> Fri, 21 October 2005 14:14 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESxel-0001Ao-VV; Fri, 21 Oct 2005 10:14:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESxel-0001Aj-E7 for ieprep@megatron.ietf.org; Fri, 21 Oct 2005 10:14:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23931 for <ieprep@ietf.org>; Fri, 21 Oct 2005 10:13:52 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESxqu-0002Vr-Ax for ieprep@ietf.org; Fri, 21 Oct 2005 10:26:37 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 21 Oct 2005 15:13:53 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 21 Oct 2005 15:13:52 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 Oct 2005 10:13:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Oct 2005 10:13:50 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
Thread-Topic: Diffserv Code Point for Emergency calls
Thread-Index: AcXUE81JfAMUtBgJRhWBEbYRrNip7wCNa7Ig
From: Reinaldo Penno <rpenno@juniper.net>
To: ieprep@ietf.org
X-OriginalArrivalTime: 21 Oct 2005 14:13:51.0672 (UTC) FILETIME=[A9A00380:01C5D649]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
Subject: [Ieprep] Diffserv Code Point for Emergency calls
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hello,

I understand this might have already been discussed (a lot) on the list
but I would like to voice my feedback.

I read
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
and was somewhat puzzled at section 4.1.2. I understand that the IETF
wants to be conservative in standardizing new DSCP, but it seems to an
emergency call DSCP would be accepted by the community (am I wrong?).

I am talking to customers and facing an implementation dilemma on "how
to convey better than EF treatment in a standardized manner since normal
voice calls already use EF?" Should normal voice calls be demoted to use
AFXY DSCP?

Yes, I know, customers can define their own DSCP, map to a specific
queue in their routers, etc, etc. All this is good. However, the
feedback I am getting is that they would like a standardized DSCP for
emergency. The recent tragedies accentuated the need for such
standardization.

I understand there are several levels of emergency calls, etc but maybe
we could start conservative and define _one_ DSCP for emergency calls?

Thanks,

Reinaldo


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep