[Ietf-community-india] Per Resource Events Protocol proposal at IETF
Rahul Gupta <cxres+ietf@protonmail.com> Sat, 02 September 2023 10:39 UTC
Return-Path: <cxres+ietf@protonmail.com>
X-Original-To: ietf-community-india@ietfa.amsl.com
Delivered-To: ietf-community-india@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF83BC14CE4B for <ietf-community-india@ietfa.amsl.com>; Sat, 2 Sep 2023 03:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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=protonmail.com
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 VMp1u2mcZojX for <ietf-community-india@ietfa.amsl.com>; Sat, 2 Sep 2023 03:39:00 -0700 (PDT)
Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch [185.70.40.135]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 88C59C14CE29 for <ietf-community-india@ietf.org>; Sat, 2 Sep 2023 03:39:00 -0700 (PDT)
Date: Sat, 02 Sep 2023 10:38:47 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1693651138; x=1693910338; bh=rpSJvEcSeH2xWkOTWQtMRiq1YugZQ8KH3lWd/WGoi9I=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=N7FwIConSvxQ7zQwQAzqfv9oCb1L1R67VarzAqgduYv5WlYFYv7H8NZv+FIkcIoSc bsKNq44QPTqg5akYr9LSKMmAan61v80oaHW3LDbz14ZBIT3Y10nzCtF4+wfC14YNnI 7ZD2CsPBiJ1ExnvPrSir4my+dLymgsy55A5PFVI4/Kqxz5RKexTlfI1QxmSygoVCwo bW/jNGOt0+tU/2JJIkBJuHjGrRE6d8bLw5T5mrZJZFf6w2ZTqe+M9uVQbwx5I5DPPi GLCHqRPZ3VaStxvtVPuhpTkIy7tbNu04CLOGDxevahOgkV3JUDWDQOQINe71cH7kZS dXudVwnSS891g==
To: "ietf-community-india@ietf.org" <ietf-community-india@ietf.org>, "info@iiesoc.in" <info@iiesoc.in>
From: Rahul Gupta <cxres+ietf@protonmail.com>
Message-ID: <gy8Jb8o4BZSQWuOJWfD6R-aDkPtMqtrOPtGzCY8rQe95UZ_nZSmkCJpbfnCGNA09OM98kpduy0Yz2izCdlhFRfq9D77Pj5xK88wvn-9Eza8=@protonmail.com>
Feedback-ID: 919445:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="------7ee4e23b8f7c24036d4f10d29455d7d60fcd6150aba0c1e1c33635d3e42e5453"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-community-india/mSnSOaCBAd9pco-QmUvA7cq4imI>
Subject: [Ietf-community-india] Per Resource Events Protocol proposal at IETF
X-BeenThere: ietf-community-india@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for IETF participants from India that is used to coordinate events internal to India." <ietf-community-india.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-community-india>, <mailto:ietf-community-india-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-community-india/>
List-Post: <mailto:ietf-community-india@ietf.org>
List-Help: <mailto:ietf-community-india-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-community-india>, <mailto:ietf-community-india-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2023 10:43:26 -0000
Hello IIESoc members, I am an independent researcher based out of Mumbai, currently proposing a new notifications specification called the Per Resource Events <https://cxres.github.io/per-resource-events/protocol> for standardization at IETF. The proposal are currently with Dispatch and HTTP-WG (Please check out the respective mailing lists). I would love to get the feedback from the IIESoc members on the proposal itself, as well as receive any guidance on how to navigate the IETF standardization process. Many thanks in advance, Best Regards, Rahul