Re: [GNAP] Subject Identifiers draft - request for volunteers

Yaron Sheffer <> Tue, 01 March 2022 13:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7259A3A0938 for <>; Tue, 1 Mar 2022 05:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Status: No, score=-2.106 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, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fZA7jbQeHIoI for <>; Tue, 1 Mar 2022 05:40:02 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B3AEA3A0933 for <>; Tue, 1 Mar 2022 05:40:02 -0800 (PST)
Received: by with SMTP id x14so7422018ill.12 for <>; Tue, 01 Mar 2022 05:40:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-transfer-encoding; bh=H/exNrPCe5JpD9M5X4q0qw3sscMWdXrv5doU93XNU9g=; b=QlHBeuHFsZ5NfAff9M32M7sN7WgVe6COLFy5yqbmzyfV7TMxcXap0yRq6k2/Nll/zd MNIx72IbnCgzJjEPwc9U0jgjQTJNiSokmg7E3Dca1idjGCviTwDDK+i+DbkoG0+A3hV0 8K5iBlPIbUTZQqOqXeVmFkn+Cg/wzbCAj3K5k2l/RvvR/4/N17scpnUzP8plmtV6MGvj rf01osQPEV8/IVQ5z9Da1En61wVStVy/BZMUMmJ8NImdrrKED8qhS8NZpdlh+oljq/+h CcvHV0NXPxpWR9Fh7Fo0fbYuQr/+0hgkxCIw2gbfyDQuoCxTgoW+w8QzeTyFzC1yw7U1 GKWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=H/exNrPCe5JpD9M5X4q0qw3sscMWdXrv5doU93XNU9g=; b=VAPXtmrtj+ZuwJZjVNLZkE3WjqaFeLQ1DViqnq9E8hG9ocLtAUm0h19y7IhMsiO2zh 3ooPiM4jbMVMUWzbBzZAz3xEMrxcaZpl3ycWCcZb6p/ewpm49M/sxQbjg180aeOu7Qdm SITze4hQ4w/Vny6iI8fgGs6ucQ5+ZmAx3G0Gfrt2QXHKaiLTAISalmgdkAZ1jMiLWp07 B7C0a5sm2AuZj467QYxjuBWKH1+/r3P+6JrccG/qpSpifGQcfGYeSIL9a5xoDdTjamLb xyHlAxAvg9I0/2oPO1erZI20ae+h9bCTKZX1R+T7UY60s+dF8XD2dXkfFfgYvr9M0EzR +geg==
X-Gm-Message-State: AOAM5331Fn5jy5Qh6rWpnvhjBjb8T++vbwSO5J19Rln5ydpNDNP1bX3G ruO7sHlD/QsPHfV5XvSSOF7x7iX5yTU=
X-Google-Smtp-Source: ABdhPJwiiPiSUZooFj0NUJ4q/i0yEHtdKrTCQ2sRcAmEK2xWRo/Soy40gFoo2tHC8YEMR3ydEp7Y4Q==
X-Received: by 2002:a92:b0b:0:b0:2c2:74db:9630 with SMTP id b11-20020a920b0b000000b002c274db9630mr22904675ilf.170.1646142001228; Tue, 01 Mar 2022 05:40:01 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id e17-20020a5d8ad1000000b00644d51bbffcsm3868710iot.36.2022. for <> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2022 05:40:00 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.58.22021501
Date: Tue, 01 Mar 2022 15:39:57 +0200
From: Yaron Sheffer <>
To: GNAP Mailing List <>
Message-ID: <>
Thread-Topic: [GNAP] Subject Identifiers draft - request for volunteers
References: <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [GNAP] Subject Identifiers draft - request for volunteers
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 01 Mar 2022 13:40:06 -0000

Thank you to all who volunteered to help, this is very much appreciated.

Prachi will be joining the author team for this draft and I hope we can conclude and publish it soon.



    On Sun, Feb 27, 2022 at 8:34 AM Yaron Sheffer <> wrote:
    > Hi,
    > The GNAP protocol has a dependency on the Subject Identifiers draft [1] from the SecEvent working group. That draft has been around for a long time and in fact has just been updated by the authors (much appreciated!), but we’ve had a hard time moving it across the finish line at the SecEvent group. I am looking for one or more volunteers to join as co-authors, preferably people who are *not* authors on the GNAP protocol.
    > The Subject ID draft should go into an abbreviated second WG last call, and then assuming everything goes well, into IETF last call and IESG review. The main task of the new author(s) would be to address IESG comments in a timely manner and move the draft to publication.
    > If you are new to the IETF, this is a great opportunity to familiarize yourself with its publication process.
    > Please get back to me or Leif for any additional details.
    > Thanks,
    >         Yaron
    > [1]