[sipcore] history and privacy (draft-barnes-sipcore-rfc4244bis-01)

OKUMURA Shinji <shin@softfront.co.jp> Fri, 10 July 2009 06:43 UTC

Return-Path: <shin@softfront.co.jp>
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 6A4C83A6D77 for <sipcore@core3.amsl.com>; Thu, 9 Jul 2009 23:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.64
X-Spam-Level: ****
X-Spam-Status: No, score=4.64 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_221=2.222, UNPARSEABLE_RELAY=0.001]
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 I4R3VP589xtl for <sipcore@core3.amsl.com>; Thu, 9 Jul 2009 23:43:14 -0700 (PDT)
Received: from mail2.softfront.co.jp (rt1.softfront.co.jp [221.186.247.166]) by core3.amsl.com (Postfix) with SMTP id 5E86C3A6CEC for <sipcore@ietf.org>; Thu, 9 Jul 2009 23:43:14 -0700 (PDT)
Received: from softfront.co.jp by mail2.softfront.co.jp id AA03332 ; 10 Jul 2009 15:43:36 +0900
From: OKUMURA Shinji <shin@softfront.co.jp>
To: sipcore@ietf.org
Date: Fri, 10 Jul 2009 15:43:35 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: HidemaruMail 5.18 (WinNT,501)
Message-Id: <7CA0129BFB19Ashin@softfront.co.jp>
Subject: [sipcore] history and privacy (draft-barnes-sipcore-rfc4244bis-01)
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: Fri, 10 Jul 2009 06:43:15 -0000

Hi,

I have some questions.

1. critical
 When proxy want to insert a hi-entry with "history" and "critical",
 can these values be encoded in hi-target-to-uri ?
 "Privacy=history;critical" ?

2. Privacy in the response
 A request include a Privacy header with "history" and hi-entries
 without Privacy headers, the last proxy anonymize all hi-entries and
 remove a Privacy header. UAS returns a response with all anonymized
 hi-entries and no Privacy header. Should the last proxy( privacy
 service) insert a "Privacy: history" ?

3. History-Info in the response
 Should privacy service restore values for History-Info headers that
 anonymized by itself ?

Regards,
Shinji