
From nobody Tue Jul  3 03:27:08 2018
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70631130DCE; Tue,  3 Jul 2018 03:27:06 -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 OFClbZq4kZUZ; Tue,  3 Jul 2018 03:27:04 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (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 0D080130E29; Tue,  3 Jul 2018 03:27:03 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1faIWR-0000Hf-U5; Tue, 03 Jul 2018 12:26:59 +0200
Date: Tue, 3 Jul 2018 12:26:59 +0200 (CEST)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: saag@ietf.org
cc: IETF DISPATCH list <dispatch@ietf.org>
Message-ID: <alpine.DEB.2.20.1807031213110.2443@softronics.hoeneisen.ch>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/LP4aAZ0tqaKDtNm4KV1NvxlGiXw>
Subject: [dispatch] New Internet-Drafts on pEp - Privacy by Default
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2018 10:27:07 -0000

Dear SAAG WG
CC DISPATCH WG

Please be informed that we have submitted five Internet Drafts 
(see below) regarding the pEp (pretty Easy privacy) approach, which 
aims for opportunistic encryption of email and other messaging. The 
pEp technology is aimed to be as easy as possible for the end user, so 
that privacy technology will be widely implemented and used.


Overview of existing pEp Internet-Drafts:

- pEp General: Basic pEp concepts / requirements generally applicable
     https://tools.ietf.org/html/draft-birk-pep-02

- pEp Email: pEp concepts specifically applied to email communication
   (automatic generation of key pairs, automatic usage of encryption,
   privacy enhancements to existing email message formats, etc.)
     https://tools.ietf.org/html/draft-marques-pep-email-00
   Note: This -00 I-D is yet in a "rough" state.

- pEp Handshake: Easy process to ensure authentication of communication
   partners and channels using Trustwords.
     https://tools.ietf.org/html/draft-marques-pep-handshake-00

- pEp Trustwords: IANA Registration for Trustwords in different languages.
     https://tools.ietf.org/html/draft-birk-pep-trustwords-02

- pEp Privacy Rating: Definition of different Privacy States (unreliable,
   encrypted, etc.) and its mapping to a traffic light semantics
   (red, yellow, green, none) as an intuitive means for presenting the
   actual Privacy Status to the user.
     https://tools.ietf.org/html/draft-marques-pep-rating-00

Note: More I-Ds are still in the pipeline, e.g. synchronization of secret 
keys among different devices of the same user.


We are looking forward to your feedback!


All the best
  Bernie

--

http://ucom.ch/
Modern Telephony Solutions and Tech Consulting for Internet Technology


From nobody Tue Jul  3 09:04:19 2018
Return-Path: <agenda@ietf.org>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE107130F8E; Tue,  3 Jul 2018 09:00:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <mary.ietf.barnes@gmail.com>, <dispatch-chairs@ietf.org>
Cc: ben@nostrum.com, dispatch@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153063362170.4893.5029587286689908393.idtracker@ietfa.amsl.com>
Date: Tue, 03 Jul 2018 09:00:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/gYPiJP9XSvfymrYGjVsnzgy_WwE>
Subject: [dispatch] dispatch - Requested session has been scheduled for IETF 102
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.26
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2018 16:00:31 -0000

Dear Mary Barnes,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    dispatch Session 1 (2:30 requested)
    Monday, 16 July 2018, Morning Session I 0930-1200
    Room Name: Duluth size: 150
    ---------------------------------------------

Special Note: Joint with ARTAREA

iCalendar: https://datatracker.ietf.org/meeting/102/sessions/dispatch.ics

Request Information:


---------------------------------------------------------
Working Group Name: Dispatch
Area Name: Applications and Real-Time Area
Session Requester: Mary Barnes

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 80
Conflicts to Avoid: 
 First Priority: jmap uta dmarc xrblock stir sipcore rtcweb rmcat payload netvc mmusic insipid ecrit avtcore bfcpbis clue core dcrup doh extra cfrg
 Second Priority: tram tsvwg tsvarea opsarea



People who must be present:
  Alexey Melnikov
  Mary Barnes
  Adam Roach
  Ben Campbell
  Cullen Jennings
  Murray Kucherawy

Resources Requested:

Special Requests:
  Please schedule in the 1st slot on Monday morning, list the meeting as coupled with ARTAREA, and avoid the same kind of conflicts with other area meetings and any Bofs and potential new ART WGs.
---------------------------------------------------------


From nobody Tue Jul 10 11:15:20 2018
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1472F130F04; Tue, 10 Jul 2018 11:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 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, HTML_OBFUSCATE_05_10=0.26, 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 E0MzrXzINQGY; Tue, 10 Jul 2018 11:15:11 -0700 (PDT)
Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com [IPv6:2a00:1450:4010:c07::242]) (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 486F5131053; Tue, 10 Jul 2018 11:15:08 -0700 (PDT)
Received: by mail-lf0-x242.google.com with SMTP id f18-v6so3007782lfc.2; Tue, 10 Jul 2018 11:15:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=CeF5VRDMQJKEeZYQb+xZh/KtApJtC4yJCT8aCxcmIUA=; b=Z92mwJhVwX1NxkuGTdJBPgSVNDg3jqs+oPjrckAshhCqFvDO2Gsw5wJc2roGVAAce1 jm9A1nqy6EqzmyEvHOnA+3ovn/8RYXvao0Ff5bziiI/mIheLsh5icN+mLIQC8itD4TQs 8ybUR3L/fqaXWnpGcy9u2pUEQCTKweLRHrAq2cPq6suNdRmbtXAsjjRpO2kSbo0fhv5T 3w/R3BasxYz4HAFPMtWWOXFWE5jzMG/dym4qscX6MXeYYZHFPuLkzaFrZFiv1TdUyqgs svV/5qQWmNcZLuSp7uYxfajpAkUYiqy9Ro5QOKOeoGRrs85cmSSUV/DPdWx5LASzXshT jhyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=CeF5VRDMQJKEeZYQb+xZh/KtApJtC4yJCT8aCxcmIUA=; b=jixz4y5ct+w0/fgVyrzm2T67YoHXvsW7ld4PVE/9qpnJoS/6vLmm+rrt38IJViFPiM mBL//Mw4QaSK9TsYTQ/IfK0LO4DNAP/bZ51LeM5s6A4b+C0eldLFwQXDF6aW1vlhJRum rIVqPjLIBjhzOYCTYPdZPHbU+kBAoq2x4pQETQ5ofWTV/k8id7YX8mJPki7NHVTSslg9 Bz8UMlKB2mzMDxk0fweOGcYhAN7hbgLHsvVx3lStBI6aW6YGRZPXgs5SqJ4pZLYSnf9e wGBRwZxljPJ/LDXoWafBVRleoE+oGVkXylGCksgEiaAnEaAUdNpbr0G8SWYd6BMYyfbY SR5g==
X-Gm-Message-State: APt69E0Zg9hXHleAG0lvOAYbs/VCZ6GVG8vknhfJYWs9TrgAjKENcvgz XDtli9gt7VsWY2+TCnhRm83bc9S7JgJ8guvwLuo=
X-Google-Smtp-Source: AAOMgpd0K2wa9A9Pn3n1o6SUYrlqKJs2cm/4YIwaIq80WrJD2vry1R+lIyyZx4NvRmuhpdcRB892GjQe3BvQ2zH5g1A=
X-Received: by 2002:a19:169f:: with SMTP id 31-v6mr3527023lfw.72.1531246505983;  Tue, 10 Jul 2018 11:15:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:9f51:0:0:0:0:0 with HTTP; Tue, 10 Jul 2018 11:15:04 -0700 (PDT)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Tue, 10 Jul 2018 13:15:04 -0500
Message-ID: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>
Cc: draft-ietf-dispatch-javascript-mjs@ietf.org,  Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="0000000000000d822c0570a91c1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/X3aBzTbPFT8bJRAYcO7ldjJmAls>
Subject: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 18:15:16 -0000

--0000000000000d822c0570a91c1e
Content-Type: text/plain; charset="UTF-8"

Hi all,


We would like to start a 2 week WGLC for this document.    If you think the
document is ready, please respond to this email.  If you have comments that
you would like considered and/or any editorial suggestions, please post
those as well.


The WGLC ends on July 25, 2018.


Regards,

Mary

DISPATCH WG tri-chair

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, May 8, 2018 at 5:41 PM
Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.txt
To: i-d-announce@ietf.org
Cc: dispatch@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Dispatch WG of the IETF.

        Title           : ECMAScript Media Types Updates
        Authors         : Bradley Farias
                          Matthew A. Miller
        Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
        Pages           : 21
        Date            : 2018-05-08

Abstract:
   This document proposes updates to the ECMAScript media types,
   superseding the existing registrations for "application/javascript"
   and "text/javascript" by adding an additional extension and removing
   usage warnings.  This document updates RFC4329, "Scripting Media
   Types".


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><p class=3D"m_=
-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:normal;font-va=
riant:normal;font-weight:normal;font-stretch:normal;font-size:12px;line-hei=
ght:normal;font-family:Helvetica">Hi all,</p>
<p class=3D"m_-8386734740231134962gmail-p2" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"m_-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica"><span class=3D"m_-838673474=
0231134962gmail-Apple-converted-space">We would like to start a 2 week WGLC=
 for this document.=C2=A0 =C2=A0=C2=A0</span>If you think the document is r=
eady, please respond to this email.=C2=A0 If you have comments that you wou=
ld like considered and/or any editorial suggestions, please post those as w=
ell.=C2=A0<br></p><p class=3D"m_-8386734740231134962gmail-p1" style=3D"marg=
in:0px;font-style:normal;font-variant:normal;font-weight:normal;font-stretc=
h:normal;font-size:12px;line-height:normal;font-family:Helvetica"><br></p><=
p class=3D"m_-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:n=
ormal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:=
12px;line-height:normal;font-family:Helvetica">The WGLC ends on July 25, 20=
18.=C2=A0</p>
<p class=3D"m_-8386734740231134962gmail-p2" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"m_-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica">Regards,</p>
<p class=3D"m_-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica">Mary<span class=3D"m_-83867=
34740231134962gmail-Apple-converted-space">=C2=A0</span></p>
<p class=3D"m_-8386734740231134962gmail-p1" style=3D"margin:0px;font-style:=
normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica">DISPATCH WG tri-chair</p>


<br><div class=3D"gmail_quote">---------- Forwarded message ----------<br>F=
rom: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</=
a>&gt;</span><br>Date: Tue, May 8, 2018 at 5:41 PM<br>Subject: [dispatch] I=
-D Action: draft-ietf-dispatch-<wbr>javascript-mjs-02.txt<br>To: <a href=3D=
"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce@ietf.org</a><=
br>Cc: <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf=
.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Dispatch WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 ECMAScript Media Types Updates<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Brad=
ley Farias<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Matthew A. Miller<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-dispatch-javascript<wbr>-mjs-02.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 21<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-05-08<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document proposes updates to the ECMAScript media types,<=
br>
=C2=A0 =C2=A0superseding the existing registrations for &quot;application/j=
avascript&quot;<br>
=C2=A0 =C2=A0and &quot;text/javascript&quot; by adding an additional extens=
ion and removing<br>
=C2=A0 =C2=A0usage warnings.=C2=A0 This document updates RFC4329, &quot;Scr=
ipting Media<br>
=C2=A0 =C2=A0Types&quot;.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-=
mjs/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<w=
br>oc/draft-ietf-dispatch-javascr<wbr>ipt-mjs/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-0=
2" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>=
aft-ietf-dispatch-javascript-<wbr>mjs-02</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javasc=
ript-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/d<wbr>oc/html/draft-ietf-dispatch-ja<wbr>vascript-mjs-02</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dispatch-javascri=
pt-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdif=
f?u<wbr>rl2=3Ddraft-ietf-dispatch-javasc<wbr>ript-mjs-02</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
<br>
______________________________<wbr>_________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/dispatch</a=
><br>
</div><br></div>
</div><br></div>

--0000000000000d822c0570a91c1e--


From nobody Tue Jul 10 16:49:34 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B9F130DE3; Tue, 10 Jul 2018 16:49:33 -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, 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 G_iORH4PE6oJ; Tue, 10 Jul 2018 16:49:29 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 9B6FF130DDC; Tue, 10 Jul 2018 16:49:29 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id b15-v6so45958450oib.10; Tue, 10 Jul 2018 16:49:29 -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=/F6GO8K0Qtx4RL6X3CjSPmYdUXvUrVTHQLSKar1HzR8=; b=P+GNB/WAI8iB1hzyNpt2Y0rjNjCpLVePT6f+IzcLbBqpVmrUAHcSZdWQLsC8TOPOpY +WPJ8O0t8Ja0VvX+ijY7Si+l+Slv2dCPdxTqs7h0RjmJW0zJdAYkcn7P3dh/58sP1nmy ZIdMU3hPv/5gBjvevfGLhmD6inAhPyFDuRl8uVxAUXA8Uaoc8nQhG991bftovjAy07+2 7oIJDIt/Ot32unSqLLd0Py/VZgNLNvrxEODVimP2q5OXXKtgTnVgolP4kAH5k+JgFJXx VJSrV+EV5OgSnThI+BJFiVtPsfrkBntgMwHalGgOGGexcejBqo6CT2a7JxNtESanrhTl JuFg==
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=/F6GO8K0Qtx4RL6X3CjSPmYdUXvUrVTHQLSKar1HzR8=; b=Ale/WEMlRZaY/leB9+U2ax28rU8PL5qM2ysUQgqZdXfTVuRlIuIzy2Abp08a5LvVMb Tk1gIoUeroVO8w+E3Qgruq5ovUuGAp8eJ5hJTpSd+8rRXPaKtPAHhU5Fik6ih3hxQrPe qdcAWiClVZamZX4dt7T6H3JQF7Qi4HB+dPfGWTN17y8Lh//yjwFQ1aBTu+pZc5LfAGh5 pD+dXGgM3nA/ZASnXu62M2JeppcBMwDKcch9Ts1bJoqzuR8pjPWwrDagqzbaIIpiKTaB 0KYlYNwAP/S63Ot1XfTC+mVh9PioZKq+65EuB+FMflMzyBpJLanGvV0Il7VsOv7qtruU KrKA==
X-Gm-Message-State: APt69E1Txr16FCVoJyb32Qj/y/2OOs+dgZbCCZFmoiyWyqV17NCFjQ9j Ptb26Z68sJs8oCXMYkOE3OIJRthRK8eH/lwz/O4=
X-Google-Smtp-Source: AAOMgpfx8Ekid1JW4FHiyamskE3RRsgEqnzhfIMPFS5IL0kOLcGG+s7Nme+nyk7sONwAwZ2UggiOXMRgYTjPEIKJHFc=
X-Received: by 2002:aca:3d43:: with SMTP id k64-v6mr28260445oia.166.1531266568801;  Tue, 10 Jul 2018 16:49:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
In-Reply-To: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 11 Jul 2018 09:49:17 +1000
Message-ID: <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Cc: DISPATCH <dispatch@ietf.org>, Barry Leiba <barryleiba@computer.org>,  draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/8X4vIcN8MkQmSqdoUXNoAfYfqLs>
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 23:49:34 -0000

LGTM

It's odd to see Matt listed in the acknowledgments and as an author.

It would help to have a short statement saying which of the many media
types is not obsolete, as the bulk of them are.
On Wed, Jul 11, 2018 at 4:15 AM Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>
> Hi all,
>
>
> We would like to start a 2 week WGLC for this document.    If you think the document is ready, please respond to this email.  If you have comments that you would like considered and/or any editorial suggestions, please post those as well.
>
>
> The WGLC ends on July 25, 2018.
>
>
> Regards,
>
> Mary
>
> DISPATCH WG tri-chair
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Tue, May 8, 2018 at 5:41 PM
> Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.txt
> To: i-d-announce@ietf.org
> Cc: dispatch@ietf..org
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Dispatch WG of the IETF.
>
>         Title           : ECMAScript Media Types Updates
>         Authors         : Bradley Farias
>                           Matthew A. Miller
>         Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
>         Pages           : 21
>         Date            : 2018-05-08
>
> Abstract:
>    This document proposes updates to the ECMAScript media types,
>    superseding the existing registrations for "application/javascript"
>    and "text/javascript" by adding an additional extension and removing
>    usage warnings.  This document updates RFC4329, "Scripting Media
>    Types".
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
> https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-02
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From nobody Tue Jul 10 18:05:18 2018
Return-Path: <dbaron@dbaron.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8622130DC7; Tue, 10 Jul 2018 18:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.941
X-Spam-Level: 
X-Spam-Status: No, score=-1.941 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dbaron.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 IwUeaqLxp8YI; Tue, 10 Jul 2018 18:05:15 -0700 (PDT)
Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 947B0127332; Tue, 10 Jul 2018 18:05:13 -0700 (PDT)
X-Originating-IP: 103.21.135.19
Received: from pescadero.dbaron.org (unknown [103.21.135.19]) (Authenticated sender: dbaron-out@dbaron.org) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id AD13C240007; Wed, 11 Jul 2018 01:05:10 +0000 (UTC)
Received: by pescadero.dbaron.org (Postfix, from userid 1000) id D378E120119; Wed, 11 Jul 2018 01:05:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbaron.org; s=b; t=1531271105; bh=+3ePGb+sNY/PU3JkNz3GBl09ehgXV+lW7hyTVGHtyfg=; l=5519; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pdlxQhLHvk/a4lza0TYCO0uuQIis+5JtXDAoIDaXd+GImP1Y7NI9LJtwrb1iirSMw foq0rClAGkm9IyZwM/Nr2HcmUlLi73O6og+RDCWY1Z2WJc4ALugeT5qhXQsd+QeY1W msI4SM4j4ii/BeC2xFToc583sMkTptvRbtl2bBXLu9BJykcEIbXclXb3sALRezN1Sa cfF1F7dl9KwohG0jIzRlbTCWQ6oV3ljwHCFbW5pkACXj7PEFr9jPs49Hai7VDQb+N/ EEYWUHv7pfD/HYTJlB7ZmSnD9kLSo6wdXVbRaNCxVaTrATyCJzcw6XBoqhhrNfLV8E SIuikMXRPNPQA==
Date: Wed, 11 Jul 2018 11:05:05 +1000
From: "L. David Baron" <dbaron@dbaron.org>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Cc: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org,  Barry Leiba <barryleiba@computer.org>
Message-ID: <20180711010505.GA4920@pescadero.dbaron.org>
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB"
Content-Disposition: inline
In-Reply-To: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/lnvyIRAfg7-Di_ynVz0D74PdkSI>
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 01:05:18 -0000

--DocE+STaALJfprDB
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi -

I have a few comments on the document:


There are two things that might be read to imply that processors
(e.g., browsers) should change their behavior as a result of file
extensions.  In particular, in section 4 (Registration):

                                                           In addition,
   a new file extension of .mjs is to be added to the list of file
   extensions with the restriction that it must correspond to the Module
   grammar of [ECMA-262].

and then repeatedly in the subsections of that section:

   Restrictions on usage:  The file extension .mjs must be parsed using
      the Module grammar of [ECMA-262]=20

This seems like a reasonable thing to suggest as the intended use of
the .mjs extension, but I think it could be read to imply that
implementations should change their behavior as a result of file
extensions, which would be a rather unusual requirement on the Web.

If that requirement were the intent, it would seem to contradict the
processing rules for script elements in the HTML specification at:
https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type
which specify that the type attribute on the script element
determines whether a script is interpreted as a classic script or as
a module script.


Additionally, I wonder whether it would be useful to have a section
that documents the changes from RFC4329.  The introduction to
section 4 (Registration) seems to document some of them, but I
noticed that it doesn't mention that application/ecmascript and
application/javascript have been changed to Obsolete, and a number
of types not previously listed in RFC4329 (but listed in
https://mimesniff.spec.whatwg.org/#javascript-mime-type) have been
added as Obsolete.  (I didn't check for other differences.)


I'm happy to see the obsolete/common distinction in this draft
reflecting current practice.

-David


On Tuesday 2018-07-10 13:15 -0500, Mary Barnes wrote:
> Hi all,
>=20
>=20
> We would like to start a 2 week WGLC for this document.    If you think t=
he
> document is ready, please respond to this email.  If you have comments th=
at
> you would like considered and/or any editorial suggestions, please post
> those as well.
>=20
>=20
> The WGLC ends on July 25, 2018.
>=20
>=20
> Regards,
>=20
> Mary
>=20
> DISPATCH WG tri-chair
>=20
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>;
> Date: Tue, May 8, 2018 at 5:41 PM
> Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.txt
> To: i-d-announce@ietf.org
> Cc: dispatch@ietf.org
>=20
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Dispatch WG of the IETF.
>=20
>         Title           : ECMAScript Media Types Updates
>         Authors         : Bradley Farias
>                           Matthew A. Miller
>         Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
>         Pages           : 21
>         Date            : 2018-05-08
>=20
> Abstract:
>    This document proposes updates to the ECMAScript media types,
>    superseding the existing registrations for "application/javascript"
>    and "text/javascript" by adding an additional extension and removing
>    usage warnings.  This document updates RFC4329, "Scripting Media
>    Types".
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
> https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-=
02
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dispatch-javascript-mjs-02
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>=20

--=20
=F0=9D=84=9E   L. David Baron                         http://dbaron.org/   =
=F0=9D=84=82
=F0=9D=84=A2   Mozilla                          https://www.mozilla.org/   =
=F0=9D=84=82
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

--DocE+STaALJfprDB
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkIYF7CKIBR780rBx7+FhJQ+E/CEFAltFV78ACgkQ7+FhJQ+E
/CEi1BAAhSd9ibHgEd5QS3lo2EJfhJjCpvIhvOACt2DaJnDUcbVBguSH8IsQz7VV
84ZKMevswZCMeCnc5yNw70EZYvtRLe6KFBJkqn1YhDv9lbM5qZAfbaYvO18VRmVx
tE7dMoWKKpYCEkOloSD2NS2v76RFK3VNLVNg9XdoIilkCCo1hPmRkwZrxIEatUbu
nmJxAo/P2zPQ0FluoQwxtDijsg+dkvoKo/djVQ7efM5zXjYdFnBJO01AvqCWCoGr
Ijdj0ElHF5APOcb528zL/ClK1i/1NaxPSVHIDF86AfE4BbvGXHNL3/vQg1zIYrd5
/Ci7OIgPfXfGwZ7KdkvW1wq+9XHBR/Iyqa5m9PeNtARuCnsBNAA07bguO3EuTKYw
mCtRiRBU72yL7VizxYoKjK1AKmNuS1DcqkZtlUpX2eBFAfHarktvrA7hurnITdbE
C5tkXiHzdQGcmnHI94JeqPxIQYAZd3kBuFBc4LFuhC8+ekxtBgmDq7rg+8ODeVX5
SZUtiIrUqUsLJuScrAhGNw2S3LNAphs+Zx4WNBoXx94E4iKcd/CUOdMHnrsrvwtK
Dt4shNXvrJEI0V4x6SNB93Lu2O50oWlRFMM9B1J4du+9kC4uP3R+DUMZGWcJzlSq
dl+qjrsYj/FOlKjTpyCv06lyQpU38VLkQ4TeoATZm2qvLp3Rp7U=
=Aj1N
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--


From nobody Wed Jul 11 10:27:32 2018
Return-Path: <bemasc@google.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0574A130DF2 for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 10:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level: 
X-Spam-Status: No, score=-17.51 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, T_DKIMWL_WL_MED=-0.01, 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 Eu9dOd-o5Ble for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 10:27:28 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 E9540130E40 for <dispatch@ietf.org>; Wed, 11 Jul 2018 10:27:27 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id l14-v6so14718491iob.7 for <dispatch@ietf.org>; Wed, 11 Jul 2018 10:27:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=CYWH6SRJY9EF/RWqwBWgXmvQAHnxt7DUjyqGFfqvDuw=; b=r3DQe8IB9pvQJcTLqGPRIc9aZBWNok5mOal/A5CGI5Gc9qnVju2UdOzzK+lk4rMMRB vv+aEU7gy+Pq+oJ2AsFYM58OlGTBYiw67TiGcW1UEuC02dIgP/RtpnFJXRaamwyt6jhW ymZoQOQzrymSQeL+ceoDmRhrZokaH6BOTR87NCR6duXkLt5GjE6FBSjy3iSPs8L1RvKD KkZncXwrGyofWovz+3IHRvQtGBqAoSqmi/0kSzIFWZIjVNQ0MvG6VsuSxf5VVgjKD2t9 2MgKnP8M9OV4BfMWX2bNd9h2eyl5Kw8c7pjoOdLCUJF/8seNH4nzVEd6abKomay0ze3l bi0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CYWH6SRJY9EF/RWqwBWgXmvQAHnxt7DUjyqGFfqvDuw=; b=HOTzuEIqzxsl1RKpLRDvcK/lNmKPoChUT9ZnEj0K3xTaurNeDTG8CHquQYuVWc93i1 2QRON1EoZm/KkiGJX3l8zS7WLtp3PdWLuaTO4xAK70PeUJfjCGRqCRtpcuTVBq3vXY44 gpGf1M1zlGPUqQ1hK7QzpkuofDLLSmxw0kpq7H7k69/+NONnXtYxUxKh0cW0BwBVVEI7 x7MthORvP+6ZLKbXLlAl8+6Vpcv4JUkLGdhBs4VpxZZMcevW/L2xS7UyGlwR74slJy9T WcQmoGwaLtBKK+/VjhNDD9X2zhAXBrJ9T7f54D+JNVM69leQM9Tl93/VkPiuD8MozYYF YhFg==
X-Gm-Message-State: AOUpUlEWgQWsn9CbSCbDWr6LhQee+G2PwK1jkYE4a7mOihgAYZYiBSJ8 ZIFRDCXOu7djlb1mN5pTmt6Otu5ZoNNxXvvdxab+iMAyV5s=
X-Google-Smtp-Source: AAOMgpfjtQYWs34EKYB72o+Rz8D4zDkJIWMHsKPDgw0PzjIkmBx4nrIyTXHLgPCBefEKLm41lxwhJKZb6zx1q1yDqLQ=
X-Received: by 2002:a6b:1fc8:: with SMTP id f191-v6mr195767iof.362.1531330046767;  Wed, 11 Jul 2018 10:27:26 -0700 (PDT)
MIME-Version: 1.0
From: Ben Schwartz <bemasc@google.com>
Date: Wed, 11 Jul 2018 13:27:15 -0400
Message-ID: <CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com>
To: Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="0000000000008117800570bc8fdc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/KWKezHLz0hSVvSXOT_fDfCM7bnM>
Subject: [dispatch] HELIUM at Dispatch
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 17:27:30 -0000

--0000000000008117800570bc8fdc
Content-Type: multipart/alternative; boundary="000000000000795ec80570bc8fa9"

--000000000000795ec80570bc8fa9
Content-Type: text/plain; charset="UTF-8"

Hi Dispatch,

One of the drafts on the Dispatch agenda for next week is HELIUM:
https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00.

There has been some discussion on the HTTP list (e.g.
https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html),
but the most detailed presentation on this proposal will be here in
Dispatch.

HELIUM has relevance to privacy protection, P2P through NAT, VPNs, advanced
IP features, QUIC, and congestion control, among other topics.  I hope
anyone who's interested will read the draft (or at least the introduction)
before our session on Monday.

Thanks,
Ben

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

<div dir=3D"ltr">Hi Dispatch,<br><div><br></div><div>One of the drafts on t=
he Dispatch agenda for next week is HELIUM:=C2=A0<a href=3D"https://tools.i=
etf.org/html/draft-schwartz-httpbis-helium-00">https://tools.ietf.org/html/=
draft-schwartz-httpbis-helium-00</a>.</div><div><br></div><div>There has be=
en some discussion on the HTTP list (e.g.=C2=A0<a href=3D"https://lists.w3.=
org/Archives/Public/ietf-http-wg/2018JulSep/0041.html">https://lists.w3.org=
/Archives/Public/ietf-http-wg/2018JulSep/0041.html</a>), but the most detai=
led presentation on this proposal will be here in Dispatch.</div><div><br><=
/div><div>HELIUM has relevance to privacy protection, P2P through NAT, VPNs=
, advanced IP features, QUIC, and congestion control, among other topics.=
=C2=A0 I hope anyone who&#39;s interested will read the draft (or at least =
the introduction) before our session on Monday.</div><div><br></div><div>Th=
anks,</div><div>Ben</div></div>

--000000000000795ec80570bc8fa9--

--0000000000008117800570bc8fdc
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMHPEBklWZfCvIVU8oMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE4MDUxNzA4MjIwNVoXDTE4MTEx
MzA4MjIwNVowIjEgMB4GCSqGSIb3DQEJAQwRYmVtYXNjQGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDQRB850FBZJnK1k18RTKWAcnV8xzvvd+Eatm0/DGMYHYhqGriJ
WRekNb6Te9Y/zCccceH4x4OjBzjaup2aBU/Lbeaj9I5AuCUQnn+xM+t6M+huTXv9pujltTAbaR/b
IfiE9ilbhz6BrM09gtcDgGccpiyDw5np6PR8nn5dkbJ+1Hes0d9i5k0BkCQp1OQYDux0aAQKV0uq
G43K/QIXth7qejm2JM1Gpzc2AKE9UJDlTHWVW7nmjdVf0JdzLbkZWHlQqpMU4cbaA/QBtWCddLOR
YOVVmfL2G0kqi3I0DPR7IGxLHCRlfrVr9b1kRA+Wt5SkoiBsoqLZ7FGFNokuAwrfAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRFiZW1hc2NAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFPUT4TOHt/oKM2x0XyaENesy/GcRMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCuK5XDeLIidLOebj/u
0+kt/1GjtDlRXEZNy6kLW2VPvzIQzpOFHz6Go02crZL1MkyvR1uWaZnGt6zRMIbNeEx0DKUMxitQ
QsVU99JBOXhtipJ0CAR94SC9vPG6ecuVPzRM8rGyVCHhjwjQnuJ9pTsYTUYUDM+DCeCJRtDOrzGd
RtcVP6W7prUn2qvDqC45qZEIEWdrLhDjdjPuWvgl0LkCKwxl9JRaUZePN8dDRRSA7X8sFr0FF8pn
w83HwJizSB2EeQeSu/lvcvIBZzs0SwX+09qAvZYfiI+m2yuQfHSleDw0BBMROMB9S2yBFkP+2E3y
BWurROrwi9IwxXqcQVLOMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMHPEBklWZ
fCvIVU8oMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCAD2oyibYQUXNGP5lac+PIQ
PmRShBwWMVn5kFbp88OJ8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xODA3MTExNzI3MjdaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAsLgxNYC7xxUEJbr5UBp69vSLezeP3QJ6VcReGOt+
Y7PUDtDwI83UszLWrIr56O6j4w2ZgG461VHNY2pcfUV7KQ2SIehvsB1IZeApcPtZPtAnXneC34O2
vfjkZzIBKPfiZhpIxWGrCgXkQ9roiZH6J6IjB5AC+rklEV0cwg0GgvhXhCgsaTr5dmzrEUhVowvu
Psctsyb96dbauxZeHzkcWK4BHL2wqNmG2jd7xhH2GXYMeynfQokqGUasJAb/k1kUcsGIMUrCMPF4
82W8wSvm9TiRMCidhYC+rTtfxjkXJXqNd6pUOEe3hO0TXkjH6sHiR7Xb8fk7TBex/xDJkJjWpg==
--0000000000008117800570bc8fdc--


From nobody Wed Jul 11 12:15:54 2018
Return-Path: <adam@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70564130EA0 for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 12:15:51 -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, HTML_MESSAGE=0.001, 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 R4WyNf9Sgb21 for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 12:15:48 -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 08EE0130EFF for <dispatch@ietf.org>; Wed, 11 Jul 2018 12:15:48 -0700 (PDT)
Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6BJFivl068325 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 11 Jul 2018 14:15:46 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, Dispatch WG <dispatch@ietf.org>
References: <CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <3dd27329-e0e8-5e85-c1f9-f12e584a980b@nostrum.com>
Date: Wed, 11 Jul 2018 14:15:44 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.0
MIME-Version: 1.0
In-Reply-To: <CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------BF1D9D0C73AB38F6794AD20F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/K3ZozHc5aITn1gdQ_tEERSsw1dE>
Subject: Re: [dispatch] HELIUM at Dispatch
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 19:15:52 -0000

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

[as an individual]

This is small, but it's going to be a recurring papercut if this works 
gains traction: I'm having a really hard time reading a document talking 
about "HIP" that is in no way related to 
https://datatracker.ietf.org/wg/hip/about/ -- please consider renaming 
this protocol.

It would probably also be worthwhile explaining how the features of 
HELIUM are significantly different than RFC 1928. I see raw IP tunneling 
and WebSocket support as differentiators, but it's not clear that this 
requires restarting the protocol from ground zero rather than extending 
an existing extensible protocol.

Lest my suggestion above be perceived as tongue-in-cheek, I'm dead 
serious: RFC 1928 is used extensively by the Tor network, and there is a 
fair body of deployed code in modern use, at least in that context.

/a

On 7/11/18 12:27 PM, Ben Schwartz wrote:
> Hi Dispatch,
>
> One of the drafts on the Dispatch agenda for next week is HELIUM: 
> https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00.
>
> There has been some discussion on the HTTP list (e.g. 
> https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html), 
> but the most detailed presentation on this proposal will be here in 
> Dispatch.
>
> HELIUM has relevance to privacy protection, P2P through NAT, VPNs, 
> advanced IP features, QUIC, and congestion control, among other 
> topics.  I hope anyone who's interested will read the draft (or at 
> least the introduction) before our session on Monday.
>
> Thanks,
> Ben
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch



--------------BF1D9D0C73AB38F6794AD20F
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">[as an individual]<br>
      <br>
      This is small, but it's going to be a recurring papercut if this
      works gains traction: I'm having a really hard time reading a
      document talking about "HIP" that is in no way related to
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/wg/hip/about/">https://datatracker.ietf.org/wg/hip/about/</a> -- please consider
      renaming this protocol.<br>
      <br>
      It would probably also be worthwhile explaining how the features
      of HELIUM are significantly different than RFC 1928. I see raw IP
      tunneling and WebSocket support as differentiators, but it's not
      clear that this requires restarting the protocol from ground zero
      rather than extending an existing extensible protocol.<br>
      <br>
      Lest my suggestion above be perceived as tongue-in-cheek, I'm dead
      serious: RFC 1928 is used extensively by the Tor network, and
      there is a fair body of deployed code in modern use, at least in
      that context.<br>
      <br>
      /a<br>
      <br>
      On 7/11/18 12:27 PM, Ben Schwartz wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">Hi Dispatch,<br>
        <div><br>
        </div>
        <div>One of the drafts on the Dispatch agenda for next week is
          HELIUM: <a
            href="https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00"
            moz-do-not-send="true">https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00</a>.</div>
        <div><br>
        </div>
        <div>There has been some discussion on the HTTP list (e.g. <a
href="https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html"
            moz-do-not-send="true">https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html</a>),
          but the most detailed presentation on this proposal will be
          here in Dispatch.</div>
        <div><br>
        </div>
        <div>HELIUM has relevance to privacy protection, P2P through
          NAT, VPNs, advanced IP features, QUIC, and congestion control,
          among other topics.  I hope anyone who's interested will read
          the draft (or at least the introduction) before our session on
          Monday.</div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div>Ben</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
dispatch mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dispatch@ietf.org">dispatch@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dispatch">https://www.ietf.org/mailman/listinfo/dispatch</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------BF1D9D0C73AB38F6794AD20F--


From nobody Wed Jul 11 13:02:54 2018
Return-Path: <bemasc@google.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567881277BB for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 13:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level: 
X-Spam-Status: No, score=-17.51 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, T_DKIMWL_WL_MED=-0.01, 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 R5HjPFutDOPP for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 13:02:50 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 22821124C04 for <dispatch@ietf.org>; Wed, 11 Jul 2018 13:02:50 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id k3-v6so25459018iog.3 for <dispatch@ietf.org>; Wed, 11 Jul 2018 13:02:50 -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=jeBDxM+qHN7Jvy3/biCXkbQ3C+E5xk09ShafYVf6LQE=; b=RNlKbJsEKGihqZkQ1iPA7UXMATtuMDqdxGpZg8UzQmNytQRP6iiXXZVe4uwsTx+wL+ Oj2qM7p79Ms78LeC5CQoVmcbX+jM4ltTLU4CLfjLmEkonhD9MTRV0cB9Nz110U2a+uub 253NyXNB8O8QnGQKwjPZwqh0M1ehb7gBzfkvH0f4VfHahc9TfQREmB4FCly3fWVNwUSJ VTaDFbZzJH/PWY8CwMriS/LkXwqOSHhDt5CXDenc0kv9gHoV/Sy2TDoOJPUd4Ju4/eHE gKBOnORxhR87YXa5xxCD34rrjMU4C8e2+E0Jh8leCLSnfGasR07y587YTn45e4q8ftfK Vuuw==
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=jeBDxM+qHN7Jvy3/biCXkbQ3C+E5xk09ShafYVf6LQE=; b=csdRHHfLSHj8+PeYvdIWuL8IR4zWQ0f0d4z7cNT3DauImclZ1dNrQE9LnYwj+m1B+j 7TLChRj6wDdBJ1ZT8mA2lBDsBxHa7vjZqR8uPwfl1nF1zT3zz8FhrVTz4d9GS50qt/Ui 51qS/jQ6U6ebOsLBdyCo1/7znZdNx6K42aJcRilW4LZbC4A0T4sHsg39fE6+KgoUsq8f U6pIYg4h2QWwKBHXygl0DGb/kdr99rewg/utSQyB+s8UEvGYG1TmdJ2xTRkoxG2h+nzm 14uCl7XcAKVfDQNO6F34WlJxvvQ4pP0qtCvOwYs3ia2kEdyhf9JpGK3wMcCEsHRpnCdm DsXw==
X-Gm-Message-State: AOUpUlGEtZmN7m52ylJFHZ35qTGf4xiglXMJiuMJ3qj/RNCzOjuLN341 NTOrXw6vcB2ylPn4nhKzJC7w58pghrtN9BVeCCpc/lFD
X-Google-Smtp-Source: AAOMgpeSEW4V7bVEo1rTY75JcJCNIS+XUHogwoQ44VhHu1DlcImS0FKvS8E7qMBiQTXRA8u0X5E3xdhfcxNn3QuXMdg=
X-Received: by 2002:a6b:cd83:: with SMTP id d125-v6mr530176iog.370.1531339368903;  Wed, 11 Jul 2018 13:02:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com> <3dd27329-e0e8-5e85-c1f9-f12e584a980b@nostrum.com>
In-Reply-To: <3dd27329-e0e8-5e85-c1f9-f12e584a980b@nostrum.com>
From: Ben Schwartz <bemasc@google.com>
Date: Wed, 11 Jul 2018 16:02:30 -0400
Message-ID: <CAHbrMsAXFBq2Qi+3Ar4gyzAsqAKbdAovwCf3q9PesPjM3zwSnQ@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="00000000000028b4c70570bebb2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Lz4dIYY_RM43o5H9MZGMWChgdE8>
Subject: Re: [dispatch] HELIUM at Dispatch
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 20:02:53 -0000

--00000000000028b4c70570bebb2b
Content-Type: multipart/alternative; boundary="0000000000001d92730570bebbcc"

--0000000000001d92730570bebbcc
Content-Type: text/plain; charset="UTF-8"

On Wed, Jul 11, 2018 at 3:15 PM Adam Roach <adam@nostrum.com> wrote:

> [as an individual]
>
> This is small, but it's going to be a recurring papercut if this works
> gains traction: I'm having a really hard time reading a document talking
> about "HIP" that is in no way related to
> https://datatracker.ietf.org/wg/hip/about/ -- please consider renaming
> this protocol.
>

OK, will do.

It would probably also be worthwhile explaining how the features of HELIUM
> are significantly different than RFC 1928. I see raw IP tunneling and
> WebSocket support as differentiators, but it's not clear that this requires
> restarting the protocol from ground zero rather than extending an existing
> extensible protocol.
>
> Lest my suggestion above be perceived as tongue-in-cheek, I'm dead
> serious: RFC 1928 is used extensively by the Tor network, and there is a
> fair body of deployed code in modern use, at least in that context.
>

I've written a lot of code for RFC 1928 (SOCKS 5) myself, including the
rarely used SOCKS5-UDP support, so I fully appreciate this.  Alternatively
TURN also supports UDP, and with RFC 6062 can proxy TCP too.  I do feel
that a clean-slate design is worthwhile in this case, but you're right that
I haven't really tried to argue that in the draft.  I'll think about the
right way to make that claim.


>
> /a
>
> On 7/11/18 12:27 PM, Ben Schwartz wrote:
>
> Hi Dispatch,
>
> One of the drafts on the Dispatch agenda for next week is HELIUM:
> https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00.
>
> There has been some discussion on the HTTP list (e.g.
> https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html),
> but the most detailed presentation on this proposal will be here in
> Dispatch.
>
> HELIUM has relevance to privacy protection, P2P through NAT, VPNs,
> advanced IP features, QUIC, and congestion control, among other topics.  I
> hope anyone who's interested will read the draft (or at least the
> introduction) before our session on Monday.
>
> Thanks,
> Ben
>
>
> _______________________________________________
> dispatch mailing listdispatch@ietf.orghttps://www.ietf.org/mailman/listinfo/dispatch
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Jul 11=
, 2018 at 3:15 PM Adam Roach &lt;<a href=3D"mailto:adam@nostrum.com">adam@n=
ostrum.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">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"m_4232121541609566916moz-cite-prefix">[as an individual]<=
br>
      <br>
      This is small, but it&#39;s going to be a recurring papercut if this
      works gains traction: I&#39;m having a really hard time reading a
      document talking about &quot;HIP&quot; that is in no way related to
      <a class=3D"m_4232121541609566916moz-txt-link-freetext" href=3D"https=
