IETF Logo Mail Archive

Re: [stir] draft-asveren-stir-p-charge-info

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 28 May 2018 17:55 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56AF12DA22 for <stir@ietfa.amsl.com>; Mon, 28 May 2018 10:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKh5IA_LRzfj for <stir@ietfa.amsl.com>; Mon, 28 May 2018 10:55:32 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FD7D12DA17 for <stir@ietf.org>; Mon, 28 May 2018 10:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1527530130; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=s9YaY3O6Df46rVesECT9Ef1LjwseH8H1atq9T/4vLAg=; b=IV9CJcq9bVwRmioOTNEXQPUyzJiwuKiHZ2HuCsI4pV5M4ut8wal1URGoRVPe0jtM MqflpZHss3NAK/POGjzVXC/3I9mKyahYhtuGQmPQaLUsURXlQGXVv029KlDgq4ph zAXR6jWDVYSZcernkvi9pkiA8Stmw2Ra/vMPGBi+xYY=;
X-AuditID: c1b4fb2d-e68d79c00000136c-a0-5b0c4292ddaa
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 5A.3B.04972.2924C0B5; Mon, 28 May 2018 19:55:30 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.29]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0382.000; Mon, 28 May 2018 19:55:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Asveren, Tolga" <tasveren@rbbn.com>, "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] draft-asveren-stir-p-charge-info
Thread-Index: AQHT5y2kgFuajFQnO0ah0J0LULLxoaRFiU5w
Date: Mon, 28 May 2018 17:55:28 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72F0F1CC@ESESSMB109.ericsson.se>
References: <9D563CDB-86A9-4939-8EC5-6717393C4DBC@shockey.us>
In-Reply-To: <9D563CDB-86A9-4939-8EC5-6717393C4DBC@shockey.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.165]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72F0F1CCESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbFdRXeSE0+0we3FChbL125jsli//Bu7 A5PHkiU/mTz2zJnEGMAUxWWTkpqTWZZapG+XwJXx9lcvS8GC6YwVh76eZWxgnDOZsYuRk0NC wERiXf8K1i5GLg4hgSOMEtcXnGCHcBYzSmy9842ti5GDg03AQqL7nzZIg4iAp0RL7wEmEFsY qHnt/0fMEHFTiZWXLrBA2EYSP77cA7NZBFQlbn49DVbDK+ArseHZR3YQW0jAVmLmxW1gNZwC dhLbu26A1TAKiEl8P7UGbD6zgLjErSfzmSAOFZBYsuc8M4QtKvHy8T9WCFtJYtatjVD1+RJT F22F2iUocXLmE5YJjMKzkIyahaRsFpKyWUBfMgtoSqzfpQ9RoigxpfshO4StIdE6Zy47svgC RvZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIERdHDLb90djKtfOx5iFOBgVOLh/WjNEy3E mlhWXJl7iFGCg1lJhJdLlytaiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/eqj1RQgLpiSWp2amp BalFMFkmDk6pBsaMk5PTmA5+3HW7Inry1Wt5bv9TzR/oCIWrJ3KuYVAVc+gXf3Vpok3Vz3Bf f3tX7eh5pu/3vp36a6nuardVSVsePbj9xP9C+Fzm68xLLI6UPo3mCfl7ZvfPvS8vC05+ekjN O2fa0nvsU39t+Mfrt5Zl4ZL/y/hVVdafdrh8/d3bzRO6zrGnbbh/Q4mlOCPRUIu5qDgRACeC LRqcAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/OVnY6xzjkDZxZFkAX4zidarbuPc>
Subject: Re: [stir] draft-asveren-stir-p-charge-info
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2018 17:55:35 -0000

Hi,

I have some questions regarding this. Some of the questions have also been raised by Keith (or are at least related):


Q1: As the purpose of draft-york-p-charge-info is document existing implementations and usage of the PCI header field, the first question is whether we should define “enhancements” and new usages of the PCI header field?


Q2: You should describe in what kind of environments this is needed.

Q3: As draft-york-p-charge-info is to be published as an Informational RFC, should draft-asveren-stir-p-charge-info also be Informational? A PASSporT extension is “Specification Required”, so I assume an Informational RFC qualifies.


Q4: The text in Section 4.3 says:


   "An entity dropping P-Charge-Info MUST drop the corresponding Identity

   header with "ppt" parameter value of "pci”."

        First, I assume you mean “an entity supporting the pci PASSporT”?

        Second, entities that only support the PCI header field, but not the pci PASSporT, will not remove the corresponding Identity header field. I think you need some text about that.


Q5: The text in section 3 says:


              "If P-Charge-Info header is added or by the…”

              Is there something missing between “or” and “by”?

Regards,

Christer






From: stir <stir-bounces@ietf.org<mailto:stir-bounces@ietf.org>> on behalf of "Asveren, Tolga" <tasveren@rbbn.com<mailto:tasveren@rbbn.com>>
Date: Tuesday, May 8, 2018 at 2:45 PM
To: "stir@ietf.org<mailto:stir@ietf.org>" <stir@ietf.org<mailto:stir@ietf.org>>
Subject: [stir] draft-asveren-stir-p-charge-info

I just submitted draft-asveren-stir-p-charge-info:

https://www.ietf.org/internet-drafts/draft-asveren-stir-p-charge-info-00..txt<https://www.ietf.org/internet-drafts/draft-asveren-stir-p-charge-info-00.txt>


It defines a new claim type for P-Charge-Info.

P-Charge-Info is going through the last steps of becoming a RFC in SIPCore WG and I though it would be a good idea to start working on/kicking off discussions about the corresponding STIR support as it is used to carry sensitive information for billing.

And here is the link for P-Charge-Info draft:

https://tools.ietf.org/html/draft-york-p-charge-info-07


Feedback/ideas/suggestions are appreciated.


Thanks,
Tolga
_______________________________________________ stir mailing list stir@ietf.org<mailto:stir@ietf.org> https://www.ietf.org/mailman/listinfo/stir

v2.23.0 | Report a Bug | By Email