Re: [stir] DRAFT Agenda for STIR ay IETF 111

Richard Shockey <> Tue, 13 July 2021 18:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E0933A0147 for <>; Tue, 13 Jul 2021 11:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (768-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ebh2j51Hi2wM for <>; Tue, 13 Jul 2021 11:25:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 57DF03A00E5 for <>; Tue, 13 Jul 2021 11:25:38 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B6DDB240F9 for <>; Tue, 13 Jul 2021 13:25:37 -0500 (CDT)
Received: from ([]) by cmsmtp with SMTP id 3N69mAZ0KL9qA3N69mi39a; Tue, 13 Jul 2021 13:25:37 -0500
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:CC: To:From:Subject:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=wd5anjaUvjiC7bfK5L5bLMTQ/WOCujSG0ceDoWKM3AA=; b=KI2JNLRjKg/PPEv0g0lAo+WlZq u10Zzxr4wCbqlp81O3niLNLkTZv8IfFbAqsoMN8WQeQ4f65JfSm4lPWdydju6coqptN/m3hT8qAy8 quDZT7sOV15MKYii8wfY0rFAm;
Received: from ([]:53988 helo=[]) by with esmtpa (Exim 4.94.2) (envelope-from <>) id 1m3N69-002yut-CJ; Tue, 13 Jul 2021 12:25:37 -0600
User-Agent: Microsoft-MacOutlook/16.50.21061301
Date: Tue, 13 Jul 2021 14:25:36 -0400
From: Richard Shockey <>
To: Russ Housley <>, Roman Shpount <>
CC: IETF STIR Mail List <>
Message-ID: <>
Thread-Topic: [stir] DRAFT Agenda for STIR ay IETF 111
References: <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3709031137_1849489421"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-BWhitelist: no
X-Source-L: No
X-Exim-ID: 1m3N69-002yut-CJ
X-Source-Sender: ([]) []:53988
X-Email-Count: 1
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NTUyNy5ibHVlaG9zdC5jb20=
X-Local-Domain: yes
Archived-At: <>
Subject: Re: [stir] DRAFT Agenda for STIR ay IETF 111
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Telephone Identity Revisited <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 13 Jul 2021 18:25:44 -0000


A new SIPIT has been under active discussion for some time with a emphasis on RCD interoperability. STIR is of course a legal requirement in the US and Canada and may be mandated in the UK and France later this year.


We’re talking about a lot of that next week.


At some point there needs to be a STIR/SHAKEN BCP. There are issues that keep coming up.  Obviously the TCP fragmentation issues. Not all network elements perform canonicalization consistently – this can result in improperly signed calls that do not get verified correctly.




Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum


Skype-Linkedin-Facebook –Twitter  rshockey101

PSTN +1 703-593-2683



From: stir <> on behalf of Russ Housley <>
Date: Tuesday, July 13, 2021 at 1:56 PM
To: Roman Shpount <>
Cc: IETF STIR Mail List <>
Subject: Re: [stir] DRAFT Agenda for STIR ay IETF 111


I think that a SIPIT would be a very good thing, but that is not and IRTF activity.  That said, I would be very happy to use this list to know about a SIPIT once it is organized.

Are there other interoperability or ops-orient topics about STIR that needed to be discussed?  If so, please start a thread.




On Jul 12, 2021, at 10:01 PM, Roman Shpount <> wrote:


Can anyone talk about the current interop and implementation status for STIR?

There was some discussion before about organizing a new SIPIT event that would be focused on STIR interop. Can we discuss the status of that during the meeting?


Thank you,
Roman Shpount



On Mon, Jul 12, 2021 at 8:10 PM Russ Housley <> wrote:

Please send comments to the mail list.


= = = = = = 

STIR Working Group at Virtual IETF 111

1) Administrivia
   - Agenda Bashing
   - Minute Taker
   - Jabber Scribe
   - Bluesheets

2) PASSporT Extension for Rich Call Data
   - Chris Wendt and Jon Peterson
   - draft-ietf-stir-passport-rcd
   - Resolve open issues from WG Last Call

3) Secure Reporting of Update Status
   - Jon Peterson
   - draft-ietf-stir-servprovider-oob
   - Prepare for WG Last Call

4) Messaging Use Cases and Extensions for STIR
   - Jon Peterson and Chris Wendt
   - draft-ietf-stir-messaging
   - Recently adopted; progress toward WG Last Call

5) Connected Identity for STIR
   - Jon Peterson and Chris Wendt
   - draft-peterson-stir-rfc4916-update
   - Discuss open issues; get ready for WG call for adoption

6) Identity Header Error Handling
   - Chris Wendt
   - draft-wendt-stir-identity-header-errors-handling
   - Discuss open issues; get ready for WG call for adoption    

7) Any Other Business (if time permits)

stir mailing list

stir mailing list

_______________________________________________ stir mailing list