://datatracker.ietf.org/wg/hip/about/" target=3D"_blank">https://datatracke=
r.ietf.org/wg/hip/about/</a> -- please consider
      renaming this protocol.<br></div></div></blockquote><div><br></div><d=
iv>OK, will do.</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div tex=
t=3D"#000000" bgcolor=3D"#FFFFFF"><div class=3D"m_4232121541609566916moz-ci=
te-prefix">
      It would probably also be worthwhile explaining how the features
      of HELIUM are significantly different than RFC 1928. I see raw IP
      tunneling and WebSocket support as differentiators, but it&#39;s not
      clear that this requires restarting the protocol from ground zero
      rather than extending an existing extensible protocol.<br>
      <br>
      Lest my suggestion above be perceived as tongue-in-cheek, I&#39;m dea=
d
      serious: RFC 1928 is used extensively by the Tor network, and
      there is a fair body of deployed code in modern use, at least in
      that context.<br></div></div></blockquote><div><br></div><div>I&#39;v=
e written a lot of code for RFC 1928 (SOCKS 5) myself, including the rarely=
 used SOCKS5-UDP support, so I fully appreciate this.=C2=A0 Alternatively T=
URN also supports UDP, and with RFC 6062 can proxy TCP too.=C2=A0 I do feel=
 that a clean-slate design is worthwhile in this case, but you&#39;re right=
 that I haven&#39;t really tried to argue that in the draft.=C2=A0 I&#39;ll=
 think about the right way to make that claim.</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><div cla=
ss=3D"m_4232121541609566916moz-cite-prefix">
      <br>
      /a<br>
      <br>
      On 7/11/18 12:27 PM, Ben Schwartz wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hi Dispatch,<br>
        <div><br>
        </div>
        <div>One of the drafts on the Dispatch agenda for next week is
          HELIUM:=C2=A0<a href=3D"https://tools.ietf.org/html/draft-schwart=
z-httpbis-helium-00" target=3D"_blank">https://tools.ietf.org/html/draft-sc=
hwartz-httpbis-helium-00</a>.</div>
        <div><br>
        </div>
        <div>There has been some discussion on the HTTP list (e.g.=C2=A0<a =
href=3D"https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.h=
tml" target=3D"_blank">https://lists.w3.org/Archives/Public/ietf-http-wg/20=
18JulSep/0041.html</a>),
          but the most detailed presentation on this proposal will be
          here in Dispatch.</div>
        <div><br>
        </div>
        <div>HELIUM has relevance to privacy protection, P2P through
          NAT, VPNs, advanced IP features, QUIC, and congestion control,
          among other topics.=C2=A0 I hope anyone who&#39;s interested will=
 read
          the draft (or at least the introduction) before our session on
          Monday.</div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div>Ben</div>
      </div>
      <br>
      <fieldset class=3D"m_4232121541609566916mimeAttachmentHeader"></field=
set>
      <br>
      <pre>_______________________________________________
dispatch mailing list
<a class=3D"m_4232121541609566916moz-txt-link-abbreviated" href=3D"mailto:d=
ispatch@ietf.org" target=3D"_blank">dispatch@ietf.org</a>
<a class=3D"m_4232121541609566916moz-txt-link-freetext" href=3D"https://www=
.ietf.org/mailman/listinfo/dispatch" target=3D"_blank">https://www.ietf.org=
/mailman/listinfo/dispatch</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </div>

</blockquote></div></div>

--0000000000001d92730570bebbcc--

--00000000000028b4c70570bebb2b
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMHPEBklWZfCvIVU8oMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE4MDUxNzA4MjIwNVoXDTE4MTEx
MzA4MjIwNVowIjEgMB4GCSqGSIb3DQEJAQwRYmVtYXNjQGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDQRB850FBZJnK1k18RTKWAcnV8xzvvd+Eatm0/DGMYHYhqGriJ
WRekNb6Te9Y/zCccceH4x4OjBzjaup2aBU/Lbeaj9I5AuCUQnn+xM+t6M+huTXv9pujltTAbaR/b
IfiE9ilbhz6BrM09gtcDgGccpiyDw5np6PR8nn5dkbJ+1Hes0d9i5k0BkCQp1OQYDux0aAQKV0uq
G43K/QIXth7qejm2JM1Gpzc2AKE9UJDlTHWVW7nmjdVf0JdzLbkZWHlQqpMU4cbaA/QBtWCddLOR
YOVVmfL2G0kqi3I0DPR7IGxLHCRlfrVr9b1kRA+Wt5SkoiBsoqLZ7FGFNokuAwrfAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRFiZW1hc2NAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFPUT4TOHt/oKM2x0XyaENesy/GcRMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCuK5XDeLIidLOebj/u
0+kt/1GjtDlRXEZNy6kLW2VPvzIQzpOFHz6Go02crZL1MkyvR1uWaZnGt6zRMIbNeEx0DKUMxitQ
QsVU99JBOXhtipJ0CAR94SC9vPG6ecuVPzRM8rGyVCHhjwjQnuJ9pTsYTUYUDM+DCeCJRtDOrzGd
RtcVP6W7prUn2qvDqC45qZEIEWdrLhDjdjPuWvgl0LkCKwxl9JRaUZePN8dDRRSA7X8sFr0FF8pn
w83HwJizSB2EeQeSu/lvcvIBZzs0SwX+09qAvZYfiI+m2yuQfHSleDw0BBMROMB9S2yBFkP+2E3y
BWurROrwi9IwxXqcQVLOMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMHPEBklWZ
fCvIVU8oMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCDxpIomd2R0evyMCOGtU7KB
4qUgPAA/cHi0m6e5zutkKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xODA3MTEyMDAyNDlaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEABzwz0VazMg21knxZ25JXSMJfc4MXjrHQmbQvoFyx
8ggQD0T3IyGq9ipxTjng8RVIne/QZaOpsZ3wfPNIJT9n2aqDEpaBhOWkpZfxHBzakvk3HjEcq7Pg
JVhXISpNdnTiIAdw1i2QnL3uD22OwCZuLpmDZ7s+L1WkBkBtbd9yQrQ0jCstPOscGrHOzNLlZByj
C1Px/agypmtRMYvxd8yUo8Vz2FOZisCzyrW32cbire9Sm0NWg2aRX5Nrn8eAXeYlexfFuC9FDewX
yfzAL3cOb1jpuyXsXwmtFQgVBzCwipcMgyouR38LTuc54Yk5pWunZ6MkS6++YR8PbUif77yBXw==
--00000000000028b4c70570bebb2b--


From nobody Wed Jul 11 14:47:50 2018
Return-Path: <bemasc@google.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C90130E73 for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 14:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level: 
X-Spam-Status: No, score=-17.51 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, T_DKIMWL_WL_MED=-0.01, 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 AzLsMQ5GokTc for <dispatch@ietfa.amsl.com>; Wed, 11 Jul 2018 14:47:46 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::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 100F6130DDD for <dispatch@ietf.org>; Wed, 11 Jul 2018 14:47:46 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id j185-v6so4544488ite.1 for <dispatch@ietf.org>; Wed, 11 Jul 2018 14:47:46 -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=VSEzllmY5bmGU8zEsqLGWFo5fQH7tHl4SPY5nNFqH1E=; b=ZotkyRDiLVjCXoqj4BJi8zTObee4tSuXCqXrPS9c2aduFwkXmq1ranflwME7aW3ncO yyjV723OkqE7bpAxE0lVjnHN+K+FbSDcqJd/CLf2a68dspahpLQ01ETTPOXEmv//q//t Gxf4OWpScVZtZnBI1OEv+62+Ui9rUnLSg8E0y+p6kRDRNHADWsHj3LSwY59Ig3wRBl44 sOIOJITRD85tCEQ0svLVOS2twZoKVytu3RfGB6WHAKCnC7I390m8Gj20yN6JazT8GqM8 Ibi0EvKstQ5S7jhPCQ9Wwg8wWyC+9/zuRpLAqu+JvxEpEgQw2jlkp2JNEa28KHZ0nyry 3G7w==
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=VSEzllmY5bmGU8zEsqLGWFo5fQH7tHl4SPY5nNFqH1E=; b=JwebIa3ZlpDjslcqOU8qAtMT2g7ANzfVuoaScXDurUEhecGzm+EqId4ufix9HyvfWX QSE9lRkcvRq+VmVYL5VZc1rXfiDN0SJTwsmnV0fjRuZ+PRCsMJRULb0ww3ZJiG+0SD53 nwW3nvUNWyZHk3uuM58zklQCTaZYaR4XwNIGCoum2cw51nzOMoMiPFFUFu50qYPNivcI 3DSjF/jlJ0L6rmcSkGzWfhyPxPXmLrMaWEmnVaDmUIokwRe91kyUkVbt2/cmN2Zn/1s7 dM8eXmxVaDlkOUCR5UaRBqrViHqOPjcd7q5ZtitV3Le0nQhhept9cweSJsPZZ7WDnMOr C1FA==
X-Gm-Message-State: AOUpUlEkA+Cbmvq03mAr2wjXuFyLRFVwUowI/DesPteWMuAYFqimKEh6 hbi6pwtsbCW2QM72mNCt1CtL5B0R9Ks3ohMlnFqLWxG2Rig=
X-Google-Smtp-Source: AAOMgpeBS6ZJwcidTRB+IdHEgYb8WL/suuBvB+PC1wCDd5vRv11ymdHeT+lwCDde9yJOtsJyXKcsifpm2ErQ8pJX+ec=
X-Received: by 2002:a24:ce81:: with SMTP id v123-v6mr146769itg.119.1531345664784;  Wed, 11 Jul 2018 14:47:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAHbrMsCpBV+GWcOeXEZ9K9ZrdajhdyGNhpjoGOOjadsC5yx7rA@mail.gmail.com> <3dd27329-e0e8-5e85-c1f9-f12e584a980b@nostrum.com> <CAHbrMsAXFBq2Qi+3Ar4gyzAsqAKbdAovwCf3q9PesPjM3zwSnQ@mail.gmail.com>
In-Reply-To: <CAHbrMsAXFBq2Qi+3Ar4gyzAsqAKbdAovwCf3q9PesPjM3zwSnQ@mail.gmail.com>
From: Ben Schwartz <bemasc@google.com>
Date: Wed, 11 Jul 2018 17:47:33 -0400
Message-ID: <CAHbrMsBtnuj4jK4=_7LGHKCy=JvL6fwsgoANVhOC5o0RzZ8wJw@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="0000000000006ae43d0570c03266"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/9ZdS82QloYD1iIJ7GWZlYtSnQXk>
Subject: Re: [dispatch] HELIUM at Dispatch
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 21:47:49 -0000

--0000000000006ae43d0570c03266
Content-Type: multipart/alternative; boundary="0000000000006136fb0570c032d8"

--0000000000006136fb0570c032d8
Content-Type: text/plain; charset="UTF-8"

On Wed, Jul 11, 2018 at 4:02 PM Ben Schwartz <bemasc@google.com> wrote:

