Re: [Sip] sip qos

"James M. Polk" <jmpolk@cisco.com> Fri, 03 June 2011 17:21 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F80E07B2 for <sip@ietfa.amsl.com>; Fri, 3 Jun 2011 10:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efMNV5RvTyzD for <sip@ietfa.amsl.com>; Fri, 3 Jun 2011 10:21:26 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id EF8EBE0677 for <sip@ietf.org>; Fri, 3 Jun 2011 10:21:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1123; q=dns/txt; s=iport; t=1307121685; x=1308331285; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=6Qm0TNYIBNlw7Shp4f7ovL9hyUWhlh3u1isR+k4HL5o=; b=DpdmEFPsU+hTfhHIeVbJ2P3mab3mYRgeCXWo1ilbmkUcGf+zN9Rs/BEK vudkuORpafre20uzqkkNd7ma1qKEytjnyu5zZ4vWWElr3ygouN+990sKA m/2X/9EPRTGzIlKD0nlgoIRDR8T0Z3H+35boGyNwp1w9CZBwtFdP7ZEZL Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOYX6U2rRDoI/2dsb2JhbABTpjp3rAedZYYhBIZwkn2GXg
X-IronPort-AV: E=Sophos;i="4.65,315,1304294400"; d="scan'208";a="329648388"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 03 Jun 2011 17:21:05 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p53HL4WJ017385; Fri, 3 Jun 2011 17:21:05 GMT
Message-Id: <201106031721.p53HL4WJ017385@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 03 Jun 2011 12:21:04 -0500
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Hakiri Akram <hakiri_akram@yahoo.fr>, "sip@ietf.org" <sip@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E98E@DC-US1MBEX4.glo bal.avaya.com>
References: <4DE5532B.1050802@yahoo.fr> <CD5674C3CD99574EBA7432465FC13C1B222907E98E@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: Re: [Sip] sip qos
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 17:21:27 -0000

At 11:15 AM 6/3/2011, Worley, Dale R (Dale) wrote:
>________________________________________
>From: sip-bounces@ietf.org [sip-bounces@ietf.org] On Behalf Of 
>Hakiri Akram [hakiri_akram@yahoo.fr]
>
>Did someone have an idea about an implementation of SIP extension for
>QoS support in DiffServ.
>_______________________________________________
>
>There have been discussions from time to time.  I can find 
>draft-veltri-sip-qsip-00.txt from 2001.  There have been other 
>efforts more recently.

now there is draft-polk-mmusic-traffic-class-for-sdp-01.txt - which 
is SDP based - for media line granularity, which SIP cannot do by itself.

James


>Dale
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is essentially closed and only used for finishing old business.
>Use sip-implementors@cs.columbia.edu for questions on how to develop 
>a SIP implementation.
>Use dispatch@ietf.org for new developments on the application of sip.
>Use sipcore@ietf.org for issues related to maintenance of the core 
>SIP specifications.