
From nobody Mon Oct  1 12:22:44 2018
Return-Path: <adam@nostrum.com>
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 0CD99130E92; Mon,  1 Oct 2018 12:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable autolearn_force=no
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 sSpEDjv9_5CL; Mon,  1 Oct 2018 12:17:41 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 30841130DE8; Mon,  1 Oct 2018 12:17:41 -0700 (PDT)
Received: from Svantevit.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w91JHUjh039495 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Oct 2018 14:17:34 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.roach.at
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>, pthatcher=40google.com@dmarc.ietf.org
Cc: mmusic@ietf.org, art@ietf.org, clue@ietf.org, ice@ietf.org, RTCWeb IETF <rtcweb@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca> <46E40ED2-D289-4C0F-8C0B-82A5980B2692@ericsson.com> <E05D7CB4-832E-4221-ADFE-D8F317EEA8F1@iii.ca> <CAJrXDUGpmZKGQXF0p1hjQv_F=5dQoJLUCT7+6y-=uzwcRv1Ncw@mail.gmail.com> <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <2f5dfed4-1f77-51cf-aec8-0d3e8e8edb14@nostrum.com>
Date: Mon, 1 Oct 2018 14:17:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ycWd6evWxVjYCajxTbWynNvOIw4>
X-Mailman-Approved-At: Mon, 01 Oct 2018 12:22:43 -0700
Subject: Re: [art] [MMUSIC] [Ice]  [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2018 19:17:42 -0000

On 9/27/18 6:20 PM, Justin Uberti wrote:
> I agree with Peter. Chrome's implementation is already closer to 8445 
> than 5245, so I don't see any issues associated with snapping this 
> cluster to 8445 (aside from the work involved).
>
> On that topic, note that JSEP will need a few more changes than just 
> the addition of the 8445 reference and note; the examples will have to 
> be updated, as will the logic regarding generation of offers and 
> answers and their parsing (to deal with the new ice-option). These 
> changes will be modest but probably will need to be done by the authors.


If I read what you're saying correctly, it sounds like you're talking 
about changes that are significant enough that we'll have to put JSEP 
through IETF last call and through the IESG again. That being the case, 
and the rest of the cluster being so close to done, I'd really prefer to 
see this done very soon, if such changes are required. When do you 
believe such an update could be available?

I've copied the RFC Series Editor on this note for her awareness.

/a


From nobody Tue Oct  2 18:35:44 2018
Return-Path: <nordmark@acm.org>
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 7B046131191 for <art@ietfa.amsl.com>; Tue,  2 Oct 2018 18:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 g-Vcfo8myCuj for <art@ietfa.amsl.com>; Tue,  2 Oct 2018 18:35:41 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 0FEB0131186 for <art@ietf.org>; Tue,  2 Oct 2018 18:35:41 -0700 (PDT)
Received: from [192.168.1.125] (107-128-215-68.lightspeed.sntcca.sbcglobal.net [107.128.215.68]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w931ZE0C020190 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 2 Oct 2018 18:35:32 -0700
To: art@ietf.org, paf@netnod.se
From: Erik Nordmark <nordmark@acm.org>
Message-ID: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org>
Date: Tue, 2 Oct 2018 18:35:11 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVaRV8znopTF5hiIMZcon0zYlmrbBy9QUcQY+Fsi3QfpGBTpeGRf6uTzXVHDL2ynUsKOr967Id5ND9UsqD3CiTsb43S9zzXrwzs=
X-Sonic-ID: C;0nOHk6zG6BGgIYLirVfHYg== M;FIEfnazG6BGgIYLirVfHYg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ymdWO5o92yc0rHhnNgx6yKw9jws>
Subject: [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 01:35:43 -0000

Patrik,

I've reviewed the document and I have a suggestion to make it a bit more 
clear. Currently one has to read much of the document including the IANA 
considerations section to be certain that the document makes the 
statement to move forward to Unicode 11.

I think it would be more clear if that was captured in the abstract. For 
instance, it could say something like this:
CURRENT:
    This document describes changes between Unicode 6.3.0 and Unicode
    11.0.0 in the context of IDNA2008.  It further suggests for the IETF
    a path forward regarding ensuring IDNA2008 follows the evolution of
    the Unicode Standard.

    In a few cases changes have been made in the Unicode Standard related
    to the algorithm IDNA2008 specifies.  IDNA2008 do give the ability to
    add exceptions for backward compatibility to the algorithm but the
    conclusions provided in this document suggests no such changes.

ADD:
     Thus the document requests that IANA update the tables to Unicode 11.

     In addition, all registries should continue the practice of 
calculating a repertoire using conservatism and inclusion principles.

[Assuming that is current recommended practice]

This wasn't clear to me in the introduction; had to read it several times:
    When the Unicode Standard is updated code points are assigned that
    earlier was not and property values changes for already assigned code
    points.
I would be more clear to say something like:
    When the Unicode Standard is updated new code points are assigned
    and property values might be changed for already assigned code
    points.

Nits and typos:

Introduction section says:
    Changing properties to already assigned code points ...
I think "for" is better than "to" here.

Conclusion section:
s/repertoir/repertoire/
s/inclusive/inclusion/

Thanks,
    Erik


From nobody Fri Oct  5 07:02:06 2018
Return-Path: <wwwrun@rfc-editor.org>
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 A3A4412426A for <art@ietfa.amsl.com>; Fri,  5 Oct 2018 07:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3gUwqTUfwPb0 for <art@ietfa.amsl.com>; Fri,  5 Oct 2018 07:02:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E174C12F1AC for <art@ietf.org>; Fri,  5 Oct 2018 07:01:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 46DCAB818E3; Fri,  5 Oct 2018 07:01:37 -0700 (PDT)
To: mnot@mnot.net, erik.wilde@dret.net, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, superuser@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: steven.liekens@gmail.com, art@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20181005140137.46DCAB818E3@rfc-editor.org>
Date: Fri,  5 Oct 2018 07:01:37 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Lk_RlJbMaZ7tDDAJie_VcfDz9lk>
Subject: [art] [Technical Errata Reported] RFC7807 (5515)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2018 14:02:03 -0000

The following errata report has been submitted for RFC7807,
"Problem Details for HTTP APIs".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5515

--------------------------------------
Type: Technical
Reported by: Steven <steven.liekens@gmail.com>

Section: 3.1

Original Text
-------------
   o  "type" (string) - A URI reference [RFC3986] that identifies the
      problem type.  This specification encourages that, when
      dereferenced, it provide human-readable documentation for the
      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
      this member is not present, its value is assumed to be
      "about:blank".

Corrected Text
--------------
   o  "type" (string) - A URI reference [RFC3986] that identifies the
      problem type.  This specification encourages that, when
      dereferenced, it provide human-readable documentation for the
      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
      this member is missing or null, its value is assumed to be
      "about:blank".

Notes
-----
JSON objects with a null "type" are syntactically correct, but there is no information on how it should be handled.

{
    "type": null,
    "status": 404,
    "title": "Not Found"
}

It makes sense to treat null as an alias of "about:blank" and that's how I think it should be documented.

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7807 (draft-ietf-appsawg-http-problem-03)
--------------------------------------
Title               : Problem Details for HTTP APIs
Publication Date    : March 2016
Author(s)           : M. Nottingham, E. Wilde
Category            : PROPOSED STANDARD
Source              : ART Area General Application Working Group
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Oct  5 16:55:35 2018
Return-Path: <mnot@mnot.net>
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 79813130DC8 for <art@ietfa.amsl.com>; Fri,  5 Oct 2018 16:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=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=MCLVHF/x; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hedA1raD
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 dslQd9kGYZO3 for <art@ietfa.amsl.com>; Fri,  5 Oct 2018 16:55:30 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2EEB129C6B for <art@ietf.org>; Fri,  5 Oct 2018 16:55:29 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 6CDC7B2A; Fri,  5 Oct 2018 19:55:28 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 05 Oct 2018 19:55:28 -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=fm3; bh=O 9ghc6cN+amwHcu2vjpdeXwMIPstPpEzagia/3m08P0=; b=MCLVHF/xaNGi4rKPt o1mxEcWVFTSUruJNlBVRp/JQ9KrCPKFkIIxLSWQPa64b6bVL9OMZ3wd9SqbpXZFy uTTehTc/B/42FRXy7L5lF33XXpkje27zSaD7K4AoMAXN19SqU/rs9o4lnSfpOqw7 cgnQyV9C8onKiGLNlvA2UQyLhqcSz/zRYEbqg4R9ZJTGj64H9mNismue4G2GVS0j JgiZq9cZaUnB2KBW0yWXFZgUfPd1qzutth+tZ+aQCJiRb7UfW0PGB6kAh1n7hHi1 h1NRPG+An52hqFFjyMabScnKHrjcFTKUjJjwzrkmBCFdPGhPlYbBsdyOpfJtaJsB hKiwA==
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=fm3; bh=O9ghc6cN+amwHcu2vjpdeXwMIPstPpEzagia/3m08 P0=; b=hedA1raDazNys2ZmKDVxX+z0hcQ/by1oG0FBNNZ5nlcjpKn3ucYeffcNm N1qB7PkxDz4Wns9hW5z9RFQ1xaUMd2K0j2LSKnfvUA+qGAreirGDMW3EsnhhbyfO YTpHD9kA0Bo+ItZJo21NlnOpSEADQXwEEa8YC0w+4L9awY0NUXTR3rv9oR9fmFgo VXZbf9V4LhTHneImGKr2R8TCJe1bQI4eDmxsbo9i/KCedosIzw/yKW07AEhV7Lln PnbUCzhNnj/ZoWTxlKu09R8kTHkEgu18HlEnYQJBkvEX/AijbNLE8DLc/1mjFLIo YVMpqG0zZ8G1AH7O7DCta7YMcosjw==
X-ME-Sender: <xms:7vm3WzVVe7cPdYzttofuQ37WNnsHLf5NxKdD38QsuZC-ol5azdFSzA>
X-ME-Proxy: <xmx:7vm3Wz8UgDOOipWrMta6L5c3Zx2DqOjreBKgzQfrCSPnxkP-Hh5RMQ> <xmx:7vm3W5p-BO15kODYof7djjZCFIkOfkBDNhQT4LBI_1oaUYizNbER7w> <xmx:7_m3Wy5Nf07T5LGIU6GdZ9VptWcY6GydcjqOJPdAzUzyupawyI7t3g> <xmx:7_m3W66v-qt2qEvSfHufWWOu9WHBn3p9HtN_Vjq7BPda_k_KfphlVw> <xmx:7_m3WxkBV_Xr918e5MkqxvBXoBhz18n5sAT5Xi20wxiVlXdk8z9enA> <xmx:8Pm3W-BT2gJ30VG-Uo4f7OusA50ltDp6rKYgQc2Vvc8g4csn_mwBKg>
Received: from [10.214.227.157] (unknown [1.136.222.0]) by mail.messagingengine.com (Postfix) with ESMTPA id 6F5D5102D2; Fri,  5 Oct 2018 19:55:26 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Mark Nottingham <mnot@mnot.net>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <20181005140137.46DCAB818E3@rfc-editor.org>
Date: Sat, 6 Oct 2018 09:55:22 +1000
Cc: erik.wilde@dret.net, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, superuser@gmail.com, steven.liekens@gmail.com, art@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BACDF95B-F2F6-49B6-A855-BE826E288C6F@mnot.net>
References: <20181005140137.46DCAB818E3@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/dISjiflAhsx3rDzO2onTQF1pXcY>
Subject: Re: [art] [Technical Errata Reported] RFC7807 (5515)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2018 23:55:34 -0000

This is a substantive change. We can=E2=80=99t do that in an erratum.=20

Sent from my iPhone

> On 6 Oct 2018, at 12:01 am, RFC Errata System <rfc-editor@rfc-editor.org> w=
rote:
>=20
> The following errata report has been submitted for RFC7807,
> "Problem Details for HTTP APIs".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5515
>=20
> --------------------------------------
> Type: Technical
> Reported by: Steven <steven.liekens@gmail.com>
>=20
> Section: 3.1
>=20
> Original Text
> -------------
>   o  "type" (string) - A URI reference [RFC3986] that identifies the
>      problem type.  This specification encourages that, when
>      dereferenced, it provide human-readable documentation for the
>      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
>      this member is not present, its value is assumed to be
>      "about:blank".
>=20
> Corrected Text
> --------------
>   o  "type" (string) - A URI reference [RFC3986] that identifies the
>      problem type.  This specification encourages that, when
>      dereferenced, it provide human-readable documentation for the
>      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
>      this member is missing or null, its value is assumed to be
>      "about:blank".
>=20
> Notes
> -----
> JSON objects with a null "type" are syntactically correct, but there is no=
 information on how it should be handled.
>=20
> {
>    "type": null,
>    "status": 404,
>    "title": "Not Found"
> }
>=20
> It makes sense to treat null as an alias of "about:blank" and that's how I=
 think it should be documented.
>=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
> --------------------------------------
> RFC7807 (draft-ietf-appsawg-http-problem-03)
> --------------------------------------
> Title               : Problem Details for HTTP APIs
> Publication Date    : March 2016
> Author(s)           : M. Nottingham, E. Wilde
> Category            : PROPOSED STANDARD
> Source              : ART Area General Application Working Group
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG


From nobody Sat Oct  6 22:30:32 2018
Return-Path: <paf@netnod.se>
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 30E41129C6A for <art@ietfa.amsl.com>; Sat,  6 Oct 2018 22:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.923
X-Spam-Level: 
X-Spam-Status: No, score=-0.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netnod-se.20150623.gappssmtp.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 xJN0q3t3iUTc for <art@ietfa.amsl.com>; Sat,  6 Oct 2018 22:30:28 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 A75021294D7 for <art@ietf.org>; Sat,  6 Oct 2018 22:30:27 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id c22-v6so14849169edc.4 for <art@ietf.org>; Sat, 06 Oct 2018 22:30:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netnod-se.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=wF0G8+k8e2umTSX/jnoG2F7dGE8oyeg7UjgMZ7sZLUU=; b=rhRu7/ZD6syAIW7dqriYAev8UE7H5WfrF/xst7ehrGswE3K61OW8CMkB7glGJJaXN+ uHOpdwdrirWIMgvx+hnEzq4zlGimQQgLGihdAJLf/9TbFelHTAO1WKxI2EI4ve7jotEV xHo0iRIwFxUyrh1SozRG1dtUvBLGqEATZ7knd1TqyVvn2tZJvyiYqOOwBOD6LH4u5rje 5yUfnibSfedCRuXjpqTfrMdDgFlmEWa4KiuZFC6bpUvFDwkrc7mCXnuRO/uOL2CoZtBR giiDMKSE2/O+GBx2tjcc9vWx49ZHVZkahUi492pHyMNCMS1z6W+oJ7aV/Awp4eRZgD67 OSLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=wF0G8+k8e2umTSX/jnoG2F7dGE8oyeg7UjgMZ7sZLUU=; b=YYaHAT7n8sk6Jqb7lpXIcoiRZZkc2BC920oUgWR22LE8sy9MP17fWpNpBUa5IT8ruF 1plsCQ+TNAJI9/SCtZrKPNR7AszT8rLvwxtFLAI/1GijThueTprcYN7SMrEwzdtFgkV9 iOUcP98xJzUDM6ST5RNVeFbdGvipDhUYybcQFF9hbp6HWdX/RkGQiHy0P0DGhF6WD24m L/IDg/X/DM0kGQFRGcptbe0BguLXybCU4V/Ub9ko7d8XUnoCiM4oJ4s4jFwzqlSvcTq4 T6GiMghLGhMreu0+0DgiAgfgh7Ws16kuoRMOvnueMGCbpAkt/b9jcclkMRv3z52hc54h g38A==
X-Gm-Message-State: ABuFfoivVmwdHArmxRPgmxY2GSa3FNDr50R+2/QaP9y71xM5nag1ny/Q ptzzuRwgW6Nk15KrGJRQviB7kzdhqXQ=
X-Google-Smtp-Source: ACcGV63//MjjUUAdN5ewyY5hi8a0rsTHb+wSRB2ghuhXtKFRPrKCwws0r6ETDIVLLsIx8+GOrec2XA==
X-Received: by 2002:a17:906:1ec9:: with SMTP id m9-v6mr17920746ejj.35.1538890225750;  Sat, 06 Oct 2018 22:30:25 -0700 (PDT)
Received: from [192.165.72.241] ([192.165.72.241]) by smtp.gmail.com with ESMTPSA id q25-v6sm2507514eda.18.2018.10.06.22.30.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Oct 2018 22:30:24 -0700 (PDT)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@netnod.se>
To: "Erik Nordmark" <nordmark@acm.org>
Cc: art@ietf.org
Date: Sun, 07 Oct 2018 07:30:22 +0200
X-Mailer: MailMate (1.12r5533)
Message-ID: <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se>
In-Reply-To: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_00787644-E9AC-42BE-BB37-F86E33242F60_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/7bRbYuz-AeG9svwiDTwKszxwZ4A>
Subject: Re: [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Oct 2018 05:30:30 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_00787644-E9AC-42BE-BB37-F86E33242F60_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks, fixed for -04.

   paf

On 3 Oct 2018, at 3:35, Erik Nordmark wrote:

> Patrik,
>
> I've reviewed the document and I have a suggestion to make it a bit mor=
e clear. Currently one has to read much of the document including the IAN=
A considerations section to be certain that the document makes the statem=
ent to move forward to Unicode 11.
>
> I think it would be more clear if that was captured in the abstract. Fo=
r instance, it could say something like this:
> CURRENT:
>    This document describes changes between Unicode 6.3.0 and Unicode
>    11.0.0 in the context of IDNA2008.  It further suggests for the IETF=

>    a path forward regarding ensuring IDNA2008 follows the evolution of
>    the Unicode Standard.
>
>    In a few cases changes have been made in the Unicode Standard relate=
d
>    to the algorithm IDNA2008 specifies.  IDNA2008 do give the ability t=
o
>    add exceptions for backward compatibility to the algorithm but the
>    conclusions provided in this document suggests no such changes.
>
> ADD:
>     Thus the document requests that IANA update the tables to Unicode 1=
1.
>
>     In addition, all registries should continue the practice of calcula=
ting a repertoire using conservatism and inclusion principles.
>
> [Assuming that is current recommended practice]
>
> This wasn't clear to me in the introduction; had to read it several tim=
es:
>    When the Unicode Standard is updated code points are assigned that
>    earlier was not and property values changes for already assigned cod=
e
>    points.
> I would be more clear to say something like:
>    When the Unicode Standard is updated new code points are assigned
>    and property values might be changed for already assigned code
>    points.
>
> Nits and typos:
>
> Introduction section says:
>    Changing properties to already assigned code points ...
> I think "for" is better than "to" here.
>
> Conclusion section:
> s/repertoir/repertoire/
> s/inclusive/inclusion/
>
> Thanks,
>    Erik

  Patrik F=C3=A4ltstr=C3=B6m
  Technical Director
  Netnod

--=_MailMate_00787644-E9AC-42BE-BB37-F86E33242F60_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iGwEARECACwWIQT9vk6hwHOftrJkxVxtJBVNQL09owUCW7mZ7g4ccGFmQG5ldG5v
ZC5zZQAKCRBtJBVNQL09o4VrAKC7W1JRvqVtAHmDRUSiYAv3zfJPQwCgzBatEPzx
amjtOyadu+XnFwKqQ0Y=
=PLBJ
-----END PGP SIGNATURE-----

--=_MailMate_00787644-E9AC-42BE-BB37-F86E33242F60_=--


From nobody Sun Oct  7 19:29:11 2018
Return-Path: <pradeepan88@hotmail.com>
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 C92331286E3 for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 19:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level: 
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 vfPxdu0drjZZ for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 19:29:07 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-hk2apc01lp0207.outbound.protection.outlook.com [65.55.88.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82A821200D7 for <art@ietf.org>; Sun,  7 Oct 2018 19:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/kRH/zRHEM9NlNpTAJG3erQ4PDmXE8otKUeUbp8RP3M=; b=QJTkzyhr4wQTE50oO91siMJ/WjBTwcEWlGkia89tQp9cEszS8wuhgQ3P2oh04hQ6ARiREdQL5AAOGJgi8YtkkaC+GqSRZFtw2jomF4/pscP194M9M9uLvo8PcHjjI++GKuK4FjPdzzmbfN7t7rW0FI6sSJ/r/pNeYoAOHDLAgS72GI9JfGt72UhCvWaVpl/0bGO+KIoaLyjnnGbefa77cQCuGU9Z1hGI6+RvzkfvD+P7UtJ4ulPW+Sq/zGDRFTYaIjnU+30WixQ1USDa2vey2Rql489EJd06LTDZE51wZ9y2FUXNtHRKuJGf47R25Em4zhpZdQb1T40UZfFr3DLT0g==
Received: from PU1APC01FT022.eop-APC01.prod.protection.outlook.com (10.152.252.59) by PU1APC01HT239.eop-APC01.prod.protection.outlook.com (10.152.253.248) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Mon, 8 Oct 2018 02:28:59 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.252.56) by PU1APC01FT022.mail.protection.outlook.com (10.152.253.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Mon, 8 Oct 2018 02:28:59 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995%4]) with mapi id 15.20.1228.020; Mon, 8 Oct 2018 02:28:59 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: "art@ietf.org" <art@ietf.org>
Thread-Topic: can a verify envelope be coded or is it available
Thread-Index: AQHUXq3m1V6aSDhTG0aYAh26mmgeUg==
Date: Mon, 8 Oct 2018 02:28:59 +0000
Message-ID: <SG2PR0302MB260622F429BD8A36C71CA510B7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:EE29088EB49EC4990F4CAF697B1B33CD63EB39F6BF61F18B5FAA4CD7DCF3493D; UpperCasedChecksum:3FD4062C661261EA6E0E77226B245F5BA655F5D9BC2D834887463F2B580EC455; SizeAsReceived:6897; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [/fo6z+i1THv5p9InaKZRRVIy5bH1kvr4]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT239; 6:tytpWrxRBJGift1CiK/vC4JrBp9kLwsW6FCPyzXmmXEIFaabJDVW+/iQDvlSmHBnxwpgLxFsUI0ZosxHOjDZBhRYYI3dmn4ffJ4Jo1XVfHSwczT7T/q202yekX98nBlI2QIa1jcO/DInZQtMbpGr/kcIoplvw5AG6Wcz9+lW5yMVvQhWjH477n+mLcSy2G9PVSVeURRcyXDNOA4A4LoBTcFmxMFqf1LeRhA749Xurwjmi8fCr+LtqDTVKt4nTMkuXn8o1X939KOQ3/qgNf1vEm1bOBeqB7Myzd4UUlWjlO697iERnqkDFKUvn3P2CRLBi/IyfabO53gcKWrMPqLoo8e3F2V/RRCHYKLQ1kBY6TH8ot/biOi6JKCJ+dGeB1ChD6QyFHKOhQ7L6viY7RTNK3aDBVdrDO2lgum9OyJ7CC6oYcztEu6JeA1T7nOFQijqj+TMcVUth5fc0xCW006xwQ==; 5:xdw/9xh5OizUz+W+9dra/AVN7JUMwUke0d+PnNk7XCNlnudVnV/JaYgAwaIpROD2/gsrYSg+zEny5iK9lPO3Yy10/QUmmZU4QSJvelxrHcHypnrgGLHfmQqxi4pEaMP+Yvz9WXLc5y3R8qxiaBz5K9zKee6HJ8ZK3qJXg0jZm/o=; 7:ToKfavqKSAD1+DU0yxDAZfdxo2VaaHl4N83uW6dH4g5QAEeGOSX40gX2TL+uTJ7fVWe+LuVWG2CKpu4sCBWEzLix0oNKA/i7wYmQklAhqDlik/qxHNuye4JwlHnx1WJaUEB5T8d0I1YSLjJBDsGqI9Z5KuNplHoQcWrYV9Q/Lamo8nfjecQqRH4t84Qm0BZ6pAfEKd42HgN+yWuQ2hO2X6KLgvWB5I7Gna7Jvu22TRn7xTQ+13pfk3rXtXYdlZpd
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:PU1APC01HT239; 
x-ms-traffictypediagnostic: PU1APC01HT239:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:PU1APC01HT239; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT239; 
x-microsoft-antispam-message-info: kYUa+sumRrA+tslkB/yLdC2lp6T9sc3t73MBDrJqDEU4TAXLFvikQnfWjsDjjlGa
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB260622F429BD8A36C71CA510B7E60SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 133e6f58-37fd-4c45-1b67-08d62cc5cdd3
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2018 02:28:59.1736 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT239
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/IglcfNZuGn4x8VjZbLxm2s8rSqc>
Subject: [art] can a verify envelope be coded or is it available
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 02:29:09 -0000

--_000_SG2PR0302MB260622F429BD8A36C71CA510B7E60SG2PR0302MB2606_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello
I proposed who is of email address and there is no solution.  I am still ge=
tting emails from my self. Or someone is able to do it. Is there a verify e=
nvelope software that i can input the email header to verify it's source.
If i get email from art@ietf.org then with current limitation it could be f=
rom any one. Before proceeding to trust it is there any verify envelope rou=
tine Google app or software available that i can use to verify before trust=
ing
Pradeep Kumar xplorer

--_000_SG2PR0302MB260622F429BD8A36C71CA510B7E60SG2PR0302MB2606_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
Hello<br>
I proposed who is of email address and there is no solution.&nbsp; I am sti=
ll getting emails from my self. Or someone is able to do it. Is there a ver=
ify envelope software that i can input the email header to verify it's sour=
ce.<br>
If i get email from art@ietf.org then with current limitation it could be f=
rom any one. Before proceeding to trust it is there any verify envelope rou=
tine Google app or software available that i can use to verify before trust=
ing<br>
Pradeep Kumar xplorer
</body>
</html>

--_000_SG2PR0302MB260622F429BD8A36C71CA510B7E60SG2PR0302MB2606_--


From nobody Sun Oct  7 20:25:37 2018
Return-Path: <mnot@mnot.net>
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 3FDB7128766 for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 20:25:36 -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=cGg3zfbg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=u/8WDZTb
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 RER_78EOKjHZ for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 20:25:34 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B7301200D7 for <art@ietf.org>; Sun,  7 Oct 2018 20:25:34 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0E58721F21; Sun,  7 Oct 2018 23:25:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 07 Oct 2018 23:25:33 -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=fm3; bh=E V0sGdwDVboBbenP/4jXLbb1pi9G9ANoSuoBBx0T/74=; b=cGg3zfbggNRiI+/nw w0J0iyOM9hAKhJfUcJHU+NKUM+4KrQOZOOz9UMdpB7hI/i/MQV07GzR+gdKqSP8i Ji3DI+gOVDBoOOaI1WSpjYq/SO7NJV2k8MiJck4sWwH55FHNkCFTT2UlE/xa94w5 4fap0BEn2mvmJo953wVkjAmkzxVAusaaX43cpXKQQls1etespm0hi4huKQqwEfaq hTBxisAloiAYQaLtjFYXmVI3+7PCPh/ziK8asUQmD/7kFfGERQqEt6CMu04+AXqC xrIPMEitWrbRrMsTokCbQVboDegHTYEkbxaUNAZnGEDPLd9Nt3eCUg1m9O5GXyli DpFVg==
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=fm3; bh=EV0sGdwDVboBbenP/4jXLbb1pi9G9ANoSuoBBx0T/ 74=; b=u/8WDZTbNuHjVMQF+rnb2BQrWCyrvQ04bnpIwO7Qg5df4Ms166mEV9wXw H1l1dSUEbx9qqSeSeK4fFHqeOWvjIzooUASQgatItoVMfvvJo9vZb/hhql0ENsmS uqVE3r8WSS9byJ7EpRWdPvK28Oyf24VinGvTw7ipy3uNQUZ48lkcmlp+nk8Atn5N H3RnPVnjnfSJUZRrJL335QeCnq9bX4/A9gABF/ZcWM2KkkKn7AOu9XN93nuIebBV oAFGf0hNoko2W83LrG9qj05Knj4ULK6/EL/iQf6PYHNBBjvKj24b1y4GlaX+Qz45 ghgNxSqpLgTl0dGyG5QJXJFgbARHw==
X-ME-Sender: <xms:K866W12sA7erdiHI9TXnvEBgbTO-R34ZHN8IGYtLcIiajMY5ZXrwQQ>
X-ME-Proxy: <xmx:K866W1_pK6OqGuDBu8031QqmNcciOer7-TEl_UX9smxZD9LIyhuw4Q> <xmx:K866Wwt4INbCgssET7RqoO3mdv2PB30JhYUHxHTGKbp126KHKKvLog> <xmx:K866W4AMu_miYcxjzoxqzDWWC4awcLACDKKXFajStJuzNGeni3eQxg> <xmx:K866W4Vg_8DKir0Lr7zMf3dGi6uXyiSriqrdpKemQP0RfhHa68idYg> <xmx:K866W2DMUJsjWDLl_YZbWNCq7VtTMKWwbwuUtj_FakiqbJVxDcl1hA> <xmx:Lc66W99oLUdO-_Q7KjSUDxLg9HjCXmdzvmusgCfKxfSu9RYEXwCGUg>
Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 68B9AE4240; Sun,  7 Oct 2018 23:25:28 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CABQ2G6TfdOLwyiY-zqMMFhePAHJSRC=dxiCigQkBYGSYi53PUQ@mail.gmail.com>
Date: Mon, 8 Oct 2018 14:25:25 +1100
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Erik Wilde <erik.wilde@dret.net>, Ben Campbell <ben@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, adam@nostrum.com, superuser@gmail.com, art@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <206FAAB7-F9C9-44AF-8FA5-774DC2ACF9C6@mnot.net>
References: <20181005140137.46DCAB818E3@rfc-editor.org> <BACDF95B-F2F6-49B6-A855-BE826E288C6F@mnot.net> <CABQ2G6TfdOLwyiY-zqMMFhePAHJSRC=dxiCigQkBYGSYi53PUQ@mail.gmail.com>
To: Steven Liekens <steven.liekens@gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Wy3Bg1-vEB5MrAZyeW55IArKCwI>
Subject: Re: [art] [Technical Errata Reported] RFC7807 (5515)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 03:25:36 -0000

Hi Steven,

That's a good question. Right now, the best we can do is mark this =
erratum "HOLD FOR UPDATE."

I've been thinking for a while that we need longer-lived issue trackers =
for all HTTP specifications. We have one for the "core" specs, but the =
"extensions" one is only intended for active specs. Hopefully we'll make =
this easier to use/understand in the not-too-distant future.

Cheers,





> On 6 Oct 2018, at 7:52 pm, Steven Liekens <steven.liekens@gmail.com> =
wrote:
>=20
> That's fair, is there a better way to report this?
>=20
> On Sat, Oct 6, 2018, 01:55 Mark Nottingham <mnot@mnot.net> wrote:
> This is a substantive change. We can=E2=80=99t do that in an erratum.=20=

>=20
> Sent from my iPhone
>=20
> > On 6 Oct 2018, at 12:01 am, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
> >=20
> > The following errata report has been submitted for RFC7807,
> > "Problem Details for HTTP APIs".
> >=20
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata/eid5515
> >=20
> > --------------------------------------
> > Type: Technical
> > Reported by: Steven <steven.liekens@gmail.com>
> >=20
> > Section: 3.1
> >=20
> > Original Text
> > -------------
> >   o  "type" (string) - A URI reference [RFC3986] that identifies the
> >      problem type.  This specification encourages that, when
> >      dereferenced, it provide human-readable documentation for the
> >      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
> >      this member is not present, its value is assumed to be
> >      "about:blank".
> >=20
> > Corrected Text
> > --------------
> >   o  "type" (string) - A URI reference [RFC3986] that identifies the
> >      problem type.  This specification encourages that, when
> >      dereferenced, it provide human-readable documentation for the
> >      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
> >      this member is missing or null, its value is assumed to be
> >      "about:blank".
> >=20
> > Notes
> > -----
> > JSON objects with a null "type" are syntactically correct, but there =
is no information on how it should be handled.
> >=20
> > {
> >    "type": null,
> >    "status": 404,
> >    "title": "Not Found"
> > }
> >=20
> > It makes sense to treat null as an alias of "about:blank" and that's =
how I think it should be documented.
> >=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
> > --------------------------------------
> > RFC7807 (draft-ietf-appsawg-http-problem-03)
> > --------------------------------------
> > Title               : Problem Details for HTTP APIs
> > Publication Date    : March 2016
> > Author(s)           : M. Nottingham, E. Wilde
> > Category            : PROPOSED STANDARD
> > Source              : ART Area General Application Working Group
> > Area                : Applications and Real-Time
> > Stream              : IETF
> > Verifying Party     : IESG
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Sun Oct  7 20:42:29 2018
Return-Path: <James.H.Manger@team.telstra.com>
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 4B81D128B14 for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 20:42:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-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 (1024-bit key) header.d=teamtelstra.onmicrosoft.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 LHu8sU9VYQJf for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 20:42:23 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) (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 4D3E6128BAC for <art@ietf.org>; Sun,  7 Oct 2018 20:42:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.54,355,1534773600"; d="scan'208";a="149416512"
X-Amp-Result: SKIPPED(no attachment in message)
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipocvi.tcif.telstra.com.au with ESMTP; 08 Oct 2018 14:42:15 +1100
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipcavi.tcif.telstra.com.au with ESMTP; 08 Oct 2018 14:42:15 +1100
Received: from wsapp5872.srv.dir.telstra.com (10.75.11.108) by WSMSG3705.srv.dir.telstra.com (172.49.40.203) with Microsoft SMTP Server (TLS) id 8.3.485.1; Mon, 8 Oct 2018 14:42:15 +1100
Received: from wsapp5585.srv.dir.telstra.com (10.75.3.67) by wsapp5872.srv.dir.telstra.com (10.75.11.108) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 8 Oct 2018 14:42:14 +1100
Received: from AUS01-ME1-obe.outbound.protection.outlook.com (10.172.101.125) by wsapp5585.srv.dir.telstra.com (10.75.3.67) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 8 Oct 2018 14:42:14 +1100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teamtelstra.onmicrosoft.com; s=selector1-team-telstra-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8MNbZO38huTZKwC0atgKnmqfHRAT+gpaO27l8wGWcBg=; b=XO0bxWA4+bz7gTOVIvaGuGjsns9hLR/drnI+UucH03QzcSc6jpdOswc55iYtbg3HKz3WWiwlB5kcBZ1znFLvXvSbWg+s9TT+nJXxsHLahBNcRFFpUbJXr1e3Ec7WYVd+qBpgN2hgh5Nq5nYA9Amo4PscJziM/SqKoKKvgYrvr7s=
Received: from MEAPR01MB3542.ausprd01.prod.outlook.com (52.134.216.9) by MEAPR01MB3656.ausprd01.prod.outlook.com (52.134.216.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.23; Mon, 8 Oct 2018 03:42:12 +0000
Received: from MEAPR01MB3542.ausprd01.prod.outlook.com ([fe80::4031:99ca:970e:721e]) by MEAPR01MB3542.ausprd01.prod.outlook.com ([fe80::4031:99ca:970e:721e%2]) with mapi id 15.20.1207.024; Mon, 8 Oct 2018 03:42:12 +0000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Mark Nottingham <mnot@mnot.net>, Steven Liekens <steven.liekens@gmail.com>
CC: "art@ietf.org" <art@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Thread-Topic: [art] [Technical Errata Reported] RFC7807 (5515)
Thread-Index: AQHUXLQPibXDLK9z+k6TUqX2ITJ2vaURVFkAgANflVqAAAAvkA==
Date: Mon, 8 Oct 2018 03:42:12 +0000
Message-ID: <MEAPR01MB3542C171203B076F71CB8013E5E60@MEAPR01MB3542.ausprd01.prod.outlook.com>
References: <20181005140137.46DCAB818E3@rfc-editor.org> <BACDF95B-F2F6-49B6-A855-BE826E288C6F@mnot.net> <CABQ2G6TfdOLwyiY-zqMMFhePAHJSRC=dxiCigQkBYGSYi53PUQ@mail.gmail.com> <206FAAB7-F9C9-44AF-8FA5-774DC2ACF9C6@mnot.net>
In-Reply-To: <206FAAB7-F9C9-44AF-8FA5-774DC2ACF9C6@mnot.net>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 10.0.500.19
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=James.H.Manger@team.telstra.com; 
x-originating-ip: [203.35.185.254]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MEAPR01MB3656; 6:hRSXfq41nhNT7VGNVw+S2iUs+DcM2OX7cUb9rsuY6QTgrWR9KHgj4YupNSwsPVtWQA/ziPQpiyJW6WNIspY+CCiBKAreeNTc+6bEzy9daS+b843nhi2HFdrcDYDb1HL2KZkn1prVNGVXPf4P71F1+d0kua8oyzde233RMsCV6X1Qoyk283n5beqajAw5PVeDGQa+Jjppt3NSLNPh3uJm4NTu5sO2mD4Sc7pOyOuNqKuZaKan1B+M3WqCX+bSujKZcuCEI3p2XUY9t+ouqvUrSL1Sm9iPSvIxCDJNAP9/O5XJcEs71gTnK34KHKpJENjtyc/3hoCh9Q5Hn+m8fHIOTkZDJ5p5INvoZV5tjrzhxdi6yammsdOyBxPfq0uzoOL+OwFauJ9mkNpEp9FvQts1zzU5qdlGDQxUbeB6bZ74p5QGNda2e8XwweaUjTwhN8pb/JM3QBT3nmypriK0Zxth4w==; 5:2iKmOjN/etcU6lSZHzpo+8FLwdCO+MdHw96g7OYHAw91wm7iooAlApNIJBJLzPdu+PpAA0ypZuNZFu0HD9p+BFJorM4rfA8Mg4WtcAMfimwEebYvgnFjcOOmrYH9Fz/to1nTO/mzU3wmDBmp3Toy08TmMkVqxF8ETPL8rmcThgU=; 7:5/RYAcNiqqmOdkfBc49R6Czi6wWx/q6p3NJLL3/hXfJJTXZapfA3JNf/MiQFf9XWs6PRAry1p/Czj7B39bPVNorKERLEYptiAKYI/DljtDHTxIaL8KHL5A5MzpV5mnXOkgtETG71yHKxF5PL0lbifFtbwwHGsQ5fnorX8l/3OwW/xTPwmFrGtvt8jWFmQZ9pGh7nfVqAYqs6hrq1pvofT/WBybzkNvzIyndk1JhP1UvThR5Dh/TFmi9GplOKDA8F
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 1d812e10-2389-420f-7212-08d62cd00896
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:MEAPR01MB3656; 
x-ms-traffictypediagnostic: MEAPR01MB3656:
x-microsoft-antispam-prvs: <MEAPR01MB36563F8F6FEB438ABBFC604CE5E60@MEAPR01MB3656.ausprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(278428928389397);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231355)(944501410)(4982022)(52105095)(3002001)(93006095)(93001095)(10201501046)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(201708071742011)(7699051); SRVR:MEAPR01MB3656; BCL:0; PCL:0; RULEID:; SRVR:MEAPR01MB3656; 
x-forefront-prvs: 081904387B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(366004)(136003)(396003)(39860400002)(199004)(189003)(13464003)(1720100001)(229853002)(99286004)(76176011)(97736004)(5250100002)(53546011)(33656002)(14454004)(6306002)(316002)(6436002)(53936002)(6246003)(6506007)(55016002)(2900100001)(7696005)(9686003)(966005)(25786009)(93886005)(478600001)(39060400002)(72206003)(71190400001)(71200400001)(5660300001)(2906002)(105586002)(256004)(446003)(14444005)(4326008)(476003)(3846002)(6116002)(486006)(86362001)(8676002)(102836004)(11346002)(81156014)(81166006)(8936002)(66066001)(68736007)(7736002)(54906003)(26005)(5003630100001)(110136005)(305945005)(106356001)(186003)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:MEAPR01MB3656; H:MEAPR01MB3542.ausprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: team.telstra.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: t7bV7NujDum3M5FQAMvIzRYlRliqEcG5rlu/IO+LVjmhdZEOSaFYLEraEtU2ugJ8TimS7GkXyenU6PDyHhHeNZqGNp8xAv8KM/cCFvtkihkAISKM734MKXevTbn3N+SWL4C4GzEzwD0vWOY/djsv53w9islNMjLPf5fvPiIpi6KtMHhHghOgRu2yMxniEyxJpem2aEVE3MbQgDpM5nN+lldv5icnBia7AJsyTWQ9YZzKDBTHvo5Rag9mNFuyESuJU+JYvzKqosI78xvGQcic3Envd3AZFxlSmuKHiwkxFhH5yVZkjmcjRJGRFgrYap3lN+UT8CFv/uO9h30Zw9ijEinyUFTjujuqoaKiZhT6nTE=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1d812e10-2389-420f-7212-08d62cd00896
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2018 03:42:12.7775 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 49dfc6a3-5fb7-49f4-adea-c54e725bb854
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MEAPR01MB3656
X-OriginatorOrg: team.telstra.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/3tbOeoIiYIf1TxoXwgrCm_cfbKw>
Subject: Re: [art] [Technical Errata Reported] RFC7807 (5515)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 03:42:28 -0000

eyJ0eXBlIjoyMywgLi4ufSwgeyJ0eXBlIjp0cnVlLCAuLi59LCB7InR5cGUiOlsiYWJjIl0sIC4u
Ln0sIGFuZCB7InR5cGUiOiJ8bm90IGEgdXJpPiIsIC4uLn0gYXJlIGp1c3QgYXMgInN5bnRhY3Rp
Y2FsbHkgY29ycmVjdCIgSlNPTiBhcyB7InR5cGUiOm51bGwsIC4uLn0uIFRoZSBzcGVjIHRleHQg
c2F5czoNCg0KICAidHlwZSIgKHN0cmluZykgLSBBIFVSSSByZWZlcmVuY2UgLi4uDQoNCnNvIGl0
IGlzIGNsZWFyIHRoYXQgYWxsIHRoZXNlIGV4YW1wbGVzIGFyZSBpbnZhbGlkLiBUaGUgc3BlYyBk
b2VzbuKAmXQgZGVmaW5lIGhvdyB0byBoYW5kbGUgdGhlIHppbGxpb25zIG9mIG90aGVyIHdheXMg
YSAicHJvYmxlbSBkZXRhaWwiIGRvYyBjYW4gYmUgaW52YWxpZCAod2hpY2ggaXMgZmluZSkgc28g
aXQgZG9lc24ndCBuZWVkIHNwZWNpYWwgdGV4dCBhYm91dCAidHlwZSI6bnVsbC4gSnVzdCBSRUpF
Q1QgdGhpcyBlcnJhdGEuDQoNCi0tDQpKYW1lcyBNYW5nZXINCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IGFydCBbbWFpbHRvOmFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgTWFyayBOb3R0aW5naGFtDQpTZW50OiBNb25kYXksIDggT2N0b2JlciAyMDE4IDI6MjUg
UE0NClRvOiBTdGV2ZW4gTGlla2VucyA8c3RldmVuLmxpZWtlbnNAZ21haWwuY29tPg0KQ2M6IEJl
biBDYW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPjsgYWRhbUBub3N0cnVtLmNvbTsgQWxleGV5IE1l
bG5pa292IDxhYW1lbG5pa292QGZhc3RtYWlsLmZtPjsgYXJ0QGlldGYub3JnOyBzdXBlcnVzZXJA
Z21haWwuY29tOyBFcmlrIFdpbGRlIDxlcmlrLndpbGRlQGRyZXQubmV0PjsgUkZDIEVycmF0YSBT
eXN0ZW0gPHJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc+DQpTdWJqZWN0OiBSZTogW2FydF0gW1Rl
Y2huaWNhbCBFcnJhdGEgUmVwb3J0ZWRdIFJGQzc4MDcgKDU1MTUpDQoNCkhpIFN0ZXZlbiwNCg0K
VGhhdCdzIGEgZ29vZCBxdWVzdGlvbi4gUmlnaHQgbm93LCB0aGUgYmVzdCB3ZSBjYW4gZG8gaXMg
bWFyayB0aGlzIGVycmF0dW0gIkhPTEQgRk9SIFVQREFURS4iDQoNCkkndmUgYmVlbiB0aGlua2lu
ZyBmb3IgYSB3aGlsZSB0aGF0IHdlIG5lZWQgbG9uZ2VyLWxpdmVkIGlzc3VlIHRyYWNrZXJzIGZv
ciBhbGwgSFRUUCBzcGVjaWZpY2F0aW9ucy4gV2UgaGF2ZSBvbmUgZm9yIHRoZSAiY29yZSIgc3Bl
Y3MsIGJ1dCB0aGUgImV4dGVuc2lvbnMiIG9uZSBpcyBvbmx5IGludGVuZGVkIGZvciBhY3RpdmUg
c3BlY3MuIEhvcGVmdWxseSB3ZSdsbCBtYWtlIHRoaXMgZWFzaWVyIHRvIHVzZS91bmRlcnN0YW5k
IGluIHRoZSBub3QtdG9vLWRpc3RhbnQgZnV0dXJlLg0KDQpDaGVlcnMsDQoNCg0KDQoNCg0KPiBP
biA2IE9jdCAyMDE4LCBhdCA3OjUyIHBtLCBTdGV2ZW4gTGlla2VucyA8c3RldmVuLmxpZWtlbnNA
Z21haWwuY29tPiB3cm90ZToNCj4gDQo+IFRoYXQncyBmYWlyLCBpcyB0aGVyZSBhIGJldHRlciB3
YXkgdG8gcmVwb3J0IHRoaXM/DQo+IA0KPiBPbiBTYXQsIE9jdCA2LCAyMDE4LCAwMTo1NSBNYXJr
IE5vdHRpbmdoYW0gPG1ub3RAbW5vdC5uZXQ+IHdyb3RlOg0KPiBUaGlzIGlzIGEgc3Vic3RhbnRp
dmUgY2hhbmdlLiBXZSBjYW7igJl0IGRvIHRoYXQgaW4gYW4gZXJyYXR1bS4gDQo+IA0KPiBTZW50
IGZyb20gbXkgaVBob25lDQo+IA0KPiA+IE9uIDYgT2N0IDIwMTgsIGF0IDEyOjAxIGFtLCBSRkMg
RXJyYXRhIFN5c3RlbSA8cmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZz4gd3JvdGU6DQo+ID4gDQo+
ID4gVGhlIGZvbGxvd2luZyBlcnJhdGEgcmVwb3J0IGhhcyBiZWVuIHN1Ym1pdHRlZCBmb3IgUkZD
NzgwNywgIlByb2JsZW0gDQo+ID4gRGV0YWlscyBmb3IgSFRUUCBBUElzIi4NCj4gPiANCj4gPiAt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+IFlvdSBtYXkgcmV2aWV3
IHRoZSByZXBvcnQgYmVsb3cgYW5kIGF0Og0KPiA+IGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcv
ZXJyYXRhL2VpZDU1MTUNCj4gPiANCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KPiA+IFR5cGU6IFRlY2huaWNhbA0KPiA+IFJlcG9ydGVkIGJ5OiBTdGV2ZW4gPHN0
ZXZlbi5saWVrZW5zQGdtYWlsLmNvbT4NCj4gPiANCj4gPiBTZWN0aW9uOiAzLjENCj4gPiANCj4g
PiBPcmlnaW5hbCBUZXh0DQo+ID4gLS0tLS0tLS0tLS0tLQ0KPiA+ICAgbyAgInR5cGUiIChzdHJp
bmcpIC0gQSBVUkkgcmVmZXJlbmNlIFtSRkMzOTg2XSB0aGF0IGlkZW50aWZpZXMgdGhlDQo+ID4g
ICAgICBwcm9ibGVtIHR5cGUuICBUaGlzIHNwZWNpZmljYXRpb24gZW5jb3VyYWdlcyB0aGF0LCB3
aGVuDQo+ID4gICAgICBkZXJlZmVyZW5jZWQsIGl0IHByb3ZpZGUgaHVtYW4tcmVhZGFibGUgZG9j
dW1lbnRhdGlvbiBmb3IgdGhlDQo+ID4gICAgICBwcm9ibGVtIHR5cGUgKGUuZy4sIHVzaW5nIEhU
TUwgW1czQy5SRUMtaHRtbDUtMjAxNDEwMjhdKS4gIFdoZW4NCj4gPiAgICAgIHRoaXMgbWVtYmVy
IGlzIG5vdCBwcmVzZW50LCBpdHMgdmFsdWUgaXMgYXNzdW1lZCB0byBiZQ0KPiA+ICAgICAgImFi
b3V0OmJsYW5rIi4NCj4gPiANCj4gPiBDb3JyZWN0ZWQgVGV4dA0KPiA+IC0tLS0tLS0tLS0tLS0t
DQo+ID4gICBvICAidHlwZSIgKHN0cmluZykgLSBBIFVSSSByZWZlcmVuY2UgW1JGQzM5ODZdIHRo
YXQgaWRlbnRpZmllcyB0aGUNCj4gPiAgICAgIHByb2JsZW0gdHlwZS4gIFRoaXMgc3BlY2lmaWNh
dGlvbiBlbmNvdXJhZ2VzIHRoYXQsIHdoZW4NCj4gPiAgICAgIGRlcmVmZXJlbmNlZCwgaXQgcHJv
dmlkZSBodW1hbi1yZWFkYWJsZSBkb2N1bWVudGF0aW9uIGZvciB0aGUNCj4gPiAgICAgIHByb2Js
ZW0gdHlwZSAoZS5nLiwgdXNpbmcgSFRNTCBbVzNDLlJFQy1odG1sNS0yMDE0MTAyOF0pLiAgV2hl
bg0KPiA+ICAgICAgdGhpcyBtZW1iZXIgaXMgbWlzc2luZyBvciBudWxsLCBpdHMgdmFsdWUgaXMg
YXNzdW1lZCB0byBiZQ0KPiA+ICAgICAgImFib3V0OmJsYW5rIi4NCj4gPiANCj4gPiBOb3Rlcw0K
PiA+IC0tLS0tDQo+ID4gSlNPTiBvYmplY3RzIHdpdGggYSBudWxsICJ0eXBlIiBhcmUgc3ludGFj
dGljYWxseSBjb3JyZWN0LCBidXQgdGhlcmUgaXMgbm8gaW5mb3JtYXRpb24gb24gaG93IGl0IHNo
b3VsZCBiZSBoYW5kbGVkLg0KPiA+IA0KPiA+IHsNCj4gPiAgICAidHlwZSI6IG51bGwsDQo+ID4g
ICAgInN0YXR1cyI6IDQwNCwNCj4gPiAgICAidGl0bGUiOiAiTm90IEZvdW5kIg0KPiA+IH0NCj4g
PiANCj4gPiBJdCBtYWtlcyBzZW5zZSB0byB0cmVhdCBudWxsIGFzIGFuIGFsaWFzIG9mICJhYm91
dDpibGFuayIgYW5kIHRoYXQncyBob3cgSSB0aGluayBpdCBzaG91bGQgYmUgZG9jdW1lbnRlZC4N
Cj4gPiANCj4gPiBJbnN0cnVjdGlvbnM6DQo+ID4gLS0tLS0tLS0tLS0tLQ0KPiA+IFRoaXMgZXJy
YXR1bSBpcyBjdXJyZW50bHkgcG9zdGVkIGFzICJSZXBvcnRlZCIuIElmIG5lY2Vzc2FyeSwgcGxl
YXNlIA0KPiA+IHVzZSAiUmVwbHkgQWxsIiB0byBkaXNjdXNzIHdoZXRoZXIgaXQgc2hvdWxkIGJl
IHZlcmlmaWVkIG9yIA0KPiA+IHJlamVjdGVkLiBXaGVuIGEgZGVjaXNpb24gaXMgcmVhY2hlZCwg
dGhlIHZlcmlmeWluZyBwYXJ0eSBjYW4gbG9nIGluIA0KPiA+IHRvIGNoYW5nZSB0aGUgc3RhdHVz
IGFuZCBlZGl0IHRoZSByZXBvcnQsIGlmIG5lY2Vzc2FyeS4NCj4gPiANCj4gPiAtLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+IFJGQzc4MDcgKGRyYWZ0LWlldGYtYXBw
c2F3Zy1odHRwLXByb2JsZW0tMDMpDQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gPiBUaXRsZSAgICAgICAgICAgICAgIDogUHJvYmxlbSBEZXRhaWxzIGZvciBI
VFRQIEFQSXMNCj4gPiBQdWJsaWNhdGlvbiBEYXRlICAgIDogTWFyY2ggMjAxNg0KPiA+IEF1dGhv
cihzKSAgICAgICAgICAgOiBNLiBOb3R0aW5naGFtLCBFLiBXaWxkZQ0KPiA+IENhdGVnb3J5ICAg
ICAgICAgICAgOiBQUk9QT1NFRCBTVEFOREFSRA0KPiA+IFNvdXJjZSAgICAgICAgICAgICAgOiBB
UlQgQXJlYSBHZW5lcmFsIEFwcGxpY2F0aW9uIFdvcmtpbmcgR3JvdXANCj4gPiBBcmVhICAgICAg
ICAgICAgICAgIDogQXBwbGljYXRpb25zIGFuZCBSZWFsLVRpbWUNCj4gPiBTdHJlYW0gICAgICAg
ICAgICAgIDogSUVURg0KPiA+IFZlcmlmeWluZyBQYXJ0eSAgICAgOiBJRVNHDQo+IA0KDQotLQ0K
TWFyayBOb3R0aW5naGFtICAgaHR0cHM6Ly93d3cubW5vdC5uZXQvDQoNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQphcnQgbWFpbGluZyBsaXN0DQphcnRA
aWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXJ0DQo=


From nobody Sun Oct  7 22:49:14 2018
Return-Path: <pradeepan88@hotmail.com>
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 40DAD128CFD for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 22:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level: 
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 HQ9H8Xuv6qUV for <art@ietfa.amsl.com>; Sun,  7 Oct 2018 22:49:08 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01lp0021.outbound.protection.outlook.com [65.55.88.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B4A2130934 for <art@ietf.org>; Sun,  7 Oct 2018 22:49:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6dpiFVjsMozPu79eWe9xed1ks6JDkV6V55/wO8rQFjw=; b=YAsf6pTDS3hU7aA/IqWJZaR2u75QWDCo1Ga++t97jZkriTG36mTLCr0HeSYyqG5DWZM+kqU6fnWNqtJpYY9FzrBwl6C9dwBPOJeSivb+Nl+iOmuOBiw1wF3TVHR20HQEwHH8srbu/REVbo2rJl9sisUwQFlOh6jmZirYYxgIMCaNpq7f5L26Do9H5J3XYC/MO9scnq0FGknZdeMy66SnYSzOxlxz73Q7glULbAKAAd3rejf3tvWSDU41MAC9dw8w5RVxYc2aGJxMcZDKPCIpPyjP5z25QsQWMdKXG537ykcUAbyfhBaf6qaILqcJXMq0pnS5H6uGB3XAu2XDCjOG4g==
Received: from PU1APC01FT038.eop-APC01.prod.protection.outlook.com (10.152.252.59) by PU1APC01HT113.eop-APC01.prod.protection.outlook.com (10.152.253.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Mon, 8 Oct 2018 05:49:04 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.252.53) by PU1APC01FT038.mail.protection.outlook.com (10.152.253.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Mon, 8 Oct 2018 05:49:04 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995%4]) with mapi id 15.20.1228.020; Mon, 8 Oct 2018 05:49:04 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: "art@ietf.org" <art@ietf.org>
Thread-Topic: [art] can a verify envelope be coded or is it available
Thread-Index: AQHUXq3m1V6aSDhTG0aYAh26mmgeUqUUoRkAgAAsA9eAAApxLQ==
Date: Mon, 8 Oct 2018 05:49:04 +0000
Message-ID: <SG2PR0302MB2606B3A0F36B18986CEB2E00B7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com>
References: <SG2PR0302MB260622F429BD8A36C71CA510B7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com>, <CAAyEnSMbZ-i2wFn79AwwWhSvbaZLRAu1yCxLq0xUbcDkoWN7WA@mail.gmail.com>, <SG2PR0302MB26066D6F07EA02CC14734B5CB7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com>
In-Reply-To: <SG2PR0302MB26066D6F07EA02CC14734B5CB7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:A9DB4FB58A0100F5A3BEEDF07F1D901F5D03CA6ACC34F7A6B457C918F1BA5217; UpperCasedChecksum:46FC8723EB31354886D5AB428DA525DF78DC070FC459CD5772BF35D250B0D7E6; SizeAsReceived:7307; Count:46
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [wxKHOXgwwRBaoH6iqgt0JCT0q8zAnAAv]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT113; 6:KmC4d+171YrX494s+UF42qC0e35oC7dhoXMMrhAoKZQJWP2KJueCrzBKzvpfEoX6G+feV/+z+f78/h/tdxIEX7Yi8z0g3dvWb8vVK1S9Rg/pBCc/CWyYrPtzE70NSSBhyzhsHmT9cCX5jthc5ahgOPgqL5/JTeEvygMoXTL3jvcvfrKz1pdLNzuvnB5r8oOVbJ1PqakA0Z2CXRE2crZmno+2kC6UvnEtJpgPlFxh8qLzWq7U0DFH3+ojmXV7Kz8XcV1Dtcf6HS1WAWSRjnfM+1hk3AS+jfRlqRrbQWnDTE1+qPfTfi2JqON+FwQtEU3Rw9MzgYVUGcZ9Y+Uymo1Mh+nIJTZPAkP+N1A872OylsXS1NKGQRvQAXTPk0g0ramJQBKZ25aGe8GUt8HPfDDaTqQWF6Pbiq2iWB0rvy83nIgXzeNYl0t1R6wgaAPV5NKwVIA8IyXupbXTZVGto6BzHw==; 5:WiAp/NDUaG/O+8+D7XVLe4iK1cFwes5NruO1hS7zKxCevLJwxGLCswnOHOmVWygcHFC+5HG8Sp52mu/SeGetReC5pi8UYZ1NEAsKwlRbnHokQs+haqVbGkMfD8hsKsYqxcTV16R6luFK3z1CkgwVAmrcmX+wroRY4uevpxrHRzk=; 7:bOTnkH1cfW/L0pgNEEP5wC/LKrUIauRVv9WdXwLYHF5K7OAy2fB3Aw/L5Mqdb606SKI8jazHR77IL9LiEVIW7MKWCcLJlNa8yxndvLbjbIRyVLErTXN5mwL3/O9/B9vi//b2qWmqhe0XVny6/tTvoGjDYNcScYhEE5EbGGIAJqFsLoW9IOEZoK5YiVfofZNPtuPKjEDO6KZaDhrXHtHK+IuC3tDNPggLa2CeMabdSE1WTW1Nr5DvvI36KCT02+XR
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:PU1APC01HT113; 
x-ms-traffictypediagnostic: PU1APC01HT113:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:PU1APC01HT113; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT113; 
x-microsoft-antispam-message-info: FIZ1iP6kJiYt39e6O/p5MO6Gu6doXwXTnu8KTXG889rZZOUEmJGw81YeIzAV7aDK
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB2606B3A0F36B18986CEB2E00B7E60SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 5a37be82-e26c-47f6-0b35-08d62ce1c19f
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2018 05:49:04.4381 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT113
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/QX6c8_PZNPtEADEPOQv2JiYOf20>
Subject: [art] Fw:  can a verify envelope be coded or is it available
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 05:49:12 -0000

--_000_SG2PR0302MB2606B3A0F36B18986CEB2E00B7E60SG2PR0302MB2606_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


________________________________
From: pradeep xplorer <pradeepan88@hotmail.com>
Sent: Monday, October 8, 2018 10:42 AM
To: Yakov Shafranovich
Subject: Re: [art] can a verify envelope be coded or is it available

To be specific this is your message header.. I have to be able to open a Go=
ogle app input this which should say its from yakov@nightwatchcybersecurity=
.com

Begin email header
Received: from SN1NAM04HT243.eop-NAM04.prod.protection.outlook.com (2603:10=
96:3:2::26) by SG2PR0302MB2606.apcprd03.prod.outlook.com with HTTPS via SG2=
PR0302CA0016.APCPRD03.PROD.OUTLOOK.COM; Mon, 8 Oct 2018 02:33:38 +0000 Rece=
ived: from SN1NAM04FT023.eop-NAM04.prod.protection.outlook.com (10.152.88.6=
0) by SN1NAM04HT243.eop-NAM04.prod.protection.outlook.com (10.152.89.18) wi=
th Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES=
_256_CBC_SHA384_P256) id 15.20.1207.19; Mon, 8 Oct 2018 02:33:37 +0000 Auth=
entication-Results: spf=3Dpass (sender IP is 209.85.215.169) smtp.mailfrom=
=3Dnightwatchcybersecurity.com; hotmail.com; dkim=3Dpass (signature was ver=
ified) header.d=3Dnightwatchcybersecurity-com.20150623.gappssmtp.com;hotmai=
l.com; dmarc=3Dbestguesspass action=3Dnone header.from=3Dnightwatchcybersec=
urity.com; Received-SPF: Pass (protection.outlook.com: domain of nightwatch=
cybersecurity.com designates 209.85.215.169 as permitted sender) receiver=
=3Dprotection.outlook.com; client-ip=3D209.85.215.169; helo=3Dmail-pg1-f169=
.google.com; Received: from mail-pg1-f169.google.com (209.85.215.169) by SN=
1NAM04FT023.mail.protection.outlook.com (10.152.88.108) with Microsoft SMTP=
 Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384=
) id 15.20.1228.17 via Frontend Transport; Mon, 8 Oct 2018 02:33:37 +0000 X=
-IncomingTopHeaderMarker: OriginalChecksum:63EF122D0E2E1BDC4900452B85577F42=
B3FF901DF1A7E4D93D4C767AF66D6C50;UpperCasedChecksum:32D5592CAC2B7B57B9321B3=
7BA7C532CF56C18C78FE728FF48E35B326A39A28F;SizeAsReceived:2420;Count:15 Rece=
ived: by mail-pg1-f169.google.com with SMTP id v133-v6so7139345pgb.2 for <p=
radeepan88@hotmail.com>; Sun, 07 Oct 2018 19:33:37 -0700 (PDT) DKIM-Signatu=
re: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dnightwatchcybersecurity=
-com.20150623.gappssmtp.com; s=3D20150623; h=3Dmime-version:references:in-r=
eply-to:from:date:message-id:subject:to; bh=3DMBAX4Z5i1xju8yd1j1UOl4995dujn=
CTCeTuVOWJUqvw=3D; b=3Dk5mGjQWUt1eYy0zXmRFHWPPzH4Q49DPYYJL0+cO/A3Igu4yNjJeY=
UW5mW8RDo4jQxe MyNn5tQR2eXsW/Lt6Pf7wk1SM0YQE5nc6Gx8QQWLN++xsJTPCygzqB+s03yo=
uD3SfnLq NyKItOLgYxXW+9P+WF8UFtDWifh1jzEmxpwZZCbf+zJObDZoVet64EX7RYAcZ8jPFM=
6E 6nxrluLUHWQ14t6xFPr3+Csdj1q3OrVFm479V6qYBUpPD2YPqH1kmtyh3BRhkavRQZo2 4a+=
PIeiYymYm07bMqHRcSJ/MhmrhWFYSVbT3qoXTz0pU5PUEMLAyzEgYFwD0HcPIw8D1 aXpw=3D=
=3D X-Google-DKIM-Signature: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=
=3D1e100.net; s=3D20161025; h=3Dx-gm-message-state:mime-version:references:=
in-reply-to:from:date :message-id:subject:to; bh=3DMBAX4Z5i1xju8yd1j1UOl499=
5dujnCTCeTuVOWJUqvw=3D; b=3DBOWtlCBViGWVnAnBOsRC9DfOxKLmwIjsrW1QfLEubKKl0xY=
d3lfxtSFA06v2znQQwm cCZNtX1A+CBzRmjwWlmiXZ5M5r0jn7asZ/b5NErx6Va84+zDgQW55nl=
P80X6ccQGGYWg PT7UsNsBss0ii3SaUXbPgsPb3ljrqJyEw3GodWFNE2AtPGUV3bcr7VVwPsGLm=
PE4BdnH TrfDwO1OJGjYhf+dh6QuWNZ3wKfPVOxlXLZSlP0Xe6Gm4pnf7r+hNF0Rwd4/PQR6TrE=
t nJIkdjWpwFSn/epkYQS4sFa48Y/k89h9pxheg9WbgduXBVwatPv5jZyOBEcMcJgiyHt5 zeTg=
=3D=3D X-Gm-Message-State: ABuFfoixtSWcktYalgyOpG+nF3YpRF1epLshOdmw2cXbcwwO=
eIMIL4V7 wiIn3SUW2fuZoPKiA7PTPiaY6Vl20uukDc3EklWn/ZRS6qE=3D X-Google-Smtp-S=
ource: ACcGV60JJfVZPDr26Uheh+dtzJcQpWeAO54QMcwlPDVQtJVwOSKOsZ9X+CMpSMc3U/gv=
9EyKezDtp0xYix+LZFcVKUc=3D X-Received: by 2002:a62:52cc:: with SMTP id g195=
-v6mr23560680pfb.241.1538966016572; Sun, 07 Oct 2018 19:33:36 -0700 (PDT) R=
eferences: <SG2PR0302MB260622F429BD8A36C71CA510B7E60@SG2PR0302MB2606.apcprd=
03.prod.outlook.com> In-Reply-To: <SG2PR0302MB260622F429BD8A36C71CA510B7E60=
@SG2PR0302MB2606.apcprd03.prod.outlook.com> From: Yakov Shafranovich <yakov=
@nightwatchcybersecurity.com> Date: Sun, 7 Oct 2018 22:33:00 -0400 Message-=
ID: <CAAyEnSMbZ-i2wFn79AwwWhSvbaZLRAu1yCxLq0xUbcDkoWN7WA@mail.gmail.com> Su=
bject: Re: [art] can a verify envelope be coded or is it available To: prad=
eepan88@hotmail.com Content-Type: text/plain; charset=3D"UTF-8" X-IncomingH=
eaderCount: 15 Return-Path: yakov@nightwatchcybersecurity.com X-MS-Exchange=
-Organization-ExpirationStartTime: 08 Oct 2018 02:33:37.3877 (UTC) X-MS-Exc=
hange-Organization-ExpirationStartTimeReason: Original Submit X-MS-Exchange=
-Organization-ExpirationInterval: 2:00:00:00.0000000 X-MS-Exchange-Organiza=
tion-ExpirationIntervalReason: Original Submit X-MS-Exchange-Organization-N=
etwork-Message-Id: c29f4ef9-7cf6-4af9-3f40-08d62cc67396 X-EOPAttributedMess=
age: 0 X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0=
 X-MS-Exchange-Organization-MessageDirectionality: Incoming X-Microsoft-Exc=
hange-Diagnostics: 1;SN1NAM04FT023;1:XjYiP/HJjdpNlL4b49eGMFyXBBQRoJ12WfDH3F=
qlW9JdEYR1qnnAOotGwdrDZUGRF8HDk6NxsIvwVPAaSzf+M749VDXcDZYlYsPxGkWZ4OM0AnS3w=
pl8zf2f4WlQqXa+ X-Forefront-Antispam-Report: EFV:NLI; X-MS-Exchange-Organiz=
ation-AuthSource: SN1NAM04FT023.eop-NAM04.prod.protection.outlook.com X-MS-=
Exchange-Organization-AuthAs: Anonymous X-MS-PublicTrafficType: Email X-MS-=
Office365-Filtering-Correlation-Id: c29f4ef9-7cf6-4af9-3f40-08d62cc67396 X-=
Microsoft-Antispam: BCL:0;PCL:0;RULEID:(5000110)(711020)(4605076)(610169)(6=
50170)(8291501071);SRVR:SN1NAM04HT243; X-Microsoft-Exchange-Diagnostics: 1;=
SN1NAM04HT243;3:SDCBptsADYSHn2IRpYcSbBpB4dT3cLQTzOt5QxOBg4RYAlKu5ArFm0U9J0D=
HyQIhP++OWx7xwV5AgZrUR9NPnrKOPo8arjAxZ54JSVLKkso7SgtcDJDHYdwTIgY8YDWf/Nllyq=
qwzXfyhL89gd4yJZDU+0zCg+YcZ23fV7eeXxI93AO7gqo5cydbDRjezBuG8g1/JQRRd1L2BgMTE=
haoxKsILbUpc0J+yNi7Ky9GI+gsWnYzk/6hDAnbrzpb6yDfx1ZzRkov5KZ2mpkRg5lfq+Qm6rJE=
CNp3usq0U8JHFYJ3LR1dGHcul+uryt4b0fnh;25:RkPDTKNKsaNOhRrC3Oa7/73ZtxqTqsWUDQr=
bms9e4+Gk3XpDjeVsxYvaed4VVpXv4lyYL8x4xWzwjAw1hKD17hyTk7VR7bLWelwWzmtovE+pG5=
8o9n3+3+KC1UJ3UA3483KPzg7wloSgL46wGdVoCOo+84PlrDMikIgLjk64L0Xug7waXKeSD91QR=
+IzEUcC3tPmQR9iVSyFnsOFMy8XMrgEtn0j1GFi3n3E3lPGBFNUrvVMIuO2ILndJEJH9JCbwEf2=
JlbidSjixnLX0UECc/7iqt4Bea16C/BM2HCYEivhIhEXxTJpCLNSN3Fev2E5FIUXXKHtUGzGAo8=
iCY8Wvw=3D=3D;31:GDSLCdpP41+BDq0j+QbzoEHwvgcXo7umYper54Q9nGSHhFGbZp+9J3Utln=
4zDkjk5fxudX7iOsQCPByFC8B4xoxYvoCsW3l+DY22sxn5WkcnEV3QZ3P3xIxn6RGDCv68cE2fu=
mbB3Dv7dp7/suvvxv8ojFeNDd18upxLdvLg6HSwi7MGJilXAYeo0V5R7RjTzHw9LMBHAz1sY4mi=
ZTfyblb8vEZ4cFf0f9rtIfqMSzs=3D X-MS-TrafficTypeDiagnostic: SN1NAM04HT243: X=
-MS-Exchange-EOPDirect: true X-Sender-IP: 209.85.215.169 X-SID-PRA: YAKOV@N=
IGHTWATCHCYBERSECURITY.COM X-SID-Result: PASS X-MS-Exchange-Organization-PC=
L: 2 X-Exchange-Antispam-Report-Test: UriScan:(194151415913766)(13087303641=
7446); X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(444111676)(=
52401380)(52601095)(52606095)(52505095)(52406095)(52305095)(52206095)(88862=
240)(88860193)(82015058);SRVR:SN1NAM04HT243;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM=
04HT243; X-Microsoft-Exchange-Diagnostics: 1;SN1NAM04HT243;4:33eFeMoKCr86iZ=
NSLD61MXai5YtyO18haT/j3HfxZRqVgN367ivoA4DK6lx0jxkurw2QnlKP8mB0WPNLq33V4x1y9=
QpNUUQQ87SxSvHjkaU1kFCvU2qarz9qCMLHVOls7zCMHZcv8fxnK1UUx5ryTwm3a6N+baN6vrhD=
aT++YXrtu5XKV9VFrXSx+O13anJ24RCW4HRTl0x5jtxFwu+tC6cAele51/YhwZ5xpbSqXbT8i2V=
BZNbfdoA8bIRObZKSYdfqizSlJ8y5G7cNAwey5iF9OAF9ZvzphR6cRrwCIyML0QX5druhaGtqpH=
bHa1WHfDlY7jPNigHkOQBM1jA4hcGMvYKXNjBrpOJrIPqsST4=3D;6:9GnNYHAAzo3mwcVG+TdN=
9k1qfhQmEmfSdUK+j6MqEJni4cvQvq0nncon90BXNUPUTbUxGmyHz5C4MzzJ2dJO40y1TRW9DKp=
rQh+rOJDkNMKmnxxsxlH526SBCQ5Uny5A//CZW6hwbWpb6AoNRC/BCtDcgu2pXqXNg8fLD7kEjw=
rbwxMeoNbbIWv+gOZoUZV063z1wn1Zcfa0LLdC2R78iNp9s7W8U73n4wl6H3RO4yjmAV2GdUaHi=
oP7fR/eRAZxeIUizhJJ3goopBz+TFp8GokbV1SJRz2DFqWSpe51Jelv0QvSShhgdWWGoxt5y3vb=
ByFCxYQnqxDHodFyq8+aVpI5WXJJ2XqCqR2Mjzmfb8ueReTtuWEvAiQHHRC3Fz0cXw+aJt9IJRf=
Vn2WSPZTpNBrtiYv3OXcrQ8PHc7xtYYoxtihN+LoFVb2L/mQkm8qinJ9+UUzLIWaAa63TC3gXBQ=
=3D=3D X-Microsoft-Antispam-Message-Info: nY7HWqAoQOZJ55vE7H2KapB/2w341Y6jK=
QNc5E0P2b+WzsQ6U/QQAr+Zal71rMG2JwFQQMlgHOdTLH1g62N7OGBzj7iqk8/npTSVQ0q5oa+Z=
5IrZ8NdnEL4cn8jQ7EZ6NtVBPtyRPqRVuc9C/udZYrw2vyF0WjpgP8FpN6jD8O+PTE88yH9XkTF=
Rijt2h87uctNViqFe+FM+1L5GndbNyvDEiMaasi/1gZ8eH9Un+qW3XdkWpyDjfnMm7BKBFTDMY0=
q4zcMvbbzHdrIocMuvwJ7VER9oGEDBXp+hfSdWq5rUm5EIEJXSsGrPUckOScMGZgiFIbQy7gXt9=
1x69j+yI+4Z7T8BwP5pOpJR4JQEuN3RuGZlFFJf71NFYG1KTRcSYVd8sAKrUCsLNqOOuujN2DaD=
VRMA60Wjn1ASR1GMuMOGIUs2fichI86w2r5PKbxmX4FLZ2tv6nMXMd3mIA8XvgDVXIkMYzxD4EG=
gjLye1DXWSaEM3DXtVTJlKeY+YFdw X-Microsoft-Exchange-Diagnostics: 1;SN1NAM04H=
T243;5:AsRiF5MdBI0u8U76bI8YRkK26AjtcLAqdeilQz0oI3yR1/zF7YSBI+d04S6qKBvkZ8km=
9euHU1VXE5eFR1helwLiGgzzeT+fxNVzsKv7X3/LvfRvbzTcD2+TSCXX3g3ZNLSH7TUX2tnaxhw=
Jhwt8bO3UZw4V2LGRrUUyhYa3dG4=3D;7:TBCKu0MPyFnWeeUhb1ekbp8vd7Vo2vaKhLS4vA4RS=
EJYhic1R6AEytqkGGXUkxT7V8vclMp2SZmqbaxyyOUR783S2XW1bDeM8fC22glHmlyNUsC5RY1p=
9eoOmz32QJNHYQIufDRhALkM/wHumXE/rVfRL7Y2DnbxE5cIecHRs8a+HDnIc7DAfOJ7MGsXUN0=
Dd7tGfpAChuA5aWAEU5mIQ/pwVM8W8Xh1n/SKvAMfa7NPQj0xc1TNFZ6G8P0OAyR9 X-Origina=
torOrg: outlook.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Oct 2=
018 02:33:37.3564 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: c29f4=
ef9-7cf6-4af9-3f40-08d62cc67396 X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6=
-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-FromEntityHeader: Interne=
t X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: d4d70346-2c10-4f39-8c=
00-e767963926d9 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04=
HT243 X-MS-Exchange-Transport-EndToEndLatency: 00:00:00.9536230 X-MS-Exchan=
ge-Processed-By-BccFoldering: 15.20.1228.020 X-Microsoft-Exchange-Diagnosti=
cs: 1;SG2PR0302MB2606;27:NhS8kqlv4+uzsa/1x2PG/Tgnmwk6qbxoqG8Z58+LhFa6fgZQrf=
E8UecWZhcg+xM5cL9rs5AvfrVezHUSFIZD/sVlbtpQFqpFQMaBkyOcMHtq3AxrZ4Qf+yPnZVIsC=
RhLJFfaCsfqGeedH1mXLBhJvjtz/NRsug1giVnLQFdKkwr0nxJQ7JZwBs1CuOmUO/qjk7EC8h3/=
qx9u1cPpGkGHdVWQ+VlwMKLVpfEJNcS2/4zS+w/f9NSWHb3v1u5j9YW9rHzV/hqVuy04ad5exSD=
jF/ApVO6u1oBJp9ll5O8HFI2d8wKNDlwfUKzxzlPVmIlf/7UYcPfnv9GUgcPLP9x4ZffFtMypmK=
hZX4XQXShL6OkFjKw9cEQmbbDs/gjbqhQILwUjHcwt8PghmbNkuWDJyyYkEFZNUJrc5MqdKwXiG=
yqIjPl6C6KDhc3ykwW766vur3nZSqAhFdAfm+6lh1A9EvTp2m3L+UDX8u0Lcd64IosCuUUwgTtn=
N0tA6FjgYZUHVsIBhHR3jN1TaAJQ6EVVN23vSRVW4GJpd7NUDdlUOqI3DDxfGr9aADCo7700Rai=
XQeQmMWD9JmR9hGT9eeTw17sPNMZvPLd9w4ulgQbcwTXCUFaPlQsdQcoaEeCK/7LO+/3CX9+koC=
+xvlpzVQJs1yXGPHV7qPTjznW6tsX+mYP5rZsB8KRcxSvZumgqP/AMLJyeAenNqP6u7iX696pDj=
w=3D=3D X-Microsoft-Antispam-Mailbox-Delivery: abwl:0;wl:0;pcwl:0;kl:0;iwl:=
0;dwl:0;dkl:0;rwl:0;ucf:0;jmr:0;ex:0;auth:1;dest:I;OFR:SpamFilterPass;ENG:(=
5062000261)(5061607266)(5061608174)(1005109)(4900095)(4920089)(6225004)(495=
0130)(4990090)(9110004); X-Message-Info: 5vMbyqxGkdcR/d/GnxoxXg6+J8QvV+lODn=
pRwYaCGhtW0uhxq+m/Y8WixcOaDSesqqjEJWvJTqOYO5mwg0ziGKiW5FOMU94Oxfgh1ndim0iuV=
5Eceer6Aux1TXAikOf5kbkDn8YBjTOhKGZwTcgaiAUx2mzatcwjfAgezn3h8+QBwBzIBiFlSkx7=
kvbbsAiM+WpmVpO7+IQDi0VRjAtHPg=3D=3D X-Message-Delivery: Vj0xLjE7dXM9MDtsPT=
A7YT0xO0Q9MTtHRD0xO1NDTD0tMQ=3D=3D X-Microsoft-Antispam-Message-Info: GxvYS=
qooZznFk6j55a4tMxPrQ/52msvwZ4V0LWYBsrvTvWcfSBY8IKkQ45uHtBFLbsAocZPnu/SIQyBK=
YGPQUOkC75JymWi23mEwku4Fm7/+stQqFOJSDgB6Bo82ZNCUAbS8aaQ0zADnf2Orn/qGE9nog2s=
T7FBRHtFz7RKyIF2OOEXPks7ms4WrZ3RzbdCE+vJXfkJXttAK1VKiwrXZxdKhU5jl8hWQpu18tK=
EVXMp6QkayCUC7lVe8GF5M9ybAwQmrLnwPn8CL8wnJZA7xMEEOEpqHcDlUbOKg0Wtcgb3xlrKdk=
3iZkARIfVSvwcKTsN/dBc4CCgDZG2xtFI7aa7LOAJADsOFOy3KkF4n7MzE4J//4GApXwJZys9hA=
r31G8w4xNEMbKFoE2PTdq8I7+3X7jPVniNIpQGu2qXqyjdIfCMLTWby48PoohSTEemC322sPf1C=
53A/Rahf0nU+Kwa8ypfDmbcrEfj05WVw5fuDUDUDXmcowJTinTAX9y5QzhdE97ILonL4+QI73D5=
ZbH3t4QqQg5JZiqFKw1kc6+a9bri3wecf6YMR39kHzWoj6NaOLKbzQkwd6BwC5USDG6hb1/HVAN=
HD9L1krpqhwunT4KSciJT+R/k37RpnUn+qvUU1OL1JYOIoDiOCUXgx1Jtr/a3BFAO7CGkhu90VX=
O/9TEw9C0/xx69D2RGuWNGc91UjyHqWON/K9TMQ2xTKxy3JrA1xCTa7KGSl8c1Yi9iEM9eCfTwb=
DBl8/7OM27DE+j0ne71SIUpMNfJ0SW6b48Dr1+PsXeYdoPVA9cCh7een4HCf6+w9isDVakXRtbi=
Xj5roL2JlCdt+v65daQiMekQ=3D=3D MIME-Version: 1.0
End EMail header
________________________________
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Sent: Monday, October 8, 2018 8:03 AM
To: pradeepan88@hotmail.com
Subject: Re: [art] can a verify envelope be coded or is it available

See SPF, DKIM and DMARC
On Sun, Oct 7, 2018 at 10:29 PM pradeep xplorer <pradeepan88@hotmail.com> w=
rote:
>


--_000_SG2PR0302MB2606B3A0F36B18986CEB2E00B7E60SG2PR0302MB2606_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> pradeep xplorer &lt;p=
radeepan88@hotmail.com&gt;<br>
<b>Sent:</b> Monday, October 8, 2018 10:42 AM<br>
<b>To:</b> Yakov Shafranovich<br>
<b>Subject:</b> Re: [art] can a verify envelope be coded or is it available=
</font>
<div>&nbsp;</div>
</div>
<div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
To be specific this is your message header.. I have to be able to open a Go=
ogle app input this which should say its from&nbsp;<span style=3D"color:rgb=
(0,0,0); font-family:Calibri,Helvetica,sans-serif; font-size:12pt">yakov@ni=
ghtwatchcybersecurity.com</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Begin email header&nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span style=3D"color:rgb(51,51,51); font-size:14px; text-align:left; backgr=
ound-color:rgb(255,255,255); display:inline!important">Received: from SN1NA=
M04HT243.eop-NAM04.prod.protection.outlook.com (2603:1096:3:2::26) by SG2PR=
0302MB2606.apcprd03.prod.outlook.com
 with HTTPS via SG2PR0302CA0016.APCPRD03.PROD.OUTLOOK.COM; Mon, 8 Oct 2018 =
02:33:38 &#43;0000 Received: from SN1NAM04FT023.eop-NAM04.prod.protection.o=
utlook.com (10.152.88.60) by SN1NAM04HT243.eop-NAM04.prod.protection.outloo=
k.com (10.152.89.18) with Microsoft
 SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA=
384_P256) id 15.20.1207.19; Mon, 8 Oct 2018 02:33:37 &#43;0000 Authenticati=
on-Results: spf=3Dpass (sender IP is 209.85.215.169) smtp.mailfrom=3Dnightw=
atchcybersecurity.com; hotmail.com; dkim=3Dpass
 (signature was verified) header.d=3Dnightwatchcybersecurity-com.20150623.g=
appssmtp.com;hotmail.com; dmarc=3Dbestguesspass action=3Dnone header.from=
=3Dnightwatchcybersecurity.com; Received-SPF: Pass (protection.outlook.com:=
 domain of nightwatchcybersecurity.com designates
 209.85.215.169 as permitted sender) receiver=3Dprotection.outlook.com; cli=
ent-ip=3D209.85.215.169; helo=3Dmail-pg1-f169.google.com; Received: from ma=
il-pg1-f169.google.com (209.85.215.169) by SN1NAM04FT023.mail.protection.ou=
tlook.com (10.152.88.108) with Microsoft
 SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA=
_P384) id 15.20.1228.17 via Frontend Transport; Mon, 8 Oct 2018 02:33:37 &#=
43;0000 X-IncomingTopHeaderMarker: OriginalChecksum:63EF122D0E2E1BDC4900452=
B85577F42B3FF901DF1A7E4D93D4C767AF66D6C50;UpperCasedChecksum:32D5592CAC2B7B=
57B9321B37BA7C532CF56C18C78FE728FF48E35B326A39A28F;SizeAsReceived:2420;Coun=
t:15
 Received: by mail-pg1-f169.google.com with SMTP id v133-v6so7139345pgb.2 f=
or &lt;pradeepan88@hotmail.com&gt;; Sun, 07 Oct 2018 19:33:37 -0700 (PDT) D=
KIM-Signature: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dnightwatchcy=
bersecurity-com.20150623.gappssmtp.com; s=3D20150623;
 h=3Dmime-version:references:in-reply-to:from:date:message-id:subject:to; b=
h=3DMBAX4Z5i1xju8yd1j1UOl4995dujnCTCeTuVOWJUqvw=3D; b=3Dk5mGjQWUt1eYy0zXmRF=
HWPPzH4Q49DPYYJL0&#43;cO/A3Igu4yNjJeYUW5mW8RDo4jQxe MyNn5tQR2eXsW/Lt6Pf7wk1=
SM0YQE5nc6Gx8QQWLN&#43;&#43;xsJTPCygzqB&#43;s03youD3SfnLq
 NyKItOLgYxXW&#43;9P&#43;WF8UFtDWifh1jzEmxpwZZCbf&#43;zJObDZoVet64EX7RYAcZ8=
jPFM6E 6nxrluLUHWQ14t6xFPr3&#43;Csdj1q3OrVFm479V6qYBUpPD2YPqH1kmtyh3BRhkavR=
QZo2 4a&#43;PIeiYymYm07bMqHRcSJ/MhmrhWFYSVbT3qoXTz0pU5PUEMLAyzEgYFwD0HcPIw8=
D1 aXpw=3D=3D X-Google-DKIM-Signature: v=3D1; a=3Drsa-sha256;
 c=3Drelaxed/relaxed; d=3D1e100.net; s=3D20161025; h=3Dx-gm-message-state:m=
ime-version:references:in-reply-to:from:date :message-id:subject:to; bh=3DM=
BAX4Z5i1xju8yd1j1UOl4995dujnCTCeTuVOWJUqvw=3D; b=3DBOWtlCBViGWVnAnBOsRC9DfO=
xKLmwIjsrW1QfLEubKKl0xYd3lfxtSFA06v2znQQwm cCZNtX1A&#43;CBzRmjwWlmiXZ5M5r0j=
n7asZ/b5NErx6Va84&#43;zDgQW55nlP80X6ccQGGYWg
 PT7UsNsBss0ii3SaUXbPgsPb3ljrqJyEw3GodWFNE2AtPGUV3bcr7VVwPsGLmPE4BdnH TrfDw=
O1OJGjYhf&#43;dh6QuWNZ3wKfPVOxlXLZSlP0Xe6Gm4pnf7r&#43;hNF0Rwd4/PQR6TrEt nJI=
kdjWpwFSn/epkYQS4sFa48Y/k89h9pxheg9WbgduXBVwatPv5jZyOBEcMcJgiyHt5 zeTg=3D=
=3D X-Gm-Message-State: ABuFfoixtSWcktYalgyOpG&#43;nF3YpRF1epLshOdmw2cXbcww=
OeIMIL4V7
 wiIn3SUW2fuZoPKiA7PTPiaY6Vl20uukDc3EklWn/ZRS6qE=3D X-Google-Smtp-Source: A=
CcGV60JJfVZPDr26Uheh&#43;dtzJcQpWeAO54QMcwlPDVQtJVwOSKOsZ9X&#43;CMpSMc3U/gv=
9EyKezDtp0xYix&#43;LZFcVKUc=3D X-Received: by 2002:a62:52cc:: with SMTP id =
g195-v6mr23560680pfb.241.1538966016572; Sun, 07
 Oct 2018 19:33:36 -0700 (PDT) References: &lt;SG2PR0302MB260622F429BD8A36C=
71CA510B7E60@SG2PR0302MB2606.apcprd03.prod.outlook.com&gt; In-Reply-To: &lt=
;SG2PR0302MB260622F429BD8A36C71CA510B7E60@SG2PR0302MB2606.apcprd03.prod.out=
look.com&gt; From: Yakov Shafranovich &lt;yakov@nightwatchcybersecurity.com=
&gt;
 Date: Sun, 7 Oct 2018 22:33:00 -0400 Message-ID: &lt;CAAyEnSMbZ-i2wFn79Aww=
WhSvbaZLRAu1yCxLq0xUbcDkoWN7WA@mail.gmail.com&gt; Subject: Re: [art] can a =
verify envelope be coded or is it available To: pradeepan88@hotmail.com Con=
tent-Type: text/plain; charset=3D&quot;UTF-8&quot;
 X-IncomingHeaderCount: 15 Return-Path: yakov@nightwatchcybersecurity.com X=
-MS-Exchange-Organization-ExpirationStartTime: 08 Oct 2018 02:33:37.3877 (U=
TC) X-MS-Exchange-Organization-ExpirationStartTimeReason: Original Submit X=
-MS-Exchange-Organization-ExpirationInterval:
 2:00:00:00.0000000 X-MS-Exchange-Organization-ExpirationIntervalReason: Or=
iginal Submit X-MS-Exchange-Organization-Network-Message-Id: c29f4ef9-7cf6-=
4af9-3f40-08d62cc67396 X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessa=
ge: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
 X-MS-Exchange-Organization-MessageDirectionality: Incoming X-Microsoft-Exc=
hange-Diagnostics: 1;SN1NAM04FT023;1:XjYiP/HJjdpNlL4b49eGMFyXBBQRoJ12WfDH3F=
qlW9JdEYR1qnnAOotGwdrDZUGRF8HDk6NxsIvwVPAaSzf&#43;M749VDXcDZYlYsPxGkWZ4OM0A=
nS3wpl8zf2f4WlQqXa&#43; X-Forefront-Antispam-Report:
 EFV:NLI; X-MS-Exchange-Organization-AuthSource: SN1NAM04FT023.eop-NAM04.pr=
od.protection.outlook.com X-MS-Exchange-Organization-AuthAs: Anonymous X-MS=
-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: c29f4ef9=
-7cf6-4af9-3f40-08d62cc67396 X-Microsoft-Antispam:
 BCL:0;PCL:0;RULEID:(5000110)(711020)(4605076)(610169)(650170)(8291501071);=
SRVR:SN1NAM04HT243; X-Microsoft-Exchange-Diagnostics: 1;SN1NAM04HT243;3:SDC=
BptsADYSHn2IRpYcSbBpB4dT3cLQTzOt5QxOBg4RYAlKu5ArFm0U9J0DHyQIhP&#43;&#43;OWx=
7xwV5AgZrUR9NPnrKOPo8arjAxZ54JSVLKkso7SgtcDJDHYdwTIgY8YDWf/NllyqqwzXfyhL89g=
d4yJZDU&#43;0zCg&#43;YcZ23fV7eeXxI93AO7gqo5cydbDRjezBuG8g1/JQRRd1L2BgMTEhao=
xKsILbUpc0J&#43;yNi7Ky9GI&#43;gsWnYzk/6hDAnbrzpb6yDfx1ZzRkov5KZ2mpkRg5lfq&#=
43;Qm6rJECNp3usq0U8JHFYJ3LR1dGHcul&#43;uryt4b0fnh;25:RkPDTKNKsaNOhRrC3Oa7/7=
3ZtxqTqsWUDQrbms9e4&#43;Gk3XpDjeVsxYvaed4VVpXv4lyYL8x4xWzwjAw1hKD17hyTk7VR7=
bLWelwWzmtovE&#43;pG58o9n3&#43;3&#43;KC1UJ3UA3483KPzg7wloSgL46wGdVoCOo&#43;=
84PlrDMikIgLjk64L0Xug7waXKeSD91QR&#43;IzEUcC3tPmQR9iVSyFnsOFMy8XMrgEtn0j1GF=
i3n3E3lPGBFNUrvVMIuO2ILndJEJH9JCbwEf2JlbidSjixnLX0UECc/7iqt4Bea16C/BM2HCYEi=
vhIhEXxTJpCLNSN3Fev2E5FIUXXKHtUGzGAo8iCY8Wvw=3D=3D;31:GDSLCdpP41&#43;BDq0j&=
#43;QbzoEHwvgcXo7umYper54Q9nGSHhFGbZp&#43;9J3Utln4zDkjk5fxudX7iOsQCPByFC8B4=
xoxYvoCsW3l&#43;DY22sxn5WkcnEV3QZ3P3xIxn6RGDCv68cE2fumbB3Dv7dp7/suvvxv8ojFe=
NDd18upxLdvLg6HSwi7MGJilXAYeo0V5R7RjTzHw9LMBHAz1sY4miZTfyblb8vEZ4cFf0f9rtIf=
qMSzs=3D
 X-MS-TrafficTypeDiagnostic: SN1NAM04HT243: X-MS-Exchange-EOPDirect: true X=
-Sender-IP: 209.85.215.169 X-SID-PRA: YAKOV@NIGHTWATCHCYBERSECURITY.COM X-S=
ID-Result: PASS X-MS-Exchange-Organization-PCL: 2 X-Exchange-Antispam-Repor=
t-Test: UriScan:(194151415913766)(130873036417446);
 X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(444111676)(524013=
80)(52601095)(52606095)(52505095)(52406095)(52305095)(52206095)(88862240)(8=
8860193)(82015058);SRVR:SN1NAM04HT243;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM04HT24=
3; X-Microsoft-Exchange-Diagnostics:
 1;SN1NAM04HT243;4:33eFeMoKCr86iZNSLD61MXai5YtyO18haT/j3HfxZRqVgN367ivoA4DK=
6lx0jxkurw2QnlKP8mB0WPNLq33V4x1y9QpNUUQQ87SxSvHjkaU1kFCvU2qarz9qCMLHVOls7zC=
MHZcv8fxnK1UUx5ryTwm3a6N&#43;baN6vrhDaT&#43;&#43;YXrtu5XKV9VFrXSx&#43;O13an=
J24RCW4HRTl0x5jtxFwu&#43;tC6cAele51/YhwZ5xpbSqXbT8i2VBZNbfdoA8bIRObZKSYdfqi=
zSlJ8y5G7cNAwey5iF9OAF9ZvzphR6cRrwCIyML0QX5druhaGtqpHbHa1WHfDlY7jPNigHkOQBM=
1jA4hcGMvYKXNjBrpOJrIPqsST4=3D;6:9GnNYHAAzo3mwcVG&#43;TdN9k1qfhQmEmfSdUK&#4=
3;j6MqEJni4cvQvq0nncon90BXNUPUTbUxGmyHz5C4MzzJ2dJO40y1TRW9DKprQh&#43;rOJDkN=
MKmnxxsxlH526SBCQ5Uny5A//CZW6hwbWpb6AoNRC/BCtDcgu2pXqXNg8fLD7kEjwrbwxMeoNbb=
IWv&#43;gOZoUZV063z1wn1Zcfa0LLdC2R78iNp9s7W8U73n4wl6H3RO4yjmAV2GdUaHioP7fR/=
eRAZxeIUizhJJ3goopBz&#43;TFp8GokbV1SJRz2DFqWSpe51Jelv0QvSShhgdWWGoxt5y3vbBy=
FCxYQnqxDHodFyq8&#43;aVpI5WXJJ2XqCqR2Mjzmfb8ueReTtuWEvAiQHHRC3Fz0cXw&#43;aJ=
t9IJRfVn2WSPZTpNBrtiYv3OXcrQ8PHc7xtYYoxtihN&#43;LoFVb2L/mQkm8qinJ9&#43;UUzL=
IWaAa63TC3gXBQ=3D=3D
 X-Microsoft-Antispam-Message-Info: nY7HWqAoQOZJ55vE7H2KapB/2w341Y6jKQNc5E0=
P2b&#43;WzsQ6U/QQAr&#43;Zal71rMG2JwFQQMlgHOdTLH1g62N7OGBzj7iqk8/npTSVQ0q5oa=
&#43;Z5IrZ8NdnEL4cn8jQ7EZ6NtVBPtyRPqRVuc9C/udZYrw2vyF0WjpgP8FpN6jD8O&#43;PT=
E88yH9XkTFRijt2h87uctNViqFe&#43;FM&#43;1L5GndbNyvDEiMaasi/1gZ8eH9Un&#43;qW3=
XdkWpyDjfnMm7BKBFTDMY0q4zcMvbbzHdrIocMuvwJ7VER9oGEDBXp&#43;hfSdWq5rUm5EIEJX=
SsGrPUckOScMGZgiFIbQy7gXt91x69j&#43;yI&#43;4Z7T8BwP5pOpJR4JQEuN3RuGZlFFJf71=
NFYG1KTRcSYVd8sAKrUCsLNqOOuujN2DaDVRMA60Wjn1ASR1GMuMOGIUs2fichI86w2r5PKbxmX=
4FLZ2tv6nMXMd3mIA8XvgDVXIkMYzxD4EGgjLye1DXWSaEM3DXtVTJlKeY&#43;YFdw
 X-Microsoft-Exchange-Diagnostics: 1;SN1NAM04HT243;5:AsRiF5MdBI0u8U76bI8YRk=
K26AjtcLAqdeilQz0oI3yR1/zF7YSBI&#43;d04S6qKBvkZ8km9euHU1VXE5eFR1helwLiGgzze=
T&#43;fxNVzsKv7X3/LvfRvbzTcD2&#43;TSCXX3g3ZNLSH7TUX2tnaxhwJhwt8bO3UZw4V2LGR=
rUUyhYa3dG4=3D;7:TBCKu0MPyFnWeeUhb1ekbp8vd7Vo2vaKhLS4vA4RSEJYhic1R6AEytqkGG=
XUkxT7V8vclMp2SZmqbaxyyOUR783S2XW1bDeM8fC22glHmlyNUsC5RY1p9eoOmz32QJNHYQIuf=
DRhALkM/wHumXE/rVfRL7Y2DnbxE5cIecHRs8a&#43;HDnIc7DAfOJ7MGsXUN0Dd7tGfpAChuA5=
aWAEU5mIQ/pwVM8W8Xh1n/SKvAMfa7NPQj0xc1TNFZ6G8P0OAyR9
 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-OriginalArrivalTime=
: 08 Oct 2018 02:33:37.3564 (UTC) X-MS-Exchange-CrossTenant-Network-Message=
-Id: c29f4ef9-7cf6-4af9-3f40-08d62cc67396 X-MS-Exchange-CrossTenant-Id: 84d=
f9e7f-e9f6-40af-b435-aaaaaaaaaaaa
 X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-CrossTe=
nant-RMS-PersistedConsumerOrg: d4d70346-2c10-4f39-8c00-e767963926d9 X-MS-Ex=
change-Transport-CrossTenantHeadersStamped: SN1NAM04HT243 X-MS-Exchange-Tra=
nsport-EndToEndLatency: 00:00:00.9536230
 X-MS-Exchange-Processed-By-BccFoldering: 15.20.1228.020 X-Microsoft-Exchan=
ge-Diagnostics: 1;SG2PR0302MB2606;27:NhS8kqlv4&#43;uzsa/1x2PG/Tgnmwk6qbxoqG=
8Z58&#43;LhFa6fgZQrfE8UecWZhcg&#43;xM5cL9rs5AvfrVezHUSFIZD/sVlbtpQFqpFQMaBk=
yOcMHtq3AxrZ4Qf&#43;yPnZVIsCRhLJFfaCsfqGeedH1mXLBhJvjtz/NRsug1giVnLQFdKkwr0=
nxJQ7JZwBs1CuOmUO/qjk7EC8h3/qx9u1cPpGkGHdVWQ&#43;VlwMKLVpfEJNcS2/4zS&#43;w/=
f9NSWHb3v1u5j9YW9rHzV/hqVuy04ad5exSDjF/ApVO6u1oBJp9ll5O8HFI2d8wKNDlwfUKzxzl=
PVmIlf/7UYcPfnv9GUgcPLP9x4ZffFtMypmKhZX4XQXShL6OkFjKw9cEQmbbDs/gjbqhQILwUjH=
cwt8PghmbNkuWDJyyYkEFZNUJrc5MqdKwXiGyqIjPl6C6KDhc3ykwW766vur3nZSqAhFdAfm&#4=
3;6lh1A9EvTp2m3L&#43;UDX8u0Lcd64IosCuUUwgTtnN0tA6FjgYZUHVsIBhHR3jN1TaAJQ6EV=
VN23vSRVW4GJpd7NUDdlUOqI3DDxfGr9aADCo7700RaiXQeQmMWD9JmR9hGT9eeTw17sPNMZvPL=
d9w4ulgQbcwTXCUFaPlQsdQcoaEeCK/7LO&#43;/3CX9&#43;koC&#43;xvlpzVQJs1yXGPHV7q=
PTjznW6tsX&#43;mYP5rZsB8KRcxSvZumgqP/AMLJyeAenNqP6u7iX696pDjw=3D=3D
 X-Microsoft-Antispam-Mailbox-Delivery: abwl:0;wl:0;pcwl:0;kl:0;iwl:0;dwl:0=
;dkl:0;rwl:0;ucf:0;jmr:0;ex:0;auth:1;dest:I;OFR:SpamFilterPass;ENG:(5062000=
261)(5061607266)(5061608174)(1005109)(4900095)(4920089)(6225004)(4950130)(4=
990090)(9110004); X-Message-Info:
 5vMbyqxGkdcR/d/GnxoxXg6&#43;J8QvV&#43;lODnpRwYaCGhtW0uhxq&#43;m/Y8WixcOaDS=
esqqjEJWvJTqOYO5mwg0ziGKiW5FOMU94Oxfgh1ndim0iuV5Eceer6Aux1TXAikOf5kbkDn8YBj=
TOhKGZwTcgaiAUx2mzatcwjfAgezn3h8&#43;QBwBzIBiFlSkx7kvbbsAiM&#43;WpmVpO7&#43=
;IQDi0VRjAtHPg=3D=3D X-Message-Delivery: Vj0xLjE7dXM9MDtsPTA7YT0xO0Q9MTtHRD=
0xO1NDTD0tMQ=3D=3D
 X-Microsoft-Antispam-Message-Info: GxvYSqooZznFk6j55a4tMxPrQ/52msvwZ4V0LWY=
BsrvTvWcfSBY8IKkQ45uHtBFLbsAocZPnu/SIQyBKYGPQUOkC75JymWi23mEwku4Fm7/&#43;st=
QqFOJSDgB6Bo82ZNCUAbS8aaQ0zADnf2Orn/qGE9nog2sT7FBRHtFz7RKyIF2OOEXPks7ms4WrZ=
3RzbdCE&#43;vJXfkJXttAK1VKiwrXZxdKhU5jl8hWQpu18tKEVXMp6QkayCUC7lVe8GF5M9ybA=
wQmrLnwPn8CL8wnJZA7xMEEOEpqHcDlUbOKg0Wtcgb3xlrKdk3iZkARIfVSvwcKTsN/dBc4CCgD=
ZG2xtFI7aa7LOAJADsOFOy3KkF4n7MzE4J//4GApXwJZys9hAr31G8w4xNEMbKFoE2PTdq8I7&#=
43;3X7jPVniNIpQGu2qXqyjdIfCMLTWby48PoohSTEemC322sPf1C53A/Rahf0nU&#43;Kwa8yp=
fDmbcrEfj05WVw5fuDUDUDXmcowJTinTAX9y5QzhdE97ILonL4&#43;QI73D5ZbH3t4QqQg5JZi=
qFKw1kc6&#43;a9bri3wecf6YMR39kHzWoj6NaOLKbzQkwd6BwC5USDG6hb1/HVANHD9L1krpqh=
wunT4KSciJT&#43;R/k37RpnUn&#43;qvUU1OL1JYOIoDiOCUXgx1Jtr/a3BFAO7CGkhu90VXO/=
9TEw9C0/xx69D2RGuWNGc91UjyHqWON/K9TMQ2xTKxy3JrA1xCTa7KGSl8c1Yi9iEM9eCfTwbDB=
l8/7OM27DE&#43;j0ne71SIUpMNfJ0SW6b48Dr1&#43;PsXeYdoPVA9cCh7een4HCf6&#43;w9i=
sDVakXRtbiXj5roL2JlCdt&#43;v65daQiMekQ=3D=3D
 MIME-Version: 1.0 </span><br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span style=3D"color:rgb(51,51,51); font-size:14px; text-align:left; backgr=
ound-color:rgb(255,255,255); display:inline!important">End EMail header</sp=
an></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Yakov Shafranovich &l=
t;yakov@nightwatchcybersecurity.com&gt;<br>
<b>Sent:</b> Monday, October 8, 2018 8:03 AM<br>
<b>To:</b> pradeepan88@hotmail.com<br>
<b>Subject:</b> Re: [art] can a verify envelope be coded or is it available=
</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt"=
>
<div class=3D"PlainText">See SPF, DKIM and DMARC<br>
On Sun, Oct 7, 2018 at 10:29 PM pradeep xplorer &lt;pradeepan88@hotmail.com=
&gt; wrote:<br>
&gt;<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>

--_000_SG2PR0302MB2606B3A0F36B18986CEB2E00B7E60SG2PR0302MB2606_--


From nobody Mon Oct  8 09:06:46 2018
Return-Path: <ted.ietf@gmail.com>
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 2D4F5130E99 for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 cl__4_VwsEbC for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 09:06:40 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 EBE83130DE1 for <art@ietf.org>; Mon,  8 Oct 2018 09:06:39 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id l1so7107365otj.5 for <art@ietf.org>; Mon, 08 Oct 2018 09:06:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j8BYzjYZlvfI5XKzc8tTlsWKgtsB3qyHkRosXozhCZk=; b=RsD7QXzLOsJW75gdRg6gLrHXo4+Vz0DpCiN+oau/rQzYUaIc76A9MzJoaeiW7dp/J/ JanEp6uTNelRNdC7uQmc+ynwHf5swz2k4I+qdukyoHPgtrAuTehnQWCfEZoPKdA8ntBe k7nM4IwXzdmkftMngSeVqEKbKwrFz/gSFl9/yvs+9XwPcj9TAhYP0z1rXgjLmYbpsqDL 6H51S3jcEXR2U6rUmCo+m5f9qS8GZZ8aP9pIr2zMTjRS5cW4sxPc2MT0Ftkm8Cosyg4C oPVJdbPg7yWvs0K15Qy1WeOJokJWR1NZQb/HaZDQyXMGMp4FAUS2iHJxpz+GP1SrUGto SYyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j8BYzjYZlvfI5XKzc8tTlsWKgtsB3qyHkRosXozhCZk=; b=RFZh/Aq/6ZW6CtMVK2YOTa7Nlf4BMC55Hkl8sVO29ME30vs9dtdPEfQT4kwbL/ZI9q zTWOnwgF7lQrk/1ddlZZYAm4u2oHxBdfYpI+TgWRUdTdqOaOm2YYmmoV5qXNODZrXDr/ kaNCh37CwGVZWM4vq8SuzGPVgoXWzc5YV5oSpi3USXdGQxyX+ljqwpZhJ0/6/mquLxaK 8rbfJc6HBhQLFXMZG8Ykfnh+VZK2j6+xidW1ZTuexYYn1rJ7CdMdreSOMJqiKIDTZfSP wFLMDJpO8MGwZqykmyG7bVrCuORRIMjMUeiG/4igQevnOgXL2ytKi2+YRG9wezPpfMwL JNMQ==
X-Gm-Message-State: ABuFfohRdDXxMXYkHkDV5LQKLOgs8yNjTsJCeGmejyI5bjsV4G7HVb/+ QSeZeT0jwqOelFma2V/XUvNFCcGOe9NiCeiuFvQ=
X-Google-Smtp-Source: ACcGV61kPWawsXTA7+BIxO5Jks6hjtiWRdHqZTHUWsCXgdDRviA/WBQErzfveyn8BmPDMzLuNPlY92RX/JQx8tIoV44=
X-Received: by 2002:a9d:992:: with SMTP id q18mr7027549otd.351.1539014799039;  Mon, 08 Oct 2018 09:06:39 -0700 (PDT)
MIME-Version: 1.0
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se>
In-Reply-To: <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 8 Oct 2018 09:06:13 -0700
Message-ID: <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com>
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>
Cc: nordmark@acm.org,  Applications and Real-Time Area Discussion <art@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066a5aa0577b9cebf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/IdqkOp0AC9IJE-dTFhvqsb5dtg0>
Subject: Re: [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 16:06:43 -0000

--00000000000066a5aa0577b9cebf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Modulo Erik's comments, I think this is ready for publication.  The
instructions to IANA are clear and the rationale behind those instructions
is laid out.

I think we could ask for AD-sponsorship for this, but I also believe that
the instructions could go to IANA now; at the very least, we could ask them
to review.

Ted

On Sat, Oct 6, 2018 at 10:30 PM Patrik F=C3=A4ltstr=C3=B6m <paf@netnod.se> =
wrote:

> Thanks, fixed for -04.
>
>    paf
>
> On 3 Oct 2018, at 3:35, Erik Nordmark wrote:
>
> > Patrik,
> >
> > I've reviewed the document and I have a suggestion to make it a bit mor=
e
> clear. Currently one has to read much of the document including the IANA
> considerations section to be certain that the document makes the statemen=
t
> to move forward to Unicode 11.
> >
> > I think it would be more clear if that was captured in the abstract. Fo=
r
> instance, it could say something like this:
> > CURRENT:
> >    This document describes changes between Unicode 6.3.0 and Unicode
> >    11.0.0 in the context of IDNA2008.  It further suggests for the IETF
> >    a path forward regarding ensuring IDNA2008 follows the evolution of
> >    the Unicode Standard.
> >
> >    In a few cases changes have been made in the Unicode Standard relate=
d
> >    to the algorithm IDNA2008 specifies.  IDNA2008 do give the ability t=
o
> >    add exceptions for backward compatibility to the algorithm but the
> >    conclusions provided in this document suggests no such changes.
> >
> > ADD:
> >     Thus the document requests that IANA update the tables to Unicode 1=
1.
> >
> >     In addition, all registries should continue the practice of
> calculating a repertoire using conservatism and inclusion principles.
> >
> > [Assuming that is current recommended practice]
> >
> > This wasn't clear to me in the introduction; had to read it several
> times:
> >    When the Unicode Standard is updated code points are assigned that
> >    earlier was not and property values changes for already assigned cod=
e
> >    points.
> > I would be more clear to say something like:
> >    When the Unicode Standard is updated new code points are assigned
> >    and property values might be changed for already assigned code
> >    points.
> >
> > Nits and typos:
> >
> > Introduction section says:
> >    Changing properties to already assigned code points ...
> > I think "for" is better than "to" here.
> >
> > Conclusion section:
> > s/repertoir/repertoire/
> > s/inclusive/inclusion/
> >
> > Thanks,
> >    Erik
>
>   Patrik F=C3=A4ltstr=C3=B6m
>   Technical Director
>   Netnod
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

--00000000000066a5aa0577b9cebf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Modulo Erik&#39;s comments, I think this is ready for=
 publication.=C2=A0 The instructions to IANA are clear and the rationale be=
hind those instructions is laid out.</div><div><br></div><div>I think we co=
uld ask for AD-sponsorship for this, but I also believe that the instructio=
ns could go to IANA now; at the very least, we could ask them to review.<br=
></div><div><br></div><div>Ted<br></div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr">On Sat, Oct 6, 2018 at 10:30 PM Patrik F=C3=A4ltstr=C3=
=B6m &lt;<a href=3D"mailto:paf@netnod.se">paf@netnod.se</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Thanks, fixed for -04.<br>
<br>
=C2=A0 =C2=A0paf<br>
<br>
On 3 Oct 2018, at 3:35, Erik Nordmark wrote:<br>
<br>
&gt; Patrik,<br>
&gt;<br>
&gt; I&#39;ve reviewed the document and I have a suggestion to make it a bi=
t more clear. Currently one has to read much of the document including the =
IANA considerations section to be certain that the document makes the state=
ment to move forward to Unicode 11.<br>
&gt;<br>
&gt; I think it would be more clear if that was captured in the abstract. F=
or instance, it could say something like this:<br>
&gt; CURRENT:<br>
&gt;=C2=A0 =C2=A0 This document describes changes between Unicode 6.3.0 and=
 Unicode<br>
&gt;=C2=A0 =C2=A0 11.0.0 in the context of IDNA2008.=C2=A0 It further sugge=
sts for the IETF<br>
&gt;=C2=A0 =C2=A0 a path forward regarding ensuring IDNA2008 follows the ev=
olution of<br>
&gt;=C2=A0 =C2=A0 the Unicode Standard.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 In a few cases changes have been made in the Unicode Stan=
dard related<br>
&gt;=C2=A0 =C2=A0 to the algorithm IDNA2008 specifies.=C2=A0 IDNA2008 do gi=
ve the ability to<br>
&gt;=C2=A0 =C2=A0 add exceptions for backward compatibility to the algorith=
m but the<br>
&gt;=C2=A0 =C2=A0 conclusions provided in this document suggests no such ch=
anges.<br>
&gt;<br>
&gt; ADD:<br>
&gt;=C2=A0 =C2=A0 =C2=A0Thus the document requests that IANA update the tab=
les to Unicode 11.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0In addition, all registries should continue the pra=
ctice of calculating a repertoire using conservatism and inclusion principl=
es.<br>
&gt;<br>
&gt; [Assuming that is current recommended practice]<br>
&gt;<br>
&gt; This wasn&#39;t clear to me in the introduction; had to read it severa=
l times:<br>
&gt;=C2=A0 =C2=A0 When the Unicode Standard is updated code points are assi=
gned that<br>
&gt;=C2=A0 =C2=A0 earlier was not and property values changes for already a=
ssigned code<br>
&gt;=C2=A0 =C2=A0 points.<br>
&gt; I would be more clear to say something like:<br>
&gt;=C2=A0 =C2=A0 When the Unicode Standard is updated new code points are =
assigned<br>
&gt;=C2=A0 =C2=A0 and property values might be changed for already assigned=
 code<br>
&gt;=C2=A0 =C2=A0 points.<br>
&gt;<br>
&gt; Nits and typos:<br>
&gt;<br>
&gt; Introduction section says:<br>
&gt;=C2=A0 =C2=A0 Changing properties to already assigned code points ...<b=
r>
&gt; I think &quot;for&quot; is better than &quot;to&quot; here.<br>
&gt;<br>
&gt; Conclusion section:<br>
&gt; s/repertoir/repertoire/<br>
&gt; s/inclusive/inclusion/<br>
&gt;<br>
&gt; Thanks,<br>
&gt;=C2=A0 =C2=A0 Erik<br>
<br>
=C2=A0 Patrik F=C3=A4ltstr=C3=B6m<br>
=C2=A0 Technical Director<br>
=C2=A0 Netnod<br>
_______________________________________________<br>
art mailing list<br>
<a href=3D"mailto:art@ietf.org" target=3D"_blank">art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/art</a><br>
</blockquote></div>

--00000000000066a5aa0577b9cebf--


From nobody Mon Oct  8 12:58:27 2018
Return-Path: <john-ietf@jck.com>
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 A2804130F5E; Mon,  8 Oct 2018 12:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 exOnqySDKkQQ; Mon,  8 Oct 2018 12:58:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27697130F67; Mon,  8 Oct 2018 12:58:24 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1g9bfY-000KLe-3s; Mon, 08 Oct 2018 15:58:20 -0400
Date: Mon, 08 Oct 2018 15:58:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@netnod.se>
cc: nordmark@acm.org, Applications and Real-Time Area Discussion <art@ietf.org>, idna-update@ietf.org
Message-ID: <B0BA40527CB85EC369DD812D@PSB>
In-Reply-To: <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/b73TKpKzj1BN99yi-RXCjs47_dY>
Subject: Re: [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 19:58:26 -0000

--On Monday, October 8, 2018 09:06 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:

> Modulo Erik's comments, I think this is ready for publication.
> The instructions to IANA are clear and the rationale behind
> those instructions is laid out.
> 
> I think we could ask for AD-sponsorship for this, but I also
> believe that the instructions could go to IANA now; at the
> very least, we could ask them to review.

Ted,

I'm sorry, but I disagree.  Patrik has, as far as I can tell,
done the job that the IAB asked him to do in his liaison
capacity to Unicode, but that job involves a number of
assumptions about how to proceed that interact with i18n
documents that the IETF has been unable to process.  If we
follow the precedent of RFC 6452, this document should be
processed as standards track even if it changes nothing.  It
would be wildly inappropriate for it to constrain the
conclusions the IETF could reach about those other documents.

My understanding coming out of the BOF at IETF 102 was that the
ART ADs were going to establish a directorate to determine how
i18n documents were to be handled and to start processing those
documents.  This document would make an entirely reasonable
addition to that directorate's queue.   However, if an progress
has been made on creating that directorate, much less having it
convene and discuss processing of documents, I seem to have
missed the announcement(s).

best,
   john


From nobody Mon Oct  8 13:27:36 2018
Return-Path: <ted.ietf@gmail.com>
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 9008313101B; Mon,  8 Oct 2018 13:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 CnNPgoeofU13; Mon,  8 Oct 2018 13:27:25 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 B61A1131007; Mon,  8 Oct 2018 13:27:25 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id u22so21202028ota.12; Mon, 08 Oct 2018 13:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RDoSaEtt0JsbKNcw4FFeA2kyK6tM06sgH1uhHcwdiiM=; b=gJ+BC9D/AYK4IFQZcZa28B8MAjamx6aIaVAu0cQ86sW9n9F+mua/txct0BtJDi1iPh 0xFVMGWuZyTwzzduz6Vb6TP9j4IksKfVNClFjdWMzHoQgSKFY/vIq/huJT6bAJZLwSd0 PR8Rd2205jatyBNRnuP+vKFaaDZ2YBuaWYQzehapMcjKokOvPF5lA5o85AyrFy+Afww7 rveWVE80QzIgbx9UC8vKpkd59BgLGAI9hbkfEWkih3+kUaHPgw5ZgNyr1s4/ltHwBLkr YVN8HoG+H+YW/bMDLBrxdw6Z5Nna6ePa92NhTWtb+kUCnamP8nem5dZOIpmoXfHyoENu uzMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RDoSaEtt0JsbKNcw4FFeA2kyK6tM06sgH1uhHcwdiiM=; b=eSK/n9DJuR7XwVZAAhd1oUMdEH+y3u4yZKT/9CLTe+SCw62oC6JjOXXOfIb8Ro7ZHc s+Zoj8A8kpf0+XNAt3lyKTmgFsyHI1kGeVLtVuY+Hp7EEwRf/eZ0sxhsICzLs4QhaCcn MUDYcf0MUKNcHg8kYZMZhjLXhT+pLfhRq/aVIXiAM7Q3VrQN9p10RvtL9Qqz5eswwvrG ZvRUd8QWkGZN5r/iVLlFA2yOpTuokXllU6p9GscNWiqoENWq1ktnkWE+TPD/cp5xhcpC YkiqduPQAEZ/KJiOI3Cn1DQGCgL7KQbDidvbRw+wPan94yAZevN0/GY+qPPd/gWXZfMu uChw==
X-Gm-Message-State: ABuFfohGz9G2aXYkqWtkxW1qoZr30mSSk1POaLrQvkmD3zJnHbdFxSim Gamm7pczukErLSIrtun57Ykn5sRFWekAqpjDgxQ=
X-Google-Smtp-Source: ACcGV60eOdc64H+y81TnOrtx14z0dkRbSNZldZKzGrOKcKIzRwCJI1soEHygT82GIrcbmFtmr8fRTk8lxkAHVcox1Dw=
X-Received: by 2002:a9d:992:: with SMTP id q18mr7624777otd.351.1539030444793;  Mon, 08 Oct 2018 13:27:24 -0700 (PDT)
MIME-Version: 1.0
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB>
In-Reply-To: <B0BA40527CB85EC369DD812D@PSB>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 8 Oct 2018 13:26:58 -0700
Message-ID: <CA+9kkMC836d20ZCHETUJ_njYCO6b=V72YYpVufquXkH4F23gsA@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>, nordmark@acm.org,  Applications and Real-Time Area Discussion <art@ietf.org>, idna-update@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f5e5300577bd7237"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/SHOAYfQPeGyV_ADK071GW8ksYos>
Subject: Re: [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 20:27:28 -0000

--000000000000f5e5300577bd7237
Content-Type: text/plain; charset="UTF-8"

Howdy,

On Mon, Oct 8, 2018 at 12:58 PM John C Klensin <john-ietf@jck.com> wrote:

> --On Monday, October 8, 2018 09:06 -0700 Ted Hardie
> <ted.ietf@gmail.com> wrote:
>
> > Modulo Erik's comments, I think this is ready for publication.
> > The instructions to IANA are clear and the rationale behind
> > those instructions is laid out.
> >
> > I think we could ask for AD-sponsorship for this, but I also
> > believe that the instructions could go to IANA now; at the
> > very least, we could ask them to review.
>
> Ted,
>
> I'm sorry, but I disagree.  Patrik has, as far as I can tell,
> done the job that the IAB asked him to do in his liaison
> capacity to Unicode, but that job involves a number of
> assumptions about how to proceed that interact with i18n
> documents that the IETF has been unable to process.  If we
> follow the precedent of RFC 6452, this document should be
> processed as standards track even if it changes nothing.  It
> would be wildly inappropriate for it to constrain the
> conclusions the IETF could reach about those other documents.
>
> I infer that you are disagreeing with my suggestion that this get
AD-sponsorship, not with my suggestion that it get at minimum IANA review.
If you disagree with that as well, perhaps you'd care to say why.  My
personal take is that it is useful to get confirmation from IANA that the
instructions are clear as soon as possible.

My understanding coming out of the BOF at IETF 102 was that the
> ART ADs were going to establish a directorate to determine how
> i18n documents were to be handled and to start processing those
> documents.  This document would make an entirely reasonable
> addition to that directorate's queue.   However, if an progress
> has been made on creating that directorate, much less having it
> convene and discuss processing of documents, I seem to have
> missed the announcement(s).
>
> As you know doubt recall from RFC 2418, the purpose of a directorate is to
advise an Area Director or a set of Area Directors:

In many areas, the Area Directors have formed an advisory group or
> directorate. These comprise experienced members of the IETF and the
> technical community represented by the area. The specific name and the
> details of the role for each group differ from area to area, but the
> primary intent is that these groups assist the Area Director(s), e.g., with
> the review of specifications produced in the area.
>

I certainly agree that the presence of a fully functional i18n directorate
would be a boon, but I believe that any AD considering sponsorship of this
would do so by consulting, informally, many of the same folks who might
serve on that directorate were it in place.  So I do not, personally, see
any reason to gate on the formality when the ADs can get the same advice
for this one without it.

regards,

Ted Hardie


> best,
>    john
>
>

--000000000000f5e5300577bd7237
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Howdy,<br><div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr">On Mon, Oct 8, 2018 at 12:58 PM John C Klensin &lt;<a href=3D"mailto:j=
ohn-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">--On Monday, October 8, 2018 09:06 -0700 Ted Hardie<br>
&lt;<a href=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.=
com</a>&gt; wrote:<br>
<br>
&gt; Modulo Erik&#39;s comments, I think this is ready for publication.<br>
&gt; The instructions to IANA are clear and the rationale behind<br>
&gt; those instructions is laid out.<br>
&gt; <br>
&gt; I think we could ask for AD-sponsorship for this, but I also<br>
&gt; believe that the instructions could go to IANA now; at the<br>
&gt; very least, we could ask them to review.<br>
<br>
Ted,<br>
<br>
I&#39;m sorry, but I disagree.=C2=A0 Patrik has, as far as I can tell,<br>
done the job that the IAB asked him to do in his liaison<br>
capacity to Unicode, but that job involves a number of<br>
assumptions about how to proceed that interact with i18n<br>
documents that the IETF has been unable to process.=C2=A0 If we<br>
follow the precedent of RFC 6452, this document should be<br>
processed as standards track even if it changes nothing.=C2=A0 It<br>
would be wildly inappropriate for it to constrain the<br>
conclusions the IETF could reach about those other documents.<br>
<br></blockquote><div>I infer that you are disagreeing with my suggestion t=
hat this get AD-sponsorship, not with my suggestion that it get at minimum =
IANA review.=C2=A0 If you disagree with that as well, perhaps you&#39;d car=
e to say why.=C2=A0 My personal take is that it is useful to get confirmati=
on from IANA that the instructions are clear as soon as possible.<br></div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
My understanding coming out of the BOF at IETF 102 was that the<br>
ART ADs were going to establish a directorate to determine how<br>
i18n documents were to be handled and to start processing those<br>
documents.=C2=A0 This document would make an entirely reasonable<br>
addition to that directorate&#39;s queue.=C2=A0 =C2=A0However, if an progre=
ss<br>
has been made on creating that directorate, much less having it<br>
convene and discuss processing of documents, I seem to have<br>
missed the announcement(s).<br>
<br></blockquote><div>As you know doubt recall from RFC 2418, the purpose o=
f a directorate is to advise an Area Director or a set of Area Directors:</=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I=
n many areas, the Area Directors have formed an advisory group or=20
directorate. These comprise experienced members of the IETF and the=20
technical community represented by the area. The specific name and the=20
details of the role for each group differ from area to area, but the=20
primary intent is that these groups assist the Area Director(s), e.g.,=20
with the review of specifications produced in the area.</div></blockquote><=
div><br></div><div>I certainly agree that the presence of a fully functiona=
l i18n directorate would be a boon, but I believe that any AD considering s=
ponsorship of this would do so by consulting, informally, many of the same =
folks who might serve on that directorate were it in place.=C2=A0 So I do n=
ot, personally, see any reason to gate on the formality when the ADs can ge=
t the same advice for this one without it.<br></div><div><br></div><div>reg=
ards,</div><div><br></div><div>Ted Hardie<br></div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
best,<br>
=C2=A0 =C2=A0john<br>
<br>
</blockquote></div></div></div>

--000000000000f5e5300577bd7237--


From nobody Mon Oct  8 13:34:32 2018
Return-Path: <asmusf@ix.netcom.com>
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 CCB5C130F67; Mon,  8 Oct 2018 13:34:16 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.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 kGUo4Ihgt7hP; Mon,  8 Oct 2018 13:34:14 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) (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 047CE130FED; Mon,  8 Oct 2018 13:34:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1539030850; bh=N4cUlQGHxmJPfIh0xttvHPrK3sTTNx5F/fWw tWcGjSs=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=ZAHmppd0nlO1rTEKFrGD3bFp3oCc3DTJE 0c/dsqG1zYF/jU84N07SMp8y+v/vD2wUfKzotIledzl4GOJ7LLwDq1Q1KElGaiiMO92 xOl3unAq7mhNEE7SMoMA0NuA166UqngwSF7EtRPgddSmO/PhYUIeKwrwDAMXfzrpgAS 1g+IUz4MNG65CJZoOQQ1TQ/owqE3jRF/NWMB/Wz0Xwg9Uf3w+s9Ijf1Z3zUxaB5Pikp wtNA4jLUpRlDBBYgrrpfDSf/yzAxqOpRvfZc+XDBBGKgRpPlxgCTUomvshgkAQx7Ktv 3tFUHNm7s+cECDOBayIz72RcR1cZOllNX0QA7kEPg==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=N142wsRx0uJFHAM0fg6URalXjz8EJUPZeeT8RUPvz868HRdPbCU1lmRmhQC09DLImqh0lSpRG2q/coMwN4GRgWq3I7pKHErjBBWUW12jQz7yqCpclyAmqp97iPplUpfLB4nbO2WBVU2JUKiidxhzSDNfADyrTa5us6BNHKId9FCIa9NcLOF3lrYmPKLEAq3aDj33Ui20jNKKLpq4qWyYJ2X927xmVeChbZrGInps1WFyO5YOJhvY8ewIUOLla4sW6nUCixGQdXbrsoKqk2slI0lyk4vpDRpyGqnqGIOJ9SmNAbBYbff2L41T89sN5tWgDr9fGRiorvhvyCkXFYIZYA==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [174.21.170.119] (helo=[192.168.1.108]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <asmusf@ix.netcom.com>) id 1g9cE7-0005GH-N6; Mon, 08 Oct 2018 16:34:03 -0400
To: John C Klensin <john-ietf@jck.com>, Ted Hardie <ted.ietf@gmail.com>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>
Cc: nordmark@acm.org, idna-update@ietf.org, Applications and Real-Time Area Discussion <art@ietf.org>, i18nrp@ietf.org
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com>
Date: Mon, 8 Oct 2018 13:34:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <B0BA40527CB85EC369DD812D@PSB>
Content-Type: multipart/alternative; boundary="------------FDABF4CDD5D941C29B2723A1"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b7eec10b52094b3e26484a1db409fbf83e1308fa4a16f794350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 174.21.170.119
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/xylj_HE0zsvkiW0qYm9O8bimE1g>
Subject: Re: [art] [Idna-update]  Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 20:34:17 -0000

This is a multi-part message in MIME format.
--------------FDABF4CDD5D941C29B2723A1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 10/8/2018 12:58 PM, John C Klensin wrote:
> --On Monday, October 8, 2018 09:06 -0700 Ted Hardie
> <ted.ietf@gmail.com> wrote:
>
>> Modulo Erik's comments, I think this is ready for publication.
>> The instructions to IANA are clear and the rationale behind
>> those instructions is laid out.
>>
>> I think we could ask for AD-sponsorship for this, but I also
>> believe that the instructions could go to IANA now; at the
>> very least, we could ask them to review.
> Ted,
>
> I'm sorry, but I disagree.  Patrik has, as far as I can tell,
> done the job that the IAB asked him to do in his liaison
> capacity to Unicode,

I thought this draft was in Patrik's role as the designated expert for 
the IANA registry.

> but that job involves a number of
> assumptions about how to proceed that interact with i18n
> documents that the IETF has been unable to process.  If we
> follow the precedent of RFC 6452, this document should be
> processed as standards track even if it changes nothing.

The relevant difference is that RFC 6452 contained this section:

-------------------

IETF Consensus

    No change to RFC 5892 is needed based on the changes made in
    Unicode 6.0.

    This consensus does not imply that no changes will be made to
    RFC 5892 for all future updates of The Unicode Standard.

    This RFC has been produced because 6.0 is the first version of
    Unicode to be released since IDNA2008 was published.
--------------------

I see no particular reason why such a section couldn't be added
to Patrik's draft, allowing it to be processed like 6452 if that is
felt to be more appropriate.

>   It
> would be wildly inappropriate for it to constrain the
> conclusions the IETF could reach about those other documents.

I don't see how this would constrain IETF conclusions about other documents,
or even RFC 5892 itself (other than that the consensus is to not add 
exceptions).

There are changes that may be motivated by the general aspects of the 
interaction
between Unicode and IDNA, but the kind of language as quoted above would not
rule those out.

You would need to make a more concrete claim how processing this RFC
interferes with the work of IETF.

> My understanding coming out of the BOF at IETF 102 was that the
> ART ADs were going to establish a directorate to determine how
> i18n documents were to be handled and to start processing those
> documents.  This document would make an entirely reasonable
> addition to that directorate's queue.   However, if an progress
> has been made on creating that directorate, much less having it
> convene and discuss processing of documents, I seem to have
> missed the announcement(s).

I don't necessarily see the plan for a new directorate as suspending IETFs
ability to process certain RFCs indefinitely. The goal was to make it 
possible
to process more of them and more consistently, not to provide an additional
hurdle.

(Taken to its logical conclusion, such restriction would have to apply 
to all
RFCs that such a directorate might be giving i18n related input on. I don't
see that happening, so I don't see why this draft needs to be singled out).

That said, I would also like to learn what progress is being made.

At some point, people were looking for volunteers, but at that point the
parameters were sufficiently vague for anyone to know what they would
be committing to.

A./




--------------FDABF4CDD5D941C29B2723A1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 10/8/2018 12:58 PM, John C Klensin
      wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:B0BA40527CB85EC369DD812D@PSB">
      <pre class="moz-quote-pre" wrap="">--On Monday, October 8, 2018 09:06 -0700 Ted Hardie
<a class="moz-txt-link-rfc2396E" href="mailto:ted.ietf@gmail.com">&lt;ted.ietf@gmail.com&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">Modulo Erik's comments, I think this is ready for publication.
The instructions to IANA are clear and the rationale behind
those instructions is laid out.

I think we could ask for AD-sponsorship for this, but I also
believe that the instructions could go to IANA now; at the
very least, we could ask them to review.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">Ted,

I'm sorry, but I disagree.  Patrik has, as far as I can tell,
done the job that the IAB asked him to do in his liaison
capacity to Unicode, </pre>
    </blockquote>
    <p>I thought this draft was in Patrik's role as the designated
      expert for the IANA registry. <br>
    </p>
    <blockquote type="cite" cite="mid:B0BA40527CB85EC369DD812D@PSB">
      <pre class="moz-quote-pre" wrap="">but that job involves a number of
assumptions about how to proceed that interact with i18n
documents that the IETF has been unable to process.  If we
follow the precedent of RFC 6452, this document should be
processed as standards track even if it changes nothing. </pre>
    </blockquote>
    <p>The relevant difference is that RFC 6452 contained this section:</p>
    <p>-------------------</p>
    <p>IETF Consensus<br>
      <br>
         No change to RFC 5892 is needed based on the changes made in<br>
         Unicode 6.0.<br>
      <br>
         This consensus does not imply that no changes will be made to<br>
         RFC 5892 for all future updates of The Unicode Standard.<br>
      <br>
         This RFC has been produced because 6.0 is the first version of<br>
         Unicode to be released since IDNA2008 was published.<br>
      --------------------<br>
    </p>
    <p>I see no particular reason why such a section couldn't be added<br>
      to Patrik's draft, allowing it to be processed like 6452 if that
      is<br>
      felt to be more appropriate.</p>
    <blockquote type="cite" cite="mid:B0BA40527CB85EC369DD812D@PSB">
      <pre class="moz-quote-pre" wrap=""> It
would be wildly inappropriate for it to constrain the
conclusions the IETF could reach about those other documents.</pre>
    </blockquote>
    <p>I don't see how this would constrain IETF conclusions about other
      documents,<br>
      or even RFC 5892 itself (other than that the consensus is to not
      add exceptions).</p>
    <p>There are changes that may be motivated by the general aspects of
      the interaction<br>
      between Unicode and IDNA, but the kind of language as quoted above
      would not<br>
      rule those out.<br>
    </p>
    <p>You would need to make a more concrete claim how processing this
      RFC<br>
      interferes with the work of IETF.
    </p>
    <blockquote type="cite" cite="mid:B0BA40527CB85EC369DD812D@PSB">
      <pre class="moz-quote-pre" wrap="">My understanding coming out of the BOF at IETF 102 was that the
ART ADs were going to establish a directorate to determine how
i18n documents were to be handled and to start processing those
documents.  This document would make an entirely reasonable
addition to that directorate's queue.   However, if an progress
has been made on creating that directorate, much less having it
convene and discuss processing of documents, I seem to have
missed the announcement(s).</pre>
    </blockquote>
    <p>I don't necessarily see the plan for a new directorate as
      suspending IETFs<br>
      ability to process certain RFCs indefinitely. The goal was to make
      it possible<br>
      to process more of them and more consistently, not to provide an
      additional<br>
      hurdle.</p>
    <p>(Taken to its logical conclusion, such restriction would have to
      apply to all<br>
      RFCs that such a directorate might be giving i18n related input
      on. I don't <br>
      see that happening, so I don't see why this draft needs to be
      singled out). <br>
    </p>
    <p>That said, I would also like to learn what progress is being
      made.</p>
    <p>At some point, people were looking for volunteers, but at that
      point the<br>
      parameters were sufficiently vague for anyone to know what they
      would<br>
      be committing to.</p>
    <p>A./<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------FDABF4CDD5D941C29B2723A1--


From nobody Mon Oct  8 13:35:51 2018
Return-Path: <stpeter@mozilla.com>
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 9AD35130FCF for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 13:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 US4bZBu8CfzA for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 13:35:47 -0700 (PDT)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 AA210130F67 for <art@ietf.org>; Mon,  8 Oct 2018 13:35:47 -0700 (PDT)
Received: by mail-it1-x12b.google.com with SMTP id e74-v6so13864577ita.2 for <art@ietf.org>; Mon, 08 Oct 2018 13:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9fySLohTB8oqHGYcT7Op/UCS2v7cZWam++FvBKwBXLY=; b=BUhXvKoznESNCAHcS2N9RPcoBz/vlBjEHZLvewJxl39aS1SZEK5mEb9RJ55cFniT39 fYjKrVYV9vRedyYgOXKakxMvwEM1forieh1RiERwWpvpE0Xxy+k/BoTZS3MuoM7Keq2/ AmeUhxnOtkMCujaE5MjRHfYSVZ1ovHWT0BHTM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=9fySLohTB8oqHGYcT7Op/UCS2v7cZWam++FvBKwBXLY=; b=r5irEwfgBGmesFcWZGw7kSGyTC02u8Mn1sxWr7IT4OL9rcBMc27kNpEtNDiv3uXS+a EsdSOX9Xtn68kX+MeSb6ZWV/Pm25usdf9GfBa9gxLFCcRK2WP6kJttUkvtIKA4pF83uo jM/WIrD88nO2s41932Bmx8+KW8uglZaZ1TIpePa8Q6ZpDtmGSXDbwuO/6nX7L7VjrIc6 waXKlnr561JA7rF/qhaFbNMi68jcPCH0WpGK+2JR5XgBt/XOa3KiWIAN5CNNILoKTt/X Y32LDuUu0Ho6NWj0C6WnTVKPolOFmifa2UsBXHJN3AqjAJJW2F8Gbp6LBPo3Fp22pcC/ L3Dg==
X-Gm-Message-State: ABuFfogJ+vit21vmxBnTMJS6EnMdRcVsYBdVyntZ6EAbodck5HyqG81S KYV3yFOb4sL+locQBdllqNoJRQ==
X-Google-Smtp-Source: ACcGV60pBYjATwI3iya1b1MBK9jIJAc1Wqth1JqJRk2seONl+soQOpDkbPiJFjUGhz3YdxHEqt+mQw==
X-Received: by 2002:a02:91c9:: with SMTP id s9-v6mr21011511jag.104.1539030946936;  Mon, 08 Oct 2018 13:35:46 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id u132-v6sm3922121ita.9.2018.10.08.13.35.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Oct 2018 13:35:46 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Ted Hardie <ted.ietf@gmail.com>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>
Cc: nordmark@acm.org, Applications and Real-Time Area Discussion <art@ietf.org>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <cf9531be-f33f-084e-982e-3f9f578842b5@mozilla.com>
Date: Mon, 8 Oct 2018 14:35:45 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <B0BA40527CB85EC369DD812D@PSB>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/6v73lLo9yyfCjI9-_hes9AlKON0>
Subject: [art] i18n directorate (was: Re: Comments on draft-faltstrom-unicode11-02)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 20:35:50 -0000

On 10/8/18 1:58 PM, John C Klensin wrote:

> My understanding coming out of the BOF at IETF 102 was that the
> ART ADs were going to establish a directorate to determine how
> i18n documents were to be handled and to start processing those
> documents.  This document would make an entirely reasonable
> addition to that directorate's queue.   However, if an progress
> has been made on creating that directorate, much less having it
> convene and discuss processing of documents, I seem to have
> missed the announcement(s).

Depending on you look at it, either I or the ADs have dropped the ball.
The requirements for creating the directorate were unclear to me, esp.
with regard to the level of detail needed in plans for (a) recruiting
and training of directorate members and (b) day-to-day operations. I
asked the ADs for clarification, but I could have also proposed a plan
to see if it was detailed enough for them. I'll reprioritize to get this
done more quickly.

Peter


From nobody Mon Oct  8 16:40:48 2018
Return-Path: <James.H.Manger@team.telstra.com>
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 E460B13104E for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 16:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=teamtelstra.onmicrosoft.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 cw7Fk9_Rvhxp for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 16:40:41 -0700 (PDT)
Received: from ipxdvo.tcif.telstra.com.au (ipxdvo.tcif.telstra.com.au [203.35.135.212]) (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 06CC6130F63 for <art@ietf.org>; Mon,  8 Oct 2018 16:40:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.54,358,1534773600";  d="scan'208,217";a="116619193"
X-Amp-Result: SKIPPED(no attachment in message)
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipodvi.tcif.telstra.com.au with ESMTP; 09 Oct 2018 10:28:59 +1100
Received: from wsmsg3704.srv.dir.telstra.com ([172.49.40.197]) by ipcbvi.tcif.telstra.com.au with ESMTP; 09 Oct 2018 10:28:57 +1100
Received: from wsapp5863.srv.dir.telstra.com (10.75.131.32) by wsmsg3704.srv.dir.telstra.com (172.49.40.197) with Microsoft SMTP Server (TLS) id 8.3.485.1; Tue, 9 Oct 2018 10:28:57 +1100
Received: from wsapp5585.srv.dir.telstra.com (10.75.3.67) by wsapp5863.srv.dir.telstra.com (10.75.131.32) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 9 Oct 2018 10:28:45 +1100
Received: from AUS01-ME1-obe.outbound.protection.outlook.com (10.172.101.126) by wsapp5585.srv.dir.telstra.com (10.75.3.67) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 9 Oct 2018 10:28:55 +1100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teamtelstra.onmicrosoft.com; s=selector1-team-telstra-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YWnOrVawBLc/0as9IO/j4U0P0xTEIWVQCIylARVIuyE=; b=rUCU90hw0Bb+cvRZiIsJSIS/7XWxc+m+/fVqisTTdUlcwX/Lj1Xr6rYvKzX3jOSd9bmU4VG00U3J92Et51gPNfEHt88emUDiULXtU/0mbhduanvdCjhvRlzc35z3249Ew16h/uybcSYHc3BdUoHg0aq5Dlkfgeiuc4EZ1Zvyl/Y=
Received: from MEAPR01MB3542.ausprd01.prod.outlook.com (52.134.216.9) by MEAPR01MB3013.ausprd01.prod.outlook.com (52.134.198.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.26; Mon, 8 Oct 2018 23:28:55 +0000
Received: from MEAPR01MB3542.ausprd01.prod.outlook.com ([fe80::4031:99ca:970e:721e]) by MEAPR01MB3542.ausprd01.prod.outlook.com ([fe80::4031:99ca:970e:721e%2]) with mapi id 15.20.1207.024; Mon, 8 Oct 2018 23:28:55 +0000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Steven Liekens <steven.liekens@gmail.com>
CC: "art@ietf.org" <art@ietf.org>
Thread-Topic: [art] [Technical Errata Reported] RFC7807 (5515)
Thread-Index: AQHUXLQPibXDLK9z+k6TUqX2ITJ2vaURVFkAgANflVqAAAAvkIAAQJMAgAEBPXA=
Date: Mon, 8 Oct 2018 23:28:55 +0000
Message-ID: <MEAPR01MB35428C99CD504725D428BB6BE5E60@MEAPR01MB3542.ausprd01.prod.outlook.com>
References: <20181005140137.46DCAB818E3@rfc-editor.org> <BACDF95B-F2F6-49B6-A855-BE826E288C6F@mnot.net> <CABQ2G6TfdOLwyiY-zqMMFhePAHJSRC=dxiCigQkBYGSYi53PUQ@mail.gmail.com> <206FAAB7-F9C9-44AF-8FA5-774DC2ACF9C6@mnot.net> <MEAPR01MB3542C171203B076F71CB8013E5E60@MEAPR01MB3542.ausprd01.prod.outlook.com> <CABQ2G6R07cxg1DBd+Jqc3R5L4R5ovNxuxACqPH_Z7kCnyKYaHQ@mail.gmail.com>
In-Reply-To: <CABQ2G6R07cxg1DBd+Jqc3R5L4R5ovNxuxACqPH_Z7kCnyKYaHQ@mail.gmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 10.0.500.19
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=James.H.Manger@team.telstra.com; 
x-originating-ip: [203.41.142.244]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MEAPR01MB3013; 6:Ih5xCbAY7LyqU8k3XC25qHGjFNP4SZEfpMIMoIKSWG2DZF6wnemZiieLzDZ35OGpN5d4pU9ESPJG5zhdFSVR3B5qToqMukcw5g1W3x8BMN8QLuDw3Oyn+zE0Hij86VCboWD4DJR+jaJPY5eJ4lD43Qz6HC8cQ78hHVP2Hyi5a2Vb6zaTmGNTDjrwR3UT/fROMB1Jy9cZtt2wARuhs4FCMuoXzXzwIzFg1CxE5Km9qDSVMm68+EwICqv9ATNreC3RVO28zN3foaZVbZf3cJ7hGGSC0QZ8oz2hBbF5R6/8egRzK8EODtzE3C0Fz+KLqJZzBykDnTHclpTZS877kTPyfo4DEVBUpM0ILEIuXbZm1ymmYKueie4KK2Iwp1Fom1Wi3SyGKj+THdxcgootSSg4NpvYvpdxWoQDX3rVsHBjXOy1CVWbAkoS/m6OGyzdQxwo1kZZGdowCjcDJEsg8E98UQ==; 5:Mn3TIGwacuCSWphImwSdxrXgAjdCxbnEp/GfJPHZdpgYjmuBDVMd9v8uAPyEa1OgI+btowuUKVu6R+0KP4xQtleJS+rHzTyLbUu0YOH7iMBT5b0JmZwJGBSAsET2qdkqQi/F2LyINCy1cJABSi4mfGw7TgZanTH2NDkCXBGNx+w=; 7:YWaVH7l5vuAa1XbOqeNJ4TU6hZSm7wXYNLY13v/B9ge+S854lMjU9JzMkHvWgiFgslMwRpfwfbqr+Jz52UQeYtDP5TunSnld6TyOkxZizfgvcKhMfOh1gse9Pj7PUJbvd2ORvMI1cux+JQEmyFHbYeEfF8NIJIho6ugxSXvfOaHEPsSyyyGs7UYF+sN4P+g7HvhQ7BidTuxNUKPskwNNqyYFjJMZsmLbWsumi6A6nmzoDOTs8wNHm7f5KuVBh4HY
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4f26cce7-3fb7-464d-76cd-08d62d75d097
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:MEAPR01MB3013; 
x-ms-traffictypediagnostic: MEAPR01MB3013:
x-microsoft-antispam-prvs: <MEAPR01MB3013049F421235DA48D247D9E5E60@MEAPR01MB3013.ausprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(272811157607776)(67441168502697)(278428928389397)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231355)(944501410)(4982022)(52105095)(10201501046)(93006095)(93001095)(3002001)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123558120)(20161123564045)(201708071742011)(7699051)(76991055); SRVR:MEAPR01MB3013; BCL:0; PCL:0; RULEID:; SRVR:MEAPR01MB3013; 
x-forefront-prvs: 081904387B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(396003)(376002)(136003)(39860400002)(13464003)(199004)(189003)(8936002)(93886005)(14444005)(256004)(5660300001)(81166006)(81156014)(229853002)(486006)(6246003)(446003)(39060400002)(476003)(8676002)(99286004)(2900100001)(26005)(7696005)(102836004)(72206003)(11346002)(966005)(186003)(76176011)(7736002)(6306002)(71200400001)(25786009)(55016002)(5003630100001)(478600001)(316002)(9686003)(6506007)(53546011)(236005)(86362001)(2906002)(6916009)(4326008)(106356001)(71190400001)(790700001)(3846002)(6116002)(74316002)(5250100002)(6436002)(68736007)(66066001)(14454004)(53936002)(97736004)(33656002)(105586002)(606006)(54896002); DIR:OUT; SFP:1102; SCL:1; SRVR:MEAPR01MB3013; H:MEAPR01MB3542.ausprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: team.telstra.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: AqtVClgDBYHO23nDJslKU7EbF6U63/D2+OJsucIUKHD9DENWQ2w5nU+CfgtfbspZe+sn60dnw5oFBu9sTgw52S9wlHV9rPIehrseJmXImGBKbqZeY/Pm8oVoM1/b8tyrP8uutDQSrBVXP0vMWC4t2VkjJVHxWIA+8QB+tuWYNFEDfzkPl5Ty1xS6nAb0ZkzMXpbpksXLa0tbOYofnOuJE0tQ4Y9waa3Tv0SFuCFETGgo8CAflPonL+iIcBpB+AebYexCj3UPtt3eKcdUNi5KKZ5ZtCDH/wOs7JV0izNh4I55jxc35QdYcGC881QgpggqJwsAh6ZXehYUkzlPYYP0PjpslEpFQ3SUJGQKiRuva/o=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MEAPR01MB35428C99CD504725D428BB6BE5E60MEAPR01MB3542ausp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4f26cce7-3fb7-464d-76cd-08d62d75d097
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2018 23:28:55.2733 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 49dfc6a3-5fb7-49f4-adea-c54e725bb854
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MEAPR01MB3013
X-OriginatorOrg: team.telstra.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/3iu1lPLtdfPNLgRWpjmGzEb74Pg>
Subject: Re: [art] [Technical Errata Reported] RFC7807 (5515)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 23:40:46 -0000

--_000_MEAPR01MB35428C99CD504725D428BB6BE5E60MEAPR01MB3542ausp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gc3VyZSBDIyBjb2RlIGNhbiBkaXN0aW5ndWlzaCBhIG1pc3NpbmcgSlNPTiBtZW1iZXIg
ZnJvbSBhIG1lbWJlciB3aXRoIHZhbHVlIG51bGwgaWYgaXQgdHJpZXMuIEJ1dCBpdCBzb3VuZHMg
bGlrZSBDIyBoYXMgYSBwb3B1bGFyIHBhcnNlLXRvLW9iamVjdCAob3Igb2JqZWN0LXRvLWpzb24p
IGltcGxlbWVudGF0aW9uIHRoYXQgZG9lc27igJl0IGRpc3Rpbmd1aXNoIHRoZXNlIGVhc2lseSBi
eSBkZWZhdWx0LiBUaGF0IGlzIGEgcGl0eS4gQnV0IGV4cGxpY2l0bHkgYWxsb3dpbmcgInR5cGUi
Om51bGwgZmVlbHMgbGlrZSBhbiBwb29yIGhhY2sgdGhhdCBhZGRzIGJ1cmRlbnMgdG8gb3RoZXIg
aW1wbGVtZW50YXRpb25zLiBJZiBpdCByZWFsbHkgaXMgbmVjZXNzYXJ5IGZvciB0aGUgSlNPTiBl
Y29zeXN0ZW0gcHJlc3VtYWJseSBpdCBhcHBsaWVzIHRvIGFsbW9zdCBhbGwgSlNPTiwgbm90IGp1
c3QgInR5cGUiIGluIFJGQzc4MDcg4oCcUHJvYmxlbSBEZXRhaWxzIGZvciBIVFRQIEFJUHPigJ0g
c28gYW4gdXBkYXRlIHRvIFJGQzc0OTMg4oCcVGhlIEktSlNPTiBNZXNzYWdlIEZvcm1hdOKAnSB3
b3VsZCBiZSBtb3JlIGFwcHJvcHJpYXRlLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQoNCkZyb206IFN0
ZXZlbiBMaWVrZW5zIFttYWlsdG86c3RldmVuLmxpZWtlbnNAZ21haWwuY29tXQ0KU2VudDogTW9u
ZGF5LCA4IE9jdG9iZXIgMjAxOCA2OjE4IFBNDQpUbzogTWFuZ2VyLCBKYW1lcyA8SmFtZXMuSC5N
YW5nZXJAdGVhbS50ZWxzdHJhLmNvbT4NCkNjOiBNYXJrIE5vdHRpbmdoYW0gPG1ub3RAbW5vdC5u
ZXQ+OyBhcnRAaWV0Zi5vcmc7IFJGQyBFcnJhdGEgU3lzdGVtIDxyZmMtZWRpdG9yQHJmYy1lZGl0
b3Iub3JnPg0KU3ViamVjdDogUmU6IFthcnRdIFtUZWNobmljYWwgRXJyYXRhIFJlcG9ydGVkXSBS
RkM3ODA3ICg1NTE1KQ0KDQpKYW1lcywgSSB0b3RhbGx5IGdldCB3aGF0IHlvdSdyZSBzYXlpbmcg
YnV0IHlvdSBjYW4ndCBtYWtlICJtaXNzaW5nIiB2YWxpZCBhbmQgIm51bGwiIGludmFsaWQganVz
dCBiZWNhdXNlIHN0YXRpY2FsbHkgdHlwZWQgbGFuZ3VhZ2VzIGxpa2UgQyMgZG9uJ3QgZXZlbiBo
YXZlIGEgd2F5IHRvIGRldGVjdCB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIG51bGwgb3IgbWlzc2lu
ZyBwcm9wZXJ0aWVzIGFmdGVyIGNvbnZlcnRpbmcgdGhlIGpzb24gdG8gb2JqZWN0cy4NCk9uIE1v
biwgT2N0IDgsIDIwMTgsIDA1OjQyIE1hbmdlciwgSmFtZXMgPEphbWVzLkguTWFuZ2VyQHRlYW0u
dGVsc3RyYS5jb208bWFpbHRvOkphbWVzLkguTWFuZ2VyQHRlYW0udGVsc3RyYS5jb20+PiB3cm90
ZToNCnsidHlwZSI6MjMsIC4uLn0sIHsidHlwZSI6dHJ1ZSwgLi4ufSwgeyJ0eXBlIjpbImFiYyJd
LCAuLi59LCBhbmQgeyJ0eXBlIjoifG5vdCBhIHVyaT4iLCAuLi59IGFyZSBqdXN0IGFzICJzeW50
YWN0aWNhbGx5IGNvcnJlY3QiIEpTT04gYXMgeyJ0eXBlIjpudWxsLCAuLi59LiBUaGUgc3BlYyB0
ZXh0IHNheXM6DQoNCiAgInR5cGUiIChzdHJpbmcpIC0gQSBVUkkgcmVmZXJlbmNlIC4uLg0KDQpz
byBpdCBpcyBjbGVhciB0aGF0IGFsbCB0aGVzZSBleGFtcGxlcyBhcmUgaW52YWxpZC4gVGhlIHNw
ZWMgZG9lc27igJl0IGRlZmluZSBob3cgdG8gaGFuZGxlIHRoZSB6aWxsaW9ucyBvZiBvdGhlciB3
YXlzIGEgInByb2JsZW0gZGV0YWlsIiBkb2MgY2FuIGJlIGludmFsaWQgKHdoaWNoIGlzIGZpbmUp
IHNvIGl0IGRvZXNuJ3QgbmVlZCBzcGVjaWFsIHRleHQgYWJvdXQgInR5cGUiOm51bGwuIEp1c3Qg
UkVKRUNUIHRoaXMgZXJyYXRhLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBhcnQgW21haWx0bzphcnQtYm91bmNlc0BpZXRmLm9yZzxtYWls
dG86YXJ0LWJvdW5jZXNAaWV0Zi5vcmc+XSBPbiBCZWhhbGYgT2YgTWFyayBOb3R0aW5naGFtDQpT
ZW50OiBNb25kYXksIDggT2N0b2JlciAyMDE4IDI6MjUgUE0NClRvOiBTdGV2ZW4gTGlla2VucyA8
c3RldmVuLmxpZWtlbnNAZ21haWwuY29tPG1haWx0bzpzdGV2ZW4ubGlla2Vuc0BnbWFpbC5jb20+
Pg0KQ2M6IEJlbiBDYW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPG1haWx0bzpiZW5Abm9zdHJ1bS5j
b20+PjsgYWRhbUBub3N0cnVtLmNvbTxtYWlsdG86YWRhbUBub3N0cnVtLmNvbT47IEFsZXhleSBN
ZWxuaWtvdiA8YWFtZWxuaWtvdkBmYXN0bWFpbC5mbTxtYWlsdG86YWFtZWxuaWtvdkBmYXN0bWFp
bC5mbT4+OyBhcnRAaWV0Zi5vcmc8bWFpbHRvOmFydEBpZXRmLm9yZz47IHN1cGVydXNlckBnbWFp
bC5jb208bWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb20+OyBFcmlrIFdpbGRlIDxlcmlrLndpbGRl
QGRyZXQubmV0PG1haWx0bzplcmlrLndpbGRlQGRyZXQubmV0Pj47IFJGQyBFcnJhdGEgU3lzdGVt
IDxyZmMtZWRpdG9yQHJmYy1lZGl0b3Iub3JnPG1haWx0bzpyZmMtZWRpdG9yQHJmYy1lZGl0b3Iu
b3JnPj4NClN1YmplY3Q6IFJlOiBbYXJ0XSBbVGVjaG5pY2FsIEVycmF0YSBSZXBvcnRlZF0gUkZD
NzgwNyAoNTUxNSkNCg0KSGkgU3RldmVuLA0KDQpUaGF0J3MgYSBnb29kIHF1ZXN0aW9uLiBSaWdo
dCBub3csIHRoZSBiZXN0IHdlIGNhbiBkbyBpcyBtYXJrIHRoaXMgZXJyYXR1bSAiSE9MRCBGT1Ig
VVBEQVRFLiINCg0KSSd2ZSBiZWVuIHRoaW5raW5nIGZvciBhIHdoaWxlIHRoYXQgd2UgbmVlZCBs
b25nZXItbGl2ZWQgaXNzdWUgdHJhY2tlcnMgZm9yIGFsbCBIVFRQIHNwZWNpZmljYXRpb25zLiBX
ZSBoYXZlIG9uZSBmb3IgdGhlICJjb3JlIiBzcGVjcywgYnV0IHRoZSAiZXh0ZW5zaW9ucyIgb25l
IGlzIG9ubHkgaW50ZW5kZWQgZm9yIGFjdGl2ZSBzcGVjcy4gSG9wZWZ1bGx5IHdlJ2xsIG1ha2Ug
dGhpcyBlYXNpZXIgdG8gdXNlL3VuZGVyc3RhbmQgaW4gdGhlIG5vdC10b28tZGlzdGFudCBmdXR1
cmUuDQoNCkNoZWVycywNCg0KDQoNCg0KDQo+IE9uIDYgT2N0IDIwMTgsIGF0IDc6NTIgcG0sIFN0
ZXZlbiBMaWVrZW5zIDxzdGV2ZW4ubGlla2Vuc0BnbWFpbC5jb208bWFpbHRvOnN0ZXZlbi5saWVr
ZW5zQGdtYWlsLmNvbT4+IHdyb3RlOg0KPg0KPiBUaGF0J3MgZmFpciwgaXMgdGhlcmUgYSBiZXR0
ZXIgd2F5IHRvIHJlcG9ydCB0aGlzPw0KPg0KPiBPbiBTYXQsIE9jdCA2LCAyMDE4LCAwMTo1NSBN
YXJrIE5vdHRpbmdoYW0gPG1ub3RAbW5vdC5uZXQ8bWFpbHRvOm1ub3RAbW5vdC5uZXQ+PiB3cm90
ZToNCj4gVGhpcyBpcyBhIHN1YnN0YW50aXZlIGNoYW5nZS4gV2UgY2Fu4oCZdCBkbyB0aGF0IGlu
IGFuIGVycmF0dW0uDQo+DQo+IFNlbnQgZnJvbSBteSBpUGhvbmUNCj4NCj4gPiBPbiA2IE9jdCAy
MDE4LCBhdCAxMjowMSBhbSwgUkZDIEVycmF0YSBTeXN0ZW0gPHJmYy1lZGl0b3JAcmZjLWVkaXRv
ci5vcmc8bWFpbHRvOnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc+PiB3cm90ZToNCj4gPg0KPiA+
IFRoZSBmb2xsb3dpbmcgZXJyYXRhIHJlcG9ydCBoYXMgYmVlbiBzdWJtaXR0ZWQgZm9yIFJGQzc4
MDcsICJQcm9ibGVtDQo+ID4gRGV0YWlscyBmb3IgSFRUUCBBUElzIi4NCj4gPg0KPiA+IC0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4gWW91IG1heSByZXZpZXcgdGhl
IHJlcG9ydCBiZWxvdyBhbmQgYXQ6DQo+ID4gaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9lcnJh
dGEvZWlkNTUxNQ0KPiA+DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4gPiBUeXBlOiBUZWNobmljYWwNCj4gPiBSZXBvcnRlZCBieTogU3RldmVuIDxzdGV2ZW4u
bGlla2Vuc0BnbWFpbC5jb208bWFpbHRvOnN0ZXZlbi5saWVrZW5zQGdtYWlsLmNvbT4+DQo+ID4N
Cj4gPiBTZWN0aW9uOiAzLjENCj4gPg0KPiA+IE9yaWdpbmFsIFRleHQNCj4gPiAtLS0tLS0tLS0t
LS0tDQo+ID4gICBvICAidHlwZSIgKHN0cmluZykgLSBBIFVSSSByZWZlcmVuY2UgW1JGQzM5ODZd
IHRoYXQgaWRlbnRpZmllcyB0aGUNCj4gPiAgICAgIHByb2JsZW0gdHlwZS4gIFRoaXMgc3BlY2lm
aWNhdGlvbiBlbmNvdXJhZ2VzIHRoYXQsIHdoZW4NCj4gPiAgICAgIGRlcmVmZXJlbmNlZCwgaXQg
cHJvdmlkZSBodW1hbi1yZWFkYWJsZSBkb2N1bWVudGF0aW9uIGZvciB0aGUNCj4gPiAgICAgIHBy
b2JsZW0gdHlwZSAoZS5nLiwgdXNpbmcgSFRNTCBbVzNDLlJFQy1odG1sNS0yMDE0MTAyOF0pLiAg
V2hlbg0KPiA+ICAgICAgdGhpcyBtZW1iZXIgaXMgbm90IHByZXNlbnQsIGl0cyB2YWx1ZSBpcyBh
c3N1bWVkIHRvIGJlDQo+ID4gICAgICAiYWJvdXQ6YmxhbmsiLg0KPiA+DQo+ID4gQ29ycmVjdGVk
IFRleHQNCj4gPiAtLS0tLS0tLS0tLS0tLQ0KPiA+ICAgbyAgInR5cGUiIChzdHJpbmcpIC0gQSBV
UkkgcmVmZXJlbmNlIFtSRkMzOTg2XSB0aGF0IGlkZW50aWZpZXMgdGhlDQo+ID4gICAgICBwcm9i
bGVtIHR5cGUuICBUaGlzIHNwZWNpZmljYXRpb24gZW5jb3VyYWdlcyB0aGF0LCB3aGVuDQo+ID4g
ICAgICBkZXJlZmVyZW5jZWQsIGl0IHByb3ZpZGUgaHVtYW4tcmVhZGFibGUgZG9jdW1lbnRhdGlv
biBmb3IgdGhlDQo+ID4gICAgICBwcm9ibGVtIHR5cGUgKGUuZy4sIHVzaW5nIEhUTUwgW1czQy5S
RUMtaHRtbDUtMjAxNDEwMjhdKS4gIFdoZW4NCj4gPiAgICAgIHRoaXMgbWVtYmVyIGlzIG1pc3Np
bmcgb3IgbnVsbCwgaXRzIHZhbHVlIGlzIGFzc3VtZWQgdG8gYmUNCj4gPiAgICAgICJhYm91dDpi
bGFuayIuDQo+ID4NCj4gPiBOb3Rlcw0KPiA+IC0tLS0tDQo+ID4gSlNPTiBvYmplY3RzIHdpdGgg
YSBudWxsICJ0eXBlIiBhcmUgc3ludGFjdGljYWxseSBjb3JyZWN0LCBidXQgdGhlcmUgaXMgbm8g
aW5mb3JtYXRpb24gb24gaG93IGl0IHNob3VsZCBiZSBoYW5kbGVkLg0KPiA+DQo+ID4gew0KPiA+
ICAgICJ0eXBlIjogbnVsbCwNCj4gPiAgICAic3RhdHVzIjogNDA0LA0KPiA+ICAgICJ0aXRsZSI6
ICJOb3QgRm91bmQiDQo+ID4gfQ0KPiA+DQo+ID4gSXQgbWFrZXMgc2Vuc2UgdG8gdHJlYXQgbnVs
bCBhcyBhbiBhbGlhcyBvZiAiYWJvdXQ6YmxhbmsiIGFuZCB0aGF0J3MgaG93IEkgdGhpbmsgaXQg
c2hvdWxkIGJlIGRvY3VtZW50ZWQuDQo+ID4NCj4gPiBJbnN0cnVjdGlvbnM6DQo+ID4gLS0tLS0t
LS0tLS0tLQ0KPiA+IFRoaXMgZXJyYXR1bSBpcyBjdXJyZW50bHkgcG9zdGVkIGFzICJSZXBvcnRl
ZCIuIElmIG5lY2Vzc2FyeSwgcGxlYXNlDQo+ID4gdXNlICJSZXBseSBBbGwiIHRvIGRpc2N1c3Mg
d2hldGhlciBpdCBzaG91bGQgYmUgdmVyaWZpZWQgb3INCj4gPiByZWplY3RlZC4gV2hlbiBhIGRl
Y2lzaW9uIGlzIHJlYWNoZWQsIHRoZSB2ZXJpZnlpbmcgcGFydHkgY2FuIGxvZyBpbg0KPiA+IHRv
IGNoYW5nZSB0aGUgc3RhdHVzIGFuZCBlZGl0IHRoZSByZXBvcnQsIGlmIG5lY2Vzc2FyeS4NCj4g
Pg0KPiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4gUkZDNzgw
NyAoZHJhZnQtaWV0Zi1hcHBzYXdnLWh0dHAtcHJvYmxlbS0wMykNCj4gPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+IFRpdGxlICAgICAgICAgICAgICAgOiBQcm9i
bGVtIERldGFpbHMgZm9yIEhUVFAgQVBJcw0KPiA+IFB1YmxpY2F0aW9uIERhdGUgICAgOiBNYXJj
aCAyMDE2DQo+ID4gQXV0aG9yKHMpICAgICAgICAgICA6IE0uIE5vdHRpbmdoYW0sIEUuIFdpbGRl
DQo+ID4gQ2F0ZWdvcnkgICAgICAgICAgICA6IFBST1BPU0VEIFNUQU5EQVJEDQo+ID4gU291cmNl
ICAgICAgICAgICAgICA6IEFSVCBBcmVhIEdlbmVyYWwgQXBwbGljYXRpb24gV29ya2luZyBHcm91
cA0KPiA+IEFyZWEgICAgICAgICAgICAgICAgOiBBcHBsaWNhdGlvbnMgYW5kIFJlYWwtVGltZQ0K
PiA+IFN0cmVhbSAgICAgICAgICAgICAgOiBJRVRGDQo+ID4gVmVyaWZ5aW5nIFBhcnR5ICAgICA6
IElFU0cNCj4NCg0KLS0NCk1hcmsgTm90dGluZ2hhbSAgIGh0dHBzOi8vd3d3Lm1ub3QubmV0Lw0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KYXJ0IG1h
aWxpbmcgbGlzdA0KYXJ0QGlldGYub3JnPG1haWx0bzphcnRAaWV0Zi5vcmc+DQpodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FydA0K

--_000_MEAPR01MB35428C99CD504725D428BB6BE5E60MEAPR01MB3542ausp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHls
ZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0K
CW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXpl
OjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tQVUiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5J4oCZbSBzdXJlIEMjIGNvZGUg
Y2FuIGRpc3Rpbmd1aXNoIGEgbWlzc2luZyBKU09OIG1lbWJlciBmcm9tIGEgbWVtYmVyIHdpdGgg
dmFsdWUgbnVsbCBpZiBpdCB0cmllcy4gQnV0IGl0IHNvdW5kcyBsaWtlIEMjIGhhcyBhIHBvcHVs
YXINCiBwYXJzZS10by1vYmplY3QgKG9yIG9iamVjdC10by1qc29uKSBpbXBsZW1lbnRhdGlvbiB0
aGF0IGRvZXNu4oCZdCBkaXN0aW5ndWlzaCB0aGVzZSBlYXNpbHkgYnkgZGVmYXVsdC4gVGhhdCBp
cyBhIHBpdHkuIEJ1dCBleHBsaWNpdGx5IGFsbG93aW5nICZxdW90O3R5cGUmcXVvdDs6bnVsbCBm
ZWVscyBsaWtlIGFuIHBvb3IgaGFjayB0aGF0IGFkZHMgYnVyZGVucyB0byBvdGhlciBpbXBsZW1l
bnRhdGlvbnMuIElmIGl0IHJlYWxseSBpcyBuZWNlc3NhcnkgZm9yIHRoZSBKU09ODQogZWNvc3lz
dGVtIHByZXN1bWFibHkgaXQgYXBwbGllcyB0byBhbG1vc3QgYWxsIEpTT04sIG5vdCBqdXN0ICZx
dW90O3R5cGUmcXVvdDsgaW4gUkZDNzgwNyDigJxQcm9ibGVtIERldGFpbHMgZm9yIEhUVFAgQUlQ
c+KAnSBzbyBhbiB1cGRhdGUgdG8gUkZDNzQ5MyDigJxUaGUgSS1KU09OIE1lc3NhZ2UgRm9ybWF0
4oCdIHdvdWxkIGJlIG1vcmUgYXBwcm9wcmlhdGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4tLTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj5KYW1lcyBNYW5nZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBTdGV2ZW4gTGlla2VucyBbbWFpbHRvOnN0ZXZlbi5s
aWVrZW5zQGdtYWlsLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIDggT2N0b2JlciAy
MDE4IDY6MTggUE08YnI+DQo8Yj5Ubzo8L2I+IE1hbmdlciwgSmFtZXMgJmx0O0phbWVzLkguTWFu
Z2VyQHRlYW0udGVsc3RyYS5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBNYXJrIE5vdHRpbmdoYW0g
Jmx0O21ub3RAbW5vdC5uZXQmZ3Q7OyBhcnRAaWV0Zi5vcmc7IFJGQyBFcnJhdGEgU3lzdGVtICZs
dDtyZmMtZWRpdG9yQHJmYy1lZGl0b3Iub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTog
W2FydF0gW1RlY2huaWNhbCBFcnJhdGEgUmVwb3J0ZWRdIFJGQzc4MDcgKDU1MTUpPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9t
OjEyLjBwdCI+SmFtZXMsIEkgdG90YWxseSBnZXQgd2hhdCB5b3UncmUgc2F5aW5nIGJ1dCB5b3Ug
Y2FuJ3QgbWFrZSAmcXVvdDttaXNzaW5nJnF1b3Q7IHZhbGlkIGFuZCAmcXVvdDtudWxsJnF1b3Q7
IGludmFsaWQganVzdCBiZWNhdXNlIHN0YXRpY2FsbHkgdHlwZWQgbGFuZ3VhZ2VzIGxpa2UgQyMg
ZG9uJ3QgZXZlbiBoYXZlIGEgd2F5IHRvIGRldGVjdCB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIG51
bGwgb3IgbWlzc2luZw0KIHByb3BlcnRpZXMgYWZ0ZXIgY29udmVydGluZyB0aGUganNvbiB0byBv
YmplY3RzLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBNb24sIE9jdCA4LCAyMDE4LCAwNTo0MiBNYW5nZXIsIEphbWVzICZsdDs8YSBocmVmPSJt
YWlsdG86SmFtZXMuSC5NYW5nZXJAdGVhbS50ZWxzdHJhLmNvbSI+SmFtZXMuSC5NYW5nZXJAdGVh
bS50ZWxzdHJhLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+eyZxdW90O3R5cGUmcXVvdDs6MjMsIC4uLn0s
IHsmcXVvdDt0eXBlJnF1b3Q7OnRydWUsIC4uLn0sIHsmcXVvdDt0eXBlJnF1b3Q7OlsmcXVvdDth
YmMmcXVvdDtdLCAuLi59LCBhbmQgeyZxdW90O3R5cGUmcXVvdDs6JnF1b3Q7fG5vdCBhIHVyaSZn
dDsmcXVvdDssIC4uLn0gYXJlIGp1c3QgYXMgJnF1b3Q7c3ludGFjdGljYWxseSBjb3JyZWN0JnF1
b3Q7IEpTT04gYXMgeyZxdW90O3R5cGUmcXVvdDs6bnVsbCwgLi4ufS4gVGhlIHNwZWMgdGV4dCBz
YXlzOjxicj4NCjxicj4NCiZuYnNwOyAmcXVvdDt0eXBlJnF1b3Q7IChzdHJpbmcpIC0gQSBVUkkg
cmVmZXJlbmNlIC4uLjxicj4NCjxicj4NCnNvIGl0IGlzIGNsZWFyIHRoYXQgYWxsIHRoZXNlIGV4
YW1wbGVzIGFyZSBpbnZhbGlkLiBUaGUgc3BlYyBkb2VzbuKAmXQgZGVmaW5lIGhvdyB0byBoYW5k
bGUgdGhlIHppbGxpb25zIG9mIG90aGVyIHdheXMgYSAmcXVvdDtwcm9ibGVtIGRldGFpbCZxdW90
OyBkb2MgY2FuIGJlIGludmFsaWQgKHdoaWNoIGlzIGZpbmUpIHNvIGl0IGRvZXNuJ3QgbmVlZCBz
cGVjaWFsIHRleHQgYWJvdXQgJnF1b3Q7dHlwZSZxdW90OzpudWxsLiBKdXN0IFJFSkVDVCB0aGlz
IGVycmF0YS48YnI+DQo8YnI+DQotLTxicj4NCkphbWVzIE1hbmdlcjxicj4NCjxicj4NCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogYXJ0IFttYWlsdG86PGEgaHJlZj0ibWFp
bHRvOmFydC1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+YXJ0LWJvdW5jZXNAaWV0
Zi5vcmc8L2E+XSBPbiBCZWhhbGYgT2YgTWFyayBOb3R0aW5naGFtPGJyPg0KU2VudDogTW9uZGF5
LCA4IE9jdG9iZXIgMjAxOCAyOjI1IFBNPGJyPg0KVG86IFN0ZXZlbiBMaWVrZW5zICZsdDs8YSBo
cmVmPSJtYWlsdG86c3RldmVuLmxpZWtlbnNAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+c3Rl
dmVuLmxpZWtlbnNAZ21haWwuY29tPC9hPiZndDs8YnI+DQpDYzogQmVuIENhbXBiZWxsICZsdDs8
YSBocmVmPSJtYWlsdG86YmVuQG5vc3RydW0uY29tIiB0YXJnZXQ9Il9ibGFuayI+YmVuQG5vc3Ry
dW0uY29tPC9hPiZndDs7DQo8YSBocmVmPSJtYWlsdG86YWRhbUBub3N0cnVtLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPmFkYW1Abm9zdHJ1bS5jb208L2E+OyBBbGV4ZXkgTWVsbmlrb3YgJmx0OzxhIGhy
ZWY9Im1haWx0bzphYW1lbG5pa292QGZhc3RtYWlsLmZtIiB0YXJnZXQ9Il9ibGFuayI+YWFtZWxu
aWtvdkBmYXN0bWFpbC5mbTwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRvOmFydEBpZXRmLm9yZyIg
dGFyZ2V0PSJfYmxhbmsiPmFydEBpZXRmLm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpzdXBlcnVz
ZXJAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+DQpzdXBlcnVzZXJAZ21haWwuY29tPC9hPjsg
RXJpayBXaWxkZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmVyaWsud2lsZGVAZHJldC5uZXQiIHRhcmdl
dD0iX2JsYW5rIj5lcmlrLndpbGRlQGRyZXQubmV0PC9hPiZndDs7IFJGQyBFcnJhdGEgU3lzdGVt
ICZsdDs8YSBocmVmPSJtYWlsdG86cmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiPnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc8L2E+Jmd0Ozxicj4NClN1YmplY3Q6IFJl
OiBbYXJ0XSBbVGVjaG5pY2FsIEVycmF0YSBSZXBvcnRlZF0gUkZDNzgwNyAoNTUxNSk8YnI+DQo8
YnI+DQpIaSBTdGV2ZW4sPGJyPg0KPGJyPg0KVGhhdCdzIGEgZ29vZCBxdWVzdGlvbi4gUmlnaHQg
bm93LCB0aGUgYmVzdCB3ZSBjYW4gZG8gaXMgbWFyayB0aGlzIGVycmF0dW0gJnF1b3Q7SE9MRCBG
T1IgVVBEQVRFLiZxdW90Ozxicj4NCjxicj4NCkkndmUgYmVlbiB0aGlua2luZyBmb3IgYSB3aGls
ZSB0aGF0IHdlIG5lZWQgbG9uZ2VyLWxpdmVkIGlzc3VlIHRyYWNrZXJzIGZvciBhbGwgSFRUUCBz
cGVjaWZpY2F0aW9ucy4gV2UgaGF2ZSBvbmUgZm9yIHRoZSAmcXVvdDtjb3JlJnF1b3Q7IHNwZWNz
LCBidXQgdGhlICZxdW90O2V4dGVuc2lvbnMmcXVvdDsgb25lIGlzIG9ubHkgaW50ZW5kZWQgZm9y
IGFjdGl2ZSBzcGVjcy4gSG9wZWZ1bGx5IHdlJ2xsIG1ha2UgdGhpcyBlYXNpZXIgdG8gdXNlL3Vu
ZGVyc3RhbmQgaW4gdGhlIG5vdC10b28tZGlzdGFudA0KIGZ1dHVyZS48YnI+DQo8YnI+DQpDaGVl
cnMsPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KJmd0OyBPbiA2IE9jdCAyMDE4
LCBhdCA3OjUyIHBtLCBTdGV2ZW4gTGlla2VucyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnN0ZXZlbi5s
aWVrZW5zQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnN0ZXZlbi5saWVrZW5zQGdtYWlsLmNv
bTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGF0J3MgZmFpciwgaXMgdGhl
cmUgYSBiZXR0ZXIgd2F5IHRvIHJlcG9ydCB0aGlzPzxicj4NCiZndDsgPGJyPg0KJmd0OyBPbiBT
YXQsIE9jdCA2LCAyMDE4LCAwMTo1NSBNYXJrIE5vdHRpbmdoYW0gJmx0OzxhIGhyZWY9Im1haWx0
bzptbm90QG1ub3QubmV0IiB0YXJnZXQ9Il9ibGFuayI+bW5vdEBtbm90Lm5ldDwvYT4mZ3Q7IHdy
b3RlOjxicj4NCiZndDsgVGhpcyBpcyBhIHN1YnN0YW50aXZlIGNoYW5nZS4gV2UgY2Fu4oCZdCBk
byB0aGF0IGluIGFuIGVycmF0dW0uIDxicj4NCiZndDsgPGJyPg0KJmd0OyBTZW50IGZyb20gbXkg
aVBob25lPGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgT24gNiBPY3QgMjAxOCwgYXQgMTI6MDEg
YW0sIFJGQyBFcnJhdGEgU3lzdGVtICZsdDs8YSBocmVmPSJtYWlsdG86cmZjLWVkaXRvckByZmMt
ZWRpdG9yLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc8L2E+
Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IFRoZSBmb2xsb3dpbmcg
ZXJyYXRhIHJlcG9ydCBoYXMgYmVlbiBzdWJtaXR0ZWQgZm9yIFJGQzc4MDcsICZxdW90O1Byb2Js
ZW0gPGJyPg0KJmd0OyAmZ3Q7IERldGFpbHMgZm9yIEhUVFAgQVBJcyZxdW90Oy48YnI+DQomZ3Q7
ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tPGJyPg0KJmd0OyAmZ3Q7IFlvdSBtYXkgcmV2aWV3IHRoZSByZXBvcnQgYmVsb3cgYW5kIGF0
Ojxicj4NCiZndDsgJmd0OyA8YSBocmVmPSJodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2VycmF0
YS9laWQ1NTE1IiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9lcnJh
dGEvZWlkNTUxNTwvYT48YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyAmZ3Q7IFR5cGU6IFRlY2huaWNh
bDxicj4NCiZndDsgJmd0OyBSZXBvcnRlZCBieTogU3RldmVuICZsdDs8YSBocmVmPSJtYWlsdG86
c3RldmVuLmxpZWtlbnNAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+c3RldmVuLmxpZWtlbnNA
Z21haWwuY29tPC9hPiZndDs8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IFNlY3Rpb246
IDMuMTxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgT3JpZ2luYWwgVGV4dDxicj4NCiZn
dDsgJmd0OyAtLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7ICZuYnNwO28mbmJzcDsg
JnF1b3Q7dHlwZSZxdW90OyAoc3RyaW5nKSAtIEEgVVJJIHJlZmVyZW5jZSBbUkZDMzk4Nl0gdGhh
dCBpZGVudGlmaWVzIHRoZTxicj4NCiZndDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IHByb2Js
ZW0gdHlwZS4mbmJzcDsgVGhpcyBzcGVjaWZpY2F0aW9uIGVuY291cmFnZXMgdGhhdCwgd2hlbjxi
cj4NCiZndDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IGRlcmVmZXJlbmNlZCwgaXQgcHJvdmlk
ZSBodW1hbi1yZWFkYWJsZSBkb2N1bWVudGF0aW9uIGZvciB0aGU8YnI+DQomZ3Q7ICZndDsmbmJz
cDsgJm5ic3A7ICZuYnNwOyBwcm9ibGVtIHR5cGUgKGUuZy4sIHVzaW5nIEhUTUwgW1czQy5SRUMt
aHRtbDUtMjAxNDEwMjhdKS4mbmJzcDsgV2hlbjxicj4NCiZndDsgJmd0OyZuYnNwOyAmbmJzcDsg
Jm5ic3A7IHRoaXMgbWVtYmVyIGlzIG5vdCBwcmVzZW50LCBpdHMgdmFsdWUgaXMgYXNzdW1lZCB0
byBiZTxicj4NCiZndDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O2Fib3V0OmJsYW5r
JnF1b3Q7Ljxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgQ29ycmVjdGVkIFRleHQ8YnI+
DQomZ3Q7ICZndDsgLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7ICZndDsmbmJzcDsgJm5ic3A7byZu
YnNwOyAmcXVvdDt0eXBlJnF1b3Q7IChzdHJpbmcpIC0gQSBVUkkgcmVmZXJlbmNlIFtSRkMzOTg2
XSB0aGF0IGlkZW50aWZpZXMgdGhlPGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsg
cHJvYmxlbSB0eXBlLiZuYnNwOyBUaGlzIHNwZWNpZmljYXRpb24gZW5jb3VyYWdlcyB0aGF0LCB3
aGVuPGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgZGVyZWZlcmVuY2VkLCBpdCBw
cm92aWRlIGh1bWFuLXJlYWRhYmxlIGRvY3VtZW50YXRpb24gZm9yIHRoZTxicj4NCiZndDsgJmd0
OyZuYnNwOyAmbmJzcDsgJm5ic3A7IHByb2JsZW0gdHlwZSAoZS5nLiwgdXNpbmcgSFRNTCBbVzND
LlJFQy1odG1sNS0yMDE0MTAyOF0pLiZuYnNwOyBXaGVuPGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7ICZu
YnNwOyAmbmJzcDsgdGhpcyBtZW1iZXIgaXMgbWlzc2luZyBvciBudWxsLCBpdHMgdmFsdWUgaXMg
YXNzdW1lZCB0byBiZTxicj4NCiZndDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O2Fi
b3V0OmJsYW5rJnF1b3Q7Ljxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgTm90ZXM8YnI+
DQomZ3Q7ICZndDsgLS0tLS08YnI+DQomZ3Q7ICZndDsgSlNPTiBvYmplY3RzIHdpdGggYSBudWxs
ICZxdW90O3R5cGUmcXVvdDsgYXJlIHN5bnRhY3RpY2FsbHkgY29ycmVjdCwgYnV0IHRoZXJlIGlz
IG5vIGluZm9ybWF0aW9uIG9uIGhvdyBpdCBzaG91bGQgYmUgaGFuZGxlZC48YnI+DQomZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7IHs8YnI+DQomZ3Q7ICZndDsmbmJzcDsgJm5ic3A7ICZxdW90O3R5
cGUmcXVvdDs6IG51bGwsPGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmcXVvdDtzdGF0dXMm
cXVvdDs6IDQwNCw8YnI+DQomZ3Q7ICZndDsmbmJzcDsgJm5ic3A7ICZxdW90O3RpdGxlJnF1b3Q7
OiAmcXVvdDtOb3QgRm91bmQmcXVvdDs8YnI+DQomZ3Q7ICZndDsgfTxicj4NCiZndDsgJmd0OyA8
YnI+DQomZ3Q7ICZndDsgSXQgbWFrZXMgc2Vuc2UgdG8gdHJlYXQgbnVsbCBhcyBhbiBhbGlhcyBv
ZiAmcXVvdDthYm91dDpibGFuayZxdW90OyBhbmQgdGhhdCdzIGhvdyBJIHRoaW5rIGl0IHNob3Vs
ZCBiZSBkb2N1bWVudGVkLjxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgSW5zdHJ1Y3Rp
b25zOjxicj4NCiZndDsgJmd0OyAtLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyAmZ3Q7IFRoaXMgZXJy
YXR1bSBpcyBjdXJyZW50bHkgcG9zdGVkIGFzICZxdW90O1JlcG9ydGVkJnF1b3Q7LiBJZiBuZWNl
c3NhcnksIHBsZWFzZSA8YnI+DQomZ3Q7ICZndDsgdXNlICZxdW90O1JlcGx5IEFsbCZxdW90OyB0
byBkaXNjdXNzIHdoZXRoZXIgaXQgc2hvdWxkIGJlIHZlcmlmaWVkIG9yIDxicj4NCiZndDsgJmd0
OyByZWplY3RlZC4gV2hlbiBhIGRlY2lzaW9uIGlzIHJlYWNoZWQsIHRoZSB2ZXJpZnlpbmcgcGFy
dHkgY2FuIGxvZyBpbiA8YnI+DQomZ3Q7ICZndDsgdG8gY2hhbmdlIHRoZSBzdGF0dXMgYW5kIGVk
aXQgdGhlIHJlcG9ydCwgaWYgbmVjZXNzYXJ5Ljxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZn
dDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7ICZndDsg
UkZDNzgwNyAoZHJhZnQtaWV0Zi1hcHBzYXdnLWh0dHAtcHJvYmxlbS0wMyk8YnI+DQomZ3Q7ICZn
dDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7ICZndDsg
VGl0bGUmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7OiBQcm9ibGVtIERldGFpbHMgZm9yIEhUVFAgQVBJczxicj4NCiZndDsgJmd0OyBQdWJsaWNh
dGlvbiBEYXRlJm5ic3A7ICZuYnNwOyA6IE1hcmNoIDIwMTY8YnI+DQomZ3Q7ICZndDsgQXV0aG9y
KHMpJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDs6IE0uIE5vdHRpbmdo
YW0sIEUuIFdpbGRlPGJyPg0KJmd0OyAmZ3Q7IENhdGVnb3J5Jm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgOiBQUk9QT1NFRCBTVEFOREFSRDxicj4NCiZndDsgJmd0OyBT
b3VyY2UmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgOiBB
UlQgQXJlYSBHZW5lcmFsIEFwcGxpY2F0aW9uIFdvcmtpbmcgR3JvdXA8YnI+DQomZ3Q7ICZndDsg
QXJlYSZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgOiBBcHBsaWNhdGlvbnMgYW5kIFJlYWwtVGltZTxicj4NCiZndDsgJmd0OyBTdHJlYW0mbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgOiBJRVRGPGJyPg0K
Jmd0OyAmZ3Q7IFZlcmlmeWluZyBQYXJ0eSZuYnNwOyAmbmJzcDsgJm5ic3A7OiBJRVNHPGJyPg0K
Jmd0OyA8YnI+DQo8YnI+DQotLTxicj4NCk1hcmsgTm90dGluZ2hhbSZuYnNwOyAmbmJzcDs8YSBo
cmVmPSJodHRwczovL3d3dy5tbm90Lm5ldC8iIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5t
bm90Lm5ldC88L2E+PGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188YnI+DQphcnQgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRv
OmFydEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmFydEBpZXRmLm9yZzwvYT48YnI+DQo8YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FydCIgdGFyZ2V0PSJf
YmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXJ0PC9hPjxvOnA+
PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_MEAPR01MB35428C99CD504725D428BB6BE5E60MEAPR01MB3542ausp_--


From nobody Mon Oct  8 20:29:19 2018
Return-Path: <suzworldwide@gmail.com>
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 5DF64131119; Mon,  8 Oct 2018 20:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 Q0rpHkig0HcT; Mon,  8 Oct 2018 20:29:08 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 6D0A913110B; Mon,  8 Oct 2018 20:29:08 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id e16-v6so62969ybk.8; Mon, 08 Oct 2018 20:29:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=mNKwO7kYmZ3U9LF9ackFaeGUV5APVx9psAMd9X5QI5M=; b=GMKi2Drh2uWUoB9XKdLuISZnOxPJ3N+2glKwjBmKPWRyCipsGhMf4MMBp0JsnTtvm/ 1Hr4ptFRHDcDPNeG/vU6Gn1p6e2NwWJrzZge7hDhfX+RiU6IbTgn6K5vuueAZCglCb2r jW9mfofTP1COLqLpAV5mzqnVuoB++gxV7f91ZCqsLNw7vxWvRDRKrel4Z6r5Z2uGUETM xCKHXvzWS0SGZJ9OYb0M9nTbrg8yI7kAUwzkIIiBgTWZqC+UcMrJ/o8wYmEikjHPjvAt 8gMLN0qS932PbWFK567xg7YCnnvBRDsOoH9iMG+qGJlMPnyC2Wd7Y5faZkwBooYTWdKk Xtxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=mNKwO7kYmZ3U9LF9ackFaeGUV5APVx9psAMd9X5QI5M=; b=AUK6eHPDn767C59ajB5kGmejtwRoRr3m4/Urwzc24a19UalXQJvaiDkfylytOHAvZh zdBc7cGDQvmvOxxuz2X8D7McXs/HmhPeDls3t3wb2UD69G/BuItC5rSHw/jITNwtRbkH Jj8QjULJA/l8t5s53Hnh/WTpNbIRdTow50+eN5QzzXsN3UKK9+rHvnZT1YEky0d0it+g oTScLbWyPYKbd+rtLZWaKtoo6ZmB2JD9x0PKwLUkQgV8TfWu0liG3twQfIZnP5wVpq45 TwI75PgndDu3kZ/nOQk12kBDua4w7T+FC8GLZxTGYuBGmy+oAfho7+elGvJ6awJpRCQD x2rw==
X-Gm-Message-State: ABuFfoi3fMOiwoWEXeH8UkfpuY0CVoRvKx+Ly36Uhj33PnZBRlMiumNX la+fMKIeE/fbtKgPVLTbjjE=
X-Google-Smtp-Source: ACcGV61rP/AT6Tju8VlMjg2a+sN80tIAXoZ1r39eU5sQge2y+US4mFtlrS0JYklFbCnQyf6979o/ZQ==
X-Received: by 2002:a25:2613:: with SMTP id m19-v6mr15215646ybm.513.1539055747647;  Mon, 08 Oct 2018 20:29:07 -0700 (PDT)
Received: from ?IPv6:2601:181:c381:29fe:49aa:4bbc:55d9:c0c1? ([2601:181:c381:29fe:49aa:4bbc:55d9:c0c1]) by smtp.gmail.com with ESMTPSA id e187-v6sm6634208ywb.106.2018.10.08.20.29.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Oct 2018 20:29:07 -0700 (PDT)
From: Suzanne Woolf <suzworldwide@gmail.com>
Message-Id: <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5D157C11-501B-4360-8C4D-C00EB6498B98"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 8 Oct 2018 23:29:04 -0400
In-Reply-To: <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com>
Cc: John C Klensin <john-ietf@jck.com>, Ted Hardie <ted.ietf@gmail.com>, =?utf-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>, i18nrp@ietf.org, nordmark@acm.org, idna-update@ietf.org, Applications and Real-Time Area Discussion <art@ietf.org>
To: Asmus Freytag <asmusf@ix.netcom.com>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/MB2cwNqfbx9euZf5wGx-pBQ3KxQ>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 03:29:11 -0000

--Apple-Mail=_5D157C11-501B-4360-8C4D-C00EB6498B98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

(A little confused over which mailing list is preferred for this =
particular discussion=E2=80=A6.)

> On Oct 8, 2018, at 4:34 PM, Asmus Freytag <asmusf@ix.netcom.com> =
wrote:
>=20
> On 10/8/2018 12:58 PM, John C Klensin wrote:
>> --On Monday, October 8, 2018 09:06 -0700 Ted Hardie
>> <ted.ietf@gmail.com> <mailto:ted.ietf@gmail.com> wrote:
>>=20
>>> Modulo Erik's comments, I think this is ready for publication.
>>> The instructions to IANA are clear and the rationale behind
>>> those instructions is laid out.
>>>=20
>>> I think we could ask for AD-sponsorship for this, but I also
>>> believe that the instructions could go to IANA now; at the
>>> very least, we could ask them to review.
>> Ted,
>>=20
>> I'm sorry, but I disagree.  Patrik has, as far as I can tell,
>> done the job that the IAB asked him to do in his liaison
>> capacity to Unicode,=20
> I thought this draft was in Patrik's role as the designated expert for =
the IANA registry.=20
>=20

That was also my impression. In March, the IAB said that =E2=80=9CThe =
IAB believes that the best current course of action for now is to bring =
the two [Unicode and the IDNA parameters registry] back into alignment =
while the IETF continues to work toward consensus on the underlying =
issues.  We have therefore asked the expert reviewer to bring the IDNA =
Parameters registry up to date=E2=80=A6=E2=80=9D The draft (I thought) =
is documenting the expert's examination of code points that had been =
added or had properties change in the course of that update, and the =
rationale for his recommendation about how to handle them in the =
registry.

>> but that job involves a number of
>> assumptions about how to proceed that interact with i18n
>> documents that the IETF has been unable to process.  If we
>> follow the precedent of RFC 6452, this document should be
>> processed as standards track even if it changes nothing.=20
> The relevant difference is that RFC 6452 contained this section:
>=20
> -------------------
>=20
> IETF Consensus
>=20
>    No change to RFC 5892 is needed based on the changes made in
>    Unicode 6.0.
>=20
>    This consensus does not imply that no changes will be made to
>    RFC 5892 for all future updates of The Unicode Standard.
>=20
>    This RFC has been produced because 6.0 is the first version of
>    Unicode to be released since IDNA2008 was published.
> --------------------
> I see no particular reason why such a section couldn't be added
> to Patrik's draft, allowing it to be processed like 6452 if that is
> felt to be more appropriate.
>=20
>=20
I think that having an RFC for this set of updates, documenting the =
rationale for the decision to update the registry to Unicode 11 without =
exceptions for the code points that changed properties, will be valuable =
for the future=E2=80=94 but AFAICT it=E2=80=99s not strictly necessary =
as part of the action Patrik was asked to take. I=E2=80=99m fine with =
adding language as Asmus is suggesting, which clarifies the current =
reasoning without restricting future decisions inappropriately.
>>  It
>> would be wildly inappropriate for it to constrain the
>> conclusions the IETF could reach about those other documents.
> I don't see how this would constrain IETF conclusions about other =
documents,
> or even RFC 5892 itself (other than that the consensus is to not add =
exceptions).
>=20
> There are changes that may be motivated by the general aspects of the =
interaction
> between Unicode and IDNA, but the kind of language as quoted above =
would not
> rule those out.
> You would need to make a more concrete claim how processing this RFC
> interferes with the work of IETF.
>=20
I admit I don=E2=80=99t see this either.=20
>> My understanding coming out of the BOF at IETF 102 was that the
>> ART ADs were going to establish a directorate to determine how
>> i18n documents were to be handled and to start processing those
>> documents.  This document would make an entirely reasonable
>> addition to that directorate's queue.   However, if an progress
>> has been made on creating that directorate, much less having it
>> convene and discuss processing of documents, I seem to have
>> missed the announcement(s).
> I don't necessarily see the plan for a new directorate as suspending =
IETFs
> ability to process certain RFCs indefinitely. The goal was to make it =
possible
> to process more of them and more consistently, not to provide an =
additional
> hurdle.
>=20
>=20
At this point, I see three separate issues, any two of which have some =
interaction, but I don=E2=80=99t see hard dependencies:

1. Updating the IDN parameters registry as the IAB requested. With =
apologies if I=E2=80=99m missing something, I don=E2=80=99t see the =
expert saying he can=E2=80=99t update the registry for some reason, or =
that there=E2=80=99s any ambiguity in what the update should be; it=E2=80=99=
s his judgment that =E2=80=9Cthe right thing to do=E2=80=9D about the =
code points that changed properties between Unicode 6.3 and Unicode 11 =
is consistent with what the standard tells him to do. So for the current =
situation, the standard, including the instructions to the expert, is =
adequate.

2. Having an RFC about the specifics of updating the registry to Unicode =
11. I agree with Patrik that having this document is useful, as an =
example of how to apply IDNA2008 to changes in Unicode; at the very =
least, the reasoning can inform future experts. But I see it as =
Informational=E2=80=94 a service to the community=E2=80=94 not as a =
change to the registry policy or an extension to the protocol standard. =
I don=E2=80=99t see a problem with making it AD-sponsored.

3. Establishing the proposed I18N directorate. I strongly agree that the =
IETF needs the directorate, or some other mechanism for reviewing i18n =
aspects of work across the IETF and providing backup for expert review =
as needed. But that=E2=80=99s also an optimization, to improve future =
handling of i18n documents.

I think all three of these things are important and useful. But it =
doesn=E2=80=99t look to me like any of the necessary decisions for these =
three items are gating on the others, or constraining the options for =
the others. They can be done more or less in parallel.



Suzanne


--Apple-Mail=_5D157C11-501B-4360-8C4D-C00EB6498B98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hi,<div class=3D""><br class=3D""></div><div class=3D""><div>(A=
 little confused over which mailing list is preferred for this =
particular discussion=E2=80=A6.)</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Oct 8, 2018, at 4:34 PM, =
Asmus Freytag &lt;<a href=3D"mailto:asmusf@ix.netcom.com" =
class=3D"">asmusf@ix.netcom.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">
 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-8" class=3D"">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
    <div class=3D"moz-cite-prefix">On 10/8/2018 12:58 PM, John C Klensin
      wrote:<br class=3D"">
    </div>
    <blockquote type=3D"cite" cite=3D"mid:B0BA40527CB85EC369DD812D@PSB" =
class=3D"">
      <pre class=3D"moz-quote-pre" wrap=3D"">--On Monday, October 8, =
2018 09:06 -0700 Ted Hardie
<a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:ted.ietf@gmail.com">&lt;ted.ietf@gmail.com&gt;</a> wrote:

</pre>
      <blockquote type=3D"cite" class=3D"">
        <pre class=3D"moz-quote-pre" wrap=3D"">Modulo Erik's comments, I =
think this is ready for publication.
The instructions to IANA are clear and the rationale behind
those instructions is laid out.

I think we could ask for AD-sponsorship for this, but I also
believe that the instructions could go to IANA now; at the
very least, we could ask them to review.
</pre>
      </blockquote>
      <pre class=3D"moz-quote-pre" wrap=3D"">Ted,

I'm sorry, but I disagree.  Patrik has, as far as I can tell,
done the job that the IAB asked him to do in his liaison
capacity to Unicode, </pre>
    </blockquote><p class=3D"">I thought this draft was in Patrik's role =
as the designated
      expert for the IANA registry. <br =
class=3D""></p></div></div></blockquote><div><br class=3D""></div><div =
class=3D"">That was also my impression. In March, the IAB said that =
=E2=80=9CThe IAB believes that the best current course of action for now =
is to bring the two [Unicode and the IDNA parameters registry] back into =
alignment while the IETF continues to work toward consensus on the =
underlying issues. &nbsp;We have therefore asked the expert reviewer to =
bring the IDNA Parameters registry up to date=E2=80=A6=E2=80=9D The =
draft (I thought) is documenting the expert's examination of code points =
that had been added or had properties change in the course of that =
update, and the rationale for his recommendation about how to handle =
them in the registry.</div><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D""><p class=3D"">
    </p>
    <blockquote type=3D"cite" cite=3D"mid:B0BA40527CB85EC369DD812D@PSB" =
class=3D"">
      <pre class=3D"moz-quote-pre" wrap=3D"">but that job involves a =
number of
assumptions about how to proceed that interact with i18n
documents that the IETF has been unable to process.  If we
follow the precedent of RFC 6452, this document should be
processed as standards track even if it changes nothing. </pre>
    </blockquote><p class=3D"">The relevant difference is that RFC 6452 =
contained this section:</p><p class=3D"">-------------------</p><p =
class=3D"">IETF Consensus<br class=3D"">
      <br class=3D"">
      &nbsp;&nbsp; No change to RFC 5892 is needed based on the changes =
made in<br class=3D"">
      &nbsp;&nbsp; Unicode 6.0.<br class=3D"">
      <br class=3D"">
      &nbsp;&nbsp; This consensus does not imply that no changes will be =
made to<br class=3D"">
      &nbsp;&nbsp; RFC 5892 for all future updates of The Unicode =
Standard.<br class=3D"">
      <br class=3D"">
      &nbsp;&nbsp; This RFC has been produced because 6.0 is the first =
version of<br class=3D"">
      &nbsp;&nbsp; Unicode to be released since IDNA2008 was =
published.<br class=3D"">
      --------------------<br class=3D"">
    </p><p class=3D"">I see no particular reason why such a section =
couldn't be added<br class=3D"">
      to Patrik's draft, allowing it to be processed like 6452 if that
      is<br class=3D"">
      felt to be more appropriate.</p><div class=3D""><br =
class=3D""></div></div></div></blockquote>I think that having an RFC for =
this set of updates, documenting the rationale for the decision to =
update the registry to Unicode 11 without exceptions for the code points =
that changed properties, will be valuable for the future=E2=80=94 but =
AFAICT it=E2=80=99s not strictly necessary as part of the action Patrik =
was asked to take. I=E2=80=99m fine with adding language as Asmus is =
suggesting, which clarifies the current reasoning without restricting =
future decisions inappropriately.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div text=3D"#000000" bgcolor=3D"#FFFFFF" =
class=3D"">
    <blockquote type=3D"cite" cite=3D"mid:B0BA40527CB85EC369DD812D@PSB" =
class=3D"">
      <pre class=3D"moz-quote-pre" wrap=3D""> It
would be wildly inappropriate for it to constrain the
conclusions the IETF could reach about those other documents.</pre>
    </blockquote><p class=3D"">I don't see how this would constrain IETF =
conclusions about other
      documents,<br class=3D"">
      or even RFC 5892 itself (other than that the consensus is to not
      add exceptions).</p><p class=3D"">There are changes that may be =
motivated by the general aspects of
      the interaction<br class=3D"">
      between Unicode and IDNA, but the kind of language as quoted above
      would not<br class=3D"">
      rule those out.<br class=3D"">
    </p><p class=3D"">You would need to make a more concrete claim how =
processing this
      RFC<br class=3D"">
      interferes with the work of IETF.
    </p></div></div></blockquote><div>I admit I don=E2=80=99t see this =
either.&nbsp;</div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
    <blockquote type=3D"cite" cite=3D"mid:B0BA40527CB85EC369DD812D@PSB" =
class=3D"">
      <pre class=3D"moz-quote-pre" wrap=3D"">My understanding coming out =
of the BOF at IETF 102 was that the
ART ADs were going to establish a directorate to determine how
i18n documents were to be handled and to start processing those
documents.  This document would make an entirely reasonable
addition to that directorate's queue.   However, if an progress
has been made on creating that directorate, much less having it
convene and discuss processing of documents, I seem to have
missed the announcement(s).</pre>
    </blockquote><p class=3D"">I don't necessarily see the plan for a =
new directorate as
      suspending IETFs<br class=3D"">
      ability to process certain RFCs indefinitely. The goal was to make
      it possible<br class=3D"">
      to process more of them and more consistently, not to provide an
      additional<br class=3D"">
      hurdle.</p><div class=3D""><br =
class=3D""></div></div></div></blockquote>At this point, I see three =
separate issues, any two of which have some interaction, but I don=E2=80=99=
t see hard dependencies:</div></div><div><br class=3D""></div><div>1. =
Updating the IDN parameters registry as the IAB requested. With =
apologies if I=E2=80=99m missing something, I don=E2=80=99t see the =
expert saying he can=E2=80=99t update the registry for some reason, or =
that there=E2=80=99s any ambiguity in what the update should be; it=E2=80=99=
s his judgment that =E2=80=9Cthe right thing to do=E2=80=9D about the =
code points that changed properties between Unicode 6.3 and Unicode 11 =
is consistent with what the standard tells him to do. So for the current =
situation, the standard, including the instructions to the expert, is =
adequate.</div><div><br class=3D""></div><div>2. Having an RFC about the =
specifics of updating the registry to Unicode 11. I agree with Patrik =
that having this document is useful, as an example of how to apply =
IDNA2008 to changes in Unicode; at the very least, the reasoning can =
inform future experts. But I see it as Informational=E2=80=94 a service =
to the community=E2=80=94 not as a change to the registry policy or an =
extension to the protocol standard. I don=E2=80=99t see a problem with =
making it AD-sponsored.</div><div><br class=3D""></div><div>3. =
Establishing the proposed I18N directorate. I strongly agree that the =
IETF needs the directorate, or some other mechanism for reviewing i18n =
aspects of work across the IETF and providing backup for expert review =
as needed. But that=E2=80=99s also an optimization, to improve future =
handling of i18n documents.</div><div><br class=3D""></div><div>I think =
all three of these things are important and useful. But it doesn=E2=80=99t=
 look to me like any of the necessary decisions for these three items =
are gating on the others, or constraining the options for the others. =
They can be done more or less in parallel.</div><div><br =
class=3D""></div><div><br class=3D""></div><div><br =
class=3D""></div><div>Suzanne</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_5D157C11-501B-4360-8C4D-C00EB6498B98--


From nobody Mon Oct  8 21:37:40 2018
Return-Path: <paf@netnod.se>
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 39EDC13101B for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 21:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netnod-se.20150623.gappssmtp.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 zlOjkuEKliI5 for <art@ietfa.amsl.com>; Mon,  8 Oct 2018 21:37:30 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 5384C131119 for <art@ietf.org>; Mon,  8 Oct 2018 21:37:27 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id m80-v6so160668lfi.12 for <art@ietf.org>; Mon, 08 Oct 2018 21:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netnod-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hJXJ4oXKdH227sXYqU+dXtp0fU9MN9ZDqdEbIpVG2dU=; b=1mLqHXQPVQ5O3F8tByaCs6/nd7ckHbXGTc+CXmjZo+WPgfXcp7cy3oMQ6j04LY49qa PKUMILAXDpXoOp2GM859UDGipIXZr28jgn1XrBpSATV0Vhnvp/KQZfbB8/mEw+pozsL2 rYqmtCi+3NAuQYqE9TY5vP+F6ACQCEkEanMumM3sLuLVZEuSARIQugt24oNmF0/YVCjH dErtUTjX/mDV+ByHeV4eHe2Ytq0U7A+IZcbO3hCOepA1MSv2fGuH2/XBWXVSN8y5Mjht GhuNm64oyxxvhiHakHGX9PLDEgQmIgiE4qvZ01VmQGoGopbfkJnsZd9pBnp+YYTMH/pk fXsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hJXJ4oXKdH227sXYqU+dXtp0fU9MN9ZDqdEbIpVG2dU=; b=B734wQyC2ZDZMnBTZQ+nvttSZuvKnQQbfl769/tyQGssm9m8lha2Fe1QOKC3AKsCU0 Wnn5Q4DSoyhg6ogl15UolUEX1FY1VmbKp/tHoSgDezi8Vh4yMAozbu/fRxMDvSgk4mE+ JnL86yxBhFzp14vSpEvkwLFofog+v59MKdSWBI2X1qMGZ0rDp9ZKVSV87qxC9TS1/fPK Oc1+AmRhcnYn8rGdw5veWec54mDmwFM7usuPipwFoKe7OZwoNWlXFifK80Hrm3rrfkzn XyN1s1ew7VZi2I3iTgyBXq5AbttF3l0FdtQMuj44Kkgh/AwjjKkXWPY0l/JGqEYfwv4R SrMA==
X-Gm-Message-State: ABuFfojl/DSfDDXpzTPFoegbhgQt5OeQ89G2NwSVnVmfAnSIn87Ux3Yq OlclPAv2lXRe+0c3DiEc9OfcoQ==
X-Google-Smtp-Source: ACcGV61rnxPmXYz5/7yngwvVKq6gZa95XX89LcQ4lPFIW75RSD439t0lI37bQssnt28XFZ85ZgvjAA==
X-Received: by 2002:a19:6719:: with SMTP id b25-v6mr14120037lfc.54.1539059845161;  Mon, 08 Oct 2018 21:37:25 -0700 (PDT)
Received: from [192.168.10.104] (c-40b2d954.028-114-73746f27.bbcust.telenor.se. [84.217.178.64]) by smtp.gmail.com with ESMTPSA id l9-v6sm3766786ljb.70.2018.10.08.21.37.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Oct 2018 21:37:24 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@netnod.se>
X-Mailer: iPad Mail (16B5059d)
In-Reply-To: <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com>
Date: Tue, 9 Oct 2018 06:37:23 +0200
Cc: Asmus Freytag <asmusf@ix.netcom.com>, John C Klensin <john-ietf@jck.com>, Ted Hardie <ted.ietf@gmail.com>, i18nrp@ietf.org, nordmark@acm.org, idna-update@ietf.org, Applications and Real-Time Area Discussion <art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com> <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/FNfOn6-qzRt1YzV2zn9BwJ41SBU>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 04:37:32 -0000

> On 9 Oct 2018, at 05:29, Suzanne Woolf <suzworldwide@gmail.com> wrote:
>=20
> 1. Updating the IDN parameters registry as the IAB requested. With apologi=
es if I=E2=80=99m missing something, I don=E2=80=99t see the expert saying h=
e can=E2=80=99t update the registry for some reason, or that there=E2=80=99s=
 any ambiguity in what the update should be; it=E2=80=99s his judgment that =E2=
=80=9Cthe right thing to do=E2=80=9D about the code points that changed prop=
erties between Unicode 6.3 and Unicode 11 is consistent with what the standa=
rd tells him to do. So for the current situation, the standard, including th=
e instructions to the expert, is adequate.

The key thing here is that I do not see myself have the competence in actual=
ly ensuring what I propose in the I-D is the correct thing to do. There are o=
ther alternatives as well, such as adding an exception to the IDNA2008 rule s=
et.

IAB asked me to bring things forward, and my call is what I call path A:
A.1. Suggest a path forward
A.2. Ask IETF to ensure what I propose is the right thing.

This is btw what was done last time we had an incompatible change like this.=


Alternatives could have been:

B. Be passive:
B.1. I ask IETF what to do with the incompatible changes (but do not suggest=
 anything)
B.2. IETF tell me what to do

C. Have IAB make the call
C.1. IAB tell me not only to move things forward, but also =E2=80=9CIAB have=
 decided that the changes made in Unicode do not require backward compatible=
 rules in IDNA2008=E2=80=9D
C.2. I move things forward based on B.1.

FWIW, I did not interpret what IAB told me was =E2=80=9CC=E2=80=9D which I r=
ead in your note Suz. Maybe I misunderstand you.

Now, IF IAB really told me C, then can you please clarify?

   Patrik


From nobody Mon Oct  8 22:37:10 2018
Return-Path: <asmusf@ix.netcom.com>
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 531B6131166; Mon,  8 Oct 2018 22:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.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 c2UBn-2TKmYN; Mon,  8 Oct 2018 22:37:05 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (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 B089413115A; Mon,  8 Oct 2018 22:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1539063425; bh=8K7LOVMZY93sl1Ifyfqp1fO8WfS5m/GouxKO 5ZRCMaE=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=bkNYQfQH3tVhw9nvx/GWWah/BmtV3B+kk RJltmZF/RPA5EjUflhnHvijpc+oIa/Xg6d/p6BuI1WQHT/p7E78B75ojTn/KoVAG1qK l40uMBTXPaaB5HGHrRR7iJri9m8Xn7n2ptnZvyoBBlJgrYkDyEE83KXI4nGF4h0oYs4 a/q3kRRAdM7Fs8h8w9UlYN85zSxPeUcSwcopuSTCMB6/HUPHuVUaz86i/wB1wCPwe7/ ZdLSuu4toyJqKfeuDICd/CO+6rPU3Pumio9WM7VUgCZtc6mR5ZGj4ojPLoOaZhijmhw TWNq6iETcnzngGIXlC3iwyp1anuboZ8N2+3cpaLuA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=e1TGXEmWtqwTFwAdatUbuINH/2CTgXeNr8FWVInO7W371+pUddmhg2LVXWhLwfA6OyvEiea8pjRUv50aBTO85tlU7yvP5KawCBynn3jTwVP2xT1V1G+PmweJxlHUE9SJ2FQHPe/zFU6uScs11T0HLWNZf2FLXoI6GzkaNgK7tzpWsquauPyjHIYsPzVQPahEyysIxb0Js0QOuH3+p+aAAst3da7hrJYi11er4H1Sy0o4rvE8t4gmbKGNmiD1XXlJAvq1nOKhlRJayNORJvqGRjm+3Mo9DFs6CFjwaiT2T0w4IuGxpZTrglNz2DkQpZDCvk8NreeTftCAp0rUutYVsg==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [174.21.170.119] (helo=[192.168.1.108]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <asmusf@ix.netcom.com>) id 1g9khY-0005kh-OO; Tue, 09 Oct 2018 01:37:01 -0400
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>, Suzanne Woolf <suzworldwide@gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, i18nrp@ietf.org, nordmark@acm.org, Applications and Real-Time Area Discussion <art@ietf.org>, John C Klensin <john-ietf@jck.com>, idna-update@ietf.org
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com> <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com> <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
From: "Asmus Freytag (c)" <asmusf@ix.netcom.com>
Message-ID: <e102f061-81a3-e8fd-7f9b-58bb5ee9d907@ix.netcom.com>
Date: Mon, 8 Oct 2018 22:37:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
Content-Type: multipart/alternative; boundary="------------62972A07847AA92503EFA7F8"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b7eec10b52094b3e949cfd12a8bd0aa53155b74982b4360f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 174.21.170.119
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/RqE0Sw6yoogfT0ZEsbFCXpfShps>
Subject: Re: [art] [Idna-update] [I18nrp] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 05:37:09 -0000

This is a multi-part message in MIME format.
--------------62972A07847AA92503EFA7F8
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 10/8/2018 9:37 PM, Patrik Fältström wrote:
>
>> On 9 Oct 2018, at 05:29, Suzanne Woolf <suzworldwide@gmail.com> wrote:
>>
>> 1. Updating the IDN parameters registry as the IAB requested. With apologies if I’m missing something, I don’t see the expert saying he can’t update the registry for some reason, or that there’s any ambiguity in what the update should be; it’s his judgment that “the right thing to do” about the code points that changed properties between Unicode 6.3 and Unicode 11 is consistent with what the standard tells him to do. So for the current situation, the standard, including the instructions to the expert, is adequate.
> The key thing here is that I do not see myself have the competence in actually ensuring what I propose in the I-D is the correct thing to do. There are other alternatives as well, such as adding an exception to the IDNA2008 rule set.
>
> IAB asked me to bring things forward, and my call is what I call path A:
> A.1. Suggest a path forward
> A.2. Ask IETF to ensure what I propose is the right thing.
>
> This is btw what was done last time we had an incompatible change like this.

Sounds like a good approach in any case.

 From where I sit, what you did looks fine, so my answer to A.2. would 
be affirmative.

A./

PS: if IAB agrees with your assessment re: rules, the more the better.

>
> Alternatives could have been:
>
> B. Be passive:
> B.1. I ask IETF what to do with the incompatible changes (but do not suggest anything)
> B.2. IETF tell me what to do
>
> C. Have IAB make the call
> C.1. IAB tell me not only to move things forward, but also “IAB have decided that the changes made in Unicode do not require backward compatible rules in IDNA2008”
> C.2. I move things forward based on B.1.
>
> FWIW, I did not interpret what IAB told me was “C” which I read in your note Suz. Maybe I misunderstand you.
>
> Now, IF IAB really told me C, then can you please clarify?
>
>     Patrik
>
> _______________________________________________
> IDNA-UPDATE mailing list
> IDNA-UPDATE@ietf.org
> https://www.ietf.org/mailman/listinfo/idna-update



--------------62972A07847AA92503EFA7F8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 10/8/2018 9:37 PM, Patrik Fältström
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">On 9 Oct 2018, at 05:29, Suzanne Woolf <a class="moz-txt-link-rfc2396E" href="mailto:suzworldwide@gmail.com">&lt;suzworldwide@gmail.com&gt;</a> wrote:

1. Updating the IDN parameters registry as the IAB requested. With apologies if I’m missing something, I don’t see the expert saying he can’t update the registry for some reason, or that there’s any ambiguity in what the update should be; it’s his judgment that “the right thing to do” about the code points that changed properties between Unicode 6.3 and Unicode 11 is consistent with what the standard tells him to do. So for the current situation, the standard, including the instructions to the expert, is adequate.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
The key thing here is that I do not see myself have the competence in actually ensuring what I propose in the I-D is the correct thing to do. There are other alternatives as well, such as adding an exception to the IDNA2008 rule set.

IAB asked me to bring things forward, and my call is what I call path A:
A.1. Suggest a path forward
A.2. Ask IETF to ensure what I propose is the right thing.

This is btw what was done last time we had an incompatible change like this.</pre>
    </blockquote>
    <p>Sounds like a good approach in any case.</p>
    <p>From where I sit, what you did looks fine, so my answer to A.2.
      would be affirmative.</p>
    <p>A./</p>
    <p>PS: if IAB agrees with your assessment re: rules, the more the
      better.<br>
    </p>
    <blockquote type="cite"
      cite="mid:3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se">
      <pre class="moz-quote-pre" wrap="">

Alternatives could have been:

B. Be passive:
B.1. I ask IETF what to do with the incompatible changes (but do not suggest anything)
B.2. IETF tell me what to do

C. Have IAB make the call
C.1. IAB tell me not only to move things forward, but also “IAB have decided that the changes made in Unicode do not require backward compatible rules in IDNA2008”
C.2. I move things forward based on B.1.

FWIW, I did not interpret what IAB told me was “C” which I read in your note Suz. Maybe I misunderstand you.

Now, IF IAB really told me C, then can you please clarify?

   Patrik

_______________________________________________
IDNA-UPDATE mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IDNA-UPDATE@ietf.org">IDNA-UPDATE@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/idna-update">https://www.ietf.org/mailman/listinfo/idna-update</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------62972A07847AA92503EFA7F8--


From nobody Mon Oct  8 22:41:04 2018
Return-Path: <yaojk@cnnic.cn>
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 58D3C131153; Mon,  8 Oct 2018 22:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 CWDKDYYrCc61; Mon,  8 Oct 2018 22:41:01 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4D27613114E; Mon,  8 Oct 2018 22:40:58 -0700 (PDT)
Received: from healthyao-PC (unknown [218.241.103.187]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0AZIPxYP7xbNcUdAA--.22364S2;  Tue, 09 Oct 2018 13:40:40 +0800 (CST)
Date: Tue, 9 Oct 2018 13:40:34 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: suzworldwide <suzworldwide@gmail.com>,  "Asmus Freytag" <asmusf@ix.netcom.com>
Cc: "Ted Hardie" <ted.ietf@gmail.com>, i18nrp <i18nrp@ietf.org>,  nordmark <nordmark@acm.org>,  =?utf-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>,  "Applications and Real-Time Area Discussion" <art@ietf.org>,  "John C Klensin" <john-ietf@jck.com>, idna-update <idna-update@ietf.org>
Reply-To: yaojk <yaojk@cnnic.cn>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com>,  <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2018100913393087166197@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart710151255258_=----"
X-CM-TRANSID: AQAAf0AZIPxYP7xbNcUdAA--.22364S2
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUYh7k0a2IF6FyUM7kC6x804xWl14x267AK xVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26ryj 6F1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4j6F4UM28EF7xvwVC2z280aVAFwI0_Cr 1j6rxdM28EF7xvwVC2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv 0487Mc02F40E42I26xC2a48xMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxV WUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0E w4CEw7xC0wCY02Avz4vE14v_GrWl42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr 0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY 17CE14v26r1q6r43MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcV C0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF 0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_Gr1l6VACY4xI67 k04243AbIYCTnIWIevJa73UjIFyTuYvjxU2eOJDUUUU
X-CM-SenderInfo: x1dryyw6fq0xffof0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/RbEwRP1nAUvjAuaLsLR8blJvx6M>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 05:41:03 -0000

This is a multi-part message in MIME format.

------=_001_NextPart710151255258_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkZyb206IFN1emFubmUgV29vbGYNCkRhdGU6IDIwMTgtMTAtMDkgMTE6MjkNClRvOiBBc211
cyBGcmV5dGFnDQpDQzogVGVkIEhhcmRpZTsgaTE4bnJwOyBub3JkbWFyazsgUGF0cmlrIEbDpGx0
c3Ryw7ZtOyBBcHBsaWNhdGlvbnMgYW5kIFJlYWwtVGltZSBBcmVhIERpc2N1c3Npb247IEpvaG4g
QyBLbGVuc2luOyBpZG5hLXVwZGF0ZQ0KU3ViamVjdDogUmU6IFthcnRdIFtJMThucnBdIFtJZG5h
LXVwZGF0ZV0gQ29tbWVudHMgb24gZHJhZnQtZmFsdHN0cm9tLXVuaWNvZGUxMS0wMg0KPiBUaGF0
IHdhcyBhbHNvIG15IGltcHJlc3Npb24uIEluIE1hcmNoLCB0aGUgSUFCIHNhaWQgdGhhdCDigJxU
aGUgSUFCIGJlbGlldmVzIHRoYXQgdGhlIGJlc3QgY3VycmVudCBjb3Vyc2Ugb2YgYWN0aW9uIGZv
ciBub3cgaXMgdG8gYnJpbmcgdGhlIHR3byBbVW5pY29kZSBhbmQgdGhlIElETkEgcGFyYW1ldGVy
cyByZWdpc3RyeV0gYmFjayBpbnRvIGFsaWdubWVudCANCltKaWFua2FuZyBZYW9dID4NCj4g

------=_001_NextPart710151255258_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20181009133629483464 {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; WORD-WRAP: break-word; COLOR: #00=
0000; FONT-SIZE: 10.5pt; 20307: ; -WEBKIT-NBSP-MODE: SPACE
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; COLOR: #000000; FONT-SIZE: 10.5pt=
; 20307:=20
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16684"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV><SPAN></SPAN></DIV></DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:suzworldwide@gmail.com">Suzanne=20
Woolf</A></DIV>
<DIV><B>Date:</B>&nbsp;2018-10-09&nbsp;11:29</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:asmusf@ix.netcom.com">Asmus=20
Freytag</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:ted.ietf@gmail.com">Ted Hardie</A>;=
 <A=20
href=3D"mailto:i18nrp@ietf.org">i18nrp</A>; <A=20
href=3D"mailto:nordmark@acm.org">nordmark</A>; <A=20
href=3D"mailto:paf@netnod.se">Patrik F=C3=A4ltstr=C3=B6m</A>; <A=20
href=3D"mailto:art@ietf.org">Applications and Real-Time Area Discussion</A=
>; <A=20
href=3D"mailto:john-ietf@jck.com">John C Klensin</A>; <A=20
href=3D"mailto:idna-update@ietf.org">idna-update</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [art] [I18nrp] [Idna-update] Comments on=20
draft-faltstrom-unicode11-02</DIV></DIV></DIV>
<DIV>
<DIV class=3DFoxDiv20181009133629483464>
<DIV>
<DIV>
<DIV type=3D"cite">
<DIV bgcolor=3D"#FFFFFF" text=3D"#000000">
<P><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
&gt;&nbsp;</FONT></SPAN>That=20
was also my impression. In March, the IAB said that =E2=80=9CThe IAB belie=
ves that the=20
best current course of action for now is to bring the two [Unicode and the=
 IDNA=20
parameters registry] back into alignment <BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;&gt;<BR>&gt;&nbsp;</FONT></SPAN></P></DIV></DIV></DIV></DIV>=
</DIV></DIV></BODY></HTML>

------=_001_NextPart710151255258_=------



From nobody Mon Oct  8 22:52:21 2018
Return-Path: <yaojk@cnnic.cn>
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 CB64F13115A; Mon,  8 Oct 2018 22:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 onAG7kbBflMS; Mon,  8 Oct 2018 22:52:11 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0098913114E; Mon,  8 Oct 2018 22:52:08 -0700 (PDT)
Received: from healthyao-PC (unknown [218.241.103.187]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0Dp8Px_QbxbgMUdAA--.21958S2;  Tue, 09 Oct 2018 13:49:51 +0800 (CST)
Date: Tue, 9 Oct 2018 13:49:45 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: suzworldwide <suzworldwide@gmail.com>,  "Asmus Freytag" <asmusf@ix.netcom.com>
Cc: "Ted Hardie" <ted.ietf@gmail.com>, i18nrp <i18nrp@ietf.org>,  nordmark <nordmark@acm.org>,  =?utf-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@netnod.se>,  "Applications and Real-Time Area Discussion" <art@ietf.org>,  "John C Klensin" <john-ietf@jck.com>, idna-update <idna-update@ietf.org>
Reply-To: yaojk <yaojk@cnnic.cn>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com>,  <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com>,  <2018100913393087166197@cnnic.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <20181009134942726001101@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart463408531813_=----"
X-CM-TRANSID: AQAAf0Dp8Px_QbxbgMUdAA--.21958S2
X-Coremail-Antispam: 1UD129KBjvdXoWrJw4DZFy5Zw4kJw18GFWxJFb_yoWxXrbEgr 4kKrW0ya1DJF43WwsFyan8XFn29r45ua10qwsFkr4Ygr1vqFs8Xw4ktry7Zw1jgFyft34Y gr98GrsxKryUXjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbfkYjsxI4VWDJwAYFVCjjxCrM7AC8VAFwI0_Gr0_Xr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVW8JVW5JwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVW8JVWxJwA2z4x0Y4vEx4A2jsIE14v26F4UJVW0owA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG6xAIxVCF xsxG0wAv7VC0I7IYx2IY67AKxVWUGVWUXwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFV Cjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lc7CjxVAa w2AFwI0_Jw0_GFylc2xSY4AK67AK6r4rMxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4 AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE 17CEb7AF67AKxVWUtVW8ZwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMI IF0xvE2Ix0cI8IcVCY1x0267AKxVW8JVWxJwCI42IY6xAIw20EY4v20xvaj40_Wr1j6rW3 Jr1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVW8JVW8Jr1l6V ACY4xI67k04243AbIYCTnIWIevJa73UjIFyTuYvjxUwlksUUUUU
X-CM-SenderInfo: x1dryyw6fq0xffof0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/jSPmLxTv4ad2eibZEk6hvHaNY2U>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 05:52:14 -0000

This is a multi-part message in MIME format.

------=_001_NextPart463408531813_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQpGcm9tOiBTdXphbm5lIFdvb2xmDQpEYXRlOiAyMDE4LTEwLTA5IDExOjI5DQpUbzogQXNtdXMg
RnJleXRhZw0KQ0M6IFRlZCBIYXJkaWU7IGkxOG5ycDsgbm9yZG1hcms7IFBhdHJpayBGw6RsdHN0
csO2bTsgQXBwbGljYXRpb25zIGFuZCBSZWFsLVRpbWUgQXJlYSBEaXNjdXNzaW9uOyBKb2huIEMg
S2xlbnNpbjsgaWRuYS11cGRhdGUNClN1YmplY3Q6IFJlOiBbYXJ0XSBbSTE4bnJwXSBbSWRuYS11
cGRhdGVdIENvbW1lbnRzIG9uIGRyYWZ0LWZhbHRzdHJvbS11bmljb2RlMTEtMDINCj4gVGhhdCB3
YXMgYWxzbyBteSBpbXByZXNzaW9uLiBJbiBNYXJjaCwgdGhlIElBQiBzYWlkIHRoYXQg4oCcVGhl
IElBQiBiZWxpZXZlcyB0aGF0IHRoZSBiZXN0IGN1cnJlbnQgY291cnNlIG9mIGFjdGlvbiBmb3Ig
bm93IGlzIHRvIGJyaW5nIHRoZSB0d28gW1VuaWNvZGUgYW5kIHRoZSBJRE5BIHBhcmFtZXRlcnMg
cmVnaXN0cnldIGJhY2sgaW50byBhbGlnbm1lbnQgDQogPg0KDQpJIHRoaW5rIHRoYXQgIGhhdmlu
ZyBhIGdvb2QgZGVzaWduIHJlZ2lzdHJ5IG9mIFtVbmljb2RlIGFuZCB0aGUgSUROQSBwYXJhbWV0
ZXJzIHJlZ2lzdHJ5XSBpcyBhIGdvb2QgaWRlYS4NCg0KQmVzdCBSZWdhcmRzDQpKaWFua2FuZyBZ
YW8=

------=_001_NextPart463408531813_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20181009133629483464 {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; WORD-WRAP: break-word; COLOR: #00=
0000; FONT-SIZE: 10.5pt; 20307: ; -WEBKIT-NBSP-MODE: SPACE
}
DIV.FoxDiv20181009134051544743 {
	LINE-HEIGHT: 1.5; MARGIN: 10px; FONT-FAMILY: &#23435; COLOR: #000000; FON=
T-SIZE: 10.5pt; 20307:=20
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; COLOR: #000000; FONT-SIZE: 10.5pt=
; 20307:=20
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16684">
<STYLE>BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18487"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>&nbsp;</DIV>
<DIV>
<DIV class=3DFoxDiv20181009134051544743>
<DIV>
<DIV><SPAN></SPAN></DIV></DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:suzworldwide@gmail.com">Suzanne=20
Woolf</A></DIV>
<DIV><B>Date:</B>&nbsp;2018-10-09&nbsp;11:29</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:asmusf@ix.netcom.com">Asmus=20
Freytag</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:ted.ietf@gmail.com">Ted Hardie</A>;=
 <A=20
href=3D"mailto:i18nrp@ietf.org">i18nrp</A>; <A=20
href=3D"mailto:nordmark@acm.org">nordmark</A>; <A=20
href=3D"mailto:paf@netnod.se">Patrik F=C3=A4ltstr=C3=B6m</A>; <A=20
href=3D"mailto:art@ietf.org">Applications and Real-Time Area Discussion</A=
>; <A=20
href=3D"mailto:john-ietf@jck.com">John C Klensin</A>; <A=20
href=3D"mailto:idna-update@ietf.org">idna-update</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [art] [I18nrp] [Idna-update] Comments on=20
draft-faltstrom-unicode11-02</DIV></DIV></DIV>
<DIV>
<DIV class=3DFoxDiv20181009133629483464>
<DIV>
<DIV>
<DIV type=3D"cite">
<DIV text=3D"#000000" bgcolor=3D"#FFFFFF">
<P><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
&gt;&nbsp;</FONT></SPAN>That=20
was also my impression. In March, the IAB said that =E2=80=9CThe IAB belie=
ves that the=20
best current course of action for now is to bring the two [Unicode and the=
 IDNA=20
parameters registry] back into alignment&nbsp;<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
&nbsp;&gt;<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<BR>I=20
think that &nbsp;having a good design registry of <FONT color=3D#000000>[U=
nicode=20
and the IDNA parameters registry]&nbsp;is a good idea.<BR><BR>Best=20
Regards<BR>Jiankang=20
Yao</FONT></FONT></SPAN></FONT></SPAN></P></DIV></DIV></DIV></DIV></DIV></=
DIV></DIV></DIV></BODY></HTML>

------=_001_NextPart463408531813_=------



From nobody Tue Oct  9 00:11:02 2018
Return-Path: <john-ietf@jck.com>
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 51EB71311C0; Tue,  9 Oct 2018 00:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 77LHvZheeMqI; Tue,  9 Oct 2018 00:10:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB481311AF; Tue,  9 Oct 2018 00:10:58 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1g9mAP-000MN6-1w; Tue, 09 Oct 2018 03:10:53 -0400
Date: Tue, 09 Oct 2018 03:10:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@netnod.se>, Suzanne Woolf <suzworldwide@gmail.com>
cc: Asmus Freytag <asmusf@ix.netcom.com>, Ted Hardie <ted.ietf@gmail.com>, i18nrp@ietf.org, nordmark@acm.org, idna-update@ietf.org, Applications and Real-Time Area Discussion <art@ietf.org>
Message-ID: <86A3FF7AA13985AFD134554D@PSB>
In-Reply-To: <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com> <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com> <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/0HCB2KAA7rwaxsSUpOTwZGN-QCo>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 07:11:00 -0000

Suzanne, Ted,

Let me build on Patrik's clarification to explain what I'm
concerned about (some other issues have been raised that I'll
come back to later).   I had read Ted's comment about
AD-sponsorship and IANA as implying something close to Patrik's
"C", i.e., the IAB decides it has the authority to just move
forward with this.  I think that would be a bad idea for the
reasons below.   But Ted said he was suggesting only asking
IANA's opinion as to whether the instructions to them were
sufficient and doing so in parallel with starting to advance the
document.   I don't see any problem with that; it would
certainly be consistent with other comments I've made lately
about working together informally to get things done rather than
getting tied up in procedures, throwing things over virtual
walls, and figuring out how and when to do that.

My concern was precisely about heading down the path to Patrik's
"C".  I think what we have learned in the last few years is that
things are more complicated -- and complicated in ways that
affect IDNA (and, btw, PRECIS) -- than the community assumed
when IDNA2008 was adopted.  Those complications include, but are
not just about, the issues that started out with the "Hamza"
discussion that prompted the original IAB statement on that
subject and evolved into what some of us have called the
non-decomposing precomposed character issue.  They also include
some of the issues Asmus has identified about complex scripts
and the requirements they impose as well as, e.g., issues of
registry responsibility and accountability (not only from
IDNA2008 but going back to RFC 1591 and earlier) and other
topics that may be in need of clarification and/or more serious
attention.

If we are either going to change or clarify IDNA2008 to address
those issues or decide to push ahead without addressing them at
all (which, itself, would change or clarify IDNA2008), I think
that must be an IETF consensus position, not done on the basis
of the IAB declaring what it believes (something the IAB is
certainly entitled to do).

best,
    john




--On Tuesday, October 9, 2018 06:37 +0200 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@netnod.se> wrote:

>=20
>=20
>> On 9 Oct 2018, at 05:29, Suzanne Woolf
>> <suzworldwide@gmail.com> wrote:
>>=20
>> 1. Updating the IDN parameters registry as the IAB requested.
>> With apologies if I'm missing something, I don't see the
>> expert saying he can't update the registry for some reason,
>> or that there's any ambiguity in what the update should be;
>> it's his judgment that "the right thing to do" about
>> the code points that changed properties between Unicode 6.3
>> and Unicode 11 is consistent with what the standard tells him
>> to do. So for the current situation, the standard, including
>> the instructions to the expert, is adequate.
>=20
> The key thing here is that I do not see myself have the
> competence in actually ensuring what I propose in the I-D is
> the correct thing to do. There are other alternatives as well,
> such as adding an exception to the IDNA2008 rule set.
>=20
> IAB asked me to bring things forward, and my call is what I
> call path A: A.1. Suggest a path forward
> A.2. Ask IETF to ensure what I propose is the right thing.
>=20
> This is btw what was done last time we had an incompatible
> change like this.
>=20
> Alternatives could have been:
>=20
> B. Be passive:
> B.1. I ask IETF what to do with the incompatible changes (but
> do not suggest anything) B.2. IETF tell me what to do
>=20
> C. Have IAB make the call
> C.1. IAB tell me not only to move things forward, but also
> "IAB have decided that the changes made in Unicode do not
> require backward compatible rules in IDNA2008" C.2. I move
> things forward based on B.1.
>=20
> FWIW, I did not interpret what IAB told me was "C" which I
> read in your note Suz. Maybe I misunderstand you.
>=20
> Now, IF IAB really told me C, then can you please clarify?
>=20
>    Patrik
>=20





From nobody Tue Oct  9 10:59:18 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
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 0CFAD127AC2; Tue,  9 Oct 2018 10:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 AD7aQUmQZN7v; Tue,  9 Oct 2018 10:59:12 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 A58BE1274D0; Tue,  9 Oct 2018 10:59:12 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id g15-v6so1034872ybf.6; Tue, 09 Oct 2018 10:59:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FMsCJOx/VoPHjmSQyV9tIy1RkzwhX+Qxw0SoLAT68Ds=; b=n32Xg0KyQBBUkHqI5kcqi2Ca55WdcWUJPxKjwMytx3LXtYcOA7lIIruicMMOn+Fsym 0+ZzU8E5Lx12yyOnnHOgshyF/hzTr8i1KxugTxTVl+d7pUYy8YuY4C3olx9XaBm2IWWD 9HelA23dRY6O2QkyL5AraF4WQNdeylsKNC/NUfx3ogLqDCwxVM7AKcl/XP16fYhatcat A5Aiv1H1t8k0L9A2xLZB3jZsO6oewUEzzqIF/Xh3gLNJR9xNJbRPrUfuXXvrocvtyNJg WS+Rjcn2sM+33gRu7h4r+vPPOHINNgFgicc+jxTR4fwERm2SASGhUEN1Myig3lqhWYau da7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FMsCJOx/VoPHjmSQyV9tIy1RkzwhX+Qxw0SoLAT68Ds=; b=sCGL1TN+gyJ0czzwxeQqe1zfYpS4Nh30XS/aTBDwOnXru/CEDryIw925mD3JY8Ax+E bqgzy3obbB4rD1soQ3y1eoW69FZx0PvH/sR6QJtcWnoMnInuxaoQMAgEeU6syfPkba32 agv0ObltKQc+tqS7C0UxOgJJwRAUDnjofo2nE5ltqmi3TkJnL8th1yGQ5dpik/EBZBcp 6RWjU9ZdP8LBvJ1S7rw/GYG9IHUCx6//rSgBge1dCrTYS84egNA+z+ixFL+IrAIIaXJ6 jmFw48bMRI9Wie3LqAxISINK1doxOVOR9DrBjC3QNAHEuA5fKmZtWTDBeP3/xBI+u20Z BEHg==
X-Gm-Message-State: ABuFfoj96ddvTidDus96CwWtlKGVQEa0Qo7JaVJxNhtNF2TaYvd28SaE EHV9HP2FAMRWuQo4ZKMNDfwba7/I6BlTCVSo3Vc=
X-Google-Smtp-Source: ACcGV63yKAgMIvmcqb2CSe8+K64gkXrPgi0CyZUjqjE2sBbnWo0m+Se8bkqUpr7CjGwI9s5wNUZXeNMo0+tECGYZL2g=
X-Received: by 2002:a25:cc4:: with SMTP id 187-v6mr16039312ybm.490.1539107951640;  Tue, 09 Oct 2018 10:59:11 -0700 (PDT)
MIME-Version: 1.0
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com> <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com> <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se> <86A3FF7AA13985AFD134554D@PSB>
In-Reply-To: <86A3FF7AA13985AFD134554D@PSB>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 9 Oct 2018 12:59:00 -0500
Message-ID: <CAKKJt-cf0aNpwbeHNbSa80VJMCYXK45DYwhXTuK53XuP3jES6A@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: paf@netnod.se, Suzanne Woolf <suzworldwide@gmail.com>, Ted Hardie <ted.ietf@gmail.com>,  asmusf@ix.netcom.com, i18nrp@ietf.org, nordmark@acm.org, art@ietf.org,  idna-update@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ba84cd0577cf7eeb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/TuP88pl1mn0Ze1b9lg5in-QdXiY>
Subject: Re: [art] [I18nrp] [Idna-update] Comments on draft-faltstrom-unicode11-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 17:59:16 -0000

--000000000000ba84cd0577cf7eeb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Posting from far outside the level of expertise I'd hope to find in the
archives for this mailing list, but on one particular point.

On Tue, Oct 9, 2018 at 2:11 AM John C Klensin <john-ietf@jck.com> wrote:

> Suzanne, Ted,
>
> Let me build on Patrik's clarification to explain what I'm
> concerned about (some other issues have been raised that I'll
> come back to later).   I had read Ted's comment about
> AD-sponsorship and IANA as implying something close to Patrik's
> "C", i.e., the IAB decides it has the authority to just move
> forward with this.  I think that would be a bad idea for the
> reasons below.   But Ted said he was suggesting only asking
> IANA's opinion as to whether the instructions to them were
> sufficient and doing so in parallel with starting to advance the
> document.   I don't see any problem with that; it would
> certainly be consistent with other comments I've made lately
> about working together informally to get things done rather than
> getting tied up in procedures, throwing things over virtual
> walls, and figuring out how and when to do that.
>

As an AD, I've had more problems when I asked for feedback on schedule and
could reasonably have asked for early feedback, than I've had when asking
for early feedback. I don't have a lot of experience with complex IANA
instructions, but even then, we've asked IANA their opinions a few times,
early in the process.

I'll leave it to others to determine what the right answer is in this
specific case, but I hope John is right.

Spencer


> My concern was precisely about heading down the path to Patrik's
> "C".  I think what we have learned in the last few years is that
> things are more complicated -- and complicated in ways that
> affect IDNA (and, btw, PRECIS) -- than the community assumed
> when IDNA2008 was adopted.  Those complications include, but are
> not just about, the issues that started out with the "Hamza"
> discussion that prompted the original IAB statement on that
> subject and evolved into what some of us have called the
> non-decomposing precomposed character issue.  They also include
> some of the issues Asmus has identified about complex scripts
> and the requirements they impose as well as, e.g., issues of
> registry responsibility and accountability (not only from
> IDNA2008 but going back to RFC 1591 and earlier) and other
> topics that may be in need of clarification and/or more serious
> attention.
>
> If we are either going to change or clarify IDNA2008 to address
> those issues or decide to push ahead without addressing them at
> all (which, itself, would change or clarify IDNA2008), I think
> that must be an IETF consensus position, not done on the basis
> of the IAB declaring what it believes (something the IAB is
> certainly entitled to do).
>
> best,
>     john
>
>
>
>
> --On Tuesday, October 9, 2018 06:37 +0200 Patrik F=C3=A4ltstr=C3=B6m
> <paf@netnod.se> wrote:
>
> >
> >
> >> On 9 Oct 2018, at 05:29, Suzanne Woolf
> >> <suzworldwide@gmail.com> wrote:
> >>
> >> 1. Updating the IDN parameters registry as the IAB requested.
> >> With apologies if I'm missing something, I don't see the
> >> expert saying he can't update the registry for some reason,
> >> or that there's any ambiguity in what the update should be;
> >> it's his judgment that "the right thing to do" about
> >> the code points that changed properties between Unicode 6.3
> >> and Unicode 11 is consistent with what the standard tells him
> >> to do. So for the current situation, the standard, including
> >> the instructions to the expert, is adequate.
> >
> > The key thing here is that I do not see myself have the
> > competence in actually ensuring what I propose in the I-D is
> > the correct thing to do. There are other alternatives as well,
> > such as adding an exception to the IDNA2008 rule set.
> >
> > IAB asked me to bring things forward, and my call is what I
> > call path A: A.1. Suggest a path forward
> > A.2. Ask IETF to ensure what I propose is the right thing.
> >
> > This is btw what was done last time we had an incompatible
> > change like this.
> >
> > Alternatives could have been:
> >
> > B. Be passive:
> > B.1. I ask IETF what to do with the incompatible changes (but
> > do not suggest anything) B.2. IETF tell me what to do
> >
> > C. Have IAB make the call
> > C.1. IAB tell me not only to move things forward, but also
> > "IAB have decided that the changes made in Unicode do not
> > require backward compatible rules in IDNA2008" C.2. I move
> > things forward based on B.1.
> >
> > FWIW, I did not interpret what IAB told me was "C" which I
> > read in your note Suz. Maybe I misunderstand you.
> >
> > Now, IF IAB really told me C, then can you please clarify?
> >
> >    Patrik
> >
>
>
>
>
> _______________________________________________
> i18nRP mailing list
> i18nRP@ietf.org
> https://www.ietf.org/mailman/listinfo/i18nrp
>

--000000000000ba84cd0577cf7eeb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Posting from far outside the level of expertise I&#39;d ho=
pe to find in the archives for this mailing list, but on one particular poi=
nt.<div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 9, 2018=
 at 2:11 AM John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com">john-ie=
tf@jck.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Suzanne,=
 Ted,<br>
<br>
Let me build on Patrik&#39;s clarification to explain what I&#39;m<br>
concerned about (some other issues have been raised that I&#39;ll<br>
come back to later).=C2=A0 =C2=A0I had read Ted&#39;s comment about<br>
AD-sponsorship and IANA as implying something close to Patrik&#39;s<br>
&quot;C&quot;, i.e., the IAB decides it has the authority to just move<br>
forward with this.=C2=A0 I think that would be a bad idea for the<br>
reasons below.=C2=A0 =C2=A0But Ted said he was suggesting only asking<br>
IANA&#39;s opinion as to whether the instructions to them were<br>
sufficient and doing so in parallel with starting to advance the<br>
document.=C2=A0 =C2=A0I don&#39;t see any problem with that; it would<br>
certainly be consistent with other comments I&#39;ve made lately<br>
about working together informally to get things done rather than<br>
getting tied up in procedures, throwing things over virtual<br>
walls, and figuring out how and when to do that.<br></blockquote><div><br><=
/div><div>As an AD, I&#39;ve had more problems when I asked for feedback on=
 schedule and could reasonably have asked for early feedback, than I&#39;ve=
 had when asking for early feedback. I don&#39;t have a lot of experience w=
ith complex IANA instructions, but even then, we&#39;ve asked IANA their op=
inions a few times, early in the process.</div><div><br></div><div>I&#39;ll=
 leave it to others to determine what the right answer is in this specific =
case, but I hope John is right.</div><div><br></div><div>Spencer</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">My concern was precisely about h=
eading down the path to Patrik&#39;s<br>
&quot;C&quot;.=C2=A0 I think what we have learned in the last few years is =
that<br>
things are more complicated -- and complicated in ways that<br>
affect IDNA (and, btw, PRECIS) -- than the community assumed<br>
when IDNA2008 was adopted.=C2=A0 Those complications include, but are<br>
not just about, the issues that started out with the &quot;Hamza&quot;<br>
discussion that prompted the original IAB statement on that<br>
subject and evolved into what some of us have called the<br>
non-decomposing precomposed character issue.=C2=A0 They also include<br>
some of the issues Asmus has identified about complex scripts<br>
and the requirements they impose as well as, e.g., issues of<br>
registry responsibility and accountability (not only from<br>
IDNA2008 but going back to RFC 1591 and earlier) and other<br>
topics that may be in need of clarification and/or more serious<br>
attention.<br>
<br>
If we are either going to change or clarify IDNA2008 to address<br>
those issues or decide to push ahead without addressing them at<br>
all (which, itself, would change or clarify IDNA2008), I think<br>
that must be an IETF consensus position, not done on the basis<br>
of the IAB declaring what it believes (something the IAB is<br>
certainly entitled to do).<br>
<br>
best,<br>
=C2=A0 =C2=A0 john<br>
<br>
<br>
<br>
<br>
--On Tuesday, October 9, 2018 06:37 +0200 Patrik F=C3=A4ltstr=C3=B6m<br>
&lt;<a href=3D"mailto:paf@netnod.se" target=3D"_blank">paf@netnod.se</a>&gt=
; wrote:<br>
<br>
&gt; <br>
&gt; <br>
&gt;&gt; On 9 Oct 2018, at 05:29, Suzanne Woolf<br>
&gt;&gt; &lt;<a href=3D"mailto:suzworldwide@gmail.com" target=3D"_blank">su=
zworldwide@gmail.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; 1. Updating the IDN parameters registry as the IAB requested.<br>
&gt;&gt; With apologies if I&#39;m missing something, I don&#39;t see the<b=
r>
&gt;&gt; expert saying he can&#39;t update the registry for some reason,<br=
>
&gt;&gt; or that there&#39;s any ambiguity in what the update should be;<br=
>
&gt;&gt; it&#39;s his judgment that &quot;the right thing to do&quot; about=
<br>
&gt;&gt; the code points that changed properties between Unicode 6.3<br>
&gt;&gt; and Unicode 11 is consistent with what the standard tells him<br>
&gt;&gt; to do. So for the current situation, the standard, including<br>
&gt;&gt; the instructions to the expert, is adequate.<br>
&gt; <br>
&gt; The key thing here is that I do not see myself have the<br>
&gt; competence in actually ensuring what I propose in the I-D is<br>
&gt; the correct thing to do. There are other alternatives as well,<br>
&gt; such as adding an exception to the IDNA2008 rule set.<br>
&gt; <br>
&gt; IAB asked me to bring things forward, and my call is what I<br>
&gt; call path A: A.1. Suggest a path forward<br>
&gt; A.2. Ask IETF to ensure what I propose is the right thing.<br>
&gt; <br>
&gt; This is btw what was done last time we had an incompatible<br>
&gt; change like this.<br>
&gt; <br>
&gt; Alternatives could have been:<br>
&gt; <br>
&gt; B. Be passive:<br>
&gt; B.1. I ask IETF what to do with the incompatible changes (but<br>
&gt; do not suggest anything) B.2. IETF tell me what to do<br>
&gt; <br>
&gt; C. Have IAB make the call<br>
&gt; C.1. IAB tell me not only to move things forward, but also<br>
&gt; &quot;IAB have decided that the changes made in Unicode do not<br>
&gt; require backward compatible rules in IDNA2008&quot; C.2. I move<br>
&gt; things forward based on B.1.<br>
&gt; <br>
&gt; FWIW, I did not interpret what IAB told me was &quot;C&quot; which I<b=
r>
&gt; read in your note Suz. Maybe I misunderstand you.<br>
&gt; <br>
&gt; Now, IF IAB really told me C, then can you please clarify?<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Patrik<br>
&gt; <br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
i18nRP mailing list<br>
<a href=3D"mailto:i18nRP@ietf.org" target=3D"_blank">i18nRP@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/i18nrp" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/i18nrp</a><br>
</blockquote></div></div></div>

--000000000000ba84cd0577cf7eeb--


From nobody Wed Oct 10 08:48:36 2018
Return-Path: <mary.ietf.barnes@gmail.com>
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 4DC3D130F91; Wed, 10 Oct 2018 08:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 hdujqIo_DHEm; Wed, 10 Oct 2018 08:48:22 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 BEBDB130F72; Wed, 10 Oct 2018 08:48:21 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id y71-v6so5353840lje.9; Wed, 10 Oct 2018 08:48:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WMhWO6b5tfRecFVJMoG2nOZ3AuN+gSXdR/IoYHhqIB4=; b=So/O0JpPJphqdwQQfkS8emCUtm8lKQh+NFwhC2pMPOhpQFqqrn/yxe16BDeetR4h8g ofVNFbMyxZGEm8CJfY01sD5u4OJBhkCy9U0zd1+7JxBq/hYoxmB3MTOg7QA9oBI1H/yy tgd90+zoEJOtDu5XZ59JkQ71X+IjSs5ey2t4P1IQoV+s8BzfHK9K0A9PVE1I81JW5HEb HhwwnqlEBDuaHNFTzhCMEfu+2ZU3B8GHmTQqDmUvUARX1oYUqt994rXXdXyYPQZrdQSg DVWO8lJjY5KoO6ukep/SD2ghiqQfex+UjY8DnYHlEHQGAJgcDOUx70IAzd4iPxNqy/p8 boYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMhWO6b5tfRecFVJMoG2nOZ3AuN+gSXdR/IoYHhqIB4=; b=jkRHjFnif1r7yq0Bir77vaDgrhF++G2PcpContBpxoBv+mUmpHe4wc9lmcT1zby2J8 cnRG6VTtAaR0qHsRlDKbRsrBHobejSZzRMqSG/BeGQcyBerx7+fjuD/rJxmW6sxPMy7M 4tBLeJOycpb/J+vvW+/hyTrdqqGHuvKv7tKsG275c3+FrdExazmsS3oSdYp7gNTwgbSR fXkUe9eopF0M/1ETaDQTpLxijNrJ8NX+2Urbu+ro6QijpA/GCyUHTQig7d1wbRJoaU+s DjjjKL90/9bQTZTHhULeWdhM+VSABSgLtVNQiGg8EZGURW3RiDbwL4ZdkemdxDPfSxgn VXkA==
X-Gm-Message-State: ABuFfoj+EA75DUFzlbtQ5A55vFsJ9Ufzp4b7+R7QrkthEdrKs/XQ7dfF 4QL8mf37T4A2ZnVp7ZmhuMKfOOrJXQew+S4VpvGk6w==
X-Google-Smtp-Source: ACcGV63bgGDsMgOipRXApW/d1VFnEIDmdiCjUFYdpgsyrJS6piJTvOq8qXFxobW5K+HeGM31gD6jKl2nvv6zpW+YgNs=
X-Received: by 2002:a2e:5b17:: with SMTP id p23-v6mr21102333ljb.91.1539186499461;  Wed, 10 Oct 2018 08:48:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5MeKQMKkFL2GpP5S7Nj+hz52Gc4-c+SzfwJSmf+r9B1A@mail.gmail.com>
In-Reply-To: <CAHBDyN5MeKQMKkFL2GpP5S7Nj+hz52Gc4-c+SzfwJSmf+r9B1A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Wed, 10 Oct 2018 10:48:07 -0500
Message-ID: <CAHBDyN4dAoL_833Hi5ve8x9txUrcdeogxLmLieCNn5tdtOH=Bw@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>, IETF ART Mailing List <art@ietf.org>
Cc: ART ADs <art-ads@ietf.org>, dispatch chairs <dispatch-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008b29720577e1c81d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/WNMY9hLAiVwQhs7zHe7NFDYhhJw>
Subject: Re: [art] Reminder: DISPATCH WG deadlines for IETF-103
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 15:48:27 -0000

--0000000000008b29720577e1c81d
Content-Type: text/plain; charset="UTF-8"

Hi all,

Folks might have noticed that DISPATCH did not get the usual Monday morning
slot due to a conflict with SECDISPATCH. We only received one request for a
5-10 min slot that we decided could be discussed in another WG.    So,
unless someone brings a solid topic forward by CoB on Friday, October 12th,
we will be canceling the DISPATCH WG/ART area session for IETF-103.  And,
if you think you submitted something that we missed, please let us know
ASAP.

Regards,
Mary
On behalf of DISPATCH WG chairs and ART ADs

On Mon, Sep 10, 2018 at 12:32 PM Mary Barnes <mary.ietf.barnes@gmail.com>
wrote:

> As a reminder the deadlines for the DISPATCH WG for IETF-103 are as
> follows:
>
>    - September 21, 2018. Cutoff date for IETF BoF submissions.
>
>
>    - September 28, 2018. Cutoff date to notify the chairs/DISPATCH WG of
>    plans to submit a proposal.
>
>
>    - October 5, 2018. Cutoff for charter proposals (i.e., problem
>    statement and proposed deliverables) for topics posted to the DISPATCH WG
>    mailing list.
>
>
>    - October 12, 2018. Announcement of topics that have been dispatched
>    for IETF-103
>
>
>    - October 22, 2018. Draft submission deadline.
>
>
> If you have a topic that you think might require an official BoF, please
> contact the ADs ASAP.
>
> Additional information on the DISPATCH WG process can be found here (along
> with the deadlines):
> https://trac.ietf.org/trac/dispatch/wiki/WikiStart
>
> Regards,
> Mary Barnes
> DISPATCH WG tri-chair
>
>

--0000000000008b29720577e1c81d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>Folks might have noticed that D=
ISPATCH did not get the usual Monday morning slot due to a conflict with SE=
CDISPATCH. We only received one request for a 5-10 min slot that we decided=
 could be discussed in another WG.=C2=A0 =C2=A0 So, unless someone brings a=
 solid topic forward by CoB on Friday, October 12th, we will be canceling t=
he DISPATCH WG/ART area session for IETF-103.=C2=A0 And,=C2=A0 if you think=
 you submitted something that we missed, please let us know ASAP.=C2=A0=C2=
=A0</div><div><br></div><div>Regards,</div><div>Mary</div><div>On behalf of=
 DISPATCH WG chairs and ART ADs</div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr">On Mon, Sep 10, 2018 at 12:32 PM Mary Barnes &lt;<a href=3D"mailt=
o:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">As a reminder the dea=
dlines for the DISPATCH WG for IETF-103 are as follows:<ul style=3D"color:r=
gb(0,0,0);font-family:Verdana,Arial,&quot;Bitstream Vera Sans&quot;,Helveti=
ca,sans-serif;text-decoration-style:initial;text-decoration-color:initial">=
<li>September 21, 2018. Cutoff date for IETF BoF submissions.</li></ul><ul =
style=3D"color:rgb(0,0,0);font-family:Verdana,Arial,&quot;Bitstream Vera Sa=
ns&quot;,Helvetica,sans-serif;text-decoration-style:initial;text-decoration=
-color:initial"><li>September 28, 2018. Cutoff date to notify the chairs/DI=
SPATCH WG of plans to submit a proposal.</li></ul><ul style=3D"color:rgb(0,=
0,0);font-family:Verdana,Arial,&quot;Bitstream Vera Sans&quot;,Helvetica,sa=
ns-serif;text-decoration-style:initial;text-decoration-color:initial"><li>O=
ctober 5, 2018. Cutoff for charter proposals (i.e., problem statement and p=
roposed deliverables) for topics posted to the DISPATCH WG mailing list.</l=
i></ul><ul style=3D"color:rgb(0,0,0);font-family:Verdana,Arial,&quot;Bitstr=
eam Vera Sans&quot;,Helvetica,sans-serif;text-decoration-style:initial;text=
-decoration-color:initial"><li>October 12, 2018. Announcement of topics tha=
t have been dispatched for IETF-103=C2=A0</li></ul><ul style=3D"color:rgb(0=
,0,0);font-family:Verdana,Arial,&quot;Bitstream Vera Sans&quot;,Helvetica,s=
ans-serif;text-decoration-style:initial;text-decoration-color:initial"><li>=
October 22, 2018. Draft submission deadline.</li></ul><div><br></div><div>I=
f you have a topic that you think might require an official BoF, please con=
tact the ADs ASAP.</div><div><br></div><div>Additional information on the D=
ISPATCH WG process can be found here (along with the deadlines):=C2=A0</div=
><div><a href=3D"https://trac.ietf.org/trac/dispatch/wiki/WikiStart" target=
=3D"_blank">https://trac.ietf.org/trac/dispatch/wiki/WikiStart</a><br></div=
><div><br></div><div>Regards,</div><div>Mary Barnes</div><div>DISPATCH WG t=
ri-chair</div><div><br></div></div>
</blockquote></div></div>

--0000000000008b29720577e1c81d--


From nobody Wed Oct 10 12:02:55 2018
Return-Path: <Shawn.Steele@microsoft.com>
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 A308212426A for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 12:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 NHXuhsBzcXwo for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 12:02:50 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720115.outbound.protection.outlook.com [40.107.72.115]) (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 D72F9130DDC for <art@ietf.org>; Wed, 10 Oct 2018 12:02:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+oj1haNtYlqnbCzjIa6M8UggXdEycjlyYFY3cyM/d3o=; b=kR/9XecnELMyd9V1hDmE07eJegRkaaDecWiAdXu52eWXa6RrFWw1ndR0HI0y9kl7oDKJDrjmCbaJ9U4icRdtIB5m8RSWBiEwYrsMDUN91aWUfsBCE/zqB5WfpX/I2DsinH/m/hHyhaPFVCcgD1rwnCAx/fZkZf7HLKLyMKBH0rA=
Received: from MW2PR2101MB0908.namprd21.prod.outlook.com (52.132.152.28) by MW2PR2101MB1034.namprd21.prod.outlook.com (52.132.149.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.6; Wed, 10 Oct 2018 19:02:30 +0000
Received: from MW2PR2101MB0908.namprd21.prod.outlook.com ([fe80::c5c5:865d:9a44:6c89]) by MW2PR2101MB0908.namprd21.prod.outlook.com ([fe80::c5c5:865d:9a44:6c89%4]) with mapi id 15.20.1228.011; Wed, 10 Oct 2018 19:02:30 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "art@ietf.org" <art@ietf.org>
Thread-Topic: Use Unicode if Using Unicode?
Thread-Index: AdRgyyu11+nsTlEOSXCvakwfGZPatw==
Date: Wed, 10 Oct 2018 19:02:29 +0000
Message-ID: <MW2PR2101MB0908F009734817997508274282E00@MW2PR2101MB0908.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=shawnste@microsoft.com;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-10-10T19:02:27.5540360Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8:9:952d:e41c:285c:8696]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MW2PR2101MB1034; 6:Hs3EmF6e1b31YJIqxVjQ61amqIdcZ5MczuH1AziwKVV1YU7IQusm5qo5Q+Il+/c+EiSNY0ByLoaWuewZpCZhoDhVdjQAP7BpOGHSqxkfy2HfHoQ4PRb39eDnhtwqyGUX8Dquo8tLymce3H9TYWFebNRVA0DiCELKikb8brfARYyGtVl0u1fcKVuZx4m0ngLNSM2//I3Kch7iOhPuBm8hMVSNHXkgayYGNvoGxfYBWvPKCQypT+399UUswFyXO/Mewbvk7Zbq8O7NfSrNBYFRMgX5ZQ7z5PBFIFJridibfc/r89VpJeFpNsON7lSmoLFmdOeaxOcaUGKKg9ytFfyX8fsoLEb6i8QjM5sH9kHmgU4ZWpSqNibDtAYylYCMw+3KzOl1DcY7f7p6Q5+j88BD4JHNJUxHvAB29fV2SGYVVvwQo//f2SiP+36GVX0Y42jkEKDesugGsNPY3toIuVFt2w==; 5:HqcdcZw95qMkTHJfw8g6fy1DZQbOUiGkDKMruUUcWlf0RLT0DaWx+ra6zp2UW16/VEfg3JdubAMBuTCGQNMMDUTKmDHCj4BbMsT9VyTnq5WCyXRTOSsScIvex0woaQPGD2vS5mxzTv+wWRmrAWCVHinT//6ytlc6Ql3W2S8kWBs=; 7:FheWqihmGysXUBRpHqYD+hEHYfC/0Q3VgbjnpKGhHPCTpAhT4BwNpLNnQgHRc2JypaTgd3x74qwz8K3LNT0wSOyQEY1R0C0Vg8EHTdA/zkE7EicAT6JOpxCply4Vlt2d7sz5+YW6JW7BLID0BUSLIVm6uuJi/k0cCIYoTCav8uddkc/54TfUVgoWRciGRo7mxKElonEWUvehsaAnlbkcB9Ijs6nWgrENCRD5O7vKLEYmO5KeuUhAk7QznLKh2ZnP
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: eb835b56-8090-4540-6c21-08d62ee2ed73
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:MW2PR2101MB1034; 
x-ms-traffictypediagnostic: MW2PR2101MB1034:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Shawn.Steele@microsoft.com; 
x-microsoft-antispam-prvs: <MW2PR2101MB103495BF5897F00D5BC4D46882E00@MW2PR2101MB1034.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3231355)(944501410)(52105095)(2018427008)(3002001)(6055026)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(201708071742011)(7699051)(76991055); SRVR:MW2PR2101MB1034; BCL:0; PCL:0; RULEID:; SRVR:MW2PR2101MB1034; 
x-forefront-prvs: 08213D42D3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(396003)(39860400002)(346002)(376002)(189003)(199004)(105586002)(5640700003)(486006)(6116002)(8990500004)(46003)(256004)(22452003)(6506007)(14444005)(86612001)(10290500003)(186003)(5660300001)(72206003)(7736002)(7696005)(86362001)(68736007)(476003)(6436002)(25786009)(102836004)(305945005)(10090500001)(6916009)(55016002)(71190400001)(71200400001)(2351001)(74316002)(33656002)(99286004)(8676002)(478600001)(316002)(9686003)(2906002)(81166006)(2900100001)(14454004)(81156014)(5250100002)(1730700003)(53936002)(97736004)(8936002)(106356001)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:MW2PR2101MB1034; H:MW2PR2101MB0908.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: DFMhkBeMKEUAMZBBm7oGmejKq2/RZc5/6udX/wpfF8X5iBxz3Lc6YFxSi0v+s7ISiiJqIsnlh79RAh6eqmGmTHHgBd6TEryxWfqAgyV8rw//GyCWz4aL4m1Ws6wZ5xL0IAHUI0R49jo3+hVf9ePIYdDHiDfpLIdFVwyZ37iUKmvXrXv2tJo8dVhg2ix27N1g4cZTcLu4TB7nJ5SDn5QOKwa65hUhd+E7y6xjDpO1+Oz5hVrkuT45O4jGufUG5rA9vCyYvxT7eXZ2TUv2O0DHylp2kFrOPGGCNg0MDc7h7k7IY6hND8MEBtsFcsOpDZ4zAhkGeh470YKR6zXTHaNKVgtNXRJOec6VT0Eq+mvcRSU=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: eb835b56-8090-4540-6c21-08d62ee2ed73
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2018 19:02:29.9973 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR2101MB1034
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-DiPOuMMb_unJxyn4jezpd96DPg>
Subject: [art] Use Unicode if Using Unicode?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 19:02:53 -0000

VGhlIGRyYWZ0IHN0YXRlcyAiSXQgZnVydGhlciBzdWdnZXN0cyBmb3IgdGhlIElFVEYgYSBwYXRo
IGZvcndhcmQgcmVnYXJkaW5nIGVuc3VyaW5nIElETkEyMDA4IGZvbGxvd3MgdGhlIGV2b2x1dGlv
biBvZiB0aGUgVW5pY29kZSBTdGFuZGFyZCIgYW5kICJ0aGlzIGRvY3VtZW50IHJlcXVlc3RzIHRo
YXQgSUFOQSB1cGRhdGUgdGhlIHRhYmxlcyB0byBVbmljb2RlIDExLiINCg0KRWFjaCBVbmljb2Rl
IHZlcnNpb24gY3JlYXRlcyBhIGRhdGEgZmlsZSB3aXRoIGluZm9ybWF0aW9uIGZyb20gYXBwbHlp
bmcgdGhlIElETkEyMDA4IHJ1bGVzIHRoYXQgY2FuIGJlIHVzZWQgZm9yIElETkEgbWFwcGluZyBh
bGdvcml0aG1zLiAgKEluZGVlZCwgdGhhdCdzIHdoZXJlIFdpbmRvd3MgZ2V0cyB0aGUgZGF0YSBm
cm9tKS4gDQoNCklmIHRoZSBnb2FsIGlzIHRvICJmb2xsb3cgdGhlIGV2b2x1dGlvbiBvZiB0aGUg
VW5pY29kZSBTdGFuZGFyZCIgYW5kIHRoZSBVbmljb2RlIFN0YW5kYXJkIGlzIHByb3ZpZGluZyBk
YXRhIHRoYXQgY29uZm9ybXMgdG8gdGhlIElETkEgcnVsZXMsIHRoZW4gd2h5IG5vdCBqdXN0IHBv
aW50IGRpcmVjdGx5IHRvIHRoZSBVbmljb2RlIGRlcml2ZWQgdGFibGVzPw0KDQotU2hhd24NCg0K


From nobody Wed Oct 10 12:13:11 2018
Return-Path: <g.e.montenegro@hotmail.com>
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 B0ED21274D0; Wed, 10 Oct 2018 12:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 Wbt8xpm0PhL4; Wed, 10 Oct 2018 12:12:59 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-oln040092006048.outbound.protection.outlook.com [40.92.6.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59135120072; Wed, 10 Oct 2018 12:12:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Uz4OMoCEPTaqOi7TuzQtTJPa6R7kIUSn63y4BBlJX4E=; b=WtlW/MkjV1r0IU3RgNZX46daEP2uwpu5IPJ3SD6YiusglYkWg1iqwiC/GWypTzB+JGOZ16B/5CBUx7BZPzAQF9weixwDOgwRNxQHiYpIJIk0p4VtUhxoygvPb/jjsy3M6AibMbVSru12Bazj14qLxCvFrwvexGc2Pxz0ODjVKclVRoef0EbmpH12m6cf/hCdlqCT7g24ia9iPYJw4Zt5M1DSv8ptUoVF20f4PBs6+0FdzOS0Lu/2Ks+gYXUHMM2HEMiYlfUCFJq2SqUcWoUW3SVygBLpFP9tK+/+FMh+f6EJ5+3BeW3BIkij3qS0DSP4BtkEeCP3mYCbAaVIicMzow==
Received: from CO1NAM03FT003.eop-NAM03.prod.protection.outlook.com (10.152.80.51) by CO1NAM03HT098.eop-NAM03.prod.protection.outlook.com (10.152.80.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Wed, 10 Oct 2018 19:12:58 +0000
Received: from YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM (10.152.80.60) by CO1NAM03FT003.mail.protection.outlook.com (10.152.80.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Wed, 10 Oct 2018 19:12:58 +0000
Received: from YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM ([fe80::dd70:501b:3a67:ff27]) by YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM ([fe80::dd70:501b:3a67:ff27%5]) with mapi id 15.20.1228.020; Wed, 10 Oct 2018 19:12:58 +0000
From: Gabriel Montenegro <g.e.montenegro@hotmail.com>
To: "paf@netnod.se" <paf@netnod.se>, "art@ietf.org" <art@ietf.org>, "i18nrp@ietf.org" <i18nrp@ietf.org>, "iab@iab.org" <iab@iab.org>
Thread-Topic: editorial comments on draft-faltstrom-unicode11-04.txt
Thread-Index: AdRgzRRbGdCsYtrrS7qD4SljMR14eQ==
Date: Wed, 10 Oct 2018 19:12:58 +0000
Message-ID: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:826DF2FA632A100D1A44F3E28E00731AB7512294044D6DFC0DDA1C0FA2D292C4; UpperCasedChecksum:59800285228ECD684C5CCA411CB983B15584301347E6088ADF10F4485BB7E627; SizeAsReceived:7143; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [D/dU4R7M/NRGsKpBj4qS6c8WYjmqfkLAC2ZK7MYuI6yTcMM3rCN5ANRoV+uYhMgw]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1NAM03HT098; 6:9osLz70zskOjxP1pcngj+dwOZwqyQE93htq+hUC0GLpMZYY/B0D5OflvQXv1p732UDv8227CgSzZnncVx+FoJKuu9ZJ1pBSOfgrKaGQHaTKpiNbl3DxlLfMM5Ou/TAKChGYZO8oNCsaR0C/JMm3NesPaMmXSIAPD14oB0YHnYawMV5f2I/pVmm223ThbOnoeJSEN9w9f/19E1lC3PCECxlAa0qEXZvFIrac4mLBqF5qnj5Bm5WGvO3Tw3JQt6heANEzHOiD4N5oIeyzrf3Ou+tjv/iuXN1h476zK5V+uJfQI5MMy6sI0kcnD4aWJSaIzBVy5p+8gbGSJzwSpIS+zP7m01FwtUaznJHd/98922lP9v3j5tMausFcfck1qyhQ3oz1Wy7NSCsrTr1qYJdOtKPwGb6aLp4v6ekTzaMfC92zyUVLY8hiJQltnx7twqOYEXcmrXTzjyattuRxK4Nh4lQ==; 5:ykH8aBONsFaqvoZR+Gchre+ihRX79FXGw4o71kUS29224rr61dpNB6gOprO9LL1wZ6DxRByjhrCitLn8awxyRwmQSNNfXOtbWtRbxtsmuyfj7HMoOTP9D80crHDDXZgnmIUjGY0RnYXG8D8bmxcuEH9bbYqQfkcNsuuIhrCNlDw=; 7:diZKPnzAK5gNxKcKpq/K0CHRDOhmtRg6MWEV4WpKlWEdfOGRVYgLGwmNpjnzqhqQPNqsYQ9CERCtHeQ53I88Ga0Sg0TpLx7o/X/oeo1N19iGWTSPe/3jv6qHgdJ3R7FSpSA618AcyttfNFZ91Q1ZJdTpDEZYoC62kDNzHKf8ZSVk3iiZAumX/IEu4nxlh5tABkHBJ5hT5QIk+zXAPO9FJshVyL2GOzgUJ+1TJpuYzbATj7QWiGMXjvasdTOLhyHf
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125500)(1603101475)(1701031045); SRVR:CO1NAM03HT098; 
x-ms-traffictypediagnostic: CO1NAM03HT098:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:CO1NAM03HT098; BCL:0; PCL:0; RULEID:; SRVR:CO1NAM03HT098; 
x-microsoft-antispam-message-info: th18bMvX9li+UpQ+kt12mfNjmn5OaaXHw99wICU8rpkT80zN71mfy3gx4JbU03mz
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-Network-Message-Id: 49fcc532-f42b-4c0f-c5ba-08d62ee463e6
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2018 19:12:58.1742 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM03HT098
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/XJDf9HFxPjqVWGAFaPFr4epwp9g>
Subject: [art] editorial comments on draft-faltstrom-unicode11-04.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 19:13:01 -0000

I looked at rev04 and have some editorial comments and nits. One such gener=
al comment is that there is a lack of commas in the text, which makes for d=
ifficult reading.

Abstract:

s/IDNA2008 do give/IDNA2008 gives/
s/document suggests/document suggest/

Introduction:

Points out that IDNA2008 "is specified in a series of documents (see Sectio=
n Section 3.1). " That still leaves unanswered what a reasonable overview i=
s for those of us who are absolute IDNA newbs. So may I suggest something l=
ike "is specified in a series of documents (see Section Section 3.1), but f=
or an overview see XXXX." [I suppose rfc5894 is the proper overview doc her=
e?]

Section 3.1:

s/DISSALOWED/DISALLOWED/
s/changes where acceptable/changes were acceptable/

Section 3.2:

s/implies stayed at Unicode Standard/implies staying at Unicode Standard/=20
[Here, I suppose it's staying, but "stayed" sounds wrong, please double-che=
ck.]

s/having a very diverse/having very diverse/

Can't parse: "that registry operators to based on the IDNA2008 specificatio=
n create additional rules...".=20
Perhaps you meant "that led registry operators to (based on the IDNA2008 sp=
ecification) create additional rules..."?

s/characters permissable/characters permissible /=20

section 4.3:

s/ZANABZAR/ZANABAZAR


Gabriel

> -----Original Message-----
> From: IAB <iab-bounces@iab.org> On Behalf Of Patrik F=E4ltstr=F6m
> Sent: 6 October, 2018 22:54
> To: i18nrp@ietf.org; iab@iab.org
> Subject: [IAB] draft-faltstrom-unicode11-04.txt
>=20
> All,
>=20
> Version -04 of this draft was just posted.
>=20
> Background: As we all know IDNA2008 is an algorithm that applied to Unico=
de
> gives a subset of code points which are permissible for in turn registrie=
s and
> others to create subsets from to be used in their respective policies.
>=20
> Being the appointed expert for the IANA registry I have flagged for IAB c=
hanges
> made to Unicode that I feel must be discussed in IETF, and here is the
> document with my proposal (details are in the draft).
>=20
> In short the draft proposes (just like RFC 6452) IETF continue to follow =
Unicode
> Standard without adding exceptions to the IDNA2008 algorithm, EVEN IF
> changes are made that are incompatible to earlier versions of Unicode.
>=20
> The choices for IETF when things like this happens are:
>=20
> 1. Keep IDNA2008 with no exceptions
>=20
> 2. Keep IDNA2008 with exceptions
>=20
> 3. Stop referring (directly) to Unicode as it is not stable enough
>=20
> Probably more choices than these...
>=20
> My proposal is [1], together with a more forceful push to strict IDNA2008
> adoption. No IDNA2003, no UTS#46, no homebrew mixes. Including that
> registries really do a careful conservative selection of code points to b=
e used in
> whatever context it is to be used.
>=20
>=20
> The problem though is that this is *my* view. Sure, a few others have
> randomly and "by pure luck" told me "this is ok".
>=20
> But is this a stable informed decision by IETF?
>=20
> This very fast turn into a process issue where IAB have asked for progres=
s, and
> IETF is to deliver.
>=20
> And this is where I take a step back, and want IESG and IAB to make up th=
eir
> mind. This group was created for I18N issues, we have a charter, but then
> what? Is this where drafts like these should be discussed?
>=20
> Maybe...
>=20
>    Patrik


From nobody Wed Oct 10 18:15:57 2018
Return-Path: <john-ietf@jck.com>
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 E9D47130DEA; Wed, 10 Oct 2018 18:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 yywl9sQnBIS9; Wed, 10 Oct 2018 18:15:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82EF7130DDC; Wed, 10 Oct 2018 18:15:47 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1gAPZn-0003eo-Nr; Wed, 10 Oct 2018 21:15:43 -0400
Date: Wed, 10 Oct 2018 21:15:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Gabriel Montenegro <g.e.montenegro@hotmail.com>
cc: paf@netnod.se, art@ietf.org, i18nrp@ietf.org, iab@iab.org
Message-ID: <A83D675604CE3DCFE1378DD2@PSB>
In-Reply-To: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
References: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ubieg-63BiT_flZKMWHUuMaZopY>
Subject: Re: [art] [I18nrp] editorial comments on draft-faltstrom-unicode11-04.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 01:15:49 -0000

I assume Patrik has not answered because, being sensible, he is
likely sleeping.  In the interest of saving a bit of time, I've
responded to the more substantive of your comments/questions
below...

--On Wednesday, October 10, 2018 19:12 +0000 Gabriel Montenegro
<g.e.montenegro@hotmail.com> wrote:

>...
> Points out that IDNA2008 "is specified in a series of
> documents (see Section Section 3.1). " That still leaves
> unanswered what a reasonable overview is for those of us who
> are absolute IDNA newbs. So may I suggest something like "is
> specified in a series of documents (see Section Section 3.1),
> but for an overview see XXXX." [I suppose rfc5894 is the
> proper overview doc here?]

Almost.  You will find that RFC 5894 is hard or impossible to
understand without some of the material in 5890, which I would
recommend at least looking through first.  The combination is
still not a tutorial.  There are several of those around, but,
unfortunately, a large fraction of them contain serious errors
or are, however unintentionally, a little misleading.  Some day,
some of us will have time.

>...
> Can't parse: "that registry operators to based on the IDNA2008
> specification create additional rules...".  Perhaps you meant
> "that led registry operators to (based on the IDNA2008
> specification) create additional rules..."?

You might find part of the note I posted earlier today (about
the same time as yours) helpful in regard to what is going on in
that section (although I agree that the current text in the I-D
needs work).

best,
   john



From nobody Wed Oct 10 19:01:12 2018
Return-Path: <john-ietf@jck.com>
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 49DE2130DFF; Wed, 10 Oct 2018 19:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 odI_SPfFzZZ2; Wed, 10 Oct 2018 19:01:07 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC4FA130DF9; Wed, 10 Oct 2018 19:01:06 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1gAQHh-0003ji-2a; Wed, 10 Oct 2018 22:01:05 -0400
Date: Wed, 10 Oct 2018 22:00:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org>, art@ietf.org,  i18nrp@ietf.org
Message-ID: <FB4FE0D631E6F6D4C72B19A1@PSB>
In-Reply-To: <MW2PR2101MB0908F009734817997508274282E00@MW2PR2101MB0908.namprd21.prod.outlook.com>
References: <MW2PR2101MB0908F009734817997508274282E00@MW2PR2101MB0908.namprd21.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/hnoGWgMhDF1yFl_9MmmG9qUUw80>
Subject: Re: [art] Use Unicode if Using Unicode?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 02:01:10 -0000

Shawn,

I'm confused about what you are suggesting, so let me clarify
where I'm confused and then hope you can enlighten me...

--On Wednesday, October 10, 2018 19:02 +0000 Shawn Steele
<Shawn.Steele=40microsoft.com@dmarc.ietf.org> wrote:

> The draft states "It further suggests for the IETF a path
> forward regarding ensuring IDNA2008 follows the evolution of
> the Unicode Standard" and "this document requests that IANA
> update the tables to Unicode 11."

> Each Unicode version creates a data file with information from
> applying the IDNA2008 rules that can be used for IDNA mapping
> algorithms.  (Indeed, that's where Windows gets the data
> from). 

Taking a half-step back, IDNA imposes two requirements for new
versions of Unicode, both of which are addressed by the present
draft.  One is that the changes in the new version be examined
to ensure that nothing new has been done that requires changes
to IDNA (most likely adding exceptions or rules for particular
code points) or careful explanation somewhere.  No one I know of
expected that provision would be exercised very often but, for a
variety of reasons, the consensus was that it was an important
safeguard.   The other was that the IDNA ruleset be run against
the characters and properties in the Unicode Character Database
to produce a table reflecting the combination of that version of
Unicode and IDNA, as modified, at that time.  That table was
(and is) to be stored with IANA but, while we expect it to be
checked carefully for accuracy, it is not actually authoritative
-- only the rules and categories specified by IDNA (and the
Unicode properties used to support them) are.

The discussion in RFC 5895 notwithstanding, one of the
critically important properties of IDNA2008 is that U-labels and
A-labels are duals: one can get from one to the other and back
without any loss of information.  That reversibility is true in
only some cases for Unicode normalization (especially with
compatibility normalization) or case folding, much less for
other mapping scenarios.  So I don't understand what sort of
"mapping" you are talking about.

The only Unicode-created IDN data files I'm aware of are those
associated with the UTS#46 effort.  Because UTS#46 makes
recommendations that are inconsistent with IDNA2008, if
Microsoft is using those tables, its usage is non-conforming to
IDNA2008.  I certainly cannot prevent Microsoft from doing that
(and wouldn't try), but it would certainly not be consistent
with general interoperability of IDNs or what is known elsewhere
as Universal Acceptance of those domain names.

> If the goal is to "follow the evolution of the Unicode
> Standard" and the Unicode Standard is providing data that
> conforms to the IDNA rules, then why not just point directly
> to the Unicode derived tables?

The simplest answer to your question is that, unless I've missed
something, the conditional is false: the Unicode Standard is not
providing data that conforms to the IDNA2008 rules.  Instead,
the data they are providing is more like one of the creative
IDNA2003-IDNA2008 hybrids to which Patrik refers.

   best,
     john


From nobody Wed Oct 10 19:14:36 2018
Return-Path: <pradeepan88@hotmail.com>
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 5DF51130DFD for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level: 
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 zQrUgVRoHC8b for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:14:33 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254092.outbound.protection.outlook.com [40.92.254.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F43B130DFB for <art@ietf.org>; Wed, 10 Oct 2018 19:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1SlBLS1B7FgJTenqLV73+2t7Eqfz/amjpjnTMjnVS5U=; b=keXs/cn3zGqL6mGYgaYmDAUoYMgQwrkI3ziQNXmajwZ+HlaGZH9CK7655g2D2o7Ld8kJJAOxCp8BJcDyapVAsX5PDeBJKLDT3IUi1+8vFHMs2+zHDzd7Rc5MgjzbkA3kS06Dn/qPvV+xNP1wB9/iypw45rboXsbU6x4jZu/DvIa2k0lRDiOc7MXdUWaTUso/xwtNw+jjbzARFiC+BLdbPSfCpgedhmglAYQdB5CBVFXYdGlJvybtjDZUIuY9hmnJuiiK9UcwE9mrzabxQeP5xfwlMgXyBdK7lVQ9G0wcL2y1VOajkHwf3QVRhsL5VhfSNovhcMFKHIZwJyKM7D4N5Q==
Received: from SG2APC01FT041.eop-APC01.prod.protection.outlook.com (10.152.250.54) by SG2APC01HT080.eop-APC01.prod.protection.outlook.com (10.152.251.239) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Thu, 11 Oct 2018 02:14:30 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.250.56) by SG2APC01FT041.mail.protection.outlook.com (10.152.251.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Thu, 11 Oct 2018 02:14:30 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995%4]) with mapi id 15.20.1228.020; Thu, 11 Oct 2018 02:14:30 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, "art@ietf.org" <art@ietf.org>
Thread-Topic: verify envelope and who is email
Thread-Index: AQHUYQcBgbYSN/G6lkuTGJWrzSYXxw==
Date: Thu, 11 Oct 2018 02:14:30 +0000
Message-ID: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:7AD2144476132A39C9BEBBD26847C143A6A82CD29709B1BC6A92F5E0BA66EE18; UpperCasedChecksum:11F82AF092E212AB55A0CDE494775E4A8617AF248E4BE9D0A100EB25B33677D1; SizeAsReceived:6917; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [ao8iesGOO7zvevMdS/q1mxbUcTJHf6RU]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT080; 6:hrLEH88uBVNc7+qmgPM/NhTP+W2r5BUW67Br6l6viUjBuYQbYblWoKmZBWFkGznm5RDCuifp6YnX4ejJsQHa0wwoNNQ6Sqsy8YwbgvbVqDeJZjJwno3iwNaVQNHGgTYrxBvnZXdc4bSMT5vlE6Fic2w1Kcqa4bPTWy+kWpYW2i8jFigpDF+VyAGGfiSAJjEbIBt4mR5a+ofTNsMqNbM2Dkz+dC1bOCvoEHFjRu6svgYLlBYVaPl1X78OgjhckfMg9VLZt4iMmb2og9fQgewM2AagY3Vry8KK+ZdqBkCK4lX7IyHzY8HR/suW+Rox0jEu8FGhZJ3x2DvB9c3cLKAiJq0hXTqnwNCEXZk6HR7I4KLFvv5fl45CiYHBJ2Ih8q3W6BabL69vJ4ivRxVGCZTyirKbbwXS19DpEVnqonR4zLD1K2toGAVJlUGJJfmc172GWYY2XPKIyJP2UZ5iVZoxig==; 5:5vxWdP2fS6Jr3bHZ1ULDWqIeqeFDzSzf/WwfMjTKM2ij+sHxGIXK6TpAwekG/q2vvQ+7l/XSlhYJyfP7rtMvgS0GmjaCvtC2Xh+uKgfyeZJ7msxVArjIhPL7iY/zyp6GjpJ6lItOxXc9vCDpAGMRPLym8eMpAeK1D7AoAT3+eXM=; 7:qQi9iLZpIPW3q1/ogGYMU087A9MkQvOeJU0seqkPhhu9rElC0SuDZXzuWoA62VkBoU+PqpBoIPvJH0R1KzUyuBVqDYu/1u5pWPL+dvioqX6fCLvZvFVsxBIN4eaid3o2ei8+T3QwAHXSNGl2j5HhYHBTPd1VhmQF1NtUa67AW2R296j4N9SlQaLrqqoH7eZSO+Hxpxmvix7zS55/Xy0PspNQRPdMGjyy3x95tZf7eKTj0CfNubXAzPCLmL4XhuqC
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:SG2APC01HT080; 
x-ms-traffictypediagnostic: SG2APC01HT080:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:SG2APC01HT080; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT080; 
x-microsoft-antispam-message-info: irji9rVGFbBLm0u6XLE4nolvvwpKgCrNO/b9dGwiMLdQ83+op6k2gvnrlFcWsWEy
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB2606721FBFDD744E0955B6E7B7E10SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 29f7a26b-f673-46ef-5a0d-08d62f1f471b
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2018 02:14:30.2720 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT080
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tGcMVdEjDMEJWS8FhzO5AXziSUg>
Subject: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 02:14:35 -0000

--_000_SG2PR0302MB2606721FBFDD744E0955B6E7B7E10SG2PR0302MB2606_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am again stressing the need for two applications
Verify envelope that verifies who the sender is
Who is email address that shows the credentials or identity documents or ce=
rtificates of a email owner. This can be password protected or shown only i=
f the user has the public key of the email owner.
With these laws can be enacted so emails can be used instead of sending reg=
istered snail mail
Right now banks and govts are getting away with solving my situation based =
on emails. I have health problems because of lack of lifestyle that cannot =
be postponed
And all these could have been delivered by engineers on payroll years ago
All desktops using emails should have access to these standard applications
Pradeep Kumar xplorer

--_000_SG2PR0302MB2606721FBFDD744E0955B6E7B7E10SG2PR0302MB2606_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
I am again stressing the need for two applications<br>
Verify envelope that verifies who the sender is<br>
Who is email address that shows the credentials or identity documents or ce=
rtificates of a email owner. This can be password protected or shown only i=
f the user has the public key of the email owner.<br>
With these laws can be enacted so emails can be used instead of sending reg=
istered snail mail<br>
Right now banks and govts are getting away with solving my situation based =
on emails. I have health problems because of lack of lifestyle that cannot =
be postponed
<br>
And all these could have been delivered by engineers on payroll years ago<b=
r>
All desktops using emails should have access to these standard applications=
<br>
Pradeep Kumar xplorer
</body>
</html>

--_000_SG2PR0302MB2606721FBFDD744E0955B6E7B7E10SG2PR0302MB2606_--


From nobody Wed Oct 10 19:42:00 2018
Return-Path: <ben@nostrum.com>
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 68582130DFE for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NsT8004zgtc6 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:41:56 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 B3718130DFB for <art@ietf.org>; Wed, 10 Oct 2018 19:41:55 -0700 (PDT)
Received: from [10.0.1.27] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9B2fruP045703 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 10 Oct 2018 21:41:54 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.27]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BB796AB6-7922-45CD-8409-D6DC6DDA916A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Wed, 10 Oct 2018 21:41:52 -0500
In-Reply-To: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
Cc: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, "art@ietf.org" <art@ietf.org>
To: pradeep xplorer <pradeepan88@hotmail.com>
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/IndzzpQBsQUmtdtqYj1tFSgoyfk>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 02:41:58 -0000

--Apple-Mail=_BB796AB6-7922-45CD-8409-D6DC6DDA916A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

(as individual)

Hi Pradeep,

The applications you propose seem to accomplish the same thing as =
cryptographic signatures and a PKI. Those technologies already exist. As =
far as I can tell, the only functional difference is that they are =
optional to use, and I gather you wish for something that is mandatory. =
The IETF can provide tools, but it cannot establish policy to force =
their deployment or use. That power belongs to governments.

Ben.

> On Oct 10, 2018, at 9:14 PM, pradeep xplorer <pradeepan88@hotmail.com> =
wrote:
>=20
> I am again stressing the need for two applications
> Verify envelope that verifies who the sender is
> Who is email address that shows the credentials or identity documents =
or certificates of a email owner. This can be password protected or =
shown only if the user has the public key of the email owner.
> With these laws can be enacted so emails can be used instead of =
sending registered snail mail
> Right now banks and govts are getting away with solving my situation =
based on emails. I have health problems because of lack of lifestyle =
that cannot be postponed
> And all these could have been delivered by engineers on payroll years =
ago
> All desktops using emails should have access to these standard =
applications
> Pradeep Kumar xplorer
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


--Apple-Mail=_BB796AB6-7922-45CD-8409-D6DC6DDA916A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlu+uHAACgkQgFZKbJXz
1A0Z5w/6A6tDCM8/VadND5SM39xYfmWgqbLa4/fs/igYeaaBuxIMFfrAb5B15mgt
LCEa3mXN3CBfohO5zIyKB2vLWvRkLaRRjZHyM6kqnVYogNUB8AImuY99+T5ooBV+
FAuDTlSxRqE0zii5ChbxBy4AhUw75Ok3ulUWNO+liX1OcgJQsG1lf/sCG2z7gZxs
+ia3FNybA7aEIn3feEDf6nKyjZGjp7cJoNGvsSsZRSEgFdBsZDQuEK4tcB+AJ0te
hJifNEmnS/23ooPRGkGQY3CHItEuZdnGJIn3QyhSLiK5A1sY07nRXOoF9ZCE3HSU
zx/RgQexgs77F0FRk757OZTUwEQvFr/ZjgpXe+AQWM5kIr78ud5KWFUUtwGWbjGJ
iDXV1VqZqSJhuI4U8A4GitkMnxU8vMPa3J8k+VutJQ1Z4ZN6+UV5wuXXop1AF+M0
KZ0PI1K3H68x3czMKkFisI9wpocxgYW+RJxruv5/t3GwKxS6TirnTGfWyyGhmy5Z
Q9VmRh4av2DIaGoNa0oP7ephjpbnLizU5hYlt1X9tLVgfN4RP9ANXWNfkZNQ17jK
T4ZRKkLrUjA08lqmVc+Bd/YVRs00ogYfCKE5hKNHYpd4WUm9uTvmjtTkC/8chfb/
SHK40O2MuVG+6JSEMiUeRdpJQmdITjWOda/Ofi9N8YM5dQdB0Mk=
=3U9e
-----END PGP SIGNATURE-----

--Apple-Mail=_BB796AB6-7922-45CD-8409-D6DC6DDA916A--


From nobody Wed Oct 10 19:55:55 2018
Return-Path: <pradeepan88@hotmail.com>
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 84FEB12F295 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 RCsEbEspvdrJ for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 19:55:51 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255090.outbound.protection.outlook.com [40.92.255.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 587E7130DF2 for <art@ietf.org>; Wed, 10 Oct 2018 19:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Rd2zgdwfPCddbJLhTQnGse46OGhA3N7Gq98oyyTb3AA=; b=eoY8zLwLBEtO0xEi7ZJ9FoxnIKM7khZnx+TTz1vV7Af/IuqomvcpbhxBkTOhK1dGOTcHz7hdyGJJt5U9Cl3Eci8XjWnQ3663lqcfVyCgzgQw3vObbllod/eVauj9DttWnRaQhhENhqvqWrqzvQg7L9Lnfq3iLXwveV7AXmBRYGRPqE2Sa9qmjGpL0MjBU6TFx2t0Yhx0rLjyKFdXjahdlFdONFzNKspJbfCbW23qnw3YmiQn9sFZrx1/8uYOiDg1GkPJ90fYD7kbl5xKB/qO4DgulJ1VOEQbjM+2Nae0ZHp/TF3cMZ+lRPe2GbhmlOzQxUfUqVuG65roh5zYLNMIaA==
Received: from HK2APC01FT060.eop-APC01.prod.protection.outlook.com (10.152.248.54) by HK2APC01HT224.eop-APC01.prod.protection.outlook.com (10.152.249.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Thu, 11 Oct 2018 02:55:47 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.248.60) by HK2APC01FT060.mail.protection.outlook.com (10.152.249.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Thu, 11 Oct 2018 02:55:47 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995%4]) with mapi id 15.20.1228.020; Thu, 11 Oct 2018 02:55:47 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: Ben Campbell <ben@nostrum.com>
CC: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, "art@ietf.org" <art@ietf.org>
Thread-Topic: [art] verify envelope and who is email
Thread-Index: AQHUYQcBgbYSN/G6lkuTGJWrzSYXx6UZVeAAgAADCXM=
Date: Thu, 11 Oct 2018 02:55:47 +0000
Message-ID: <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>, <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com>
In-Reply-To: <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:970D1A11F1A47670912F2BEAAAC0DAE2936C9C0C782FAC71F58709D9C645CFB9; UpperCasedChecksum:85BCBB15DF7F88C88477793D50B84FFB58A02BE001E936685927493C8E3E421A; SizeAsReceived:7239; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [OFnd7aTXuVsDjd6VSdDpw6EUO5VHKZN7]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HK2APC01HT224; 6:nDyra8L0W0KiQb9uNOSJTdAFrAxOhpXn/GZf5ecl0oqR3ezMeyRQs33+CdKy49CuxbS9oXJo1hcXvg2pkh6y0YphlXng3Y4YZrj7R32VD9iDKW3ACewSYVJZENGV47QPgsy6lC+YrxuHatl8EGLtMibUZWd1RJhznjVWb7Wgebp+NRwqZZl8T5BKZoU6rs7PXb/Oyp6ISfNp/Sc8fh8DXl5SSx46Ml0dOLvW/R/ca0p3o14yox63gX4SV1LxVcw4ftLpj90hoMyi7K5Jc3Ms4DpMZkBmpbnjPsTbw/v5iT+WEzbd5Uecf8GX/o7mpQlc9YYrw6YY2HNHYo+fFR5h+uS6s2iRM3ejqlJJc02IVEB3vKf/UPCq1GtS3pSwGF/brRIdon0SW5gGb98s0s6WyXlUJMCoUZnsPGZb/A8pJ42vJnQQ7PeDmF2SC5ZQ9newgbawU5r8jVyerfYMem19qw==; 5:pmmJTPlHxTnjO4Q4vaMIe3Ri33M5dYol23370NPo3a44qb8TW/V1iXAJ4NiJ1eehLJ+SLOmYYG9J1MK7WF0vrdi9Bjv3unr/4TQxYRoFb43gV8hoNtIqNhatZEoXj+SJglXYuy+j42IR01ByMaLQAImQqoYDPqHXTLyIfoK+UD4=; 7:P1HgtkoFkv7sYrecWTtJ1qVsp8X/uO2yt3SJL/D6vFcwtHyLW6Hm1SL0sRF4tfeXnsDqiNfcBg+VEfPlOkzY3BteTnIcZCxUDw5Q5xKr+mHvKBZ7ZXy38dz8yfAaFTwzX/PQkp7uqL5nyUmVZQFIgN82HzrBR7vNiiSz6QvsKUVdsGHoofOJfpPRRs/4efiDr+GJIVGTSyBbYrDOnuVASz9jMfzi5nGrEh2waNtZoFVV47hgIvJngxUmjmji0wIP
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:HK2APC01HT224; 
x-ms-traffictypediagnostic: HK2APC01HT224:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:HK2APC01HT224; BCL:0; PCL:0; RULEID:; SRVR:HK2APC01HT224; 
x-microsoft-antispam-message-info: sAcsDuMW7TEXpMQST6xaWMDXipvINCbQ4tyojHskhTiT16ivf14Xr817Ke+c+7k6
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB260669F3406EC000F886153CB7E10SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: d04662fb-f9f8-42e5-cb71-08d62f250ba2
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2018 02:55:47.4487 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT224
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/UCqn856NfxlmNen05R7tDIPC-iA>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 02:55:54 -0000

--_000_SG2PR0302MB260669F3406EC000F886153CB7E10SG2PR0302MB2606_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please be specific where are the tools. I am using android where are the to=
ols in Google play store?. I am saying tools are not available. If i am wro=
ng correct me point me to the tools available for major platforms.
Pradeep Kumar xplorer
________________________________
From: Ben Campbell <ben@nostrum.com>
Sent: Thursday, October 11, 2018 8:11:52 AM
To: pradeep xplorer
Cc: Yakov Shafranovich; art@ietf.org
Subject: Re: [art] verify envelope and who is email

(as individual)

Hi Pradeep,

The applications you propose seem to accomplish the same thing as cryptogra=
phic signatures and a PKI. Those technologies already exist. As far as I ca=
n tell, the only functional difference is that they are optional to use, an=
d I gather you wish for something that is mandatory. The IETF can provide t=
ools, but it cannot establish policy to force their deployment or use. That=
 power belongs to governments.

Ben.

> On Oct 10, 2018, at 9:14 PM, pradeep xplorer <pradeepan88@hotmail.com> wr=
ote:
>
> I am again stressing the need for two applications
> Verify envelope that verifies who the sender is
> Who is email address that shows the credentials or identity documents or =
certificates of a email owner. This can be password protected or shown only=
 if the user has the public key of the email owner.
> With these laws can be enacted so emails can be used instead of sending r=
egistered snail mail
> Right now banks and govts are getting away with solving my situation base=
d on emails. I have health problems because of lack of lifestyle that canno=
t be postponed
> And all these could have been delivered by engineers on payroll years ago
> All desktops using emails should have access to these standard applicatio=
ns
> Pradeep Kumar xplorer
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


--_000_SG2PR0302MB260669F3406EC000F886153CB7E10SG2PR0302MB2606_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
Please be specific where are the tools. I am using android where are the to=
ols in Google play store?. I am saying tools are not available. If i am wro=
ng correct me point me to the tools available for major platforms.
<br>
Pradeep Kumar xplorer
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Ben Campbell &lt;ben@=
nostrum.com&gt;<br>
<b>Sent:</b> Thursday, October 11, 2018 8:11:52 AM<br>
<b>To:</b> pradeep xplorer<br>
<b>Cc:</b> Yakov Shafranovich; art@ietf.org<br>
<b>Subject:</b> Re: [art] verify envelope and who is email</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">(as individual)<br>
<br>
Hi Pradeep,<br>
<br>
The applications you propose seem to accomplish the same thing as cryptogra=
phic signatures and a PKI. Those technologies already exist. As far as I ca=
n tell, the only functional difference is that they are optional to use, an=
d I gather you wish for something
 that is mandatory. The IETF can provide tools, but it cannot establish pol=
icy to force their deployment or use. That power belongs to governments.<br=
>
<br>
Ben.<br>
<br>
&gt; On Oct 10, 2018, at 9:14 PM, pradeep xplorer &lt;pradeepan88@hotmail.c=
om&gt; wrote:<br>
&gt; <br>
&gt; I am again stressing the need for two applications<br>
&gt; Verify envelope that verifies who the sender is<br>
&gt; Who is email address that shows the credentials or identity documents =
or certificates of a email owner. This can be password protected or shown o=
nly if the user has the public key of the email owner.<br>
&gt; With these laws can be enacted so emails can be used instead of sendin=
g registered snail mail<br>
&gt; Right now banks and govts are getting away with solving my situation b=
ased on emails. I have health problems because of lack of lifestyle that ca=
nnot be postponed<br>
&gt; And all these could have been delivered by engineers on payroll years =
ago<br>
&gt; All desktops using emails should have access to these standard applica=
tions<br>
&gt; Pradeep Kumar xplorer<br>
&gt; _______________________________________________<br>
&gt; art mailing list<br>
&gt; art@ietf.org<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/art">https://www.ietf=
.org/mailman/listinfo/art</a><br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_SG2PR0302MB260669F3406EC000F886153CB7E10SG2PR0302MB2606_--


From nobody Wed Oct 10 20:09:00 2018
Return-Path: <ben@nostrum.com>
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 51854130E01 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 SeHaQ93po8Zp for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:08:56 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4E4DD130DFE for <art@ietf.org>; Wed, 10 Oct 2018 20:08:56 -0700 (PDT)
Received: from [10.0.1.27] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9B38qsa050096 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 10 Oct 2018 22:08:53 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.27]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <611C2942-C4C4-4C98-A326-6D8CC223E3F2@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_53B8DD33-92D1-4B9E-B646-1D444EA5A00D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Wed, 10 Oct 2018 22:08:52 -0500
In-Reply-To: <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
Cc: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>, "art@ietf.org" <art@ietf.org>
To: pradeep xplorer <pradeepan88@hotmail.com>
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com> <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/YyIeBpPX9fZDwxi5ozdGNFeP1Ys>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 03:08:58 -0000

--Apple-Mail=_53B8DD33-92D1-4B9E-B646-1D444EA5A00D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

To be clear, the IETF is also not a software development shop. We make =
standards, not code. We cannot make people implement, deploy or use =
them.

Digital signatures will only help your problem if people use them, and =
they are not used widely. But if we introduce even more tools to =
accomplish a subset of the same thing, they will likely be used even =
less widely.

But to your specific question: A DuckDuckGo search for =E2=80=9Cs/mime =
for android=E2=80=9D turns up several hits. I am not an Android user, so =
I do not have experience with any of them.

Ben.


> On Oct 10, 2018, at 9:55 PM, pradeep xplorer <pradeepan88@hotmail.com> =
wrote:
>=20
> Please be specific where are the tools. I am using android where are =
the tools in Google play store?. I am saying tools are not available. If =
i am wrong correct me point me to the tools available for major =
platforms.
> Pradeep Kumar xplorer
> From: Ben Campbell <ben@nostrum.com>
> Sent: Thursday, October 11, 2018 8:11:52 AM
> To: pradeep xplorer
> Cc: Yakov Shafranovich; art@ietf.org
> Subject: Re: [art] verify envelope and who is email
>=20
> (as individual)
>=20
> Hi Pradeep,
>=20
> The applications you propose seem to accomplish the same thing as =
cryptographic signatures and a PKI. Those technologies already exist. As =
far as I can tell, the only functional difference is that they are =
optional to use, and I gather you wish for something that is mandatory. =
The IETF can provide tools, but it cannot establish policy to force =
their deployment or use. That power belongs to governments.
>=20
> Ben.
>=20
> > On Oct 10, 2018, at 9:14 PM, pradeep xplorer =
<pradeepan88@hotmail.com> wrote:
> >
> > I am again stressing the need for two applications
> > Verify envelope that verifies who the sender is
> > Who is email address that shows the credentials or identity =
documents or certificates of a email owner. This can be password =
protected or shown only if the user has the public key of the email =
owner.
> > With these laws can be enacted so emails can be used instead of =
sending registered snail mail
> > Right now banks and govts are getting away with solving my situation =
based on emails. I have health problems because of lack of lifestyle =
that cannot be postponed
> > And all these could have been delivered by engineers on payroll =
years ago
> > All desktops using emails should have access to these standard =
applications
> > Pradeep Kumar xplorer
> > _______________________________________________
> > art mailing list
> > art@ietf.org
> > https://www.ietf.org/mailman/listinfo/art
>=20


--Apple-Mail=_53B8DD33-92D1-4B9E-B646-1D444EA5A00D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlu+vsQACgkQgFZKbJXz
1A14mw/9G+PBsRWO0FtABNJDLpuH+H5yu7IMaRwnNjl2GLJWuLIJ1qRX36LxgQ1B
0Z86vc/MoOuDKgC3VBmw5BFFQZ5+O/MvtBxJQH5EJSgiVmSrVqPxvvBbfMqxzjth
8S8r0Mb4VL06b6fGfMi5qi6flj+ehxXUUPUedj+HqobKhT7sMCe5ZgUrAi8vu6wL
YxEc+f+54x17Lp8OsqqpRFKqlFN2nTkAVLc1qmxtsinBzLvrf1sAHHIyVIcIm4i3
AyftigpZof2CfzB726JoDlAL0zP9Ltw60PF7DyKow2S8LsxrHM2GnTLF1V9G/y64
Hf6ZNjjqJ9bJp3nEjahFMetiDW1GksnwsqSXivfjrLoDJj+JmC4zyWiG1XNMuF0c
lRDCmqbxHcuU5UBq5X2OmfdATnySl2o+yyHkHGADm60y0/46xNAuh4NkS7PHFNLp
eZcs3lcXwV+217fyqCI0lylnTu22a9xKySlJmdVsUj4xnINpfE8WwGRwqvZ8MK8X
ZDkFFd0uMEkWP6Rhn5rQWCCD1YBt3mjaJxcxwvh5VUTeRg3EdQFQ+yNGmto6ospP
+QN7Jse3Kxe24AYp0vzoHoI1UnMe/GhKWjy+G8LuNgWKHiAgea+r3jOVaQspoayg
Al/EtCl1cAumGbo1C6pHghIUWqp/2++AYpgFkWppARrLNBreYLc=
=CwP+
-----END PGP SIGNATURE-----

--Apple-Mail=_53B8DD33-92D1-4B9E-B646-1D444EA5A00D--


From nobody Wed Oct 10 20:14:52 2018
Return-Path: <yakov@nightwatchcybersecurity.com>
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 18C6A130E08 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nightwatchcybersecurity-com.20150623.gappssmtp.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 ODLz0yR9NFW4 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:14:48 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 B168D130DFE for <art@ietf.org>; Wed, 10 Oct 2018 20:14:48 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id f8-v6so3453002pgq.5 for <art@ietf.org>; Wed, 10 Oct 2018 20:14:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nightwatchcybersecurity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=rLYJqAbZrFrecnSGqnY3nW3Z8tTU/XUelrifuOT7cOg=; b=0ZMnldMhfrKpaYV9RoTIAakhvSgH5iAdrb3TP+b90Qz+4Xi9dhx6LRJgytOxGpu+W4 O0FmfLPUv8cRn48/MJuA0UWzZsmr5Xid8xwN+tkLXGass8BD7aicTbBwLfZcjOJHvXUM XM8WAPmAQkQ5Pk6drMvHJHH2Og9JZa3CYbAkEMnSUHTB2TvEwp5RzTcJzlFt9CCFPE41 joKmnj/e1PwcDPnssU8G3zDMvuotuLY/JLdWQ/988S5pmy7pDilzoQsI7wwOLZSba41H PWEEbK4lLyHTVP5Es+O1Gf9HElhrmXFUSX1fFmt8VCL5zxP3QoC8HEkEcGMYWMAKcjmK RViQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=rLYJqAbZrFrecnSGqnY3nW3Z8tTU/XUelrifuOT7cOg=; b=pTMoMgaT3N+eM8auUawmqbpI6pihiO8OxdI1smbAdBJ+b+LTOC65BTqHLLH9e69yT1 vwVoLetMJXJ7FpMGIQehjTX+6EK6ftf9CTufpBvU3hmgaPJ6lZtYfmf+vSnb3JDIOyrR EesizY0dIiUjUTmjFm8q0Gu2VfM4wISINV1BCfwFc4Ku2fjrj7cD4YG/5y0fwFc3RXli U8MnkRCPMA8aJRgDQqcB/bBKAMdUo+8jVywuwcEozvLG455CdBjddTWrAi5poEz1E+lk ay1O/2NqULJSmMdfsN636ktxAsazN6+KacyVO/gepsbk1S9+xSZK59szg9jcJ6A3dVyR Scyw==
X-Gm-Message-State: ABuFfohsvhX026siHJOv+K/dBOErlyMGBaaQQCTgo8hZLhQf8TXRuom1 4NEIq5AkJCGpUcZdwQfuN5pbuCC7D5eGiUVuRgguMA==
X-Google-Smtp-Source: ACcGV62/g+m/WlZQunSDnXxtSKFFfSMezqxraq+ccRqVGrISb4PaNVr2SPGd1NfO6oF/jKsYfieBwj8G7IxxmzJexPw=
X-Received: by 2002:a63:64c2:: with SMTP id y185-v6mr31631269pgb.411.1539227688011;  Wed, 10 Oct 2018 20:14:48 -0700 (PDT)
MIME-Version: 1.0
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com> <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <611C2942-C4C4-4C98-A326-6D8CC223E3F2@nostrum.com>
In-Reply-To: <611C2942-C4C4-4C98-A326-6D8CC223E3F2@nostrum.com>
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Date: Wed, 10 Oct 2018 23:14:12 -0400
Message-ID: <CAAyEnSPnzgahQOEzgEBBdrSaawp739wTQgR97+cV0PhqKOyQdA@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: pradeepan88@hotmail.com, art@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/kN8JLUXHt57yPmKR5-sHEuHipsE>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 03:14:51 -0000

The SPF and DKIM protocols allow verification of the envelope against
a domain name and some of the headers / content respectively
(depending on configuration). There are additional protocols like
DMARC, DANE, etc. which provide additional functionality in this
space. The initial development of these protocols was done in IRTF's
ASRG group back in 2001 and on. However, as Ben said, we cannot force
people to use them.

May of these are in-use today by most major email providers. For
example, Gmail added DKIM support back in 2008:
https://gmail.googleblog.com/2008/07/fighting-phishing-with-ebay-and-paypal=
.html

Here is information about Hotmail support for SPF and DKIM:
https://wordtothewise.com/2012/12/hotmail-moves-to-spf-authentication/
https://blogs.msdn.microsoft.com/tzink/2016/10/18/hotmailoutlook-com-evalua=
tes-dkim-a-little-differently-than-office-365/

A more extreme case of how DKIM digital signatures were used is the
case of Wikileaks using Gmail's DKIM keys to verify the authenticity
of stolen/leaked DNC emails in 2016:
https://blog.erratasec.com/2016/10/yes-we-can-validate-wikileaks-emails.htm=
l

Thanks
On Wed, Oct 10, 2018 at 11:08 PM Ben Campbell <ben@nostrum.com> wrote:
>
> To be clear, the IETF is also not a software development shop. We make st=
andards, not code. We cannot make people implement, deploy or use them.
>
> Digital signatures will only help your problem if people use them, and th=
ey are not used widely. But if we introduce even more tools to accomplish a=
 subset of the same thing, they will likely be used even less widely.
>
> But to your specific question: A DuckDuckGo search for =E2=80=9Cs/mime fo=
r android=E2=80=9D turns up several hits. I am not an Android user, so I do=
 not have experience with any of them.
>
> Ben.
>
>
> > On Oct 10, 2018, at 9:55 PM, pradeep xplorer <pradeepan88@hotmail.com> =
wrote:
> >
> > Please be specific where are the tools. I am using android where are th=
e tools in Google play store?. I am saying tools are not available. If i am=
 wrong correct me point me to the tools available for major platforms.
> > Pradeep Kumar xplorer
> > From: Ben Campbell <ben@nostrum.com>
> > Sent: Thursday, October 11, 2018 8:11:52 AM
> > To: pradeep xplorer
> > Cc: Yakov Shafranovich; art@ietf.org
> > Subject: Re: [art] verify envelope and who is email
> >
> > (as individual)
> >
> > Hi Pradeep,
> >
> > The applications you propose seem to accomplish the same thing as crypt=
ographic signatures and a PKI. Those technologies already exist. As far as =
I can tell, the only functional difference is that they are optional to use=
, and I gather you wish for something that is mandatory. The IETF can provi=
de tools, but it cannot establish policy to force their deployment or use. =
That power belongs to governments.
> >
> > Ben.
> >
> > > On Oct 10, 2018, at 9:14 PM, pradeep xplorer <pradeepan88@hotmail.com=
> wrote:
> > >
> > > I am again stressing the need for two applications
> > > Verify envelope that verifies who the sender is
> > > Who is email address that shows the credentials or identity documents=
 or certificates of a email owner. This can be password protected or shown =
only if the user has the public key of the email owner.
> > > With these laws can be enacted so emails can be used instead of sendi=
ng registered snail mail
> > > Right now banks and govts are getting away with solving my situation =
based on emails. I have health problems because of lack of lifestyle that c=
annot be postponed
> > > And all these could have been delivered by engineers on payroll years=
 ago
> > > All desktops using emails should have access to these standard applic=
ations
> > > Pradeep Kumar xplorer
> > > _______________________________________________
> > > art mailing list
> > > art@ietf.org
> > > https://www.ietf.org/mailman/listinfo/art
> >
>


From nobody Wed Oct 10 20:17:47 2018
Return-Path: <yakov@nightwatchcybersecurity.com>
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 AFB02130E09 for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nightwatchcybersecurity-com.20150623.gappssmtp.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 gNV0TPj7XP3A for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 20:17:43 -0700 (PDT)
Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) (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 48722130DFE for <art@ietf.org>; Wed, 10 Oct 2018 20:17:43 -0700 (PDT)
Received: by mail-pl1-x644.google.com with SMTP id f8-v6so3484690plb.2 for <art@ietf.org>; Wed, 10 Oct 2018 20:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nightwatchcybersecurity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=6jrj0E9EuUJbJb7m1mfMjCPG9yEd1QwJTJez+8P9K9A=; b=0NumSyOj+dcL8gQ+2BRwbjHHGIh1ZICDaKxfweWUxJnpsa5Mngg8nB4imqD8d/0ta5 ZKPUuYLqoUPHUogDpn6uBNYI9WUcGtbHgzeLBJhxXu5W7LWhPaEohNUxgRoV4HXUDUnC mWBzyBQ75YFVM9N2RxLj8XD+l5P+snbL5Fh+MIAXwcTcJMZk848kBwsxMQQA7HKY8tY2 MPH/nqhjB17PQuD+PuzJ6f17d/v4EShk9NW4M6RnZ0dDxxw6D1Ucu03meUT40ZZJ6QUj BUjfOG7+Sn+tZKfQhmiii2lLJKfYYGcAd10+CUhfp1kKxPbfXHH4blfdlryCPhB6wYpd 2B5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=6jrj0E9EuUJbJb7m1mfMjCPG9yEd1QwJTJez+8P9K9A=; b=nwlpcdHK2hfepyF7ffJSDGAPi26mgYOksNaKW4vkiHv+Zb/4IErwHkRxrOp8qd0GcR heIkFuer/7u2d5eAWyZnPQ2wak/5EgnAhDHHry+mDEikoTXH6+8hYmyVBe0UnkPNDBAX rqJonjwtqkx7mg5zkTG7S/GR9CfwYH8quGUIJ56F0Gv7i9NVEA1xUikeUx/t+KHczu6a 1vyDVkzI7PjPUxIHwYNAtMOXNsQZfFerz+0hP8KDBIR4Sk+CXlsHHPPqSYCdRKyRryEF azjux0TYOYaI0Q6L+REBc5Seljwt/VcbNMfQobvTX5o0AJkDUqWSHc6Ad+I+a5b1eoIZ F5ug==
X-Gm-Message-State: ABuFfoiUedIQ/p4GhDp50H7eJrshvHY9aA4RDp/HWOvbNj+nB+iNyGl6 1qE1xC7//yKjKJ2Tz++t3XK0DT3vZQdaNfof1BfcAw==
X-Google-Smtp-Source: ACcGV61ecv/3cVITjDg6if+z66wIP4Rtio5ES7Of3JRkliN+rnybZ8iCYIVxY+7X6rQIh/g/+w8tl0oVQ882zLKlutc=
X-Received: by 2002:a17:902:1121:: with SMTP id d30-v6mr34357869pla.250.1539227862670;  Wed, 10 Oct 2018 20:17:42 -0700 (PDT)
MIME-Version: 1.0
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com> <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <611C2942-C4C4-4C98-A326-6D8CC223E3F2@nostrum.com> <CAAyEnSPnzgahQOEzgEBBdrSaawp739wTQgR97+cV0PhqKOyQdA@mail.gmail.com>
In-Reply-To: <CAAyEnSPnzgahQOEzgEBBdrSaawp739wTQgR97+cV0PhqKOyQdA@mail.gmail.com>
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Date: Wed, 10 Oct 2018 23:17:06 -0400
Message-ID: <CAAyEnSO=EEN3ugkW_kGbY9m8Ad=UWj6ELYiDTVE8R2X6BccPrA@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: pradeepan88@hotmail.com, art@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/g-VcYWbCJcN9yvlj3xUe9_6TIiM>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 03:17:46 -0000

To be clear, this accomplishes verification of various types of
Internet identifiers like email addresses against other Internet
identifiers like domain names. These protocols do not necessarily
address the issue of how to verify something on the Internet against a
real world identity, although the PKI pieces may lead in that
direction.

Thanks
On Wed, Oct 10, 2018 at 11:14 PM Yakov Shafranovich
<yakov@nightwatchcybersecurity.com> wrote:
>
> The SPF and DKIM protocols allow verification of the envelope against
> a domain name and some of the headers / content respectively
> (depending on configuration). There are additional protocols like
> DMARC, DANE, etc. which provide additional functionality in this
> space. The initial development of these protocols was done in IRTF's
> ASRG group back in 2001 and on. However, as Ben said, we cannot force
> people to use them.
>
> May of these are in-use today by most major email providers. For
> example, Gmail added DKIM support back in 2008:
> https://gmail.googleblog.com/2008/07/fighting-phishing-with-ebay-and-payp=
al.html
>
> Here is information about Hotmail support for SPF and DKIM:
> https://wordtothewise.com/2012/12/hotmail-moves-to-spf-authentication/
> https://blogs.msdn.microsoft.com/tzink/2016/10/18/hotmailoutlook-com-eval=
uates-dkim-a-little-differently-than-office-365/
>
> A more extreme case of how DKIM digital signatures were used is the
> case of Wikileaks using Gmail's DKIM keys to verify the authenticity
> of stolen/leaked DNC emails in 2016:
> https://blog.erratasec.com/2016/10/yes-we-can-validate-wikileaks-emails.h=
tml
>
> Thanks
> On Wed, Oct 10, 2018 at 11:08 PM Ben Campbell <ben@nostrum.com> wrote:
> >
> > To be clear, the IETF is also not a software development shop. We make =
standards, not code. We cannot make people implement, deploy or use them.
> >
> > Digital signatures will only help your problem if people use them, and =
they are not used widely. But if we introduce even more tools to accomplish=
 a subset of the same thing, they will likely be used even less widely.
> >
> > But to your specific question: A DuckDuckGo search for =E2=80=9Cs/mime =
for android=E2=80=9D turns up several hits. I am not an Android user, so I =
do not have experience with any of them.
> >
> > Ben.
> >
> >
> > > On Oct 10, 2018, at 9:55 PM, pradeep xplorer <pradeepan88@hotmail.com=
> wrote:
> > >
> > > Please be specific where are the tools. I am using android where are =
the tools in Google play store?. I am saying tools are not available. If i =
am wrong correct me point me to the tools available for major platforms.
> > > Pradeep Kumar xplorer
> > > From: Ben Campbell <ben@nostrum.com>
> > > Sent: Thursday, October 11, 2018 8:11:52 AM
> > > To: pradeep xplorer
> > > Cc: Yakov Shafranovich; art@ietf.org
> > > Subject: Re: [art] verify envelope and who is email
> > >
> > > (as individual)
> > >
> > > Hi Pradeep,
> > >
> > > The applications you propose seem to accomplish the same thing as cry=
ptographic signatures and a PKI. Those technologies already exist. As far a=
s I can tell, the only functional difference is that they are optional to u=
se, and I gather you wish for something that is mandatory. The IETF can pro=
vide tools, but it cannot establish policy to force their deployment or use=
. That power belongs to governments.
> > >
> > > Ben.
> > >
> > > > On Oct 10, 2018, at 9:14 PM, pradeep xplorer <pradeepan88@hotmail.c=
om> wrote:
> > > >
> > > > I am again stressing the need for two applications
> > > > Verify envelope that verifies who the sender is
> > > > Who is email address that shows the credentials or identity documen=
ts or certificates of a email owner. This can be password protected or show=
n only if the user has the public key of the email owner.
> > > > With these laws can be enacted so emails can be used instead of sen=
ding registered snail mail
> > > > Right now banks and govts are getting away with solving my situatio=
n based on emails. I have health problems because of lack of lifestyle that=
 cannot be postponed
> > > > And all these could have been delivered by engineers on payroll yea=
rs ago
> > > > All desktops using emails should have access to these standard appl=
ications
> > > > Pradeep Kumar xplorer
> > > > _______________________________________________
> > > > art mailing list
> > > > art@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/art
> > >
> >


From nobody Wed Oct 10 23:46:38 2018
Return-Path: <pradeepan88@hotmail.com>
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 E171D130E3A for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 23:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 TFWAXL93gO3u for <art@ietfa.amsl.com>; Wed, 10 Oct 2018 23:46:33 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254098.outbound.protection.outlook.com [40.92.254.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6958130E3C for <art@ietf.org>; Wed, 10 Oct 2018 23:46:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KBzk+cAdQ0sJ4xhOvuw9IvH7xaxVXhsuTuSHyt/wLtY=; b=q7YM3INdwQHoctcn03rOnEp5P/wehgeKxF9SKZkTXCW+xidyBQpW95omb9fS5qaAXS5d/JdpJtOZHpuMQAvkQCdI1r2ZRpIDKkIIqyHhbDbGsxDvfgspyc91//GXjKKwKzLgh5bRyrt7ImgJO4C0fZiqTc6km8ys4Yaws21Pk1cDh/lQ0OFQcDYMc+YR3LnB7/YQQAuKDLJKQJNEzaYPX/CTfDhomQ9k8d2FYgO7wWGvNaPN5EfHG0DqrSrqR/pOFdJn/P+Gnb77pke8IiI/U6YPnfSRZTciG694MEr43kb2WCo4ZZ78ULhuNGXANEPvDkBBhioGBEmeam8Y/C7ECw==
Received: from SG2APC01FT026.eop-APC01.prod.protection.outlook.com (10.152.250.51) by SG2APC01HT246.eop-APC01.prod.protection.outlook.com (10.152.251.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1228.17; Thu, 11 Oct 2018 06:46:29 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.250.53) by SG2APC01FT026.mail.protection.outlook.com (10.152.250.190) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1228.17 via Frontend Transport; Thu, 11 Oct 2018 06:46:29 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::101b:ccae:d02e:3995%4]) with mapi id 15.20.1228.020; Thu, 11 Oct 2018 06:46:29 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
CC: "art@ietf.org" <art@ietf.org>
Thread-Topic: [art] verify envelope and who is email
Thread-Index: AQHUYQcBgbYSN/G6lkuTGJWrzSYXx6UZVeAAgAADCXOAAASCAIAAAX0AgAAA0ACAADiRXw==
Date: Thu, 11 Oct 2018 06:46:29 +0000
Message-ID: <SG2PR0302MB26068B64905157C250BC7D2EB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
References: <SG2PR0302MB2606721FBFDD744E0955B6E7B7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <93205FE3-79DB-485C-B149-E2D063ABB30B@nostrum.com> <SG2PR0302MB260669F3406EC000F886153CB7E10@SG2PR0302MB2606.apcprd03.prod.outlook.com> <611C2942-C4C4-4C98-A326-6D8CC223E3F2@nostrum.com> <CAAyEnSPnzgahQOEzgEBBdrSaawp739wTQgR97+cV0PhqKOyQdA@mail.gmail.com>, <CAAyEnSO=EEN3ugkW_kGbY9m8Ad=UWj6ELYiDTVE8R2X6BccPrA@mail.gmail.com>
In-Reply-To: <CAAyEnSO=EEN3ugkW_kGbY9m8Ad=UWj6ELYiDTVE8R2X6BccPrA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:BC7E1791B5C73FE4F599E789EEAEDE77B6082BDAADF668C7E6AEA661FA968060; UpperCasedChecksum:CBA1521A2D6684C0F4F6B2CBB73030FDF246738DD02C53C0B68957E8E163E997; SizeAsReceived:7538; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [D7OZYlI41M96Mm4tcksMY4Wgn+nkCPiVzsdiHuNoR0Y=]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT246; 6:hHqxgOt/3VKeBxasy0s5WFESuXJxa/pRBvW5BDs4oGK3y+ql/LbQTIB6ZmPVa+JXTlshbBan4qnJIm7t7rGyNGLflExiBXwd4/djN5JYAFepYW91+SNRmfh0QJDjCCjF8tdC1EWJuUfugzN0qMMpuyyY/oiQ//R1OXv/9yn0FC98lY9J9/yqD42SucW3BqJ5AN8rK6m19CfO92Hju1q7GBwGiX7VoMbHKmmO7WNJf3BCUAhiD0Gc6Ob/nPLxVk99EW0fEnsdPqxpUCpN9DT1wuH0LHlTVgV1CEykuyOG/eYLRyFidbJjtrRrH4vXdSNxe3lnqoXE8rCtjL95eiWuXCa678kTRa/z8sjHoCg8JZ8/OUag/60OZnAgyAtYAO0T14znGN3PvcEP7ysq/8pzwAEi0Yw+FQztgyiN9As0m8klpqQdveeJE+gwHdvkxly6oHoorkAK5NI2mVBUh7Wqig==; 5:v7sWMHIS3Xh4NJShfsiM1wi4VS0h2hCdN6ulE2tg7LXGjDK3GC5HCmu0LVpPmRgCwGk5ffZqocdykHu2HOnojwnHPUGpefi4wyGGML2Lo+awWC22ReGXoGxd7hgQIee4yQZNAfBsN2mVHSGfJd4v0Hx3Oh8Cd9tLYL3ockF9c+c=; 7:2a50ceDwD6Y10VgUa7zDQoG1NCJoeQXfmOM9qG2e3pSCjQdRxYz5XcacVtmFUsNBRebXOq/ohZ/avnmUF44Y7bIGsmSKrtCqEobpHje2m0OJdopQ7/1UHbNWAAsdIoq+riQv/WfCktVkCwcHVU01s8v2UUHiwKJ96xVrxN9AfJ3JKG8WknRY3xM2k/LE1IQ3r+O4upAvELagwQtqo4GZXDXpgLrjId/kLhhXpYfVUWNtQ/JyPSkeRUWh1mBUvq4v
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125500)(1603101475)(1701031045); SRVR:SG2APC01HT246; 
x-ms-traffictypediagnostic: SG2APC01HT246:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:SG2APC01HT246; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT246; 
x-microsoft-antispam-message-info: JaPNFnbxf+CmZtKQYcGrOs3gXq14O6tbNfCfZtMaob3E6SOd3S7PLFbgCaVMVeG1
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB26068B64905157C250BC7D2EB7E10SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 52cea72e-fc0a-4edc-2009-08d62f454660
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2018 06:46:29.6434 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT246
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-XfVeCTtI_9B1MYroU0Eb18Uw6w>
Subject: Re: [art] verify envelope and who is email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 06:46:36 -0000

--_000_SG2PR0302MB26068B64905157C250BC7D2EB7E10SG2PR0302MB2606_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

>From the answers it looks like theres no application verifyenvelope like pu=
tty that can be downloaded and used to verify envelope of an inbound email =
because some combination of human intelligence and software has to be used =
to do this task and cannot be completely automated. It is not available on =
each and every desktop that can recieve emails. OR this is not implemented =
and released because of some policy decisions. By that i mean the expertise=
 and technology is available making it widely available as a app that can b=
e downloaded and used would lead to problems for some and they are against =
it becoming available.

________________________________
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Sent: Thursday, October 11, 2018 8:47 AM
To: Ben Campbell
Cc: pradeepan88@hotmail.com; art@ietf.org
Subject: Re: [art] verify envelope and who is email

To be clear, this accomplishes verification of various types of
Internet identifiers like email addresses against other Internet
identifiers like domain names. These protocols do not necessarily
address the issue of how to verify something on the Internet against a
real world identity, although the PKI pieces may lead in that
direction.

Thanks
On Wed, Oct 10, 2018 at 11:14 PM Yakov Shafranovich
<yakov@nightwatchcybersecurity.com> wrote:
>
> The SPF and DKIM protocols allow verification of the envelope against
> a domain name and some of the headers / content respectively
> (depending on configuration). There are additional protocols like
> DMARC, DANE, etc. which provide additional functionality in this
> space. The initial development of these protocols was done in IRTF's
> ASRG group back in 2001 and on. However, as Ben said, we cannot force
> people to use them.
>
> May of these are in-use today by most major email providers. For
> example, Gmail added DKIM support back in 2008:
> https://gmail.googleblog.com/2008/07/fighting-phishing-with-ebay-and-payp=
al.html
>
> Here is information about Hotmail support for SPF and DKIM:
> https://wordtothewise.com/2012/12/hotmail-moves-to-spf-authentication/
> https://blogs.msdn.microsoft.com/tzink/2016/10/18/hotmailoutlook-com-eval=
uates-dkim-a-little-differently-than-office-365/
>
> A more extreme case of how DKIM digital signatures were used is the
> case of Wikileaks using Gmail's DKIM keys to verify the authenticity
> of stolen/leaked DNC emails in 2016:
> https://blog.erratasec.com/2016/10/yes-we-can-validate-wikileaks-emails.h=
tml
>
> Thanks
> On Wed, Oct 10, 2018 at 11:08 PM Ben Campbell <ben@nostrum.com> wrote:
> >
> > To be clear, the IETF is also not a software development shop. We make =
standards, not code. We cannot make people implement, deploy or use them.
> >
> > Digital signatures will only help your problem if people use them, and =
they are not used widely. But if we introduce even more tools to accomplish=
 a subset of the same thing, they will likely be used even less widely.
> >
> > But to your specific question: A DuckDuckGo search for =93s/mime for an=
droid=94 turns up several hits. I am not an Android user, so I do not have =
experience with any of them.
> >
> > Ben.
> >
> >
> > > On Oct 10, 2018, at 9:55 PM, pradeep xplorer <pradeepan88@hotmail.com=
> wrote:
> > >
> > > Please be specific where are the tools. I am using android where are =
the tools in Google play store?. I am saying tools are not available. If i =
am wrong correct me point me to the tools available for major platforms.
> > > Pradeep Kumar xplorer
> > > From: Ben Campbell <ben@nostrum.com>
> > > Sent: Thursday, October 11, 2018 8:11:52 AM
> > > To: pradeep xplorer
> > > Cc: Yakov Shafranovich; art@ietf.org
> > > Subject: Re: [art] verify envelope and who is email
> > >
> > > (as individual)
> > >
> > > Hi Pradeep,
> > >
> > > The applications you propose seem to accomplish the same thing as cry=
ptographic signatures and a PKI. Those technologies already exist. As far a=
s I can tell, the only functional difference is that they are optional to u=
se, and I gather you wish for something that is mandatory. The IETF can pro=
vide tools, but it cannot establish policy to force their deployment or use=
. That power belongs to governments.
> > >
> > > Ben.
> > >
> > > > On Oct 10, 2018, at 9:14 PM, pradeep xplorer <pradeepan88@hotmail.c=
om> wrote:
> > > >
> > > > I am again stressing the need for two applications
> > > > Verify envelope that verifies who the sender is
> > > > Who is email address that shows the credentials or identity documen=
ts or certificates of a email owner. This can be password protected or show=
n only if the user has the public key of the email owner.
> > > > With these laws can be enacted so emails can be used instead of sen=
ding registered snail mail
> > > > Right now banks and govts are getting away with solving my situatio=
n based on emails. I have health problems because of lack of lifestyle that=
 cannot be postponed
> > > > And all these could have been delivered by engineers on payroll yea=
rs ago
> > > > All desktops using emails should have access to these standard appl=
ications
> > > > Pradeep Kumar xplorer
> > > > _______________________________________________
> > > > art mailing list
> > > > art@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/art
> > >
> >

--_000_SG2PR0302MB26068B64905157C250BC7D2EB7E10SG2PR0302MB2606_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
>From the answers it looks like theres no application verifyenvelope like pu=
tty that can be downloaded&nbsp;<span style=3D"color: rgb(0, 0, 0); font-fa=
mily: Calibri, Helvetica, sans-serif; font-size: 12pt;">and used to verify =
envelope of an inbound email because some
 combination of human intelligence and software has to be used to do this t=
ask and cannot be completely automated. It is not available on each and eve=
ry desktop that can recieve emails. OR this is not implemented and released=
 because of some policy decisions.
 By that i mean the expertise and technology is available making it widely =
available as a app that can be downloaded and used would lead to problems f=
or some and they are against it becoming available.</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Yakov Shafranovich &l=
t;yakov@nightwatchcybersecurity.com&gt;<br>
<b>Sent:</b> Thursday, October 11, 2018 8:47 AM<br>
<b>To:</b> Ben Campbell<br>
<b>Cc:</b> pradeepan88@hotmail.com; art@ietf.org<br>
<b>Subject:</b> Re: [art] verify envelope and who is email</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">To be clear, this accomplishes verification of var=
ious types of<br>
Internet identifiers like email addresses against other Internet<br>
identifiers like domain names. These protocols do not necessarily<br>
address the issue of how to verify something on the Internet against a<br>
real world identity, although the PKI pieces may lead in that<br>
direction.<br>
<br>
Thanks<br>
On Wed, Oct 10, 2018 at 11:14 PM Yakov Shafranovich<br>
&lt;yakov@nightwatchcybersecurity.com&gt; wrote:<br>
&gt;<br>
&gt; The SPF and DKIM protocols allow verification of the envelope against<=
br>
&gt; a domain name and some of the headers / content respectively<br>
&gt; (depending on configuration). There are additional protocols like<br>
&gt; DMARC, DANE, etc. which provide additional functionality in this<br>
&gt; space. The initial development of these protocols was done in IRTF's<b=
r>
&gt; ASRG group back in 2001 and on. However, as Ben said, we cannot force<=
br>
&gt; people to use them.<br>
&gt;<br>
&gt; May of these are in-use today by most major email providers. For<br>
&gt; example, Gmail added DKIM support back in 2008:<br>
&gt; <a href=3D"https://gmail.googleblog.com/2008/07/fighting-phishing-with=
-ebay-and-paypal.html">
https://gmail.googleblog.com/2008/07/fighting-phishing-with-ebay-and-paypal=
.html</a><br>
&gt;<br>
&gt; Here is information about Hotmail support for SPF and DKIM:<br>
&gt; <a href=3D"https://wordtothewise.com/2012/12/hotmail-moves-to-spf-auth=
entication/">
https://wordtothewise.com/2012/12/hotmail-moves-to-spf-authentication/</a><=
br>
&gt; <a href=3D"https://blogs.msdn.microsoft.com/tzink/2016/10/18/hotmailou=
tlook-com-evaluates-dkim-a-little-differently-than-office-365/">
https://blogs.msdn.microsoft.com/tzink/2016/10/18/hotmailoutlook-com-evalua=
tes-dkim-a-little-differently-than-office-365/</a><br>
&gt;<br>
&gt; A more extreme case of how DKIM digital signatures were used is the<br=
>
&gt; case of Wikileaks using Gmail's DKIM keys to verify the authenticity<b=
r>
&gt; of stolen/leaked DNC emails in 2016:<br>
&gt; <a href=3D"https://blog.erratasec.com/2016/10/yes-we-can-validate-wiki=
leaks-emails.html">
https://blog.erratasec.com/2016/10/yes-we-can-validate-wikileaks-emails.htm=
l</a><br>
&gt;<br>
&gt; Thanks<br>
&gt; On Wed, Oct 10, 2018 at 11:08 PM Ben Campbell &lt;ben@nostrum.com&gt; =
wrote:<br>
&gt; &gt;<br>
&gt; &gt; To be clear, the IETF is also not a software development shop. We=
 make standards, not code. We cannot make people implement, deploy or use t=
hem.<br>
&gt; &gt;<br>
&gt; &gt; Digital signatures will only help your problem if people use them=
, and they are not used widely. But if we introduce even more tools to acco=
mplish a subset of the same thing, they will likely be used even less widel=
y.<br>
&gt; &gt;<br>
&gt; &gt; But to your specific question: A DuckDuckGo search for =93s/mime =
for android=94 turns up several hits. I am not an Android user, so I do not=
 have experience with any of them.<br>
&gt; &gt;<br>
&gt; &gt; Ben.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt; On Oct 10, 2018, at 9:55 PM, pradeep xplorer &lt;pradeepan88=
@hotmail.com&gt; wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Please be specific where are the tools. I am using android w=
here are the tools in Google play store?. I am saying tools are not availab=
le. If i am wrong correct me point me to the tools available for major plat=
forms.<br>
&gt; &gt; &gt; Pradeep Kumar xplorer<br>
&gt; &gt; &gt; From: Ben Campbell &lt;ben@nostrum.com&gt;<br>
&gt; &gt; &gt; Sent: Thursday, October 11, 2018 8:11:52 AM<br>
&gt; &gt; &gt; To: pradeep xplorer<br>
&gt; &gt; &gt; Cc: Yakov Shafranovich; art@ietf.org<br>
&gt; &gt; &gt; Subject: Re: [art] verify envelope and who is email<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; (as individual)<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Hi Pradeep,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The applications you propose seem to accomplish the same thi=
ng as cryptographic signatures and a PKI. Those technologies already exist.=
 As far as I can tell, the only functional difference is that they are opti=
onal to use, and I gather you wish for something
 that is mandatory. The IETF can provide tools, but it cannot establish pol=
icy to force their deployment or use. That power belongs to governments.<br=
>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Ben.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; On Oct 10, 2018, at 9:14 PM, pradeep xplorer &lt;pradee=
pan88@hotmail.com&gt; wrote:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; I am again stressing the need for two applications<br>
&gt; &gt; &gt; &gt; Verify envelope that verifies who the sender is<br>
&gt; &gt; &gt; &gt; Who is email address that shows the credentials or iden=
tity documents or certificates of a email owner. This can be password prote=
cted or shown only if the user has the public key of the email owner.<br>
&gt; &gt; &gt; &gt; With these laws can be enacted so emails can be used in=
stead of sending registered snail mail<br>
&gt; &gt; &gt; &gt; Right now banks and govts are getting away with solving=
 my situation based on emails. I have health problems because of lack of li=
festyle that cannot be postponed<br>
&gt; &gt; &gt; &gt; And all these could have been delivered by engineers on=
 payroll years ago<br>
&gt; &gt; &gt; &gt; All desktops using emails should have access to these s=
tandard applications<br>
&gt; &gt; &gt; &gt; Pradeep Kumar xplorer<br>
&gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; art mailing list<br>
&gt; &gt; &gt; &gt; art@ietf.org<br>
&gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/art">h=
ttps://www.ietf.org/mailman/listinfo/art</a><br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
</div>
</span></font></div>
</body>
</html>

--_000_SG2PR0302MB26068B64905157C250BC7D2EB7E10SG2PR0302MB2606_--


From nobody Thu Oct 11 00:48:54 2018
Return-Path: <Shawn.Steele@microsoft.com>
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 DAF2D130E07; Thu, 11 Oct 2018 00:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 s3wH0LQltJI5; Thu, 11 Oct 2018 00:48:40 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0100.outbound.protection.outlook.com [104.47.42.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15340130E43; Thu, 11 Oct 2018 00:48:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y9I7ITzB/r2G14/ce+8mNlwmgtacWl4SPlhcghJdEQU=; b=BrPIQlhpnssaM6Hsyu7Q/d5ANW4rEdEvvy2X2aE8PhkfFuuAkLC9FkCGH7lrfEZmP4Z7rJT8d2AQJnyWR9c0TaOppB9Mo50hzYLwmfa9ILuT9Gat3AhBreq7t8moscW5rI+WAFK1TqunnjueCdLQeyr766eTJYqy+UMjg44kkjI=
Received: from MW2PR2101MB0908.namprd21.prod.outlook.com (52.132.152.28) by MW2PR2101MB0892.namprd21.prod.outlook.com (52.132.152.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.7; Thu, 11 Oct 2018 07:48:38 +0000
Received: from MW2PR2101MB0908.namprd21.prod.outlook.com ([fe80::c5c5:865d:9a44:6c89]) by MW2PR2101MB0908.namprd21.prod.outlook.com ([fe80::c5c5:865d:9a44:6c89%4]) with mapi id 15.20.1228.011; Thu, 11 Oct 2018 07:48:38 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <john-ietf@jck.com>, "art@ietf.org" <art@ietf.org>, "i18nrp@ietf.org" <i18nrp@ietf.org>
Thread-Topic: [art] Use Unicode if Using Unicode?
Thread-Index: AdRgyyu11+nsTlEOSXCvakwfGZPatwAOxVeAAAt0f9A=
Date: Thu, 11 Oct 2018 07:48:38 +0000
Message-ID: <MW2PR2101MB0908D4D3EB13FFAA07AD610682E10@MW2PR2101MB0908.namprd21.prod.outlook.com>
References: <MW2PR2101MB0908F009734817997508274282E00@MW2PR2101MB0908.namprd21.prod.outlook.com> <FB4FE0D631E6F6D4C72B19A1@PSB>
In-Reply-To: <FB4FE0D631E6F6D4C72B19A1@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.35.70.68]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MW2PR2101MB0892; 6:IUH8Wn0cNPxjeG+Lcx46wZpq8Dd4X7xgvwE38ySL/duTMcQfD2sjmP9+CDK7aJflgcgC3R8xQPdmJZ7SAaNxUiugYxPHtzp/PHLivPWDpL1O7NLo3amQKs/+v1XrfDUHDx7yuzu/e/vluzrAa2USIGzryYqWNaPID/hcIqq9J9O3P18vwiBfzjE54TD7GDsAWfuuimiOUQdsAm19qhtvgYRr1xRJDNX3aeA3Sv9KG5OF/xs2wSfebxmzA5Z7clfB67aw9Xg8aMoNJ+LR2sae/1b4wHHJ+vTZJyXkfC3Z1NN9A6yXfNtb6kziF7jSTz2hq8n8XKv+OIfmFyp+jYPWqGcWOLb3KSkTfnbDMO8vC2w0edv9snmhRP+uvvqVQ/ovPAIUiTvCJzYX+Dw0EVtDeF6saw5PoCFH+8z3tZhbOEb+vDj1tQCBoEK2YtfABrZ7+dSJXSJSkx3V/meRjI6DAg==; 5:HbxIJ/SVCDzTBHtGrdhwoEXAbsNYj6MJFA5woTDBilJFy/kABTtSupqcgNMpCKiu71OgSvmMzCZyVThBImhdKO0EqBG0Ntinhr8LQ6wfQFl1DerXPOw+hCo9NcA10RGViofxg4rVWnDifhkKZDUPWCB5wQ4DiJ3/eNrHANAGZik=; 7:JmGZh95elwezeamWTUgNbdq3UO0t8ewb4VkOoA8ev5561TBPb83yALjbhcgn2rgCv0vQKMlqUHmVBTqTKNvenIw3qr75ZqFMaGlXQb+ysygag4TF6VT6URZGzAh8j0TXU9uaW7OTmTZDbjdk9KIAoaznNCnhrBifKJOu9yW2czuC/R7EkwQfdVkRFXSIj+YfACmvS2Z2JIwsLsQTd23ms3hbEYdB1jnRVhUcuWmJZdqVnyufWgxssn2n5wZTGRHw
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2a5de695-9c6c-4aa5-6752-08d62f4df4c2
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:MW2PR2101MB0892; 
x-ms-traffictypediagnostic: MW2PR2101MB0892:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Shawn.Steele@microsoft.com; 
x-microsoft-antispam-prvs: <MW2PR2101MB08927C2F6199866B5998BE4682E10@MW2PR2101MB0892.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317)(269456686620040)(28532068793085)(89211679590171); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(3231355)(944501410)(52105095)(2018427008)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991055); SRVR:MW2PR2101MB0892; BCL:0; PCL:0; RULEID:; SRVR:MW2PR2101MB0892; 
x-forefront-prvs: 08220FA8D6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(346002)(376002)(366004)(136003)(189003)(199004)(13464003)(74316002)(105586002)(11346002)(6246003)(478600001)(97736004)(446003)(25786009)(2201001)(86362001)(86612001)(55016002)(316002)(110136005)(7696005)(26005)(53936002)(186003)(9686003)(102836004)(99286004)(76176011)(22452003)(2906002)(71190400001)(3846002)(71200400001)(6116002)(2501003)(6436002)(33656002)(53546011)(68736007)(5660300001)(6506007)(5250100002)(486006)(14454004)(476003)(305945005)(7736002)(2900100001)(10290500003)(72206003)(106356001)(229853002)(8936002)(66066001)(10090500001)(8990500004)(8676002)(81156014)(81166006)(256004)(14444005); DIR:OUT; SFP:1102; SCL:1; SRVR:MW2PR2101MB0892; H:MW2PR2101MB0908.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: P1mW7sux4TBJ0D/MrRwSJYKkFAtVKTevy5RqHzdSyRkYN/6kZlEtvAU7WjGQMQP4JnjcL4gKQ2YgZe7EsOx/SGn2E0MpSN/MQXNmLyTicbOUO9PT6yHU447DaSOrQuQD/t6jNWZk6E+k+r4qAg9lWLJiJ3zz/CkiijtMy3UTXxLuKbpG7ZXlHKhebqt7LGSw1QmqG4O4Om3n+tpN6zmOCJ/lzqPnQRDUiBEqLai5FnIvqr7jT+zaHL4BUeQvz6U2AB7jvaHRgfqRzJ08vsIufKdDxoBMcydhAh3mRis3d/f14h3lxd9VPsY+2dTK8Nc+SWoXDJBqIM6gLco9+sOB/iPzvC/0j/frULiDlt1e/Sw=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2a5de695-9c6c-4aa5-6752-08d62f4df4c2
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2018 07:48:38.4247 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR2101MB0892
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/YorYM-_Mc6345_bAuvL0KxfkTXg>
Subject: Re: [art] Use Unicode if Using Unicode?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 07:48:45 -0000

VGhlIGZpbGUgVW5pY29kZSBnZW5lcmF0ZXMgY2FuIGJlIHVzZWQgZWl0aGVyIHdpdGggdGhlIFVU
UzQ2IGNvbXBhdGliaWxpdHkgY2hhcmFjdGVycyBvciB3aXRob3V0LiAgVG8gdXNlIHlvdXIgdGVy
bXMsIGl0IGJvdGggcHJvdmlkZXMgZGF0YSB0aGF0IGNvbmZvcm1zIHRvIHRoZSBJRE5BMjAwOCBy
dWxlcy4uLiBhbmQgaHlicmlkIHZlcnNpb25zLiAgSWYgeW91IGNob29zZSB0aGUgYXBwcm9wcmlh
dGUgaW5mb3JtYXRpb24gd2hlbiByZWFkaW5nIHRoZSBJZG5hTWFwcGluZ1RhYmxlLnR4dCB5b3Ug
c2hvdWxkIGhhdmUgZXhhY3RseSB0aGUgdGFibGUgZXhwZWN0ZWQuICBJbiBwYXJ0aWN1bGFyIHRo
ZSBOVjggYW5kIFhWOCB0YWdnZWQgY2hhcmFjdGVycyBJIGJlbGlldmUgeW91J2QgcHJlZmVyIHRv
IGV4Y2x1ZGUuDQoNCkknbSB1bmF3YXJlIG9mIG90aGVyIGRpZmZlcmVuY2VzLiAgSSBjb3VsZCBh
bHNvIGJlIGluIGVycm9yLCBJIGhhdmVuJ3QgYWN0dWFsbHkgZG9uZSBhbiBleGhhdXN0aXZlIGNv
bXBhcmlzb24gb2YgdGhlIEluZGFNYXBwaW5nVGFibGUudHh0IGRhdGEgdnMgZ2VuZXJhdGVkIGRh
dGFzZXRzIHZpYSB0aGUgcnVsZXMuDQoNClRoZSBJZG5hTWFwcGluZ1RhYmxlLnR4dCBmaWxlIGFs
c28gaXNuJ3QgImF1dGhvcml0YXRpdmUsIiBob3dldmVyIHNpbmNlIGl0J3MgZ2VuZXJhdGVkIGZy
b20gdGhlIFVuaWNvZGUgZGF0YSBhbmQgdGhlIHJ1bGVzIGluIHRoZSBSRkNzLCB0aGUgZmlsZSBz
aG91bGQgYmUgYXMgYWNjdXJhdGUgYXMgYW55IG90aGVyIHJlZmVyZW5jZS4gIA0KDQpVbmljb2Rl
IGlzIGF3YXJlIG9mIHRoZSBpbXBvcnRhbmNlIG9mIHRoZSBzdGFiaWxpdHkgb2YgdGhlIHZhbGlk
IGNoYXJhY3RlciBzZXQsIHNvIHByb2JhYmx5IHRoZSBiZXN0IHRpbWUgdG8gcmV2aWV3IGFuZCB2
ZXQgdGhlIFVuaWNvZGUgY2hhbmdlcyBmb3IgbmV3IFVuaWNvZGUgdmVyc2lvbnMgd291bGQgYmUg
ZHVyaW5nIHRoZSBVbmljb2RlIHByb2Nlc3MsIHByaW9yIHRvIHJlbGVhc2UuICBBZnRlciBhIFVu
aWNvZGUgdmVyc2lvbiB3YXMgcmVsZWFzZWQsIGFueSBkaXNhZ3JlZW1lbnRzIHdvdWxkIGxlYWQg
dG8gcHJvYmxlbWF0aWMgY29uZnVzaW9uIChhcyB3ZSd2ZSBzZWVuIGJlZm9yZS4pDQoNCkl0IHNl
ZW1zIHRvIG1lIHRoYXQgdXNpbmcgdGhlIElkbmFNYXBwaW5nVGFibGUudHh0IC0gcGVyaGFwcyB3
aXRoIGd1aWRhbmNlIGFzIHRvIHByb3BlciB1c2FnZSAtIHdvdWxkIHJlZHVjZSBkZWxheXMgaW4g
YWRvcHRpbmcgbmV3IGNoYXJhY3RlcnMuDQoNCi1TaGF3bg0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogSm9obiBDIEtsZW5zaW4gPGpvaG4taWV0ZkBqY2suY29tPiANClNlbnQ6
IFdlZG5lc2RheSwgT2N0b2JlciAxMCwgMjAxOCA3OjAxIFBNDQpUbzogU2hhd24gU3RlZWxlIDxT
aGF3bi5TdGVlbGVAbWljcm9zb2Z0LmNvbT47IGFydEBpZXRmLm9yZzsgaTE4bnJwQGlldGYub3Jn
DQpTdWJqZWN0OiBSZTogW2FydF0gVXNlIFVuaWNvZGUgaWYgVXNpbmcgVW5pY29kZT8NCg0KU2hh
d24sDQoNCkknbSBjb25mdXNlZCBhYm91dCB3aGF0IHlvdSBhcmUgc3VnZ2VzdGluZywgc28gbGV0
IG1lIGNsYXJpZnkgd2hlcmUgSSdtIGNvbmZ1c2VkIGFuZCB0aGVuIGhvcGUgeW91IGNhbiBlbmxp
Z2h0ZW4gbWUuLi4NCg0KLS1PbiBXZWRuZXNkYXksIE9jdG9iZXIgMTAsIDIwMTggMTk6MDIgKzAw
MDAgU2hhd24gU3RlZWxlIDxTaGF3bi5TdGVlbGU9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYu
b3JnPiB3cm90ZToNCg0KPiBUaGUgZHJhZnQgc3RhdGVzICJJdCBmdXJ0aGVyIHN1Z2dlc3RzIGZv
ciB0aGUgSUVURiBhIHBhdGggZm9yd2FyZCANCj4gcmVnYXJkaW5nIGVuc3VyaW5nIElETkEyMDA4
IGZvbGxvd3MgdGhlIGV2b2x1dGlvbiBvZiB0aGUgVW5pY29kZSANCj4gU3RhbmRhcmQiIGFuZCAi
dGhpcyBkb2N1bWVudCByZXF1ZXN0cyB0aGF0IElBTkEgdXBkYXRlIHRoZSB0YWJsZXMgdG8gDQo+
IFVuaWNvZGUgMTEuIg0KDQo+IEVhY2ggVW5pY29kZSB2ZXJzaW9uIGNyZWF0ZXMgYSBkYXRhIGZp
bGUgd2l0aCBpbmZvcm1hdGlvbiBmcm9tIA0KPiBhcHBseWluZyB0aGUgSUROQTIwMDggcnVsZXMg
dGhhdCBjYW4gYmUgdXNlZCBmb3IgSUROQSBtYXBwaW5nIA0KPiBhbGdvcml0aG1zLiAgKEluZGVl
ZCwgdGhhdCdzIHdoZXJlIFdpbmRvd3MgZ2V0cyB0aGUgZGF0YSBmcm9tKS4NCg0KVGFraW5nIGEg
aGFsZi1zdGVwIGJhY2ssIElETkEgaW1wb3NlcyB0d28gcmVxdWlyZW1lbnRzIGZvciBuZXcgdmVy
c2lvbnMgb2YgVW5pY29kZSwgYm90aCBvZiB3aGljaCBhcmUgYWRkcmVzc2VkIGJ5IHRoZSBwcmVz
ZW50IGRyYWZ0LiAgT25lIGlzIHRoYXQgdGhlIGNoYW5nZXMgaW4gdGhlIG5ldyB2ZXJzaW9uIGJl
IGV4YW1pbmVkIHRvIGVuc3VyZSB0aGF0IG5vdGhpbmcgbmV3IGhhcyBiZWVuIGRvbmUgdGhhdCBy
ZXF1aXJlcyBjaGFuZ2VzIHRvIElETkEgKG1vc3QgbGlrZWx5IGFkZGluZyBleGNlcHRpb25zIG9y
IHJ1bGVzIGZvciBwYXJ0aWN1bGFyIGNvZGUgcG9pbnRzKSBvciBjYXJlZnVsIGV4cGxhbmF0aW9u
IHNvbWV3aGVyZS4gIE5vIG9uZSBJIGtub3cgb2YgZXhwZWN0ZWQgdGhhdCBwcm92aXNpb24gd291
bGQgYmUgZXhlcmNpc2VkIHZlcnkgb2Z0ZW4gYnV0LCBmb3IgYSB2YXJpZXR5IG9mIHJlYXNvbnMs
IHRoZSBjb25zZW5zdXMgd2FzIHRoYXQgaXQgd2FzIGFuIGltcG9ydGFudA0Kc2FmZWd1YXJkLiAg
IFRoZSBvdGhlciB3YXMgdGhhdCB0aGUgSUROQSBydWxlc2V0IGJlIHJ1biBhZ2FpbnN0DQp0aGUg
Y2hhcmFjdGVycyBhbmQgcHJvcGVydGllcyBpbiB0aGUgVW5pY29kZSBDaGFyYWN0ZXIgRGF0YWJh
c2UgdG8gcHJvZHVjZSBhIHRhYmxlIHJlZmxlY3RpbmcgdGhlIGNvbWJpbmF0aW9uIG9mIHRoYXQg
dmVyc2lvbiBvZiBVbmljb2RlIGFuZCBJRE5BLCBhcyBtb2RpZmllZCwgYXQgdGhhdCB0aW1lLiAg
VGhhdCB0YWJsZSB3YXMgKGFuZCBpcykgdG8gYmUgc3RvcmVkIHdpdGggSUFOQSBidXQsIHdoaWxl
IHdlIGV4cGVjdCBpdCB0byBiZSBjaGVja2VkIGNhcmVmdWxseSBmb3IgYWNjdXJhY3ksIGl0IGlz
IG5vdCBhY3R1YWxseSBhdXRob3JpdGF0aXZlDQotLSBvbmx5IHRoZSBydWxlcyBhbmQgY2F0ZWdv
cmllcyBzcGVjaWZpZWQgYnkgSUROQSAoYW5kIHRoZSBVbmljb2RlIHByb3BlcnRpZXMgdXNlZCB0
byBzdXBwb3J0IHRoZW0pIGFyZS4NCg0KVGhlIGRpc2N1c3Npb24gaW4gUkZDIDU4OTUgbm90d2l0
aHN0YW5kaW5nLCBvbmUgb2YgdGhlIGNyaXRpY2FsbHkgaW1wb3J0YW50IHByb3BlcnRpZXMgb2Yg
SUROQTIwMDggaXMgdGhhdCBVLWxhYmVscyBhbmQgQS1sYWJlbHMgYXJlIGR1YWxzOiBvbmUgY2Fu
IGdldCBmcm9tIG9uZSB0byB0aGUgb3RoZXIgYW5kIGJhY2sgd2l0aG91dCBhbnkgbG9zcyBvZiBp
bmZvcm1hdGlvbi4gIFRoYXQgcmV2ZXJzaWJpbGl0eSBpcyB0cnVlIGluIG9ubHkgc29tZSBjYXNl
cyBmb3IgVW5pY29kZSBub3JtYWxpemF0aW9uIChlc3BlY2lhbGx5IHdpdGggY29tcGF0aWJpbGl0
eSBub3JtYWxpemF0aW9uKSBvciBjYXNlIGZvbGRpbmcsIG11Y2ggbGVzcyBmb3Igb3RoZXIgbWFw
cGluZyBzY2VuYXJpb3MuICBTbyBJIGRvbid0IHVuZGVyc3RhbmQgd2hhdCBzb3J0IG9mICJtYXBw
aW5nIiB5b3UgYXJlIHRhbGtpbmcgYWJvdXQuDQoNClRoZSBvbmx5IFVuaWNvZGUtY3JlYXRlZCBJ
RE4gZGF0YSBmaWxlcyBJJ20gYXdhcmUgb2YgYXJlIHRob3NlIGFzc29jaWF0ZWQgd2l0aCB0aGUg
VVRTIzQ2IGVmZm9ydC4gIEJlY2F1c2UgVVRTIzQ2IG1ha2VzIHJlY29tbWVuZGF0aW9ucyB0aGF0
IGFyZSBpbmNvbnNpc3RlbnQgd2l0aCBJRE5BMjAwOCwgaWYgTWljcm9zb2Z0IGlzIHVzaW5nIHRo
b3NlIHRhYmxlcywgaXRzIHVzYWdlIGlzIG5vbi1jb25mb3JtaW5nIHRvIElETkEyMDA4LiAgSSBj
ZXJ0YWlubHkgY2Fubm90IHByZXZlbnQgTWljcm9zb2Z0IGZyb20gZG9pbmcgdGhhdCAoYW5kIHdv
dWxkbid0IHRyeSksIGJ1dCBpdCB3b3VsZCBjZXJ0YWlubHkgbm90IGJlIGNvbnNpc3RlbnQgd2l0
aCBnZW5lcmFsIGludGVyb3BlcmFiaWxpdHkgb2YgSUROcyBvciB3aGF0IGlzIGtub3duIGVsc2V3
aGVyZSBhcyBVbml2ZXJzYWwgQWNjZXB0YW5jZSBvZiB0aG9zZSBkb21haW4gbmFtZXMuDQoNCj4g
SWYgdGhlIGdvYWwgaXMgdG8gImZvbGxvdyB0aGUgZXZvbHV0aW9uIG9mIHRoZSBVbmljb2RlIFN0
YW5kYXJkIiBhbmQgDQo+IHRoZSBVbmljb2RlIFN0YW5kYXJkIGlzIHByb3ZpZGluZyBkYXRhIHRo
YXQgY29uZm9ybXMgdG8gdGhlIElETkEgDQo+IHJ1bGVzLCB0aGVuIHdoeSBub3QganVzdCBwb2lu
dCBkaXJlY3RseSB0byB0aGUgVW5pY29kZSBkZXJpdmVkIHRhYmxlcz8NCg0KVGhlIHNpbXBsZXN0
IGFuc3dlciB0byB5b3VyIHF1ZXN0aW9uIGlzIHRoYXQsIHVubGVzcyBJJ3ZlIG1pc3NlZCBzb21l
dGhpbmcsIHRoZSBjb25kaXRpb25hbCBpcyBmYWxzZTogdGhlIFVuaWNvZGUgU3RhbmRhcmQgaXMg
bm90IHByb3ZpZGluZyBkYXRhIHRoYXQgY29uZm9ybXMgdG8gdGhlIElETkEyMDA4IHJ1bGVzLiAg
SW5zdGVhZCwgdGhlIGRhdGEgdGhleSBhcmUgcHJvdmlkaW5nIGlzIG1vcmUgbGlrZSBvbmUgb2Yg
dGhlIGNyZWF0aXZlDQpJRE5BMjAwMy1JRE5BMjAwOCBoeWJyaWRzIHRvIHdoaWNoIFBhdHJpayBy
ZWZlcnMuDQoNCiAgIGJlc3QsDQogICAgIGpvaG4NCg0K


From nobody Thu Oct 11 02:35:41 2018
Return-Path: <paf@netnod.se>
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 A04E9130DD4 for <art@ietfa.amsl.com>; Thu, 11 Oct 2018 02:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netnod-se.20150623.gappssmtp.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 ojeVf0PhhSq1 for <art@ietfa.amsl.com>; Thu, 11 Oct 2018 02:35:30 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 853FB130DD0 for <art@ietf.org>; Thu, 11 Oct 2018 02:35:30 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id q39-v6so6143538lfi.8 for <art@ietf.org>; Thu, 11 Oct 2018 02:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netnod-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kdRiZTUBOmIDu99b2P9IK4QITFBn3/jwLklUjVb0GcE=; b=YXmpgZXzdU3HzkLz4iCmINV7dEJ5eTNc91lLsCVkMUJMmRaGJAsXPrMP/9slTTyWuY qQMtDDWlBU+1ReoniIcJezRj1ugOvREhbZD7+wepmhkXowGWvDOGTCog2HIxZeq4eI/v q7fDg7nW6KYfsDVjy/TaRZaoPjF0/3mnJgvlpnSrKbuSMvPM/vYW/U8fWmSge3/zUlKL W8x7z1NHKuNqjokPZ+8R+oiD1caHFWAvBeH6kaWSPExhaiecZePR240u5vODlZlZANwh Q7vvJRXEOXukh1nvpPsiM6GG0AI0/ZLQTc48+kKXpU6aSdst8p6ZifyF6mV2qtJcbUbM LeLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kdRiZTUBOmIDu99b2P9IK4QITFBn3/jwLklUjVb0GcE=; b=ukKDaEkzQvM2/HU/Q8KG/3atQ00TLMRzLFi5QAbv/UftmrzgE/iHCjTWvZiLUedn4U z1J6OIaSWCe3UGnnoOEHGEbUAU0Wvjj3RTNlTCtuGyzHjXv45j4RLsK/zu1lOR8YIVW6 eHpJvN0uUp3O0pNg54ePX3bcS7cCIeVzJGiXJP2QLlTn8Ls7C0ZRbl3LIvXEodlE5M7C yBHoU3T3RhtLr2M4KEMM34fCuqFEl+jxzntHgs5lc/jqYSNvaS8cYJ+gaiQ6ulpwi3gH sj5X2MZXAJmXt6xLazhM1S/jxBzHrhrfMJz0g9ug1Z1SWLeReiiesMO9H1NGRYOVCzFH t7Lw==
X-Gm-Message-State: ABuFfohzf/CVYCwiE+pbGgeXQIWaO4OxaiFGG1QihtziX6gkiFyjPPTw AFIfxjX/ETViCgKfT1FK91lRxg==
X-Google-Smtp-Source: ACcGV61UqjauHRKsmYES339+nZFqOeeLEt3GwMPfYTUr/f1hCt41GxZcVJeX1b3hxyHnXsykfo3E8A==
X-Received: by 2002:a19:2b11:: with SMTP id r17-v6mr595808lfr.128.1539250528314;  Thu, 11 Oct 2018 02:35:28 -0700 (PDT)
Received: from ?IPv6:2a01:3f0::4b:8674:4edc:121e:1a2f? ([2a01:3f0:0:4b:8674:4edc:121e:1a2f]) by smtp.gmail.com with ESMTPSA id 12-v6sm5945573ljj.82.2018.10.11.02.35.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Oct 2018 02:35:27 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@netnod.se>
X-Mailer: iPad Mail (16B5077c)
In-Reply-To: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
Date: Thu, 11 Oct 2018 11:35:27 +0200
Cc: "art@ietf.org" <art@ietf.org>, "i18nrp@ietf.org" <i18nrp@ietf.org>, "iab@iab.org" <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BB2EAE7-FB93-4654-A1B5-D0C8C9CCE061@netnod.se>
References: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
To: Gabriel Montenegro <g.e.montenegro@hotmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/HbpP_bLts3GReuMy_yRnRWWT2xQ>
Subject: Re: [art] editorial comments on draft-faltstrom-unicode11-04.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 09:35:34 -0000

Thanks, will take care of these editorial issues...

   Patrik

> On 10 Oct 2018, at 21:12, Gabriel Montenegro <g.e.montenegro@hotmail.com> w=
rote:
>=20
> I looked at rev04 and have some editorial comments and nits. One such gene=
ral comment is that there is a lack of commas in the text, which makes for d=
ifficult reading.
>=20
> Abstract:
>=20
> s/IDNA2008 do give/IDNA2008 gives/
> s/document suggests/document suggest/
>=20
> Introduction:
>=20
> Points out that IDNA2008 "is specified in a series of documents (see Secti=
on Section 3.1). " That still leaves unanswered what a reasonable overview i=
s for those of us who are absolute IDNA newbs. So may I suggest something li=
ke "is specified in a series of documents (see Section Section 3.1), but for=
 an overview see XXXX." [I suppose rfc5894 is the proper overview doc here?]=

>=20
> Section 3.1:
>=20
> s/DISSALOWED/DISALLOWED/
> s/changes where acceptable/changes were acceptable/
>=20
> Section 3.2:
>=20
> s/implies stayed at Unicode Standard/implies staying at Unicode Standard/=20=

> [Here, I suppose it's staying, but "stayed" sounds wrong, please double-ch=
eck.]
>=20
> s/having a very diverse/having very diverse/
>=20
> Can't parse: "that registry operators to based on the IDNA2008 specificati=
on create additional rules...".=20
> Perhaps you meant "that led registry operators to (based on the IDNA2008 s=
pecification) create additional rules..."?
>=20
> s/characters permissable/characters permissible /=20
>=20
> section 4.3:
>=20
> s/ZANABZAR/ZANABAZAR
>=20
>=20
> Gabriel
>=20
>> -----Original Message-----
>> From: IAB <iab-bounces@iab.org> On Behalf Of Patrik F=C3=A4ltstr=C3=B6m
>> Sent: 6 October, 2018 22:54
>> To: i18nrp@ietf.org; iab@iab.org
>> Subject: [IAB] draft-faltstrom-unicode11-04.txt
>>=20
>> All,
>>=20
>> Version -04 of this draft was just posted.
>>=20
>> Background: As we all know IDNA2008 is an algorithm that applied to Unico=
de
>> gives a subset of code points which are permissible for in turn registrie=
s and
>> others to create subsets from to be used in their respective policies.
>>=20
>> Being the appointed expert for the IANA registry I have flagged for IAB c=
hanges
>> made to Unicode that I feel must be discussed in IETF, and here is the
>> document with my proposal (details are in the draft).
>>=20
>> In short the draft proposes (just like RFC 6452) IETF continue to follow U=
nicode
>> Standard without adding exceptions to the IDNA2008 algorithm, EVEN IF
>> changes are made that are incompatible to earlier versions of Unicode.
>>=20
>> The choices for IETF when things like this happens are:
>>=20
>> 1. Keep IDNA2008 with no exceptions
>>=20
>> 2. Keep IDNA2008 with exceptions
>>=20
>> 3. Stop referring (directly) to Unicode as it is not stable enough
>>=20
>> Probably more choices than these...
>>=20
>> My proposal is [1], together with a more forceful push to strict IDNA2008=

>> adoption. No IDNA2003, no UTS#46, no homebrew mixes. Including that
>> registries really do a careful conservative selection of code points to b=
e used in
>> whatever context it is to be used.
>>=20
>>=20
>> The problem though is that this is *my* view. Sure, a few others have
>> randomly and "by pure luck" told me "this is ok".
>>=20
>> But is this a stable informed decision by IETF?
>>=20
>> This very fast turn into a process issue where IAB have asked for progres=
s, and
>> IETF is to deliver.
>>=20
>> And this is where I take a step back, and want IESG and IAB to make up th=
eir
>> mind. This group was created for I18N issues, we have a charter, but then=

>> what? Is this where drafts like these should be discussed?
>>=20
>> Maybe...
>>=20
>>   Patrik


From nobody Thu Oct 11 21:52:31 2018
Return-Path: <masinter@gmail.com>
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 31916128CB7; Thu, 11 Oct 2018 21:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no 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 iySk92g6NYUV; Thu, 11 Oct 2018 21:52:28 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 6FDE312F295; Thu, 11 Oct 2018 21:52:28 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id 80-v6so5222656pgh.10; Thu, 11 Oct 2018 21:52:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=message-id:sender:mime-version:to:from:subject:date:importance :thread-topic:in-reply-to:references; bh=BmghY2spsnZMmfZ48twCi6ZzkPL0Sl5GZPcFbAbfUBY=; b=esJm5LYXXWGxO7rSqFiMkIbRxCIX0D9iTUeHVo8j/OFuLkwpSnRkvU6AEkA016U3cZ 3EN5QmkMyj9eA1U/2vkvMzAqXoYPzYaz3j6EEQe1YdCBF5beVcZ3TuuwobnVXyo/2lHR wY1VmzTvwndkg5lszmdzk4+rpU23N8p5wlP5AoX/uSWsRZZFS4KLyw+LzuPUoZbln4pr E8T2naF8HM7uScqOZAEFqFeMhCrSwEjlLL2lCNw6qxLap+HugFKz6MwxXk1z2B2MmrLJ 5seJUgQLH0bUeNLrJ8fJbR6bjBVKexYtUOX4T+9/oHv6YsLhy/aVq2vMWwYjRypCXqqf bDHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:sender:mime-version:to:from:subject :date:importance:thread-topic:in-reply-to:references; bh=BmghY2spsnZMmfZ48twCi6ZzkPL0Sl5GZPcFbAbfUBY=; b=edOGcxqOv71hTapvpDqt6KJBwbSQ3HqWUm6+M6/+lnny50Jrc6mGFMKbWhDNcStulA U1LaKhSZI9xHeOXoM/NzkBuGkz0yw84RdJWdrvFP2WQlLRkeMsQQkuAMmBTIK9QrfXRH /ESJQbUOjdsIQoU+j9EA03nyHFfSGjuQR9tNnoj4EYo08CLQ8CnpQvzikjyuMYqZMbFE QdEkILRAEat4zjxPMmXknfG5mGzgOeEWGz8wdrAM+K3OnWDv2DnGPosCy30TRsIpZV7w 8uRDkYh9yA71OZ+5MutkBhNcXMfps6q/g5fphzo80oE8qD2F941Tt1w8MJiffa6oXhFg BepQ==
X-Gm-Message-State: ABuFfojtWL0H1Uf1DZi2zFCTccKnuw1ldJGjUDequoxH4p2Zjc/rXSHg aYX59zi07tNDH6WNQ5aonmFayu+F
X-Google-Smtp-Source: ACcGV63KIIrEhtel2w3jmMHX3b3wPBuLNhLkKxMS8JKmcZgUtk1rOuaqtyvPWVGOsUSLW+NgQR07fw==
X-Received: by 2002:a63:9c01:: with SMTP id f1-v6mr4004370pge.156.1539319947147;  Thu, 11 Oct 2018 21:52:27 -0700 (PDT)
Received: from ?IPv6:::ffff:192.150.23.129? (c-24-6-174-39.hsd1.ca.comcast.net. [24.6.174.39]) by smtp.gmail.com with ESMTPSA id g5-v6sm63999pfk.160.2018.10.11.21.52.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Oct 2018 21:52:26 -0700 (PDT)
Message-ID: <5bc0288a.1c69fb81.73f2f.0213@mx.google.com>
Sender: Larry Masinter <masinter@gmail.com>
MIME-Version: 1.0
To: "art@ietf.org" <art@ietf.org>, "i18nrp@ietf.org" <i18nrp@ietf.org>
From: Larry Masinter <LMM@acm.org>
Date: Thu, 11 Oct 2018 21:52:28 -0700
Importance: normal
X-Priority: 3
Thread-Topic: [art] Use Unicode if Using Unicode?
In-Reply-To: <MW2PR2101MB0908D4D3EB13FFAA07AD610682E10@MW2PR2101MB0908.namprd21.prod.outlook.com>
References: <MW2PR2101MB0908F009734817997508274282E00@MW2PR2101MB0908.namprd21.prod.outlook.com> <FB4FE0D631E6F6D4C72B19A1@PSB> <MW2PR2101MB0908D4D3EB13FFAA07AD610682E10@MW2PR2101MB0908.namprd21.prod.outlook.com>
Content-Type: multipart/alternative; boundary="_27E5E152-D49A-46EE-9DFB-47591A9551FD_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/4CxPd8jVqw3EPQY-ym3DTruRWh0>
Subject: Re: [art] [I18nrp]  Use Unicode if Using Unicode?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2018 04:52:31 -0000

--_27E5E152-D49A-46EE-9DFB-47591A9551FD_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

No matter what path you take for new RFCs, implementations will lag, and so=
me choices for strings used for domain names, (LHS of) email addresses and =
short URLs will have problems=20
1) When put through different implementations of normalization (IDNA2008 vs=
 2003 vs. some exceptions)
2) When used in user interfaces for comparison or validation or comparison =
(in the address bar or rollover links)
3) When scanning text for picking out URLS
4) when used in print or other media (in an ad or written on a napkin)

These are in order of decreasing specificity, increasing =E2=80=9Cliberal d=
isplacement=E2=80=9D.
I think those who are choosing names to use (as domain name, email address,=
 short url) will want to use (4), no matter what rules the registry applies=
. Anyone registering a domain name, a user name at a mail host, or a (short=
) URL will want to choose names that they can print on a business card or a=
n ad or a roster and believe that their target audience can enter and get t=
he string intended.
And 1 < 2 < 3 < 4 as equivalence goes.=20

I don=E2=80=99t think it=E2=80=99s practical to redo all the protocols that=
 use these strings to pass along a tuple of string and context.

Larry
--
https://LarryMasinter.net



--_27E5E152-D49A-46EE-9DFB-47591A9551FD_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:147088828;
	mso-list-type:hybrid;
	mso-list-template-ids:1355941968 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:472454377;
	mso-list-type:hybrid;
	mso-list-template-ids:-977217784 -1 67698691 67698693 67698689 67698691 67=
698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style></head><body lang=3DEN-US link=3Dblue vlink=3D"#954F72"><div cla=
ss=3DWordSection1><p class=3DMsoNormal>No matter what path you take for new=
 RFCs, implementations will lag, and some choices for strings used for doma=
in names, (LHS of) email addresses and short URLs will have problems </p><o=
l style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoListParagraph =
style=3D'margin-left:0in;mso-list:l0 level1 lfo2'>When put through differen=
t implementations of normalization (IDNA2008 vs 2003 vs. some exceptions)</=
li><li class=3DMsoListParagraph style=3D'margin-left:0in;mso-list:l0 level1=
 lfo2'>When used in user interfaces for comparison or validation or compari=
son (in the address bar or rollover links)</li><li class=3DMsoListParagraph=
 style=3D'margin-left:0in;mso-list:l0 level1 lfo2'>When scanning text for p=
icking out URLS</li><li class=3DMsoListParagraph style=3D'margin-left:0in;m=
so-list:l0 level1 lfo2'>when used in print or other media (in an ad or writ=
ten on a napkin)</li></ol><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p clas=
s=3DMsoNormal>These are in order of decreasing specificity, increasing =E2=
=80=9Cliberal displacement=E2=80=9D.</p><p class=3DMsoNormal>I think those =
who are choosing names to use (as domain name, email address, short url) wi=
ll want to use (4), no matter what rules the registry applies. Anyone regis=
tering a domain name, a user name at a mail host, or a (short) URL will wan=
t to choose names that they can print on a business card or an ad or a rost=
er and believe that their target audience can enter and get the string inte=
nded.</p><p class=3DMsoNormal>And 1 &lt; 2 &lt; 3 &lt; 4 as equivalence goe=
s. </p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I don=
=E2=80=99t think it=E2=80=99s practical to redo all the protocols that use =
these strings to pass along a tuple of string and context.</p><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Larry</p><p class=3DMsoNo=
rmal>--</p><p class=3DMsoNormal><a href=3D"https://LarryMasinter.net">https=
://LarryMasinter.net</a></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_27E5E152-D49A-46EE-9DFB-47591A9551FD_--


From nobody Fri Oct 12 08:14:04 2018
Return-Path: <pthatcher@google.com>
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 BB809130E30 for <art@ietfa.amsl.com>; Fri, 12 Oct 2018 08:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 oWbTnTortLLX for <art@ietfa.amsl.com>; Fri, 12 Oct 2018 08:13:59 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 93CE6130E23 for <art@ietf.org>; Fri, 12 Oct 2018 08:13:58 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id 185-v6so13339209wmt.2 for <art@ietf.org>; Fri, 12 Oct 2018 08:13:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=etlBKbGm6Rx8jUhwiuTFvHYu0MfcO87t/ldv6ckv7zE=; b=kbBh2vZCT06dAV3ddSrKPchglwtC8qRWjrgpG1GC3QjX9AXBxSApO3aKOtzujZ1GJH NuaKnRCqMOOIKiLpGPK0amWRJB6IHtvqv0lyw6V0VrOXiQFEOWW5z9ZfJNtom9rVUMth srAF3yf6cO4smgde0l/2PxMpQUxisblBkAKKgyCCmJD0MulxYe/FnS8SVUeAZK+mM6nd A02AV7eei3jIPsSy7umZW+OCNqoRBLDTnCKdcbOj4iiCZ/ezz/JDHJ3xqztfpYQtVnHA WV2BiJHi//Y+F18B0VtqjPKvciwJluxjT2iBwYlIagr2XtbQIQQ+QfI2r1qurIdAV6O6 dUlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=etlBKbGm6Rx8jUhwiuTFvHYu0MfcO87t/ldv6ckv7zE=; b=OztN6oLYw7mjNNWCmH7SD/gWVfxs7sKz7xSX5VzvUa35Dnhsa74ops3iTQgX3U1qLK f7xgN2bruXfbTwIqpyIlayxv48RgWimjmun25feNXvTFUruGCL48C+y3wo3i2J8py+m/ p0e/4Wse9blW1nZB59fBcLd+aeUgY3c4YxnlgyiutDSuYqKdybA+j6k7kMNw7dptv2KG LJnWq1tIZ2QkCy9Sh7O5dVFCyPq+qIQKcz0T6t1E5pUzVYKn6vHlHWQL20Et9U7Pt0pE RyZ3X5VhbpWuyZFJ+rPewoO2IZSFAbr2wPVogbOLbm5I+beYxbZj/u3L9uZmqAXp7yzR BOMw==
X-Gm-Message-State: ABuFfoh3ZnRpT/meucqlSywK7zahyktbmcmav7PEC0/buDQkPC62bcFT F/S9HFtHEwwsX9JP4OSFMfdB0aCqm7BDTNqH92GqtQ==
X-Google-Smtp-Source: ACcGV634Ej7c20K7On6ejzP2cAt8eLYIXpqP4/04vMUVSZ5LAKuB4CO37p/gwM5vXcwoWcgRzkxkf0aZRDqFdo1DeUI=
X-Received: by 2002:a1c:838a:: with SMTP id f132-v6mr5822773wmd.51.1539357236687;  Fri, 12 Oct 2018 08:13:56 -0700 (PDT)
MIME-Version: 1.0
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca> <46E40ED2-D289-4C0F-8C0B-82A5980B2692@ericsson.com> <E05D7CB4-832E-4221-ADFE-D8F317EEA8F1@iii.ca> <CAJrXDUGpmZKGQXF0p1hjQv_F=5dQoJLUCT7+6y-=uzwcRv1Ncw@mail.gmail.com> <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com>
In-Reply-To: <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 12 Oct 2018 08:13:43 -0700
Message-ID: <CAJrXDUEToHCk0ERJSGMuoq+6vgySp8RsA5Ee5AZf4wOqsE_wNw@mail.gmail.com>
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
Cc: pthatcher=40google.com@dmarc.ietf.org, mmusic@ietf.org, art@ietf.org,  clue@ietf.org, ice@ietf.org, RTCWeb IETF <rtcweb@ietf.org>,  Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="00000000000047047205780989dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/cLnkdfy3v8mOnxTIyHZ836sC14E>
Subject: Re: [art] [MMUSIC] [Ice]  [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2018 15:14:03 -0000

--00000000000047047205780989dd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 27, 2018 at 4:21 PM Justin Uberti <juberti=3D
40google.com@dmarc.ietf.org> wrote:

> I agree with Peter. Chrome's implementation is already closer to 8445 tha=
n
> 5245, so I don't see any issues associated with snapping this cluster to
> 8445 (aside from the work involved).
>
> On that topic, note that JSEP will need a few more changes than just the
> addition of the 8445 reference and note; the examples will have to be
> updated, as will the logic regarding generation of offers and answers and
> their parsing (to deal with the new ice-option). These changes will be
> modest but probably will need to be done by the authors.
>
>
I've updated the references to 8445 (and to draft-ietf-mmusic-ice-sip-sdp)
in this PR: https://github.com/rtcweb-wg/jsep/pull/851

I've also added the ice2 processing and added ice2 to the examples in the
same PR.

What did you mean by "and note"?  Is there something more needed?


> On Wed, Sep 19, 2018 at 9:52 PM Peter Thatcher <pthatcher=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> I'm late to the discussion, and reading through it, it seems that we hav=
e
>> a lot of back and forth without addressing Cullen's root issue.  Let me =
see
>> if I understand Cullen's root issue correctly.  I think it's something l=
ike:
>>
>> 1.  Cisco has existing code that it wants to call "WebRTC 1.0 compliant"
>> without changing to be compliant with 8445.
>>
>> 2.  Cisco has existing code that it wants to continue to interoperate
>> with endpoints, especially Chrome, even as they make changes to become 8=
445
>> compliant.  And they don't want to have to test against old and new
>> versions.
>>
>> Cullen, is that accurate?
>>
>>
>>
>> OK, so some of my thoughts:
>>
>> 1.  I don't think there is any interop risk here at all related to
>> timings.  If you're worried about the drop in minimum check interval goi=
ng
>> from 20ms to 5ms, don't.  Just because the spec allows for going that lo=
w
>> doesn't mean endpoints will.  And if they do, they'll do it carefully.
>> Endpoints can and should still choose a value that works best regardless=
 of
>> the min in the spec.  For example, Chrome is still using an interval of
>> 48ms (we're not in a rush to lower it, but we have non-browser endpoints
>> that do go lower).  And if we roll out a lower value, it will be via
>> experiments or opt-ins and carefully tracked to make sure connectivity
>> rates don't drop.  If any problem were found in practice, it would be
>> quickly reverted.
>>
>> 2.  I don't think there is any interop risk here related to nomination
>> either.
>> Chrome's default behavior has never been compliant to any spec anyway,
>> and it's never been an issue.  And like with ping intervals, any changes=
 to
>> implementations will be done slowly and carefully.
>>
>> 3.  I don't think it really matters to major implementations what the
>> dependency graph looks like.  Whether some point to 5245 and others to 8=
445
>> or if all of them point to 8445, it doesn't matter, implementations will
>> behave the same either way.  Chrome, for example will adjust timings as
>> works well in practice (perhaps someday to below 20ms interval) regardle=
ss
>> of which RFCs point to 8445 and which point to 5245.  If interop issues
>> ever do come up, then they can be fixed.  And that has nothing to do wit=
h
>> which RFCs point to 5245 and which point to 8445.
>>
>> 5.  You're going to need to test against different versions of different
>> browser no matter what the RFC references are.  ICE timings and nominati=
ons
>> seem like the least of your testing problems.  But on the flip side, Chr=
ome
>> (and I assume other browsers) have been very slow and careful when makin=
g
>> changes to the ICE code.
>>
>> 6.  FlexICE should go a long way to putting the web app in control of th=
e
>> ICE behavior.  So if you are worried about what browsers will do with IC=
E,
>> I suggest supporting the FlexICE effort.  In fact, it's the result of yo=
ur
>> proposal at TPAC in 2017 for wanting to have lower-level of control of
>> ICE...  If we get that into all the browsers, you won't have to worry an=
y
>> more about any of this because you'll be in control (assuming you contro=
l
>> the web app).
>>
>
>> Altogether, I don't see any reason to not reference 8445 everywhere, at
>> least not any related to interop risk and web browsers.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Sep 7, 2018 at 9:37 AM Cullen Jennings <fluffy@iii.ca> wrote:
>>
>>>
>>> On Sep 7, 2018, at 1:25 AM, Christer Holmberg <
>>> christer.holmberg@ericsson..com <christer.holmberg@ericsson.com>> wrote=
:
>>>
>>> > Cisco has implemented stuff that is WebRTC 1.0 compliant without this
>>> change. These gratuitous changes, years after the implementation were
>>> coded, with no real benefit will ensure that we are not
>>> > and will not become compliant with the RFC. It's unlikely we will
>>> upgrade to the new ICE until it has real befits.
>>>
>>> The main reason we did 8445 was because people had identified issues
>>> with 5245. The work was driven mostly by the WebRTC community, includin=
g
>>> yourself and the Chrome people (or, at least the Google people), and on=
e of
>>> the reason it took time to finalize 8445 was because you (among others)
>>> wanted to make sure we get things right (by making network measurements
>>> etc). Are you now saying all those changes bring no benefit? Did we all
>>> waste our time?
>>>
>>>
>>> Our testing, which we do not share, dig not indicate an improvement of
>>> connectivity rates. I did not see results from others that did. Some of=
 the
>>> early test results from others that drove this work were not reproducib=
le
>>> in our testing. The one thing I think most people did find is that the =
more
>>> out of sync the pacing of the two agents was, the worse the connectivit=
y
>>> was. But all of this is water under the bridge, we have old and new ice=
,
>>> people can use either. What we are talking about here is what is the
>>> minimum bar for WebRTC 1.0
>>>
>>>
>>> > It is doubtful Justin will want to implement the 8445 mechanisms of
>>> supporting both new and old ICE. Instead, we will move to say "works
>>> with Browser X version Y or later." We have watched at W3C as it moved =
to
>>> be that unless chrome does it, it rare that it becomes a standard.
>>> > Right here I am watching how the stuff IETF defines will be less
>>> relevant than the issue of what chrome implements.
>>>
>>> What exactly would Justin have to change?
>>>
>>>
>>>
>>> For us, the largest part is having to test for both old and new - it=E2=
=80=99s
>>> not easy to do good automated testing for ICE.
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>> _______________________________________________
>
>
>> Ice mailing list
>> Ice@ietf.org
>> https://www.ietf.org/mailman/listinfo/ice
>>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--00000000000047047205780989dd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu=
, Sep 27, 2018 at 4:21 PM Justin Uberti &lt;juberti=3D<a href=3D"mailto:40g=
oogle.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">I agree with Peter. Chro=
me&#39;s implementation is already closer to 8445 than 5245, so I don&#39;t=
 see any issues associated with snapping this cluster to 8445 (aside from t=
he work involved).<div><br></div><div>On that topic, note that JSEP will ne=
ed a few more changes than just the addition of the 8445 reference and note=
; the examples will have to be updated, as will the logic regarding generat=
ion of offers and answers and their parsing (to deal with the new ice-optio=
n). These changes will be modest but probably will need to be done by the a=
uthors.</div></div><br></blockquote><div><br></div><div>I&#39;ve updated th=
e references to 8445 (and to=C2=A0draft-ietf-mmusic-ice-sip-sdp) in this PR=
:=C2=A0<a href=3D"https://github.com/rtcweb-wg/jsep/pull/851">https://githu=
b.com/rtcweb-wg/jsep/pull/851</a></div><div><br></div><div>I&#39;ve also ad=
ded the ice2 processing and added ice2 to the examples in the same PR.=C2=
=A0</div><div><br></div><div>What did you mean by &quot;and note&quot;?=C2=
=A0 Is there something more needed?</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div class=3D"gmail_quote"></div><div class=3D"gmail_quote"><=
div dir=3D"ltr">On Wed, Sep 19, 2018 at 9:52 PM Peter Thatcher &lt;pthatche=
r=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40goog=
le.com@dmarc.ietf.org</a>&gt; wrote:<br></div></div><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I&#39;m late to th=
e discussion, and reading through it, it seems that we have a lot of back a=
nd forth without addressing Cullen&#39;s root issue.=C2=A0 Let me see if I =
understand Cullen&#39;s root issue correctly.=C2=A0 I think it&#39;s someth=
ing like:</div><div><br></div><div>1.=C2=A0 Cisco has existing code that it=
 wants to call &quot;WebRTC 1.0 compliant&quot; without changing to be comp=
liant with 8445.</div><div><br></div><div>2.=C2=A0 Cisco has existing code =
that it wants to continue to interoperate with endpoints, especially Chrome=
, even as they make changes to become 8445 compliant.=C2=A0 And they don&#3=
9;t want to have to test against old and new versions.=C2=A0=C2=A0</div><di=
v><br></div><div>Cullen, is that accurate?</div><div><br></div><div><br></d=
iv><div><br></div><div>OK, so some of my thoughts:</div><div><br></div><div=
>1.=C2=A0 I don&#39;t think there is any interop risk here at all related t=
o timings.=C2=A0 If you&#39;re worried about the drop in minimum check inte=
rval going from 20ms to 5ms, don&#39;t.=C2=A0 Just because the spec allows =
for going that low doesn&#39;t mean endpoints will.=C2=A0 And if they do, t=
hey&#39;ll do it carefully.=C2=A0 Endpoints can and should still choose a v=
alue that works best regardless of the min in the spec.=C2=A0 For example, =
Chrome is still using an interval of 48ms (we&#39;re not in a rush to lower=
 it, but we have non-browser endpoints that do go lower).=C2=A0 And if we r=
oll out a lower value, it will be via experiments or opt-ins and carefully =
tracked to make sure connectivity rates don&#39;t drop.=C2=A0 If any proble=
m were found in practice, it would be quickly reverted.=C2=A0=C2=A0</div><d=
iv><br></div><div>2.=C2=A0 I don&#39;t think there is any interop risk here=
 related to nomination either.=C2=A0=C2=A0</div><div>Chrome&#39;s default b=
ehavior has never been compliant to any spec anyway, and it&#39;s never bee=
n an issue.=C2=A0 And like with ping intervals, any changes to implementati=
ons will be done slowly and carefully.=C2=A0=C2=A0</div><div><br></div><div=
>3.=C2=A0 I don&#39;t think it really matters to major implementations what=
 the dependency graph looks like.=C2=A0 Whether some point to 5245 and othe=
rs to 8445 or if all of them point to 8445, it doesn&#39;t matter, implemen=
tations will behave the same either way.=C2=A0 Chrome, for example will adj=
ust timings as works well in practice (perhaps someday to below 20ms interv=
al) regardless of which RFCs point to 8445 and which point to 5245.=C2=A0 I=
f interop issues ever do come up, then they can be fixed.=C2=A0 And that ha=
s nothing to do with which RFCs point to 5245 and which point to 8445.</div=
><div><br></div><div>5.=C2=A0 You&#39;re going to need to test against diff=
erent versions of different browser no matter what the RFC references are.=
=C2=A0 ICE timings and nominations seem like the least of your testing prob=
lems.=C2=A0 But on the flip side, Chrome (and I assume other browsers) have=
 been very slow and careful when making changes to the ICE code.</div><div>=
<br></div></div></blockquote></div><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"ltr"><div>6.=C2=A0 FlexICE should go a long w=
ay to putting the web app in control of the ICE behavior.=C2=A0 So if you a=
re worried about what browsers will do with ICE, I suggest supporting the F=
lexICE effort.=C2=A0 In fact, it&#39;s the result of your proposal at TPAC =
in 2017 for wanting to have lower-level of control of ICE...=C2=A0 If we ge=
t that into all the browsers, you won&#39;t have to worry any more about an=
y of this because you&#39;ll be in control (assuming you control the web ap=
p).=C2=A0</div></div></blockquote></div><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div><br></div><div>Altogether, I d=
on&#39;t see any reason to not reference 8445 everywhere, at least not any =
related to interop risk and web browsers.</div><div><br></div><div><br></di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br></di=
v><div>=C2=A0</div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><div><br></div><div><br></div><div><br></div><br></div><=
/blockquote></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Sep 7=
, 2018 at 9:37 AM Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" targ=
et=3D"_blank">fluffy@iii.ca</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv><br><blockquote type=3D"cite"><div>On Sep 7, 2018, at 1:25 AM, Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_b=
lank">christer.holmberg@ericsson..com</a>&gt; wrote:</div><br class=3D"m_16=
80274079720651929m_3204432535681369445m_-6802286700116899682Apple-interchan=
ge-newline"><div><div style=3D"font-family:Helvetica;font-size:12px;font-st=
yle:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:norma=
l;text-align:start;text-indent:0px;text-transform:none;white-space:normal;w=
ord-spacing:0px;text-decoration:none"><div style=3D"margin:0cm 0cm 0.0001pt=
;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">&gt; C=
isco has implemented stuff that is WebRTC 1.0 compliant without this change=
.<span class=3D"m_1680274079720651929m_3204432535681369445m_-68022867001168=
99682Apple-converted-space">=C2=A0</span></span>These gratuitous changes, y=
ears after the implementation were coded, with no real benefit will ensure =
that we are not<u></u><u></u></div><div style=3D"margin:0cm 0cm 0.0001pt;fo=
nt-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">&gt;<span=
 class=3D"m_1680274079720651929m_3204432535681369445m_-6802286700116899682A=
pple-converted-space">=C2=A0</span></span><span lang=3D"EN-US">and will not=
 become compliant with the RFC.<span class=3D"m_1680274079720651929m_320443=
2535681369445m_-6802286700116899682Apple-converted-space">=C2=A0</span></sp=
an>It&#39;s unlikely we will upgrade to the new ICE until it has real befit=
s.<span class=3D"m_1680274079720651929m_3204432535681369445m_-6802286700116=
899682Apple-converted-space">=C2=A0</span><u></u><u></u></div><div style=3D=
"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u>=
</u>=C2=A0<u></u></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt=
;font-family:Calibri,sans-serif"><span lang=3D"EN-US">The main reason we di=
d 8445 was because people had identified issues with 5245. The work was dri=
ven mostly by the WebRTC community, including yourself and the Chrome peopl=
e (or, at least the Google people), and one of the reason it took time to f=
inalize 8445 was because you (among others) wanted to make sure we get thin=
gs right (by making network measurements etc). Are you now saying all those=
 changes bring no benefit? Did we all waste our time?</span></div></div></d=
iv></blockquote><div><br></div></div></div><div style=3D"word-wrap:break-wo=
rd;line-break:after-white-space"><div>Our testing, which we do not share, d=
ig not indicate an improvement of connectivity rates. I did not see results=
 from others that did. Some of the early test results from others that drov=
e this work were not reproducible in our testing. The one thing I think mos=
t people did find is that the more out of sync the pacing of the two agents=
 was, the worse the connectivity was. But all of this is water under the br=
idge, we have old and new ice, people can use either. What we are talking a=
bout here is what is the minimum bar for WebRTC 1.0=C2=A0</div></div><div s=
tyle=3D"word-wrap:break-word;line-break:after-white-space"><div><br><blockq=
uote type=3D"cite"><div><div style=3D"font-family:Helvetica;font-size:12px;=
font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-space:n=
ormal;word-spacing:0px;text-decoration:none"><div style=3D"margin:0cm 0cm 0=
.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US"=
><u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size=
:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US"><u></u>=C2=A0<u>=
</u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-=
family:Calibri,sans-serif"><span lang=3D"EN-US">&gt; It is doubtful Justin =
will want to implement the 8445 mechanisms of supporting both new and old I=
CE.<span class=3D"m_1680274079720651929m_3204432535681369445m_-680228670011=
6899682Apple-converted-space">=C2=A0</span></span>Instead, we will move to =
say &quot;works with Browser X version Y or later.&quot; We have watched at=
 W3C as it moved to be that unless chrome does it, it rare that it becomes =
a standard. =C2=A0<u></u><u></u></div><div style=3D"margin:0cm 0cm 0.0001pt=
;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">&gt;<s=
pan class=3D"m_1680274079720651929m_3204432535681369445m_-68022867001168996=
82Apple-converted-space">=C2=A0</span></span><span lang=3D"EN-US">Right her=
e I am watching how the stuff IETF defines will be less relevant than the i=
ssue of what chrome implements.=C2=A0</span><span lang=3D"EN-US"><u></u><u>=
</u></span></div></div><div style=3D"font-family:Helvetica;font-size:12px;f=
ont-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing=
:normal;text-align:start;text-indent:0px;text-transform:none;white-space:no=
rmal;word-spacing:0px;text-decoration:none"><div style=3D"margin:0cm 0cm 0.=
0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">=
<u></u>=C2=A0<u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font=
-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">What exactl=
y would Justin have to change?<u></u><u></u></span></div><div style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span la=
ng=3D"EN-US"><u></u>=C2=A0<u></u></span></div></div></div></blockquote></di=
v><br></div><div style=3D"word-wrap:break-word;line-break:after-white-space=
"><div>For us, the largest part is having to test for both old and new - it=
=E2=80=99s not easy to do good automated testing for ICE.=C2=A0</div></div>=
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div></blockquote></div><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"></di=
v></div>
_______________________________________________</blockquote></div><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Ice mailing list<br>
<a href=3D"mailto:Ice@ietf.org" target=3D"_blank">Ice@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ice" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ice</a><br>
</blockquote></div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div>

--00000000000047047205780989dd--


From nobody Fri Oct 12 18:09:15 2018
Return-Path: <juberti@google.com>
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 E5B41130ECB for <art@ietfa.amsl.com>; Fri, 12 Oct 2018 18:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 EIofP_Fg2VmQ for <art@ietfa.amsl.com>; Fri, 12 Oct 2018 18:08:49 -0700 (PDT)
Received: from mail-it1-x12e.google.com (mail-it1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 B50E3130DDE for <art@ietf.org>; Fri, 12 Oct 2018 18:08:44 -0700 (PDT)
Received: by mail-it1-x12e.google.com with SMTP id l127-v6so22702989ith.1 for <art@ietf.org>; Fri, 12 Oct 2018 18:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZvnkrFDKS2tvIfI4jJqEb63gbq43fw9zgj6Fo/uFPGQ=; b=HY9k6sPH8AwHFqiTqDrKoZrt2+oiGv4wnkLgO2EJ2X+Xwe/NuVMJLDF+BXs+8UVrqv OwU35yytFJ8BahZEQqzcm9ClCZEbzJeGmaZChOncxBqwIx+W6ML5SIIwgeIKjOZ2wMZ0 VC9z0R0oRWHcN3al4nNBQbf0xNBFhQqlb6LfxhauoHaic/0AlPJWfFjDtaa2k8Kgl0Mi C/8RLksxpqFvp6+qA6WsMwF4mMihJoByhUVTrWDJ8UGq9his1q39j7Udy4uXTj/l0UcY C3Gt0B9GxReliBZP1hCPfYgk2GLqzC5c6TRc7qfCdWyaqMEzFr1iRjOjV/A+8fkG1FwR JiaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZvnkrFDKS2tvIfI4jJqEb63gbq43fw9zgj6Fo/uFPGQ=; b=DOGoeeSamPXFCnKrnM9URb2UD8tJ9RF2MLgh7lLzpd2TtRvgf+lioKmxUYD672iZli 6QxDUtXH+ZnWHLbpZdMZidUKReNusxgpJ+lJvqh6SbvkZMyBtiOheKCetCjuOu0sHGc5 +Q8+viYWZn1proRmzeHRY1WSPY/BcboljBl0TPmpTeJbplDOs9acNeQX/5/L19PK7l/z h8MHakibLClea3XmsKKKFSXAcJBCAA8QfI5nc4LjhYCj3s2uTB8FduT3mf/8SCJQ4NaX s6Taut7OOz9VmlMFQga5wqeF1HYFiSXayvJX88RyXn0166MoyjAAHQmleleeAGo2wW2w YLBg==
X-Gm-Message-State: ABuFfohvYxLtoZtJTD4FYlMDzLpFo0ehjKWTDhQLvunkgZbt2EPCFAb6 DA1y4+1YjAehcI6S55Az1oARSpyu4kswAJhVKzUar/Jnm/xryA==
X-Google-Smtp-Source: ACcGV63ndaLILfkWGr55imIClvCOJ3JtTzCJeZ4VsYmNIX8q2gBRPm1dEyM+CcrCiwJIiVQ5Ia89iSVo6PHpklJ2piM=
X-Received: by 2002:a24:fc02:: with SMTP id b2-v6mr6257023ith.45.1539392923522;  Fri, 12 Oct 2018 18:08:43 -0700 (PDT)
MIME-Version: 1.0
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca> <46E40ED2-D289-4C0F-8C0B-82A5980B2692@ericsson.com> <E05D7CB4-832E-4221-ADFE-D8F317EEA8F1@iii.ca> <CAJrXDUGpmZKGQXF0p1hjQv_F=5dQoJLUCT7+6y-=uzwcRv1Ncw@mail.gmail.com> <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com> <CAJrXDUEToHCk0ERJSGMuoq+6vgySp8RsA5Ee5AZf4wOqsE_wNw@mail.gmail.com>
In-Reply-To: <CAJrXDUEToHCk0ERJSGMuoq+6vgySp8RsA5Ee5AZf4wOqsE_wNw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 12 Oct 2018 18:08:29 -0700
Message-ID: <CAOJ7v-3mk+Qg9-dnZ+-=csOFEVwjNLVqib_NfGp_64=4HxZJNA@mail.gmail.com>
To: pthatcher=40google.com@dmarc.ietf.org
Cc: Peter Thatcher <pthatcher@google.com>, mmusic@ietf.org, art@ietf.org, clue@ietf.org,  ice@ietf.org, RTCWeb IETF <rtcweb@ietf.org>, Cullen Jennings <fluffy@iii.ca>,  Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="00000000000060d8e5057811d87f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/KBcTubEeTKF3fiwhXia_gNEuPZ8>
Subject: Re: [art] [MMUSIC] [Ice]  [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Oct 2018 01:08:58 -0000

--00000000000060d8e5057811d87f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 12, 2018 at 8:14 AM Peter Thatcher <pthatcher=3D
40google.com@dmarc.ietf.org> wrote:

>
>
> On Thu, Sep 27, 2018 at 4:21 PM Justin Uberti <juberti=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> I agree with Peter. Chrome's implementation is already closer to 8445
>> than 5245, so I don't see any issues associated with snapping this clust=
er
>> to 8445 (aside from the work involved).
>>
>> On that topic, note that JSEP will need a few more changes than just the
>> addition of the 8445 reference and note; the examples will have to be
>> updated, as will the logic regarding generation of offers and answers an=
d
>> their parsing (to deal with the new ice-option). These changes will be
>> modest but probably will need to be done by the authors.
>>
>>
> I've updated the references to 8445 (and to draft-ietf-mmusic-ice-sip-sdp=
)
> in this PR: https://github.com/rtcweb-wg/jsep/pull/851
>
> I've also added the ice2 processing and added ice2 to the examples in the
> same PR.
>

Thanks for doing this, Peter.

>
> What did you mean by "and note"?  Is there something more needed?
>

The note in question is the text that Adam mentioned in the original email:

*While this specification formally relies on [RFC8445], at the time of its
publication, the majority of WebRTC implementations support the version of
ICE described in [RFC5245], and use a pre-standard version of the trickle
ice mechanism described in [RFCXXXX]. The use of the "ice2" attribute
defined in [RFC8445] can be used to detect the version in use by a remote
endpoint and to provide a smooth transition from the older specification to
the newer one. *

I do think we need text similar to this to be added to S 5.11 (processing
an answer) in JSEP.

>
>
>> On Wed, Sep 19, 2018 at 9:52 PM Peter Thatcher <pthatcher=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> I'm late to the discussion, and reading through it, it seems that we
>>> have a lot of back and forth without addressing Cullen's root issue.  L=
et
>>> me see if I understand Cullen's root issue correctly.  I think it's
>>> something like:
>>>
>>> 1.  Cisco has existing code that it wants to call "WebRTC 1.0 compliant=
"
>>> without changing to be compliant with 8445.
>>>
>>> 2.  Cisco has existing code that it wants to continue to interoperate
>>> with endpoints, especially Chrome, even as they make changes to become =
8445
>>> compliant.  And they don't want to have to test against old and new
>>> versions.
>>>
>>> Cullen, is that accurate?
>>>
>>>
>>>
>>> OK, so some of my thoughts:
>>>
>>> 1.  I don't think there is any interop risk here at all related to
>>> timings.  If you're worried about the drop in minimum check interval go=
ing
>>> from 20ms to 5ms, don't.  Just because the spec allows for going that l=
ow
>>> doesn't mean endpoints will.  And if they do, they'll do it carefully.
>>> Endpoints can and should still choose a value that works best regardles=
s of
>>> the min in the spec.  For example, Chrome is still using an interval of
>>> 48ms (we're not in a rush to lower it, but we have non-browser endpoint=
s
>>> that do go lower).  And if we roll out a lower value, it will be via
>>> experiments or opt-ins and carefully tracked to make sure connectivity
>>> rates don't drop.  If any problem were found in practice, it would be
>>> quickly reverted.
>>>
>>> 2.  I don't think there is any interop risk here related to nomination
>>> either.
>>> Chrome's default behavior has never been compliant to any spec anyway,
>>> and it's never been an issue.  And like with ping intervals, any change=
s to
>>> implementations will be done slowly and carefully.
>>>
>>> 3.  I don't think it really matters to major implementations what the
>>> dependency graph looks like.  Whether some point to 5245 and others to =
8445
>>> or if all of them point to 8445, it doesn't matter, implementations wil=
l
>>> behave the same either way.  Chrome, for example will adjust timings as
>>> works well in practice (perhaps someday to below 20ms interval) regardl=
ess
>>> of which RFCs point to 8445 and which point to 5245.  If interop issues
>>> ever do come up, then they can be fixed.  And that has nothing to do wi=
th
>>> which RFCs point to 5245 and which point to 8445.
>>>
>>> 5.  You're going to need to test against different versions of differen=
t
>>> browser no matter what the RFC references are.  ICE timings and nominat=
ions
>>> seem like the least of your testing problems.  But on the flip side, Ch=
rome
>>> (and I assume other browsers) have been very slow and careful when maki=
ng
>>> changes to the ICE code.
>>>
>>> 6.  FlexICE should go a long way to putting the web app in control of
>>> the ICE behavior.  So if you are worried about what browsers will do wi=
th
>>> ICE, I suggest supporting the FlexICE effort.  In fact, it's the result=
 of
>>> your proposal at TPAC in 2017 for wanting to have lower-level of contro=
l of
>>> ICE...  If we get that into all the browsers, you won't have to worry a=
ny
>>> more about any of this because you'll be in control (assuming you contr=
ol
>>> the web app).
>>>
>>
>>> Altogether, I don't see any reason to not reference 8445 everywhere, at
>>> least not any related to interop risk and web browsers.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Sep 7, 2018 at 9:37 AM Cullen Jennings <fluffy@iii.ca> wrote:
>>>
>>>>
>>>> On Sep 7, 2018, at 1:25 AM, Christer Holmberg <
>>>> christer.holmberg@ericsson..com <christer.holmberg@ericsson.com>>
>>>> wrote:
>>>>
>>>> > Cisco has implemented stuff that is WebRTC 1.0 compliant without thi=
s
>>>> change.. These gratuitous changes, years after the implementation were
>>>> coded, with no real benefit will ensure that we are not
>>>> > and will not become compliant with the RFC. It's unlikely we will
>>>> upgrade to the new ICE until it has real befits.
>>>>
>>>> The main reason we did 8445 was because people had identified issues
>>>> with 5245. The work was driven mostly by the WebRTC community, includi=
ng
>>>> yourself and the Chrome people (or, at least the Google people), and o=
ne of
>>>> the reason it took time to finalize 8445 was because you (among others=
)
>>>> wanted to make sure we get things right (by making network measurement=
s
>>>> etc). Are you now saying all those changes bring no benefit? Did we al=
l
>>>> waste our time?
>>>>
>>>>
>>>> Our testing, which we do not share, dig not indicate an improvement of
>>>> connectivity rates. I did not see results from others that did. Some o=
f the
>>>> early test results from others that drove this work were not reproduci=
ble
>>>> in our testing. The one thing I think most people did find is that the=
 more
>>>> out of sync the pacing of the two agents was, the worse the connectivi=
ty
>>>> was. But all of this is water under the bridge, we have old and new ic=
e,
>>>> people can use either. What we are talking about here is what is the
>>>> minimum bar for WebRTC 1.0
>>>>
>>>>
>>>> > It is doubtful Justin will want to implement the 8445 mechanisms of
>>>> supporting both new and old ICE. Instead, we will move to say "works
>>>> with Browser X version Y or later." We have watched at W3C as it moved=
 to
>>>> be that unless chrome does it, it rare that it becomes a standard.
>>>> > Right here I am watching how the stuff IETF defines will be less
>>>> relevant than the issue of what chrome implements.
>>>>
>>>> What exactly would Justin have to change?
>>>>
>>>>
>>>>
>>>> For us, the largest part is having to test for both old and new - it=
=E2=80=99s
>>>> not easy to do good automated testing for ICE.
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>
>>> _______________________________________________
>>
>>
>>> Ice mailing list
>>> Ice@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ice
>>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

--00000000000060d8e5057811d87f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr">On Fri, Oct 12, 2018 at 8:14 AM Peter Thatcher &lt;pthatcher=
=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40googl=
e.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr">On Thu, Sep 27, 2018 at 4:21 PM Justin Uberti &lt;juberti=3D<=
a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40google.co=
m@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr">I agree with Peter. Chrome&#39;s implement=
ation is already closer to 8445 than 5245, so I don&#39;t see any issues as=
sociated with snapping this cluster to 8445 (aside from the work involved).=
<div><br></div><div>On that topic, note that JSEP will need a few more chan=
ges than just the addition of the 8445 reference and note; the examples wil=
l have to be updated, as will the logic regarding generation of offers and =
answers and their parsing (to deal with the new ice-option). These changes =
will be modest but probably will need to be done by the authors.</div></div=
><br></blockquote><div><br></div><div>I&#39;ve updated the references to 84=
45 (and to=C2=A0draft-ietf-mmusic-ice-sip-sdp) in this PR:=C2=A0<a href=3D"=
https://github.com/rtcweb-wg/jsep/pull/851" target=3D"_blank">https://githu=
b.com/rtcweb-wg/jsep/pull/851</a></div><div><br></div><div>I&#39;ve also ad=
ded the ice2 processing and added ice2 to the examples in the same PR.=C2=
=A0</div></div></div></blockquote><div><br></div><div>Thanks for doing this=
, Peter.=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div><div>What did y=
ou mean by &quot;and note&quot;?=C2=A0 Is there something more needed?</div=
></div></div></blockquote><div><br></div><div>The note in question is the t=
ext that Adam mentioned in the original email:</div><div><br></div><div><i>=
While this specification formally relies on [RFC8445], at the time of its p=
ublication, the majority of WebRTC implementations support the version of I=
CE described in [RFC5245], and use a pre-standard version of the trickle ic=
e mechanism described in [RFCXXXX]. The use of the &quot;ice2&quot; attribu=
te defined in [RFC8445] can be used to detect the version in use by a remot=
e endpoint and to provide a smooth transition from the older specification =
to the newer one.=C2=A0</i></div><div><i><br></i></div><div>I do think we n=
eed text similar to this to be added to S 5.11 (processing an answer) in JS=
EP.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"=
><div class=3D"gmail_quote"><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div class=3D"gmail_quote"></div><div class=3D"gmail_qu=
ote"><div dir=3D"ltr">On Wed, Sep 19, 2018 at 9:52 PM Peter Thatcher &lt;pt=
hatcher=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">=
40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div></div><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div>I&#39;m late to the discussion, and reading through it, it seems tha=
t we have a lot of back and forth without addressing Cullen&#39;s root issu=
e.=C2=A0 Let me see if I understand Cullen&#39;s root issue correctly.=C2=
=A0 I think it&#39;s something like:</div><div><br></div><div>1.=C2=A0 Cisc=
o has existing code that it wants to call &quot;WebRTC 1.0 compliant&quot; =
without changing to be compliant with 8445.</div><div><br></div><div>2.=C2=
=A0 Cisco has existing code that it wants to continue to interoperate with =
endpoints, especially Chrome, even as they make changes to become 8445 comp=
liant.=C2=A0 And they don&#39;t want to have to test against old and new ve=
rsions.=C2=A0=C2=A0</div><div><br></div><div>Cullen, is that accurate?</div=
><div><br></div><div><br></div><div><br></div><div>OK, so some of my though=
ts:</div><div><br></div><div>1.=C2=A0 I don&#39;t think there is any intero=
p risk here at all related to timings.=C2=A0 If you&#39;re worried about th=
e drop in minimum check interval going from 20ms to 5ms, don&#39;t.=C2=A0 J=
ust because the spec allows for going that low doesn&#39;t mean endpoints w=
ill.=C2=A0 And if they do, they&#39;ll do it carefully.=C2=A0 Endpoints can=
 and should still choose a value that works best regardless of the min in t=
he spec.=C2=A0 For example, Chrome is still using an interval of 48ms (we&#=
39;re not in a rush to lower it, but we have non-browser endpoints that do =
go lower).=C2=A0 And if we roll out a lower value, it will be via experimen=
ts or opt-ins and carefully tracked to make sure connectivity rates don&#39=
;t drop.=C2=A0 If any problem were found in practice, it would be quickly r=
everted.=C2=A0=C2=A0</div><div><br></div><div>2.=C2=A0 I don&#39;t think th=
ere is any interop risk here related to nomination either.=C2=A0=C2=A0</div=
><div>Chrome&#39;s default behavior has never been compliant to any spec an=
yway, and it&#39;s never been an issue.=C2=A0 And like with ping intervals,=
 any changes to implementations will be done slowly and carefully.=C2=A0=C2=
=A0</div><div><br></div><div>3.=C2=A0 I don&#39;t think it really matters t=
o major implementations what the dependency graph looks like.=C2=A0 Whether=
 some point to 5245 and others to 8445 or if all of them point to 8445, it =
doesn&#39;t matter, implementations will behave the same either way.=C2=A0 =
Chrome, for example will adjust timings as works well in practice (perhaps =
someday to below 20ms interval) regardless of which RFCs point to 8445 and =
which point to 5245.=C2=A0 If interop issues ever do come up, then they can=
 be fixed.=C2=A0 And that has nothing to do with which RFCs point to 5245 a=
nd which point to 8445.</div><div><br></div><div>5.=C2=A0 You&#39;re going =
to need to test against different versions of different browser no matter w=
hat the RFC references are.=C2=A0 ICE timings and nominations seem like the=
 least of your testing problems.=C2=A0 But on the flip side, Chrome (and I =
assume other browsers) have been very slow and careful when making changes =
to the ICE code.</div><div><br></div></div></blockquote></div><div class=3D=
"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div>6.=C2=A0 FlexICE should go a long way to putting the web app in =
control of the ICE behavior.=C2=A0 So if you are worried about what browser=
s will do with ICE, I suggest supporting the FlexICE effort.=C2=A0 In fact,=
 it&#39;s the result of your proposal at TPAC in 2017 for wanting to have l=
ower-level of control of ICE...=C2=A0 If we get that into all the browsers,=
 you won&#39;t have to worry any more about any of this because you&#39;ll =
be in control (assuming you control the web app).=C2=A0</div></div></blockq=
uote></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div><br></div><div>Altogether, I don&#39;t s=
ee any reason to not reference 8445 everywhere, at least not any related to=
 interop risk and web browsers.</div><div><br></div><div><br></div><div><br=
></div><div><br></div><div><br></div><div><br></div><div><br></div><div>=C2=
=A0</div><div><br></div><div><br></div><div><br></div><div><br></div><div><=
br></div><div><br></div><div><br></div><div><br></div><br></div></blockquot=
e></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Fri, Sep 7, 2018 at 9:37 AM Cullen Jennings &lt;<a href=3D"mailto:fluffy@ii=
i.ca" target=3D"_blank">fluffy@iii.ca</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-wor=
d;"><div><br><blockquote type=3D"cite"><div>On Sep 7, 2018, at 1:25 AM, Chr=
ister Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=
=3D"_blank">christer.holmberg@ericsson..com</a>&gt; wrote:</div><br class=
=3D"m_-6748401474167513945m_-955334991712834571m_1680274079720651929m_32044=
32535681369445m_-6802286700116899682Apple-interchange-newline"><div><div st=
yle=3D"font-family:Helvetica;font-size:12px;font-style:normal;font-variant-=
caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-dec=
oration:none"><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-fam=
ily:Calibri,sans-serif"><span lang=3D"EN-US">&gt; Cisco has implemented stu=
ff that is WebRTC 1.0 compliant without this change..<span class=3D"m_-6748=
401474167513945m_-955334991712834571m_1680274079720651929m_3204432535681369=
445m_-6802286700116899682Apple-converted-space">=C2=A0</span></span>These g=
ratuitous changes, years after the implementation were coded, with no real =
benefit will ensure that we are not<u></u><u></u></div><div style=3D"margin=
:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang=
=3D"EN-US">&gt;<span class=3D"m_-6748401474167513945m_-955334991712834571m_=
1680274079720651929m_3204432535681369445m_-6802286700116899682Apple-convert=
ed-space">=C2=A0</span></span><span lang=3D"EN-US">and will not become comp=
liant with the RFC.<span class=3D"m_-6748401474167513945m_-9553349917128345=
71m_1680274079720651929m_3204432535681369445m_-6802286700116899682Apple-con=
verted-space">=C2=A0</span></span>It&#39;s unlikely we will upgrade to the =
new ICE until it has real befits.<span class=3D"m_-6748401474167513945m_-95=
5334991712834571m_1680274079720651929m_3204432535681369445m_-68022867001168=
99682Apple-converted-space">=C2=A0</span><u></u><u></u></div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u><=
/u>=C2=A0<u></u></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;=
font-family:Calibri,sans-serif"><span lang=3D"EN-US">The main reason we did=
 8445 was because people had identified issues with 5245. The work was driv=
en mostly by the WebRTC community, including yourself and the Chrome people=
 (or, at least the Google people), and one of the reason it took time to fi=
nalize 8445 was because you (among others) wanted to make sure we get thing=
s right (by making network measurements etc). Are you now saying all those =
changes bring no benefit? Did we all waste our time?</span></div></div></di=
v></blockquote><div><br></div></div></div><div style=3D"overflow-wrap: brea=
k-word;"><div>Our testing, which we do not share, dig not indicate an impro=
vement of connectivity rates. I did not see results from others that did. S=
ome of the early test results from others that drove this work were not rep=
roducible in our testing. The one thing I think most people did find is tha=
t the more out of sync the pacing of the two agents was, the worse the conn=
ectivity was. But all of this is water under the bridge, we have old and ne=
w ice, people can use either. What we are talking about here is what is the=
 minimum bar for WebRTC 1.0=C2=A0</div></div><div style=3D"overflow-wrap: b=
reak-word;"><div><br><blockquote type=3D"cite"><div><div style=3D"font-fami=
ly:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font=
-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><d=
iv><span lang=3D"EN-US"><u></u><u></u></span></div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"=
EN-US"><u></u>=C2=A0<u></u></span></div><div style=3D"margin:0cm 0cm 0.0001=
pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">&gt;=
 It is doubtful Justin will want to implement the 8445 mechanisms of suppor=
ting both new and old ICE.<span class=3D"m_-6748401474167513945m_-955334991=
712834571m_1680274079720651929m_3204432535681369445m_-6802286700116899682Ap=
ple-converted-space">=C2=A0</span></span>Instead, we will move to say &quot=
;works with Browser X version Y or later.&quot; We have watched at W3C as i=
t moved to be that unless chrome does it, it rare that it becomes a standar=
d. =C2=A0<u></u><u></u></div><div style=3D"margin:0cm 0cm 0.0001pt;font-siz=
e:11pt;font-family:Calibri,sans-serif"><span lang=3D"EN-US">&gt;<span class=
=3D"m_-6748401474167513945m_-955334991712834571m_1680274079720651929m_32044=
32535681369445m_-6802286700116899682Apple-converted-space">=C2=A0</span></s=
pan><span lang=3D"EN-US">Right here I am watching how the stuff IETF define=
s will be less relevant than the issue of what chrome implements.=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></div></div><div style=3D"font=
-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal=
;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;=
text-transform:none;white-space:normal;word-spacing:0px;text-decoration:non=
e"><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri=
,sans-serif"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></div><div sty=
le=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif=
"><span lang=3D"EN-US">What exactly would Justin have to change?<u></u><u><=
/u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-f=
amily:Calibri,sans-serif"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span><=
/div></div></div></blockquote></div><br></div><div style=3D"overflow-wrap: =
break-word;"><div>For us, the largest part is having to test for both old a=
nd new - it=E2=80=99s not easy to do good automated testing for ICE.=C2=A0<=
/div></div>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div></blockquote></div><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_quote"></div></div>
_______________________________________________</blockquote></div><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Ice mailing list<br>
<a href=3D"mailto:Ice@ietf.org" target=3D"_blank">Ice@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ice" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ice</a><br>
</blockquote></div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div>
</blockquote></div></div></div>

--00000000000060d8e5057811d87f--


From nobody Sat Oct 13 02:23:23 2018
Return-Path: <sergio.garcia.murillo@gmail.com>
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 ACBA4130ED3; Sat, 13 Oct 2018 02:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 rOFA15A1GPTX; Sat, 13 Oct 2018 02:23:11 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 778F5130DFB; Sat, 13 Oct 2018 02:23:11 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id e4-v6so15854539wrs.0; Sat, 13 Oct 2018 02:23:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Sp9Nt9uE+JXulHdZQVT+BwLv9NztoQ+Rd9dmHrMralQ=; b=BT7QJGNmalxTS/AWqWfTAmxpgd+VQtm7Ucl0+OnfQZ3L4915LIEe3BK4nCwtHaGzLE Zw8mKNoWpWuhUwYE39uziadui6MpaqwGuB+wYknJfiPLsE76s1j+qaNEeLUwCSCP/bb/ cmEGIN7LeqX2306QVgo/hwP2dfbLn4pj/B6rXSbtUUd/N2BrVlvUwpHp/poEzNHEYf7a ISiJgT0JcYALp6uY1/lLY7L/9tat8EsgUWoDr8/lElNOxPl4Z+QMfR8NdsPIhiThoEoM fETCnE7yK34tcu77aidgmcKyBFUxZkqdHfda8jsZqpTG5pTfvWFxv9+AvTQGLM7/Vvje wPLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Sp9Nt9uE+JXulHdZQVT+BwLv9NztoQ+Rd9dmHrMralQ=; b=SStcxfpebV7wg/GrIcyl5eLL/kTxjHB3YBZJ69o+QTIkUpKXXyl6Pw9v1d44b0YIj4 B3PeVPMJWIALzskmct4mh6jE7oftAms+W16QZ7lLOKN5xoF6bJkgIizJefh7mlYvX7vh QR3vsPhlFfRHSNXaz0YHt0BPu/yijhDq2GQ0j+WTINhbnAMypRZjdzm7i0FTAqJ1lmVG 8+kRLhfye+fIqQf+1/cm8AN6wweneotMc4imjdDFGPL8dgw2Bh/19gG9PuxRFH+Na1g2 gdXvSiRqHnhvuNFHCXjj8EM5hOHJ8MI21D1OAbJKELbTQqN/6OGYB+BWaSmcVVYvFPj6 oKqw==
X-Gm-Message-State: ABuFfojBlIYT7b5ZVpSkig0hKI+1pb7SwaKnUCDfu2iHm3w0Ll6VZpmI cpS8dUOHhPY9IDGONj/u3+h7FyVNRHvWDL4zBAdomw==
X-Google-Smtp-Source: ACcGV60WWQuevL5fbD3oz4Gs8DzWxJeznaO8eAY/OgVF7CNyE1S+aMdU+7QwPHRRsrhRK2IcaVCgP1tz9/wrtcUzjcg=
X-Received: by 2002:a5d:6648:: with SMTP id f8-v6mr8226804wrw.218.1539422589907;  Sat, 13 Oct 2018 02:23:09 -0700 (PDT)
MIME-Version: 1.0
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca> <46E40ED2-D289-4C0F-8C0B-82A5980B2692@ericsson.com> <E05D7CB4-832E-4221-ADFE-D8F317EEA8F1@iii.ca> <CAJrXDUGpmZKGQXF0p1hjQv_F=5dQoJLUCT7+6y-=uzwcRv1Ncw@mail.gmail.com> <CAOJ7v-36OvrLo1ud3Uc2Edjk1n2kmY=2bkda-w5kVMVn2QfUVg@mail.gmail.com> <2f5dfed4-1f77-51cf-aec8-0d3e8e8edb14@nostrum.com>
In-Reply-To: <2f5dfed4-1f77-51cf-aec8-0d3e8e8edb14@nostrum.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Sat, 13 Oct 2018 11:22:58 +0200
Message-ID: <CA+ag07Yub+Qf56JxP2nKfhb8GT=Xodn9qHabjcVv2yJ1P9aOng@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Justin Uberti <juberti=40google.com@dmarc.ietf.org>,  pthatcher=40google.com@dmarc.ietf.org, mmusic@ietf.org, art@ietf.org,  "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, clue@ietf.org, ice@ietf.org, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a1789e057818c0bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/HXOpo0KFbvk7H-WY7yIstK49iJE>
Subject: Re: [art] [rtcweb] [MMUSIC] [Ice]  [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Oct 2018 09:23:14 -0000

--000000000000a1789e057818c0bb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

p0090

El lun., 1 oct. 2018 23:11, Adam Roach <adam@nostrum.com> escribi=C3=B3:

> On 9/27/18 6:20 PM, Justin Uberti wrote:
> > I agree with Peter. Chrome's implementation is already closer to 8445
> > than 5245, so I don't see any issues associated with snapping this
> > cluster to 8445 (aside from the work involved).
> >
> > On that topic, note that JSEP will need a few more changes than just
> > the addition of the 8445 reference and note; the examples will have to
> > be updated, as will the logic regarding generation of offers and
> > answers and their parsing (to deal with the new ice-option). These
> > changes will be modest but probably will need to be done by the authors=
.
>
>
> If I read what you're saying correctly, it sounds like you're talking
> about changes that are significant enough that we'll have to put JSEP
> through IETF last call and through the IESG again. That being the case,
> and the rest of the cluster being so close to done, I'd really prefer to
> see this done very soon, if such changes are required. When do you
> believe such an update could be available?
>
> I've copied the RFC Series Editor on this note for her awareness.
>
> /a
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

--000000000000a1789e057818c0bb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">p0090</div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
">El lun., 1 oct. 2018 23:11, Adam Roach &lt;<a href=3D"mailto:adam@nostrum=
.com">adam@nostrum.com</a>&gt; escribi=C3=B3:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">On 9/27/18 6:20 PM, Justin Uberti wrote:<br>
&gt; I agree with Peter. Chrome&#39;s implementation is already closer to 8=
445 <br>
&gt; than 5245, so I don&#39;t see any issues associated with snapping this=
 <br>
&gt; cluster to 8445 (aside from the work involved).<br>
&gt;<br>
&gt; On that topic, note that JSEP will need a few more changes than just <=
br>
&gt; the addition of the 8445 reference and note; the examples will have to=
 <br>
&gt; be updated, as will the logic regarding generation of offers and <br>
&gt; answers and their parsing (to deal with the new ice-option). These <br=
>
&gt; changes will be modest but probably will need to be done by the author=
s.<br>
<br>
<br>
If I read what you&#39;re saying correctly, it sounds like you&#39;re talki=
ng <br>
about changes that are significant enough that we&#39;ll have to put JSEP <=
br>
through IETF last call and through the IESG again. That being the case, <br=
>
and the rest of the cluster being so close to done, I&#39;d really prefer t=
o <br>
see this done very soon, if such changes are required. When do you <br>
believe such an update could be available?<br>
<br>
I&#39;ve copied the RFC Series Editor on this note for her awareness.<br>
<br>
/a<br>
<br>
_______________________________________________<br>
rtcweb mailing list<br>
<a href=3D"mailto:rtcweb@ietf.org" target=3D"_blank" rel=3D"noreferrer">rtc=
web@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtcweb" rel=3D"noreferrer =
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/rtcweb<=
/a><br>
</blockquote></div>

--000000000000a1789e057818c0bb--


From nobody Wed Oct 17 13:46:06 2018
Return-Path: <adam@nostrum.com>
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 68F8D130DFF for <art@ietfa.amsl.com>; Wed, 17 Oct 2018 13:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level: 
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qN2cbltMYiUq for <art@ietfa.amsl.com>; Wed, 17 Oct 2018 13:46:01 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 1AC12130DD9 for <art@ietf.org>; Wed, 17 Oct 2018 13:46:01 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9HKjxRB041851 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 17 Oct 2018 15:46:00 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Cullen Jennings <fluffy@iii.ca>, Applications and Real-Time Area Discussion <art@ietf.org>
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca>
From: Adam Roach <adam@nostrum.com>
Message-ID: <26aaec5e-0abb-a4af-3d0f-c94bda3aa251@nostrum.com>
Date: Wed, 17 Oct 2018 15:45:53 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca>
Content-Type: multipart/alternative; boundary="------------D7B6E60DEAD6A1869CFBB912"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ny-3iegplNK5bl-WLOiyIZAA0z4>
Subject: Re: [art] [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2018 20:46:05 -0000

This is a multi-part message in MIME format.
--------------D7B6E60DEAD6A1869CFBB912
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Cullen --

Thanks for sharing your perspective. In the spirit of section 3 of RFC 
7282, I
believe that the specific points you raised have been considered and 
addressed
(even though they haven't necessarily all been accommodated). I see evidence
that the impacted working groups have taken the objections seriously and
provided technically sound responses. I have taken steps to address the
process objection you highlighted regarding the timing and duration of the
period for feedback. Your input regarding the impact on two specific 
documents
beyond that which was called out in the original proposal has been noted and
is in the process of being addressed.

Specific details pertaining to each raised point can be found below.

On 9/6/18 3:24 PM, Cullen Jennings wrote:

 > It is not merely an issue of which document we point out, and they 
are all the
 > same. The problem is the timing of 8445 is not clearly interoperable 
with the
 > timing of 5245. ICE relies on both sides to do sequence things at 
roughly the
 > same order so that suicided packets open pinholes in the reverse 
direction at
 > the right time. The changes in timing change how this happens and is 
a problem
 > for the ICE algorithm.
 >
 > This was discussed in the WG, and though not everyone agrees it is a 
problem
 > or not, no one has ever provided a convincing argument that it is not.

Peter has attempted to do so. It is difficult to prove that something is 
not a
problem, but the explanation seems pretty compelling, especially when 
coupled
with Justin's later observation that the currently deployed Chrome code more
closely resembles RFC 8445 than it does RFC 5245.

 > This is
 > a very substantial change to the on the wire protocol and at a 
minimum would
 > need to be reviewed and discussed in the WG not slipped through in 
Auth 48
 > during a one week period in the summer while everyone is on vacation.

Based on your feedback, I have kept the issue open for eight weeks, 
including
four of which that are unambiguously not part of the northern hemisphere's
summer. I will also be running another IETF last call for the JSEP document,
to ensure proper exposure of this set of changes to the IETF community.

 > We will
 > also need to change other examples and normative text in drafts like 
JSEP.

A plan is being put in place to address JSEP's normative text (the authors
have already prepared a PR to address these changes), while the latest 
version
of the SDP examples document already contains such modifications.

 > I would propose that instead of the parts of specs that use the trickle
 > mechanism purely reference that part of the new ICE spec that defines the
 > syntax and say to transfer trickle candidates.

This preference has not received support from other participants.

 > Cisco has implemented stuff that is WebRTC 1.0 compliant without this 
change.
 > These gratuitous changes, years after the implementation were coded, 
with no
 > real benefit will ensure that we are not and will not become 
compliant with
 > the RFC. It's unlikely we will upgrade to the new ICE until it has real
 > befits. It is doubtful Justin will want to implement the 8445 
mechanisms of
 > supporting both new and old ICE.

Justin Uberti has indicated that Chrome's current behavior more closely
reflects RFC 8445 behavior than it does the behavior specified by RFC 5245,
and so this change brings the published documents closer to current browser
implementations than any proposed alternatives.  Nils Ohlmeier, who owns 
this
decision for Mozilla, has indicated that Firefox intends to implement 
both RFC
8445 and RFC 5245 behavior and use the "a=ice2" flag to determine which to
use. To the extent that Cisco products work with browsers deployed today,
these statements would seem to ensure that they should continue to do so in
the face of the plan I outlined.

 > Instead, we will move to say "works with
 > Browser X version Y or later." We have watched at W3C as it moved to 
be that
 > unless chrome does it, it rare that it becomes a standard. Right here 
I am
 > watching how the stuff IETF defines will be less relevant than the 
issue of
 > what chrome implements.

Given what Justin has indicated about Chrome's current behavior, this logic
would argue for moving to reference RFC 8445 rather than not doing so.

Again, thanks for taking the time to clearly spell our your objections 
so that
they could be fully considered by the interested parties. I believe that we
are in a better place, both from a process and from a protocol perspective,
because of your input.

/a


...
>> On Aug 22, 2018, at 10:58 AM, Adam Roach <adam@nostrum.com 
>> <mailto:adam@nostrum.com>> wrote:
>>
>> Members of the ART community interested in real-time communications:
>>
>> Cluster 238 [1] is a set of inter-related documents dealing with 
>> real-time communications. The bulk of these documents relate to 
>> WebRTC, either directly or indirectly. They also form the 
>> underpinnings of CLUE. As of now, there are 34 documents in the 
>> cluster that are not yet published, with 25 of these already in the 
>> RFC Editor's queue. The dependency graph among these documents is 
>> such that the bulk of them can be published as soon as a specific six 
>> of them are handed off to the RFC editor, and we expect this to 
>> happen in the upcoming few months.
>>
>> One long-running complication for this cluster of documents is that 
>> each of the documents were developed over the course of seven years, 
>> in concert with implementations, while the ICE protocol itself was 
>> undergoing significant revision. As a consequence, some documents 
>> rely (directly or indirectly) on the older ICE specification (RFC 
>> 5245), while some rely on the newer one (RFC 8445). In some cases, 
>> documents refer directly to the old version and transitively to the 
>> new version.
>>
>> It is noteworthy that RFC 8445 obsoletes RFC 5245; and that the 
>> mechanism described in RFC 8445 has some  changes that break 
>> backwards compatibility with the mechanism defined in RFC 5245 (with 
>> such behavioral changes controlled by an SDP attribute, allowing 
>> clients to transition from one to the other).
>>
>> Most notably, draft-ietf-rtcweb-jsep (which is the core WebRTC 
>> protocol in the IETF) refers to directly to RFC 5245, while relying 
>> on the behavior defined in draft-ietf-ice-trickle; 
>> draft-ietf-ice-trickle, in turn, is based on the newer RFC 8445 
>> handling. JSEP's reference to RFC 5245 is a practical consideration 
>> that acknowledges that current deployments of WebRTC implement the 
>> older version of ICE. At the same time, these deployed 
>> implementations use a somewhat older version of 
>> draft-ietf-ice-trickle in concert with the older ICE implementation.
>>
>> In order to get Cluster 238 published, we need to find some way to 
>> rationalize its references to ICE. At a basic level, the ART Area 
>> Directors do not believe that it makes sense to publish new documents 
>> that refer to an already obsoleted RFC. At the same time, we 
>> recognize that there is value in our specifications being informed by 
>> running code. For WebRTC, the complexity of the system has led us to 
>> a point that we must choose between these principles. Our proposal is 
>> to choose the first, while acknowledging the second.
>>
>> This would result in a request to the RFC editor to update all 
>> references to RFC 5245 in the Cluster 238 documents to instead point 
>> to RFC 8445. Documents not yet in the RFC editor queue would be 
>> updated prior to IESG review. We would further request that the RFC 
>> editor add the following text to draft-ietf-rtcweb-overview and 
>> draft-ietf-rtcweb-jsep:
>>
>>
>>> While this specification formally relies on [RFC8445], at the time 
>>> of its publication, the majority of WebRTC implementations support 
>>> the version of ICE described in [RFC5245], and use a pre-standard 
>>> version of the trickle ice mechanism described in [RFCXXXX]. The use 
>>> of the "ice2" attribute defined in [RFC8445] can be used to detect 
>>> the version in use by a remote endpoint and to provide a smooth 
>>> transition from the older specification to the newer one. 
>> RFC 8445 would be a normative reference for both documents, while RFC 
>> 5245 would be informative.
>>
>> There is one more minor complication, in that 
>> draft-ietf-mmusic-sdp-mux-attributes (which currently points to RFC 
>> 5245) is intended to be an exhaustive list of the SDP attributes 
>> defined in the documents it lists, and RFC 8445 adds a new "ice2" 
>> attribute that was not present in RFC 5245. For this reason, we would 
>> also ask the RFC Editor to add a new row to the table in 
>> draft-ietf-mmusic-sdp-mux-attributes section 5.12, as follows:
>>
>>
>>>     +-------------------+---------------------------+-------+-----------+
>>>     | Name              | Notes                     | Level | Mux       |
>>>     |                   |                           |       | Category  |
>>>     +-------------------+---------------------------+-------+-----------+
>>>     | ice2              | Not Impacted              | S     | NORMAL    |
>>>     |                   |                           |       |           |
>>>     +-------------------+---------------------------+-------+-----------+
>>
>> For clarity, the affected documents are as follows.
>>
>> The following documents would be updated to reference RFC 8445 prior 
>> to IESG evaluation:
>>
>>   * draft-ietf-clue-datachannel
>>   * draft-ietf-clue-signaling
>>   * draft-ietf-rtcweb-security
>>   * draft-ietf-rtcweb-security-arch
>>
>>
>> The following documents would be updated to reference RFC 8445 by the 
>> RFC Editor:
>>
>>   * draft-ietf-mmusic-mux-exclusive
>>   * draft-ietf-mmusic-sctp-sdp
>>   * draft-ietf-rtcweb-alpn
>>   * draft-ietf-rtcweb-data-channel
>>   * draft-ietf-rtcweb-rtp-usage
>>
>>
>> The following documents would be updated to reference RFC 8445 and 
>> have the text proposed above added to them:
>>
>>   * draft-ietf-rtcweb-jsep
>>   * draft-ietf-rtcweb-overview
>>
>>
>> The following document would be updated to reference RFC 8445 by the 
>> RFC Editor, and include a new row for "ice2" in its Section 5.12, as 
>> described above:
>>
>>   * draft-ietf-mmusic-sdp-mux-attributes
>>
>>
>> This message is cross-posted to the affected working groups. Because 
>> the issue at hand has impact across several different groups, we ask 
>> that all follow-up discussion take place on <art@ietf.org>. Thank you.
>>
>> /Adam on behalf of the ART Area Directors
>>
>> ____
>> [1] https://www.rfc-editor.org/cluster_info.php?cid=C238
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org <mailto:clue@ietf.org>
>> https://www.ietf.org/mailman/listinfo/clue
>
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art



--------------D7B6E60DEAD6A1869CFBB912
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Cullen --<br>
    <br>
    Thanks for sharing your perspective. In the spirit of section 3 of
    RFC 7282, I<br>
    believe that the specific points you raised have been considered and
    addressed<br>
    (even though they haven't necessarily all been accommodated). I see
    evidence<br>
    that the impacted working groups have taken the objections seriously
    and<br>
    provided technically sound responses. I have taken steps to address
    the<br>
    process objection you highlighted regarding the timing and duration
    of the<br>
    period for feedback. Your input regarding the impact on two specific
    documents<br>
    beyond that which was called out in the original proposal has been
    noted and<br>
    is in the process of being addressed.<br>
    <br>
    Specific details pertaining to each raised point can be found below.<br>
    <br>
    On 9/6/18 3:24 PM, Cullen Jennings wrote:<br>
    <br>
    &gt; It is not merely an issue of which document we point out, and
    they are all the<br>
    &gt; same. The problem is the timing of 8445 is not clearly
    interoperable with the<br>
    &gt; timing of 5245. ICE relies on both sides to do sequence things
    at roughly the<br>
    &gt; same order so that suicided packets open pinholes in the
    reverse direction at<br>
    &gt; the right time. The changes in timing change how this happens
    and is a problem<br>
    &gt; for the ICE algorithm.<br>
    &gt;<br>
    &gt; This was discussed in the WG, and though not everyone agrees it
    is a problem<br>
    &gt; or not, no one has ever provided a convincing argument that it
    is not.<br>
    <br>
    Peter has attempted to do so. It is difficult to prove that
    something is not a<br>
    problem, but the explanation seems pretty compelling, especially
    when coupled<br>
    with Justin's later observation that the currently deployed Chrome
    code more<br>
    closely resembles RFC 8445 than it does RFC 5245.<br>
    <br>
    &gt; This is<br>
    &gt; a very substantial change to the on the wire protocol and at a
    minimum would<br>
    &gt; need to be reviewed and discussed in the WG not slipped through
    in Auth 48<br>
    &gt; during a one week period in the summer while everyone is on
    vacation.<br>
    <br>
    Based on your feedback, I have kept the issue open for eight weeks,
    including<br>
    four of which that are unambiguously not part of the northern
    hemisphere's<br>
    summer. I will also be running another IETF last call for the JSEP
    document,<br>
    to ensure proper exposure of this set of changes to the IETF
    community.<br>
    <br>
    &gt; We will<br>
    &gt; also need to change other examples and normative text in drafts
    like JSEP.<br>
    <br>
    A plan is being put in place to address JSEP's normative text (the
    authors<br>
    have already prepared a PR to address these changes), while the
    latest version<br>
    of the SDP examples document already contains such modifications.<br>
    <br>
    &gt; I would propose that instead of the parts of specs that use the
    trickle<br>
    &gt; mechanism purely reference that part of the new ICE spec that
    defines the<br>
    &gt; syntax and say to transfer trickle candidates.<br>
    <br>
    This preference has not received support from other participants.<br>
    <br>
    &gt; Cisco has implemented stuff that is WebRTC 1.0 compliant
    without this change.<br>
    &gt; These gratuitous changes, years after the implementation were
    coded, with no<br>
    &gt; real benefit will ensure that we are not and will not become
    compliant with<br>
    &gt; the RFC. It's unlikely we will upgrade to the new ICE until it
    has real<br>
    &gt; befits. It is doubtful Justin will want to implement the 8445
    mechanisms of<br>
    &gt; supporting both new and old ICE.<br>
    <br>
    Justin Uberti has indicated that Chrome's current behavior more
    closely<br>
    reflects RFC 8445 behavior than it does the behavior specified by
    RFC 5245,<br>
    and so this change brings the published documents closer to current
    browser<br>
    implementations than any proposed alternatives.  Nils Ohlmeier, who
    owns this<br>
    decision for Mozilla, has indicated that Firefox intends to
    implement both RFC<br>
    8445 and RFC 5245 behavior and use the "a=ice2" flag to determine
    which to<br>
    use. To the extent that Cisco products work with browsers deployed
    today,<br>
    these statements would seem to ensure that they should continue to
    do so in<br>
    the face of the plan I outlined.<br>
    <br>
    &gt; Instead, we will move to say "works with<br>
    &gt; Browser X version Y or later." We have watched at W3C as it
    moved to be that<br>
    &gt; unless chrome does it, it rare that it becomes a standard. 
    Right here I am<br>
    &gt; watching how the stuff IETF defines will be less relevant than
    the issue of<br>
    &gt; what chrome implements.<br>
    <br>
    Given what Justin has indicated about Chrome's current behavior,
    this logic<br>
    would argue for moving to reference RFC 8445 rather than not doing
    so.<br>
    <br>
    Again, thanks for taking the time to clearly spell our your
    objections so that<br>
    they could be fully considered by the interested parties. I believe
    that we<br>
    are in a better place, both from a process and from a protocol
    perspective,<br>
    because of your input.<br>
    <br>
    /a<br>
    <br>
    <div class="moz-cite-prefix"><br>
    </div>
    ...
    <blockquote type="cite"
      cite="mid:7D1A35C5-FF09-4F93-ABA8-74D877952EF0@iii.ca">
      <div>
        <blockquote type="cite" class="">
          <div class="">On Aug 22, 2018, at 10:58 AM, Adam Roach &lt;<a
              href="mailto:adam@nostrum.com" class=""
              moz-do-not-send="true">adam@nostrum.com</a>&gt; wrote:</div>
          <br class="Apple-interchange-newline">
          <div class="">
            <meta http-equiv="content-type" content="text/html;
              charset=UTF-8" class="">
            <div text="#000000" bgcolor="#FFFFFF" class=""> Members of
              the ART community interested in real-time communications:
              <p class="">Cluster 238 [1] is a set of inter-related
                documents dealing with real-time communications. The
                bulk of these documents relate to WebRTC, either
                directly or indirectly. They also form the underpinnings
                of CLUE. As of now, there are 34 documents in the
                cluster that are not yet published, with 25 of these
                already in the RFC Editor's queue. The dependency graph
                among these documents is such that the bulk of them can
                be published as soon as a specific six of them are
                handed off to the RFC editor, and we expect this to
                happen in the upcoming few months.</p>
              <p class="">One long-running complication for this cluster
                of documents is that each of the documents were
                developed over the course of seven years, in concert
                with implementations, while the ICE protocol itself was
                undergoing significant revision. As a consequence, some
                documents rely (directly or indirectly) on the older ICE
                specification (RFC 5245), while some rely on the newer
                one (RFC 8445). In some cases, documents refer directly
                to the old version and transitively to the new version.<br
                  class="">
              </p>
              <p class="">It is noteworthy that RFC 8445 obsoletes RFC
                5245; and that the mechanism described in RFC 8445 has
                some  changes that break backwards compatibility with
                the mechanism defined in RFC 5245 (with such behavioral
                changes controlled by an SDP attribute, allowing clients
                to transition from one to the other).</p>
              <p class="">Most notably, draft-ietf-rtcweb-jsep (which is
                the core WebRTC protocol in the IETF) refers to directly
                to RFC 5245, while relying on the behavior defined in
                draft-ietf-ice-trickle; draft-ietf-ice-trickle, in turn,
                is based on the newer RFC 8445 handling. JSEP's
                reference to RFC 5245 is a practical consideration that
                acknowledges that current deployments of WebRTC
                implement the older version of ICE. At the same time,
                these deployed implementations use a somewhat older
                version of draft-ietf-ice-trickle in concert with the
                older ICE implementation.</p>
              <p class="">In order to get Cluster 238 published, we need
                to find some way to rationalize its references to ICE.
                At a basic level, the ART Area Directors do not believe
                that it makes sense to publish new documents that refer
                to an already obsoleted RFC. At the same time, we
                recognize that there is value in our specifications
                being informed by running code. For WebRTC, the
                complexity of the system has led us to a point that we
                must choose between these principles. Our proposal is to
                choose the first, while acknowledging the second.</p>
              <p class="">This would result in a request to the RFC
                editor to update all references to RFC 5245 in the
                Cluster 238 documents to instead point to RFC 8445.
                Documents not yet in the RFC editor queue would be
                updated prior to IESG review. We would further request
                that the RFC editor add the following text to
                draft-ietf-rtcweb-overview and draft-ietf-rtcweb-jsep:</p>
              <div class=""> <br class="webkit-block-placeholder">
              </div>
              <blockquote type="cite" class="">While this specification
                formally relies on [RFC8445], at the time of its
                publication, the majority of WebRTC implementations
                support the version of ICE described in [RFC5245], and
                use a pre-standard version of the trickle ice mechanism
                described in [RFCXXXX]. The use of the "ice2" attribute
                defined in [RFC8445] can be used to detect the version
                in use by a remote endpoint and to provide a smooth
                transition from the older specification to the newer
                one. </blockquote>
              RFC 8445 would be a normative reference for both
              documents, while RFC 5245 would be informative.
              <p class="">There is one more minor complication, in that
                draft-ietf-mmusic-sdp-mux-attributes (which currently
                points to RFC 5245) is intended to be an exhaustive list
                of the SDP attributes defined in the documents it lists,
                and RFC 8445 adds a new "ice2" attribute that was not
                present in RFC 5245. For this reason, we would also ask
                the RFC Editor to add a new row to the table in
                draft-ietf-mmusic-sdp-mux-attributes section 5.12, as
                follows:<br class="">
              </p>
              <div class=""> <br class="webkit-block-placeholder">
              </div>
              <blockquote type="cite" class="">
                <pre class="newpage">   +-------------------+---------------------------+-------+-----------+
   | Name              | Notes                     | Level | Mux       |
   |                   |                           |       | Category  |
   +-------------------+---------------------------+-------+-----------+
   | ice2              | Not Impacted              | S     | NORMAL    |
   |                   |                           |       |           |
   +-------------------+---------------------------+-------+-----------+
</pre>
              </blockquote>
              <br class="">
              <p class="">For clarity, the affected documents are as
                follows.</p>
              <p class="">The following documents would be updated to
                reference RFC 8445 prior to IESG evaluation:<br class="">
              </p>
              <ul class="">
                <li class="">draft-ietf-clue-datachannel<br class="">
                </li>
                <li class="">draft-ietf-clue-signaling</li>
                <li class="">draft-ietf-rtcweb-security</li>
                <li class="">draft-ietf-rtcweb-security-arch</li>
              </ul>
              <p class=""><br class="">
              </p>
              <p class="">The following documents would be updated to
                reference RFC 8445 by the RFC Editor:<br class="">
              </p>
              <ul class="">
                <li class="">draft-ietf-mmusic-mux-exclusive<br class="">
                </li>
                <li class="">draft-ietf-mmusic-sctp-sdp</li>
                <li class="">draft-ietf-rtcweb-alpn</li>
                <li class="">draft-ietf-rtcweb-data-channel</li>
                <li class="">draft-ietf-rtcweb-rtp-usage</li>
              </ul>
              <p class=""><br class="">
              </p>
              <p class="">The following documents would be updated to
                reference RFC 8445 and have the text proposed above
                added to them:<br class="">
              </p>
              <ul class="">
                <li class="">draft-ietf-rtcweb-jsep</li>
                <li class="">draft-ietf-rtcweb-overview</li>
              </ul>
              <p class=""><br class="">
              </p>
              <p class="">The following document would be updated to
                reference RFC 8445 by the RFC Editor, and include a new
                row for "ice2" in its Section 5.12, as described above:</p>
              <ul class="">
                <li class="">draft-ietf-mmusic-sdp-mux-attributes</li>
              </ul>
              <p class=""><br class="">
              </p>
              <p class="">This message is cross-posted to the affected
                working groups. Because the issue at hand has impact
                across several different groups, we ask that all
                follow-up discussion take place on <a
                  class="moz-txt-link-rfc2396E"
                  href="mailto:art@ietf.org" moz-do-not-send="true">&lt;art@ietf.org&gt;</a>.
                Thank you.</p>
              <p class="">/Adam on behalf of the ART Area Directors<br
                  class="">
              </p>
              <p class="">____<br class="">
                [1] <a class="moz-txt-link-freetext"
                  href="https://www.rfc-editor.org/cluster_info.php?cid=C238"
                  moz-do-not-send="true">https://www.rfc-editor.org/cluster_info.php?cid=C238</a><br
                  class="">
              </p>
            </div>
            _______________________________________________<br class="">
            clue mailing list<br class="">
            <a href="mailto:clue@ietf.org" class=""
              moz-do-not-send="true">clue@ietf.org</a><br class="">
            <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/clue">https://www.ietf.org/mailman/listinfo/clue</a><br class="">
          </div>
        </blockquote>
      </div>
      <br class="">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
art mailing list
<a class="moz-txt-link-abbreviated" href="mailto:art@ietf.org">art@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/art">https://www.ietf.org/mailman/listinfo/art</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------D7B6E60DEAD6A1869CFBB912--


From nobody Sat Oct 27 00:48:24 2018
Return-Path: <pradeep@explodingmoon.org>
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 EB1BE12785F for <art@ietfa.amsl.com>; Sat, 27 Oct 2018 00:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=explodingmoon.org
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 a59p1Z78Nt23 for <art@ietfa.amsl.com>; Sat, 27 Oct 2018 00:48:20 -0700 (PDT)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) (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 576EC128D68 for <art@ietf.org>; Sat, 27 Oct 2018 00:48:20 -0700 (PDT)
Received: from cmgw14.unifiedlayer.com (unknown [10.9.0.14]) by gproxy9.mail.unifiedlayer.com (Postfix) with ESMTP id 829991E0801 for <art@ietf.org>; Sat, 27 Oct 2018 01:48:19 -0600 (MDT)
Received: from box439.bluehost.com ([69.89.31.239]) by cmsmtp with ESMTP id GJKVgDz1svdTuGJKVgXdb3; Sat, 27 Oct 2018 01:48:19 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=explodingmoon.org; s=default; h=Content-Type:MIME-Version:Subject: Message-ID:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=dVw+PImnhdPekYSWy3CzIIw1klEKiooPXjg9mjKnnqg=; b=IOoxkDr++CJbS9qwpPZEeP/cg wnviwc/GLna+wm5+FBaAWXgzPgeQNULCQVbxKhAbps7P3Sh6OikhWqYOjtzw9JzGaF4biihaYRwMI YI+P46KEYO4sXVxLWo64jry6Hgsry30mDVMTgajawxowZ/4dQyN/5r7u6sOqtOdhRIfaOopxS6ZfD LxpRtpgaljQ0aDexzavyV4WZOyevJKUMU+5VQr8Q/lilC110fxWu/Wd+z2FAZONar69gFnAlje8D3 DLVUUuAxdooEv7w7zxdn+zwHG/1S8sK751hNIqKtE2Iv38Fgxn6vcAhJS7r92McTMNiX5sCP+PTM+ +lHCM9KXA==;
Received: from [42.109.144.179] (port=53973 helo=[10.220.23.202]) by box439.bluehost.com with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.91) (envelope-from <pradeep@explodingmoon.org>) id 1gGJKU-002f5d-Fg for art@ietf.org; Sat, 27 Oct 2018 01:48:19 -0600
Date: Sat, 27 Oct 2018 13:18:09 +0530
From: pradeep@explodingmoon.org
To: art@ietf.org
Message-ID: <43f5b117-d14f-44ba-bb4e-9ec7fba5ad68.maildroid@localhost>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_0_1122543800.1540626489831"
X-Mailer: MailDroid/4.91 (Android 4.2.2)
User-Agent: MailDroid/4.91 (Android 4.2.2)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box439.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - explodingmoon.org
X-BWhitelist: no
X-Source-IP: 42.109.144.179
X-Source-L: No
X-Exim-ID: 1gGJKU-002f5d-Fg
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([10.220.23.202]) [42.109.144.179]:53973
X-Source-Auth: pradeep@explodingmoon.org
X-Email-Count: 2
X-Source-Cap: ZXhwbG9kaTQ7ZXhwbG9kaTQ7Ym94NDM5LmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/CK1htIDBVqVI1EVW9HQGrz_GKhs>
Subject: [art] Where is private key stored if I generated key pair using openkeychain
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2018 07:48:22 -0000

------=_Part_0_1122543800.1540626489831
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

QSBHb29nbGUgYXBwLiBJIGNhbm5vdCBzaWduIHVzaW5nIGRyb2lkbWFpbC4gSSB1cGxvYWRlZCBw
dWJsaWMga2V5IGZvciBwcmFkZWVwQGV4cGxvZGluZ21vb24ub3JnIGluIHBncC5taXQuZWR1LgoK
U2VudCBmcm9tIE1haWxEcm9pZA==
------=_Part_0_1122543800.1540626489831
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

QSBHb29nbGUgYXBwLiBJIGNhbm5vdCBzaWduIHVzaW5nIGRyb2lkbWFpbC4gSSB1cGxvYWRlZCBw
dWJsaWMga2V5IGZvciA8YSBocmVmPSJtYWlsdG86cHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZyI+
cHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZzwvYT4gaW4gPGEgaHJlZj0iaHR0cDovL3BncC5taXQu
ZWR1Ij5wZ3AubWl0LmVkdTwvYT4uPGJyLz4KPGJyLz4KPGZvbnQgY29sb3I9IiM4ODg4ODgiPjxm
b250IGNvbG9yPSIjODg4ODg4Ij5TZW50IGZyb20gPC9mb250Pjxmb250IGNvbG9yPSIjODg4ODg4
Ij48YSBocmVmPSJodHRwczovL2dvby5nbC9PRGd3QmIiPk1haWxEcm9pZDwvYT48L2ZvbnQ+PC9m
b250Pg==
------=_Part_0_1122543800.1540626489831--


From nobody Sat Oct 27 01:18:33 2018
Return-Path: <pradeepan88@hotmail.com>
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 1748512F18C for <art@ietfa.amsl.com>; Sat, 27 Oct 2018 01:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 Uff9N2BSW-9U for <art@ietfa.amsl.com>; Sat, 27 Oct 2018 01:18:29 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254012.outbound.protection.outlook.com [40.92.254.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18CF0130D7A for <art@ietf.org>; Sat, 27 Oct 2018 01:18:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+Zl2z8kdGTAsAm6zbaFPS1bgap8/yApQSrwJThAvAjg=; b=gvWLiI+fVS+z0NqMZK6qVul7yg4wm3327rOtiGLW7GQWH9V2tPH86HXP1B2TyZXB9A9rqve7gVrlbiYFvGBjar00sQ/X8wHZHWC12oUbVjLK1iiyFrGsLKAgo1H0G5PhVJS1PfUVdR/thiKE7GjmqWtiEimzSLkc9fNML/MFRLAAaue+fPZk1Skz/FGrYcJJBFEZpODfPrCteXtBTtvt1j1eo0thLnQEY5Dd0wv7NDb0SVTqJbsZPMsgF9YoZTF+7tp6G8rKp9p/9Ffpw41NvN8s32SxFpFLThKOFf67z7W4aZjlWEZYJcpk48iiLqp6EjoHRL49VOGZf5TkfaxOEA==
Received: from SG2APC01FT116.eop-APC01.prod.protection.outlook.com (10.152.250.56) by SG2APC01HT038.eop-APC01.prod.protection.outlook.com (10.152.251.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14; Sat, 27 Oct 2018 08:18:26 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com (10.152.250.58) by SG2APC01FT116.mail.protection.outlook.com (10.152.250.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14 via Frontend Transport; Sat, 27 Oct 2018 08:18:26 +0000
Received: from SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::29d2:2729:f77b:e02e]) by SG2PR0302MB2606.apcprd03.prod.outlook.com ([fe80::29d2:2729:f77b:e02e%12]) with mapi id 15.20.1294.014; Sat, 27 Oct 2018 08:18:26 +0000
From: pradeep xplorer <pradeepan88@hotmail.com>
To: "art@ietf.org" <art@ietf.org>
Thread-Topic: Private key is stored where?
Thread-Index: AQHUbcziCo5TnEOBOUCOVlw6p5vXMqUyv6CA
Date: Sat, 27 Oct 2018 08:18:26 +0000
Message-ID: <SG2PR0302MB2606454F6E7677D853F3E4DCB7F10@SG2PR0302MB2606.apcprd03.prod.outlook.com>
References: <a012b87c-d851-4413-9688-21ffe7daabd2.maildroid@localhost> <db0ce854-b6fc-48b8-9558-4f670f2e3884.maildroid@localhost>
In-Reply-To: <db0ce854-b6fc-48b8-9558-4f670f2e3884.maildroid@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: MA1PR0101CA0061.INDPRD01.PROD.OUTLOOK.COM (2603:1096:a00:20::23) To SG2PR0302MB2606.apcprd03.prod.outlook.com (2603:1096:3:3::15)
x-incomingtopheadermarker: OriginalChecksum:5070FD9FC0CD9654410D2108DE451C8D7D5F602FA8E26A198BE0589D3AFAC2E0; UpperCasedChecksum:FDAC8760DD0C971D5AC58A7DF5DBE9674493E96F62A78F66F2FD25C630DA8C85; SizeAsReceived:7467; Count:49
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [OPUmJ/Ab87XJ995EVkpk3YNbt3hciMk7]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT038; 6:QRnQKBVleOSFsyOmLbb7Cx2B/sRYYFH4n8J9EosAk7aAn5PWBnjzop9p9+bMxeQPJuPfZ4H83oYtRzNSgelZOerjqxAAOeCQiddAwC6pg1iunUZLhz9xp+r0z0vJFo3ctedkv4G4Uv3HIoLqHmKVRvhA1tcibVg0p9vGkKpiYLYj8N+SOjFTk+e6dblucrk7EjL60szurKIG19QFhgmSmRkpVkizDg/+nRiDoSaB+hwClAr0y5DzY9nBrKTC1ZYP8ahvCbSAXyE+ennPOV+6/F21jMnFpSQVod7fkY6Qew8D8XKGjGOAk3wmUxMIZOp6Eakq5sWrr4H6rDNZN3vQA6JJM5lvQ1eE4zT9qiGQ6DzcHjQ3b16I62apRvIZegncii02XOmXq+D7LHur5nRmLQh+w5cy3VD3aURfFKp7U62lkTZryivhasvCJRMd9Q2C68PV5cjYBPDjAj+ak7Cthw==; 5:dBUXI2fOX8+wMsucRMqDa5oqDu0VYsGx7DDztDRk7M/AS1QaRfqlbGODAJgP4F8xbDojwa8bv5cOLANlbkW6avjHCRXZKvqTD0wijIxBejS82/wklTX1ie00K50PxtdibUkTsLj4U+iXilZtRjfL50QHsOlSwy1qPRIaeQzfwbE=; 7:QaZYDXH3QwyLGzyP9Vqhg/3DgmVlXWam3QhO6ztnQfPY4RvJZVMsf+rh4f4Guri5OxDJHjCs8Io0RS7mowY/skPHzmJgy2L4EevnqwCbbwaAcNGXO8nMe/U9+3DqGfhF/6sAYSq2LzNcHf+WdonfZQ==
x-incomingheadercount: 49
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:SG2APC01HT038; 
x-ms-traffictypediagnostic: SG2APC01HT038:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:SG2APC01HT038; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT038; 
x-microsoft-antispam-message-info: BOHr6dAJZKSwPch6lL3T0xPVwNqlAR5I2asko4sI1FnrAgqv6+n0GR3fdXs0KGc/
Content-Type: multipart/alternative; boundary="_000_SG2PR0302MB2606454F6E7677D853F3E4DCB7F10SG2PR0302MB2606_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 33235d18-1c12-4bce-a216-08d63be4c452
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Oct 2018 08:18:26.4666 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT038
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/n9RodykXNvkv4uroA84owxbQj5U>
Subject: [art] Fwd: Private key is stored where?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2018 08:18:31 -0000

--_000_SG2PR0302MB2606454F6E7677D853F3E4DCB7F10SG2PR0302MB2606_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpJIGFtIHVzaW5nIGRyb2lkbWFpbCBHb29nbGUgYXBwIEkgZ2VuZXJhdGVkIGEga2V5IHBhaXIg
Zm9yIHByYWRlZXBAZXhwbG9kaW5nbW9vbi5vcmc8bWFpbHRvOnByYWRlZXBAZXhwbG9kaW5nbW9v
bi5vcmc+IGJ1dCBJIGNhbid0IHNpZ24gaXQuIEFueW9uZSBoYXMgdXNlZCB0aGVzZS4gVGhlIG9w
ZW5rZXljaGFpbiBzaG93cyBhIGtleSBlbnRyeSBpbiBteSBhbmRyb2lkIHBob25lIHNhbXN1bmcN
ClNlbnQgZnJvbSBNYWlsRHJvaWQ8aHR0cHM6Ly9nb28uZ2wvT0Rnd0JiPg0KDQotLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogcHJhZGVlcGt1bWFyeHBsb3JlckBwcmFkZWVwa3VtYXJ4
cGxvcmVyLmNvbTxtYWlsdG86cHJhZGVlcGt1bWFyeHBsb3JlckBwcmFkZWVwa3VtYXJ4cGxvcmVy
LmNvbT4NClRvOiBwcmFkZWVwYW44OEBob3RtYWlsLmNvbTxtYWlsdG86cHJhZGVlcGFuODhAaG90
bWFpbC5jb20+DQpTZW50OiBTYXQsIDI3IE9jdCAyMDE4IDEzPHRlbDoyMDE4MTM+OjQzDQpTdWJq
ZWN0OiBGd2Q6IFByaXZhdGUga2V5IGlzIHN0b3JlZCB3aGVyZT8NCg0KDQoNClNlbnQgZnJvbSBN
YWlsRHJvaWQ8aHR0cHM6Ly9nb28uZ2wvT0Rnd0JiPg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogcHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZzxtYWlsdG86cHJhZGVlcEBleHBs
b2Rpbmdtb29uLm9yZz4NClRvOiBqb2huQGpjay5jb208bWFpbHRvOmpvaG5AamNrLmNvbT4NClNl
bnQ6IFNhdCwgMjcgT2N0IDIwMTggMTI8dGVsOjIwMTgxMj46NDcNClN1YmplY3Q6IFByaXZhdGUg
a2V5IGlzIHN0b3JlZCB3aGVyZT8NCg0KDQpJIHVzZWQgb3BlbmtleWNoYWluIGFuIGFuZHJvaWQg
YXBwIHRvIGNyZWF0ZSBrZXkgcGFpciBmb3IgcHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZzxtYWls
dG86cHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZz4gYW5kIGV4cG9ydGVkIHRoZSBwdWJsaWMga2V5
IGFuZCBpdCBzaG93cyBhIGtleSBpbiBteSBhbmRyb2lkIGJ1dCBJICBjYW4ndCBzaWduIHRoaXMg
ZW1haWwNCldoZXJlIGlzIHRoZSBwcml2YXRlIGtleSBzdG9yZWQ/DQpQcmFkZWVwIGt1bWFyIHhw
bG9yZXINClNlbnQgZnJvbSBNYWlsRHJvaWQ8aHR0cHM6Ly9nb28uZ2wvT0Rnd0JiPg0K

--_000_SG2PR0302MB2606454F6E7677D853F3E4DCB7F10SG2PR0302MB2606_
Content-Type: text/html; charset="utf-8"
Content-ID: <85505038A2D4AA439D669B631E433630@apcprd03.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGJyPg0KSSBhbSB1
c2luZyBkcm9pZG1haWwgR29vZ2xlIGFwcCBJIGdlbmVyYXRlZCBhIGtleSBwYWlyIGZvciA8YSBo
cmVmPSJtYWlsdG86cHJhZGVlcEBleHBsb2Rpbmdtb29uLm9yZyI+DQpwcmFkZWVwQGV4cGxvZGlu
Z21vb24ub3JnPC9hPiBidXQgSSBjYW4ndCBzaWduIGl0LiBBbnlvbmUgaGFzIHVzZWQgdGhlc2Uu
IFRoZSBvcGVua2V5Y2hhaW4gc2hvd3MgYSBrZXkgZW50cnkgaW4gbXkgYW5kcm9pZCBwaG9uZSBz
YW1zdW5nPGJyPg0KPGZvbnQgY29sb3I9IiM4ODg4ODgiPjxmb250IGNvbG9yPSIjODg4ODg4Ij5T
ZW50IGZyb20gPC9mb250Pjxmb250IGNvbG9yPSIjODg4ODg4Ij48YSBocmVmPSJodHRwczovL2dv
by5nbC9PRGd3QmIiPk1haWxEcm9pZDwvYT48L2ZvbnQ+PC9mb250Pjxicj4NCjxicj4NCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogPGEgaHJlZj0ibWFpbHRvOnByYWRlZXBr
dW1hcnhwbG9yZXJAcHJhZGVlcGt1bWFyeHBsb3Jlci5jb20iPnByYWRlZXBrdW1hcnhwbG9yZXJA
cHJhZGVlcGt1bWFyeHBsb3Jlci5jb208L2E+PGJyPg0KVG86IDxhIGhyZWY9Im1haWx0bzpwcmFk
ZWVwYW44OEBob3RtYWlsLmNvbSI+cHJhZGVlcGFuODhAaG90bWFpbC5jb208L2E+PGJyPg0KU2Vu
dDogU2F0LCAyNyBPY3QgPGEgaHJlZj0idGVsOjIwMTgxMyI+MjAxOCAxMzwvYT46NDM8YnI+DQpT
dWJqZWN0OiBGd2Q6IFByaXZhdGUga2V5IGlzIHN0b3JlZCB3aGVyZT88YnI+DQo8YnI+DQo8YnI+
DQo8YnI+DQo8Zm9udCBjb2xvcj0iIzg4ODg4OCI+PGZvbnQgY29sb3I9IiM4ODg4ODgiPlNlbnQg
ZnJvbSA8L2ZvbnQ+PC9mb250Pjxmb250IGNvbG9yPSIjODg4ODg4Ij48Zm9udCBjb2xvcj0iIzg4
ODg4OCI+PGEgaHJlZj0iaHR0cHM6Ly9nb28uZ2wvT0Rnd0JiIj5NYWlsRHJvaWQ8L2E+PC9mb250
PjwvZm9udD48YnI+DQo8YnI+DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206
IDxhIGhyZWY9Im1haWx0bzpwcmFkZWVwQGV4cGxvZGluZ21vb24ub3JnIj5wcmFkZWVwQGV4cGxv
ZGluZ21vb24ub3JnPC9hPjxicj4NClRvOiA8YSBocmVmPSJtYWlsdG86am9obkBqY2suY29tIj5q
b2huQGpjay5jb208L2E+PGJyPg0KU2VudDogU2F0LCAyNyBPY3QgPGEgaHJlZj0idGVsOjIwMTgx
MiI+MjAxOCAxMjwvYT46NDc8YnI+DQpTdWJqZWN0OiBQcml2YXRlIGtleSBpcyBzdG9yZWQgd2hl
cmU/PGJyPg0KPGJyPg0KPGJyPg0KSSB1c2VkIG9wZW5rZXljaGFpbiBhbiBhbmRyb2lkIGFwcCB0
byBjcmVhdGUga2V5IHBhaXIgZm9yIDxhIGhyZWY9Im1haWx0bzpwcmFkZWVwQGV4cGxvZGluZ21v
b24ub3JnIj4NCnByYWRlZXBAZXhwbG9kaW5nbW9vbi5vcmc8L2E+IGFuZCBleHBvcnRlZCB0aGUg
cHVibGljIGtleSBhbmQgaXQgc2hvd3MgYSBrZXkgaW4gbXkgYW5kcm9pZCBidXQgSSZuYnNwOyBj
YW4ndCBzaWduIHRoaXMgZW1haWw8YnI+DQpXaGVyZSBpcyB0aGUgcHJpdmF0ZSBrZXkgc3RvcmVk
Pzxicj4NClByYWRlZXAga3VtYXIgeHBsb3Jlcjxicj4NCjxmb250IGNvbG9yPSIjODg4ODg4Ij48
Zm9udCBjb2xvcj0iIzg4ODg4OCI+U2VudCBmcm9tIDwvZm9udD48L2ZvbnQ+PGZvbnQgY29sb3I9
IiM4ODg4ODgiPjxmb250IGNvbG9yPSIjODg4ODg4Ij48YSBocmVmPSJodHRwczovL2dvby5nbC9P
RGd3QmIiPk1haWxEcm9pZDwvYT48L2ZvbnQ+PC9mb250Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_SG2PR0302MB2606454F6E7677D853F3E4DCB7F10SG2PR0302MB2606_--

