From nobody Sun Feb 27 08:34:18 2022 Return-Path: X-Original-To: txauth@ietfa.amsl.com Delivered-To: txauth@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59F5F3A129A; Sun, 27 Feb 2022 08:34:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 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, 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: 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 apd94bgrCUn0; Sun, 27 Feb 2022 08:34:10 -0800 (PST) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 75A693A1296; Sun, 27 Feb 2022 08:34:07 -0800 (PST) Received: by mail-wm1-x330.google.com with SMTP id l1-20020a7bcf01000000b0037f881182a8so4486687wmg.2; Sun, 27 Feb 2022 08:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :mime-version:content-transfer-encoding; bh=W+ldaJtfbhCxnMfu1POgfzyZVatT6VoEXCoOkkAmyA4=; b=iUt5queMjHGs1aiZp7eUVUIrpbz9nS3NnfF0Jh8k6do7OSAo28JZvEEWGetuBaUfF1 CxIk+MU41fe+NhzGY0oUMb22wceq07v1q1W6UhZQoIWg285b+Etdu1rl5IO6VwMGpahH vT80l+ji5/+yD6i3zyCLwxM0PeQCLlb35dOQ/+u6XmdLKTpMf1c+KBgy745lyF762m9o 33X30TA8MahJf6cUsBvMAARqbdc6JaznKWc9yXKMXbxp9ogRwj5080CA4aykJQuBqYfz v3LJh5Qi/pjXWt/L1q3XV/WKBNnSKaz+/EoyNHiTMHLihVyhKAnZwkp+SBQSwJ9IVezx 4Lvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:mime-version:content-transfer-encoding; bh=W+ldaJtfbhCxnMfu1POgfzyZVatT6VoEXCoOkkAmyA4=; b=wDzxI1eeHfC/S1dR2DAXpvjk9jElQnWQG638mEXMENqhxmIo78hjK+CzrDO1ZuNjRO RC7elP3oHn50gYwe0fGChxhNWbAlnr6nnaLjLZfOHTVIIcaSQRZKqWE4iVeSZIRky5fb aY5SO2lCjuuIdydmP8/e5SxxgJ+ZfLOSuF9siW+0MuvxausOAt8iYMpQkr3zgTm8j/s6 1D2ox1rwnX6Zufq5udRejw54W0O0dlWG3JJ9M2V/ZvIorXv9z7vBkuxIpZ0ul8fQR4w+ 428llaJIOJCduU+I7QJ77b6suxzMtynkNDhhdiVoQ8eWgUbwi6ySQy/fpGT8YHOZYhGX 8D9A== X-Gm-Message-State: AOAM531depvdbkeFLLnqdD1SR/A0r3+7FsG9upqqGM5zt3Gkw+DaaQsA TTDd07R391kWaSl15ZF7qk9lohaxDSI= X-Google-Smtp-Source: ABdhPJzcXZnWhD8gOz57AF+a1ax2jnICp16vDMwRCjCCVJL65XlHIDOMRITST3n+lQI3D3Vx9XZSUg== X-Received: by 2002:a05:600c:3d13:b0:37b:b8e5:ed80 with SMTP id bh19-20020a05600c3d1300b0037bb8e5ed80mr10282752wmb.183.1645979645098; Sun, 27 Feb 2022 08:34:05 -0800 (PST) Received: from [192.168.68.108] (IGLD-84-229-146-220.inter.net.il. [84.229.146.220]) by smtp.gmail.com with ESMTPSA id c14-20020a7bc84e000000b0038100c9a593sm15705162wml.45.2022.02.27.08.34.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Feb 2022 08:34:04 -0800 (PST) User-Agent: Microsoft-MacOutlook/16.58.22021501 Date: Sun, 27 Feb 2022 18:34:03 +0200 From: Yaron Sheffer To: GNAP Mailing List CC: Message-ID: Thread-Topic: Subject Identifiers draft - request for volunteers Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Archived-At: Subject: [GNAP] Subject Identifiers draft - request for volunteers X-BeenThere: txauth@ietf.org 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: Sun, 27 Feb 2022 16:34:16 -0000 Hi, The GNAP protocol has a dependency on the Subject Identifiers draft [1] fro= m 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=E2=80=99= 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 peo= ple 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. Th= e main task of the new author(s) would be to address IESG comments in a time= ly manner and move the draft to publication. If you are new to the IETF, this is a great opportunity to familiarize your= self with its publication process. Please get back to me or Leif for any additional details. Thanks, Yaron [1] https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifier= s/