IETF Logo Mail Archive

Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

"Asveren, Tolga" <tasveren@sonusnet.com> Fri, 21 July 2017 11:19 UTC

Return-Path: <tasveren@sonusnet.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31E1131467 for <sipcore@ietfa.amsl.com>; Fri, 21 Jul 2017 04:19:55 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message 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 aQ4PwYQ6TN11 for <sipcore@ietfa.amsl.com>; Fri, 21 Jul 2017 04:19:54 -0700 (PDT)
Received: from us-smtp-delivery-126.mimecast.com (us-smtp-delivery-126.mimecast.com [216.205.24.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09A7B129B7F for <sipcore@ietf.org>; Fri, 21 Jul 2017 04:19:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-sonusnet-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=T7BISDU4BaG9USfmFBDkUGzCzGFQs5UZF5j8Yl5wSro=; b=iHRNEMr/npJ9gu9nrHWX8UrdsUWwq/aWWtr1Tg7xI2BCD564iXEFkj1szIB7O9UhmWqHV/BUe/e6hUsw8EdFkQxNlxn8bZuYtspweAzrtevf2DZgG157fh1S0FIAL0rPZF15zVka7LDIOC6mBFcw+ruOgo+9lCDk2SExJwC+P98=
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02lp0047.outbound.protection.outlook.com [207.46.163.47]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-17-snfNUqKoOHaF5TfF3peX4A-1; Fri, 21 Jul 2017 07:19:49 -0400
Received: from SN2PR03MB2350.namprd03.prod.outlook.com (10.166.210.141) by SN2PR03MB077.namprd03.prod.outlook.com (10.255.175.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.13; Fri, 21 Jul 2017 11:19:46 +0000
Received: from SN2PR03MB2350.namprd03.prod.outlook.com ([10.166.210.141]) by SN2PR03MB2350.namprd03.prod.outlook.com ([10.166.210.141]) with mapi id 15.01.1282.016; Fri, 21 Jul 2017 11:19:46 +0000
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities
Thread-Index: AQHS//8f86lEHhh9VUKR5rSbwxo4z6Ja0ofAgABzoYCAAC1loIAAAo2AgAAGWUCAACJWAIABaRBwgAASotCAAM0KkA==
Date: Fri, 21 Jul 2017 11:19:46 +0000
Message-ID: <SN2PR03MB2350FB4E3C9CF42314A22860B2A40@SN2PR03MB2350.namprd03.prod.outlook.com>
References: <CY1PR09MB07602078727954F586DCBDD3EAA10@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB235023C01D8658B9B25A3577B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <75f4364f-a10d-18eb-f547-8bdb17acef78@alum.mit.edu> <SN2PR03MB23509530AE70988D06A97191B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <CY1PR09MB07606A3F6AD98F8CB7235FD5EAA60@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB2350B8FDFC86CC4DDA03F013B2A60@SN2PR03MB2350.namprd03.prod.outlook.com> <CY1PR09MB07602F832CB319979A6FDB29EAA60@CY1PR09MB0760.namprd09.prod.outlook.com> <SN2PR03MB2350515B6772F8676C96678FB2A70@SN2PR03MB2350.namprd03.prod.outlook.com> <CY1PR09MB076067F5F63692A40F364BB5EAA70@CY1PR09MB0760.namprd09.prod.outlook.com>
In-Reply-To: <CY1PR09MB076067F5F63692A40F364BB5EAA70@CY1PR09MB0760.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [73.29.18.75]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN2PR03MB077; 20:0/jcTttD5D8zTTvNtG52591WIG6UjHhxWNfybitA5pAmesqxPw5HHsYOiLWdUeVhFiYWvRUtTEZVKsnbMoPdyuQHt4PSOjNaloEt9dr4t9HLVUny4bs5Sop15kEQwBh81NtA9yvMeigZfS4GJW/bvVjB8fcip8EuYma8nzTVGvA=
x-ms-office365-filtering-correlation-id: dcc0c930-4570-4269-6ca5-08d4d02a64ad
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:SN2PR03MB077;
x-ms-traffictypediagnostic: SN2PR03MB077:
x-exchange-antispam-report-test: UriScan:;
x-microsoft-antispam-prvs: <SN2PR03MB0771EA44481D146CDCA25B0B2A40@SN2PR03MB077.namprd03.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(6041248)(20161123564025)(20161123562025)(20161123560025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN2PR03MB077; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN2PR03MB077;
x-forefront-prvs: 0375972289
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(39410400002)(39400400002)(39830400002)(13464003)(199003)(377454003)(189002)(3660700001)(2950100002)(101416001)(68736007)(2171002)(93886004)(54356999)(8936002)(105586002)(74316002)(102836003)(3846002)(2906002)(6246003)(6116002)(229853002)(50986999)(38730400002)(14454004)(2501003)(7696004)(6506006)(99286003)(106356001)(86362001)(230783001)(97736004)(5660300001)(2900100001)(66066001)(3280700002)(305945005)(33656002)(25786009)(81156014)(81166006)(6436002)(76176999)(9686003)(8676002)(478600001)(53936002)(55016002)(189998001)(53546010)(77096006)(7736002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR03MB077; H:SN2PR03MB2350.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: sonusnet.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2017 11:19:46.1123 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN2PR03MB077
X-MC-Unique: snfNUqKoOHaF5TfF3peX4A-1
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/3YBUG35u_6PWiH_GrXU2Tm4ZtHA>
Subject: Re: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2017 11:19:56 -0000

Initially I liked the idea of using "type" as a binary indicator but after thinking a bit more about it:

i- I don't think that would be proper use of "type". It is not meant to indicate probability but, as the name indicates, the type of the call. Overloading its semantics is not a good idea IMHO. So, still using "spam" is the right thing to do if one want to go "binary" AFAICT.
ii- On another node on "type": I really am not sure what use this field would have as far as enduser is concerned. As I indicated in an earlier message, any indication has practical value only during ringing IMHO. Do we really foresee the UI display something related with the "type" -unless it is for a type-value, for which network can assert 100% that is correct, e.g. "government", "emergency-alert"? I would keep type-values restricted to such values.

Thanks,
Tolga

-----Original Message-----
From: Henning Schulzrinne [mailto:Henning.Schulzrinne@fcc.gov] 
Sent: Thursday, July 20, 2017 3:22 PM
To: Asveren, Tolga <tasveren@sonusnet.com>; Paul Kyzivat <pkyzivat@alum.mit.edu>; sipcore@ietf.org
Subject: RE: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

It does say explicitly that all parameters are optional, but I will add text about what the absence means ("good enough", basically, since no indicator is 100% correct).

-----Original Message-----
From: Asveren, Tolga [mailto:tasveren@sonusnet.com] 
Sent: Thursday, July 20, 2017 2:41 PM
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>; Paul Kyzivat <pkyzivat@alum.mit.edu>; sipcore@ietf.org
Subject: RE: [sipcore] draft-ietf-sipcore-callinfo-spam-01 - SIP entities

O.K., this sounds good. It really could be good to add a sentence or two about this issue -even if the syntax already defines "spam" as optional"- though.
"Use of spam parameter requires a fine granularity decision about the nature of the call. It may not be possible to easily predict or use in an efficient way for certain networks, call flows, end-points."

Thanks,
Tolga

v2.23.0 | Report a Bug | By Email