From nobody Mon Jun 3 08:30:59 2019 Return-Path: X-Original-To: art@ietfa.amsl.com Delivered-To: art@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5A84120392 for ; Mon, 3 Jun 2019 08:30:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it 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 NYAoBb6rv8l4 for ; Mon, 3 Jun 2019 08:30:56 -0700 (PDT) Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63750120395 for ; Mon, 3 Jun 2019 08:30:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1559575841; bh=tNB5kwsQCkWUdUGYoXLUTcXesmduiv7Xov5IsFEQD4c=; l=971; h=From:To:Date; b=AOqOupX8EfbJXaHwORER7F0Id7uXjq3W1GjNCANKEaNfM4X81TpZf6ZN0X7oHmli8 MmRdnZAvCrkMoXzBVequYBAJ2pGYbz8dGqIN+/ZykuoajelT+zLtYJ510cLyiMy3WS qb8j97OuJx6kUQNx2Je58aoPpyl8pxaybnKiEHz2y8HzMJZxV7xdG2oSBcGxo Authentication-Results: tana.it; auth=pass (details omitted) Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Mon, 03 Jun 2019 17:30:41 +0200 id 00000000005DC082.000000005CF53D21.00007C8C From: Alessandro Vesely To: "art@ietf.org" Openpgp: id=0A5B4BB141A53F7F55FC8CBCB6ACF44490D17C00 Message-ID: Date: Mon, 3 Jun 2019 17:30:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [art] Can now register draft-vesely-authmethod-dnswl? X-BeenThere: art@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Applications and Real-Time Area Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jun 2019 15:30:58 -0000 Hi all, we've been using a dnswl Email Authentication Method since 2013, but it hasn't been possible to register it in the corresponding IANA page because of a misunderstanding on the use of ptype's. In fact, the method provides for a ptype of "dns", e.g. used like so: Authentication-Results: mail.example.com; dnswl=pass dns.zone=list.dnswl.example policy.ip=127.0.9.2 policy.txt=sender.domain.example According to the obsolete spec, dns.zone should have been named policy.zone. At design time, the latter was considered unclear, because its value could have been a dotted decimal like policy.ip, possibly generating confusion. Now that rfc8601 allows that ptype, I'd like to register it at IANA, so as to avoid that those names could be used for different methods. I've updated my draft, in case it's needed: https://tools.ietf.org/html/draft-vesely-authmethod-dnswl-08 Would someone kindly suggest me how to proceed? TIA Ale -- From nobody Wed Jun 5 19:24:51 2019 Return-Path: X-Original-To: art@ietfa.amsl.com Delivered-To: art@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0930120094 for ; Wed, 5 Jun 2019 19:24:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=gSOHG431; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MknpwNZs 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 nX7NIBqGISyV for ; Wed, 5 Jun 2019 19:24:47 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BC6B1200A4 for ; Wed, 5 Jun 2019 19:24:47 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A6848221B6; Wed, 5 Jun 2019 22:24:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 05 Jun 2019 22:24:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=s FEySR5UUJ/S7LG+BfbJ8lUDvou4rN/krgA5NkXqR1o=; b=gSOHG431ZLaZnxdcY D/AGi62M9Kc9iO84v1QsZ+mY2rdyI9SqTm/CgDd2uLYjfZbIqWNx5G1gwkzlBsAi btvzG1M6ex1RXbZvxPhVy8wRYK1ZgiUH5iHdVMoN8qSkKYZ5kAujuK/jscGasGxt bFEOJGGGwIWF5c2POZtYNzJmsvTaYYe+++yLtrnJL2K+r2VSFqlu7ING/8tGZy8c MeRrFc0z2oZr8PfR28vunWqknXOghLRU5Bvg0v/GMi70GDARZLli0qdbdOIJFPKx LCHtqd4jLbXIZR5TrcGNb3TJBgybnr3KB8hw/YyHWpcPa7mx0pIf0uhsZdceN1hz Dsr+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=sFEySR5UUJ/S7LG+BfbJ8lUDvou4rN/krgA5NkXqR 1o=; b=MknpwNZsXJbsNplXBYM5T5a6OeWzWC9tRCXu2U+wrtNQJuFTudXssqQLL /Yb9YMHmEsRrZgtphDuHFZWTqPsQMf/hHN+JKVTfJUW51OHg7IleRdXxgklZGR8H WVQzxdTarSwG5gPuFiTTGLpC0pQAk0E+xWbAvQo//2ItilThn1ndXnRfDuWKppd7 ncVqFPO6riSsq6jCn8zHOrHO1T3aKEw/78x9hxGspmUPIGVhkJAKlnx6txkbxoox fkLroysTAlsLDILKmYZeeJlyYE+88MoK3Sq/iFO3OCIbAFT7i3BAkTCoChOxMwKo Ae6QwXEGQXKWYSK/7m/FZZAKO8+1w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegfedgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuffhomhgrihhnpehrfhgtqdgvughithhorhdrohhrghdpmhhnoh htrdhnvghtnecukfhppedugeegrddufeeirddujeehrddvkeenucfrrghrrghmpehmrghi lhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from macbook-pro.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 986D280060; Wed, 5 Jun 2019 22:24:40 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Mark Nottingham In-Reply-To: <20190604191748.C6BADB82181@rfc-editor.org> Date: Thu, 6 Jun 2019 12:24:36 +1000 Cc: pbryan@anode.ca, kris@sitepen.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, superuser@gmail.com, sven.willenbuecher@gmx.de, art@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190604191748.C6BADB82181@rfc-editor.org> To: RFC Errata System X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [art] [Editorial Errata Reported] RFC6901 (5745) X-BeenThere: art@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Applications and Real-Time Area Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2019 02:24:50 -0000 Sven, That section of the specification is specifically about representing = JSON pointers in JSON strings, which does require such escaping. Recommend REJECT. Cheers, > On 5 Jun 2019, at 5:17 am, RFC Errata System = wrote: >=20 > The following errata report has been submitted for RFC6901, > "JavaScript Object Notation (JSON) Pointer". >=20 > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata/eid5745 >=20 > -------------------------------------- > Type: Editorial > Reported by: Sven Willenb=C3=BCcher >=20 > Section: 5 >=20 > Original Text > ------------- > The following JSON strings evaluate to the accompanying values: >=20 > "/i\j" 5 > "/k\"l" 6 >=20 > Corrected Text > -------------- > The following JSON strings evaluate to the accompanying values: >=20 > /i\j 5 > /k"l 6 >=20 > Notes > ----- > In JSON itself some special characters like the backslash and the = double quote character can be escaped using a backslash. A similar = escaping was not described for JSON pointers. Therefore it is not clear = to me why such an escaping is needed in JSON pointers too. Maybe the = additional double quotes around the example JSON pointers enforce this. = In the corrected text I have stated my view on this. >=20 > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party =20 > can log in to change the status and edit the report, if necessary.=20 >=20 > -------------------------------------- > RFC6901 (draft-ietf-appsawg-json-pointer-09) > -------------------------------------- > Title : JavaScript Object Notation (JSON) Pointer > Publication Date : April 2013 > Author(s) : P. Bryan, Ed., K. Zyp, M. Nottingham, Ed. > Category : PROPOSED STANDARD > Source : Applications Area Working Group APP > Area : Applications > Stream : IETF > Verifying Party : IESG -- Mark Nottingham https://www.mnot.net/