IETF Logo Mail Archive

Re: [Id-event] Dealing with issuer conflict

Dick Hardt <dick.hardt@gmail.com> Thu, 18 May 2017 13:42 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A60126C26 for <id-event@ietfa.amsl.com>; Thu, 18 May 2017 06:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DtChhlMOpZJv for <id-event@ietfa.amsl.com>; Thu, 18 May 2017 06:42:24 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 3A7B91294D4 for <id-event@ietf.org>; Thu, 18 May 2017 06:37:10 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id v27so34037093qtg.2 for <id-event@ietf.org>; Thu, 18 May 2017 06:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ol8qo2HDljbv6dUqORq9eS4XKSYGkTb9OgaNKUSQElI=; b=onlFZgBXAL1kcy1sv7k3JjYUgkKHiVCbyvQp2DVZ1HZRH8zec75i8ca89B3nqeNJVW 5/uHSc5IIO4/KJWba7ycY9AoBnvzPfartRNyb30/Q1InfYrFkPQmvhituUAeAoiWSK7Z OLRwh9hLHtKxnF4AJLwVXCbvV1rSQGTq1NAwOqZEOTLNEkhHGI0Jyw4XInQJWNwkGbrq 8xjvKmyhZS79w+apAS9XKx+siPPJ2zz9QAIFuQ4E5JYtL9Jr36YPUowkyjZANJ0a0cUP h+67pJBLVZEWs/EBDifvJllRKrba2TrTMC/G//H8Vx9f8+mg7w2ozcIoUtsPtuwwq89Y gsGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ol8qo2HDljbv6dUqORq9eS4XKSYGkTb9OgaNKUSQElI=; b=Oo09PzeiaK9srVM1vilij/+HaoOESckcqBTpwFlyUDXw4QC0P0QJLu8uOy4rBvYDmr 64C99iM52zkMuBeU6GLMlmGX323Xkow+/jDuArmzGt6WzdKgwS0Ftjk1GVVdTB/QuFWH /I9XwtaDZ3ZWVd4rhufna3/L7K1uozaFjE6BqJbhKTAh6xdFDxDKNoHyj2Ju/4uuA+TT vijjnLpNvxmOrpm3agAFIkTazmQAUPpBiaoYWwm1BrcJuYloFxQ5Vb/qYkYKCBdPsriw s2YdMDJOP/2PrsmLqtDp3/+7tCiIU+1v0H4IqR317sSQaHtvywzAWvYDNxR03WaftM8l fadQ==
X-Gm-Message-State: AODbwcBEy9ZPHA/3j/BbkZKn5TuGJy5DtU/mDXxTvdMfnyc2NDo0oH8h iWXAmWosvIYiU9RrxVkG3eQPqg5hFQ==
X-Received: by 10.200.38.11 with SMTP id u11mr4196909qtu.293.1495114629333; Thu, 18 May 2017 06:37:09 -0700 (PDT)
MIME-Version: 1.0
References: <D1129EE9-8D49-4262-A569-FF373490EB85@oracle.com>
In-Reply-To: <D1129EE9-8D49-4262-A569-FF373490EB85@oracle.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 18 May 2017 13:36:56 +0000
Message-ID: <CAD9ie-unodo_BgMdH-iT64U6n7A4H_kEVOLCViWqDuLfRSRgSg@mail.gmail.com>
To: ID Events Mailing List <id-event@ietf.org>, "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="001a11411f06614c1d054fcc802c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/JbIW-oVgmkxZRaUn2vsBBYILA_Q>
Subject: Re: [Id-event] Dealing with issuer conflict
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2017 13:42:26 -0000

Phil, would you clarify the use case and the requirement to ensure everyone
on the list is aligned? Thanks

On Wed, May 17, 2017 at 9:45 PM Phil Hunt (IDM) <phil.hunt@oracle.com>
wrote:

> In many cases where we are talking about events (eg risc) there is no need
> for extra claims other than the event type itself.
>
> It occurs to me that in the case of RP issued events the current sectoken
> format requires an embedded iss to deal with the conflict with the set
> issuer. It seems to add a lot of complication for most events.
>
> What if we defined a new sectoken top level attribute 'subIss' to mean
> "subject issuer" and keep iss reserved for the SET issuer.
>
> I would suggest this as a recommended attribute even when iss and subIss
> are the same for parsing consistency.
>
> Thoughts?
>
> Phil
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
-- 
Subscribe to the HARDTWARE <http://hardtware.com/> mail list to learn about
projects I am working on!

v2.23.0 | Report a Bug | By Email