[sipcore] Feature-Caps - Terminology

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 03 November 2011 12:50 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D560311E80AC for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 05:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.3
X-Spam-Status: No, score=-6.3 tagged_above=-999 required=5 tests=[AWL=0.299, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7izgEF1dNpt2 for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 05:50:24 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net []) by ietfa.amsl.com (Postfix) with ESMTP id 263CF11E80D2 for <sipcore@ietf.org>; Thu, 3 Nov 2011 05:50:23 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-bf-4eb28e0e4510
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain []) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id EC.47.13753.E0E82BE4; Thu, 3 Nov 2011 13:50:22 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([]) by esessmw0237.eemea.ericsson.se ([]) with mapi; Thu, 3 Nov 2011 13:50:21 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "<sipcore@ietf.org>" <sipcore@ietf.org>
Date: Thu, 3 Nov 2011 13:50:20 +0100
Thread-Topic: Feature-Caps - Terminology
Thread-Index: AQHMmZdcQYx9iM69S0ia7qNL9RWaF5WbDHUg
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852235962759@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A058522357173A0@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058522357173A0@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [sipcore] Feature-Caps - Terminology
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, 03 Nov 2011 12:50:25 -0000


Based on the terminology comments, I suggest some modified/new text for Section 1 and Section 3 (still working on section 4).

   "1.  Introduction

   The Session Initiation Protocol (SIP) "Caller Preferences" extension,
   defined in RFC 3840 [RFC3840], provides a mechanism that allows a SIP
   message to convey information relating to the originator's features
   and capabilities, using the Contact header field.
   This document defines a new SIP header field, Feature-Caps, that can
   be used by SIP entities to indicate support of features and capabilities,
   in cases where the Contact header field contains a URI that does not 
   represent the SIP entity that wants to indicate support of its features and 
   capabilities. Such cases are:

	- The SIP entity acts as a SIP proxy.
	- The SIP entity acts as a SIP registrar.
	- The SIP entity acts as a B2BUA, where the Contact header field URI 
	represents another SIP entity."

Section 3:

The proxy definition text is removed.