From nobody Thu Jun 23 13:51:37 2022 Return-Path: X-Original-To: regext@ietfa.amsl.com Delivered-To: regext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF87C15A736 for ; Thu, 23 Jun 2022 13:51:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.807 X-Spam-Level: X-Spam-Status: No, score=-1.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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 (1024-bit key) header.d=pirorg.onmicrosoft.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 qW-Cm0EleJhT for ; Thu, 23 Jun 2022 13:51:33 -0700 (PDT) Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12lp2174.outbound.protection.outlook.com [104.47.59.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32125C15A730 for ; Thu, 23 Jun 2022 13:51:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YFcPubTwml4r316q3nAHUQzhLC/VKcpGVJD/quIo4FAslkzK/CJiivjV6P5d0IILKgRMtHRO5bQYyLhu+ujT/MAjdPcSmXiCZEUUOIBX42Ds9EIzc1CfL0PUbnzAAG4nmnzGvGR7KU0gC3JX8DWCKKuFzlCIDZfDP9fz5V/l4dnW2f+ng1/JVbPhXCwfhKXsCBcsi1ZhjZpj914nmr8+FZSDsmZXntUGahGTmsMqltPhPz9od6Fb48vCbvTYdcPr7z3fTV2uedGZJj1cJPYhxsITcYtD/1wFx6HaBXcTLsqqjLvNTnV38wJmJNQWnuzpHLoZL06ik/sWpfD7uk/dmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=N4privfpSDsV0NJTAXnXlUeM7bGDh0SHdu1jZ/uIBlo=; b=Gepvcpvy2W44UXuYTtMtPU+499EzlykA3/OsY5f40CCJnvCuJmFiWR+Z36Nnr5K9IwYeZwbjfwxbYyszQfHWJPmvBhiRw6ht1OjMlmQAxvAvBc7b43/NBYy0lSk7Ia7YtuVJL+4gxHbdMir9ZMBRZLTeKUrTLC7avq25Wtp3kA12m6j+qTYWtclvcbDNlMxnKcHXbsgI2soBMo668iFa3kYf7Hf1DEIjqn5tWTNsBTe7/FqHILQ/CxLMq3Mrq4pA2ia7deNypClw7emqMzpgRkPH8o7hN6/T6Gp8rdzbuPgGznZF0obGpc4tXaOlrv3kZ3BQ5C9PUCvo60LD5KDo8w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=pir.org; dmarc=pass action=none header.from=pir.org; dkim=pass header.d=pir.org; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pirorg.onmicrosoft.com; s=selector2-pirorg-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=N4privfpSDsV0NJTAXnXlUeM7bGDh0SHdu1jZ/uIBlo=; b=LvqaQKCbIhat9hVEGBjIg5LRYYRRxTp0GZKJGn5pHtxaMOjZIXUHpdYUK6+ZD6p/rBxcgMhkq5DMSqKh8RVnn83P5/ReSHx/xrZy3lLRCMy8BUQGQ28EvyS9MiRLvWpw5ylJ35Qq9w9RWPPuogBaJlDu11thhXvBCvoDM9qFPLE= Received: from BY5PR10MB4179.namprd10.prod.outlook.com (2603:10b6:a03:206::8) by BN8PR10MB3714.namprd10.prod.outlook.com (2603:10b6:408:b8::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5353.17; Thu, 23 Jun 2022 20:51:25 +0000 Received: from BY5PR10MB4179.namprd10.prod.outlook.com ([fe80::840a:d0d9:d57:9f5f]) by BY5PR10MB4179.namprd10.prod.outlook.com ([fe80::840a:d0d9:d57:9f5f%7]) with mapi id 15.20.5373.015; Thu, 23 Jun 2022 20:51:25 +0000 From: Rick Wilhelm To: "regext@ietf.org" , Jim Gould CC: "regext@ietf.org" Thread-Topic: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-redacted-07.txt Thread-Index: AQHYcSh2E3FbB/ykzk+XXxiE7NxZRa1dmKoA Date: Thu, 23 Jun 2022 20:51:25 +0000 Message-ID: References: <165358710762.5821.7136050682512315839@ietfa.amsl.com> In-Reply-To: <165358710762.5821.7136050682512315839@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=PIR.org; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 02fae6ad-75cf-402d-6484-08da555a2366 x-ms-traffictypediagnostic: BN8PR10MB3714:EE_ x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: s3OkETLlzNFi2Er58GsFIjQAscx26k018j/N9931BB8he0U3WQg//Cs2tA1FN0elP4ayGTSUZz7C3PnCU9fhobAPUqsxBqp7AStevC+H11l2yNxzg2DZnuPq15vFE/MYrOtQbV2BTgGi69BgDhkuTFvKW1MdE/UZjOjzx2b1oqSOTx8ibtJAMblNDlL7EDtLD7B7EqUTPPyrwnp3V0dcXCu8tE3RPUMttym2tuKQnvKeE6vUirbxVRAv3iGGiPNh55fDScfj+G9zB1OXxBKmKKAXKn1+dsE7FXKy3Q/KwBZvEPfuGjW0bLifBojr9i88TmMWe+Hb9EQbi8ebiOV2Fha4wLRDW5u01JaO30+lmkv2YvKdSPCDYVNXsvULjLnI+nGjqW2esd/KWUcaXiHBYe4CMUmqbJjnq26neeb6mjgF2tEtOTv1L7Qt+1/TcsHzHtWwqaZEDpjJVewK+/TS34ZjV7oqJi5Ec9GbSVlB9MjTSw50+NphYp+0c9QcfmyyMOYtTBGy2JFooAtNzzWT+28s7TxHmPGxLZX5cSsJgg3qoV6a6TjLQkGynymYFLuSNsohRO82UsClmWGmOgRmtDJq9bITfYx0zlzOvCqbDHpmq0oVPfn2CHBSFzKT+u+iaLqi34PQVePoKmUeyvKrIb6kCIvCDYBvGcVpnup6tB6prZ2lLZtF6jeJQYyyjjHPbeIIO99+Ceakvqz98XmQlXtHnpS0ELNLNnvt+x7ZDUVuCWy5bALnFVd94uI9CdDhZ9sW493RbHqZVrTT6iDCGiFbLEtz4GIfH1DngPSrlJ1GIVanTcdhJDOkNFZTLWdfeURvmOVdcy4IEvUsXC0coVNBH14+Tbch9Dj5hKb5jkE= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR10MB4179.namprd10.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(4636009)(39840400004)(376002)(136003)(396003)(366004)(346002)(316002)(55016003)(8936002)(52536014)(38100700002)(9686003)(38070700005)(26005)(86362001)(41300700001)(122000001)(478600001)(66574015)(110136005)(2906002)(5660300002)(33656002)(91956017)(186003)(166002)(966005)(64756008)(66446008)(66476007)(66946007)(8676002)(76116006)(66556008)(4326008)(71200400001)(53546011)(83380400001)(7696005)(6506007); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?uSaOaFQ0O8YdqLoUINbKRkoIB69Qww2LgYPUtpC4mSA1TbRN9ojPPZp/?= =?Windows-1252?Q?Xb3tlkLyvQFx7cjFN1hlNCbfthhDyCIGaYWNAW9AqdsB0HI6G2cXxOXN?= =?Windows-1252?Q?aC9L6Ma6nx2afJdO9VlscipurIyKXqDEZMBmuxUkrbg/V4HEBf/XUGdd?= =?Windows-1252?Q?g24w7kxmSK9LAC4LBvNIH4EAGGDKuM2u2V8V3nV8nw/z3hSh5EOJzGUY?= =?Windows-1252?Q?+YdAq2CQEXdiQDfr4hwusqorBPTJ61GQv+S0MkKSht+7eyFSkk+xZlEw?= =?Windows-1252?Q?XAIT6wudiNr0ke5a+ZIhb4Og9x5PurvpjLUEtzijzsyTAv7HB1cAod7K?= =?Windows-1252?Q?jZOMcnq47UpmcMUj3cpYmohmRpTQdGFs5gh0xWjKpcTzi0OX2Pqeta+M?= =?Windows-1252?Q?kL6nvzDCOOB5ffYjWzZ/+4afFOCfXPEIEZOf9CL7J50t44kdO2UkGWWm?= =?Windows-1252?Q?sr0/Q+YHHN/SOrV+4C07k6C30Xz86JPVmFePIM8v6CXWoV47M+NuJ16C?= =?Windows-1252?Q?43Ds3TGw2Nm5i1z7i5kmhEj7jP5ks7dfAPPjFXUx25JWoRJe8CdMM0S8?= =?Windows-1252?Q?/nQVeTnkRvM7dfKfMmbu2iv0lQmoYwNxWUAVw6/alGO6YFvsHBDHWiyc?= =?Windows-1252?Q?J9Pje9NnyA38GR4LiVstiG9Y055BHiXbBADYBtuHwtRNeuTSq4xYwD6K?= =?Windows-1252?Q?xgMn85TkDNLKFcgZ6sT5JBBRMWvQtJPXvKJnTarS2Odfq5ird7eqbtWt?= =?Windows-1252?Q?xM8oLuVDTZuRGeriso0R3Rz6uVmk/gfYT85ifMZ7hZAXnteMuSEt8IpF?= =?Windows-1252?Q?yG1nqRcCxjzRjsLgOV5Y9c2S3NM2INg1ajvZ0u1Y+iCYd8lpeewHkJFZ?= =?Windows-1252?Q?Um7KnGNZ9awlzmstT7dzxr/BbKSEdrFDXj99fXnw3drTA20ZoRTWhX9S?= =?Windows-1252?Q?eU16p3epAfONXtG2MfBGxlWLaEbJicFeDxHfOFVuwbstvzI1EmY6wsOz?= =?Windows-1252?Q?5SG9uKclQorckamKeVCX84lPVT8VtYq3WsXtDY+ZHr4Yf94yXryiLE6A?= =?Windows-1252?Q?WTaNMhTrjKz1YC0BCICZwnm6z5/KnQTryYRvZx/JQaxfMOvktTevN8Dv?= =?Windows-1252?Q?YPJ/oJvw9a7cZpccbijVUHbIO4Ayvcz3m+Cp/HkGKFMK2gkGc0bkoTTQ?= =?Windows-1252?Q?m05EEWhzLzeXCtm+nlga+PNCB+YB4E+nExlkwIG7xUUclJQnqsEB+Rb5?= =?Windows-1252?Q?GXvMHFYGYMP7LnJL1IwB6Hu+1cW0IvxCcD2n/BauWF222hX1xa24IMPJ?= =?Windows-1252?Q?LeFYyuE999hnqAtJG7CGZtcW7o9zVBQnHVim73wP5RoH6KpnnEGR4P10?= =?Windows-1252?Q?Lo/iNCGdkPYWGH+mo0Lzk3A9P5S5NwnJAm9DRcs8wv3RjsGmCPxQiMGX?= =?Windows-1252?Q?2LTrwnoGrhDyks9RTkpBaUrQrexshzbqKjScR4j4fZ2oVmdp1dFnYelD?= =?Windows-1252?Q?HpGghC5F+6Hk+gne5LAWoC/w6PC++j/io8AOrbBhbgRQfeuedWiX9/Ze?= =?Windows-1252?Q?0UPdbxROay88iRtR0lgelF8Sy3TOU18LQPKNmMPrw9td9eOd76E1q/g5?= =?Windows-1252?Q?LzsS1+foDd+T+D/23iNlGtTPDAVnUcMTixmyfsH6lbE/zPTWzRYoyMpR?= =?Windows-1252?Q?WJLku13MQR+FJfY/ox8XFIIsC8poUnIYVTHhe6ZIAtz1kaqNyrQCMQ?= =?Windows-1252?Q?=3D=3D?= Content-Type: multipart/alternative; boundary="_000_BY5PR10MB417953A092E3F5A118FFA44AC9B59BY5PR10MB4179namp_" MIME-Version: 1.0 X-OriginatorOrg: pir.org X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BY5PR10MB4179.namprd10.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 02fae6ad-75cf-402d-6484-08da555a2366 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jun 2022 20:51:25.5521 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 6c8ced78-b98f-4fa4-b6df-38beaa0d935d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: A+qfiQoRvGO0yHlrOag5V1wyNXix79i5kZfsa/zNi8V1ebg2SPQf68PoCVR/1kHEhZrz5NjOF4BfiT8PhragAw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR10MB3714 Archived-At: Subject: Re: [regext] [EXTERNAL] I-D Action: draft-ietf-regext-rdap-redacted-07.txt X-BeenThere: regext@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Registration Protocols Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2022 20:51:37 -0000 --_000_BY5PR10MB417953A092E3F5A118FFA44AC9B59BY5PR10MB4179namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Jim, et al, While there is clearly work going on to determine a direction related to th= e conformance values, I wanted to invest some time to give a careful review= of the current rdap-redacted draft to have it better prepared to progress = after the WG comes to some consensus. Overall, I think that this draft looks really good. I=92m hoping that we c= an figure out the conformance thing soon. In that context, and in the order of the document, here is some feedback. = Most of these are small, trending toward nit. 1. Introduction Regarding: A redacted RDAP field is one that has data removed from the RDAP response due to the lack of client privilege to receive the field. As has been discussed elsewhere and is presented in this document, the conc= ept of =93redaction=94 is broader than =93removal=94 and also includes =93e= dit=94. Additionally, there may be any number of reasons why a response wo= uld be redacted (which would most certainly include =93lack of client privi= lege=94, but could also include other reasons. To that end, I would sugges= t the following edit: A redacted RDAP field is one that has data in the RDAP response edited due to policy, for example, the lack of clie= nt privilege to receive the field. 3. Redaction Methods Regarding: The redaction of RDAP fields fall into the two categories of Redaction by Removal Method (Section 3.1) and Redaction by Empty Value Method (Section 3.2), defined in the following sub-sections. I think that this paragraph needs updating to account for (the recently add= ed) Section 3.3. As in: The redaction of RDAP fields fall into the two categories of Redaction by Removal Method (Section 3.1), Redaction by Empty Value Method (Section 3.2), and Redaction by Replacement Value Method (Section 3.3), defined in the following sub-sections. 3.1 Redaction by Removal Method Nit: Suggest putting a paragraph break before =93An example of redacting= =85=94 in order to better separate the example from the normative text. 4.2 =93redacted member=94 Regarding: The "redacted" member MUST be added to the RDAP response when there are redacted fields. Suggest that this is updated to have the MUST unambiguously cover the case = when there is exactly 1 redacted field The "redacted" member MUST be added to the RDAP response when there Is one or more redacted fields. Regarding: "method": OPTIONAL redaction method used with "removal" indicating the Redaction By Removal Method (Section 3.1), "emptyValue" indicating the Redaction by Empty Value Method (Section 3.2), and "replacementValue" indicating the Redaction by Replacement Value Method (Section 3.3). The default value is "removal" when not provided. I think that there is punctuation needed and a minor ed in the first line t= o improve clarity. Suggested edit: "method": OPTIONAL redaction method used; with one of the following val= ues: "removal" indicating the Redaction By Removal Method (Section 3.1), "emptyValue" indicating the Redaction by Empty Value Method (Section 3.2), and "replacementValue" indicating the Redaction by Replacement Value Method (Section 3.3). The default value is "removal" when not provided. Hope that helps. Questions welcome. Thanks Rick From: regext on behalf of internet-drafts@ietf.or= g Date: Thursday, May 26, 2022 at 1:46 PM To: i-d-announce@ietf.org Cc: regext@ietf.org Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-redacted-07= .txt CAUTION: This email came from outside your organization. Don=92t trust emai= ls, links, or attachments from senders that seem suspicious or you are not = expecting. A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Registration Protocols Extensions WG of th= e IETF. Title : Redacted Fields in the Registration Data Access Protocol (RDAP) Res= ponse Authors : James Gould David Smith Jody Kolker Roger Carney Filename : draft-ietf-regext-rdap-redacted-07.txt Pages : 37 Date : 2022-05-26 Abstract: This document describes an RDAP extension for explicitly identifying redacted RDAP response fields, using JSONPath as the default expression language. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-redacted/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-redacted-07.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-regext-rdap-redacted-07 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-dra= fts _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext --_000_BY5PR10MB417953A092E3F5A118FFA44AC9B59BY5PR10MB4179namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Jim, et al,

 

While there is clea= rly work going on to determine a direction related to the conformance value= s, I wanted to invest some time to give a careful review of the current rda= p-redacted draft to have it better prepared to progress after the WG comes to some consensus.

 

Overall, I think th= at this draft looks really good.  I=92m hoping that we can figure out = the conformance thing soon.

 

In that context, an= d in the order of the document, here is some feedback.  Most of these = are small, trending toward nit.

 

 

1. Introduction

 

Regarding:

 

A redacted RDAP fie= ld is one that has data

   remove= d from the RDAP response due to the lack of client privilege to<= /span>

   receiv= e the field.

 

As has been discuss= ed elsewhere and is presented in this document, the concept of =93redaction= =94 is broader than =93removal=94 and also includes =93edit=94.  Addit= ionally, there may be any number of reasons why a response would be redacted (which would most certainly include =93lack of client pr= ivilege=94, but could also include other reasons.  To that end, I woul= d suggest the following edit:

 

A redacted RDAP fie= ld is one that has data

   in the= RDAP response edited due to policy, for example, the lack of client privil= ege to

   receiv= e the field.

 

3. Redaction Method= s

 

Regarding:

 

   The re= daction of RDAP fields fall into the two categories of

   Redact= ion by Removal Method (Section 3.1) and Redaction by Empty

   Value = Method (Section 3.2), defined in the following sub-sections.

 

I think that this p= aragraph needs updating to account for (the recently added) Section 3.3.&nb= sp; As in:

 

   The re= daction of RDAP fields fall into the two categories of

   Redact= ion by Removal Method (Section 3.1), Redaction by Empty

   Value = Method (Section 3.2), and Redaction by Replacement Value<= /p>

   Method= (Section 3.3), defined in the following sub-sections.

 

 

3.1 Redaction by Re= moval Method

 

Nit:  Suggest = putting a paragraph break before =93An example of redacting=85=94 in order = to better separate the example from the normative text.

 

4.2 =93redacted mem= ber=94

 

Regarding:

 

   The &q= uot;redacted" member MUST be added to the RDAP response when there

   are re= dacted fields.

 

Suggest that this i= s updated to have the MUST unambiguously cover the case when there is exact= ly 1 redacted field

 

   The &q= uot;redacted" member MUST be added to the RDAP response when there

   Is one= or more redacted fields.

 

 

Regarding:

 

   "= method":  OPTIONAL redaction method used with "removal"= indicating

   &= nbsp;   the Redaction By Removal Method (Section 3.1), "empt= yValue"

   &= nbsp;   indicating the Redaction by Empty Value Method (Section 3= .2), and

   &= nbsp;   "replacementValue" indicating the Redaction by = Replacement Value

   &= nbsp;   Method (Section 3.3).  The default value is "re= moval" when not

   &= nbsp;   provided.

 

I think that there = is punctuation needed and a minor ed in the first line to improve clarity.&= nbsp; Suggested edit:

 

   "= method":  OPTIONAL redaction method used; with one of the followi= ng values: "removal" indicating

   &= nbsp;   the Redaction By Removal Method (Section 3.1), "empt= yValue"

   &= nbsp;   indicating the Redaction by Empty Value Method (Section 3= .2), and

   &= nbsp;   "replacementValue" indicating the Redaction by = Replacement Value

   &= nbsp;   Method (Section 3.3).  The default value is "re= moval" when not

   &= nbsp;   provided.

 

 

Hope that helps.&nb= sp; Questions welcome.

 

Thanks

Rick

 

 

From: regext <regext-b= ounces@ietf.org> on behalf of internet-drafts@ietf.org <internet-draf= ts@ietf.org>
Date: Thursday, May 26, 2022 at 1:46 PM
To: i-d-announce@ietf.org <i-d-announce@ietf.org>
Cc: regext@ietf.org <regext@ietf.org>
Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-reda= cted-07.txt

CAUTION: This email= came from outside your organization. Don=92t trust emails, links, or attac= hments from senders that seem suspicious or you are not expecting.


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
This draft is a work item of the Registration Protocols Extensions WG of th= e IETF.

Title : Redacted Fields in the Registration Data Access Protocol (RDAP) Res= ponse
Authors : James Gould
David Smith
Jody Kolker
Roger Carney
Filename : draft-ietf-regext-rdap-redacted-07.txt
Pages : 37
Date : 2022-05-26

Abstract:
This document describes an RDAP extension for explicitly identifying
redacted RDAP response fields, using JSONPath as the default
expression language.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext= -rdap-redacted/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-regext-rdap-redacte= d-07.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-regext-rdap-red= acted-07


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-dra= fts


_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

--_000_BY5PR10MB417953A092E3F5A118FFA44AC9B59BY5PR10MB4179namp_--