IETF Logo Mail Archive

Re: [sipcore] consensus call: draft-roach-sipcore-priority-00: define semantics of values?

Michael Procter <michael@voip.co.uk> Thu, 29 November 2012 10:27 UTC

Return-Path: <michael@voip.co.uk>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0406E21F89DB for <sipcore@ietfa.amsl.com>; Thu, 29 Nov 2012 02:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level:
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
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 nCCE3KHe+w2N for <sipcore@ietfa.amsl.com>; Thu, 29 Nov 2012 02:27:28 -0800 (PST)
Received: from na3sys009aog103.obsmtp.com (na3sys009aog103.obsmtp.com [74.125.149.71]) by ietfa.amsl.com (Postfix) with SMTP id 575E021F89D7 for <sipcore@ietf.org>; Thu, 29 Nov 2012 02:27:28 -0800 (PST)
Received: from mail-gh0-f198.google.com ([209.85.160.198]) (using TLSv1) by na3sys009aob103.postini.com ([74.125.148.12]) with SMTP ID DSNKULc4j/7CuiUGmBe4kJtEyrKaPeYHVoz1@postini.com; Thu, 29 Nov 2012 02:27:28 PST
Received: by mail-gh0-f198.google.com with SMTP id r18so21004708ghr.1 for <sipcore@ietf.org>; Thu, 29 Nov 2012 02:27:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ZostCMZd5h+skUlEhO4kdZjN6t1mbE8iOLHHCQRN324=; b=VMUdLxzUDz8KKi4qsH+ee55VRdT2UGzVzbm7edQ3VdE+NhWKpbiJ0BKSAYuP4Ko8NE eO2dNTYPDN2Gs4K5akakygc2Jfmp4EadzRLN6iBEhgqtGX9Gf8UFb5IP4FwKsEGZDAjX klXPMlvAP39M+6zBLkVGYH/JaJIml22leNujnkahOMPqWpsmIXPWFwE73qkbax5KLrFV gcOk5wZpPNaYTAIZZBievZpnZLNBiI3MudpQPNlnkhXTMGrkS++qYfIlWqK8YTKkcSae BuZm/u01aLoXxuuzycHeVQSc068EPkL/vBPnB3nkwHZX1yOgcvP4+AQbtvNqC/AwWnaB 4tZA==
Received: by 10.58.162.130 with SMTP id ya2mr32645259veb.2.1354184847067; Thu, 29 Nov 2012 02:27:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.58.162.130 with SMTP id ya2mr32645253veb.2.1354184846936; Thu, 29 Nov 2012 02:27:26 -0800 (PST)
Received: by 10.58.244.132 with HTTP; Thu, 29 Nov 2012 02:27:26 -0800 (PST)
In-Reply-To: <50B69304.3060602@alum.mit.edu>
References: <50A160D8.8030602@alum.mit.edu> <50B68A43.8040605@alum.mit.edu> <50B69304.3060602@alum.mit.edu>
Date: Thu, 29 Nov 2012 10:27:26 +0000
Message-ID: <CAPms+wQ2fv3CwVeS5H2pHTNx8kkJqmGBPFoyBc1ZvxLYvtnyjg@mail.gmail.com>
From: Michael Procter <michael@voip.co.uk>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQkLwqza0NQMNDlS2QCvyoWa/CMSZNSoT7m0ZjXeTxGljqKvoWZ6dVch6Ojq6adLHFZJLKwUMO3PFQKGl+xyOfQd4Q1LwNHFr2uYpWMDFQX7RKsERCAKG5G3YPEiLMI6TarGBIQ/tFdt12RZpX5vN/FwoaPVVQ==
Cc: sipcore@ietf.org
Subject: Re: [sipcore] consensus call: draft-roach-sipcore-priority-00: define semantics of values?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 10:27:29 -0000

NO

I'm happy to defer defining the semantics of 'urgent', 'non-urgent'
and 'normal' until not having the semantics defined causes
interoperability problems.  Given the limited impact the priority
header can have on a session, I suspect that the natural meanings of
the tokens are adequate for the time being.

Michael

v2.23.0 | Report a Bug | By Email