Re: [Ieprep] Diffserv Code Point for Emergency calls

ken carlberg <carlberg@g11.org.uk> Fri, 21 October 2005 14:58 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESyLn-0004gW-U6; Fri, 21 Oct 2005 10:58:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESyLm-0004g8-8b for ieprep@megatron.ietf.org; Fri, 21 Oct 2005 10:58:30 -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 KAA27255 for <ieprep@ietf.org>; Fri, 21 Oct 2005 10:58:18 -0400 (EDT)
Received: from athena.hosts.co.uk ([212.84.175.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESyXv-0004TF-On for ieprep@ietf.org; Fri, 21 Oct 2005 11:11:04 -0400
Received: from [69.138.71.61] (helo=[192.168.1.100]) by athena.hosts.co.uk with esmtpa (Exim 4.52) id 1ESyLL-0000pE-WF; Fri, 21 Oct 2005 15:58:07 +0100
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A89EB72D-7A4E-48D1-886D-DB2964B29453@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
Date: Fri, 21 Oct 2005 10:57:58 -0400
To: "Reinaldo Penno" <rpenno@juniper.net>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 2.0 (++)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
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 Reinaldo,

> 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?).

well, from my own take, I would say that the "community" is not  
against an emergency call DSCP per se, but rather awaits specific  
proposals with a cautious mindset.  Recall from that section 4.1.2  
that there is a need to define a behavior in addition to identifying  
a code point.  So if you want a code point of 1 or more bits for  
"emergency", what would be its defined forwarding behavior?

one such proposal, primarily aimed at MLPP, is called Multi-Level  
Expedited Forwarding (MLEF) and can be found at:
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman- 
tsvwg-mlefphb-03.txt

I would also suggest reading a counter proposal that avoids defining  
a new DSCP:
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg- 
mlpp-that-works-02.txt
you can dig around the TSVWG archives over the past 2 months for some  
comments on the draft.

-ken


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