IETF Logo Mail Archive

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

"Asveren, Tolga" <tasveren@rbbn.com> Wed, 09 May 2018 06:28 UTC

Return-Path: <tasveren@rbbn.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 C287612D87A for <stir@ietfa.amsl.com>; Tue, 8 May 2018 23:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level:
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=sonusnetworks.onmicrosoft.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 kSiGmJ9jF8x4 for <stir@ietfa.amsl.com>; Tue, 8 May 2018 23:28:11 -0700 (PDT)
Received: from us-smtp-delivery-181.mimecast.com (us-smtp-delivery-181.mimecast.com [216.205.24.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9093F126DFB for <stir@ietf.org>; Tue, 8 May 2018 23:28:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-rbbn-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=x9jrrKFUNut/9IOwZG8nY2nmFrdOAj5P8Q4YKbbQPWM=; b=IKRt5iNLN5+A8PGTJisP192MuCYtZm7gnLHNc+9xcXcgVQY0cKFRQWn42s5CijXkD5LkjFPqzREiq0IW3wUeeEQQXD/24/OhVAIe/eYkNTRDn17ogPzaF/6FbwqJLWiFxyhWstvVR1SdX3REGfgArXKNzzy0d7Q7xsdu6+3dJBM=
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01lp0181.outbound.protection.outlook.com [216.32.180.181]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-151-6dSMP41iMXylMQ2P2u8D7w-1; Wed, 09 May 2018 02:28:08 -0400
Received: from CY4PR03MB3160.namprd03.prod.outlook.com (10.171.245.165) by CY4PR03MB3365.namprd03.prod.outlook.com (10.171.244.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 9 May 2018 06:28:06 +0000
Received: from CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::1ce6:570f:804d:b113]) by CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::1ce6:570f:804d:b113%13]) with mapi id 15.20.0735.019; Wed, 9 May 2018 06:28:06 +0000
From: "Asveren, Tolga" <tasveren@rbbn.com>
To: Richard Shockey <richard@shockey.us>, "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] draft-asveren-stir-p-charge-info
Thread-Index: AQHT5y2lQ/Jlv4a9pUCLwxHhKMtu56Qm7VKQ
Date: Wed, 09 May 2018 06:28:06 +0000
Message-ID: <CY4PR03MB3160818BD1D609F2AA7456A5A5990@CY4PR03MB3160.namprd03.prod.outlook.com>
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: [73.29.251.142]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR03MB3365; 7:4eH+Avg9jT9e5ZIfRMV7N1c99vKRzYpmC+yp2fBoYp9xGAzspSURJcGioGe86duFfSEWSwnGQ/qBMZsmfyR9U73ZXx76MflXOJIDe/ZpZhm8hbwBei5MlRPA/r9dlBIfrDOsBDtVaGYw0i++R/IMGEdD6LqMXvw8indVDxstbnX+6SbzSSrPx74ZZe9WE8cMY+xNCO8anzWjr6JtDvvg3pNy9lopHv/qpM6ZfFOupOr09+SSls6YAElcG+GnQrq/; 20:VORNy6xgM8FbbN8b9SGabeh7h+zwHZDHcPx/t+oInrWvlzgmABkhgO3p036zxRuIe5CoR7xNtttLrx490P8/mQ6XuWz+iwVimIvlJlQG3WhjthjCxESKebY4Rotz5YO5Or2MRlxdUoaIyXhtloqmeazsURIq1JUbJ5p1RYhRH3Q=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7153060)(7193020); SRVR:CY4PR03MB3365;
x-ms-traffictypediagnostic: CY4PR03MB3365:
x-microsoft-antispam-prvs: <CY4PR03MB3365066D977E157F4A752076A5990@CY4PR03MB3365.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155)(5213294742642);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:CY4PR03MB3365; BCL:0; PCL:0; RULEID:; SRVR:CY4PR03MB3365;
x-forefront-prvs: 0667289FF8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(346002)(396003)(39380400002)(39860400002)(199004)(189003)(51914003)(105586002)(6506007)(229853002)(59450400001)(106356001)(102836004)(6116002)(186003)(9686003)(26005)(66066001)(3280700002)(53936002)(3660700001)(54896002)(236005)(6306002)(55016002)(5250100002)(2501003)(110136005)(6436002)(3846002)(790700001)(68736007)(53546011)(316002)(97736004)(606006)(1680700002)(45080400002)(53386004)(478600001)(6246003)(74316002)(486006)(33656002)(966005)(2900100001)(5660300001)(25786009)(99286004)(76176011)(2906002)(81156014)(446003)(11346002)(81166006)(8676002)(14454004)(476003)(7696005)(8936002)(7736002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR03MB3365; H:CY4PR03MB3160.namprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-microsoft-antispam-message-info: 3QJri49aOv4QyKHoPYUU1CTlv4r3IViJ2B2Riq0xUkVLU7aeka5TmnKQ3Ag598MJux3lUDQ+I9kEehLAEW0L7Z70Wh3k4YcCoY3MFJZIM8h0S/ivxD51mArGSMWqb1Et80ir2+dlipZ4+qE4q/KVtgcXyZpRsRwXDc5at6wLGT94zWHoKQJKqnZLhSdQjrcZ
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: cd1b214c-527b-425e-2a4c-08d5b576066c
X-OriginatorOrg: rbbn.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cd1b214c-527b-425e-2a4c-08d5b576066c
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2018 06:28:06.0376 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR03MB3365
X-MC-Unique: 6dSMP41iMXylMQ2P2u8D7w-1
Content-Type: multipart/alternative; boundary="_000_CY4PR03MB3160818BD1D609F2AA7456A5A5990CY4PR03MB3160namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/-_KSiKL91G190FlNupKyJl837Ug>
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: Wed, 09 May 2018 06:28:16 -0000

Thanks for the questions.

i- draft-york-p-charge-info will be sent for IESG processing soon. There are no pending technical/nit issues. If I may say, the reason for the delay is the “usual IETF backlog”. This draft is used in practice, considered needed by various organizations, e.g. FCC, TCC (JJ.90 30).

ii- P-Charge-Info conveys sensitive information about billing so its assertion is critical to avoid fraud therefor the need for a PASSporT extension. Several operators I had conversed as part of commercial projects were seeing this as a “natural extension” for P-Charge-Info. Do you think it shouldn’t be asserted? If so, why?

Thanks,
Tolga

From: stir <stir-bounces@ietf.org> On Behalf Of Richard Shockey
Sent: Tuesday, May 8, 2018 8:35 PM
To: Asveren, Tolga <tasveren@rbbn.com>; stir@ietf.org
Subject: Re: [stir] draft-asveren-stir-p-charge-info

________________________________
NOTICE: This email was received from an EXTERNAL sender
________________________________


Who wants this?   What is the use case or business case for this as a PASSporT?

I’m actually curious?

It has certainly taken way to long for Dan York’s draft to float through the convoluted IETF process but why?

—

Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us<http://www.shockey.us>

www.sipforum.org<http://www.sipforum.org>

richard<at>shockey.us

Skype-Linkedin-Facebook –Twitter  rshockey101

PSTN +1 703-593-2683

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