From nobody Wed May 1 10:58:12 2019 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 D830C120125 for ; Wed, 1 May 2019 10:58:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no 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 GpTJ6oTrMYu2 for ; Wed, 1 May 2019 10:58:08 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5AB120130 for ; Wed, 1 May 2019 10:58:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6430A300AE5 for ; Wed, 1 May 2019 13:39:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id z51QQ5WdECZp for ; Wed, 1 May 2019 13:39:49 -0400 (EDT) Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 4B859300471 for ; Wed, 1 May 2019 13:39:49 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Date: Wed, 1 May 2019 13:58:06 -0400 References: To: IETF STIR Mail List In-Reply-To: Message-Id: <8D22E1C6-7DF4-4113-BDD7-6C1BEA4C856A@vigilsec.com> X-Mailer: Apple Mail (2.3445.104.8) Archived-At: Subject: Re: [stir] Call for Adoption by STIR WG: draft-peterson-stir-cert-delegation-00 X-BeenThere: stir@ietf.org 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: Wed, 01 May 2019 17:58:11 -0000 There was significant support for adoption at the meeting in Prague. = There has been very little email traffic, but all of it has been = supportive of adoption, although some comments were provided too. = Authors, please post a draft-ietf-stir-cert-delegation draft. Russ > On Mar 31, 2019, at 4:10 PM, Russ Housley = wrote: >=20 > During IETF 104, several people expressed a desire for the STIR WG to = adopt draft-peterson-stir-cert-delegation-00. >=20 > Please send your support or concerns to the list or the chairs by = Friday, 19 April 2019. (This leaves a little over three weeks since many = have travel plans after the IETF week). >=20 > Robert and Russ From nobody Wed May 1 12:48:45 2019 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 CDFD012008D for ; Wed, 1 May 2019 12:18:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 8p9naHjKfazG for ; Wed, 1 May 2019 12:18:47 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366B2120021 for ; Wed, 1 May 2019 12:18:47 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 507B2B80E92; Wed, 1 May 2019 12:18:35 -0700 (PDT) To: jon.peterson@neustar.biz, fluffy@cisco.com, ekr@rtfm.com, chris-ietf@chriswendt.net, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, rjsparks@nostrum.com, housley@vigilsec.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: alexl@telnyx.com, stir@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20190501191835.507B2B80E92@rfc-editor.org> Date: Wed, 1 May 2019 12:18:35 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Wed, 01 May 2019 12:48:44 -0700 Subject: [stir] [Technical Errata Reported] RFC8224 (5715) X-BeenThere: stir@ietf.org 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: Wed, 01 May 2019 19:18:50 -0000 The following errata report has been submitted for RFC8224, "Authenticated Identity Management in the Session Initiation Protocol (SIP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5715 -------------------------------------- Type: Technical Reported by: Alex Lee Section: 4.1 Original Text ------------- o Second, the JSON "dest" array MUST be populated. If the destination identity is a telephone number, then the array MUST be populated with a JSON object containing a "tn" element with a value set to the value of the quoted destination identity, a canonicalized telephone number (see Section 8.3). Otherwise, the array MUST be populated with a JSON object containing a "uri" element, set to the value of the addr-spec component of the To header field, which is the AoR to which the request is being sent, per the procedures in Section 8.5. Multiple JSON objects are permitted in "dest" for future compatibility reasons. ... The "orig" and "dest" arrays may contain identifiers of heterogeneous type; for example, the "orig" array might contain a "tn" claim, while the "dest" contains a "uri" claim. Also note that in some cases, the "dest" array may be populated with more than one value. This could, for example, occur when multiple "dest" identities are specified in a meshed conference. Defining how a SIP implementation would align multiple destination identities in PASSporT with such systems is left as a subject for future specifications. Corrected Text -------------- o Second, the JSON "dest" object MUST be populated. If the destination identity is a telephone number, then the object MUST contain a "tn" element with a value set to an array containing the value of the quoted destination identity, a canonicalized telephone number (see Section 8.3). Otherwise, the object MUST contain a "uri" element, set to an array containing the value of the addr-spec component of the To header field, which is the AoR to which the request is being sent, per the procedures in Section 8.5. Additional elements are permitted in "dest" for future compatibility reasons. ... The "orig" and "dest" objects may contain identifiers of heterogeneous type; for example, the "orig" object might contain a "tn" claim, while the "dest" contains a "uri" claim. Also note that in some cases, the "dest" object may be populated with more than one claim, and its claim value arrays may contain more than one value. This could, for example, occur when multiple "dest" identities are specified in a meshed conference. Defining how a SIP implementation would align multiple destination identities in PASSporT with such systems is left as a subject for future specifications. Notes ----- The description of the "dest" element does not match RFC8225 or the example that is provided in this section. The terminology is a bit less clear than in RFC8225 section 5.2.1, in that no differentiation is made between the top level "claims" and embedded "identity claims". The proposed correction does not address this lack of clarity, however. >From RFC8225 section 5.2.1: The "dest" claim is a JSON object with the claim name of "dest" and MUST have at least one identity claim object. The "dest" claim value is an array containing one or more identity claim JSON objects representing the destination identities of any type (currently "tn" or "uri"). If the "dest" claim value array contains both "tn" and "uri" claim names, the JSON object should list the "tn" array first and the "uri" array second. Within the "tn" and "uri" arrays, the identity strings should be put in lexicographical order, including the scheme-specific portion of the URI characters. (The above text might need correction as well, because it refers to the '"dest" claim value array'.) Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8224 (draft-ietf-stir-rfc4474bis-16) -------------------------------------- Title : Authenticated Identity Management in the Session Initiation Protocol (SIP) Publication Date : February 2018 Author(s) : J. Peterson, C. Jennings, E. Rescorla, C. Wendt Category : PROPOSED STANDARD Source : Secure Telephone Identity Revisited Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Wed May 1 14:43:51 2019 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 5463712007C for ; Wed, 1 May 2019 14:43:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no 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 SsHn1-_Z-ZWr for ; Wed, 1 May 2019 14:43:47 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7402912001B for ; Wed, 1 May 2019 14:43:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4AAA1300A0B for ; Wed, 1 May 2019 17:25:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BkoG4yxTLWzg for ; Wed, 1 May 2019 17:25:28 -0400 (EDT) Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 4A882300471 for ; Wed, 1 May 2019 17:25:28 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Date: Wed, 1 May 2019 17:43:44 -0400 References: <9E2381A8-F39F-425D-BB64-EB39AE1018F6@vigilsec.com> To: IETF STIR Mail List In-Reply-To: <9E2381A8-F39F-425D-BB64-EB39AE1018F6@vigilsec.com> Message-Id: <5F35F385-E52B-4226-9DE0-F899F5D364A4@vigilsec.com> X-Mailer: Apple Mail (2.3445.104.8) Archived-At: Subject: Re: [stir] Second WGLC: draft-ietf-stir-passport-divert-05 X-BeenThere: stir@ietf.org 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: Wed, 01 May 2019 21:43:49 -0000 I have seen responses to all of the comments that were sent to the list. = Can the authors please post an update to the Internet-Draft that = includes the changes that were discussed. Once that is posted, we will = give the commenters a few days to makes sure the comments were resolved. = Unless a concern us raised, then we will send this document to the = IESG. Russ > On Mar 31, 2019, at 4:01 PM, Russ Housley = wrote: >=20 > This is the second Working Group Last Call for = draft-ietf-stir-passport-divert, which is now at revision -05. >=20 > Please send your comments to the list or the chairs by Friday, 19 = April 2019. (This leaves a little over three weeks since many have = travel plans after the IETF week). >=20 > Robert and Russ From nobody Wed May 1 14:53:01 2019 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 AA7E112004F for ; Wed, 1 May 2019 14:52:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no 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 YO4Qgz677B3U for ; Wed, 1 May 2019 14:52:58 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9153512001B for ; Wed, 1 May 2019 14:52:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 838FD300ADA for ; Wed, 1 May 2019 17:34:40 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id q9uVAaAkOENX for ; Wed, 1 May 2019 17:34:39 -0400 (EDT) Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 76F20300471 for ; Wed, 1 May 2019 17:34:39 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Date: Wed, 1 May 2019 17:52:56 -0400 References: <3BF05F63-D7C2-4BC3-912F-A7628F1B3BEC@vigilsec.com> <8bc5e24f-5e79-a496-664c-9f09aeaa0232@nostrum.com> To: IETF STIR Mail List In-Reply-To: <8bc5e24f-5e79-a496-664c-9f09aeaa0232@nostrum.com> Message-Id: <55FD247D-D028-4907-802C-289F31AA2E38@vigilsec.com> X-Mailer: Apple Mail (2.3445.104.8) Archived-At: Subject: Re: [stir] Second WGLC: draft-ietf-stir-oob-04 X-BeenThere: stir@ietf.org 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: Wed, 01 May 2019 21:53:00 -0000 I have seen responses to all of the comments that were sent to the list. = Can the authors please post an update to the Internet-Draft that = includes the changes that were discussed, including the intended status = of Informational. One of the comments was fairly major, but a way = forward was agreed. Once the updated Internet-Draft is posted, we will = give the commenters a week or so to make sure their comments were = resolved. Unless a concern is raised, then we will send this document = to the IESG. Russ > On Apr 9, 2019, at 12:44 PM, Robert Sparks = wrote: >=20 > Retransmitting so that the subject matches the body. >=20 > RjS >=20 > On 3/31/19 3:07 PM, Russ Housley wrote: >> This is the second Working Group Last Call for draft-ietf-stir-oob, = which is now at revision -04. >>=20 >> Please send your comments to the list or the chairs by Friday, 19 = April 2019. (This leaves a little over three weeks since many have = travel plans after the IETF week). >>=20 >> Robert and Russ From nobody Tue May 14 18:35:28 2019 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 32E2F120232; Tue, 14 May 2019 18:35:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 8DX-pKw3L-O4; Tue, 14 May 2019 18:35:15 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F052F12004E; Tue, 14 May 2019 18:35:14 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 806F5B81DA3; Tue, 14 May 2019 18:35:02 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, stir@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20190515013502.806F5B81DA3@rfc-editor.org> Date: Tue, 14 May 2019 18:35:02 -0700 (PDT) Archived-At: Subject: [stir] =?utf-8?q?RFC_8588_on_Personal_Assertion_Token_=28PaSSpor?= =?utf-8?q?T=29_Extension_for_Signature-based_Handling_of_Asserted_informa?= =?utf-8?q?tion_using_toKENs_=28SHAKEN=29?= X-BeenThere: stir@ietf.org 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: Wed, 15 May 2019 01:35:17 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8588 Title: Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN) Author: C. Wendt, M. Barnes Status: Standards Track Stream: IETF Date: May 2019 Mailbox: chris-ietf@chriswendt.net, mary.ietf.barnes@gmail.com Pages: 9 Characters: 17254 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-stir-passport-shaken-08.txt URL: https://www.rfc-editor.org/info/rfc8588 DOI: 10.17487/RFC8588 This document extends the Personal Assertion Token (PASSporT), which is a token object that conveys cryptographically signed information about the participants involved in communications. The extension is defined based on the "Signature-based Handling of Asserted information using toKENs (SHAKEN)" specification by the ATIS/SIP Forum IP-NNI Task Group. It provides both (1) a specific set of levels of confidence in the correctness of the originating identity of a call originated in a SIP-based telephone network as well as (2) an identifier that allows the Service Provider (SP) to uniquely identify the origin of the call within its network. This document is a product of the Secure Telephone Identity Revisited Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC