Re: [Ieprep] Diffserv Code Point for Emergency calls

Fred Baker <fred@cisco.com> Wed, 26 October 2005 20:41 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUs5R-0007O0-1W; Wed, 26 Oct 2005 16:41:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUs5N-0007MW-OM for ieprep@megatron.ietf.org; Wed, 26 Oct 2005 16:41:27 -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 QAA11595 for <ieprep@ietf.org>; Wed, 26 Oct 2005 16:41:09 -0400 (EDT)
Received: from 130.155.216.216.transedge.com ([216.216.155.130] helo=vbn.0053136.lodgenet.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUsIZ-0007zE-HD for ieprep@ietf.org; Wed, 26 Oct 2005 16:55:05 -0400
Received: from [10.2.2.144] (helo=[10.2.2.144]) by vbn.0053136.lodgenet.net with esmtp (Exim 3.34 #1) id 1EUs58-0002oH-00; Wed, 26 Oct 2005 16:41:10 -0400
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <94255790-FA0D-4D0A-823B-F6F7DFACD98C@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
Date: Wed, 26 Oct 2005 14:59:05 -0400
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: 7bit
Cc: "James M. Polk" <jmpolk@cisco.com>, ken carlberg <carlberg@g11.org.uk>, 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

 From my perspective, the question in the data plane is not whether  
the packet is part of an emergency session, but whether it is  
authorized to use the bandwidth. Emergency authorization is a control  
plane problem.

That is why I have suggested authorization of users to use the EF  
code point during CAC.

On Oct 22, 2005, at 8:45 AM, Reinaldo Penno wrote:

> Your point is well taken James.
>
> I guess the risk is no different from what we face nowadays with doom
> packets marked with EF DSCP. The solution as well is no different from
> what we have today to deal with those packets. Usually  
> independently of
> the DSCP an endpoint might put in a packet, the edge router perform
> classification and if necessary remarks the packet with whatever  
> DSCP it
> should have.
>
> Therefore, if we just continue with just EF for normal and emergency
> voice calls, the risk is the same, the drawback that I see is that we
> cannot prioritize emergency over normal calls.
>
> So, in general an edge device that can perform SIP parsing and mark
> emergency calls with the emergency DSCP and others with EF DSCP.
> Alternatively, in a decomposed gateway scenario the SIP Proxy can let
> the router know that a certain call is an emergency and that it should
> be marked differently.
>
> Regards,
>
> Reinaldo
>
>
>
>> -----Original Message-----
>> From: James M. Polk [mailto:jmpolk@cisco.com]
>> Sent: Friday, October 21, 2005 11:02 PM
>> To: Reinaldo Penno
>> Cc: ken carlberg; ieprep@ietf.org
>> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>>
>> Reinaldo
>>
>> Adding fuel to a discussion that has churned on many lists over the
>>
> last
>
>> several years, I'd really want to understand the threat anaylsis
>>
> observed
>
>> by such a proposal (for a emergency DSCP) to ensure it could not be
>>
> used
>
>> for a fairly trivial to generate DDOS on the network - even all the
>>
> way to
>
>> the PSAP, or just used by neighbors wanting the very best throughput
>>
> for
>
>> their game of Doom.
>>
>> At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
>>
>>> 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
>>>
>>
>>
>> cheers,
>> James
>>
>>                                  *******************
>>                  Truth is not to be argued... it is to be presented.
>>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>


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