> On Wed, Jul 11, 2018 at 3:15 PM Adam Roach <adam@nostrum.com> wrote:
>
>> [as an individual]
>>
>> This is small, but it's going to be a recurring papercut if this works
>> gains traction: I'm having a really hard time reading a document talking
>> about "HIP" that is in no way related to
>> https://datatracker.ietf.org/wg/hip/about/ -- please consider renaming
>> this protocol.
>>
>
> OK, will do.
>
> It would probably also be worthwhile explaining how the features of HELIUM
>> are significantly different than RFC 1928. I see raw IP tunneling and
>> WebSocket support as differentiators, but it's not clear that this requires
>> restarting the protocol from ground zero rather than extending an existing
>> extensible protocol.
>>
>> Lest my suggestion above be perceived as tongue-in-cheek, I'm dead
>> serious: RFC 1928 is used extensively by the Tor network, and there is a
>> fair body of deployed code in modern use, at least in that context.
>>
>
> I've written a lot of code for RFC 1928 (SOCKS 5) myself, including the
> rarely used SOCKS5-UDP support, so I fully appreciate this.  Alternatively
> TURN also supports UDP, and with RFC 6062 can proxy TCP too.  I do feel
> that a clean-slate design is worthwhile in this case, but you're right that
> I haven't really tried to argue that in the draft.  I'll think about the
> right way to make that claim.
>

For completeness, I also want to mention the current SOCKS 6 proposal:
https://tools.ietf.org/html/draft-olteanu-intarea-socks-6


>
>
>>
>> /a
>>
>> On 7/11/18 12:27 PM, Ben Schwartz wrote:
>>
>> Hi Dispatch,
>>
>> One of the drafts on the Dispatch agenda for next week is HELIUM:
>> https://tools.ietf.org/html/draft-schwartz-httpbis-helium-00.
>>
>> There has been some discussion on the HTTP list (e.g.
>> https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.html),
>> but the most detailed presentation on this proposal will be here in
>> Dispatch.
>>
>> HELIUM has relevance to privacy protection, P2P through NAT, VPNs,
>> advanced IP features, QUIC, and congestion control, among other topics.  I
>> hope anyone who's interested will read the draft (or at least the
>> introduction) before our session on Monday.
>>
>> Thanks,
>> Ben
>>
>>
>> _______________________________________________
>> dispatch mailing listdispatch@ietf.orghttps://www.ietf.org/mailman/listinfo/dispatch
>>
>>
>>

--0000000000006136fb0570c032d8
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 Wed=
, Jul 11, 2018 at 4:02 PM Ben Schwartz &lt;<a href=3D"mailto:bemasc@google.=
com">bemasc@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Wed, Jul 11, 2018 at 3:15 PM Adam Roach &lt;<a href=3D"mailto:a=
dam@nostrum.com" target=3D"_blank">adam@nostrum.com</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);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <div class=3D"gmail-m_-2236565192039928393m_4232121541609566916moz-cite=
-prefix">[as an individual]<br>
      <br>
      This is small, but it&#39;s going to be a recurring papercut if this
      works gains traction: I&#39;m having a really hard time reading a
      document talking about &quot;HIP&quot; that is in no way related to
      <a class=3D"gmail-m_-2236565192039928393m_4232121541609566916moz-txt-=
link-freetext" href=3D"https://datatracker.ietf.org/wg/hip/about/" target=
=3D"_blank">https://datatracker.ietf.org/wg/hip/about/</a> -- please consid=
er
      renaming this protocol.<br></div></div></blockquote><div><br></div><d=
iv>OK, will do.</div><div><br></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 bgcolor=3D"#FFFFFF"><div class=3D"gmail-m_-2236565192039928=
393m_4232121541609566916moz-cite-prefix">
      It would probably also be worthwhile explaining how the features
      of HELIUM are significantly different than RFC 1928. I see raw IP
      tunneling and WebSocket support as differentiators, but it&#39;s not
      clear that this requires restarting the protocol from ground zero
      rather than extending an existing extensible protocol.<br>
      <br>
      Lest my suggestion above be perceived as tongue-in-cheek, I&#39;m dea=
d
      serious: RFC 1928 is used extensively by the Tor network, and
      there is a fair body of deployed code in modern use, at least in
      that context.<br></div></div></blockquote><div><br></div><div>I&#39;v=
e written a lot of code for RFC 1928 (SOCKS 5) myself, including the rarely=
 used SOCKS5-UDP support, so I fully appreciate this.=C2=A0 Alternatively T=
URN also supports UDP, and with RFC 6062 can proxy TCP too.=C2=A0 I do feel=
 that a clean-slate design is worthwhile in this case, but you&#39;re right=
 that I haven&#39;t really tried to argue that in the draft.=C2=A0 I&#39;ll=
 think about the right way to make that claim.</div></div></div></blockquot=
e><div><br></div><div>For completeness, I also want to mention the current =
SOCKS 6 proposal:=C2=A0<a href=3D"https://tools.ietf.org/html/draft-olteanu=
-intarea-socks-6">https://tools.ietf.org/html/draft-olteanu-intarea-socks-6=
</a></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n: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>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><div class=
=3D"gmail-m_-2236565192039928393m_4232121541609566916moz-cite-prefix">
      <br>
      /a<br>
      <br>
      On 7/11/18 12:27 PM, Ben Schwartz wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hi Dispatch,<br>
        <div><br>
        </div>
        <div>One of the drafts on the Dispatch agenda for next week is
          HELIUM:=C2=A0<a href=3D"https://tools.ietf.org/html/draft-schwart=
z-httpbis-helium-00" target=3D"_blank">https://tools.ietf.org/html/draft-sc=
hwartz-httpbis-helium-00</a>.</div>
        <div><br>
        </div>
        <div>There has been some discussion on the HTTP list (e.g.=C2=A0<a =
href=3D"https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0041.h=
tml" target=3D"_blank">https://lists.w3.org/Archives/Public/ietf-http-wg/20=
18JulSep/0041.html</a>),
          but the most detailed presentation on this proposal will be
          here in Dispatch.</div>
        <div><br>
        </div>
        <div>HELIUM has relevance to privacy protection, P2P through
          NAT, VPNs, advanced IP features, QUIC, and congestion control,
          among other topics.=C2=A0 I hope anyone who&#39;s interested will=
 read
          the draft (or at least the introduction) before our session on
          Monday.</div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div>Ben</div>
      </div>
      <br>
      <fieldset class=3D"gmail-m_-2236565192039928393m_4232121541609566916m=
imeAttachmentHeader"></fieldset>
      <br>
      <pre>_______________________________________________
dispatch mailing list
<a class=3D"gmail-m_-2236565192039928393m_4232121541609566916moz-txt-link-a=
bbreviated" href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ie=
tf.org</a>
<a class=3D"gmail-m_-2236565192039928393m_4232121541609566916moz-txt-link-f=
reetext" href=3D"https://www.ietf.org/mailman/listinfo/dispatch" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/dispatch</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </div>

</blockquote></div></div>
</blockquote></div></div>

--0000000000006136fb0570c032d8--

--0000000000006ae43d0570c03266
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMHPEBklWZfCvIVU8oMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE4MDUxNzA4MjIwNVoXDTE4MTEx
MzA4MjIwNVowIjEgMB4GCSqGSIb3DQEJAQwRYmVtYXNjQGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDQRB850FBZJnK1k18RTKWAcnV8xzvvd+Eatm0/DGMYHYhqGriJ
WRekNb6Te9Y/zCccceH4x4OjBzjaup2aBU/Lbeaj9I5AuCUQnn+xM+t6M+huTXv9pujltTAbaR/b
IfiE9ilbhz6BrM09gtcDgGccpiyDw5np6PR8nn5dkbJ+1Hes0d9i5k0BkCQp1OQYDux0aAQKV0uq
G43K/QIXth7qejm2JM1Gpzc2AKE9UJDlTHWVW7nmjdVf0JdzLbkZWHlQqpMU4cbaA/QBtWCddLOR
YOVVmfL2G0kqi3I0DPR7IGxLHCRlfrVr9b1kRA+Wt5SkoiBsoqLZ7FGFNokuAwrfAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRFiZW1hc2NAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFPUT4TOHt/oKM2x0XyaENesy/GcRMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCuK5XDeLIidLOebj/u
0+kt/1GjtDlRXEZNy6kLW2VPvzIQzpOFHz6Go02crZL1MkyvR1uWaZnGt6zRMIbNeEx0DKUMxitQ
QsVU99JBOXhtipJ0CAR94SC9vPG6ecuVPzRM8rGyVCHhjwjQnuJ9pTsYTUYUDM+DCeCJRtDOrzGd
RtcVP6W7prUn2qvDqC45qZEIEWdrLhDjdjPuWvgl0LkCKwxl9JRaUZePN8dDRRSA7X8sFr0FF8pn
w83HwJizSB2EeQeSu/lvcvIBZzs0SwX+09qAvZYfiI+m2yuQfHSleDw0BBMROMB9S2yBFkP+2E3y
BWurROrwi9IwxXqcQVLOMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMHPEBklWZ
fCvIVU8oMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCDlB/bomaCSYXBF8BTTeTXR
2X3qB4EoM/Oh1mZWdDX/1DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xODA3MTEyMTQ3NDVaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAm7IXPGc0mvtdXQIxJt4HJnAoNo9i9LUXZfFn2KMk
I3n72NBxEjipOHGbLl9VPuhUqY+M94aiQ6v/+4ASHEav7F56vxdWUjL+hPFnNkGOgAeD7oKIfb/5
MRDJxtAFPu3g/yVrcrxGjXDvGUMmrBaeZ4j5Lo3DjN0O8wKZ+2j2ZXFJRsGdUDcenXXuUNpcMpmz
O9cu1Im1H38gw/XWe4ZY2J4bysyYuDbMlI4sPznhW06iPWymcpBbW/XBjfYFxkVRYvzUdxMVcsax
tdGOOil46vL7a8H6z0E6sXBRFQ1SUq1lt3CODByPw7x5O/Xx18hItrr58ae75huLpTmaiLOGuQ==
--0000000000006ae43d0570c03266--


From nobody Thu Jul 12 07:36:07 2018
Return-Path: <bradley.meck@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B665913112C; Thu, 12 Jul 2018 07:36:05 -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 IAxn7l4Q8P6S; Thu, 12 Jul 2018 07:36:02 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 B8B05131127; Thu, 12 Jul 2018 07:36:02 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id a195-v6so7122951itd.3; Thu, 12 Jul 2018 07:36:02 -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;  bh=qaNq7Gvm1sOAVcRWtAxy3JjqSUlP63GEUGM9a91NYuE=; b=GYr7LWm27MORvOHlWRcLgZa8eUUoDiWJjT6n45O7eppjSl3E7fgoOo7iHwBYFTrqXR owvKl100jiHtfrGycw4q7mzdJptLbglxn5SEZSw+FeAZnbXRAkYzVqlYOfhb4/qY4xV4 VOKHS8CCy97d4bPAUkIkAsfgrWzl1mPUm0HpR/rf+vhYkCuBC0yYNWNKCmsynLYpMJea 7GrUtaGVjcXIJRvhQwt4T+td88U8ggUy3wTxVBSRMlPaTVvJvxuE1msvo8khh196BlVG yLEz1pIJVuAivndeGO/uDlM6ZBA5oIEqcTLMIrnXbftFFnG8qmZ/PglXef48yj59E73s TxPQ==
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; bh=qaNq7Gvm1sOAVcRWtAxy3JjqSUlP63GEUGM9a91NYuE=; b=RQjp3tdpmxwiQ73K+gp3cc5/ZVxXIyDgIpk2592fVEK/uKHuorfNefwQ/CIp8gMEGZ mX1wCG6XLJ+TiWNP9Rzr6yjEKmPNNoK4E465X3rqyF56+RdVcFfCyp0Gn6iBBS9Tnm3I w95RNdUCqnkC5+24lAoIr28eRKFl18J7xT2HGjuu46fbjmz6qZ3AbOq9cy46sF0KQrRa Tp8oknppZGpGoRLqw3er7pyz8WI43hwoeFkJN8UUFd+jYx57x2UR1YSwyjtKpRteINWs IXdbGwtFFmaLcP/78zwt7TqanCeXkhPBhm7MdcU5AEdb0LWnRj9LP+hyo/ZftAfPyG7I I48w==
X-Gm-Message-State: AOUpUlHTJUBs7OleNAJ66LEBXFUG5PUYdHGh/4D7jnjmgbDPa9qvd0LH ZvBl/N/e/oir1rkBPKSEyKOMxNWU6KY/UnlxoUeEng==
X-Google-Smtp-Source: AAOMgpcmR6hoyJYRJG/vQVI8g4Wr6h7WDHYQ0yJ2dbIoik7j7PMqAelaD18MvQ4XyTwAitf9TQN7zElTa3Bhd++3Gn0=
X-Received: by 2002:a02:503:: with SMTP id e3-v6mr1819043jad.29.1531406161567;  Thu, 12 Jul 2018 07:36:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com>
In-Reply-To: <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com>
From: Bradley Meck <bradley.meck@gmail.com>
Date: Thu, 12 Jul 2018 09:35:51 -0500
Message-ID: <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000446f290570ce48c5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/rAzwrcdsTeoSqWssfxcxhCBfMSU>
Subject: [dispatch] Fwd:  WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 14:36:06 -0000

--000000000000446f290570ce48c5
Content-Type: text/plain; charset="UTF-8"

this mailing list workflow is not my norm, sorry for the forwarding

---------- Forwarded message ---------
From: Bradley Meck <bradley.meck@gmail.com>
Date: Thu, Jul 12, 2018 at 9:09 AM
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
To: Martin Thomson <martin.thomson@gmail.com>


I added Matt because he spent a considerable amount of time in helping me
make the document. Only `text/javascript` is not obsolete per
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages :

Servers should use text/javascript for JavaScript resources. Servers should
not use other JavaScript MIME types for JavaScript resources, and must not
use non-JavaScript MIME types.


We could add a paragraph stating that the other MIMEs are only there for
backwards compatibility concerns at the top if that makes sense.

On Tue, Jul 10, 2018 at 6:49 PM Martin Thomson <martin.thomson@gmail.com>
wrote:

> LGTM
>
> It's odd to see Matt listed in the acknowledgments and as an author.
>
> It would help to have a short statement saying which of the many media
> types is not obsolete, as the bulk of them are.
> On Wed, Jul 11, 2018 at 4:15 AM Mary Barnes <mary.ietf.barnes@gmail.com>
> wrote:
> >
> > Hi all,
> >
> >
> > We would like to start a 2 week WGLC for this document.    If you think
> the document is ready, please respond to this email.  If you have comments
> that you would like considered and/or any editorial suggestions, please
> post those as well.
> >
> >
> > The WGLC ends on July 25, 2018.
> >
> >
> > Regards,
> >
> > Mary
> >
> > DISPATCH WG tri-chair
> >
> >
> > ---------- Forwarded message ----------
> > From: <internet-drafts@ietf.org>
> > Date: Tue, May 8, 2018 at 5:41 PM
> > Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.txt
> > To: i-d-announce@ietf.org
> > Cc: dispatch@ietf..org
> >
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Dispatch WG of the IETF.
> >
> >         Title           : ECMAScript Media Types Updates
> >         Authors         : Bradley Farias
> >                           Matthew A. Miller
> >         Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
> >         Pages           : 21
> >         Date            : 2018-05-08
> >
> > Abstract:
> >    This document proposes updates to the ECMAScript media types,
> >    superseding the existing registrations for "application/javascript"
> >    and "text/javascript" by adding an additional extension and removing
> >    usage warnings.  This document updates RFC4329, "Scripting Media
> >    Types".
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-02
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> >
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
>

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

<div dir=3D"ltr">this mailing list workflow is not my norm, sorry for the f=
orwarding<div><br><div class=3D"gmail_quote"><div dir=3D"ltr">---------- Fo=
rwarded message ---------<br>From: <strong class=3D"gmail_sendername" dir=
=3D"auto">Bradley Meck</strong> <span dir=3D"ltr">&lt;<a href=3D"mailto:bra=
dley.meck@gmail.com">bradley.meck@gmail.com</a>&gt;</span><br>Date: Thu, Ju=
l 12, 2018 at 9:09 AM<br>Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-=
javascript-mjs-02.txt<br>To: Martin Thomson &lt;<a href=3D"mailto:martin.th=
omson@gmail.com">martin.thomson@gmail.com</a>&gt;<br></div><br><br><div dir=
=3D"ltr">I added Matt because he spent a considerable amount of time in hel=
ping me make the document. Only `text/javascript` is not obsolete per=C2=A0=
<a href=3D"https://html.spec.whatwg.org/multipage/scripting.html#scriptingL=
anguages" target=3D"_blank">https://html.spec.whatwg.org/multipage/scriptin=
g.html#scriptingLanguages</a> :=C2=A0<div><br></div><blockquote style=3D"ma=
rgin:0 0 0 40px;border:none;padding:0px">Servers should use text/javascript=
 for JavaScript resources. Servers should not use other JavaScript MIME typ=
es for JavaScript resources, and must not use non-JavaScript MIME types.<br=
><br><br></blockquote>We could add a paragraph stating that the other MIMEs=
 are only there for backwards compatibility concerns at the top if that mak=
es sense.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Jul =
10, 2018 at 6:49 PM Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gma=
il.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">LGTM<br>
<br>
It&#39;s odd to see Matt listed in the acknowledgments and as an author.<br=
>
<br>
It would help to have a short statement saying which of the many media<br>
types is not obsolete, as the bulk of them are.<br>
On Wed, Jul 11, 2018 at 4:15 AM Mary Barnes &lt;<a href=3D"mailto:mary.ietf=
.barnes@gmail.com" target=3D"_blank">mary.ietf.barnes@gmail.com</a>&gt; wro=
te:<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt;<br>
&gt; We would like to start a 2 week WGLC for this document.=C2=A0 =C2=A0 I=
f you think the document is ready, please respond to this email.=C2=A0 If y=
ou have comments that you would like considered and/or any editorial sugges=
tions, please post those as well.<br>
&gt;<br>
&gt;<br>
&gt; The WGLC ends on July 25, 2018.<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Mary<br>
&gt;<br>
&gt; DISPATCH WG tri-chair<br>
&gt;<br>
&gt;<br>
&gt; ---------- Forwarded message ----------<br>
&gt; From: &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank=
">internet-drafts@ietf.org</a>&gt;<br>
&gt; Date: Tue, May 8, 2018 at 5:41 PM<br>
&gt; Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.=
txt<br>
&gt; To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-ann=
ounce@ietf.org</a><br>
&gt; Cc: dispatch@ietf..org<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.<br>
&gt; This draft is a work item of the Dispatch WG of the IETF.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: ECMAScript Media Types Updates<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Bradley Farias<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0Matthew A. Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 draft-ietf-dispatch-javascript-mjs-02.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: 21<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 : 2018-05-08<br>
&gt;<br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0 This document proposes updates to the ECMAScript media ty=
pes,<br>
&gt;=C2=A0 =C2=A0 superseding the existing registrations for &quot;applicat=
ion/javascript&quot;<br>
&gt;=C2=A0 =C2=A0 and &quot;text/javascript&quot; by adding an additional e=
xtension and removing<br>
&gt;=C2=A0 =C2=A0 usage warnings.=C2=A0 This document updates RFC4329, &quo=
t;Scripting Media<br>
&gt;=C2=A0 =C2=A0 Types&quot;.<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dispatch-javasc=
ript-mjs/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-dispatch-javascript-mjs/</a><br>
&gt;<br>
&gt; There are also htmlized versions available at:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-dispatch-javascript-=
mjs-02" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr=
aft-ietf-dispatch-javascript-mjs-02</a><br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-j=
avascript-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://datatracker.=
ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02</a><br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dispatch-jav=
ascript-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/r=
fcdiff?url2=3Ddraft-ietf-dispatch-javascript-mjs-02</a><br>
&gt;<br>
&gt;<br>
&gt; Please note that it may take a couple of minutes from the time of subm=
ission<br>
&gt; until the htmlized version and diff are available at <a href=3D"http:/=
/tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<b=
r>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" tar=
get=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; dispatch mailing list<br>
&gt; <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.o=
rg</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a=
><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; dispatch mailing list<br>
&gt; <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.o=
rg</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a=
><br>
</blockquote></div>
</div></div></div>

--000000000000446f290570ce48c5--


From nobody Thu Jul 12 07:36:56 2018
Return-Path: <bradley.meck@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8C213112D; Thu, 12 Jul 2018 07:36:50 -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 YVDqZ8Q6Klne; Thu, 12 Jul 2018 07:36:45 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 8B83B130E3E; Thu, 12 Jul 2018 07:36:45 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id p17-v6so7074685itc.2; Thu, 12 Jul 2018 07:36:45 -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;  bh=gYorm+Sp3uSAhQThZU5C55XCrZnfWwcbJ4z4TybqA3s=; b=QYeNs8xDHPSX02yA4XpPS7hcMWSmYOHmJKVdn9U1TreWft534agQ+z6P/AbNhckEsM 6EUQyuaFLesOZDQgWtYdJY3MjjJTD0Onkft9gLoDiE5aQYlOEne7D8vVBDkQFVMWV2SW nD/zSaoESfjMPgV5nRJ/OVGoC3bnN+MlN0nn7WyubEoXHM9Rqhv/eDQfWiq3fu0TVs2y eLF3PIIbGen/MZDhkdc2QVf8/u7PA0zjwhI+owUngX/kB5sQIEai7+VvKRAGNCgz6V4H TSwJp/AMJS0AX7ya+3vfVrjlxhBOVvOLFU5gK8MB/pN9tZU4wExYQjsr40HlEtH8JRgo V3Sw==
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; bh=gYorm+Sp3uSAhQThZU5C55XCrZnfWwcbJ4z4TybqA3s=; b=rWeZ7skkPfqXz2EVcEYY+PSxJkSzYGZMZtMNwVPzKBOZTnJS2l7S377siH0wydl9Qo Z8sSTxJTIz564+MyniKyDe8Xq5340GAhWAqHaX0QEiU/8T4UNTcS0g1m+rQpiSu/xXXI wxZcX3baVP25soAAdmjzfWSrNS7QTJPW5f26D2MfFFmoZdDSoCvtQb3VJ6z/HMelF5Kc 4qDDRfk8ZmnbC3dAnxU7YEUrp0GsYIuK7aY7ese2jbf+TPXsYNfTjBG1Ihl9b+uVMXFt /qElWnLWsH9VxqRxsqeV/N63ZSHF4lAgE9lZhVCzGGNBKwHFeRzgnyQbqXBFukM99hTw XIpw==
X-Gm-Message-State: AOUpUlHggCYw8ymu5VIwHuRlgxVig47eIRSfppKYiLa4ZxjZ3betk5ci h59Obfi5+wVC0iE1vv4wsZSXiERvAMrTuybipi3uAf5o
X-Google-Smtp-Source: AAOMgpf8LccxCh173pQSiXLjnlrcty2gL9aQm28jXyDNzDuHxwzxmVTsC7+shTgpA431qYtzgfCuZOY5QwMWN8NJN80=
X-Received: by 2002:a02:8895:: with SMTP id n21-v6mr1743766jaj.21.1531406204504;  Thu, 12 Jul 2018 07:36:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <20180711010505.GA4920@pescadero.dbaron.org> <CANnEKUY-L3pb_vBQh+VW_oX6WSsU+nRa8=DsSgyk4u8i4FYyaA@mail.gmail.com>
In-Reply-To: <CANnEKUY-L3pb_vBQh+VW_oX6WSsU+nRa8=DsSgyk4u8i4FYyaA@mail.gmail.com>
From: Bradley Meck <bradley.meck@gmail.com>
Date: Thu, 12 Jul 2018 09:36:34 -0500
Message-ID: <CANnEKUZtN9HA3_pB5xUo0YwjTC-N-N226gM9V__fFf=jqgpCxQ@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d394150570ce4aef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/yeBFYNcixsSplND6Th-Dxv2uRis>
Subject: [dispatch] Fwd:  WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 14:36:51 -0000

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

this mailing list workflow is not my norm, sorry for the forwarding

---------- Forwarded message ---------
From: Bradley Meck <bradley.meck@gmail.com>
Date: Thu, Jul 12, 2018 at 9:27 AM
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
To: <dbaron@dbaron.org>


This seems like a reasonable thing to suggest as the intended use of
the .mjs extension, but I think it could be read to imply that
implementations should change their behavior as a result of file
extensions, which would be a rather unusual requirement on the Web.

If that requirement were the intent, it would seem to contradict the
processing rules for script elements in the HTML specification at:
https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type
which specify that the type attribute on the script element
determines whether a script is interpreted as a classic script or as
a module script.


----

Browsers use MIME to determine how to interpret resources when under
`<script type=3Dmodule>` but do not use MIME for other forms of `<script
type=3D...>`.

This is notable since it means charset is not honored and actually prevents
execution of JS in browsers if places in the attribute :
http://jsfiddle.net/uhfvxy69/2/ . It is actually looking at strings within
the `type` attribute even though they resemble MIMEs, they are not. In
addition `<script type=3Dtext/javascript>` does not use MIMEs even for the
source text they load, this is easily seen by comparing it with `<script
type=3Dmodule>` using data URLs : http://jsfiddle.net/urg89f6d/2/ .

Per the extension, the specification in
https://mimesniff.spec.whatwg.org/#interpreting-the-resource-metadata , it
explicitly calls out that file extensions are not used in order to obtain
MIMEs. The only concern for file extensions from web standards is left up
to browser environments themselves per
https://html.spec.whatwg.org/multipage/input.html#file-upload-state-(type=
=3Dfile)
:

On platforms that only use file extensions to describe file types, the
extensions listed here can be used to filter the allowed documents, while
the MIME types can be used with the system's type registration table
(mapping MIME types to extensions used by the system), if any, to determine
any other extensions to allow. Similarly, on a system that does not have
file names or extensions but labels documents with MIME types internally,
the MIME types can be used to pick the allowed files, while the extensions
can be used if the system has an extension registration table that maps
known extensions to MIME types used by the system.


This draft would not affect existing behavior of `<script
type=3Dtext/javascript>` through the changes to the MIME. There is the
addition of the `goal=3D` parameter that could be supported by browsers per=
 a
PR in https://github.com/whatwg/html/pull/3205 , but even if it is not
supported by browsers it is allowed to be ignored if it is an unrecognized
parameter per https://tools.ietf.org/html/rfc2045#section-5 .

MIME implementations must ignore any parameters whose names they do
not recognize.


----

