[sipcore] draft-barnes-sipcore-rfc4244bis - privacy syntax
"Dale Worley" <dworley@nortel.com> Wed, 08 July 2009 18:31 UTC
Return-Path: <dworley@nortel.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5EF63A6BF8 for <sipcore@core3.amsl.com>; Wed, 8 Jul 2009 11:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.694
X-Spam-Level:
X-Spam-Status: No, score=-6.694 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXp5egF0DhLp for <sipcore@core3.amsl.com>; Wed, 8 Jul 2009 11:31:58 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id E5A823A6AAD for <sipcore@ietf.org>; Wed, 8 Jul 2009 11:31:57 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n68IWLX06430 for <sipcore@ietf.org>; Wed, 8 Jul 2009 18:32:21 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 8 Jul 2009 14:32:08 -0400
From: Dale Worley <dworley@nortel.com>
To: Mary Barnes <mary.barnes@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1EDE5C07@zrc2hxm0.corp.nortel.com>
References: <1246996560.5962.37.camel@victoria-pingtel-com.us.nortel.com> <1ECE0EB50388174790F9694F77522CCF1EDE5C07@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 08 Jul 2009 14:32:08 -0400
Message-Id: <1247077928.3712.26.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jul 2009 18:32:08.0751 (UTC) FILETIME=[66BF9BF0:01C9FFFA]
Cc: SIPCORE <sipcore@ietf.org>
Subject: [sipcore] draft-barnes-sipcore-rfc4244bis - privacy syntax
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 08 Jul 2009 18:31:58 -0000
I'm curious why the privacy attribute of an hi-targeted-to-uri is specified by adding a header-parameter to the URI, rather than being given as a field-parameter. That is, an example of the current syntax is: <sip:UserB@example.com?Privacy=history&Reason=SIP%3Bcause%3D486>;index=1.2;mapped where I would expect: <sip:UserB@example.com?Reason=SIP%3Bcause%3D486>;index=1.2;mapped;privacy=history This privacy value is an annotation of the URI, whereas the current syntax incorporates it *into* the URI. And indeed, to reconstitute the actual historical request-URI, one has to remove the Privacy header from the URI part of the name-addr, that is, the stuff inside <...>. (Although given that the historical URI can have had no header parameters (due its use as a request-URI), that processing step is not ambiguous.) In addition, the values of the 4244 Privacy header do not have exactly the same semantics as the same tokens used as values of the Privacy header. I guess that for compatibility with RFC 4244, we have to continue to record privacy and reason information in the URI this way, but I'm curious what the motivation was for this rather unusual way to represent this information. Dale
- [sipcore] draft-barnes-sipcore-rfc4244bis - hi-ta… Dale Worley
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - h… Mary Barnes
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - h… Dale Worley
- [sipcore] draft-barnes-sipcore-rfc4244bis - priva… Dale Worley
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Mary Barnes
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Francois Audet
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Dale Worley
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Mary Barnes
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Francois Audet
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Hadriel Kaplan
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Hadriel Kaplan
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Hans Erik van Elburg
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Paul Kyzivat
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Francois Audet
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… OKUMURA Shinji
- Re: [sipcore] draft-barnes-sipcore-rfc4244bis - p… Dale Worley