From atul@sgnl.ai Fri Mar 15 00:02:33 2024 Return-Path: X-Original-To: secdispatch@ietfa.amsl.com Delivered-To: secdispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5FBC14F5FB for ; Fri, 15 Mar 2024 00:02:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.085 X-Spam-Level: X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sgnl.ai Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPECtnB8kyPe for ; Fri, 15 Mar 2024 00:02:29 -0700 (PDT) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37540C14F5F5 for ; Fri, 15 Mar 2024 00:02:28 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-5dca1efad59so1405243a12.2 for ; Fri, 15 Mar 2024 00:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sgnl.ai; s=google; t=1710486148; x=1711090948; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=XwRRs/8isnEF2AeUGMs4L+FMdXMRCH14laTBIf/R48U=; b=BzhB07pgO7ISWevRlNsY+QpOjxO5HUcxsm2TjOUX+ZIpGcVsvdbFcBnI4DNB0GLJSE s7cfGBxvpH8sQ+Zcj0ytVyiJYCoa+GuNMSgUpJE/z8HbNUa0FqhcEOMm5WkG7JYajeEk J0rw4gMHRwWIqIWCy+q7n1oy8VHcNY+bvXrjN6dF+Y1vwZ+qtiYv7CuZ4DgcDWVfT6Ei OVsu+uKzZX4XfnXqvOHuva81a+sLQ5i38E4N4Z7LD41wEAmgN48movSdU00P9raKUSAb gf3EPIUnFRAPPTvuOlVvBaQGqEhRL71+1cKqgyPrMlibFnBLH3J7tjuJOZugcYgn04Xl n2jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710486148; x=1711090948; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=XwRRs/8isnEF2AeUGMs4L+FMdXMRCH14laTBIf/R48U=; b=mNCD3+WTFMvv/KuLIv9yqlJmUP6HNOONZ6TTDwWHguFfH9cOQSgWmWjb0M/GrUPxZ9 DGHcwkA8Yjm9vLIDQw9Ay2K+MS6CDMh7aDfKFG60VfziD61Np4rp+hrMB0gGRnUIr2/N mNNHB4UuTUt2GhGguZ9fuqJn0+d8Sfm8PwFlmpNO7jpqZgT+knQUg49JtE89amjEFz6G bhuHUwDlycge6YdeJ2PSnBjSd/2sUMjRrXiCMrGDmxXUh04DZzXRLjX0T/9E1YPb4+Ap 5uuI3Qtz2Rhqt564qTnEdU341TzkNjfkeFyfua2f+dxQiHp9uDLqROeaBXa1uyebK9Gy +Qcg== X-Gm-Message-State: AOJu0YzdoVzezaWV0cKJGmBtXa4jhgINLCWIYTV58wDm/9HiA+/Ak3c2 VvEO8wo9Ku5GkXBIVqs2EazRPZpv/ze5IFvawKmKPSFa8m/TVlL+dEodf68sRcuRhdtn7yTFVND /ha229qvNefx3TQrv5wEWnkqiCaNUscPY+YGXmi0oV1hjAi5n4G/j3A== X-Google-Smtp-Source: AGHT+IE8TvldGQubxU45UM+6PsNCnKxZg0YGZPdp7mnmFe8z1ilPAm62MvK3IrvOBGOHAvKDQDWneAwS5paUHo5dVYc= X-Received: by 2002:a17:90b:1008:b0:299:58af:c873 with SMTP id gm8-20020a17090b100800b0029958afc873mr3755568pjb.10.1710486147551; Fri, 15 Mar 2024 00:02:27 -0700 (PDT) MIME-Version: 1.0 From: Atul Tulshibagwale Date: Fri, 15 Mar 2024 12:32:11 +0530 Message-ID: To: secdispatch@ietf.org Content-Type: multipart/alternative; boundary="00000000000037f6250613ad972e" Archived-At: Subject: [Secdispatch] Two topics of discussion for the Sec Dispatch session X-BeenThere: secdispatch@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Security Dispatch List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2024 07:02:34 -0000 --00000000000037f6250613ad972e Content-Type: text/plain; charset="UTF-8" Hi all, There are a couple of topics for which I have been seeking answers. I don't know if these are appropriate topics for the saag session next week. I will be attending remotely, and can prepare a presentation for the second point below if required. 1. *Errata to RFC 9493* There is an errata required for RFC9493 (Subject Identifiers for Security Event Tokens). The errata request is here . The errata requests a change to the registry created by this RFC, and there was consensus on the mailing list that the errata should be accepted and the appropriate change reflected in the IANA registry. However, since the WG is completed, there was no clear identification of how to go about making these changes. If there is discussion required on this topic, we should have it in the meeting in Brisbane. 2. *New PushPull Delivery Proposal* While we currently have specified Push delivery (RFC 8935 ) and Poll delivery (RFC 8936 ), we are seeing a clear requirement in the OpenID Shared Signals Working Group (SSWG) where a Transmitter is also a Receiver, and we would like to have a way of symmetric asynchronous event delivery. I would like to propose a new spec for this, but since the WG is closed, I wanted to know how to go about doing this. I realize the date for proposing new ideas for IETF 119 is past, but I can propose it after IETF 119 and discuss it in Vancouver. The topic I would like to discuss in IETF 119 is: What is the venue to propose this new idea for a combined "push and pull" delivery mechanism? Thanks, Atul -- Atul Tulshibagwale CTO --00000000000037f6250613ad972e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
There are a couple of topics for which I have = been seeking answers. I don't know if these are appropriate topics for = the saag session next week. I will be attending remotely, and can prepare a= presentation for the second point below if required.
  1. = Errata to RFC 9493 There is an errata required for RFC9493=C2=A0(Subject Identifiers for= Security Event Tokens). The errata request is here. The errata requests a change to the reg= istry created by this RFC, and there was consensus on the mail= ing list that the errata should be accepted and the appropriate change = reflected in the IANA registry. However, since the WG is completed, there w= as no clear identification of how to go about making these changes. If ther= e is discussion required on this topic, we should=C2=A0have it in the meeti= ng in Brisbane.
  2. New PushPull Delivery Proposal While we curr= ently have specified Push delivery (RFC 8935) and Poll delivery (RFC 8936), we are seeing a clear req= uirement in the OpenID Shared Signals Working Group (SSWG) where a Transmit= ter is also a Receiver, and we would like to have a way of symmetric asynch= ronous event delivery. I would like to propose a new spec for this, but sin= ce the WG is closed, I wanted to know how to go about doing this. I realize= the date for proposing new ideas for IETF 119 is past, but I can propose i= t after IETF 119 and discuss it in Vancouver. The topic I would like to dis= cuss in IETF 119 is: What is the venue to propose this new idea for a combi= ned "push and pull" delivery mechanism?
Thanks,
Atul

--

Atul Tulshibagwale

C= TO

--00000000000037f6250613ad972e--