From nobody Wed May 11 13:20:57 2022 Return-Path: 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 BD954C14F74D for ; Wed, 11 May 2022 13:20:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.571 X-Spam-Level: X-Spam-Status: No, score=-7.571 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDha9oGPGSdV for ; Wed, 11 May 2022 13:20:52 -0700 (PDT) Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-vi1eur04on0607.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0e::607]) (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 E24D4C14EB1F for ; Wed, 11 May 2022 13:20:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LUDa1booSkEnphHmYZDoNyvEji8w70VHT+et24sg3Q43JhVOQj5TiRm7TwelKATTut7NkVV6Z2QaHvPcLxbSFF6X7vJpaV8jWJFit2002zRh1KeLq+9OIYM2iYjQyfXSgocyymO/W3w38/LrYoHaw2nCywI8lP9sTOMkmi/6NCITuupEzRprm7wsVFF9Inod9OJK5/Lvtur6EjykYxfIht1sRfmOzcs1uW33kAHXqbIaynQsN3OqrH0u2O5w2CmS3NTiffGmJ8gvsuei7Vov4/2foELBime6zaENAR2G+LBoRvu09R7Npgr8B4CgMFxGvMymCgNVQpYIes6F4tQQNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=zbdUZ50c5KTUbH4iSjBC36Xa52HQ7MTQzVGPg7pYwFw=; b=gw1jmMQfQOvubj8iZgwINDZq3Tkna168lo/GpjfUpzJQFbDliqeoB+da5kfoI1dJMd1LcwQaUmDAK3PCBosslnvob9i+jEya3m/ITA4oohsADkCvqvUS4KC3YzCZRGuyo/gIfEX/OBUhaYPVkBG5+m+5TBolRzdDEj4E41vDOpFt1W5reksOSgcpiEvNpUm5vohIQsSq9o9ne1CbYu2JLPaanypioN4QZaEXpMqiBZ5/NOa6bdp15tP7MVXxeJ7FBzHfMlmt7FZSLnJgy3mpjYxGU8/V01XVyS96XLo5Ys19JKbK849Ci4gEiB/7VVE3YovVFcKSFu+jQiJhF1qsVA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zbdUZ50c5KTUbH4iSjBC36Xa52HQ7MTQzVGPg7pYwFw=; b=J9Bawu2iDtcO29yPPov2BBDYBgGeq6phFuJLyXaQTxYgKT+9iXglDYwbsIhZL3Ih3SCdizh0MWzaOp/HzMNF/9tOCWwfbabhJRj7NMJERADSqbiEj/543ymhyEZzOyJmQQ1CddUpOcxPALFtHG9sHKuXHQdTEhBV4NsDFuhpqgE= Received: from HE1PR07MB4441.eurprd07.prod.outlook.com (2603:10a6:7:9f::27) by DU2PR07MB8269.eurprd07.prod.outlook.com (2603:10a6:10:276::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5250.12; Wed, 11 May 2022 20:20:46 +0000 Received: from HE1PR07MB4441.eurprd07.prod.outlook.com ([fe80::2978:72c:44da:e08e]) by HE1PR07MB4441.eurprd07.prod.outlook.com ([fe80::2978:72c:44da:e08e%6]) with mapi id 15.20.5227.018; Wed, 11 May 2022 20:20:38 +0000 From: Christer Holmberg To: "Gorman, Pierce" , Richard Shockey , "stir@ietf.org" Thread-Topic: [stir] Definition of STIR Thread-Index: AQHYZWjwURRuMvOSyEKuuvYTpWphu60aDUDQgAABwICAAA2qIA== Date: Wed, 11 May 2022 20:20:38 +0000 Message-ID: References: <700E1CC1-37ED-4A26-9822-35874C925646@shockey.us> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c18bf13e-45b5-4c53-0417-08da338bb6c3 x-ms-traffictypediagnostic: DU2PR07MB8269:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: c59kanb/JyY2dYsK0Djwf2n+H8I8LMAuD0xMDNYVAnc/9elm6Pr5YNbgbOVpfbK73htr8VrIoMRAzyw2l+2UR8LdBbvhUREsC0HmlGmCqyUK2ltTeZ5rpxOgyqYYgwtB4eBskm5yZoUuMhWpD9UmiLSS6bWRnE3pTMoz3hADcmadsHPf0CPBRIqp5S9w1Ct6pd647BgKEakME4usQRqrErtr+av9RIQTAUpDYOkdtLs2PIihVr2+A7W7i1gB25Eal1FuSpIeSZ8W/YYqOvqEmB9+9PYIWxAFHybLEzscLJCP5Ahc4P2YRWVf8rcjIuV59Fnk8FAd08Z6NuJdru4TL8Ezccmo0VGhlzU67tIxxRY1cqzKUoiC1w/wcAzUwEuiSFMElUAZFS6j7OgMg0wFOhc3h1BVspMWczYHvfslG9Ou2npcuHEdVCyDvgUgG/ztSZmeJOT9qGqMRUcdAwxtmwL5oiPsB2d/9EZAMF/RmKGe3SRQgaUvyFZTz/S1yokDtRJc4H3KLrDB+W9bm8g/2B3G5EuYUagt9ejZF8o1oisgjYnk2/en36UAWBjRsRBWyt84g+OhdxqDCw5H37Y9gW2cgiqBy7y6CvGELo7dFJFE3+MqnOmKva8z9nfVFsrh+RWXA8WgL8g5XZ3H2X3nhRXDiXnBLfX6pt3VRk6ScSlTBQeWWWrw5wi1fS3CxUO95oEkWvJEJyPDm56ELKFjS4HObsKeLtxtI7AJ38zuUzsnDvVoWZsCjqqG7FKL9/vJzcXqiWz69DpL/HM11EJRUuTqHJm0G3JE6bvsM+TdOQObLfn3KbXh3aYipURAD22Lpgbn/0U+RC9K3QcI0efmzw== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HE1PR07MB4441.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(6506007)(66476007)(66556008)(53546011)(66446008)(166002)(66946007)(76116006)(122000001)(64756008)(508600001)(45080400002)(33656002)(83380400001)(26005)(40140700001)(9686003)(55016003)(44832011)(86362001)(5660300002)(110136005)(2906002)(8936002)(82960400001)(8676002)(38100700002)(38070700005)(52536014)(71200400001)(966005)(296002)(7696005)(316002)(186003); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?iAmBhPpctNS9CuggXwkTAyv8Bh8A6JTCOisj/+axz6KNV0DBDU9BDp5tUjOo?= =?us-ascii?Q?b0D6gf2xlZGxlynY1Uq8oxqzrf7FL9mXnD9kjMh+KRRqme0NuxeC+pN5/Amq?= =?us-ascii?Q?c7A+sin0HTiTvRFWQ/s5cLzHi4s9lNYc636oDjNMf8q1n+E2YLNWqWs2F5pG?= =?us-ascii?Q?PGr8XBbtHJPgXtOhPgy2pO8ZHZqZHT7uGTA5B5+uxw2q6PcmKiUdwT8seZfu?= =?us-ascii?Q?HbFrUG6UpPZ4DvhJ+p1K2JUP/96y4QBSYhyun6+fku5VfxiptgVrqaCB9Yfc?= =?us-ascii?Q?qSvUA16r+YkW6HALE1/baGeSouSLEJ5vMpXRCkgWAgzkmfidN/KUZU7ihQeM?= =?us-ascii?Q?3s2cMo12lR0thFwVlpEKmfRItGM39kdNqL1I3Gs2HIlNndczHiShjAEbw19P?= =?us-ascii?Q?G8/xagPQkE6P3HPM5YaBxKHj9+ARsUm5MDJO+nc7ICTDioB7fpmoeOZINTO7?= =?us-ascii?Q?UYwHeJIQaZ4yPIz/c+U70Lb2wIOJSgKmAZiI3pBWerJDuzynNU8yyPQt8lxw?= =?us-ascii?Q?Niqw28ZhdqJwTjUYjbbHMzS74hCRDxfKDMVBZOmEw2mEubWjcBoiJS3zG1JN?= =?us-ascii?Q?lzAqnpPLHOUl72laKlL7AV8koA7F9cTV9zyy2SAidJ/Araf7ExPTgQxv9k6h?= =?us-ascii?Q?Dfx28Pvb3NdUQ7n2S774L7lNb0DznqC2CpfTbF8HTeaqOsxI5HRkVVQ/12pK?= =?us-ascii?Q?hiDwLQI25EqI/2H1SdFeVJ+XZBpZu8J7Jiu6Qp8BKCofiyyO9S25DreMHoa+?= =?us-ascii?Q?tVlbbSjX+pdWGWkU/9ozqq7eocaDl93cBk3sLFMelHy9ECKu2XX5HFmqdEan?= =?us-ascii?Q?ruqelZE0HP+NRixns63cwo14Ky7Uuz9RjnUNmopSX3G6eLuRzvOR9St7SSM2?= =?us-ascii?Q?8IRf96uMKl5y0t5pX1QT8lbMjPTFM9BWSeWIdnxw+h+qCV0qYEvc3qcK/GfK?= =?us-ascii?Q?2LcjnXf/xh4w/pIW+W+VYG4NdlpN21mBtHgA1lpKbwjBPyS1WN4RrIkpLpcj?= =?us-ascii?Q?6SAdYeZj/kYSw3vgEdAYEb7aUARSDFteXk8053DMJz5uqpY2lFoQ9aA1pygH?= =?us-ascii?Q?6pl2B2bXh1AH7UwEORxfhocWbMJjju75fRa7/RPpyzcKQ3JHGFaS2S72Xqpj?= =?us-ascii?Q?3I+6gejnBP97WKfdjnvvc644bqurZaa6I4iota85AXLVOnOrSrAVNYDtuSaX?= =?us-ascii?Q?cYQKpMZyyONSUm7RqJZt/7CxQ628DAR60IqfGprKzDJF4FdxfQwevVnBnAHH?= =?us-ascii?Q?DffJRzvCEckmlNvYElHjy2nprVkuMpzcMpldmcygmfM4NfipkzJkYIEVJWa2?= =?us-ascii?Q?lQhzQs8HbLiPJfnlstgULtkvEpQcDaq+ItTfl5O6FMmaT+YP6BqxlSJZxZY5?= =?us-ascii?Q?IpKr+Ezjisp/WiUX81arHlJdGt535gRU7+7YB5g/WuQLf8KUmYSDT68s1pam?= =?us-ascii?Q?OSpkNKQ1nVRFVhvFzYmN3nNWBobHniaNuaDobSljxjet/DmuMzuQ8myVkTaA?= =?us-ascii?Q?gZAZpuRbli/kmEro8+bhX2f8QjsWYKEt6IzG6aiqnL3AQ+rkFHPQQKJ8KOyy?= =?us-ascii?Q?+/CCS1hMJ2/vUT7o2a1IIrYe5bdQwjURqnCAPwAxwxOlDynLfaSJ8fZsq5H/?= =?us-ascii?Q?nIVJ1Eml/lABt05PWdD489rc2t1hIJpI049LmDLjwNTlBKR7HBIFY2ZdkKmO?= =?us-ascii?Q?TQYX5OqGxZMrL0jl4zz2mVqru78zf66MM2nambz1KkRX3I17yBR6mzpcHW4x?= =?us-ascii?Q?d3Z3tww6bqVePSYQw8fxgBk8s+zaADg=3D?= Content-Type: multipart/alternative; boundary="_000_HE1PR07MB4441BB167B0AD82243F005B493C89HE1PR07MB4441eurp_" MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4441.eurprd07.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: c18bf13e-45b5-4c53-0417-08da338bb6c3 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2022 20:20:38.5582 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: tBByyx00pzoW38urnmFjqIoitwgjviikymPaKoDLiR/n9fCHzwXcOvV+y2/TmDKL4W6bjA8+OEgL4JggQ/5twxEG+ZsLft79uIllJ5d2Yq0= X-MS-Exchange-Transport-CrossTenantHeadersStamped: DU2PR07MB8269 Archived-At: Subject: Re: [stir] Definition of STIR X-BeenThere: stir@ietf.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Secure Telephone Identity Revisited List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2022 20:20:56 -0000 --_000_HE1PR07MB4441BB167B0AD82243F005B493C89HE1PR07MB4441eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, >Does it need to be in an RFC? Maybe update the WG charter instead? I don't think we normally define terminology in the charter. Also, as the W= G/charter may not "last forever", I don't know if we can reference it. >I'm not against it being in an RFC, but don't know if there is a need. The word "STIR" is used in many RFCs, but there is no (AFAIK) definition or= reference anywhere. draft-ietf-stir-identity-header-errors-handling references RFC 8224 for the= new "STIR" Reason header protocol value. Regards, Christer From: Christer Holmberg > Sent: Wednesday, May 11, 2022 2:23 PM To: Richard Shockey >; Gorman= , Pierce >; s= tir@ietf.org Subject: RE: [stir] Definition of STIR Hi, >Pierce that about covers it... But that is not documented in any RFC, is it? Regards, Christer - Richard Shockey Shockey Consulting LLC Chairman of the Board SIP Forum www.shockey.us www.sipforum.org www.sipnoc.org = (2022) richardshockey.us Skype-Linkedin-Facebook -Twitter rshockey101 PSTN +1 703-593-2683 From: stir > on behalf = of "Gorman, Pierce" > Date: Wednesday, May 11, 2022 at 2:04 PM To: Christer Holmberg >, "stir@ietf.org" > Subject: Re: [stir] Definition of STIR I suppose you or others could volunteer attempts at a definition. Once sat= isfactorily achieved, what would you do with it? Not trying to be a smart = alec. I'm seriously curious. I will volunteer that I think of "STIR" as being the collection of work in = the IETF that is referenced in "SHAKEN" call authentication specifications = in use in the US and Canada (so far). "STIR" is the collection of work that tells you how to create a SIP Identit= y header of whatever type you need for a particular call type, and how to c= reate an X.509 security certificate (chain) with extensions and constraints= needed to verify the contents of a SIP Identity header. "SHAKEN" (a body of work in the ATIS/SIP Forum Joint Task Force on IP-NNI) = tells you how to create and use various SIP Identity types defined in "STIR= " and about the governance, policy, and certificate authorization framework= used to acquire SHAKEN-specific X.509 end-entity certificates. Beyond this, the call authentication governance authorities in the US and C= anada have created requirements and selected entities to be Policy Administ= rators (PAs) and also created Certificate Policies which outline the requir= ements to be an authorized (within their respective jurisdictions) Certific= ation Authority (CA), thus creating the SHAKEN GA/PA/CA Secure Telephone Id= entity (STI) Public Key Infrastructures (PKIs). I expect others can volunteer alternative, and potentially better, definiti= ons. Best regards, Pierce Gorman From: stir > On Behalf = Of Christer Holmberg Sent: Wednesday, May 11, 2022 11:52 AM To: stir@ietf.org Subject: [stir] Definition of STIR [External] Hi, What exactly is "STIR", other than the name of an IETF WG? Sometimes "STIR" used in document titles, sometimes there is text saying "S= TIR"/"the STIR mechanism" does this and that, provides this and that etc. d= raft-ietf-stir-identity-header-errors-handling talks about "extending STIR"= . RFC 7340 is supposed to describe the STIR problem, but 7340 does not even s= ay what STIR stands for (Secure Telephone Identity Revisited), and there is= no RFC named "STIR". The question came up while I was reviewing the messaging draft, which says: "Secure Telephone Identity Revisited (STIR) provides a means of attesting t= he identity of a telephone caller..." Regards, Christer _______________________________________________ stir mailing list stir@ietf= .org https://www.ietf.org/mailman/listinfo/stir --_000_HE1PR07MB4441BB167B0AD82243F005B493C89HE1PR07MB4441eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= /o:p>

 

>Does= it need to be in an RFC?  Maybe update the WG charter instead?=

 

I don’t think we normally= define terminology in the charter. Also, as the WG/charter may not “= last forever”, I don’t know if we can reference it.<= /span>

 =

>I= 217;m not against it being in an RFC, but don’t know if there is a ne= ed.

 

The word “STIR” is = used in many RFCs, but there is no (AFAIK) definition or reference anywhere= .

 

draft-ietf-stir-identity-header= -errors-handling references RFC 8224 for the new “STIR” Reason = header protocol value.

 

Regards,

 

Christer

 

&n= bsp;

 =

From: Christer Holmberg <christer.holmberg@ericsson.com>
Sent: Wednesday, May 11, 2022 2:23 PM
To: Richard Shockey <richar= d@shockey.us>; Gorman, Pierce <Pierce.Gorman@t-mobile.com>; stir@ietf.org
Subject: RE: [stir] Definition of STIR

 

Hi,

 

>= Pierce that about covers it…

 

But that is not documented in a= ny RFC, is it?

 

Regards,

 

Christer

 

 

 

 

— 

Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

richard<at>shockey.us

Skype-Linkedin-Facebook –Twitter  rshockey101<= /span>

PSTN +1 703-593-2683

 

 

From: stir= <stir-bounces@ietf.org>= on behalf of "Gorman, Pierce" <Pierce.Gorman@t-mobile.com>
Date: Wednesday, May 11, 2022 at 2:04 PM
To: Christer Holmberg <christer.holmberg=3D40ericsson.com@dmarc.ietf.or= g>, "stir@ietf.org" &= lt;stir@ietf.org>
Subject: Re: [stir] Definition of STIR

 

I suppose you or others could volunteer attempts at a definition.  O= nce satisfactorily achieved, what would you do with it?  Not trying to be a smart alec.  I’m seriously curious.

 

I will volunteer that I think of “STIR” as be= ing the collection of work in the IETF that is referenced in “SHAKEN&= #8221; call authentication specifications in use in the US and Canada (so far).

 

“STIR” is the collection of work that tells y= ou how to create a SIP Identity header of whatever type you need for a particular call type, and how to create an X.509 security certificat= e (chain) with extensions and constraints needed to verify the contents of = a SIP Identity header.

 

“SHAKEN” (a body of work in the ATIS/SIP Foru= m Joint Task Force on IP-NNI) tells you how to create and use various SIP Identity types defined in “STIR” and about the gov= ernance, policy, and certificate authorization framework used to acquire SH= AKEN-specific X.509 end-entity certificates.

 

Beyond this, the call authentication governance authoriti= es in the US and Canada have created requirements and selected entities to be Policy Administrators (PAs) and also created C= ertificate Policies which outline the requirements to be an authorized (wit= hin their respective jurisdictions) Certification Authority (CA), thus crea= ting the SHAKEN GA/PA/CA Secure Telephone Identity (STI) Public Key Infrastructures (PKIs).

 

I expect others can volunteer alternative, and potentiall= y better, definitions.

 

Best regards,

 

 

Pierce Gorman

From: stir <stir-bounces@= ietf.org> On Behalf Of Christer Holmberg
Sent: Wednesday, May 11, 2022 11:52 AM
To: stir@ietf.org
Subject: [stir] Definition of STIR

 

<= span lang=3D"EN-US" style=3D"font-size:10.0pt;color:#9C6500">[External]

 

Hi,

 

What exactly is ”STIR”, other than the na= me of an IETF WG?

 

Sometimes “STIR” used in document titles,= sometimes there is text saying “STIR”/“the STIR mechanis= m” does this and that, provides this and that etc. draft-ietf-stir-id= entity-header-errors-handling talks about “extending STIR”.

 

RFC 7340 is supposed to describe the STIR problem, bu= t 7340 does not even say what STIR stands for (Secure Telephone Identity Re= visited), and there is no RFC named “STIR”.

 

The question came up while I was reviewing the messag= ing draft, which says:

 

“Secure Telephone Identity Revisited (STIR) pro= vides a means of attesting the identity of a telephone caller…”=

 

Regards,

 

Christer

 

_______________________________= ________________ stir mailing list stir@ietf.org https://www.ietf.org/mailman/listinfo/stir

--_000_HE1PR07MB4441BB167B0AD82243F005B493C89HE1PR07MB4441eurp_--