Re: [Ieprep] proposed charter 5 priority levels
Curtis Villamizar <curtis@occnc.com> Wed, 27 September 2006 01:28 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSOE4-0007QD-3E; Tue, 26 Sep 2006 21:28:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSOE3-0007Q8-2Y for ieprep@ietf.org; Tue, 26 Sep 2006 21:28:39 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSOE1-000178-NN for ieprep@ietf.org; Tue, 26 Sep 2006 21:28:39 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1]) by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id k8R2FI5J006271; Tue, 26 Sep 2006 22:15:19 -0400 (EDT) (envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200609270215.k8R2FI5J006271@workhorse.brookfield.occnc.com>
To: John Rosenberg <jrrosenberg@lucent.com>
Subject: Re: [Ieprep] proposed charter 5 priority levels
In-reply-to: Your message of "Tue, 26 Sep 2006 19:10:49 CDT." <6.2.1.2.0.20060926190508.03463c30@ihmail.ih.lucent.com>
Date: Tue, 26 Sep 2006 22:15:18 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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>
Errors-To: ieprep-bounces@ietf.org
In message <6.2.1.2.0.20060926190508.03463c30@ihmail.ih.lucent.com> John Rosenberg writes: > > At 05:52 PM 9/26/2006, ieprep-request@ietf.org wrote: > > >Date: Tue, 26 Sep 2006 12:56:15 -0400 > >From: Curtis Villamizar <curtis@occnc.com> > > >In message > <OFBAA95066.05652C8C-ON852571F5.004A9C8A-852571F5.004B6690@csc.com> > >Janet P Gunn writes: > >> > >> > >> As RFC 4412 makes perfectly clear, the RPH serves a dual role of signalling > >> priority across an IP network (e.g. from an originating circuit switched > >> access network to a terminating circuit switched access network) as well as > >> signalling priority within the IP network. > >> > >> For each of the namespaces described in RFC 4412, the number of priority > >> values (5 in most cases, 6 in one) is driven by the former role, based on > >> the number of priority values in use, or being considered, in the access > >> network priority scheme. > >> > >> The issue of how many priority levels to differentiate WITHIN the IP > >> network is an issue currently being addressed by vendors and providers. > >> > >> Janet > > > > > >Janet, > > > >You are right, but you may be just focusing on SIP which is one peice > >of the puzzle. > > > >RFC 4412 does not make it perfectly clear whether we need 1 DSCP code > >point, EF, or 5 DSCP code points (IP Prec 0-4?) or 15 DSCP code > >points (the 4 AF classes plus one more AF class. Or is it some > >multiple of 6? This RFC doesn't even mention DSCP. > > > > Let me add my voice and suggest that we're really in need of some mechanism > that allows the application (e.g. MLPP, ETS, whatever) to determine a > "priority level" for a session and indicate to the endpoint that it's > serving what DSCP value that the endpoint should use for its bearer packets. > > It could be a header or parameter in some subset of SIP messages, it could > be an attribute in SDP, it could be something else entirely. I think the > whole question of how many and which DSCP values should be used for some > arbitrary application is a little premature if we don't have a way for the > application to get that value used. > > John Rosenberg The discussion just went full circle. We already have a SIP priority in RFC4412. Use of DSCP is only touched on in RFC4190. Both the SIP priority and DSCP value can be carried in microflow RSVP (draft-briscoe-tsvwg-cl-architecture-03.txt). Which DSCP value seems to be an open issue for now. Discussion seems to favor a new DSCP EF-like value for ETS. Curtis _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep
- Re: [Ieprep] proposed charter 5 priority levels John Rosenberg
- Re: [Ieprep] proposed charter 5 priority levels Curtis Villamizar
- RE: [Ieprep] proposed charter 5 priority levels Ash, Gerald R (Jerry), ALABS
- Re: [Ieprep] proposed charter 5 priority levels Curtis Villamizar
- Re: [Ieprep] proposed charter 5 priority levels John Rosenberg
- Re: [Ieprep] proposed charter 5 priority levels Fred Baker
- Re: [Ieprep] proposed charter 5 priority levels Curtis Villamizar
- Re: [Ieprep] proposed charter 5 priority levels John Rosenberg
- Re: [Ieprep] proposed charter 5 priority levels James M. Polk
- Re: [Ieprep] proposed charter 5 priority levels James M. Polk