[stir] Minutes and Materials for STIR's 16-Jun-2017 Virtual Interim

Robert Sparks <rjsparks@nostrum.com> Fri, 23 June 2017 20:10 UTC

Return-Path: <rjsparks@nostrum.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 EDF8A129411 for <stir@ietfa.amsl.com>; Fri, 23 Jun 2017 13:10:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 hRbBdGAJlblN for <stir@ietfa.amsl.com>; Fri, 23 Jun 2017 13:10:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50CF7129401 for <stir@ietf.org>; Fri, 23 Jun 2017 13:10:03 -0700 (PDT)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5NKA2jY022096 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <stir@ietf.org>; Fri, 23 Jun 2017 15:10:02 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: "stir@ietf.org" <stir@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <462690fb-57d3-c486-99fb-5192f458f9a8@nostrum.com>
Date: Fri, 23 Jun 2017 15:10:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/KeviYEuwQo9EAVwhxjIZlJMYHb4>
Subject: [stir] Minutes and Materials for STIR's 16-Jun-2017 Virtual Interim
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: Fri, 23 Jun 2017 20:10:08 -0000

All the materials are available here:

<https://datatracker.ietf.org/meeting/interim-2017-stir-01/session/stir>

The minutes are copied below for your convenience:

------

STIR Interim Meeting
16 June 2017
1900 UTC, via WebEx

Thanks to Eric Burger and Russ Housley for taking notes.


Robert - Agenda Bashing
=======================
No changes to the agenda were requested.
Reminder that the NOTE WELL applies to this meeting.  See
    https://www.ietf.org/about/note-well.html.


Jon Peterson: Out of Band (draft-rescola-fallback-02)
=====================================================
Discussion the processing of PASSporT by a Call Placement Service (CPS):
Draft: CPS accepts a PASSporT with an ‘acceptable’ root
Eric B.: Should just be a hint; whether a particular PASSporT is accepted
    or not is a matter of local policy
EKR: Would the receiving CPS need to know about all other CPS?
Mary: For the gateway use case, the gateway would probably have an
    account at the CPS.
Jon: I would not want to require an account, as that would kill the
    possibility of having an open, public service.  That said, would
    expect existing STIR credentials would already be trusted.  I would
    not rule out pre-association, such as an account, from the gateway.

Discussion on how to query the CPS to retrieve the PASSporT:
EKR: Is this not a pen register?
Robert: We probably need to assert both called and calling identities.
Jon: Likely, but still have a problem with diversion, which we will talk
    about later.  Also, there is potentially a problem because you are
    handing all the metadata to the CPS; conversely, someone can attack
    a CPS to extract metadata.  Plan to address the former with
    encryption.  Not sure there is a technical solution for the latter.

Discussion on WG Adoption:
Shockey: I will not work on the document.
Robert: Will take call for adoption to the list.


Martin Dolly: RPH extension (draft-singh-stir-rph-00)
=====================================================
Martin discussed the recently posted Internet-Draft that proposes a
PASSPorT Extension for Resource-Priority Authorization.  There was a
suggestion to reduce the complexity of the "rph" claim by eliminating
one layer of nesting.

Robert: Will take call for adoption to the list.


Jon Peterson: CNAM (draft-peterson-stir-cnam-02)
================================================
Discussion the proposed addition of the "cna" claim to PASSporT, which
is intended to be richer that Caller-ID:
Shockey: A lot of people outside the IETF are working on this topic.  Is
    this a generic object transport proposal or something interoperable?
General discussion ensued over the fact that calling name delivery is
    outright illegal in many jurisdictions, including most of the
    European continent, so this topic really a North American issue.

Robert: Will take call for adoption to the list with the understanding
    that draft-peterson-stir-cnam will be posted with a new filename that
    avoids the use of "cnam" to eliminate the potential for confusion
    with other activities that are taking place in other fora.


Jon Peterson: Diversion (draft-peterson-passport-divert-01)
===========================================================
Discussion of the handling of retargeted calls.  Is a reason code needed
to indicate that retargeting has taken place?
Mary offered to send use cases to the list.

Robert: Heard lots of interest to adopt this document. Will take call
    for adoption to the list.


Other
=====
Plan to discuss Connected ID at the upcoming IETF 99 meeting in Prague.