Additionally, I wonder whether it would be useful to have a section
that documents the changes from RFC4329.  The introduction to
section 4 (Registration) seems to document some of them, but I
noticed that it doesn't mention that application/ecmascript and
application/javascript have been changed to Obsolete, and a number
of types not previously listed in RFC4329 (but listed in
https://mimesniff.spec.whatwg.org/#javascript-mime-type) have been
added as Obsolete.  (I didn't check for other differences.)


----

Only `text/javascript` is considered to be common anymore due to we
specification in
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages :

Servers should use text/javascript for JavaScript resources. Servers should
not use other JavaScript MIME types for JavaScript resources, and must not
use non-JavaScript MIME types.


We could perhaps just phrase this that it makes *all* other MIMEs obsolete
rather than making a list?

On Tue, Jul 10, 2018 at 8:05 PM L. David Baron <dbaron@dbaron.org> wrote:

> Hi -
>
> I have a few comments on the document:
>
>
> There are two things that might be read to imply that processors
> (e.g., browsers) should change their behavior as a result of file
> extensions.  In particular, in section 4 (Registration):
>
>                                                            In addition,
>    a new file extension of .mjs is to be added to the list of file
>    extensions with the restriction that it must correspond to the Module
>    grammar of [ECMA-262].
>
> and then repeatedly in the subsections of that section:
>
>    Restrictions on usage:  The file extension .mjs must be parsed using
>       the Module grammar of [ECMA-262]
>
> This seems like a reasonable thing to suggest as the intended use of
> the .mjs extension, but I think it could be read to imply that
> implementations should change their behavior as a result of file
> extensions, which would be a rather unusual requirement on the Web.
>
> If that requirement were the intent, it would seem to contradict the
> processing rules for script elements in the HTML specification at:
> https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type
> which specify that the type attribute on the script element
> determines whether a script is interpreted as a classic script or as
> a module script.
>
>
> Additionally, I wonder whether it would be useful to have a section
> that documents the changes from RFC4329.  The introduction to
> section 4 (Registration) seems to document some of them, but I
> noticed that it doesn't mention that application/ecmascript and
> application/javascript have been changed to Obsolete, and a number
> of types not previously listed in RFC4329 (but listed in
> https://mimesniff.spec.whatwg.org/#javascript-mime-type) have been
> added as Obsolete.  (I didn't check for other differences.)
>
>
> I'm happy to see the obsolete/common distinction in this draft
> reflecting current practice.
>
> -David
>
>
> On Tuesday 2018-07-10 13:15 -0500, Mary Barnes wrote:
> > Hi all,
> >
> >
> > We would like to start a 2 week WGLC for this document.    If you think
> the
> > document is ready, please respond to this email.  If you have comments
> that
> > you would like considered and/or any editorial suggestions, please post
> > those as well.
> >
> >
> > The WGLC ends on July 25, 2018.
> >
> >
> > Regards,
> >
> > Mary
> >
> > DISPATCH WG tri-chair
> >
> > ---------- Forwarded message ----------
> > From: <internet-drafts@ietf.org>;
> > Date: Tue, May 8, 2018 at 5:41 PM
> > Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.t=
xt
> > To: i-d-announce@ietf.org
> > Cc: dispatch@ietf.org
> >
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the Dispatch WG of the IETF.
> >
> >         Title           : ECMAScript Media Types Updates
> >         Authors         : Bradley Farias
> >                           Matthew A. Miller
> >         Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
> >         Pages           : 21
> >         Date            : 2018-05-08
> >
> > Abstract:
> >    This document proposes updates to the ECMAScript media types,
> >    superseding the existing registrations for "application/javascript"
> >    and "text/javascript" by adding an additional extension and removing
> >    usage warnings.  This document updates RFC4329, "Scripting Media
> >    Types".
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-=
02
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dispatch-javascript-mjs-=
02
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> >
>
> --
> =F0=9D=84=9E   L. David Baron                         http://dbaron.org/ =
  =F0=9D=84=82
> =F0=9D=84=A2   Mozilla                          https://www.mozilla.org/ =
  =F0=9D=84=82
>              Before I built a wall I'd ask to know
>              What I was walling in or walling out,
>              And to whom I was like to give offense.
>                - Robert Frost, Mending Wall (1914)
>

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

<div dir=3D"ltr"><span style=3D"font-size:small;text-decoration-style:initi=
al;text-decoration-color:initial;float:none;display:inline">this mailing li=
st workflow is not my norm, sorry for the forwarding</span><br><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr">---------- Forwarded message ---------<=
br>From: <strong class=3D"gmail_sendername" dir=3D"auto">Bradley Meck</stro=
ng> <span dir=3D"ltr">&lt;<a href=3D"mailto:bradley.meck@gmail.com">bradley=
.meck@gmail.com</a>&gt;</span><br>Date: Thu, Jul 12, 2018 at 9:27 AM<br>Sub=
ject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt<br>To:=
  &lt;<a href=3D"mailto:dbaron@dbaron.org">dbaron@dbaron.org</a>&gt;<br></d=
iv><br><br><div dir=3D"ltr"><blockquote style=3D"margin:0px 0px 0px 40px;bo=
rder:none;padding:0px"><div><span style=3D"font-size:small;background-color=
:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initi=
al;float:none;display:inline">This seems like a reasonable thing to suggest=
 as the intended use of</span></div><div><span style=3D"font-size:small;bac=
kground-color:rgb(255,255,255);text-decoration-style:initial;text-decoratio=
n-color:initial;float:none;display:inline">the .mjs extension, but I think =
it could be read to imply that</span></div><div><span style=3D"font-size:sm=
all;background-color:rgb(255,255,255);text-decoration-style:initial;text-de=
coration-color:initial;float:none;display:inline">implementations should ch=
ange their behavior as a result of file</span></div><div><span style=3D"fon=
t-size:small;background-color:rgb(255,255,255);text-decoration-style:initia=
l;text-decoration-color:initial;float:none;display:inline">extensions, whic=
h would be a rather unusual requirement on the Web.</span></div><div><br st=
yle=3D"font-size:small;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial"></div><div><span style=3D"font-s=
ize:small;background-color:rgb(255,255,255);text-decoration-style:initial;t=
ext-decoration-color:initial;float:none;display:inline">If that requirement=
 were the intent, it would seem to contradict the</span></div><div><span st=
yle=3D"font-size:small;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;float:none;display:inline">proces=
sing rules for script elements in the HTML specification at:</span></div><d=
iv><a href=3D"https://html.spec.whatwg.org/multipage/scripting.html#attr-sc=
ript-type" rel=3D"noreferrer" style=3D"color:rgb(17,85,204);font-size:small=
;background-color:rgb(255,255,255)" target=3D"_blank">https://html.spec.wha=
twg.org/multipage/scripting.html#attr-script-type</a></div><div><span style=
=3D"font-size:small;background-color:rgb(255,255,255);text-decoration-style=
:initial;text-decoration-color:initial;float:none;display:inline">which spe=
cify that the type attribute on the script element</span></div><div><span s=
tyle=3D"font-size:small;background-color:rgb(255,255,255);text-decoration-s=
tyle:initial;text-decoration-color:initial;float:none;display:inline">deter=
mines whether a script is interpreted as a classic script or as</span></div=
><div><span style=3D"font-size:small;background-color:rgb(255,255,255);text=
-decoration-style:initial;text-decoration-color:initial;float:none;display:=
inline">a module script.</span></div></blockquote><div><br></div><div>----<=
/div><br>Browsers use MIME to determine how to interpret resources when und=
er `&lt;script type=3Dmodule&gt;` but do not use MIME for other forms of `&=
lt;script type=3D...&gt;`.<div><br></div><div>This is notable since it mean=
s charset is not honored and actually prevents execution of JS in browsers =
if places in the attribute :=C2=A0<a href=3D"http://jsfiddle.net/uhfvxy69/2=
/" target=3D"_blank">http://jsfiddle.net/uhfvxy69/2/</a> . It is actually l=
ooking at strings within the `type` attribute even though they resemble MIM=
Es, they are not. In addition `&lt;script type=3Dtext/javascript&gt;` does =
not use MIMEs even for the source text they load, this is easily seen by co=
mparing it with `&lt;script type=3Dmodule&gt;` using data URLs :=C2=A0<a hr=
ef=3D"http://jsfiddle.net/urg89f6d/2/" target=3D"_blank">http://jsfiddle.ne=
t/urg89f6d/2/</a> .<div><div><br></div><div>Per the extension, the specific=
ation in=C2=A0<a href=3D"https://mimesniff.spec.whatwg.org/#interpreting-th=
e-resource-metadata" target=3D"_blank">https://mimesniff.spec.whatwg.org/#i=
nterpreting-the-resource-metadata</a> , it explicitly calls out that file e=
xtensions are not used in order to obtain MIMEs. The only concern for file =
extensions from web standards is left up to browser environments themselves=
 per <a href=3D"https://html.spec.whatwg.org/multipage/input.html#file-uplo=
ad-state-(type=3Dfile)" target=3D"_blank">https://html.spec.whatwg.org/mult=
ipage/input.html#file-upload-state-(type=3Dfile)</a> :</div><div><br></div>=
</div></div><blockquote style=3D"margin:0px 0px 0px 40px;border:none;paddin=
g:0px">On platforms that only use file extensions to describe file types, t=
he extensions listed here can be used to filter the allowed documents, whil=
e the MIME types can be used with the system&#39;s type registration table =
(mapping MIME types to extensions used by the system), if any, to determine=
 any other extensions to allow. Similarly, on a system that does not have f=
ile names or extensions but labels documents with MIME types internally, th=
e MIME types can be used to pick the allowed files, while the extensions ca=
n be used if the system has an extension registration table that maps known=
 extensions to MIME types used by the system.</blockquote><div><div><div><s=
pan style=3D"font-size:small;background-color:rgb(255,255,255);text-decorat=
ion-style:initial;text-decoration-color:initial;float:none;display:inline">=
<br></span></div><div><span style=3D"font-size:small;background-color:rgb(2=
55,255,255);text-decoration-style:initial;text-decoration-color:initial;flo=
at:none;display:inline">This draft would not affect existing behavior of `&=
lt;script type=3Dtext/javascript&gt;` through the changes to the MIME. Ther=
e is the addition of the `goal=3D` parameter that could be supported by bro=
wsers per a PR in=C2=A0<a href=3D"https://github.com/whatwg/html/pull/3205"=
 target=3D"_blank">https://github.com/whatwg/html/pull/3205</a> , but even =
if it is not supported by browsers it is allowed to be ignored if it is an =
unrecognized parameter per=C2=A0<a href=3D"https://tools.ietf.org/html/rfc2=
045#section-5" target=3D"_blank">https://tools.ietf.org/html/rfc2045#sectio=
n-5</a> .</span><br></div><div><span style=3D"font-size:small;background-co=
lor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:in=
itial;float:none;display:inline"><br></span></div></div></div><blockquote s=
tyle=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>MIME=C2=
=A0implementations must ignore any parameters whose names they do not=C2=A0=
recognize.</div></div></blockquote><div><div><br></div></div><div>----</div=
><div><br></div><blockquote style=3D"margin:0px 0px 0px 40px;border:none;pa=
dding:0px"><div><div><span style=3D"font-size:small;background-color:rgb(25=
5,255,255);text-decoration-style:initial;text-decoration-color:initial;floa=
t:none;display:inline">Additionally, I wonder whether it would be useful to=
 have a section</span></div></div><div><div><span style=3D"font-size:small;=
background-color:rgb(255,255,255);text-decoration-style:initial;text-decora=
tion-color:initial;float:none;display:inline">that documents the changes fr=
om RFC4329.=C2=A0 The introduction to</span></div></div><div><div><span sty=
le=3D"font-size:small;background-color:rgb(255,255,255);text-decoration-sty=
le:initial;text-decoration-color:initial;float:none;display:inline">section=
 4 (Registration) seems to document some of them, but I</span></div></div><=
div><div><span style=3D"font-size:small;background-color:rgb(255,255,255);t=
ext-decoration-style:initial;text-decoration-color:initial;float:none;displ=
ay:inline">noticed that it doesn&#39;t mention that application/ecmascript =
and</span></div></div><div><div><span style=3D"font-size:small;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial;float:none;display:inline">application/javascript have been changed =
to Obsolete, and a number</span></div></div><div><div><span style=3D"font-s=
ize:small;background-color:rgb(255,255,255);text-decoration-style:initial;t=
ext-decoration-color:initial;float:none;display:inline">of types not previo=
usly listed in RFC4329 (but listed in</span></div></div><div><div><a href=
=3D"https://mimesniff.spec.whatwg.org/#javascript-mime-type" rel=3D"norefer=
rer" style=3D"color:rgb(17,85,204);font-size:small;background-color:rgb(255=
,255,255)" target=3D"_blank">https://mimesniff.spec.whatwg.org/#javascript-=
mime-type</a><span style=3D"font-size:small;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;float:none;d=
isplay:inline">) have been</span></div></div><div><div><span style=3D"font-=
size:small;background-color:rgb(255,255,255);text-decoration-style:initial;=
text-decoration-color:initial;float:none;display:inline">added as Obsolete.=
=C2=A0 (I didn&#39;t check for other differences.)</span></div></div></bloc=
kquote><div><div><br></div><div>----</div><div><br></div><div>Only `text/ja=
vascript` is considered to be common anymore due to we specification in <a =
href=3D"https://html.spec.whatwg.org/multipage/scripting.html#scriptingLang=
uages" target=3D"_blank">https://html.spec.whatwg.org/multipage/scripting.h=
tml#scriptingLanguages</a> :</div><div><br></div></div><blockquote style=3D=
"margin:0 0 0 40px;border:none;padding:0px">Servers should use text/javascr=
ipt for JavaScript resources. Servers should not use other JavaScript MIME =
types for JavaScript resources, and must not use non-JavaScript MIME types.=
</blockquote><div><div><div><br></div><div>We could perhaps just phrase thi=
s that it makes *all* other MIMEs obsolete rather than making a list?</div>=
<div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Jul 10, 2018 a=
t 8:05 PM L. David Baron &lt;<a href=3D"mailto:dbaron@dbaron.org" target=3D=
"_blank">dbaron@dbaron.org</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">Hi -<br>
<br>
I have a few comments on the document:<br>
<br>
<br>
There are two things that might be read to imply that processors<br>
(e.g., browsers) should change their behavior as a result of file<br>
extensions.=C2=A0 In particular, in section 4 (Registration):<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0In addition,<=
br>
=C2=A0 =C2=A0a new file extension of .mjs is to be added to the list of fil=
e<br>
=C2=A0 =C2=A0extensions with the restriction that it must correspond to the=
 Module<br>
=C2=A0 =C2=A0grammar of [ECMA-262].<br>
<br>
and then repeatedly in the subsections of that section:<br>
<br>
=C2=A0 =C2=A0Restrictions on usage:=C2=A0 The file extension .mjs must be p=
arsed using<br>
=C2=A0 =C2=A0 =C2=A0 the Module grammar of [ECMA-262] <br>
<br>
This seems like a reasonable thing to suggest as the intended use of<br>
the .mjs extension, but I think it could be read to imply that<br>
implementations should change their behavior as a result of file<br>
extensions, which would be a rather unusual requirement on the Web.<br>
<br>
If that requirement were the intent, it would seem to contradict the<br>
processing rules for script elements in the HTML specification at:<br>
<a href=3D"https://html.spec.whatwg.org/multipage/scripting.html#attr-scrip=
t-type" rel=3D"noreferrer" target=3D"_blank">https://html.spec.whatwg.org/m=
ultipage/scripting.html#attr-script-type</a><br>
which specify that the type attribute on the script element<br>
determines whether a script is interpreted as a classic script or as<br>
a module script.<br>
<br>
<br>
Additionally, I wonder whether it would be useful to have a section<br>
that documents the changes from RFC4329.=C2=A0 The introduction to<br>
section 4 (Registration) seems to document some of them, but I<br>
noticed that it doesn&#39;t mention that application/ecmascript and<br>
application/javascript have been changed to Obsolete, and a number<br>
of types not previously listed in RFC4329 (but listed in<br>
<a href=3D"https://mimesniff.spec.whatwg.org/#javascript-mime-type" rel=3D"=
noreferrer" target=3D"_blank">https://mimesniff.spec.whatwg.org/#javascript=
-mime-type</a>) have been<br>
added as Obsolete.=C2=A0 (I didn&#39;t check for other differences.)<br>
<br>
<br>
I&#39;m happy to see the obsolete/common distinction in this draft<br>
reflecting current practice.<br>
<br>
-David<br>
<br>
<br>
On Tuesday 2018-07-10 13:15 -0500, Mary Barnes wrote:<br>
&gt; Hi all,<br>
&gt; <br>
&gt; <br>
&gt; We would like to start a 2 week WGLC for this document.=C2=A0 =C2=A0 I=
f you think the<br>
&gt; document is ready, please respond to this email.=C2=A0 If you have com=
ments that<br>
&gt; you would like considered and/or any editorial suggestions, please pos=
t<br>
&gt; those as well.<br>
&gt; <br>
&gt; <br>
&gt; The WGLC ends on July 25, 2018.<br>
&gt; <br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Mary<br>
&gt; <br>
&gt; DISPATCH WG tri-chair<br>
&gt; <br>
&gt; ---------- Forwarded message ----------<br>
&gt; From: &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank=
">internet-drafts@ietf.org</a>&gt;;<br>
&gt; Date: Tue, May 8, 2018 at 5:41 PM<br>
&gt; Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.=
txt<br>
&gt; To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-ann=
ounce@ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ie=
tf.org</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
&gt; directories.<br>
&gt; This draft is a work item of the Dispatch WG of the IETF.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: ECMAScript Media Types Updates<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Bradley Farias<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0Matthew A. Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 draft-ietf-dispatch-javascript-mjs-02.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: 21<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 : 2018-05-08<br>
&gt; <br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0 This document proposes updates to the ECMAScript media ty=
pes,<br>
&gt;=C2=A0 =C2=A0 superseding the existing registrations for &quot;applicat=
ion/javascript&quot;<br>
&gt;=C2=A0 =C2=A0 and &quot;text/javascript&quot; by adding an additional e=
xtension and removing<br>
&gt;=C2=A0 =C2=A0 usage warnings.=C2=A0 This document updates RFC4329, &quo=
t;Scripting Media<br>
&gt;=C2=A0 =C2=A0 Types&quot;.<br>
&gt; <br>
&gt; <br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dispatch-javasc=
ript-mjs/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-dispatch-javascript-mjs/</a><br>
&gt; <br>
&gt; There are also htmlized versions available at:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-dispatch-javascript-=
mjs-02" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr=
aft-ietf-dispatch-javascript-mjs-02</a><br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-j=
avascript-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://datatracker.=
ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02</a><br>
&gt; <br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dispatch-jav=
ascript-mjs-02" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/r=
fcdiff?url2=3Ddraft-ietf-dispatch-javascript-mjs-02</a><br>
&gt; <br>
&gt; <br>
&gt; Please note that it may take a couple of minutes from the time of subm=
ission<br>
&gt; until the htmlized version and diff are available at <a href=3D"http:/=
/tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<b=
r>
&gt; <br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" tar=
get=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; dispatch mailing list<br>
&gt; <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.o=
rg</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a=
><br>
&gt; <br>
<br>
-- <br>
=F0=9D=84=9E=C2=A0 =C2=A0L. David Baron=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://db=
aron.org/" rel=3D"noreferrer" target=3D"_blank">http://dbaron.org/</a>=C2=
=A0 =C2=A0=F0=9D=84=82<br>
=F0=9D=84=A2=C2=A0 =C2=A0Mozilla=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.moz=
illa.org/" rel=3D"noreferrer" target=3D"_blank">https://www.mozilla.org/</a=
>=C2=A0 =C2=A0=F0=9D=84=82<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Before I built a wall I&#39=
;d ask to know<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0What I was walling in or wa=
lling out,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0And to whom I was like to g=
ive offense.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Robert Frost, Mend=
ing Wall (1914)<br>
</blockquote></div></div></div></div></div>
</div></div>

--000000000000d394150570ce4aef--


From nobody Thu Jul 12 16:55:59 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCC613121C; Thu, 12 Jul 2018 16:55:57 -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, 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 mo7bHVdKyDpA; Thu, 12 Jul 2018 16:55:55 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 AC777131221; Thu, 12 Jul 2018 16:55:55 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id q11-v6so33500771oic.12; Thu, 12 Jul 2018 16:55:55 -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=YCrrexOwD6JKULPwlEmUefKClGToj4bUj8OqoavuYfA=; b=ufoc365aGqjhl4cHO3JtPdBtVnt6AJDk9XD0ROina1nUFkOWVBnUqvd8OWdutjf7ch MiBFJ38X45jF8AL9JI0T/IXG7sSt/zm1mP0LHysY0I5ySSPX0bmjXT6CTfevdItwH5iw +iJ2fl9n+UwEBp6MkBD7NM4zj486vTtYYTmLOSPtkckRRa8WO5S1QUzRZlWYECWEgIIw od8v8V9r1XzSySA8yMDLHivCmlFSwxVhbaUhzWkZz8kkdN9WDZjcoZ6BQFdBriCHLj7g LdanaYBjMza8kwkl0ebhWYLtzqhiHbTh/mVGVk5NPyESpkhRX7qgTLUhcWCtBTM/+Ogw Xnsg==
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=YCrrexOwD6JKULPwlEmUefKClGToj4bUj8OqoavuYfA=; b=MT0+q1vG21PsYtSKOyEEvRdakP+yn34l6RkJBeF+s25Nx1GZh0wMkB8Oa0qoWvc6Hq 0WWG1zq0dHo8E5ZpM+XvpbumQ1QiFwKXlNi0bHQRVosbCn1SlG+Nhg3FOItR95+1lTCH XbHqX/N888pn5bLDPp7TGkujQoeNPHNExxBsP+YwccAJzux3EcNW2ic+MasFQU46VdVa hXLaWw9oXn5DLkImpSJjAbJCaHXXgyeQeJNboPKhnDYpTY/jC50cpdFi3UR4LQMkWhOe t/vXrTrYg1qjq8Ew1uWkpKtve/f27z7U10xjYNIqknG3aEqt7ag0/AXvK4pgdMjt5gb9 N+/Q==
X-Gm-Message-State: AOUpUlFtyq91mGhOYPu1tgkW032qv6+4ajLnA/MlOeY7BUjFUNaGap0a lzB9v2J+VBig/e56f4iG0M86qatkamSCtWBbyCe1ojt8
X-Google-Smtp-Source: AAOMgpfoEyUWL29dHej4Tp1x4nIqepG3djDCt7ChUyKJ4IfFNPM0+0LgZWSLmZjFfGONuB8LNIPBNwOuj1Ppm3yx1ck=
X-Received: by 2002:aca:100f:: with SMTP id 15-v6mr4952424oiq.110.1531439754955;  Thu, 12 Jul 2018 16:55:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com>
In-Reply-To: <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 13 Jul 2018 09:55:43 +1000
Message-ID: <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com>
To: Bradley Meck <bradley.meck@gmail.com>
Cc: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Dn_LrhC2dhug9RSn5q5qL_BfAlc>
Subject: Re: [dispatch] Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 23:55:59 -0000

On Fri, Jul 13, 2018 at 12:36 AM Bradley Meck <bradley.meck@gmail.com> wrote:
> I added Matt because he spent a considerable amount of time in helping me make the document. Only `text/javascript` is not obsolete per https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages :

You don't need to acknowledge a co-author; that's all :)

I think that a paragraph on text/javascript would be ideal.  It's
otherwise buried in a lot of noise.


From nobody Sun Jul 15 08:35:39 2018
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70376130ED6 for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 08:35:29 -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=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 RHT8ByyY_Pfp for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 08:35:27 -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 69658130EFC for <dispatch@ietf.org>; Sun, 15 Jul 2018 08:35:27 -0700 (PDT)
Received: from [10.5.10.6] (ip-81-232-239-173.texas.us.northamericancoax.com [173.239.232.81]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6FFZMEx087936 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 15 Jul 2018 10:35:24 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-81-232-239-173.texas.us.northamericancoax.com [173.239.232.81] claimed to be [10.5.10.6]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <D6D7FC35-0C14-400D-ACEC-4E3890F65710@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1896578D-8701-442B-9B81-9C131F383DE4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 15 Jul 2018 11:35:21 -0400
In-Reply-To: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com>
Cc: dispatch@ietf.org
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/XXRVWGJmLjoSRpJY9UJ1ghwl97U>
Subject: Re: [dispatch] Web Service Discovery
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jul 2018 15:35:37 -0000

--Apple-Mail=_1896578D-8701-442B-9B81-9C131F383DE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Just a general reminder for everyone interested in this topic:

We=E2=80=99ve got a  list specifically for discussion of HTTP =
"well-known" topics at =
https://www.ietf.org/mailman/listinfo/Http-well-known

Thanks!

Ben.



> On Jun 14, 2018, at 12:50 PM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>=20
> Following our last meeting, I have put together a draft describing the =
approach I am using to perform Web Service Discovery which I would like =
to discuss in Montreal
>=20
> =
https://datatracker.ietf.org/doc/draft-hallambaker-web-service-discovery/
>=20
> My approach is largely constrained by existing RFCs and 'common sense' =
but these are not enough to remove all variability in approaches.
>=20
> The goal here is to enable discovery of Web Services by means of a =
compact account identifier in the form users are used to using. That is =
alice@example.com.
>=20
>=20
> I am aware of previous work in this space. In particular the original =
OpenID specification that tried to tell people http://example.com/alice =
was an account identifier, XRI, etc. and a large number of 'open' =
protocols with proprietary infrastructures. So there are now multiple =
services using the same 'open protocol' but the users can't talk to each =
other because the user names don't provide for federation.
>=20
> In my view, none of those are as good as the approach established in =
rfc822 and descendants which users are already familiar with.
>=20
> It will be noted that the approach does allow for negotiating across =
presentation protocols. For example, http vs QUIC or COAP. I have not =
gone down that rabbit hole at this time.
>=20
>=20
> I would like to move forward with this document either as an =
independent draft or as a Working Group. Which is appropriate really =
depends on whether there is an interest in defining additional discovery =
description keys to the three specified in the documentation. The keys I =
have defined are narrowly focused and the scope for variation is limited =
to deciding whether we should use abbreviations for the key names or =
not.
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


--Apple-Mail=_1896578D-8701-442B-9B81-9C131F383DE4
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAltLabkACgkQgFZKbJXz
1A1XxQ/8CB/kJkTzo5hSKVRRdjajl4gR8QNhIPE47un+t7XaFHIBYcqPB6QXzy8v
CinM+OXdAl1Mx+Wn3aDFCffJHNo1A2LfLn1gfeZ4r5o3GgvKON9GKZOLs7/uWq/G
nd8eSGXF8PFEH8vouZCLDVsXes7JXE5Ka9xFjCfY/DZw8WxTcSrTmLIVftwoRjvq
EanrRAES+YYMVloEzWsl5wna9p+aGXZes0Gj0nTQkqOktOKL4eGadcDfbIjq+Jrj
CVYcCjkaCgRa7QTbAUATpyRTy7gU0smx65RBqwk7GVn0x2GREkUM/sNngGti4K5T
vIh99aKtL7wXKkyHWYVVi9mC6/Ox9mXOLDOHlDtiDd6+vY80ot9J6Jh5ry7k9LyL
ftusgva9R4N5HHoElhON2w9o3qyl6RUkzzLCtIISGKB97+IVYrpv8hvGRMxDloOg
VamCc8eWgtTTwgHSTwWsto/0cU2w/6icWXNCQq0a3fR8UaUICN2PPs81Zr/Rf3A2
n3erkYPZsz1Tvl+pHvtbRoornZhWHTKx8+90HETRp1A60OXbXWI++x3Ugg5G2m8l
Zc+sVUM4Qh7SXcoFHA6QOPNHKlrHV9veoCzRdXE4UQ+BkxOVmYEl4XF/x4xjwZl8
EiBK3fYP7zyU55ym01RbC22j1luPN+1fDk0rCkCSDpqfD2Y7Iu4=
=RWqP
-----END PGP SIGNATURE-----

--Apple-Mail=_1896578D-8701-442B-9B81-9C131F383DE4--


From nobody Sun Jul 15 08:59:14 2018
Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CF6130E3E for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 08:59:11 -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=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 bzc1VH5qRxz9 for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 08:59:09 -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 B09D0130DEE for <dispatch@ietf.org>; Sun, 15 Jul 2018 08:59:09 -0700 (PDT)
Received: from dhcp-9a25.meeting.ietf.org (dhcp-9a25.meeting.ietf.org [31.133.154.37]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6FFx5v4091778 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 15 Jul 2018 10:59:06 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Message-Id: <CFB0FF74-7E51-4428-B012-94E47E9A014C@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C9DD4385-3635-47D1-8116-A25ACEA68131"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 15 Jul 2018 11:59:03 -0400
In-Reply-To: <D6D7FC35-0C14-400D-ACEC-4E3890F65710@nostrum.com>
Cc: dispatch@ietf.org
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com> <D6D7FC35-0C14-400D-ACEC-4E3890F65710@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/g4DOTaDeenVj-zIkK1xfD79EMik>
Subject: Re: [dispatch] Web Service Discovery
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jul 2018 15:59:12 -0000

--Apple-Mail=_C9DD4385-3635-47D1-8116-A25ACEA68131
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Oops, it has been brought to my attention that I was mistaken about the =
scope of the http-well-known mailing list. Please ignore my previous =
email :-)

Ben.

> On Jul 15, 2018, at 11:35 AM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Just a general reminder for everyone interested in this topic:
>=20
> We=E2=80=99ve got a  list specifically for discussion of HTTP =
"well-known" topics at =
https://www.ietf.org/mailman/listinfo/Http-well-known
>=20
> Thanks!
>=20
> Ben.
>=20
>=20
>=20
>> On Jun 14, 2018, at 12:50 PM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>>=20
>> Following our last meeting, I have put together a draft describing =
the approach I am using to perform Web Service Discovery which I would =
like to discuss in Montreal
>>=20
>> =
https://datatracker.ietf.org/doc/draft-hallambaker-web-service-discovery/
>>=20
>> My approach is largely constrained by existing RFCs and 'common =
sense' but these are not enough to remove all variability in approaches.
>>=20
>> The goal here is to enable discovery of Web Services by means of a =
compact account identifier in the form users are used to using. That is =
alice@example.com.
>>=20
>>=20
>> I am aware of previous work in this space. In particular the original =
OpenID specification that tried to tell people http://example.com/alice =
was an account identifier, XRI, etc. and a large number of 'open' =
protocols with proprietary infrastructures. So there are now multiple =
services using the same 'open protocol' but the users can't talk to each =
other because the user names don't provide for federation.
>>=20
>> In my view, none of those are as good as the approach established in =
rfc822 and descendants which users are already familiar with.
>>=20
>> It will be noted that the approach does allow for negotiating across =
presentation protocols. For example, http vs QUIC or COAP. I have not =
gone down that rabbit hole at this time.
>>=20
>>=20
>> I would like to move forward with this document either as an =
independent draft or as a Working Group. Which is appropriate really =
depends on whether there is an interest in defining additional discovery =
description keys to the three specified in the documentation. The keys I =
have defined are narrowly focused and the scope for variation is limited =
to deciding whether we should use abbreviations for the key names or =
not.
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>=20


--Apple-Mail=_C9DD4385-3635-47D1-8116-A25ACEA68131
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAltLb0cACgkQgFZKbJXz
1A1jExAAw3bOiXBeAmp1m7UvGgojNJvycQTtYLjVY+FkJ4q43lu3bMcpunKtQx2L
Vty3MGuiS2s1LLtPmnU5eFZOvQ94XdBasY/nzTgymGM+w9kvcuoTHu1IR1wpK8hv
Grp7+0NRuKWvsMXyVzl84awc+rVPbWKI/lSr25JpLZvcPscMwFYfyaqRxGMsh5Hk
xIpPPBOwQ45Q6Vu53Yw4hiAa1Lf9ElXnu6fmjilnO6moUqAJJjHexEVM7nxwpm+4
Ch0uWBoURNHrPRDU41yyPmL5I7o6d7sQnViZ/Qx5tF5gO9DpTO25l/+nsw6IRFc4
jby/CsQBzRn9NY294Bh4pQ63ZOYMc23IUb5ThNpG4FsAMQ8Xd9G7GZyLEcRBR8xX
3Q1Bt+4jgnBgQxcB4z7nEOj/8Sb1OM4tQYZ9qPwFAhOWuUxLFZMzQlNSHv4wmu1O
hTOb+G2vjoPqd95kShcy+Mb6JCRofNfvaQa3fjhNylO+kK3+j/qkNpMKjmCPpvmL
ub/b83wvC0R1GKNkJ60FTfvlEGQ2hEv89F40gK4uGzE4sU/HKaxWTKzumroMRlbZ
MZrPZFpge5B4L/8i3t0fHomlzywPLWL7rQdyx2et71OfE+Z4JtBe5IFB1FjQ+V3h
XJVJc+AJ6p2DepSLADnIwYLTZyUh2QcScNFaqEZqVT759nxeSCo=
=JBpU
-----END PGP SIGNATURE-----

--Apple-Mail=_C9DD4385-3635-47D1-8116-A25ACEA68131--


From nobody Sun Jul 15 20:08:43 2018
Return-Path: <hallam@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D17E130F36 for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 20:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=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 NzVZSB4qz5iV for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::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 CA9B9130F35 for <dispatch@ietf.org>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id k81-v6so72074340oib.4 for <dispatch@ietf.org>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r10ktCwnA2SmrAdKkbDOtGBjelSmWo32yurMe2FYO0E=; b=pyd5CWBGhCOvRPMSPqU4W++PJQfVudy5jTBhzA0uvMkNc7+rmfFLB2f7ibQUfDHmkT gzbl+8ENMIexQOz0HVavxuIQTXY1r7OJelctY9DZ2MdBADBlx5Lo6441XWpU19K+wgZh P6/KxiPChBcopod0fF8xVDETd97e/HhVrVelLZAPN9XefnKW0ltJvuHj/Js0v4v+umPi VFplnieyzNfUd5rETepgG5gMS851G9/Nl/TSJpWK/Yk7sVRuKxdF2utHg1L0n1pSCE6a FOdsihyW2E9vD07d76slVskpCJ6CPcVznm4vXH7yal7Qd02gdj5Hw4Ix3ifmsDDmlmw9 7b9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r10ktCwnA2SmrAdKkbDOtGBjelSmWo32yurMe2FYO0E=; b=pdDDj4cVpPVLAacNiGgVY2JpwvqwT0ns1W1BWkfbpvt9ioWkOnzBOFjsysv36NxnRT vJBxTaioKM6Sg+XQ3DQkU8fHo1rr6SKPL489NBfIPCyMO6v1rh7lvxPR5tHAsUojm7JT C3iraFtARajBIAWjAtm7cx1Ci7Jf+QU6lT3r3nhGJkVq6lgI/ByvRBAhMYim2NDv4hnX OWCvz4aoRKBthOR9oKz+FNU3EZlkdOj55Ww1P5a20F0AP9vgnGCgtkpXuCCNH9AGL2vn 41uf7/LHLAP3UuguW4ll7r9L7fjJIHPoA/gQNWResuLzFp5M2tmkpUxte9J0PloGsfh3 mgUg==
X-Gm-Message-State: AOUpUlGz4QA/1DNEQ2XnPnQZZ5mhUVhNy17dzSJQ4ursqEWS3jz6QUHR k43Q+8b7L/FO3BmjkYWp1di90VaGG6DHXYTtPqk=
X-Google-Smtp-Source: AAOMgpdFDVn8mjoRRxDKxzFrbMlFOFBncXjUwt0/g5yNdnvsdvwDClESh60pBDeU4wQuuvGpNVCbi5MMMA/gMeJ6XCQ=
X-Received: by 2002:aca:dad7:: with SMTP id r206-v6mr15634670oig.271.1531710518062;  Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:3a74:0:0:0:0:0 with HTTP; Sun, 15 Jul 2018 20:08:37 -0700 (PDT)
In-Reply-To: <CFB0FF74-7E51-4428-B012-94E47E9A014C@nostrum.com>
References: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com> <D6D7FC35-0C14-400D-ACEC-4E3890F65710@nostrum.com> <CFB0FF74-7E51-4428-B012-94E47E9A014C@nostrum.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 15 Jul 2018 23:08:37 -0400
X-Google-Sender-Auth: 8Dig4w1JWMs6PtZN5xeoSyIFDgo
Message-ID: <CAMm+LwiiPmuB4rUySdHjzTwtYkf57+2hTo2BajGimD=hMgVGTg@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000053f78c0571152591"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/-iNVjoC8pGQafdR2I8xBAUHAVm8>
Subject: Re: [dispatch] Web Service Discovery
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2018 03:08:41 -0000

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

What the draft is trying to do here is to join up the dots between the Web
Services world, the DNS world and the HTTP-ish world which are actually
more separate than might be expected.

The use of .well-known is only one part of the draft and is a default (but
a necessary one).


On Sun, Jul 15, 2018 at 11:59 AM, Ben Campbell <ben@nostrum.com> wrote:

> Oops, it has been brought to my attention that I was mistaken about the
> scope of the http-well-known mailing list. Please ignore my previous emai=
l
> :-)
>
> Ben.
>
> > On Jul 15, 2018, at 11:35 AM, Ben Campbell <ben@nostrum.com> wrote:
> >
> > Just a general reminder for everyone interested in this topic:
> >
> > We=E2=80=99ve got a  list specifically for discussion of HTTP "well-kno=
wn"
> topics at https://www.ietf.org/mailman/listinfo/Http-well-known
> >
> > Thanks!
> >
> > Ben.
> >
> >
> >
> >> On Jun 14, 2018, at 12:50 PM, Phillip Hallam-Baker <
> phill@hallambaker.com> wrote:
> >>
> >> Following our last meeting, I have put together a draft describing the
> approach I am using to perform Web Service Discovery which I would like t=
o
> discuss in Montreal
> >>
> >> https://datatracker.ietf.org/doc/draft-hallambaker-web-
> service-discovery/
> >>
> >> My approach is largely constrained by existing RFCs and 'common sense'
> but these are not enough to remove all variability in approaches.
> >>
> >> The goal here is to enable discovery of Web Services by means of a
> compact account identifier in the form users are used to using. That is
> alice@example.com.
> >>
> >>
> >> I am aware of previous work in this space. In particular the original
> OpenID specification that tried to tell people http://example.com/alice
> was an account identifier, XRI, etc. and a large number of 'open' protoco=
ls
> with proprietary infrastructures. So there are now multiple services usin=
g
> the same 'open protocol' but the users can't talk to each other because t=
he
> user names don't provide for federation.
> >>
> >> In my view, none of those are as good as the approach established in
> rfc822 and descendants which users are already familiar with.
> >>
> >> It will be noted that the approach does allow for negotiating across
> presentation protocols. For example, http vs QUIC or COAP. I have not gon=
e
> down that rabbit hole at this time.
> >>
> >>
> >> I would like to move forward with this document either as an
> independent draft or as a Working Group. Which is appropriate really
> depends on whether there is an interest in defining additional discovery
> description keys to the three specified in the documentation. The keys I
> have defined are narrowly focused and the scope for variation is limited =
to
> deciding whether we should use abbreviations for the key names or not.
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dispatch
> >
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Wha=
t the draft is trying to do here is to join up the dots between the Web Ser=
vices world, the DNS world and the HTTP-ish world which are actually more s=
eparate than might be expected.</div><div class=3D"gmail_default" style=3D"=
font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:=
small">The use of .well-known is only one part of the draft and is a defaul=
t (but a necessary one).=C2=A0</div><div class=3D"gmail_default" style=3D"f=
ont-size:small"><br></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Sun, Jul 15, 2018 at 11:59 AM, Ben Campbell <span dir=3D"ltr">&=
lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Oops, it has been brou=
ght to my attention that I was mistaken about the scope of the http-well-kn=
own mailing list. Please ignore my previous email :-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ben.<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On Jul 15, 2018, at 11:35 AM, Ben Campbell &lt;<a href=3D"mailto:ben@n=
ostrum.com">ben@nostrum.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Just a general reminder for everyone interested in this topic:<br>
&gt; <br>
&gt; We=E2=80=99ve got a=C2=A0 list specifically for discussion of HTTP &qu=
ot;well-known&quot; topics at <a href=3D"https://www.ietf.org/mailman/listi=
nfo/Http-well-known" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.=
org/mailman/<wbr>listinfo/Http-well-known</a><br>
&gt; <br>
&gt; Thanks!<br>
&gt; <br>
&gt; Ben.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;&gt; On Jun 14, 2018, at 12:50 PM, Phillip Hallam-Baker &lt;<a href=3D"=
mailto:phill@hallambaker.com">phill@hallambaker.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Following our last meeting, I have put together a draft describing=
 the approach I am using to perform Web Service Discovery which I would lik=
e to discuss in Montreal<br>
&gt;&gt; <br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-hallambaker-web-=
service-discovery/" rel=3D"noreferrer" target=3D"_blank">https://datatracke=
r.ietf.org/<wbr>doc/draft-hallambaker-web-<wbr>service-discovery/</a><br>
&gt;&gt; <br>
&gt;&gt; My approach is largely constrained by existing RFCs and &#39;commo=
n sense&#39; but these are not enough to remove all variability in approach=
es.<br>
&gt;&gt; <br>
&gt;&gt; The goal here is to enable discovery of Web Services by means of a=
 compact account identifier in the form users are used to using. That is <a=
 href=3D"mailto:alice@example.com">alice@example.com</a>.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; I am aware of previous work in this space. In particular the origi=
nal OpenID specification that tried to tell people <a href=3D"http://exampl=
e.com/alice" rel=3D"noreferrer" target=3D"_blank">http://example.com/alice<=
/a> was an account identifier, XRI, etc. and a large number of &#39;open&#3=
9; protocols with proprietary infrastructures. So there are now multiple se=
rvices using the same &#39;open protocol&#39; but the users can&#39;t talk =
to each other because the user names don&#39;t provide for federation.<br>
&gt;&gt; <br>
&gt;&gt; In my view, none of those are as good as the approach established =
in rfc822 and descendants which users are already familiar with.<br>
&gt;&gt; <br>
&gt;&gt; It will be noted that the approach does allow for negotiating acro=
ss presentation protocols. For example, http vs QUIC or COAP. I have not go=
ne down that rabbit hole at this time.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; I would like to move forward with this document either as an indep=
endent draft or as a Working Group. Which is appropriate really depends on =
whether there is an interest in defining additional discovery description k=
eys to the three specified in the documentation. The keys I have defined ar=
e narrowly focused and the scope for variation is limited to deciding wheth=
er we should use abbreviations for the key names or not.<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; dispatch mailing list<br>
&gt;&gt; <a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/di=
spatch</a><br>
&gt; <br>
<br>
</div></div></blockquote></div><br></div></div>

--00000000000053f78c0571152591--


From nobody Mon Jul 16 12:06:01 2018
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7618112F295 for <dispatch@ietfa.amsl.com>; Mon, 16 Jul 2018 12:05:59 -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 8OW9uU-3EgUl for <dispatch@ietfa.amsl.com>; Mon, 16 Jul 2018 12:05:55 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 A1633130F8B for <dispatch@ietf.org>; Mon, 16 Jul 2018 12:05:54 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id a4-v6so33022950lff.5 for <dispatch@ietf.org>; Mon, 16 Jul 2018 12:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=SMfzT4xEF+tvVCy2PJTaCI9H2z8+Sa6u1HNPRnWGcyc=; b=C2DViF7pynnlKfBDDnS+/ab9muwfU79BcUe4R0FqYFKfsEOzF3vENIlSpPwCIot+VM ijsdQs9OrW1V/biUz7/Xq4jhINeZ1KTELl91lecvyUlT9FsNHWlrAEcprVeLP6qJ9+UH 1Mx8ouIlpVefDelV+MEZ346ciV4ab7EftfWKQTTKzm8shbeQwELBm9TQSSfhfbvrIIDh e0TVT6EdFp2X3lKyhG1mk3lBHmqCwkhC5rJmDNGuda4169zBaiA7O2B2GCCMAi4+GJAK mq9YdDlnJGqsvwfcWPmheRgCGGWzMOFvn9pq9ncE7TJFAShXHzvaUWkuWUXkOOuA1kb2 7tlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=SMfzT4xEF+tvVCy2PJTaCI9H2z8+Sa6u1HNPRnWGcyc=; b=qVuSpWKVPi3H9aGnrXs0eRzJuJbYmGv3HI5sNpqWSsHgQQoPbw3wKObVXRDDV1anVC GSwHkk9rEUNu60f5sgtAjKlWCEDDCCHP+nroGkS8mpZmymXENTsFs6QSoaxgI+zshcst HgItfrnj6m/oTVtgJfSSnbYFPOBOOczkBqq8OW6Zf1U7UZ+NfWWvnzdAZABQmyHKWPAH QjTmbv9cHZuDWlq345m6VAXMMQ3ziC62bA5hxAmv9FnaPhpbEHqP7m9tVwqSAvyGDxP7 81rX0appFb4EFN2ftA6a4l1Vr3Shu3uV89TNh2oRCBgCKh44uwCIk05MNRWVT+xLOTuO 09Ag==
X-Gm-Message-State: AOUpUlGuVHgwUJYVz8K4r/1/ke9UvSV/NaccXOYwueKMugycYF5EKc03 0DNFZKQW8NEfjNzlJWmF99pbToMpmETYVcty3Dk=
X-Google-Smtp-Source: AAOMgpfGdCGiCV1tczNOBvjMaQwqBigl+5geFHXzQgxM0IElwxaKj6+4WQnIrJ61yrmp8r+yb2InBy7hpTl/Q8C2Aak=
X-Received: by 2002:a19:63dc:: with SMTP id v89-v6mr13128265lfi.23.1531767952558;  Mon, 16 Jul 2018 12:05:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:9f51:0:0:0:0:0 with HTTP; Mon, 16 Jul 2018 12:05:51 -0700 (PDT)
In-Reply-To: <5b4cdfb3.1c69fb81.3b095.e2cbSMTPIN_ADDED_BROKEN@mx.google.com>
References: <5b4cdfb3.1c69fb81.3b095.e2cbSMTPIN_ADDED_BROKEN@mx.google.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, 16 Jul 2018 14:05:51 -0500
Message-ID: <CAHBDyN53=sX554MvN=XUQWkxSwsr7DFM-o7O1pP+-S-+Sm9ZkA@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b0d0c705712284bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/uLLGbHG1oBPV1w21I19fEr_NXUU>
Subject: [dispatch] Fwd: [SIPForum-techwg] SIPNOC 2018 CFP Extended to August 7 -Submit Your SIPNOC 2018 Speaking Proposal Today!
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2018 19:06:00 -0000

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

I typically prefer not to have conference postings on WG mailing lists, but
I think this one is directly related that folks would be interested, so I'm
making this one posting.

If you have any questions, let me know.  This will be the 8th year of doing
this conference and there's always really interesting presentations.

Regards,
Mary.

---------- Forwarded message ----------
From: Marc Robins <marc.robins@sipforum.org>
Date: Mon, Jul 16, 2018 at 1:10 PM
Subject: [SIPForum-techwg] SIPNOC 2018 CFP Extended to August 7 -Submit
Your SIPNOC 2018 Speaking Proposal Today!
To: techwg@sipforum.org


SIP Forum TechWG Members:

We know many of you have been busy enjoying vacations and generally trying
to stay cool, so we decided to extend the deadline for SIPNOC 2018 Call for
Presentations until August 7, 2018.

So, if you=E2=80=99re interested in speaking at SIPNOC 2018, there=E2=80=99=
s still
time to submit
your proposal for a general sessions or panel discussion addressing the
deployment of SIP in service provider environments!

To view the official call for presentations, which includes instructions on
submitting material and specific SIPNOC policies, please visit
https://www.sipforum.org/news-events/sipnoc-2018-overview/
sipnoc-2018-call-for-presentations/. To submit, visit
https://www.easychair.org/conferences/?conf=3Dsipnoc2018.

Topics can include any issue relating to deploying, managing, and
monitoring SIP services and applications in a service provider environment,
including SIP peering, SIP trunking, Emergency Services, Congestion
Control, Scaling and Capacity Issues, SIP-based applications, Routing,
Security, SIP-Network Operations Center Best Practices, IPv6 deployment
challenges, User-agent Configuration, Standardization Issues and Progress,
HD voice deployments, Video Interoperability, WebRTC and SIP, Testing or
other issues facing SIP network operations.

SIPNOC 2018 offers several different types of speaking opportunities
including:

   - General Session Talks: A General Session presentation should be on a
   topic of interest to the general SIPNOC audience, and are generally 30
   minutes long (including time for Q&A).
   - General Session Panel Discussions: Panels are sessions with a
   moderator and a team of experts. The panel moderator should submit an
   abstract on the panel topic, a list of panelists, and how the panel will=
 be
   organized. Panel selection is based on the importance, originality, focu=
s
   and timeliness of the topic, expertise of proposed panelists, as well as
   the potential for informative and controversial discussion.
   - SIPNOC =E2=80=9CSuper-Sessions=E2=80=9D: These run for 1-2 hours, prov=
iding time to
   focus in-depth on a variety of issues important to the SIPNOC community.
   Topics can include a review of SIP RFCs and standards development, the
   regulatory environment, etc.
   - Research Topics: Researchers are invited to present short summaries of
   their work for operator feedback. Topics may include call routing, netwo=
rk
   performance, statistical measurement and analysis and protocol developme=
nt
   and implementation. Studies presented may be works in progress. Research=
ers
   from academia, government, and industry are encouraged to present.
   - BOFs: Birds of a Feather sessions are informal sessions on topics
   which are of interest to a portion of the SIPNOC community. BOFs may be
   held in break=E2=80=90out areas or in an unscheduled room. Requests for =
scheduled
   BOFs can be made at any time, including on site at the conference.

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

*SIPNOC 2018 General Info*

SIPNOC 2018 event details are located at https://www.sipforum.org/news-
events/sipnoc-2018-overview/.

And Early-Bird Registration for SIPNOC 2018 is officially open!

*Regular All-Access Conference Pass:* The regular =E2=80=9CAll-Access=E2=80=
=9D SIPNOC 2018
conference registration fee is $1295, and includes access to the Robocall
Summit followed by two days of General Session conference proceedings. This
=E2=80=9Call-inclusive=E2=80=9D fee also includes breakfasts, lunches and b=
reak
refreshments and snacks, and special networking receptions the first and
second nights of the event! Take advantage of Early-Bird Savings! Save $200
on the regular all-access rate if you register before August 1, 2018!

*Full Member All-Access Pass:* Individuals from SIP Forum Full Member
companies save even more ($300 to be exact) on an Early-Bird All-Access
Pass! (Please note that in order to qualify for this rate, you must be
employed by a SIP Forum Full Member company
<https://www.sipforum.org/membership/full-member-listing/>.) If you
qualify, please send an email to sipnocinfo@sipforum.org to obtain the
exclusive Full Member discount code.

*Robocall Summit Only Pass*: Just want to attend the Robocall Summit? No
problem! Simply select this registration type, with an associated fee of
$595.

*Conference Sessions Only Pass*: Aren=E2=80=99t interested in the Robocall =
Summit
but want to attend the General Sessions part of the conference? We have you
covered! Register by selecting the =E2=80=9CConference Sessions Only=E2=80=
=9D option. The
regular =E2=80=9CConference Sessions Only=E2=80=9D Pass is $1095 for two da=
ys of conference
proceedings, meals and breaks, and the Beer and Gear Networking Dinner
reception. Take advantage of Early-Bird Savings! Save $100 on the
conference-only rate if you register before August 1, 2018.

Register today at https://www.regonline.com/sipnoc2018.
------------------------------

*SIPNOC 2018 Sponsorship Information*

Interested in sponsoring SIPNOC 2018? Download the SIPNOC 2018 Sponsorship
Opportunities Brochure!
<https://www.sipforum.org/download/sipnoc-2017-sponsorship-opportunities-br=
ochure/?wpdmdl=3D3381>

For more information about the corporate sponsorship opportunities at
SIPNOC 2018, please contact Marc Robins, SIP Forum President and Managing
Director, at +1-203-829-6307 or marc.robins@sipforum.org.
------------------------------





_______________________________________________
techwg mailing list
Send mail to: techwg@sipforum.org
Unsubscribe or edit options at:  http://mail.sipforum.org/
mailman/listinfo/techwg

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

<div dir=3D"ltr">I typically prefer not to have conference postings on WG m=
ailing lists, but I think this one is directly related that folks would be =
interested, so I&#39;m making this one posting.=C2=A0 =C2=A0<div><br></div>=
<div>If you have any questions, let me know.=C2=A0 This will be the 8th yea=
r of doing this conference and there&#39;s always really interesting presen=
tations.=C2=A0</div><div><br></div><div>Regards,</div><div>Mary.</div><div>=
<br><div class=3D"gmail_quote">---------- Forwarded message ----------<br>F=
rom: <b class=3D"gmail_sendername">Marc Robins</b> <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:marc.robins@sipforum.org">marc.robins@sipforum.org</a>&gt;<=
/span><br>Date: Mon, Jul 16, 2018 at 1:10 PM<br>Subject: [SIPForum-techwg] =
SIPNOC 2018 CFP Extended to August 7 -Submit Your SIPNOC 2018 Speaking Prop=
osal Today!<br>To: <a href=3D"mailto:techwg@sipforum.org">techwg@sipforum.o=
rg</a><br><br><br><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div c=
lass=3D"m_7662008050844638566WordSection1"><p><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;">SIP Forum TechWG<span style=3D"co=
lor:#1f497d"> </span>Members:<u></u><u></u></span></p><p><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">We know many of you ha=
ve been busy enjoying vacations and generally trying to stay cool, so we de=
cided to extend the deadline for SIPNOC 2018 Call for Presentations until A=
ugust 7, 2018.<u></u><u></u></span></p><p><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;">So, if you=E2=80=99re interested in s=
peaking at SIPNOC 2018, there=E2=80=99s still time to<span style=3D"color:#=
1f497d"> s</span>ubmit your proposal for a general sessions or panel discus=
sion addressing the deployment of SIP in service provider environments!<u><=
/u><u></u></span></p><p><span style=3D"font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;">To view the official call for presentations, which incl=
udes instructions on submitting material and specific SIPNOC policies, plea=
se visit <span style=3D"color:#1f497d"><a href=3D"https://www.sipforum.org/=
news-events/sipnoc-2018-overview/sipnoc-2018-call-for-presentations/" targe=
t=3D"_blank">https://www.sipforum.org/news-<wbr>events/sipnoc-2018-overview=
/<wbr>sipnoc-2018-call-for-<wbr>presentations/</a>. T</span>o submit, visit=
 <a href=3D"https://www.easychair.org/conferences/?conf=3Dsipnoc2018" targe=
t=3D"_blank"><span style=3D"color:#1f497d">https://www.easychair.org/<wbr>c=
onferences/?conf=3Dsipnoc2018</span></a>.<u></u><u></u></span></p><p><span =
style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Topics can=
 include any issue relating to deploying, managing, and monitoring SIP serv=
ices and applications in a service provider environment, including SIP peer=
ing, SIP trunking, Emergency Services, Congestion Control, Scaling and Capa=
city Issues, SIP-based applications, Routing, Security, SIP-Network Operati=
ons Center Best Practices, IPv6 deployment challenges, User-agent Configura=
tion, Standardization Issues and Progress, HD voice deployments, Video Inte=
roperability, WebRTC and SIP, Testing or other issues facing SIP network op=
erations. <u></u><u></u></span></p><p><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;">SIPNOC 2018 offers several different type=
s of speaking opportunities including:<u></u><u></u></span></p><ul type=3D"=
disc"><li class=3D"MsoNormal"><span style=3D"font-size:12.0pt">General Sess=
ion Talks: A General Session presentation should be on a topic of interest =
to the general SIPNOC audience, and are generally 30 minutes long (includin=
g time for Q&amp;A). <u></u><u></u></span></li><li class=3D"MsoNormal"><spa=
n style=3D"font-size:12.0pt">General Session Panel Discussions: Panels are =
sessions with a moderator and a team of experts. The panel moderator should=
 submit an abstract on the panel topic, a list of panelists, and how the pa=
nel will be organized. Panel selection is based on the importance, original=
ity, focus and timeliness of the topic, expertise of proposed panelists, as=
 well as the potential for informative and controversial discussion.<u></u>=
<u></u></span></li><li class=3D"MsoNormal"><span style=3D"font-size:12.0pt"=
>SIPNOC =E2=80=9CSuper-Sessions=E2=80=9D: These run for 1-2 hours, providin=
g time to focus in-depth on a variety of issues important to the SIPNOC com=
munity. Topics can include a review of SIP RFCs and standards development, =
the regulatory environment, etc.<u></u><u></u></span></li><li class=3D"MsoN=
ormal"><span style=3D"font-size:12.0pt">Research Topics: Researchers are in=
vited to present short summaries of their work for operator feedback. Topic=
s may include call routing, network performance, statistical measurement an=
d analysis and protocol development and implementation. Studies presented m=
ay be works in progress. Researchers from academia, government, and industr=
y are encouraged to present.<u></u><u></u></span></li><li class=3D"MsoNorma=
l"><span style=3D"font-size:12.0pt">BOFs: Birds of a Feather sessions<span =
style=3D"color:#1f497d"> </span>are informal sessions on topics which are o=
f interest to a portion of the SIPNOC community. BOFs may be held in break=
=E2=80=90out areas or in an unscheduled room. Requests for scheduled BOFs c=
an be made at any time, including on site at the conference.<u></u><u></u><=
/span></li></ul><div class=3D"MsoNormal" align=3D"center" style=3D"text-ali=
gn:center"><span style=3D"font-size:12.0pt;font-family:&quot;MS PGothic&quo=
t;,&quot;sans-serif&quot;"><hr size=3D"2" width=3D"100%" align=3D"center"><=
/span></div><p><b><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;">SIPNOC 2018 General Info<u></u><u></u></span></b></p><p><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">SIPNOC 20=
18 event details are located at <span style=3D"color:#1f497d"><a href=3D"ht=
tps://www.sipforum.org/news-events/sipnoc-2018-overview/" target=3D"_blank"=
><span style=3D"color:#1f497d">https://www.sipforum.org/news-<wbr>events/si=
pnoc-2018-overview/</span></a></span>.<u></u><u></u></span></p><p><span sty=
le=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">And Early-Bir=
d Registration for SIPNOC 2018 is officially open!<u></u><u></u></span></p>=
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Regular All-Acce=
ss Conference Pass:</span></b><span style=3D"font-size:12.0pt"> The regular=
 =E2=80=9CAll-Access=E2=80=9D SIPNOC 2018 conference registration fee is $1=
295, and includes access to the Robocall Summit followed by two days of Gen=
eral Session conference proceedings. This =E2=80=9Call-inclusive=E2=80=9D f=
ee also includes breakfasts, lunches and break refreshments and snacks, and=
 special networking receptions the first and second nights of the event! Ta=
ke advantage of Early-Bird Savings! Save $200 on the regular all-access rat=
e if you register before August 1, 2018!<u></u><u></u></span></p><p class=
=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Full Member All-Access P=
ass:</span></b><span style=3D"font-size:12.0pt"> Individuals from SIP Forum=
 Full Member companies save even more ($300 to be exact) on an Early-Bird A=
ll-Access Pass! (Please note that in order to qualify for this rate, you mu=
st be employed by a <a href=3D"https://www.sipforum.org/membership/full-mem=
ber-listing/" target=3D"_blank">SIP Forum Full Member company</a>.) If you =
qualify, please send an email to <a href=3D"mailto:sipnocinfo@sipforum.org"=
 target=3D"_blank">sipnocinfo@sipforum.org</a> to obtain the exclusive Full=
 Member discount code.<u></u><u></u></span></p><p class=3D"MsoNormal"><b><s=
pan style=3D"font-size:12.0pt">Robocall Summit Only Pass</span></b><span st=
yle=3D"font-size:12.0pt">: Just want to attend the Robocall Summit? No prob=
lem! Simply select this registration type, with an associated fee of $595.<=
u></u><u></u></span></p><p class=3D"MsoNormal"><b><span style=3D"font-size:=
12.0pt">Conference Sessions Only Pass</span></b><span style=3D"font-size:12=
.0pt">: Aren=E2=80=99t interested in the Robocall Summit but want to attend=
 the General Sessions part of the conference? We have you covered! Register=
 by selecting the =E2=80=9CConference Sessions Only=E2=80=9D option. The re=
gular =E2=80=9CConference Sessions Only=E2=80=9D Pass is $1095 for two days=
 of conference proceedings, meals and breaks, and the Beer and Gear Network=
ing Dinner reception. Take advantage of Early-Bird Savings! Save $100 on th=
e conference-only rate if you register before August 1, 2018.<u></u><u></u>=
</span></p><p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;">Register today at <a href=3D"https://www.regonline.com/sipnoc2018=
" target=3D"_blank"><span style=3D"color:#1f497d">https://www.regonline.com=
/<wbr>sipnoc2018</span></a>.=C2=A0<u></u><u></u></span></p><div class=3D"Ms=
oNormal" align=3D"center" style=3D"text-align:center"><span style=3D"font-s=
ize:12.0pt"><hr size=3D"2" width=3D"100%" align=3D"center"></span></div><p>=
<b><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">S=
IPNOC 2018 Sponsorship Information<u></u><u></u></span></b></p><p><span sty=
le=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Interested in=
 sponsoring SIPNOC 2018? <a href=3D"https://www.sipforum.org/download/sipno=
c-2017-sponsorship-opportunities-brochure/?wpdmdl=3D3381" target=3D"_blank"=
>Download the SIPNOC 2018 Sponsorship Opportunities Brochure!</a> <u></u><u=
></u></span></p><p><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;">For more information about the<span style=3D"color:#1f497d">=
 </span>corporate sponsorship opportunities at SIPNOC 2018, please contact =
Marc Robins<span style=3D"color:#1f497d">, </span>SIP Forum President and M=
anaging Director, at +1-203-829-6307 or <a href=3D"mailto:marc.robins@sipfo=
rum.org" target=3D"_blank">marc.robins@sipforum.org</a>.<u></u><u></u></spa=
n></p><div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"=
><span style=3D"font-size:12.0pt"><hr size=3D"2" width=3D"100%" align=3D"ce=
nter"></span></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=
=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div><br>____________________=
__________<wbr>_________________<br>
techwg mailing list<br>
Send mail to: <a href=3D"mailto:techwg@sipforum.org">techwg@sipforum.org</a=
><br>
Unsubscribe or edit options at:=C2=A0 <a href=3D"http://mail.sipforum.org/m=
ailman/listinfo/techwg" rel=3D"noreferrer" target=3D"_blank">http://mail.si=
pforum.org/<wbr>mailman/listinfo/techwg</a><br>
<br></div><br></div></div>

--000000000000b0d0c705712284bf--


From nobody Tue Jul 17 07:15:42 2018
Return-Path: <masinter@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C9F012F1A6; Tue, 17 Jul 2018 07:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=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 NZLegSF7ORRX; Tue, 17 Jul 2018 07:15:39 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 6FA99127AC2; Tue, 17 Jul 2018 07:15:39 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id r1-v6so497559pgp.11; Tue, 17 Jul 2018 07:15:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=YQGX9sBLibPSn5cPD54sQzmN+QnGd/WwVsnRz6Yse8g=; b=bGcetcOZbw/fjhRJNoKRfTIvI+lahmSMtOm+rxCA3Ayv6wWR5YZOlx7gYUdgE6KDzm qFSqdQBVJI7O6s1I2u0yR5h3WdDvu/ns0SmBeKv8epJGR5rhfqKeSucqgi7Xuu2FPoSp pHBkJUAhj+WBzGnie1yblO5mE4RZgS+0RWxJYHRQjYLDCVhZKfBJzm0opHANcTP3z9M1 ZsTuws/p8jUqsW91/XM1S7i4lXWrflNuk6UCRj0bHR5D8y/iybFwucpv0sLx6xLn3wnQ 8di4tcxdHtrKVMy0/rLd7gJiJv2EPpHfEqswiVVWo32jR+Z8CE0MCWmOYtQZo36KOCQB O/cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=YQGX9sBLibPSn5cPD54sQzmN+QnGd/WwVsnRz6Yse8g=; b=dIgYJQXpgk4k36Aqa+QsWCBawlTu26MSPvksGU4GmKVYl8ZcMPfXL197VFhxh1/gCX Krh87sA0q+z7z3hzi3uaG0u8Kueh2NmyjdJ+vKgLug/BURg2BCYJM444tz/IbUA+gVW+ KG6zJMbfPU+uO6oYsEBYd7E2wsmK+IL88CzZ09VGKzu6gRJPiDBvrS1LVQJN4ZpB0bcD hXGRre9uktVmmqi4EoSDXxkUxk2sWNBrMjc/dytut/+PVYG7UPJyDrXv0OY/DdvH/Jnv 8UojmTFY4O2Cd7Wh6pLzb+LbgxF4m4iaBiEBqGwA3r5VSAcVgzMxde5kuszLf8ZmXtWJ VksA==
X-Gm-Message-State: AOUpUlFYiwnHHW9NZ0vPVSCRq+uGcJCzhF+C/JXhMheqn6PVjktWlUhN WS8XTT0iioXIaSYzVR35rf4=
X-Google-Smtp-Source: AAOMgpckA/cBnA+rNOUGDqorbYAvmolakiF205VsKxZrcuDvhZSs93BN2/P1vU/EvavezpuTn0FDcQ==
X-Received: by 2002:a65:6203:: with SMTP id d3-v6mr1789973pgv.420.1531836938874;  Tue, 17 Jul 2018 07:15:38 -0700 (PDT)
Received: from TVPC (c-24-6-174-39.hsd1.ca.comcast.net. [24.6.174.39]) by smtp.gmail.com with ESMTPSA id g5-v6sm3481411pgn.73.2018.07.17.07.15.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 07:15:37 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Martin Thomson'" <martin.thomson@gmail.com>, "'Bradley Meck'" <bradley.meck@gmail.com>
Cc: "'DISPATCH'" <dispatch@ietf.org>, <draft-ietf-dispatch-javascript-mjs@ietf.org>
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com>, <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com>
In-Reply-To: <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com>
Date: Tue, 17 Jul 2018 07:15:36 -0700
Message-ID: <000001d41dd8$a2ad12e0$e80738a0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHUGjwIgZSPI+/PLkuVU40cEzx4fKSTcM7a
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/YB4zwINenVoVwV-14BPARUThQBE>
Subject: Re: [dispatch] Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 14:15:41 -0000

=E2=9E=A2 Only `text/javascript` is not obsolete per =
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages =


I wonder about the utility of newly registering (or updating the =
registration) of types that are obsolete.
If there=E2=80=99s significant deployment of names that new =
implementations need to be aware of, then =E2=80=98obsolete=E2=80=99 =
isn=E2=80=99t the right status; if not, then who would use the new, but =
obsolete, definition?

Larry
http://LarryMasinter.net





From nobody Tue Jul 17 07:25:29 2018
Return-Path: <bradley.meck@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBDD129385; Tue, 17 Jul 2018 07:25:26 -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 734K2JUXl5zz; Tue, 17 Jul 2018 07:25:23 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 69E1E130FCD; Tue, 17 Jul 2018 07:25:23 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id v71-v6so2132516itb.3; Tue, 17 Jul 2018 07:25:23 -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=7qbcFyH/2xDj4GWmku5qe1pLGvrnHQqYqqchu4YInxs=; b=poq3HswxKQT23yrvQOT8YEEToBz6TNZoNoz8XhuxoLsNFYriQsaMc1r8w0gSlQ+5Um YA9GycxmjRuv1lQhjsKuZ0fYQWgS3Rp6xzduSpOA/tOP5VmmxORhWg4wRcgpF3xJfptE wf0HoYqaj7Cl2RjD2n3i8tJYfeKiA02E0UMYLt9CnYWkUl3JQtAmWdFHoo03KAv5oa9a uA1c/kitxyDDEET9Ju4qpwFtEmToz3KAJOu1dDmiJH6PR54jt6Da/9xWPo+fJ0CsabZ5 flWfYhXPp4xP+do5UgSLvZy5NopO/U8jw+VBg1L+HGnwf0lQjL8Qs+W3hZBdJz25Is7z 64vw==
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=7qbcFyH/2xDj4GWmku5qe1pLGvrnHQqYqqchu4YInxs=; b=rC6xc0pO0ZiKclgPV9WxDW+7O1RQBvmdcTuAY65HbOX+YoaW17tROfoQ5JRz1aiegw 5clTSBByt40CVAPO4FmT7FlRc6Lo5N6L6IkpBJHTeoNVack6C+TY9ACStFTIP9eNrrmj cC0oeYQzP1M7Vm93Abclm2NYuunCQeSWWYQbWRj5CfU4yz77AhnZXLydOWhHRuO7vOmY 2fKopJiXvq7afBIWwxX0bFDcFoITFCrgbuKXQjX4m0uD1c5MHG8/LXW4TTMPBtv7VVo2 l4jx9asmPcP+yYPhitCT13t/UOicaYyZI0qP9QB7k6PuVfyP44EQjCgiiOpnae1VOIWp E9zQ==
X-Gm-Message-State: AOUpUlGOXtGgVdrt8FafOGZEAcyXcb7+CmjtYziqeAHTAGT8FmATXvPQ +CZXTRrp9XWeRPgPy1ef+IRTpmfsHGzMy+WVAD0=
X-Google-Smtp-Source: AAOMgpfZIQhvfQINbiZyrmwSqwhqbJfxdoX4kNZgqmZev2h/ARr+mXV5tVFa9LROGTRHT+i/Hm32vkGVQIA8YkYEUvs=
X-Received: by 2002:a02:9833:: with SMTP id t48-v6mr1681732jaj.111.1531837522684;  Tue, 17 Jul 2018 07:25:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com> <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com> <000001d41dd8$a2ad12e0$e80738a0$@acm.org>
In-Reply-To: <000001d41dd8$a2ad12e0$e80738a0$@acm.org>
From: Bradley Meck <bradley.meck@gmail.com>
Date: Tue, 17 Jul 2018 09:25:18 -0500
Message-ID: <CANnEKUZCyb29-_e-6FKrqM0vbJyiZkOSuFj_0GZAq5ve4H=wFg@mail.gmail.com>
To: LMM@acm.org
Cc: Martin Thomson <martin.thomson@gmail.com>, DISPATCH <dispatch@ietf.org>,  draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000064ae82057132b706"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/sshlBJ_7V57MPuAWtIGSXKUwGJA>
Subject: Re: [dispatch] Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 14:25:27 -0000

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

Per https://github.com/bmeck/I-D/issues/2

The extra registrations are to match up with the Web specification on
accepted MIME types for historical reasons
https://mimesniff.spec.whatwg.org/#javascript-mime-type

On Tue, Jul 17, 2018 at 9:15 AM Larry Masinter <LMM@acm.org> wrote:

> =E2=9E=A2 Only `text/javascript` is not obsolete per
> https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages
>
> I wonder about the utility of newly registering (or updating the
> registration) of types that are obsolete.
> If there=E2=80=99s significant deployment of names that new implementatio=
ns need
> to be aware of, then =E2=80=98obsolete=E2=80=99 isn=E2=80=99t the right s=
tatus; if not, then who
> would use the new, but obsolete, definition?
>
> Larry
> http://LarryMasinter.net
>
>
>
>
>

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

<div dir=3D"ltr">Per=C2=A0<a href=3D"https://github.com/bmeck/I-D/issues/2"=
>https://github.com/bmeck/I-D/issues/2</a><div><br></div><div>The extra reg=
istrations are to match up with the Web specification on accepted MIME type=
s for historical reasons=C2=A0<a href=3D"https://mimesniff.spec.whatwg.org/=
#javascript-mime-type">https://mimesniff.spec.whatwg.org/#javascript-mime-t=
ype</a></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, =
Jul 17, 2018 at 9:15 AM Larry Masinter &lt;<a href=3D"mailto:LMM@acm.org">L=
MM@acm.org</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">=E2=9E=
=A2 Only `text/javascript` is not obsolete per <a href=3D"https://html.spec=
.whatwg.org/multipage/scripting.html#scriptingLanguages" rel=3D"noreferrer"=
 target=3D"_blank">https://html.spec.whatwg.org/multipage/scripting.html#sc=
riptingLanguages</a> <br>
<br>
I wonder about the utility of newly registering (or updating the registrati=
on) of types that are obsolete.<br>
If there=E2=80=99s significant deployment of names that new implementations=
 need to be aware of, then =E2=80=98obsolete=E2=80=99 isn=E2=80=99t the rig=
ht status; if not, then who would use the new, but obsolete, definition?<br=
>
<br>
Larry<br>
<a href=3D"http://LarryMasinter.net" rel=3D"noreferrer" target=3D"_blank">h=
ttp://LarryMasinter.net</a><br>
<br>
<br>
<br>
<br>
</blockquote></div>

--00000000000064ae82057132b706--


From nobody Wed Jul 18 07:53:29 2018
Return-Path: <jari.arkko@piuha.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4574C130DD3 for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 07:53:28 -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, 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 RmpyRnx5tvSY for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 07:53:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5391B130F06 for <dispatch@ietf.org>; Wed, 18 Jul 2018 07:53:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 943616600BC; Wed, 18 Jul 2018 17:53:23 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxTMSkBZqLYZ; Wed, 18 Jul 2018 17:53:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id F0F4C660162; Wed, 18 Jul 2018 17:53:21 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 18 Jul 2018 10:53:20 -0400
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com>
To: dispatch@ietf.org
Message-Id: <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/DG9j3BtUakMxjaPl3YQ7Q2GCZXM>
Subject: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 14:53:28 -0000

Ted and I have written a draft to update one IANA registry that
(we think unnecessarily) calls for registering postal addresses
for people who request code points. We think this should
not be done for privacy, GDPR, exception at IANA, etc.=20
reasons.

We=E2=80=99d love to get feedback, and if there=E2=80=99s no roadblocks,
move pretty quickly to asking the working group or the ADs
to take the draft forward.

Jari

> Name:		draft-arkko-trip-registry-update
> Revision:	00
> Title:		Update to the TRIP IANA Registry Rules Regarding =
Postal Addresses
> Document date:	2018-07-16
> Group:		Individual Submission
> Pages:		3
> URL:            =
https://www.ietf.org/internet-drafts/draft-arkko-trip-registry-update-00.t=
xt
> Status:         =
https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/
> Htmlized:       =
https://tools.ietf.org/html/draft-arkko-trip-registry-update-00
> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-arkko-trip-registry-update
>=20
>=20
> Abstract:
>   This memo updates the IANA registry rules for the Telephony Routing
>   over IP (TRIP) protocol, by no longer requiring that postal =
addresses
>   be included in contact information.
>=20
>   This memo updates RFC 3219.


From nobody Wed Jul 18 08:21:37 2018
Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B562213119C for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 08:21:35 -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, 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 Et-ageH83-hb for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 08:21:33 -0700 (PDT)
Received: from smtp72.ord1d.emailsrvr.com (smtp72.ord1d.emailsrvr.com [184.106.54.72]) (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 73BF7131127 for <dispatch@ietf.org>; Wed, 18 Jul 2018 08:21:33 -0700 (PDT)
Received: from smtp2.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp2.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 7CF62402D9; Wed, 18 Jul 2018 11:21:32 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp2.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 314824044E;  Wed, 18 Jul 2018 11:21:32 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from rtp-vpn1-822.cisco.com ([UNAVAILABLE]. [173.38.117.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:25 (trex/5.7.12); Wed, 18 Jul 2018 11:21:32 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
Date: Wed, 18 Jul 2018 11:21:31 -0400
Cc: dispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <595F209B-CC6A-4D91-A8F5-DFA3B95CD83B@iii.ca>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/5-QADoSiFUQUvmNt3qzbx6wc3Ks>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 15:21:36 -0000

100% support this draft and it looks done to me. It seems like a good =
draft to be AD to sponsor but if the ADs would prefer it to go through =
the WG, I think we should  adopt it if they are no objections.=20


> On Jul 18, 2018, at 10:53 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> Ted and I have written a draft to update one IANA registry that
> (we think unnecessarily) calls for registering postal addresses
> for people who request code points. We think this should
> not be done for privacy, GDPR, exception at IANA, etc.=20
> reasons.
>=20
> We=E2=80=99d love to get feedback, and if there=E2=80=99s no =
roadblocks,
> move pretty quickly to asking the working group or the ADs
> to take the draft forward.
>=20
> Jari
>=20
>> Name:		draft-arkko-trip-registry-update
>> Revision:	00
>> Title:		Update to the TRIP IANA Registry Rules Regarding =
Postal Addresses
>> Document date:	2018-07-16
>> Group:		Individual Submission
>> Pages:		3
>> URL:            =
https://www.ietf.org/internet-drafts/draft-arkko-trip-registry-update-00.t=
xt
>> Status:         =
https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/
>> Htmlized:       =
https://tools.ietf.org/html/draft-arkko-trip-registry-update-00
>> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-arkko-trip-registry-update
>>=20
>>=20
>> Abstract:
>>  This memo updates the IANA registry rules for the Telephony Routing
>>  over IP (TRIP) protocol, by no longer requiring that postal =
addresses
>>  be included in contact information.
>>=20
>>  This memo updates RFC 3219.
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From nobody Wed Jul 18 11:14:10 2018
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76EC9130EC2 for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 11:14:08 -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 8ObcO0NB90cu for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 11:14:05 -0700 (PDT)
Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (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 78EF7130E8A for <dispatch@ietf.org>; Wed, 18 Jul 2018 11:14:05 -0700 (PDT)
Received: by mail-lj1-x244.google.com with SMTP id f1-v6so3265779ljc.9 for <dispatch@ietf.org>; Wed, 18 Jul 2018 11:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=U8qS/9h+n9eu/IbI2DAqktrnE56W+rxveqromkSH9Jo=; b=Fl2N9QFdyN0PGKTBE+aMiEP0DGTuT9B31D1wLdIesOeFAaO1eecWltZCqlo4sPGs0M fCaH/8J98CnnTifsWuO/j0KGpl/LaNBi9eGOp+HO1mIuHMeqPyyB2/0oMwxMLJ5da/7t cy9qb6qjbbetusyCH0iD3NvSjXumUBb45HEQnVbKR9+33SnvOVKAddtFip+tHiDLnbda YmxDRwC4qCBJaydAxkjo0gXLJAcTkuj08vO2tyfKvd3ep2HJPJmJthicHXO1eDgFkYav i0H0Hanho0BdDLBE8xFIx6RWLxh3NWdlndAFIZQ68yZqlyU234c4nzv/hBFqgYQrmI2c aNhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=U8qS/9h+n9eu/IbI2DAqktrnE56W+rxveqromkSH9Jo=; b=ZF4zA5/GRTNdpIBYap+B0OhjOisscc7xF/WsL7p2QPuP8O4IPZD8VB75y4B+UOuAn5 o1ViYcyJQUHIHPei4a6dkRZQ+GsKzZrZm3cVzHD/9NeQNa+sb6JtcdqvEVrCMIBRe8Fx RFrq0Is06y/iAYC9WeCVL2vkDUXPRKQSCqrQll6rDb6Xqzu1Ef3mCPOJb+7lducZ4arE 454xk7k0OblnwfeUjR4Vl0hI85Rek5jD31SPRjj5xuPfC4J3nnpuJp/tAdouTdSyoW7C 4VqzNPPOMzwEkihQ9ST+KXr2YiOvRMFi/qNxl50QejGZIzFKexU+Sr/BR3H3NsZBCAdv gx8w==
X-Gm-Message-State: AOUpUlEOyGc1VyGRzchnoMvivOOhKxUdXXoNv8W73S1F8suI41wBCrPq 3yCI/qbVyCWYczU3XhgzOsqn+SKjP2OwZez3hyg=
X-Google-Smtp-Source: AAOMgpfGH9E0HvDynoOci5Uqfb4s4qk0zngDsAQPygkXA5j2fPw0+67H/GbNTinvOvzCGHYH4k08LlK3O8Sm8BaMUkA=
X-Received: by 2002:a2e:9bc9:: with SMTP id w9-v6mr5272589ljj.33.1531937643814;  Wed, 18 Jul 2018 11:14:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:8446:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 11:14:03 -0700 (PDT)
In-Reply-To: <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Wed, 18 Jul 2018 13:14:03 -0500
Message-ID: <CAHBDyN7k=+7RTdygjDX1ZBza7kMsT-=isjORMTXrkqNpJZoZVg@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: DISPATCH <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000013e53205714a0777"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/d6EUyMT4h-biy3cvAbC0QsxtVnY>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 18:14:09 -0000

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

As an individual, I agree with this proposal.  Including the addresses was
a carryover from the telecom world where all the registries required (and
still do) postal addresses.

As chair, it's probably within scope of being a WG document since it's
related to a registry.

Regards,
Mary

On Wed, Jul 18, 2018 at 9:53 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Ted and I have written a draft to update one IANA registry that
> (we think unnecessarily) calls for registering postal addresses
> for people who request code points. We think this should
> not be done for privacy, GDPR, exception at IANA, etc.
> reasons.
>
> We=E2=80=99d love to get feedback, and if there=E2=80=99s no roadblocks,
> move pretty quickly to asking the working group or the ADs
> to take the draft forward.
>
> Jari
>
> > Name:         draft-arkko-trip-registry-update
> > Revision:     00
> > Title:                Update to the TRIP IANA Registry Rules Regarding
> Postal Addresses
> > Document date:        2018-07-16
> > Group:                Individual Submission
> > Pages:                3
> > URL:            https://www.ietf.org/internet-drafts/draft-arkko-trip-
> registry-update-00.txt
> > Status:         https://datatracker.ietf.org/
> doc/draft-arkko-trip-registry-update/
> > Htmlized:       https://tools.ietf.org/html/draft-arkko-trip-registry-
> update-00
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-arkko-trip-
> registry-update
> >
> >
> > Abstract:
> >   This memo updates the IANA registry rules for the Telephony Routing
> >   over IP (TRIP) protocol, by no longer requiring that postal addresses
> >   be included in contact information.
> >
> >   This memo updates RFC 3219.
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

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

<div dir=3D"ltr">As an individual, I agree with this proposal.=C2=A0 Includ=
ing the addresses was a carryover from the telecom world where all the regi=
stries required (and still do) postal addresses.=C2=A0 =C2=A0<div><br></div=
><div>As chair, it&#39;s probably within scope of being a WG document since=
 it&#39;s related to a registry.=C2=A0=C2=A0<br><div><br></div><div>Regards=
,</div><div>Mary</div></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Wed, Jul 18, 2018 at 9:53 AM, Jari Arkko <span dir=3D"l=
tr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkk=
o@piuha.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ted and=
 I have written a draft to update one IANA registry that<br>
(we think unnecessarily) calls for registering postal addresses<br>
for people who request code points. We think this should<br>
not be done for privacy, GDPR, exception at IANA, etc. <br>
reasons.<br>
<br>
We=E2=80=99d love to get feedback, and if there=E2=80=99s no roadblocks,<br=
>
move pretty quickly to asking the working group or the ADs<br>
to take the draft forward.<br>
<br>
Jari<br>
<br>
&gt; Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-arkko-trip-registry-<wbr>=
update<br>
&gt; Revision:=C2=A0 =C2=A0 =C2=A000<br>
&gt; Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Update t=
o the TRIP IANA Registry Rules Regarding Postal Addresses<br>
&gt; Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2018-07-16<br>
&gt; Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individu=
al Submission<br>
&gt; Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3<br>
&gt; URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.i=
etf.org/internet-drafts/draft-arkko-trip-registry-update-00.txt" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/internet-<wbr>drafts/draft-=
arkko-trip-<wbr>registry-update-00.txt</a><br>
&gt; Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracke=
r.ietf.org/doc/draft-arkko-trip-registry-update/" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-arkko-trip-registry=
-<wbr>update/</a><br>
&gt; Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/=
html/draft-arkko-trip-registry-update-00" rel=3D"noreferrer" target=3D"_bla=
nk">https://tools.ietf.org/html/<wbr>draft-arkko-trip-registry-<wbr>update-=
00</a><br>
&gt; Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/html/draft-arkko-trip-registry-update" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/<wbr>doc/html/draft-arkko-trip-<wb=
r>registry-update</a><br>
&gt; <br>
&gt; <br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0This memo updates the IANA registry rules for the Telephon=
y Routing<br>
&gt;=C2=A0 =C2=A0over IP (TRIP) protocol, by no longer requiring that posta=
l addresses<br>
&gt;=C2=A0 =C2=A0be included in contact information.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0This memo updates RFC 3219.<br>
<br>
______________________________<wbr>_________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dispatch</a=
><br>
</blockquote></div><br></div>

--00000000000013e53205714a0777--


From nobody Wed Jul 18 14:05:57 2018
Return-Path: <masinter@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043C91311B8 for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 14:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=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 a7B6HLsEBvYs for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 14:05:49 -0700 (PDT)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (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 4A8CF131048 for <dispatch@ietf.org>; Wed, 18 Jul 2018 14:05:49 -0700 (PDT)
Received: by mail-pf0-x22b.google.com with SMTP id j26-v6so2766407pfi.10 for <dispatch@ietf.org>; Wed, 18 Jul 2018 14:05:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=tuxR8gAaDZ+g8NLJoacqYEbCnkwcrpDrjwUb1KZsUDo=; b=dDj0AGsCKqOoMIuJWdIpTXBszcmPO48mPMckz55+bDW2c0u2FpqWTsb7hiX3BU89s/ g+FwgM2RrQuzujsCGSwGVUMkoPLXz29uwKZ0zr1YT8S+1MHiBMOdv3hCygsnY+KGpLdm uUpn5R7xgGJgEMdoKV7nkIGFRIK1AGaApQ0ZBXaIBiwRe2wpmL3huMANSeO26nQimS0G vSocoq2tAmPNHRCZhenmB5H3aB6tSBwqdJSMBKKRFm1EcEj9S6yqkYi/SrIy7afOeJYQ 8xALjn1gAFZr9udhefkAO9uRGOsfI3KaLyEIGcRWBUaGVLjrR2INrysvh+AHe6jdv9lI kXVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=tuxR8gAaDZ+g8NLJoacqYEbCnkwcrpDrjwUb1KZsUDo=; b=Y+KKjSBfJ6TAhSoQEbDLPe6LhFDntARWM7RdChEtJHB8HhKLC9jVnR8HPsfINNdGqa aPZFyeciuoncM4BY4u9xV/HnjsLcYHakzNbXXrFRO1Y6wOsBuNm2J/JLA2Jd51ktXBmA sp85kTNSbV1xRSqOtB7Sqv5nF2lXkBuKlhYfpFNvxyjMrwLW6WmH/fMpEJbc3ZvHDfJk 8zfSdeDp0zWeh6+ingiZEpEpHaiTtgOIOYOF7fRBKpDPz1k+L0apAE56Qd8mYbDq/3Vs YZJLl5j8OnR58blBJKQZq4/Kjt/iLGGbokolrsaQiUh4dFvC2csY5VfgwPg8dzVWDfyy /cHA==
X-Gm-Message-State: AOUpUlH1lzKzjbim5+kOFV+y+0E0aO35+tKChcHhALLxUbedt9PqDq0i cDpIujqiYOKxRzYHCOxHdZz/OL6i
X-Google-Smtp-Source: AAOMgpdJWIQpkd4JEylWlSI4mIg9wUZdBxEWTg22ID9s6guelMCpXV/wOU8tW19XA9+inxS7oK4LZA==
X-Received: by 2002:a63:24c:: with SMTP id 73-v6mr7427229pgc.252.1531947948309;  Wed, 18 Jul 2018 14:05:48 -0700 (PDT)
Received: from TVPC (c-24-6-174-39.hsd1.ca.comcast.net. [24.6.174.39]) by smtp.gmail.com with ESMTPSA id i20-v6sm8282096pfj.82.2018.07.18.14.05.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Jul 2018 14:05:46 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Cullen Jennings'" <fluffy@iii.ca>, "'Jari Arkko'" <jari.arkko@piuha.net>
Cc: <dispatch@ietf.org>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net> <595F209B-CC6A-4D91-A8F5-DFA3B95CD83B@iii.ca>
In-Reply-To: <595F209B-CC6A-4D91-A8F5-DFA3B95CD83B@iii.ca>
Date: Wed, 18 Jul 2018 14:05:45 -0700
Message-ID: <000001d41edb$18f7ef80$4ae7ce80$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHUHqcbuSLltaTUjEa1eYTOxLn5paSVGLSAgAAgIcA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/mzNznpqARFi8oDVjex_JkUAyCEg>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 21:05:53 -0000

Postal addresses should be part of "information about the organization =
that will administer the ITAD" (RFC 3219 Section 13.5).  What is the =
privacy benefit for such an organization to not reveal its postal =
address, if it has one?

TRIP Attributes requires a Specification ("RFC or equivalent"), which =
have authors, who often provide a postal address in their contact info. =
So what is the privacy benefit for those registering the type?

In general, you have to trade off privacy vs. security and robustness of =
process. For example, the successful use of "NOTE WELL" notices rather =
than explicit consortia-membership agreements depends to some degree on =
the ability to connect a posting to a registry to an individual who =
agrees to be bound by the terms in NOTE WELL. (Otherwise, what's the =
point?)

Why is address useful? Hard to make up new ones, and gives a clue about =
jurisdiction of the contributor.

To those reviewing IETF RFCs for unneeded use of addresses: consider =
this in your evaluation of postal or physical address privacy issues.=20

Larry
--
https://LarryMasinter.net



From nobody Wed Jul 18 14:34:34 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F814131066 for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 14:34:32 -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 YxfTcEFNc4WX for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 14:34:29 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 5C533130DEB for <dispatch@ietf.org>; Wed, 18 Jul 2018 14:34:29 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id q11-v6so11576635oic.12 for <dispatch@ietf.org>; Wed, 18 Jul 2018 14:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Z5Buv8HAJmQe1vNnrFdaUFZlCWTIGMtBO7hl07Anssc=; b=NwQdN/5Im44K4fo2X2IRWzW9SyHfWFgXd+o3A9mspfrowKAqq4ivdTTHPQcxpuAPFZ IUZQDRDCQQZ2bvJQ48zRGNwLCQb/CYrLwovEpmSc3TY5KTf5VuP3n/+UTkf2UbkVeGPE 7X07FGDYJBvtXmNnMsZ59VCr+4nJuR+eWRi45INP3UWnAeWZd3xzyCNdmxgiv7+l4vbj 3+u08pRS/5WPDpaotwCZfcJq5qgUwn32cRFZRjJUF8QpzYrCB0uvSUgDsGATXSZRjMVi 34gAMpiGHrkBKWCQAnTue7+D/YRvdqx8dzmR83D03ixNa1jH1cTnlrThSaFF068Ap8sC xnfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Z5Buv8HAJmQe1vNnrFdaUFZlCWTIGMtBO7hl07Anssc=; b=X4Zn3mpa+UQDA+Zv3kN5yG+594Hvmd4Dw/nn63Ypj1xzBM86iXAVr5aRxu71naP6al ByVVm6iIgTXOzPpB6ytlCyA+lza5D9ZxuAC1y0qzU0VUj8TlYZgUNdlkcCEQ3Tv6eKAL 7kuVtTnfyAbI9Y40mCxfSIoEYmCX3YyjLDHz/czjLbCf7BQGGDQglzp6hD8x6zvuMofK 0FCa8ibD6Cw898GHIkctbczSUyDDRHkfZEO+2YZrVR8is7UsmdDL4kBCCtbvLC4jTTsE Gz/WgBTww9h1I/nvYg/XgJ8wTR/kjubL5QPJlzFOLHLtNJ8NvxqFs1b+Cb+Cow9E/+ig yLJw==
X-Gm-Message-State: AOUpUlHjZyUK885fOx86r0v+jrIviL0+HqgzcTzcrHy2Nqbf74CjcJYw Qokygx2xmIWnXM87MQbGx+X+JW3Pi6EJ5zf1tlI=
X-Google-Smtp-Source: AAOMgpeKcwvCQqLFs6Rl+Py1vjw2a4EyUNLquFonm4moD+/UpXyIvPrfs5giZrwrv6rrNB/Slndc+o7bIeH8T30oj8A=
X-Received: by 2002:aca:2c83:: with SMTP id s125-v6mr4629037ois.103.1531949668404;  Wed, 18 Jul 2018 14:34:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 14:33:57 -0700 (PDT)
In-Reply-To: <000001d41edb$18f7ef80$4ae7ce80$@acm.org>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net> <595F209B-CC6A-4D91-A8F5-DFA3B95CD83B@iii.ca> <000001d41edb$18f7ef80$4ae7ce80$@acm.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 18 Jul 2018 17:33:57 -0400
Message-ID: <CA+9kkMCWuZA_FEm6GxT42mKCWDZLS9xAM5uK2_iyEp1Es3udaw@mail.gmail.com>
To: Larry Masinter <LMM@acm.org>
Cc: Cullen Jennings <fluffy@iii.ca>, Jari Arkko <jari.arkko@piuha.net>, dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cc9af305714cd311"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/0SsC_jl2K9atDBz5XpObyBsEKfc>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 21:34:33 -0000

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

Hi Larry,

On Wed, Jul 18, 2018 at 5:05 PM, Larry Masinter <LMM@acm.org> wrote:

> Postal addresses should be part of "information about the organization
> that will administer the ITAD" Section 13.5)
>

That's the section of RFC 3219 that this draft modifies, and that's why it
is listed as updating the RFC.


> .  What is the privacy benefit for such an organization to not reveal its
> postal address, if it has one?
>
>
I think our thinking is more-or-less the reverse of this:  what public
benefit is publication of this data serving?  In the case of this registry,
the use of this data did not require the postal address at all, and the
electronic contact information is also available.  Continuing to collect it
when it is not used seems to be un-needed.


> TRIP Attributes requires a Specification ("RFC or equivalent"), which have
> authors, who often provide a postal address in their contact info. So what
> is the privacy benefit for those registering the type?
>
> ITAD numbers don't actually require this, but are first come first served,
requiring only completing a form:

https://www.iana.org/form/trip-itad

regards,

Ted Hardie

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

<div dir=3D"ltr">Hi Larry,<br><div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Wed, Jul 18, 2018 at 5:05 PM, Larry Masinter <span dir=
=3D"ltr">&lt;<a href=3D"mailto:LMM@acm.org" target=3D"_blank">LMM@acm.org</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">P=
ostal addresses should be part of &quot;information about the organization =
that will administer the ITAD&quot; Section 13.5)<br></blockquote><div><br>=
</div><div>That&#39;s the section of RFC 3219 that this draft modifies, and=
 that&#39;s why it is listed as updating the RFC.<br></div><div>=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"> .=C2=A0 What is the pri=
vacy benefit for such an organization to not reveal its postal address, if =
it has one?<br>
<br></blockquote><div><br></div><div>I think our thinking is more-or-less t=
he reverse of this:=C2=A0 what public benefit is publication of this data s=
erving?=C2=A0 In the case of this registry, the use of this data did not re=
quire the postal address at all, and the electronic contact information is =
also available.=C2=A0 Continuing to collect it when it is not used seems to=
 be un-needed.<br></div><div>=C2=A0</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">
TRIP Attributes requires a Specification (&quot;RFC or equivalent&quot;), w=
hich have authors, who often provide a postal address in their contact info=
. So what is the privacy benefit for those registering the type?<br>
<br></blockquote><div>ITAD numbers don&#39;t actually require this, but are=
 first come first served, requiring only completing a form:</div><div><br><=
/div><div><a href=3D"https://www.iana.org/form/trip-itad" target=3D"_blank"=
>https://www.iana.org/form/<wbr>trip-itad</a><br></div><div>=C2=A0</div><di=
v>regards,</div><div><br></div><div>Ted Hardie<br></div></div></div></div><=
/div>

--000000000000cc9af305714cd311--


From nobody Wed Jul 18 17:15:28 2018
Return-Path: <sm@elandsys.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D34B131207 for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 17:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.78
X-Spam-Level: 
X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=TjEVRUhO; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=InDjonWu
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 Q1da6_uij19t for <dispatch@ietfa.amsl.com>; Wed, 18 Jul 2018 17:15:24 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B5F1310D1 for <dispatch@ietf.org>; Wed, 18 Jul 2018 17:15:24 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.148.198]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id w6J0FD1V000269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Jul 2018 17:15:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1531959323; x=1532045723; bh=Ic08iyhzQM21+H8UZxWMev8AFp2++0TZdCJvhi65SkY=; h=Date:To:From:Subject:In-Reply-To:References; b=TjEVRUhOAKbcEC9ju9XfLp7/VFhivqmpxWbNpmA0/UDhlxKLlVxES5d455ATzeeON xtg7NarIPUBawD4S50vkumct8jTj1LPC5+AKKEaj0wKROXMJYIoy+0kQwcg53dO6JK fc5pFwJgs2O2lezpu3rmaqBI+6+JvU2qslR9/Wp8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1531959323; x=1532045723; i=@elandsys.com; bh=Ic08iyhzQM21+H8UZxWMev8AFp2++0TZdCJvhi65SkY=; h=Date:To:From:Subject:In-Reply-To:References; b=InDjonWui6D4uzaj3Ux/B7JdTkUONwuprppEiQHh0gotAmmfq5fGeJfCehmf3y+kE PFEUOgA9uhKLz3xceVOSejenScams5ut7g2mbHFfwC2/t6ngrIhWnWzmeg6rZzDcMa tEmZn1FWFDwRCFnm9MVKugCcaG/f/YwwYSbDEeYc=
Message-Id: <6.2.5.6.2.20180718171158.132b4da0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 18 Jul 2018 17:14:44 -0700
To: Jari Arkko <jari.arkko@piuha.net>, dispatch@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAHBDyN7k=+7RTdygjDX1ZBza7kMsT-=isjORMTXrkqNpJZoZVg@mail.g mail.com>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net> <CAHBDyN7k=+7RTdygjDX1ZBza7kMsT-=isjORMTXrkqNpJZoZVg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CBrVj8UH7Cilj9tK1kT0tYdhnp8>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 00:15:26 -0000

Hi Jari,
At 11:14 AM 18-07-2018, Mary Barnes wrote:
>As an individual, I agree with this=20
>proposal.=C2  Including the addresses was a=20
>carryover from the telecom world where all the=20
>registries required (and still do) postal addresses.

The Introduction Section mentions "privacy=20
benefit" with respect to postal addresses.  If I=20
understood corectly, the issue is about=20
PII.  Should both postal and email addresses be=20
considered instead of postal addresses only?

Regards,
S. Moonesamy


From nobody Wed Jul 18 21:17:26 2018
Return-Path: <masinter@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6486130EEC; Wed, 18 Jul 2018 21:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=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 ym3M_QScdEwF; Wed, 18 Jul 2018 21:17:22 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 BAC20130E6F; Wed, 18 Jul 2018 21:17:22 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id r1-v6so2977070pgp.11; Wed, 18 Jul 2018 21:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=wdDbD990zSxIaJ5hsiJkTfNI5U2aQrnZEOZYz+YIwUI=; b=G/QBgWEsmokYJYNhGSSF+fTH5AUaz/6qtyg9Gr/cgoqCDF2sBeGO4EN1FvHCOAA76C FayaKEX4yXqyoMnJST5qJ/f4HjNtzaFh08+7GxrrOMjnqQGmzfrhTStZKxZhHPS+v9Op OwqYy7khFKNmKC8QypOph9WHKGiKGTHpqWWIa6dYnbJBPpe5jwWY5tiJIYj19bjNL4F7 MFRBHaeV5gcJNK9oa5+s26Or8BdH5n0B5I9aWvecvCYW6xJ1k4fOGcFKrt9gTMJcZIy5 JP5oTrJJU1Bc3OPkMLA3YKFl/Z37h0Yj5mkWOjt0cHLd7cpBz1bpZ/0ZLm0Kcvy5GjRV 9HRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:thread-index:content-language; bh=wdDbD990zSxIaJ5hsiJkTfNI5U2aQrnZEOZYz+YIwUI=; b=hJhnJ2Yu6OrsYiioiiaRNnvVgLSH8MJgukOHxasZTL8Vx0mhXJ3h8p1xqhQSXgI7Ii S0fNbQ3RsabxEimA0eu7xCfEFpQyKuezmB4aD/rtp/H5aIDf+4VALz4zZlGeY2BSRjwp rQqaiy9cgN7IQs2sp8CUSz1tUjb5bAO2pIbTanasCfjchNXCRVXyNogdKKPZRl2C2EZm xetwb14rB8k6RScNNZMzieI1pjQC/zyljV5FplSCdxGZ+N8DYbGbSkvzAwmUoIoI+yv9 rebQyxi6PmqRR8YLHfI6KphCb6GJnNCD3MkKC5i2BNvM2H2nAdgIQWwi5yZIYD3fB6cK KSzA==
X-Gm-Message-State: AOUpUlG6UnvFFH/t6UIxfwxgf/VZZIMig91M65sn9zayvhkYNx2MMcJN 4L4o8br5MqBpoiGY1O2CzxI=
X-Google-Smtp-Source: AAOMgpcyTWSN02WJOqFKJjkLBPnrYraEmgEB1bptSzlHeL9SGvr4H8h5VKWCLtIIbLs0l4pGF3eOoQ==
X-Received: by 2002:a63:4924:: with SMTP id w36-v6mr8457657pga.143.1531973842302;  Wed, 18 Jul 2018 21:17:22 -0700 (PDT)
Received: from TVPC (c-24-6-174-39.hsd1.ca.comcast.net. [24.6.174.39]) by smtp.gmail.com with ESMTPSA id z9-v6sm8034697pfi.150.2018.07.18.21.17.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Jul 2018 21:17:20 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Bradley Meck'" <bradley.meck@gmail.com>, <LMM@acm.org>
Cc: "'DISPATCH'" <dispatch@ietf.org>, <draft-ietf-dispatch-javascript-mjs@ietf.org>
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com> <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com> <000001d41dd8$a2ad12e0$e80738a0$@acm.org> <CANnEKUZCyb29-_e-6FKrqM0vbJyiZkOSuFj_0GZAq5ve4H=wFg@mail.gmail.com>
In-Reply-To: <CANnEKUZCyb29-_e-6FKrqM0vbJyiZkOSuFj_0GZAq5ve4H=wFg@mail.gmail.com>
Date: Wed, 18 Jul 2018 21:17:19 -0700
Message-ID: <00a501d41f17$63233e70$2969bb50$@acm.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A6_01D41EDC.B6C4DBA0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHUGjwIgZSPI+/PLkuVU40cEzx4fKSTcM7agAAOsgCAAADVUA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/fiZ2Q3eu4sE0zuWiQ8bKE0F-p_g>
Subject: Re: [dispatch] Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 04:17:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A6_01D41EDC.B6C4DBA0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I was hoping to avoid stuffing the MIME registry with (and making =
everyone review) lots of useless obsolete templates; the use of OBSOLETE =
in =E2=80=9CIntended use=E2=80=9D should only be for previously =
registered types. Not new (dubious) registrations.

=20

Sent: Tuesday, July 17, 2018 7:25 AM
To: LMM@acm.org
Cc: DISPATCH <dispatch@ietf.org>; =
draft-ietf-dispatch-javascript-mjs@ietf.org
Subject: Re: [dispatch] Fwd: WGLC: =
draft-ietf-dispatch-javascript-mjs-02.txt

=20

Per https://github.com/bmeck/I-D/issues/2

=20

The extra registrations are to match up with the Web specification on =
accepted MIME types for historical reasons =
https://mimesniff.spec.whatwg.org/#javascript-mime-type

=20

On Tue, Jul 17, 2018 at 9:15 AM Larry Masinter <LMM@acm.org =
<mailto:LMM@acm.org> > wrote:

=E2=9E=A2 Only `text/javascript` is not obsolete per =
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages =
<https://html.spec..whatwg.org/multipage/scripting.html#scriptingLanguage=
s> =20

I wonder about the utility of newly registering (or updating the =
registration) of types that are obsolete.
If there=E2=80=99s significant deployment of names that new =
implementations need to be aware of, then =E2=80=98obsolete=E2=80=99 =
isn=E2=80=99t the right status; if not, then who would use the new, but =
obsolete, definition?

Larry
http://LarryMasinter.net






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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-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:"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;}
@font-face
	{font-family:"Segoe UI Symbol";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* 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:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I was =
hoping to avoid stuffing the MIME registry with (and making everyone =
review) lots of useless obsolete templates; the use of OBSOLETE in =
=E2=80=9CIntended use=E2=80=9D should only be for previously registered =
types. Not new (dubious) registrations.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><b>Sent:</b> =
Tuesday, July 17, 2018 7:25 AM<br><b>To:</b> LMM@acm.org<br><b>Cc:</b> =
DISPATCH &lt;dispatch@ietf.org&gt;; =
draft-ietf-dispatch-javascript-mjs@ietf.org<br><b>Subject:</b> Re: =
[dispatch] Fwd: WGLC: =
draft-ietf-dispatch-javascript-mjs-02.txt<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Per&nbsp;<a =
href=3D"https://github.com/bmeck/I-D/issues/2">https://github.com/bmeck/I=
-D/issues/2</a><o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The extra registrations are to match up with the Web =
specification on accepted MIME types for historical reasons&nbsp;<a =
href=3D"https://mimesniff.spec.whatwg.org/#javascript-mime-type">https://=
mimesniff.spec.whatwg.org/#javascript-mime-type</a><o:p></o:p></p></div><=
/div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>On Tue, Jul 17, 2018 at 9:15 AM Larry Masinter &lt;<a =
href=3D"mailto:LMM@acm.org">LMM@acm.org</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5=
.0pt'><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-family:"Segoe UI Symbol",sans-serif'>=E2=9E=A2</span> Only =
`text/javascript` is not obsolete per <a =
href=3D"https://html.spec..whatwg.org/multipage/scripting.html#scriptingL=
anguages" =
target=3D"_blank">https://html.spec.whatwg.org/multipage/scripting.html#s=
criptingLanguages</a> <br><br>I wonder about the utility of newly =
registering (or updating the registration) of types that are =
obsolete.<br>If there=E2=80=99s significant deployment of names that new =
implementations need to be aware of, then =E2=80=98obsolete=E2=80=99 =
isn=E2=80=99t the right status; if not, then who would use the new, but =
obsolete, definition?<br><br>Larry<br><a =
href=3D"http://LarryMasinter.net" =
target=3D"_blank">http://LarryMasinter.net</a><br><br><br><br><o:p></o:p>=
</p></blockquote></div></div></body></html>
------=_NextPart_000_00A6_01D41EDC.B6C4DBA0--


From nobody Thu Jul 19 06:02:19 2018
Return-Path: <bradley.meck@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69129130DE0; Thu, 19 Jul 2018 06:02:17 -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 eR4xtARelWDb; Thu, 19 Jul 2018 06:02:15 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 18FF91277CC; Thu, 19 Jul 2018 06:02:15 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id q9-v6so6967793ioj.8; Thu, 19 Jul 2018 06:02:15 -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=CNUf4YyycZEOpGBl/5ZPjPCdkadLQnVnGQfIujWiwls=; b=R1p4ghHkEIZk52qA7r7HnpReQyxheTRAlRS9JtAorKm+qDgI+hxK1MWSvZeLiJF8Pt LSbPsuA1esqyJ6rgWrT5m8CS9Lo6UpX8yghSo/LeHgkO6pdMhuOrhQ3cL12z7Ono4/mn hqsWkZhnKq4oBMuzxayZ2WFscLGCIdy8z6hkbZfJClJ3+9OgZMQoptG6AzoPKdSr4lc9 +tPUSfoNAXoEon7uL2HIsTpMIspt/ntZjL3OENYhGGQSnd7U7HbEQRNjEj+iiPTnzy3S Uw7AsyYQ6OHUg+fC36+F2vo/2VC7GKbcmkGc/jCWoQqiBdabwHD/IGFY2YDxkprmNka3 q7wQ==
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=CNUf4YyycZEOpGBl/5ZPjPCdkadLQnVnGQfIujWiwls=; b=sOrQroc8qEUjO+3K7e6X+dLHYJGaiJzpgvZ5zJOf08aBTpsbCNayNZFxC587sQCUqi 3c/dYGWgxXiAyvNt2VeJQw3bfdSy+NkOPvh5eQw9v55mukvtEE/bc9tphS4SNdtdPnCM 5U0VXspB4SGXAz+1Pc1IjMJgONjMUy23eexbCbWyLMF3CWhnLZmuiPdXNbCbcO2T6v+L mmG4d3UgI2e5EBRKl6G+0F5468LApq73qa/tQFOg7WMcWWq3UzViGQ4qhrGnpjwi5/yq eUW/HiXts48AFDgIANttsV5VceJXEAMYiOZlEYJsaOJnTW/kgYszgHl/EJUxOJlGs4vj twSA==
X-Gm-Message-State: AOUpUlG15fOpvI+VI9dPgfQ8iFbVW4CXk/wVLX9h+Hduf09AJg154x1P sptdNfyx+V/CdABfxtZ6TPo08RSHdilPn0LlCZleMw==
X-Google-Smtp-Source: AA+uWPzES69C2MyHtozlEiexLJjX7l6G3Z9RlfhtRfOuHGiu6oL1ryCiTaLbYrFkS+fzgesf69X2meKagjLUoAik9lo=
X-Received: by 2002:a6b:2614:: with SMTP id m20-v6mr8204663iom.211.1532005334353;  Thu, 19 Jul 2018 06:02:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com> <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com> <000001d41dd8$a2ad12e0$e80738a0$@acm.org> <CANnEKUZCyb29-_e-6FKrqM0vbJyiZkOSuFj_0GZAq5ve4H=wFg@mail.gmail.com> <00a501d41f17$63233e70$2969bb50$@acm.org>
In-Reply-To: <00a501d41f17$63233e70$2969bb50$@acm.org>
From: Bradley Meck <bradley.meck@gmail.com>
Date: Thu, 19 Jul 2018 08:02:04 -0500
Message-ID: <CANnEKUZA7YWVhDGV7t5LescEivOoNWq3sbasXuJtd9orwHrj=g@mail.gmail.com>
To: Larry Masinter <LMM@acm.org>
Cc: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bf8b9d057159c9d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/YzdMxH6m4ilr1Dv3tliXW-vFA9A>
Subject: Re: [dispatch] Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 13:02:18 -0000

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

I think reflecting reality is important, is the only concern the number of
types / review time? Should that be split into a separate RFC to add all
the obsolete types so that it can take more time to land all of those.
Regardless of intent, there MIMEs are in use and part of the web standards
used by browsers. Having them documented/registered seems important if the
MIME registry is intended to reflect actual usage.

On Wed, Jul 18, 2018 at 11:17 PM Larry Masinter <LMM@acm.org> wrote:

> I was hoping to avoid stuffing the MIME registry with (and making everyon=
e
> review) lots of useless obsolete templates; the use of OBSOLETE in
> =E2=80=9CIntended use=E2=80=9D should only be for previously registered t=
ypes. Not new
> (dubious) registrations.
>
>
>
> *Sent:* Tuesday, July 17, 2018 7:25 AM
> *To:* LMM@acm.org
> *Cc:* DISPATCH <dispatch@ietf.org>;
> draft-ietf-dispatch-javascript-mjs@ietf.org
> *Subject:* Re: [dispatch] Fwd: WGLC:
> draft-ietf-dispatch-javascript-mjs-02.txt
>
>
>
> Per https://github.com/bmeck/I-D/issues/2
>
>
>
> The extra registrations are to match up with the Web specification on
> accepted MIME types for historical reasons
> https://mimesniff.spec.whatwg.org/#javascript-mime-type
>
>
>
> On Tue, Jul 17, 2018 at 9:15 AM Larry Masinter <LMM@acm.org> wrote:
>
> =E2=9E=A2 Only `text/javascript` is not obsolete per
> https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages
> <https://html.spec..whatwg.org/multipage/scripting.html#scriptingLanguage=
s>
>
> I wonder about the utility of newly registering (or updating the
> registration) of types that are obsolete.
> If there=E2=80=99s significant deployment of names that new implementatio=
ns need
> to be aware of, then =E2=80=98obsolete=E2=80=99 isn=E2=80=99t the right s=
tatus; if not, then who
> would use the new, but obsolete, definition?
>
> Larry
> http://LarryMasinter.net
>
>
>
>

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

<div dir=3D"ltr">I think reflecting reality is important, is the only conce=
rn the number of types / review time? Should that be split into a separate =
RFC to add all the obsolete types so that it can take more time to land all=
 of those. Regardless of intent, there MIMEs are in use and part of the web=
 standards used by browsers. Having them documented/registered seems import=
ant if the MIME registry is intended to reflect actual usage.</div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Jul 18, 2018 at 11:17 PM La=
rry Masinter &lt;<a href=3D"mailto:LMM@acm.org">LMM@acm.org</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" v=
link=3D"purple"><div class=3D"m_2647529920265590543WordSection1"><p class=
=3D"MsoNormal">I was hoping to avoid stuffing the MIME registry with (and m=
aking everyone review) lots of useless obsolete templates; the use of OBSOL=
ETE in =E2=80=9CIntended use=E2=80=9D should only be for previously registe=
red types. Not new (dubious) registrations.<u></u><u></u></p><p class=3D"Ms=
oNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal"><b>Sent:</b> Tuesda=
y, July 17, 2018 7:25 AM<br><b>To:</b> <a href=3D"mailto:LMM@acm.org" targe=
t=3D"_blank">LMM@acm.org</a><br><b>Cc:</b> DISPATCH &lt;<a href=3D"mailto:d=
ispatch@ietf.org" target=3D"_blank">dispatch@ietf.org</a>&gt;; <a href=3D"m=
ailto:draft-ietf-dispatch-javascript-mjs@ietf.org" target=3D"_blank">draft-=
ietf-dispatch-javascript-mjs@ietf.org</a><br><b>Subject:</b> Re: [dispatch]=
 Fwd: WGLC: draft-ietf-dispatch-javascript-mjs-02.txt<u></u><u></u></p><p c=
lass=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal">Per=
=C2=A0<a href=3D"https://github.com/bmeck/I-D/issues/2" target=3D"_blank">h=
ttps://github.com/bmeck/I-D/issues/2</a><u></u><u></u></p><div><p class=3D"=
MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">The ex=
tra registrations are to match up with the Web specification on accepted MI=
ME types for historical reasons=C2=A0<a href=3D"https://mimesniff.spec.what=
wg.org/#javascript-mime-type" target=3D"_blank">https://mimesniff.spec.what=
wg.org/#javascript-mime-type</a><u></u><u></u></p></div></div><p class=3D"M=
soNormal"><u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal">On Tue, =
Jul 17, 2018 at 9:15 AM Larry Masinter &lt;<a href=3D"mailto:LMM@acm.org" t=
arget=3D"_blank">LMM@acm.org</a>&gt; wrote:<u></u><u></u></p></div><blockqu=
ote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0i=
n 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5=
.0pt"><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"=
font-family:&quot;Segoe UI Symbol&quot;,sans-serif">=E2=9E=A2</span> Only `=
text/javascript` is not obsolete per <a href=3D"https://html.spec..whatwg.o=
rg/multipage/scripting.html#scriptingLanguages" target=3D"_blank">https://h=
tml.spec.whatwg.org/multipage/scripting.html#scriptingLanguages</a> <br><br=
>I wonder about the utility of newly registering (or updating the registrat=
ion) of types that are obsolete.<br>If there=E2=80=99s significant deployme=
nt of names that new implementations need to be aware of, then =E2=80=98obs=
olete=E2=80=99 isn=E2=80=99t the right status; if not, then who would use t=
he new, but obsolete, definition?<br><br>Larry<br><a href=3D"http://LarryMa=
sinter.net" target=3D"_blank">http://LarryMasinter.net</a><br><br><br><br><=
u></u><u></u></p></blockquote></div></div></div></blockquote></div>

--000000000000bf8b9d057159c9d8--


From nobody Thu Jul 19 06:21:49 2018
Return-Path: <mnot@mnot.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63FF7129619; Thu, 19 Jul 2018 06:21:47 -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=pdHkvGKp; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HRRXXPhm
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 3nFceGzSslNR; Thu, 19 Jul 2018 06:21:45 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB2E130DDB; Thu, 19 Jul 2018 06:21:44 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 310A621BCA; Thu, 19 Jul 2018 09:21:44 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 19 Jul 2018 09:21:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=Hurt23YyZY9uy0jLgWoA1AXiJHUT7 MLiNPSAugKTgOg=; b=pdHkvGKpirILwSDaqJXeeh+q0flkitVhZ+cH7LjXWuCBQ CnUHfPDsOo4y7lqlChCMpyFM1XEawwxMlzkeuWSVTuUpUMKXeP5/GKEJubucn+rU 40+Et/UyKnHBZ2+SRd8/vBKmmYcp9UYjNLLcVRnPALFTG9XXZ9VCESqOWVkYN4El JmmjodQeH9PoUh9pnbrlOwG5HbZ3Sc4mUGLLFjjTHnp+pEbfmO1LcxJLiPle4YNd oBc2qn52nsHb3Mm7UhLYOBh57NeAWbp55Vrbssg4JuQRnXw70A6xiT7L8xPTOEUZ Yk5ysrLfjduTb2d6UBsRIqnIrdgAqbLmlB6db9QtA==
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-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Hurt23 YyZY9uy0jLgWoA1AXiJHUT7MLiNPSAugKTgOg=; b=HRRXXPhmm1Wct6lKxcbOme mwwPgp3/hKuQGagWV26F1hFXw9gz2wG2hcJ9CbTiqeCyWM++pgF1Vnw1j5s/KbzM 2Wwt4oJ0ThD2eNXVJkmf7yCmQVyizDsKHIifF25h1dl3Kf4iU9qG5J5/fn1uM8/O 2g/UtGAgLrtr4ibqS2qIhSnDLv/1djVi1oBmO7aRmkwi/okNZIobrHqhOXo5MVel 6nv2axVtIHm+vJ0t85EssQTecHsPpGOBGtsLhUuJb46lA3L+4B+kxXbWzh6urNAX sugzt0SQdPhkd91AalIQDo6dX9L05Id0U3NBuCGmIR1Kamukwvel3y+1orpYfdoA ==
X-ME-Proxy: <xmx:Z5BQW0sJa4_NuvuwJDFhQ798K_ezUry1F0O9SHcmSDw9xRq_41uumQ> <xmx:Z5BQW8JjqhaQ2JpjSp8tVycl0-u5-_neBzix3pxQWOayGWJZqic2mQ> <xmx:Z5BQW8MmhVxeAhbkrkHbxKCRDFcsV1bAo0HtX5lZU3IMlJx1BMNtYw> <xmx:Z5BQW9OFGYUksBdNtikj6zUiae_z__bSok9Ej300BEYn9GucWhwzfA> <xmx:Z5BQWwFGtTJ66HnvDMPVf9--eQnhnP7Sz0Y0qCNe2dze-_wUEZPkmQ> <xmx:aJBQW2ZWVdG-BNyGV-_JvdfYl9oNXYqDMnYqg1bpfwwPiTXRlYTAyw>
X-ME-Sender: <xms:Z5BQW7E1KQTh6EGuAvNYPcAalf6murjT_AxfMjeR7XRBqbKIWtsBLQ>
Received: from dhcp-873a.meeting.ietf.org (dhcp-873a.meeting.ietf.org [31.133.135.58]) by mail.messagingengine.com (Postfix) with ESMTPA id 58FD310268; Thu, 19 Jul 2018 09:21:43 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CANnEKUZA7YWVhDGV7t5LescEivOoNWq3sbasXuJtd9orwHrj=g@mail.gmail.com>
Date: Thu, 19 Jul 2018 09:21:42 -0400
Cc: Larry Masinter <LMM@acm.org>, DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC9E582B-2539-4678-AE47-3FF005D024EA@mnot.net>
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com> <CABkgnnXEbYtc7VKisvyTEAiTbteQPT=gXF9HY=VgeSrSCo7FCg@mail.gmail.com> <CANnEKUaUuRQ5NrLafcg_BtVKTdf+NNgDUEfn0h2oWh4R1F6+xw@mail.gmail.com> <CANnEKUbBY4XsFsR_-zP1v_PJnav6mhtFUBC5YOGt1OrzNNSzew@mail.gmail.com> <CABkgnnWnhoW8Om9DKgiTXMcC466d9y_4zDy0newrb5LFWqO47Q@mail.gmail.com> <000001d41dd8$a2ad12e0$e80738a0$@acm.org> <CANnEKUZCyb29-_e-6FKrqM0vbJyiZkOSuFj_0GZAq5ve4H=wFg@mail.gmail.com> <00a501d41f17$63233e70$2969bb50$@acm.org> <CANnEKUZA7YWVhDGV7t5LescEivOoNWq3sbasXuJtd9orwHrj=g@mail.gmail.com>
To: Bradley Meck <bradley.meck@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/YdpmEnF9qm70ypGxWDCd_VMN2Ng>
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 13:21:48 -0000

+1. There's confusion about their status; the registry is the right =
place to set the record straight.



> On 19 Jul 2018, at 9:02 am, Bradley Meck <bradley.meck@gmail.com> =
wrote:
>=20
> I think reflecting reality is important, is the only concern the =
number of types / review time? Should that be split into a separate RFC =
to add all the obsolete types so that it can take more time to land all =
of those. Regardless of intent, there MIMEs are in use and part of the =
web standards used by browsers. Having them documented/registered seems =
important if the MIME registry is intended to reflect actual usage.
>=20
> On Wed, Jul 18, 2018 at 11:17 PM Larry Masinter <LMM@acm.org> wrote:
> I was hoping to avoid stuffing the MIME registry with (and making =
everyone review) lots of useless obsolete templates; the use of OBSOLETE =
in =E2=80=9CIntended use=E2=80=9D should only be for previously =
registered types. Not new (dubious) registrations.
>=20
> =20
>=20
> Sent: Tuesday, July 17, 2018 7:25 AM
> To: LMM@acm.org
> Cc: DISPATCH <dispatch@ietf.org>; =
draft-ietf-dispatch-javascript-mjs@ietf.org
> Subject: Re: [dispatch] Fwd: WGLC: =
draft-ietf-dispatch-javascript-mjs-02.txt
>=20
> =20
>=20
> Per https://github.com/bmeck/I-D/issues/2
>=20
> =20
>=20
> The extra registrations are to match up with the Web specification on =
accepted MIME types for historical reasons =
https://mimesniff.spec.whatwg.org/#javascript-mime-type
>=20
> =20
>=20
> On Tue, Jul 17, 2018 at 9:15 AM Larry Masinter <LMM@acm.org> wrote:
>=20
> =E2=9E=A2 Only `text/javascript` is not obsolete per =
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages=20=

>=20
> I wonder about the utility of newly registering (or updating the =
registration) of types that are obsolete.
> If there=E2=80=99s significant deployment of names that new =
implementations need to be aware of, then =E2=80=98obsolete=E2=80=99 =
isn=E2=80=99t the right status; if not, then who would use the new, but =
obsolete, definition?
>=20
> Larry
> http://LarryMasinter.net
>=20
>=20
>=20
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

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


From nobody Thu Jul 19 10:38:56 2018
Return-Path: <jdrosen@jdrosen.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F287A1310D5 for <dispatch@ietfa.amsl.com>; Thu, 19 Jul 2018 10:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=jdrosen.net
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 gYKONXjjm4Hn for <dispatch@ietfa.amsl.com>; Thu, 19 Jul 2018 10:38:45 -0700 (PDT)
Received: from ecbiz193.inmotionhosting.com (ecbiz193.inmotionhosting.com [67.199.146.193]) (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 AFDA2130FA6 for <dispatch@ietf.org>; Thu, 19 Jul 2018 10:38:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jdrosen.net ; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=E1b2k3sjZGzd/16L92v4FJcY0utREEujk77nd028+8c=; b=iRZLUTu1a7+lJ3zvv3rfd1fX3E xOHHofRhKWKhHke/Jo0mBD4fBxr59VTwvXn63k8h83Bt5ajm6j4XWQo4k9Fk83x2xkYxKAcrbMAnr m3D15SYeXupBPBd4C87PHGMjGtSQANaBSuaqwqaGYxlGFni18zGHzudKP2eGbRI5/zaotdXLUthmu zVJwz72sGgkT7W57EDlcZAQw11JrEc1RVR5l1oDA9cIWkmFz3awjCAqISuZOs97itEzDQu1rmtzL5 G6xOYbKvknLf1SStNbRBM3Nm75UV8WnGUuvMwXNyRebIxHbhff+0c0py7qeinRn15aj2f11QTwn3B v71XO0eQ==;
Received: from mail-oi0-f51.google.com ([209.85.218.51]:40127) by ecbiz193.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <jdrosen@jdrosen.net>) id 1fgCsq-00BLY0-Fo for dispatch@ietf.org; Thu, 19 Jul 2018 13:38:44 -0400
Received: by mail-oi0-f51.google.com with SMTP id w126-v6so16451247oie.7 for <dispatch@ietf.org>; Thu, 19 Jul 2018 10:38:32 -0700 (PDT)
X-Gm-Message-State: AOUpUlHCMinHThlPZigD5G9CFWoWNEecXoBuSm8smxkz/vBNSyTn32Qm EWAB1zpmqTbmFhZccY2dPIi+oDAVBuUltJ0Lvm4=
X-Google-Smtp-Source: AAOMgpcEQKQ8/RLydmiwc1QXuPzrbAxNz2r+uf42aoUTe1o4TzzFY3VC/hjj8S98HJJOfIbtwxptmOAPMvMrn3FpnjE=
X-Received: by 2002:aca:6a48:: with SMTP id f69-v6mr12511423oic.279.1532021912153;  Thu, 19 Jul 2018 10:38:32 -0700 (PDT)
MIME-Version: 1.0
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
In-Reply-To: <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Thu, 19 Jul 2018 13:38:20 -0400
X-Gmail-Original-Message-ID: <CA+23+fHsWh-FEkzm1GLjgMw2DYOu36OWx3_d6Qt+Ypx0YT=q+w@mail.gmail.com>
Message-ID: <CA+23+fHsWh-FEkzm1GLjgMw2DYOu36OWx3_d6Qt+Ypx0YT=q+w@mail.gmail.com>
To: jari.arkko@piuha.net
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dcbe0005715da509"
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz193.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jdrosen.net
X-Get-Message-Sender-Via: ecbiz193.inmotionhosting.com: authenticated_id: jdrosen+jdrosen.net/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: ecbiz193.inmotionhosting.com: jdrosen@jdrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/6c6by4QDpJSGGJhqVx_q236AjJM>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 17:38:54 -0000

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

Im supportive of this. When we specified TRIP oh-so-long-ago there wasnt
really a technical need - it just seemed a reasonable thing to do to
collect the address. GIven the new sensitivies to PII it makes sense to
change this. Worth noting that I dont think there are any real TRIP
depoyments, so this is largely a cleanup exercise I think.

-Jonathan R.

On Wed, Jul 18, 2018 at 10:53 AM Jari Arkko <jari.arkko@piuha.net> wrote:

> Ted and I have written a draft to update one IANA registry that
> (we think unnecessarily) calls for registering postal addresses
> for people who request code points. We think this should
> not be done for privacy, GDPR, exception at IANA, etc.
> reasons.
>
> We=E2=80=99d love to get feedback, and if there=E2=80=99s no roadblocks,
> move pretty quickly to asking the working group or the ADs
> to take the draft forward.
>
> Jari
>
> > Name:         draft-arkko-trip-registry-update
> > Revision:     00
> > Title:                Update to the TRIP IANA Registry Rules Regarding
> Postal Addresses
> > Document date:        2018-07-16
> > Group:                Individual Submission
> > Pages:                3
> > URL:
> https://www.ietf.org/internet-drafts/draft-arkko-trip-registry-update-00.=
txt
> > Status:
> https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/
> > Htmlized:
> https://tools.ietf.org/html/draft-arkko-trip-registry-update-00
> > Htmlized:
> https://datatracker.ietf.org/doc/html/draft-arkko-trip-registry-update
> >
> >
> > Abstract:
> >   This memo updates the IANA registry rules for the Telephony Routing
> >   over IP (TRIP) protocol, by no longer requiring that postal addresses
> >   be included in contact information.
> >
> >   This memo updates RFC 3219.
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>


--=20
Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net
http://www.jdrosen.net

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

<div dir=3D"ltr"><div>Im supportive of this. When we specified TRIP oh-so-l=
ong-ago there wasnt really a technical need - it just seemed a reasonable t=
hing to do to collect the address. GIven the new sensitivies to PII it make=
s sense to change this. Worth noting that I dont think there are any real T=
RIP depoyments, so this is largely a cleanup exercise I think.</div><div><b=
r></div><div>-Jonathan R.<br></div></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr">On Wed, Jul 18, 2018 at 10:53 AM Jari Arkko &lt;<a href=3D"ma=
ilto:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Ted and I have written a draft to update one IA=
NA registry that<br>
(we think unnecessarily) calls for registering postal addresses<br>
for people who request code points. We think this should<br>
not be done for privacy, GDPR, exception at IANA, etc. <br>
reasons.<br>
<br>
We=E2=80=99d love to get feedback, and if there=E2=80=99s no roadblocks,<br=
>
move pretty quickly to asking the working group or the ADs<br>
to take the draft forward.<br>
<br>
Jari<br>
<br>
&gt; Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-arkko-trip-registry-updat=
e<br>
&gt; Revision:=C2=A0 =C2=A0 =C2=A000<br>
&gt; Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Update t=
o the TRIP IANA Registry Rules Regarding Postal Addresses<br>
&gt; Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2018-07-16<br>
&gt; Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individu=
al Submission<br>
&gt; Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3<br>
&gt; URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.i=
etf.org/internet-drafts/draft-arkko-trip-registry-update-00.txt" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/internet-drafts/draft-arkko=
-trip-registry-update-00.txt</a><br>
&gt; Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracke=
r.ietf.org/doc/draft-arkko-trip-registry-update/" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/doc/draft-arkko-trip-registry-upda=
te/</a><br>
&gt; Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/=
html/draft-arkko-trip-registry-update-00" rel=3D"noreferrer" target=3D"_bla=
nk">https://tools.ietf.org/html/draft-arkko-trip-registry-update-00</a><br>
&gt; Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/html/draft-arkko-trip-registry-update" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/doc/html/draft-arkko-trip-registry=
-update</a><br>
&gt; <br>
&gt; <br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0This memo updates the IANA registry rules for the Telephon=
y Routing<br>
&gt;=C2=A0 =C2=A0over IP (TRIP) protocol, by no longer requiring that posta=
l addresses<br>
&gt;=C2=A0 =C2=A0be included in contact information.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0This memo updates RFC 3219.<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
mail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Jonatha=
n Rosenberg, Ph.D.<br><a href=3D"mailto:jdrosen@jdrosen.net" target=3D"_bla=
nk">jdrosen@jdrosen.net</a><br><a href=3D"http://www.jdrosen.net" target=3D=
"_blank">http://www.jdrosen.net</a></div></div>

--000000000000dcbe0005715da509--


From nobody Fri Jul 20 05:35:38 2018
Return-Path: <jari.arkko@piuha.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D06127332 for <dispatch@ietfa.amsl.com>; Fri, 20 Jul 2018 05:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_FILL_THIS_FORM_SHORT=0.01] 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 NiLgaITyqOlj for <dispatch@ietfa.amsl.com>; Fri, 20 Jul 2018 05:35:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B1FDD12426A for <dispatch@ietf.org>; Fri, 20 Jul 2018 05:35:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C09076601DA; Fri, 20 Jul 2018 15:35:32 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGFcQjfvXdRV; Fri, 20 Jul 2018 15:35:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 7ED74660162; Fri, 20 Jul 2018 15:35:31 +0300 (EEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20180718171158.132b4da0@elandnews.com>
Date: Fri, 20 Jul 2018 08:35:29 -0400
Cc: dispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <48730143-CC13-4CA3-A793-C9249ABDAE9A@piuha.net>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net> <CAHBDyN7k=+7RTdygjDX1ZBza7kMsT-=isjORMTXrkqNpJZoZVg@mail.gmail.com> <6.2.5.6.2.20180718171158.132b4da0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/UYPIUO68oElkaPNCq4GUILqCxGc>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2018 12:35:36 -0000

SM,

> The Introduction Section mentions "privacy benefit" with respect to =
postal addresses.  If I understood corectly, the issue is about PII.  =
Should both postal and email addresses be considered instead of postal =
addresses only?

Good question.

However, we are targeting only one change with regards to this draft, =
the postal addresses. This registry is to my knowledge the only one that =
current requires postal addresses, and we want to fix that because that =
keeps showing up as an exception in IANA=E2=80=99s explanation of how =
they handle privacy, how they deal with GDPR, etc.

There=E2=80=99s another and potentially bigger question of many =
registries including email addresses; the position that we have taken is =
that those addresses are necessary for the public benefit that these =
registries provide, e.g., by allowing us to reach out to the people who =
made requests and ask them about their usage. Nevertheless, it was not =
the purpose of this draft to go into the email question, and if any =
change were to be made there, it should probably apply more broadly than =
the TRIP registry. And be in another draft :-)

Hope this clarifies,

Jari

