Re: [stir] Second WG Last Call for RFC4474bis

Alissa Cooper <alissa@cooperw.in> Mon, 26 September 2016 15:43 UTC

Return-Path: <alissa@cooperw.in>
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 749E912B2D3 for <stir@ietfa.amsl.com>; Mon, 26 Sep 2016 08:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=xq6ohvhD; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=KKM/GE/M
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 KhDYBU-s6GST for <stir@ietfa.amsl.com>; Mon, 26 Sep 2016 08:43:38 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E28AE12B04A for <stir@ietf.org>; Mon, 26 Sep 2016 08:43:37 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4E448206D1; Mon, 26 Sep 2016 11:43:37 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 26 Sep 2016 11:43:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=Mu7u1w1odZzZRjnwbF7OqKukOdw=; b=xq6ohv hD+C4EEi6Rau0YIsbnoIpLoABgS5O7jfnMiPW/SCm4rMaNVYp8k3jTBMFpceMbF/ jkBhqhKHQr+V5gm7EiH65gFtBpPO4zkTJiIIDkpl+PdL6BsnbpXQCxdqmgCZVNpb 4kktp2kL50EO0oIlPUA/w82cSXZ1diDXwilOo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Mu7u1w1odZzZRjn wbF7OqKukOdw=; b=KKM/GE/McaAUPsyYg4Q1vAjglQ1IAKWvsBU8UlAfqeo4SIW gGLa1Udo4B3tHj2JcZZDjZGWucg/N1LzGfm8Nye7DkX8faDRgZybyM1JV8dHpTCL PAepAfztP5GGndCdQBefjwm4e3mBwcUhrYR0wMu68keYM//f6vmq8liBJPPE=
X-Sasl-enc: ++k4ip7zWIFX/fxh8hNc14r0EidKulXFRxsofupI7b1O 1474904616
Received: from dhcp-10-150-9-154.cisco.com (unknown [173.38.117.90]) by mail.messagingengine.com (Postfix) with ESMTPA id D39B6CCEB0; Mon, 26 Sep 2016 11:43:36 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <D4096F01.1BA013%jon.peterson@neustar.biz>
Date: Mon, 26 Sep 2016 11:43:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6713660A-6B29-46A2-816B-3F143DCD0093@cooperw.in>
References: <C1E751BC-55E9-4D8C-A6A5-B5674835870E@vigilsec.com> <10F4895C-4103-497A-B1E0-7B6CB617F13C@vigilsec.com> <7D464687-370D-43CA-8AFA-2DE5C9C576E8@cooperw.in> <D4096F01.1BA013%jon.peterson@neustar.biz>
To: Jon Peterson <jon.peterson@neustar.biz>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/zeHDZM8uQqlki4NXVgJLl8Fil4M>
Cc: IETF STIR Mail List <stir@ietf.org>, Russ Housley <housley@vigilsec.com>
Subject: Re: [stir] Second WG Last Call for RFC4474bis
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 26 Sep 2016 15:43:39 -0000

> On Sep 22, 2016, at 3:12 PM, Peterson, Jon <jon.peterson@neustar.biz> wrote:
> 
>> 
>> (2)
>> "Defining how a SIP implementation
>>  would provision multiple originating or destination identities is
>>  left as a subject for future specification."
>> 
>> I'm assuming this meant to say that defining how a STIR implementation
>> deals with multiple identities is what is left for future specification.
>> Is that correct? If so, it would be helpful to clarify.
> 
> Well, this means more aligning STIR with potential ways that SIP might
> signify that a request is "To" multiple destinations or "From" multiple
> parties, say. Even when PAI is present and is different from the From,
> there is still a general sense in personal communications that they are
> from some person (a persona even). We do have some vague notion that we
> want to work with meshed and centralized conferences, though, and don't
> want to close the door on that, which is why there's some forward-looking
> text about this here, and why the text is pretty broad.

Ok. I was reading this to mean the From+PAI case in current deployment, which is why it sounded confusing to me.

Thanks,
Alissa