
From nobody Sun Jun  1 13:45:28 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3C81A008C for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 13:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 tl8DD7uCV_VE for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 13:45:23 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D4FE1A0086 for <ietf@ietf.org>; Sun,  1 Jun 2014 13:45:23 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id rp18so3675213iec.40 for <ietf@ietf.org>; Sun, 01 Jun 2014 13:45:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=QjZUgo3hsmrvD7LifJj2pyCK6Hsts6popzvMxbaGL1g=; b=Tl3o4v919MQJvy5cs+EUPTURNM1nOqwUfYlDevZRkCsGNcHpWs3dR+3Xdg7zs8ydU2 93ACX2KOfHxZvw3lDVGoFiDyJXnusjQegiiKr5xAw12RAnfolvukpTG6ENHWT24Rq/VB 4qmheBfNsLni6RKC33Di43Qt+mpVDvTqH4KHQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=QjZUgo3hsmrvD7LifJj2pyCK6Hsts6popzvMxbaGL1g=; b=TU7kQzstbxJofCgW/diNabGUX7TDr83OsrmUfIuIq/6LNAvOQpice9IQeNRO/ZGgbD FF+vq4nzfOTUpOiXI/eoK86Nz2zm+z9FslXCoNmtLnNeYTvLo8ZFMaz71WiY2luT4w3k 7yPiuZl9hn1EzFSC0Q5r2Uj612dghYzBZy8dbVSLE0NwjHD1xxOfUVtJkaTsKXTGy5QN ubKaB/Y2Oy2IUKNkonVHqS9Oj+p6Mppa/khmmmuXxW9aK0hVt+/FJZS594/DViDGgpJk rHSvih+V70RYSRixBqVmc1dIFzBnXbUsNjzm60LN1AR4OfgPLE7Nk2W+wxTkCkIUvV0C fneA==
X-Gm-Message-State: ALoCoQlCV7JcM4+54TqXxvfjcoRLxIe83raNh7DOB9Iw4pcHCwf/7W2tvlDDBSSC0Q165/lYpASb
X-Received: by 10.43.70.12 with SMTP id ye12mr31478988icb.46.1401655517794; Sun, 01 Jun 2014 13:45:17 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:1:ecb7:d9b:5ca0:b8eb? ([2001:4900:1042:1:ecb7:d9b:5ca0:b8eb]) by mx.google.com with ESMTPSA id c8sm859575igx.8.2014.06.01.13.45.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Jun 2014 13:45:17 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_1946BF28-8987-4ACB-A148-53383A1577E9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <1B58612C-795E-4DCE-8692-78A785863FD6@virtualized.org>
Date: Sun, 1 Jun 2014 23:45:14 +0300
Message-Id: <7AB20196-5BD5-472B-8510-8D10CD408B5C@hopcount.ca>
References: <20140520204238.21772.64347.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140521194638.06eaf508@resistor.net> <1111FB79-012A-414B-B8CD-0BBDAE8BD6A8@hopcount.ca> <6.2.5.6.2.20140522095317.0c5fd648@elandnews.com> <5C02BCCA-79D7-40A5-BFB0-26284A667E78@vpnc.org> <DC9ED318-2352-4AF0-8A43-29D237C32B64@vigilsec.com> <924045CD-DC34-423B-8702-CD99CF687D46@vpnc.org> <FDC0E3E9-DD1B-4EF4-8C3C-54B902AEC92F@vigilsec.com> <3F0D0CB6-B534-433D-B321-762EB15D2126@hopcount.ca> <1B58612C-795E-4DCE-8692-78A785863FD6@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vI-Am91nGifzFt_J9cwZhBbD00M
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 20:45:25 -0000

--Apple-Mail=_1946BF28-8987-4ACB-A148-53383A1577E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 30 May 2014, at 20:24, David Conrad <drc@virtualized.org> wrote:

> On May 30, 2014, at 2:49 AM, Joe Abley <jabley@hopcount.ca> wrote:
>> The current text talks about the service, not individual servers.
>>=20
>> The service (as provided by thirteen root servers) is available over =
both IPv6 and IPv4 today, and hence complies with the proposed BCP.
>=20
> So, to reduce this to the absurd, if a single root server operator =
provided IPv6 DNS service via a dust-covered 8088 PC connected over a =
300 bps nailed up SLIP line, the proposed BCP would be met?
>=20
> BCP177 would appear to be a significantly better answer here.

My understanding here is that this is an attempt to codify a set of =
protocol requirements for the service, deliberately leaving operational =
considerations like deployment using anycast, capacity and capabilities =
of individual root servers, etc to be described in a kind of =
self-declaration by the root server operators themselves.

This was originally proposed to meet the kind of challenge you outlined =
in a previous e-mail relating to the odd, non-contractual relationship =
between individual root server operators and, well, everybody else.

I think this sub-thread is mainly concerned about whether that is a =
sensible approach, and the particular issue of whether IPv6 transport =
for individual servers belongs in this document is just an example of =
the wider issue.

Perhaps pulling up a thousand feet and considering whether the proposed =
split of

1. protocol requirements for the service -- RFC series
2. description of the operational aspects of the service -- RSSAC =
document

with the idea that both would functionally replace 2870 is what needs to =
happen?

(I appreciate, as others have mentioned, that the RSSAC document has not =
yet been published in draft or final copy.)


Joe

--Apple-Mail=_1946BF28-8987-4ACB-A148-53383A1577E9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlOLkNoACgkQNI8MvYZSOiyC/gCfVtbcrp88EQa2QLN4n39StO5s
YpkAnR6IQEEE9kDODjOGfRfdOaiw19s0
=Ly2r
-----END PGP SIGNATURE-----

--Apple-Mail=_1946BF28-8987-4ACB-A148-53383A1577E9--


From nobody Sun Jun  1 14:13:34 2014
Return-Path: <serrhini@mail.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238511A0086 for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 14:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.15
X-Spam-Level: ***
X-Spam-Status: No, score=3.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 2V1uo_m4IWa7 for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 14:13:30 -0700 (PDT)
Received: from f416.i.mail.ru (f416.i.mail.ru [185.5.136.87]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51E621A008C for <ietf@ietf.org>; Sun,  1 Jun 2014 14:13:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2;  h=Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=H8TzYkLsXbATA6f27c0+2Lp1dfFr3v6T/nzaAAk2nCA=;  b=CR2UEulO8QL3cnBA/be+/aMWz2BTv+zdo+n+atpnuJp4e3DnmHl5pDEGiub5pmpD+ft0ylRTghYWV2rae0T9VDZA7y2IG5em/5U4cSYOiyjaZMvIAVxFwF+ghaa5f23Z1xb/SiXooc99o7lmiCXf32kRQ+zwU8f35IjoABp8Jow=;
Received: from mail by f416.i.mail.ru with local (envelope-from <serrhini@mail.ru>) id 1WrD4D-000524-HO; Mon, 02 Jun 2014 01:13:21 +0400
Received: from [41.137.68.121] by e.mail.ru with HTTP; Mon, 02 Jun 2014 01:13:21 +0400
From: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
To: =?UTF-8?B?aWV0ZkBpZXRmLm9yZw==?= <ietf@ietf.org>, internetpolicy@elists.isoc.org
Subject: =?UTF-8?B?RndkOiBSZTogW0ludGVybmV0IFBvbGljeV0gcm9vdCBqdXN0aWZpY2F0aW9u?= =?UTF-8?B?IGZvciBuZXQgbmV1dHJhbGl0eT8=?=
Mime-Version: 1.0
X-Mailer: Mail.Ru Mailer 1.0
X-Originating-IP: [41.137.68.121]
Date: Mon, 02 Jun 2014 01:13:21 +0400
X-Priority: 3 (Normal)
Message-ID: <1401657201.842471284@f416.i.mail.ru>
Content-Type: multipart/alternative; boundary="--ALT--RNFdTKlu1401657201"
X-Mras: Ok
X-Spam: undefined
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PzAScqikTZ4zLjbHURX2yW_0WuU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 21:13:33 -0000

----ALT--RNFdTKlu1401657201
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CnRoZSBpbnRlcm5ldCBhY2Nlc3MgbXVzdCBiZSBmcmVlLCAgYXMgdGhlIG94eWdlbiBicmVhdGhp
bmcsIHRoZSBwcm9wb3NpdGlvbiB0aGF0IEludGVybmV0IGNvdWxkIGJlIHByb3ZpZGVkIGFzIGEg
cHVibGljIHNlcnZpY2UgYW5kIGZ1bmRlZCB0aHJvdWdoIHRheGVzICBpcyBub3QgdmVyeSBjb3Jy
ZWN0IGJlY2F1c2UgIG1vc3QgcGFydCBvZiB0aGUgd29ybGQgcG9wdWxhdGlvbiBzdWZmZXJzIGZy
b20gdGF4ZXMgb3IgYWxyZWFkeSBhcmUgIG92ZXJ0YXhlZCwgYWxsIG9mIHVzIGtub3cgYWJvdXQg
dGhlIHF1YWxpdHkgb2YgcHVibGljIHNlcnZpY2VzLCAgbm93YWRheXMgbW9zdCBwdWJsaWMgc2Vy
dmljZXMgYXJlIHByaXZhdGl6ZWQgLiBpbiB0aGUgZW5kIGludGVybmV0IHNlcnZpY2VzIHdpbGwg
YmUgcmVwcml2YXRpemVkIGFnYWluLgpJIHRoaW5rIHRoZXJlIHNob3VsZCBiZSBhIHRheCBvbiBl
YWNoIGludGVybmV0IGZpbmFuY2lhbCB0cmFuc2FjdGlvbiBub3Qgb24gdGhlIGNsaWVudCBzaWRl
IGJ1dCBvbiB0aGUgc2lkZSBvZiBjb21wYW5pZXMswqAgd2UgYWxsIGRheXPCoCBoZWFyZCBhYm91
dCBpbnRlcm5ldCBtb25leSAgYW5kIHRoZSBleHBvbm9uY2lhbCBudW1iZXIgb2YgYmlsaW9uLiAK
cGVlcmluZyBpcyBncmVldCBzb2x1dGlvbiBmb3IgcmVkdWNpbmcgY29zdCBvZiBpbnRlcm5ldC4g
CgpNb2hhbW1lZCBTZXJyaGluaSAKTW9yb2NjbyBjaGFwdGVyCgotLS0tLS0tLSDQn9C10YDQtdGB
0YvQu9Cw0LXQvNC+0LUg0YHQvtC+0LHRidC10L3QuNC1IC0tLS0tLS0tCtCe0YIg0LrQvtCz0L46
IERhdmlkIENvbGxpZXItQnJvd24gPGRhdmVjLWJAcm9nZXJzLmNvbT4K0JrQvtC80YM6IGludGVy
bmV0cG9saWN5QGVsaXN0cy5pc29jLm9yZwrQlNCw0YLQsDogRnJpLCAzMCBNYXkgMjAxNCAyMDoz
ODozMiAtMDQwMArQotC10LzQsDogUmU6IFtJbnRlcm5ldCBQb2xpY3ldIHJvb3QganVzdGlmaWNh
dGlvbiBmb3IgbmV0IG5ldXRyYWxpdHk/CgpNYXkgSSBzcGVjdWxhdGUgdGhhdCBhY2Nlc3MgaXMg
Y2hlYXAgZW5vdWdoIHRoYXQgaXQgY2FuIGJlIHRyZWF0ZWQgYXMgYQp1bml2ZXJzYWwgZ29vZCwg
bXVjaCBsaWtlIGxpZ2h0LWhvdXNlcy4KClVuaXZlcnNhbHMgYXJlIGJlbmVmaWNpYWwgdG8gZXZl
cnlvbmUsIGJ1dCBjb3N0IHNvIGxpdHRsZSBwZXIgYmVuZWZpdAp0aGF0IGl0J3MgaGFyZCB0byBm
aWd1cmUgb3V0IGhvdyB0byBjaGFyZ2UgZm9yIHRoZW0uICBMaWdodGhvdXNlcyBhcmUKdGhlIGNs
YXNzaWMgZXhhbXBsZSwgYW5kIGFyZSB0aGUgdmVyeSBmaXJzdCB0aGluZyB0aGF0IHRoZSBnb3Zl
cm5tZW50IG9mCnRoZSBVbml0ZWQgU3RhdGVzIGJ1aWx0Li4uCgotLWRhdmUKCgpPbiAwNS8zMC8y
MDE0IDExOjIxIEFNLCBSaWNoYXJkIEhpbGwgd3JvdGU6Cj4gVmVuaSwKPiAKPiBUaGF0IGlzIGdy
ZWF0LCBidXQgdGhlbiBJIGd1ZXNzIHRoYXQgbXkgYWNjZXNzIGlzIGJlaW5nIHN1YnNpZGl6ZWQg
YnkKPiBCdWxnYXJpYW4gdXNlcnMuICBWZXJ5IGdlbmVyb3VzIG9mIHRoZW0uCj4gCj4gQmVzdCwK
PiBSaWNoYXJkCj4gCj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSBGcm9tOiAiVmVuaSBN
YXJrb3Zza2kiIDwgdmVuaUB2ZW5pLmNvbSA+Cj4gVG86ICJSaWNoYXJkIEhpbGwiIDwgcmhpbGxA
aGlsbC1hLmNoID47ICJHYXJ5IFdheW5lIEtlbndhcmQiCj4gPCBnYXJ5a2Vud2FyZEBpZWVlLm9y
ZyA+OyAiTmljayBBc2h0b24tSGFydCIgPCBuYXNodG9uQGNvbnNlbnN1cy5wcm8gPgo+IENjOiA8
IGludGVybmV0cG9saWN5QGVsaXN0cy5pc29jLm9yZyA+Cj4gU2VudDogRnJpZGF5LCBNYXkgMzAs
IDIwMTQgNToxOSBQTQo+IFN1YmplY3Q6IFJlOiBbSW50ZXJuZXQgUG9saWN5XSByb290IGp1c3Rp
ZmljYXRpb24gZm9yIG5ldCBuZXV0cmFsaXR5Pwo+IAo+IAo+PiBIaS4KPj4gU2VlIGJlbG93IHNs
aWdodCBjb3JyZWN0aW9uLgo+Pgo+PiBPbiAwNS8zMC8xNCAxMDowNCwgUmljaGFyZCBIaWxsIHdy
b3RlOgo+Pj4gSSBhZ3JlZSB3aXRoIEdhcnkgYW5kIHBhcnRseSB3aXRoIE5pY2suCj4+Pgo+Pj4g
VXBzdHJlYW0gc2VydmljZSBwcm92aWRlcnMgYXJlIGFscmVhZHkgcGF5aW5nIHRvIGNvbm5lY3Qg
dG8gdGhlCj4+PiBJbnRlcm5ldCwgYnV0IHRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHRoZXkgc2hv
dWxkIHBheSBtb3JlIHdoZW4gd2hhdAo+Pj4gdGhleSBkbyBpbXBvc2VzIGNhcGFjaXR5IHVwZ3Jh
ZGVzIGRvd25zdHJlYW0uCj4+Pgo+Pj4gVEFOU1RBQUZMIChpZiB5b3UgZG9uJ3Qga25vdyB0aGF0
IGFjcm9ueW0sIHNlZQo+Pj4gIGh0dHA6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvVGFuc3RhYWZs
ICkKPj4+Cj4+PiBJbiB0aGUgZW5kLCBpdCBpcyBhbHdheXMgdXMsIHRoZSBwZW9wbGUgd2hvIHBh
eS4gIFRoZSBxdWVzdGlvbiBpcyBob3cKPj4+IGFuZCBob3cgbXVjaC4gIFRoZSBJbnRlcm5ldCBj
b3VsZCBiZSBwcm92aWRlZCBhcyBhIHB1YmxpYyBzZXJ2aWNlIGFuZAo+Pj4gZnVuZGVkIHRocm91
Z2ggdGF4ZXMgKG9yIHBhcnRseSBmdW5kZWQgdGhyb3VnaCB0YXhlcyksIG9yIGl0IGNhbiBiZQo+
Pj4gZnVuZGVkIGJ5IGZsYXQtcmF0ZSBwYXltZW50cyBmcm9tIHVzZXJzICh0aGUgc3lzdGVtIG1v
c3QgY29tbW9ubHkKPj4+IHVzZWQgdG9kYXkpLCBvciBpdCBjb3VsZCBiZSBmdW5kZWQgYnkgZGF0
YS12b2x1bWUgYmFzZWQgcGF5bWVudHMgZnJvbQo+Pj4gdXNlcnMgKGEgc3lzdGVtIHVzZWQgaW4g
c29tZSBwbGFjZXMpLCBvciBpdCBjb3VsZCBiZSBmdW5kZWQgYnkgc29tZQo+Pj4gY29tYmluYXRp
b24gb2YgcGF5bWVudHMgZnJvbSB1c2VycyBhbmQgdXBzdHJlYW0gc3VwcGxpZXJzIChvZnRlbgo+
Pj4gY2FsbGVkIE9UVCkuCj4+Pgo+Pgo+PiBOb3QgYWx3YXlzLCBSaWNoYXJkLgo+PiBDb21lIHRv
IFNvZmlhLCBCdWxnYXJpYSwgYW5kIGxvZ2luIGF0IGFueSBvZiB0aGUgdGhvdXNhbmRzIGZyZWUg
d2ktZmkKPj4gbG9jYXRpb25zLiBObyBwYXNzd29yZHMsIG5vIHJlZ2lzdHJhdGlvbiwgbm90IHJl
cXVpcmVtZW50cyAobGlrZSBpbgo+PiBvdGhlciBFVSBjb3VudHJpZXMpIHRvIGdpdmUgeW91ciBw
ZXJzb25hbCBkYXRhLiBZZXMsIHRoZSBpbnRlcm5ldAo+PiBhY2Nlc3MgY291bGQgYmUgYWxzbyBm
cmVlLgo+Pgo+Pgo+Pgo+PiAtLSAKPj4KPj4gQmVzdCwKPj4gVmVuaSBNYXJrb3Zza2kKPj4gIGh0
dHA6Ly93d3cudmVuaS5jb20KPj4gIGh0dHBzOi8vd3d3LmZhY2Vib29rLmNvbS92ZW5pbWFya292
c2tpCj4+ICBodHRwczovL3R3aXR0ZXIuY29tL3ZlbmkKPj4KPj4gVGhlIG9waW5pb25zIGV4cHJl
c3NlZCBhYm92ZSBhcmUgdGhvc2Ugb2YgdGhlCj4+IGF1dGhvciwgbm90IG9mIGFueSBvcmdhbml6
YXRpb25zLCBhc3NvY2lhdGVkCj4+IHdpdGggb3IgcmVsYXRlZCB0byBoaW0gaW4gYW55IGdpdmVu
IHdheS4KPj4KPj4KPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+IFRvIG1hbmFnZSB5b3VyIElTT0Mgc3Vic2NyaXB0aW9ucyBvciB1bnN1YnNjcmli
ZSwKPiBwbGVhc2UgbG9nIGludG8gdGhlIElTT0MgTWVtYmVyIFBvcnRhbDoKPiAgaHR0cHM6Ly9w
b3J0YWwuaXNvYy5vcmcvCj4gVGhlbiBjaG9vc2UgSW50ZXJlc3RzICYgU3Vic2NyaXB0aW9ucyBm
cm9tIHRoZSBNeSBBY2NvdW50IG1lbnUuCj4gCgoKLS0gCkRhdmlkIENvbGxpZXItQnJvd24sICAg
ICAgICAgfCBBbHdheXMgZG8gcmlnaHQuIFRoaXMgd2lsbCBncmF0aWZ5ClN5c3RlbSBQcm9ncmFt
bWVyIGFuZCBBdXRob3IgfCBzb21lIHBlb3BsZSBhbmQgYXN0b25pc2ggdGhlIHJlc3QKZGF2ZWNi
QHNwYW1jb3AubmV0IHwgICAgICAgICAgICAgICAgICAgICAgLS0gTWFyayBUd2FpbgoKLS0gCkRh
dmlkIENvbGxpZXItQnJvd24sICAgICAgICAgfCBBbHdheXMgZG8gcmlnaHQuIFRoaXMgd2lsbCBn
cmF0aWZ5ClN5c3RlbSBQcm9ncmFtbWVyIGFuZCBBdXRob3IgfCBzb21lIHBlb3BsZSBhbmQgYXN0
b25pc2ggdGhlIHJlc3QKZGF2ZWNiQHNwYW1jb3AubmV0IHwgICAgICAgICAgICAgICAgICAgICAg
LS0gTWFyayBUd2FpbgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXwpUbyBtYW5hZ2UgeW91ciBJU09DIHN1YnNjcmlwdGlvbnMgb3IgdW5zdWJzY3JpYmUsCnBs
ZWFzZSBsb2cgaW50byB0aGUgSVNPQyBNZW1iZXIgUG9ydGFsOgpodHRwczovL3BvcnRhbC5pc29j
Lm9yZy8KVGhlbiBjaG9vc2UgSW50ZXJlc3RzICYgU3Vic2NyaXB0aW9ucyBmcm9tIHRoZSBNeSBB
Y2NvdW50IG1lbnUuCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgrQoSDRg9Cy0LDQttC10L3QuNC10LwsCm1vaGFt
bWVkIHNlcnJoaW5pCnNlcnJoaW5pQG1haWwucnUK

----ALT--RNFdTKlu1401657201
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

CjxIVE1MPjxCT0RZPjxicj50aGUgaW50ZXJuZXQgYWNjZXNzIG11c3QgYmUgZnJlZSwgPHNwYW4g
aWQ9InJlc3VsdF9ib3giIGNsYXNzPSJzaG9ydF90ZXh0IiBsYW5nPSJlbiI+PHNwYW4gY2xhc3M9
ImhwcyI+YXM8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPnRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9
ImhwcyI+b3h5Z2VuPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5icmVhdGhpbmcsIHRoZSBwcm9w
b3NpdGlvbiB0aGF0IEludGVybmV0IGNvdWxkIGJlIHByb3ZpZGVkIGFzIGEgcHVibGljIHNlcnZp
Y2UgYW5kIGZ1bmRlZCB0aHJvdWdoIHRheGVzIDwvc3Bhbj48L3NwYW4+PHNwYW4gaWQ9InJlc3Vs
dF9ib3giIGxhbmc9ImVuIj48c3BhbiBjbGFzcz0iaHBzIj5pcyBub3Q8L3NwYW4+IDxzcGFuIGNs
YXNzPSJocHMiPnZlcnkgY29ycmVjdDwvc3Bhbj4gYmVjYXVzZSA8c3BhbiBjbGFzcz0iaHBzIj5t
b3N0PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5wYXJ0IG9mIHRoZTwvc3Bhbj4gPHNwYW4gY2xh
c3M9ImhwcyI+d29ybGQ8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPnBvcHVsYXRpb248L3NwYW4+
IDxzcGFuIGNsYXNzPSJocHMiPnN1ZmZlcnMgZnJvbTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+
dGF4ZXM8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPm9yPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBz
Ij5hbHJlYWR5PC9zcGFuPiBhcmUgPHNwYW4gY2xhc3M9ImhwcyI+b3ZlcnRheGVkLCBhbGwgb2Yg
dXMga25vdyBhYm91dCB0aGUgcXVhbGl0eSBvZiBwdWJsaWMgc2VydmljZXMsIDxzcGFuIGlkPSJy
ZXN1bHRfYm94IiBsYW5nPSJlbiI+PHNwYW4gY2xhc3M9ImhwcyI+bm93YWRheXM8L3NwYW4+IDxz
cGFuIGNsYXNzPSJocHMiPm1vc3Q8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPnB1YmxpYzwvc3Bh
bj4gPHNwYW4gY2xhc3M9ImhwcyI+c2VydmljZXM8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmFy
ZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+cHJpdmF0aXplZDwvc3Bhbj48L3NwYW4+PC9zcGFu
Pjwvc3Bhbj4uIGluIHRoZSBlbmQgaW50ZXJuZXQgc2VydmljZXMgd2lsbCBiZSByZXByaXZhdGl6
ZWQgYWdhaW4uPGJyPjxzcGFuIGlkPSJyZXN1bHRfYm94IiBjbGFzcz0ibG9uZ190ZXh0Ij48c3Bh
biBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogI2ZmZmZmZjsiIHRpdGxlPSJqZSBwZW5zZSBxdSdp
bCBkb2l0IHkgYXZvaXIgdW5lIHRheGUgc3VyIGNoYXF1ZSB0cmFuc2FjdGlvbiBmaW5hbmNpZXJl
IG5vbiBkdSBjb3TDqSBkdSBjbGllbnQgbWFpcyBkdSBjb3TDqSBkZXMgc29jaWV0w6lzIHF1aSBm
b250IGxldXJzIGJlbmlmaWNlcyBzdXIgaW50ZXJuZXQgY29tbWUiIGRhdGEtbWNlLXN0eWxlPSJi
YWNrZ3JvdW5kLWNvbG9yOiAjZmZmZmZmOyI+SSB0aGluayB0aGVyZSBzaG91bGQgYmUgYSB0YXgg
b24gZWFjaCBpbnRlcm5ldCBmaW5hbmNpYWwgdHJhbnNhY3Rpb24gbm90IG9uIHRoZSBjbGllbnQg
c2lkZSBidXQgb24gdGhlIHNpZGUgb2YgY29tcGFuaWVzLCZuYnNwOzwvc3Bhbj48L3NwYW4+PHNw
YW4gaWQ9InJlc3VsdF9ib3giIGNsYXNzPSJsb25nX3RleHQiPjxzcGFuIHN0eWxlPSJiYWNrZ3Jv
dW5kLWNvbG9yOiAjZmZmZmZmOyIgdGl0bGU9ImplIHBlbnNlIHF1J2lsIGRvaXQgeSBhdm9pciB1
bmUgdGF4ZSBzdXIgY2hhcXVlIHRyYW5zYWN0aW9uIGZpbmFuY2llcmUgbm9uIGR1IGNvdMOpIGR1
IGNsaWVudCBtYWlzIGR1IGNvdMOpIGRlcyBzb2NpZXTDqXMgcXVpIGZvbnQgbGV1cnMgYmVuaWZp
Y2VzIHN1ciBpbnRlcm5ldCBjb21tZSIgZGF0YS1tY2Utc3R5bGU9ImJhY2tncm91bmQtY29sb3I6
ICNmZmZmZmY7Ij4gPC9zcGFuPjwvc3Bhbj53ZSBhbGwgZGF5cyZuYnNwOyBoZWFyZCBhYm91dCBp
bnRlcm5ldCBtb25leSAgYW5kIHRoZSBleHBvbm9uY2lhbCBudW1iZXIgb2YgYmlsaW9uLiA8YnI+
cGVlcmluZyBpcyBncmVldCBzb2x1dGlvbiBmb3IgcmVkdWNpbmcgY29zdCBvZiBpbnRlcm5ldC4g
PGJyPjxicj5Nb2hhbW1lZCBTZXJyaGluaSA8YnI+TW9yb2NjbyBjaGFwdGVyPGJyPjxicj4tLS0t
LS0tLSDQn9C10YDQtdGB0YvQu9Cw0LXQvNC+0LUg0YHQvtC+0LHRidC10L3QuNC1IC0tLS0tLS0t
PGJyPgrQntGCINC60L7Qs9C+OiBEYXZpZCBDb2xsaWVyLUJyb3duICZsdDtkYXZlYy1iQHJvZ2Vy
cy5jb20mZ3Q7PGJyPgrQmtC+0LzRgzogaW50ZXJuZXRwb2xpY3lAZWxpc3RzLmlzb2Mub3JnPGJy
PgoK0JTQsNGC0LA6IEZyaSwgMzAgTWF5IDIwMTQgMjA6Mzg6MzIgLTA0MDA8YnI+CtCi0LXQvNCw
OiBSZTogW0ludGVybmV0IFBvbGljeV0gcm9vdCBqdXN0aWZpY2F0aW9uIGZvciBuZXQgbmV1dHJh
bGl0eT88YnI+Cjxicj4KCgkKCgoKICAgIAoKCgoKCgoKCgoJCgkKCgoJCgkKCQoJCgkKCgkKCQoK
CQoJCgoKCjxkaXYgY2xhc3M9ImpzLWhlbHBlciBqcy1yZWFkbXNnLW1zZyI+Cgk8c3R5bGUgdHlw
ZT0idGV4dC9jc3MiPjwvc3R5bGU+CiAJPGRpdj4KCQk8YmFzZSB0YXJnZXQ9Il9zZWxmIiBocmVm
PSJodHRwczovL2UubWFpbC5ydS8iPgoJCQoJCQk8ZGl2IGlkPSJzdHlsZV8xNDAxNTY4ODcxMDAw
MDAwMDQyNF9CT0RZIj5NYXkgSSBzcGVjdWxhdGUgdGhhdCBhY2Nlc3MgaXMgY2hlYXAgZW5vdWdo
IHRoYXQgaXQgY2FuIGJlIHRyZWF0ZWQgYXMgYTxicj4KdW5pdmVyc2FsIGdvb2QsIG11Y2ggbGlr
ZSBsaWdodC1ob3VzZXMuPGJyPgo8YnI+ClVuaXZlcnNhbHMgYXJlIGJlbmVmaWNpYWwgdG8gZXZl
cnlvbmUsIGJ1dCBjb3N0IHNvIGxpdHRsZSBwZXIgYmVuZWZpdDxicj4KdGhhdCBpdCdzIGhhcmQg
dG8gZmlndXJlIG91dCBob3cgdG8gY2hhcmdlIGZvciB0aGVtLiAgTGlnaHRob3VzZXMgYXJlPGJy
Pgp0aGUgY2xhc3NpYyBleGFtcGxlLCBhbmQgYXJlIHRoZSB2ZXJ5IGZpcnN0IHRoaW5nIHRoYXQg
dGhlIGdvdmVybm1lbnQgb2Y8YnI+CnRoZSBVbml0ZWQgU3RhdGVzIGJ1aWx0Li4uPGJyPgo8YnI+
Ci0tZGF2ZTxicj4KPGJyPgo8YnI+Ck9uIDA1LzMwLzIwMTQgMTE6MjEgQU0sIFJpY2hhcmQgSGls
bCB3cm90ZTo8YnI+CiZndDsgVmVuaSw8YnI+CiZndDsgPGJyPgomZ3Q7IFRoYXQgaXMgZ3JlYXQs
IGJ1dCB0aGVuIEkgZ3Vlc3MgdGhhdCBteSBhY2Nlc3MgaXMgYmVpbmcgc3Vic2lkaXplZCBieTxi
cj4KJmd0OyBCdWxnYXJpYW4gdXNlcnMuICBWZXJ5IGdlbmVyb3VzIG9mIHRoZW0uPGJyPgomZ3Q7
IDxicj4KJmd0OyBCZXN0LDxicj4KJmd0OyBSaWNoYXJkPGJyPgomZ3Q7IDxicj4KJmd0OyAtLS0t
LSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIEZyb206ICJWZW5pIE1hcmtvdnNraSIgJmx0OzxhIGhy
ZWY9Ii9jb21wb3NlP1RvPXZlbmlAdmVuaS5jb20iPnZlbmlAdmVuaS5jb208L2E+Jmd0Ozxicj4K
Jmd0OyBUbzogIlJpY2hhcmQgSGlsbCIgJmx0OzxhIGhyZWY9Ii9jb21wb3NlP1RvPXJoaWxsQGhp
bGwlMmRhLmNoIj5yaGlsbEBoaWxsLWEuY2g8L2E+Jmd0OzsgIkdhcnkgV2F5bmUgS2Vud2FyZCI8
YnI+CiZndDsgJmx0OzxhIGhyZWY9Ii9jb21wb3NlP1RvPWdhcnlrZW53YXJkQGllZWUub3JnIj5n
YXJ5a2Vud2FyZEBpZWVlLm9yZzwvYT4mZ3Q7OyAiTmljayBBc2h0b24tSGFydCIgJmx0OzxhIGhy
ZWY9Ii9jb21wb3NlP1RvPW5hc2h0b25AY29uc2Vuc3VzLnBybyI+bmFzaHRvbkBjb25zZW5zdXMu
cHJvPC9hPiZndDs8YnI+CiZndDsgQ2M6ICZsdDs8YSBocmVmPSIvY29tcG9zZT9Ubz1pbnRlcm5l
dHBvbGljeUBlbGlzdHMuaXNvYy5vcmciPmludGVybmV0cG9saWN5QGVsaXN0cy5pc29jLm9yZzwv
YT4mZ3Q7PGJyPgomZ3Q7IFNlbnQ6IEZyaWRheSwgTWF5IDMwLCAyMDE0IDU6MTkgUE08YnI+CiZn
dDsgU3ViamVjdDogUmU6IFtJbnRlcm5ldCBQb2xpY3ldIHJvb3QganVzdGlmaWNhdGlvbiBmb3Ig
bmV0IG5ldXRyYWxpdHk/PGJyPgomZ3Q7IDxicj4KJmd0OyA8YnI+CiZndDsmZ3Q7IEhpLjxicj4K
Jmd0OyZndDsgU2VlIGJlbG93IHNsaWdodCBjb3JyZWN0aW9uLjxicj4KJmd0OyZndDs8YnI+CiZn
dDsmZ3Q7IE9uIDA1LzMwLzE0IDEwOjA0LCBSaWNoYXJkIEhpbGwgd3JvdGU6PGJyPgomZ3Q7Jmd0
OyZndDsgSSBhZ3JlZSB3aXRoIEdhcnkgYW5kIHBhcnRseSB3aXRoIE5pY2suPGJyPgomZ3Q7Jmd0
OyZndDs8YnI+CiZndDsmZ3Q7Jmd0OyBVcHN0cmVhbSBzZXJ2aWNlIHByb3ZpZGVycyBhcmUgYWxy
ZWFkeSBwYXlpbmcgdG8gY29ubmVjdCB0byB0aGU8YnI+CiZndDsmZ3Q7Jmd0OyBJbnRlcm5ldCwg
YnV0IHRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHRoZXkgc2hvdWxkIHBheSBtb3JlIHdoZW4gd2hh
dDxicj4KJmd0OyZndDsmZ3Q7IHRoZXkgZG8gaW1wb3NlcyBjYXBhY2l0eSB1cGdyYWRlcyBkb3du
c3RyZWFtLjxicj4KJmd0OyZndDsmZ3Q7PGJyPgomZ3Q7Jmd0OyZndDsgVEFOU1RBQUZMIChpZiB5
b3UgZG9uJ3Qga25vdyB0aGF0IGFjcm9ueW0sIHNlZTxicj4KJmd0OyZndDsmZ3Q7IDxhIGhyZWY9
Imh0dHA6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvVGFuc3RhYWZsIiB0YXJnZXQ9Il9ibGFuayI+
aHR0cDovL2VuLndpa2lwZWRpYS5vcmcvd2lraS9UYW5zdGFhZmw8L2E+ICk8YnI+CiZndDsmZ3Q7
Jmd0Ozxicj4KJmd0OyZndDsmZ3Q7IEluIHRoZSBlbmQsIGl0IGlzIGFsd2F5cyB1cywgdGhlIHBl
b3BsZSB3aG8gcGF5LiAgVGhlIHF1ZXN0aW9uIGlzIGhvdzxicj4KJmd0OyZndDsmZ3Q7IGFuZCBo
b3cgbXVjaC4gIFRoZSBJbnRlcm5ldCBjb3VsZCBiZSBwcm92aWRlZCBhcyBhIHB1YmxpYyBzZXJ2
aWNlIGFuZDxicj4KJmd0OyZndDsmZ3Q7IGZ1bmRlZCB0aHJvdWdoIHRheGVzIChvciBwYXJ0bHkg
ZnVuZGVkIHRocm91Z2ggdGF4ZXMpLCBvciBpdCBjYW4gYmU8YnI+CiZndDsmZ3Q7Jmd0OyBmdW5k
ZWQgYnkgZmxhdC1yYXRlIHBheW1lbnRzIGZyb20gdXNlcnMgKHRoZSBzeXN0ZW0gbW9zdCBjb21t
b25seTxicj4KJmd0OyZndDsmZ3Q7IHVzZWQgdG9kYXkpLCBvciBpdCBjb3VsZCBiZSBmdW5kZWQg
YnkgZGF0YS12b2x1bWUgYmFzZWQgcGF5bWVudHMgZnJvbTxicj4KJmd0OyZndDsmZ3Q7IHVzZXJz
IChhIHN5c3RlbSB1c2VkIGluIHNvbWUgcGxhY2VzKSwgb3IgaXQgY291bGQgYmUgZnVuZGVkIGJ5
IHNvbWU8YnI+CiZndDsmZ3Q7Jmd0OyBjb21iaW5hdGlvbiBvZiBwYXltZW50cyBmcm9tIHVzZXJz
IGFuZCB1cHN0cmVhbSBzdXBwbGllcnMgKG9mdGVuPGJyPgomZ3Q7Jmd0OyZndDsgY2FsbGVkIE9U
VCkuPGJyPgomZ3Q7Jmd0OyZndDs8YnI+CiZndDsmZ3Q7PGJyPgomZ3Q7Jmd0OyBOb3QgYWx3YXlz
LCBSaWNoYXJkLjxicj4KJmd0OyZndDsgQ29tZSB0byBTb2ZpYSwgQnVsZ2FyaWEsIGFuZCBsb2dp
biBhdCBhbnkgb2YgdGhlIHRob3VzYW5kcyBmcmVlIHdpLWZpPGJyPgomZ3Q7Jmd0OyBsb2NhdGlv
bnMuIE5vIHBhc3N3b3Jkcywgbm8gcmVnaXN0cmF0aW9uLCBub3QgcmVxdWlyZW1lbnRzIChsaWtl
IGluPGJyPgomZ3Q7Jmd0OyBvdGhlciBFVSBjb3VudHJpZXMpIHRvIGdpdmUgeW91ciBwZXJzb25h
bCBkYXRhLiBZZXMsIHRoZSBpbnRlcm5ldDxicj4KJmd0OyZndDsgYWNjZXNzIGNvdWxkIGJlIGFs
c28gZnJlZS48YnI+CiZndDsmZ3Q7PGJyPgomZ3Q7Jmd0Ozxicj4KJmd0OyZndDs8YnI+CiZndDsm
Z3Q7IC0tIDxicj4KJmd0OyZndDs8YnI+CiZndDsmZ3Q7IEJlc3QsPGJyPgomZ3Q7Jmd0OyBWZW5p
IE1hcmtvdnNraTxicj4KJmd0OyZndDsgPGEgaHJlZj0iaHR0cDovL3d3dy52ZW5pLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHA6Ly93d3cudmVuaS5jb208L2E+PGJyPgomZ3Q7Jmd0OyA8YSBocmVm
PSJodHRwczovL3d3dy5mYWNlYm9vay5jb20vdmVuaW1hcmtvdnNraSIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHBzOi8vd3d3LmZhY2Vib29rLmNvbS92ZW5pbWFya292c2tpPC9hPjxicj4KJmd0OyZndDsg
PGEgaHJlZj0iaHR0cHM6Ly90d2l0dGVyLmNvbS92ZW5pIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly90d2l0dGVyLmNvbS92ZW5pPC9hPjxicj4KJmd0OyZndDs8YnI+CiZndDsmZ3Q7IFRoZSBvcGlu
aW9ucyBleHByZXNzZWQgYWJvdmUgYXJlIHRob3NlIG9mIHRoZTxicj4KJmd0OyZndDsgYXV0aG9y
LCBub3Qgb2YgYW55IG9yZ2FuaXphdGlvbnMsIGFzc29jaWF0ZWQ8YnI+CiZndDsmZ3Q7IHdpdGgg
b3IgcmVsYXRlZCB0byBoaW0gaW4gYW55IGdpdmVuIHdheS48YnI+CiZndDsmZ3Q7PGJyPgomZ3Q7
Jmd0Ozxicj4KJmd0OyA8YnI+CiZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188YnI+CiZndDsgVG8gbWFuYWdlIHlvdXIgSVNPQyBzdWJzY3JpcHRpb25z
IG9yIHVuc3Vic2NyaWJlLDxicj4KJmd0OyBwbGVhc2UgbG9nIGludG8gdGhlIElTT0MgTWVtYmVy
IFBvcnRhbDo8YnI+CiZndDsgPGEgaHJlZj0iaHR0cHM6Ly9wb3J0YWwuaXNvYy5vcmcvIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cHM6Ly9wb3J0YWwuaXNvYy5vcmcvPC9hPjxicj4KJmd0OyBUaGVuIGNo
b29zZSBJbnRlcmVzdHMgJmFtcDsgU3Vic2NyaXB0aW9ucyBmcm9tIHRoZSBNeSBBY2NvdW50IG1l
bnUuPGJyPgomZ3Q7IDxicj4KPGJyPgo8YnI+Ci0tIDxicj4KRGF2aWQgQ29sbGllci1Ccm93biwg
ICAgICAgICB8IEFsd2F5cyBkbyByaWdodC4gVGhpcyB3aWxsIGdyYXRpZnk8YnI+ClN5c3RlbSBQ
cm9ncmFtbWVyIGFuZCBBdXRob3IgfCBzb21lIHBlb3BsZSBhbmQgYXN0b25pc2ggdGhlIHJlc3Q8
YnI+CjxhIGhyZWY9Ii9jb21wb3NlP1RvPWRhdmVjYkBzcGFtY29wLm5ldCI+ZGF2ZWNiQHNwYW1j
b3AubmV0PC9hPiAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAtLSBNYXJrIFR3YWlu
PGJyPgo8YnI+Ci0tIDxicj4KRGF2aWQgQ29sbGllci1Ccm93biwgICAgICAgICB8IEFsd2F5cyBk
byByaWdodC4gVGhpcyB3aWxsIGdyYXRpZnk8YnI+ClN5c3RlbSBQcm9ncmFtbWVyIGFuZCBBdXRo
b3IgfCBzb21lIHBlb3BsZSBhbmQgYXN0b25pc2ggdGhlIHJlc3Q8YnI+CjxhIGhyZWY9Ii9jb21w
b3NlP1RvPWRhdmVjYkBzcGFtY29wLm5ldCI+ZGF2ZWNiQHNwYW1jb3AubmV0PC9hPiAgICAgICAg
ICAgfCAgICAgICAgICAgICAgICAgICAgICAtLSBNYXJrIFR3YWluPGJyPgpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4KVG8gbWFuYWdlIHlvdXIgSVNP
QyBzdWJzY3JpcHRpb25zIG9yIHVuc3Vic2NyaWJlLDxicj4KcGxlYXNlIGxvZyBpbnRvIHRoZSBJ
U09DIE1lbWJlciBQb3J0YWw6PGJyPgo8YSBocmVmPSJodHRwczovL3BvcnRhbC5pc29jLm9yZy8i
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL3BvcnRhbC5pc29jLm9yZy88L2E+PGJyPgpUaGVuIGNo
b29zZSBJbnRlcmVzdHMgJmFtcDsgU3Vic2NyaXB0aW9ucyBmcm9tIHRoZSBNeSBBY2NvdW50IG1l
bnUuPGJyPgo8L2Rpdj4KCQkJCgkJCgkJPGJhc2UgdGFyZ2V0PSJfc2VsZiIgaHJlZj0iaHR0cHM6
Ly9lLm1haWwucnUvIj4KCTwvZGl2PgoKCQo8L2Rpdj4KCgoKPGJyPjxocj4KPGJyPtChINGD0LLQ
sNC20LXQvdC40LXQvCw8YnI+bW9oYW1tZWQgc2Vycmhpbmk8YnI+c2VycmhpbmlAbWFpbC5ydTxi
cj48L0JPRFk+PC9IVE1MPgo=

----ALT--RNFdTKlu1401657201--


From nobody Mon Jun  2 07:31:03 2014
Return-Path: <nd@syndicat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7A91A0221 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 07:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.152
X-Spam-Level: 
X-Spam-Status: No, score=-2.152 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 vauOTV14OmLA for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 07:30:58 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 34F371A02BA for <ietf@ietf.org>; Mon,  2 Jun 2014 07:30:57 -0700 (PDT)
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 4.82) (envelope-from <nd@syndicat.com>) id 1WrTGD-0000Ls-Ic; Mon, 02 Jun 2014 16:30:49 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcktIK37SXLP; Mon,  2 Jun 2014 16:30:49 +0200 (CEST)
Received: from p508c7938.dip0.t-ipconnect.de ([80.140.121.56] helo=gongo.localnet) by mail.syndicat.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Syndicat.com PostHamster 4.82) (envelope-from <nd@syndicat.com>) id 1WrTGD-0002dE-5s; Mon, 02 Jun 2014 16:30:49 +0200
From: Niels Dettenbach <nd@syndicat.com>
To: ietf@ietf.org, mohammed serrhini <serrhini@mail.ru>
Subject: Re: Fwd: Re: [Internet Policy] root justification for net neutrality?
Date: Mon, 02 Jun 2014 16:30:44 +0200
Message-ID: <1808188.hD4gOhDU5i@gongo>
Organization: Syndicat IT&Internet
User-Agent: KMail/4.12.2 (Linux/3.13.3-gentoo; KDE/4.12.2; x86_64; ; )
In-Reply-To: <1401657201.842471284@f416.i.mail.ru>
References: <1401657201.842471284@f416.i.mail.ru>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1969251.pzONnCdkW6"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/odXOEKuDuF89jOW1q1NXnSmeGwU
Cc: internetpolicy@elists.isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 14:31:01 -0000

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

Am Montag, 2. Juni 2014, 01:13:21 schrieb mohammed serrhini:
> the internet access must be free,  as the oxygen breathing, the propo=
sition
> that Internet could be provided as a public service and funded throug=
h
> taxes  is not very correct because  most part of the world population=

> suffers from taxes or already are  overtaxed, all of us know about th=
e
> quality of public services, =20

yes,

The comparation of oxygen and internet is often used in the "political =
scenes" =20
=2D far away from the reality of the internet and how it is working and=20=

organized until today - but just wrong for different reasons.

It is one of the dangerous, famous ideas today that a public service in=
ternet=20
(alias internet from government) would offer more "fairness" at all - o=
r at=20
least more "freedom", "security", "quality" etc.pp..

"Public Services" are not "free" nor "costless" - they just are service=
s=20
offered by a government, which has to be paid too - i.e. by taxes (as y=
ou=20
mention byself...). The only difference is, that a government can press=
=20
peoples to pay a services they don't want to use/buy - i.e. to let them=
 pay=20
for others who won't pay/work for that service.

Oxygen is a naturally available and "generated" ressource - at least un=
til=20
today - but even this is not correct anymore as there are countries who=
 are=20
let working / paying for oxygen ressource regeneration (i.e. over CO2=20=

certificates, laws about planting for oxygen consumption).


> nowadays most public services are privatized .
> in the end internet services will be reprivatized again.
Yes, but they are oligopolized to monopolized then - at least highly=20=

privileged, what distortes free markets what is by fact destruction of =
freedom=20
of each human. But who the hell today still want's "freedom" or such a=20=

thing...

Why should i pay for a product i won't use (because it doesnt fit my pe=
rsonal=20
needs)? Why should my government better know then me what kind of IP ac=
cesses=20
i want to buy and which not? Why should other providers with more speci=
al=20
product palettes offer their products in my region if users have to pay=
 double=20
for it? I remember perfectly the times here in germany where the "Telek=
om"=20
("Deutsche Post") was THE (monopolized) internet service - no one today=
 would=20
pay for such kind of a service if he still has the freedom to go otherw=
here.=20
But even today (with a "demonopolized" Telekom) they occupy many region=
s.

And why should i trust my government not to use their influence onto or=
=20
ownership of that service to spy me out like i.e. the StaSi does it wit=
h us?=20

The internet - by structure and history - is a network of "autonomous" =
private=20
rooms where private "room owners" are giving their users the ability to=
=20
connect to other users in other private rooms in a (usually bilateral)=20=

contractual relationship. Each room owner can decide if and how far thi=
s=20
interconnectivity goes while users can decide which of the private room=
s they=20
are using (or not using). Anyone who has the audience and the basic=20
infrastructure could request, allocate and use IP address space and=20
participate on that "inter network".

There was no government required to bring up the (real) internet to it'=
s=20
importance for the globe - the independence from Governments (contrary =
to i.e.=20
former ITU's network) was one of the main points for the success of tha=
t=20
network over other networks (even ITU ones). There is no tax, no public=
=20
internet service and no governmental internet security agency required =
to run=20
a proper internet into the future. All these governmental manipulations=
 will=20
destroy network neutrality and defect the users freedom as they does it=
 with=20
former networks.=20

There was nowhere more corruption, monopoly and "nfairness" then in the=
 old=20
global telephone networks which by fact governed mainly by governments.=



> I think there
> should be a tax on each internet financial transaction not on the cli=
ent
> side but on the side of companies,  we all days  heard about internet=
 money
>  and the expononcial number of bilion. peering is greet solution for
> reducing cost of internet.
Ah,
another one "who heard" something about "alotofmoney" which is not in h=
is=20
hands att...=20

Taxing based on the amount of transactions * transaction volume (* some=
 kind=20
of factor) is just one of the newest ideas of the new ideological polit=
ical to=20
bring more "fairness" and "humanity" to the "world". By fact this is no=
nsense.=20
Such a transaction tax will privilege the largest financial companies o=
ver=20
each smaller one by many reasons and not at least - EACH of that taxes =
have to=20
be PAID from someone at the "end" - usually the "client" as a consumer.=
 The=20
only comfortable for politicans is: the majority of their target audien=
ce of=20
voters did not are and will be aware of that.

This "robin hood syndrome" ("taking from the rich to give to the poor" =
=2D a=20
widely misunderstanding of the Robin Hood story where he taked it from =
the (by=20
governmentals) "priviledged" to give it to the "underprivileged", what =
is a=20
completely different thing) is very typical at the time where the last =
victims=20
of the great marxism and socialism experiments are dying away.=20

This leads - step by step - to a government controlled internet to brin=
g=20
"freedom", "neutrality", "security" and - not at least - more "fariness=
 to=20
all".=20

Georges Orwell's "animal farm" sends greetings...



cheers,


Niels.


=2D-=20
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
=20




--nextPart1969251.pzONnCdkW6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABCAAGBQJTjIqXAAoJEM78prARigUnQqMQAJqrWZ6+vswPY8cmazVge4zO
yUum8h1AawN896wF6VQH6tRfRKHfOR4FbY9uirRALbdXYYlMy1jjF8hBacv5ho3I
DHwtZLjqPVqvbBDpb196neRsgJhFsH/kp3xzXBrkmODKUjiNO835eEWIADx9/h/n
MDCDefSa/huupv4ZnRlx9LPfVYwK6lcJoQxLsQqBly0Hgh03liqzl2tFaD6ayn1L
2b86+xlY3NNIiM4Wg4gaJ7g5ikX5f3VdbcRv48Tj22gCMa2rvvGmNUY2fjv8mptP
GfdS935kMejeBQq79OM3xekEXfWc17uX8tqNlMvWPhaCmFiSyDY9cjBI+N2iq4wS
7OYqBELDK2EIighegYxUVSg54ABwjhyoIP1zyolR+uDeFEU+IxT0GBYcdJ2WjNcU
MvkJI1QWGOwhA9vjv74TpY2pXf4apcye1OQA3CMKIKpjplJPuLifvpmXpo+zzh0s
/6ioYhhbLXCvYIAr9uQ/9QeUvdjni3uzOkDkVSKw+9UJM0L08xSYfS7jn8RpSmcm
LacXkGi+vr8yWrKw3/yK+Dbpdsq1y+u1Pd5MTOwl64SGGVCy6CYYBXfvrY/nxF54
RhpX0gw0PvnT5yvEC9gTmFgSJq70BHtVNrA/iyUW2b3m/88G3Gf3CJPFN0pb/Io8
lQnbjbPdm8epVV7q3MNx
=T92n
-----END PGP SIGNATURE-----

--nextPart1969251.pzONnCdkW6--


From amelnaud@gmail.com  Sun Jun  1 15:53:43 2014
Return-Path: <amelnaud@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B814F1A00CF for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 15:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ILBuHOTZt-UF for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 15:53:40 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5942D1A00D4 for <ietf@ietf.org>; Sun,  1 Jun 2014 15:53:40 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id oz11so4368102veb.17 for <ietf@ietf.org>; Sun, 01 Jun 2014 15:53:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+CEMwf4dWnJosGH2a2++fwOWNcWu5SCPl5byMpIIQB4=; b=FKE3MulmMSsVHiouuL0nU/8US2bg01BOtX97JRbIJZjFQ06S0/brsZi0cMjvKuw+N6 J/gBCAv1x7CTuEafbOCJaNTAdNrYP5RP2jSPL+8q6E3I1lzzUgII/wxmetYZCfUqCofK 5/3cWXMqLtZbPdiiM0WLk7rinZOcdqptxUC+/Y+nm9QUKsLyKW6QddMocZQTxVqVc5Cg vjixk7vs5zLBGFhqo9rorANsQ9j0+Pzix81jBhKo5APggLr7TkRk6Pjj+ghd5QKmoWMW 5g7KtD1fIDnt+G9eB3VoYaiRzwbvObplN/QyCehIU3oeY8ju3Z3m6EaOodtRZ+SIWERJ M2NQ==
MIME-Version: 1.0
X-Received: by 10.220.174.137 with SMTP id t9mr27009974vcz.12.1401663214714; Sun, 01 Jun 2014 15:53:34 -0700 (PDT)
Received: by 10.58.134.46 with HTTP; Sun, 1 Jun 2014 15:53:34 -0700 (PDT)
In-Reply-To: <1401657201.842471284@f416.i.mail.ru>
References: <1401657201.842471284@f416.i.mail.ru>
Date: Sun, 1 Jun 2014 22:53:34 +0000
Message-ID: <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: Arnaud AMELINA <amelnaud@gmail.com>
To: mohammed serrhini <serrhini@mail.ru>
Content-Type: multipart/alternative; boundary=089e0149c5940205c604face263e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AMovMkjzj6VDTf3NVLstaCD_UYU
X-Mailman-Approved-At: Mon, 02 Jun 2014 07:35:32 -0700
Cc: internetpolicy@elists.isoc.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 22:56:12 -0000

--089e0149c5940205c604face263e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I totally agree with you Mohammed, if we do not want a bic=C3=A9phal intern=
et
with a Private party and another who will be free with perpetual war, as we
are seeing at the softwares, better leave things as they are. Each finding
its interest, without encroaching too far on the other's.

Arnaud A. A. AMELINA

ISOC-TOGO
West Africa


2014-06-01 21:13 GMT+00:00 mohammed serrhini <serrhini@mail.ru>:

>
> the internet access must be free, as the oxygen breathing, the
> proposition that Internet could be provided as a public service and funde=
d
> through taxes is not very correct because most part of the world
> population suffers from taxes or already are overtaxed, all of us know
> about the quality of public services, nowadays most public services are
> privatized. in the end internet services will be reprivatized again.
> I think there should be a tax on each internet financial transaction not
> on the client side but on the side of companies,  we all days  heard
> about internet money and the expononcial number of bilion.
> peering is greet solution for reducing cost of internet.
>
> Mohammed Serrhini
> Morocco chapter
>
> -------- =D0=9F=D0=B5=D1=80=D0=B5=D1=81=D1=8B=D0=BB=D0=B0=D0=B5=D0=BC=D0=
=BE=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B5 --------
> =D0=9E=D1=82 =D0=BA=D0=BE=D0=B3=D0=BE: David Collier-Brown <davec-b@roger=
s.com>
> =D0=9A=D0=BE=D0=BC=D1=83: internetpolicy@elists.isoc.org
> =D0=94=D0=B0=D1=82=D0=B0: Fri, 30 May 2014 20:38:32 -0400
> =D0=A2=D0=B5=D0=BC=D0=B0: Re: [Internet Policy] root justification for ne=
t neutrality?
>
>
>  May I speculate that access is cheap enough that it can be treated as a
> universal good, much like light-houses.
>
> Universals are beneficial to everyone, but cost so little per benefit
> that it's hard to figure out how to charge for them. Lighthouses are
> the classic example, and are the very first thing that the government of
> the United States built...
>
> --dave
>
>
> On 05/30/2014 11:21 AM, Richard Hill wrote:
> > Veni,
> >
> > That is great, but then I guess that my access is being subsidized by
> > Bulgarian users. Very generous of them.
> >
> > Best,
> > Richard
> >
> > ----- Original Message ----- From: "Veni Markovski" <veni@veni.com
> <https://e.mail.ru/compose?To=3Dveni@veni.com>>
> > To: "Richard Hill" <rhill@hill-a.ch
> <https://e.mail.ru/compose?To=3Drhill@hill%2da.ch>>; "Gary Wayne Kenward"
> > <garykenward@ieee.org
> <https://e.mail.ru/compose?To=3Dgarykenward@ieee.org>>; "Nick Ashton-Hart=
" <
> nashton@consensus.pro <https://e.mail.ru/compose?To=3Dnashton@consensus.p=
ro>
> >
> > Cc: <internetpolicy@elists.isoc.org
> <https://e.mail.ru/compose?To=3Dinternetpolicy@elists.isoc.org>>
> > Sent: Friday, May 30, 2014 5:19 PM
> > Subject: Re: [Internet Policy] root justification for net neutrality?
> >
> >
> >> Hi.
> >> See below slight correction.
> >>
> >> On 05/30/14 10:04, Richard Hill wrote:
> >>> I agree with Gary and partly with Nick.
> >>>
> >>> Upstream service providers are already paying to connect to the
> >>> Internet, but the question is whether they should pay more when what
> >>> they do imposes capacity upgrades downstream.
> >>>
> >>> TANSTAAFL (if you don't know that acronym, see
> >>> http://en.wikipedia.org/wiki/Tanstaafl )
> >>>
> >>> In the end, it is always us, the people who pay. The question is how
> >>> and how much. The Internet could be provided as a public service and
> >>> funded through taxes (or partly funded through taxes), or it can be
> >>> funded by flat-rate payments from users (the system most commonly
> >>> used today), or it could be funded by data-volume based payments from
> >>> users (a system used in some places), or it could be funded by some
> >>> combination of payments from users and upstream suppliers (often
> >>> called OTT).
> >>>
> >>
> >> Not always, Richard.
> >> Come to Sofia, Bulgaria, and login at any of the thousands free wi-fi
> >> locations. No passwords, no registration, not requirements (like in
> >> other EU countries) to give your personal data. Yes, the internet
> >> access could be also free.
> >>
> >>
> >>
> >> --
> >>
> >> Best,
> >> Veni Markovski
> >> http://www.veni.com
> >> https://www.facebook.com/venimarkovski
> >> https://twitter.com/veni
> >>
> >> The opinions expressed above are those of the
> >> author, not of any organizations, associated
> >> with or related to him in any given way.
> >>
> >>
> >
> > _______________________________________________
> > To manage your ISOC subscriptions or unsubscribe,
> > please log into the ISOC Member Portal:
> > https://portal.isoc.org/
> > Then choose Interests & Subscriptions from the My Account menu.
> >
>
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net <https://e.mail.ru/compose?To=3Ddavecb@spamcop.net> | =
--
> Mark Twain
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net <https://e.mail.ru/compose?To=3Ddavecb@spamcop.net> | =
--
> Mark Twain
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.
>
> ------------------------------
>
> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
> mohammed serrhini
> serrhini@mail.ru
>
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.
>

--089e0149c5940205c604face263e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><span id=3D"result_box" class=3D"" lang=3D"=
en"><span class=3D"">I totally</span> <span class=3D"">agree with you</span=
> <span class=3D"">Mohammed</span><span>,</span> <span class=3D"">if we do<=
/span> <span class=3D"">not want a</span> <span class=3D"">bic=C3=A9phal</s=
pan> <span class=3D"">internet</span> <span class=3D"">with</span> <span cl=
ass=3D"">a</span> <span class=3D"">Private</span> <span class=3D"">party</s=
pan> <span class=3D"">and another</span> <span class=3D"">who will be</span=
> <span class=3D"">free</span> with <span class=3D"">perpetual war</span><s=
pan>, as</span> <span class=3D"">we are seeing</span> <span class=3D"">at t=
he</span> <span class=3D"">software</span><span>s,</span> <span class=3D"">=
better leave</span> <span class=3D"">things</span> <span class=3D"">as they=
</span> <span class=3D"">are</span><span>.</span> <span class=3D"">Each</sp=
an> <span class=3D"">finding its</span> <span class=3D"">interest, without<=
/span> <span class=3D"">encroaching too far</span> <span class=3D"">on</spa=
n> <span class=3D"">the</span> <span class=3D"">other&#39;s.<br>
<br></span></span></div><span id=3D"result_box" class=3D"" lang=3D"en"><spa=
n class=3D"">Arnaud A. A. AMELINA<br><br></span></span></div><span id=3D"re=
sult_box" class=3D"" lang=3D"en"><span class=3D"">ISOC-TOGO<br></span></spa=
n></div><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"">Wes=
t Africa<br>
</span></span></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_=
quote">2014-06-01 21:13 GMT+00:00 mohammed serrhini <span dir=3D"ltr">&lt;<=
a href=3D"mailto:serrhini@mail.ru" target=3D"_blank">serrhini@mail.ru</a>&g=
t;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div><br>the internet access must be free, <span lang=3D"en"><span>as</span=
> <span>the</span> <span>oxygen</span> <span>breathing, the proposition tha=
t Internet could be provided as a public service and funded through taxes <=
/span></span><span lang=3D"en"><span>is not</span> <span>very correct</span=
> because <span>most</span> <span>part of the</span> <span>world</span> <sp=
an>population</span> <span>suffers from</span> <span>taxes</span> <span>or<=
/span> <span>already</span> are <span>overtaxed, all of us know about the q=
uality of public services, <span lang=3D"en"><span>nowadays</span> <span>mo=
st</span> <span>public</span> <span>services</span> <span>are</span> <span>=
privatized</span></span></span></span>. in the end internet services will b=
e reprivatized again.<br>
<span><span style=3D"background-color:#ffffff" title=3D"je pense qu&#39;il =
doit y avoir une taxe sur chaque transaction financiere non du cot=C3=A9 du=
 client mais du cot=C3=A9 des societ=C3=A9s qui font leurs benifices sur in=
ternet comme">I think there should be a tax on each internet financial tran=
saction not on the client side but on the side of companies,=C2=A0</span></=
span><span><span style=3D"background-color:#ffffff" title=3D"je pense qu&#3=
9;il doit y avoir une taxe sur chaque transaction financiere non du cot=C3=
=A9 du client mais du cot=C3=A9 des societ=C3=A9s qui font leurs benifices =
sur internet comme"> </span></span>we all days=C2=A0 heard about internet m=
oney  and the expononcial number of bilion. <br>
peering is greet solution for reducing cost of internet. <br><br>Mohammed S=
errhini <br>Morocco chapter<br><br>-------- =D0=9F=D0=B5=D1=80=D0=B5=D1=81=
=D1=8B=D0=BB=D0=B0=D0=B5=D0=BC=D0=BE=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=
=D0=B5=D0=BD=D0=B8=D0=B5 --------<br>
=D0=9E=D1=82 =D0=BA=D0=BE=D0=B3=D0=BE: David Collier-Brown &lt;<a href=3D"m=
ailto:davec-b@rogers.com" target=3D"_blank">davec-b@rogers.com</a>&gt;<br>
=D0=9A=D0=BE=D0=BC=D1=83: <a href=3D"mailto:internetpolicy@elists.isoc.org"=
 target=3D"_blank">internetpolicy@elists.isoc.org</a><br>

=D0=94=D0=B0=D1=82=D0=B0: Fri, 30 May 2014 20:38:32 -0400<br>
=D0=A2=D0=B5=D0=BC=D0=B0: Re: [Internet Policy] root justification for net =
neutrality?<div><div class=3D"h5"><br>
<br>

=09



   =20









=09
=09


=09
=09
=09
=09
=09

=09
=09

=09
=09



<div>
=09
 	<div>
	=09
	=09
			<div>May I speculate that access is cheap enough that it can be treated =
as a<br>
universal good, much like light-houses.<br>
<br>
Universals are beneficial to everyone, but cost so little per benefit<br>
that it&#39;s hard to figure out how to charge for them.  Lighthouses are<b=
r>
the classic example, and are the very first thing that the government of<br=
>
the United States built...<br>
<br>
--dave<br>
<br>
<br>
On 05/30/2014 11:21 AM, Richard Hill wrote:<br>
&gt; Veni,<br>
&gt; <br>
&gt; That is great, but then I guess that my access is being subsidized by<=
br>
&gt; Bulgarian users.  Very generous of them.<br>
&gt; <br>
&gt; Best,<br>
&gt; Richard<br>
&gt; <br>
&gt; ----- Original Message ----- From: &quot;Veni Markovski&quot; &lt;<a h=
ref=3D"https://e.mail.ru/compose?To=3Dveni@veni.com" target=3D"_blank">veni=
@veni.com</a>&gt;<br>
&gt; To: &quot;Richard Hill&quot; &lt;<a href=3D"https://e.mail.ru/compose?=
To=3Drhill@hill%2da.ch" target=3D"_blank">rhill@hill-a.ch</a>&gt;; &quot;Ga=
ry Wayne Kenward&quot;<br>
&gt; &lt;<a href=3D"https://e.mail.ru/compose?To=3Dgarykenward@ieee.org" ta=
rget=3D"_blank">garykenward@ieee.org</a>&gt;; &quot;Nick Ashton-Hart&quot; =
&lt;<a href=3D"https://e.mail.ru/compose?To=3Dnashton@consensus.pro" target=
=3D"_blank">nashton@consensus.pro</a>&gt;<br>

&gt; Cc: &lt;<a href=3D"https://e.mail.ru/compose?To=3Dinternetpolicy@elist=
s.isoc.org" target=3D"_blank">internetpolicy@elists.isoc.org</a>&gt;<br>
&gt; Sent: Friday, May 30, 2014 5:19 PM<br>
&gt; Subject: Re: [Internet Policy] root justification for net neutrality?<=
br>
&gt; <br>
&gt; <br>
&gt;&gt; Hi.<br>
&gt;&gt; See below slight correction.<br>
&gt;&gt;<br>
&gt;&gt; On 05/30/14 10:04, Richard Hill wrote:<br>
&gt;&gt;&gt; I agree with Gary and partly with Nick.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Upstream service providers are already paying to connect to th=
e<br>
&gt;&gt;&gt; Internet, but the question is whether they should pay more whe=
n what<br>
&gt;&gt;&gt; they do imposes capacity upgrades downstream.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; TANSTAAFL (if you don&#39;t know that acronym, see<br>
&gt;&gt;&gt; <a href=3D"http://en.wikipedia.org/wiki/Tanstaafl" target=3D"_=
blank">http://en.wikipedia.org/wiki/Tanstaafl</a> )<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; In the end, it is always us, the people who pay.  The question=
 is how<br>
&gt;&gt;&gt; and how much.  The Internet could be provided as a public serv=
ice and<br>
&gt;&gt;&gt; funded through taxes (or partly funded through taxes), or it c=
an be<br>
&gt;&gt;&gt; funded by flat-rate payments from users (the system most commo=
nly<br>
&gt;&gt;&gt; used today), or it could be funded by data-volume based paymen=
ts from<br>
&gt;&gt;&gt; users (a system used in some places), or it could be funded by=
 some<br>
&gt;&gt;&gt; combination of payments from users and upstream suppliers (oft=
en<br>
&gt;&gt;&gt; called OTT).<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Not always, Richard.<br>
&gt;&gt; Come to Sofia, Bulgaria, and login at any of the thousands free wi=
-fi<br>
&gt;&gt; locations. No passwords, no registration, not requirements (like i=
n<br>
&gt;&gt; other EU countries) to give your personal data. Yes, the internet<=
br>
&gt;&gt; access could be also free.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -- <br>
&gt;&gt;<br>
&gt;&gt; Best,<br>
&gt;&gt; Veni Markovski<br>
&gt;&gt; <a href=3D"http://www.veni.com" target=3D"_blank">http://www.veni.=
com</a><br>
&gt;&gt; <a href=3D"https://www.facebook.com/venimarkovski" target=3D"_blan=
k">https://www.facebook.com/venimarkovski</a><br>
&gt;&gt; <a href=3D"https://twitter.com/veni" target=3D"_blank">https://twi=
tter.com/veni</a><br>
&gt;&gt;<br>
&gt;&gt; The opinions expressed above are those of the<br>
&gt;&gt; author, not of any organizations, associated<br>
&gt;&gt; with or related to him in any given way.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; To manage your ISOC subscriptions or unsubscribe,<br>
&gt; please log into the ISOC Member Portal:<br>
&gt; <a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.=
isoc.org/</a><br>
&gt; Then choose Interests &amp; Subscriptions from the My Account menu.<br=
>
&gt; <br>
<br>
<br>
-- <br>
David Collier-Brown,         | Always do right. This will gratify<br>
System Programmer and Author | some people and astonish the rest<br>
<a href=3D"https://e.mail.ru/compose?To=3Ddavecb@spamcop.net" target=3D"_bl=
ank">davecb@spamcop.net</a>           |                      -- Mark Twain<=
br>
<br>
-- <br>
David Collier-Brown,         | Always do right. This will gratify<br>
System Programmer and Author | some people and astonish the rest<br>
<a href=3D"https://e.mail.ru/compose?To=3Ddavecb@spamcop.net" target=3D"_bl=
ank">davecb@spamcop.net</a>           |                      -- Mark Twain<=
br>
_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.=
org/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br>
</div>
		=09
	=09
	=09
	</div>

=09
</div>



<br></div></div><hr>
<br>=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,<br>moham=
med serrhini<br><a href=3D"mailto:serrhini@mail.ru" target=3D"_blank">serrh=
ini@mail.ru</a><br></div>
<br>_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.=
org/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br></bl=
ockquote></div><br></div>

--089e0149c5940205c604face263e--


From kelvin@skysys.co.ke  Sun Jun  1 16:14:01 2014
Return-Path: <kelvin@skysys.co.ke>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72CC21A00DA for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 16:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 9KtqaidzvCKr for <ietf@ietfa.amsl.com>; Sun,  1 Jun 2014 16:13:58 -0700 (PDT)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BD0E1A00DF for <ietf@ietf.org>; Sun,  1 Jun 2014 16:13:57 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id j15so1689638qaq.41 for <ietf@ietf.org>; Sun, 01 Jun 2014 16:13:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=82NnrVV/KgW58OoWXEk1iXmUbCq9k6d4WE5lNWZSIkY=; b=U73jVkw2iDH4BzQPkcq1QaD67WwbbmKhSNFkhjZAsVJfVQb4EH5l/976Gwf/pJbkd1 nGwxD7OOUKiPcdtnW1NKFM66exxZpa0LTLTHkBQkzP4zIkI9n3mW7HqhR61U+WfQEl9z OwQsCx6TdBXMwHZzs3TovmZFtSfJnm21DN/u7Etcj449toKGuihtnB8yp3UPUZSTGe5K fVvjzSqAhRzuaMqHcrzT0PlX+KaGdoAu1e6AMh/TLOKWVFe79t/DK2dKEpCPUrXva/Pj bdkceic5a5gFn9U//45jNSZuVIZxZ6wjLn5g91xzR5d9fnzysjJE986DFYKWeWQaOOc7 q1+w==
X-Gm-Message-State: ALoCoQmpqKKUaDsSuV/NF1ZnrlbxH6stD7vLzJbnZX0kT6NeCwdVmh+Sv2M2k2h5pq8gE2vcznYn
X-Received: by 10.140.29.226 with SMTP id b89mr41721645qgb.48.1401664432125; Sun, 01 Jun 2014 16:13:52 -0700 (PDT)
Received: from [100.251.102.115] ([172.56.22.230]) by mx.google.com with ESMTPSA id i9sm18483323qaq.14.2014.06.01.16.13.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Jun 2014 16:13:51 -0700 (PDT)
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-12D19DFE-423C-4CB5-8C57-795878B866E0
Content-Transfer-Encoding: 7bit
Message-Id: <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke>
X-Mailer: iPhone Mail (11D201)
From: Kelvin Githira <kelvin@skysys.co.ke>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
Date: Sun, 1 Jun 2014 19:13:49 -0400
To: Arnaud AMELINA <amelnaud@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/k8moDc5DE64nzbB671NzXKD2nJw
X-Mailman-Approved-At: Mon, 02 Jun 2014 07:43:12 -0700
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 23:17:36 -0000

--Apple-Mail-12D19DFE-423C-4CB5-8C57-795878B866E0
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

I foresee it being optional.=20

Some will preffer it being free , while some who can will prefer to pay for i=
t.=20

A free sevice will have its cons while a paid service will center on its pro=
s

i.e value for quality.=20

Focus should primariry be at this point internet for all.

Sent using 100% recycled electrons on a tiny keyboard. Please excuse typos a=
nd brevity

> On Jun 1, 2014, at 6:53 PM, Arnaud AMELINA <amelnaud@gmail.com> wrote:
>=20
> I totally agree with you Mohammed, if we do not want a bic=C3=A9phal inter=
net with a Private party and another who will be free with perpetual war, as=
 we are seeing at the softwares, better leave things as they are. Each findi=
ng its interest, without encroaching too far on the other's.
>=20
> Arnaud A. A. AMELINA
>=20
> ISOC-TOGO
> West Africa
>=20
>=20
> 2014-06-01 21:13 GMT+00:00 mohammed serrhini <serrhini@mail.ru>:
>>=20
>> the internet access must be free, as the oxygen breathing, the propositio=
n that Internet could be provided as a public service and funded through tax=
es is not very correct because most part of the world population suffers fro=
m taxes or already are overtaxed, all of us know about the quality of public=
 services, nowadays most public services are privatized. in the end internet=
 services will be reprivatized again.
>> I think there should be a tax on each internet financial transaction not o=
n the client side but on the side of companies,  we all days  heard about in=
ternet money and the expononcial number of bilion.=20
>> peering is greet solution for reducing cost of internet.=20
>>=20
>> Mohammed Serrhini=20
>> Morocco chapter
>>=20
>> -------- =D0=9F=D0=B5=D1=80=D0=B5=D1=81=D1=8B=D0=BB=D0=B0=D0=B5=D0=BC=D0=BE=
=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B5 --------
>> =D0=9E=D1=82 =D0=BA=D0=BE=D0=B3=D0=BE: David Collier-Brown <davec-b@roger=
s.com>
>> =D0=9A=D0=BE=D0=BC=D1=83: internetpolicy@elists.isoc.org
>> =D0=94=D0=B0=D1=82=D0=B0: Fri, 30 May 2014 20:38:32 -0400
>> =D0=A2=D0=B5=D0=BC=D0=B0: Re: [Internet Policy] root justification for ne=
t neutrality?
>>=20
>>=20
>> May I speculate that access is cheap enough that it can be treated as a
>> universal good, much like light-houses.
>>=20
>> Universals are beneficial to everyone, but cost so little per benefit
>> that it's hard to figure out how to charge for them. Lighthouses are
>> the classic example, and are the very first thing that the government of
>> the United States built...
>>=20
>> --dave
>>=20
>>=20
>> On 05/30/2014 11:21 AM, Richard Hill wrote:
>> > Veni,
>> >=20
>> > That is great, but then I guess that my access is being subsidized by
>> > Bulgarian users. Very generous of them.
>> >=20
>> > Best,
>> > Richard
>> >=20
>> > ----- Original Message ----- From: "Veni Markovski" <veni@veni.com>
>> > To: "Richard Hill" <rhill@hill-a.ch>; "Gary Wayne Kenward"
>> > <garykenward@ieee.org>; "Nick Ashton-Hart" <nashton@consensus.pro>
>> > Cc: <internetpolicy@elists.isoc.org>
>> > Sent: Friday, May 30, 2014 5:19 PM
>> > Subject: Re: [Internet Policy] root justification for net neutrality?
>> >=20
>> >=20
>> >> Hi.
>> >> See below slight correction.
>> >>
>> >> On 05/30/14 10:04, Richard Hill wrote:
>> >>> I agree with Gary and partly with Nick.
>> >>>
>> >>> Upstream service providers are already paying to connect to the
>> >>> Internet, but the question is whether they should pay more when what
>> >>> they do imposes capacity upgrades downstream.
>> >>>
>> >>> TANSTAAFL (if you don't know that acronym, see
>> >>> http://en.wikipedia.org/wiki/Tanstaafl )
>> >>>
>> >>> In the end, it is always us, the people who pay. The question is how
>> >>> and how much. The Internet could be provided as a public service and
>> >>> funded through taxes (or partly funded through taxes), or it can be
>> >>> funded by flat-rate payments from users (the system most commonly
>> >>> used today), or it could be funded by data-volume based payments from=

>> >>> users (a system used in some places), or it could be funded by some
>> >>> combination of payments from users and upstream suppliers (often
>> >>> called OTT).
>> >>>
>> >>
>> >> Not always, Richard.
>> >> Come to Sofia, Bulgaria, and login at any of the thousands free wi-fi
>> >> locations. No passwords, no registration, not requirements (like in
>> >> other EU countries) to give your personal data. Yes, the internet
>> >> access could be also free.
>> >>
>> >>
>> >>
>> >> --=20
>> >>
>> >> Best,
>> >> Veni Markovski
>> >> http://www.veni.com
>> >> https://www.facebook.com/venimarkovski
>> >> https://twitter.com/veni
>> >>
>> >> The opinions expressed above are those of the
>> >> author, not of any organizations, associated
>> >> with or related to him in any given way.
>> >>
>> >>
>> >=20
>> > _______________________________________________
>> > To manage your ISOC subscriptions or unsubscribe,
>> > please log into the ISOC Member Portal:
>> > https://portal.isoc.org/
>> > Then choose Interests & Subscriptions from the My Account menu.
>> >=20
>>=20
>>=20
>> --=20
>> David Collier-Brown, | Always do right. This will gratify
>> System Programmer and Author | some people and astonish the rest
>> davecb@spamcop.net | -- Mark Twain
>>=20
>> --=20
>> David Collier-Brown, | Always do right. This will gratify
>> System Programmer and Author | some people and astonish the rest
>> davecb@spamcop.net | -- Mark Twain
>> _______________________________________________
>> To manage your ISOC subscriptions or unsubscribe,
>> please log into the ISOC Member Portal:
>> https://portal.isoc.org/
>> Then choose Interests & Subscriptions from the My Account menu.
>>=20
>>=20
>> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
>> mohammed serrhini
>> serrhini@mail.ru
>>=20
>> _______________________________________________
>> To manage your ISOC subscriptions or unsubscribe,
>> please log into the ISOC Member Portal:
>> https://portal.isoc.org/
>> Then choose Interests & Subscriptions from the My Account menu.
>=20
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.

--Apple-Mail-12D19DFE-423C-4CB5-8C57-795878B866E0
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>I foresee it being optional.&nbsp;</di=
v><div><br></div><div>Some will preffer it being free , while some who can w=
ill prefer to pay for it.&nbsp;</div><div><br></div><div>A free sevice will h=
ave its cons while a paid service will center on its pros</div><div><br></di=
v><div>i.e value for quality.&nbsp;</div><div><br></div><div>Focus should pr=
imariry be at this point internet for all.<br><br>Sent <span style=3D"backgr=
ound-color: rgba(255, 255, 255, 0);">using 100% recycled electrons on a tiny=
 keyboard. Please excuse typos and brevity</span></div><div><br>On Jun 1, 20=
14, at 6:53 PM, Arnaud AMELINA &lt;<a href=3D"mailto:amelnaud@gmail.com">ame=
lnaud@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><=
div dir=3D"ltr"><div><div><div><span id=3D"result_box" class=3D"" lang=3D"en=
"><span class=3D"">I totally</span> <span class=3D"">agree with you</span> <=
span class=3D"">Mohammed</span><span>,</span> <span class=3D"">if we do</spa=
n> <span class=3D"">not want a</span> <span class=3D"">bic=C3=A9phal</span> <=
span class=3D"">internet</span> <span class=3D"">with</span> <span class=3D"=
">a</span> <span class=3D"">Private</span> <span class=3D"">party</span> <sp=
an class=3D"">and another</span> <span class=3D"">who will be</span> <span c=
lass=3D"">free</span> with <span class=3D"">perpetual war</span><span>, as</=
span> <span class=3D"">we are seeing</span> <span class=3D"">at the</span> <=
span class=3D"">software</span><span>s,</span> <span class=3D"">better leave=
</span> <span class=3D"">things</span> <span class=3D"">as they</span> <span=
 class=3D"">are</span><span>.</span> <span class=3D"">Each</span> <span clas=
s=3D"">finding its</span> <span class=3D"">interest, without</span> <span cl=
ass=3D"">encroaching too far</span> <span class=3D"">on</span> <span class=3D=
"">the</span> <span class=3D"">other's.<br>
<br></span></span></div><span id=3D"result_box" class=3D"" lang=3D"en"><span=
 class=3D"">Arnaud A. A. AMELINA<br><br></span></span></div><span id=3D"resu=
lt_box" class=3D"" lang=3D"en"><span class=3D"">ISOC-TOGO<br></span></span><=
/div><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"">West Af=
rica<br>
</span></span></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_q=
uote">2014-06-01 21:13 GMT+00:00 mohammed serrhini <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:serrhini@mail.ru" target=3D"_blank">serrhini@mail.ru</a>&gt;</=
span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
<div><br>the internet access must be free, <span lang=3D"en"><span>as</span>=
 <span>the</span> <span>oxygen</span> <span>breathing, the proposition that I=
nternet could be provided as a public service and funded through taxes </spa=
n></span><span lang=3D"en"><span>is not</span> <span>very correct</span> bec=
ause <span>most</span> <span>part of the</span> <span>world</span> <span>pop=
ulation</span> <span>suffers from</span> <span>taxes</span> <span>or</span> <=
span>already</span> are <span>overtaxed, all of us know about the quality of=
 public services, <span lang=3D"en"><span>nowadays</span> <span>most</span> <=
span>public</span> <span>services</span> <span>are</span> <span>privatized</=
span></span></span></span>. in the end internet services will be reprivatize=
d again.<br>
<span><span style=3D"background-color:#ffffff" title=3D"je pense qu'il doit y=
 avoir une taxe sur chaque transaction financiere non du cot=C3=A9 du client=
 mais du cot=C3=A9 des societ=C3=A9s qui font leurs benifices sur internet c=
omme">I think there should be a tax on each internet financial transaction n=
ot on the client side but on the side of companies,&nbsp;</span></span><span=
><span style=3D"background-color:#ffffff" title=3D"je pense qu'il doit y avo=
ir une taxe sur chaque transaction financiere non du cot=C3=A9 du client mai=
s du cot=C3=A9 des societ=C3=A9s qui font leurs benifices sur internet comme=
"> </span></span>we all days&nbsp; heard about internet money  and the expon=
oncial number of bilion. <br>
peering is greet solution for reducing cost of internet. <br><br>Mohammed Se=
rrhini <br>Morocco chapter<br><br>-------- =D0=9F=D0=B5=D1=80=D0=B5=D1=81=D1=
=8B=D0=BB=D0=B0=D0=B5=D0=BC=D0=BE=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=
=D0=BD=D0=B8=D0=B5 --------<br>
=D0=9E=D1=82 =D0=BA=D0=BE=D0=B3=D0=BE: David Collier-Brown &lt;<a href=3D"ma=
ilto:davec-b@rogers.com" target=3D"_blank">davec-b@rogers.com</a>&gt;<br>
=D0=9A=D0=BE=D0=BC=D1=83: <a href=3D"mailto:internetpolicy@elists.isoc.org" t=
arget=3D"_blank">internetpolicy@elists.isoc.org</a><br>

=D0=94=D0=B0=D1=82=D0=B0: Fri, 30 May 2014 20:38:32 -0400<br>
=D0=A2=D0=B5=D0=BC=D0=B0: Re: [Internet Policy] root justification for net n=
eutrality?<div><div class=3D"h5"><br>
<br>

=09



   =20









=09
=09


=09
=09
=09
=09
=09

=09
=09

=09
=09



<div>
=09
 	<div>
	=09
	=09
			<div>May I speculate that access is cheap enough th=
at it can be treated as a<br>
universal good, much like light-houses.<br>
<br>
Universals are beneficial to everyone, but cost so little per benefit<br>
that it's hard to figure out how to charge for them.  Lighthouses are<br>
the classic example, and are the very first thing that the government of<br>=

the United States built...<br>
<br>
--dave<br>
<br>
<br>
On 05/30/2014 11:21 AM, Richard Hill wrote:<br>
&gt; Veni,<br>
&gt; <br>
&gt; That is great, but then I guess that my access is being subsidized by<b=
r>
&gt; Bulgarian users.  Very generous of them.<br>
&gt; <br>
&gt; Best,<br>
&gt; Richard<br>
&gt; <br>
&gt; ----- Original Message ----- From: "Veni Markovski" &lt;<a href=3D"http=
s://e.mail.ru/compose?To=3Dveni@veni.com" target=3D"_blank">veni@veni.com</a=
>&gt;<br>
&gt; To: "Richard Hill" &lt;<a href=3D"https://e.mail.ru/compose?To=3Drhill@=
hill%2da.ch" target=3D"_blank">rhill@hill-a.ch</a>&gt;; "Gary Wayne Kenward"=
<br>
&gt; &lt;<a href=3D"https://e.mail.ru/compose?To=3Dgarykenward@ieee.org" tar=
get=3D"_blank">garykenward@ieee.org</a>&gt;; "Nick Ashton-Hart" &lt;<a href=3D=
"https://e.mail.ru/compose?To=3Dnashton@consensus.pro" target=3D"_blank">nas=
hton@consensus.pro</a>&gt;<br>

&gt; Cc: &lt;<a href=3D"https://e.mail.ru/compose?To=3Dinternetpolicy@elists=
.isoc.org" target=3D"_blank">internetpolicy@elists.isoc.org</a>&gt;<br>
&gt; Sent: Friday, May 30, 2014 5:19 PM<br>
&gt; Subject: Re: [Internet Policy] root justification for net neutrality?<b=
r>
&gt; <br>
&gt; <br>
&gt;&gt; Hi.<br>
&gt;&gt; See below slight correction.<br>
&gt;&gt;<br>
&gt;&gt; On 05/30/14 10:04, Richard Hill wrote:<br>
&gt;&gt;&gt; I agree with Gary and partly with Nick.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Upstream service providers are already paying to connect to the=
<br>
&gt;&gt;&gt; Internet, but the question is whether they should pay more when=
 what<br>
&gt;&gt;&gt; they do imposes capacity upgrades downstream.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; TANSTAAFL (if you don't know that acronym, see<br>
&gt;&gt;&gt; <a href=3D"http://en.wikipedia.org/wiki/Tanstaafl" target=3D"_b=
lank">http://en.wikipedia.org/wiki/Tanstaafl</a> )<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; In the end, it is always us, the people who pay.  The question i=
s how<br>
&gt;&gt;&gt; and how much.  The Internet could be provided as a public servi=
ce and<br>
&gt;&gt;&gt; funded through taxes (or partly funded through taxes), or it ca=
n be<br>
&gt;&gt;&gt; funded by flat-rate payments from users (the system most common=
ly<br>
&gt;&gt;&gt; used today), or it could be funded by data-volume based payment=
s from<br>
&gt;&gt;&gt; users (a system used in some places), or it could be funded by s=
ome<br>
&gt;&gt;&gt; combination of payments from users and upstream suppliers (ofte=
n<br>
&gt;&gt;&gt; called OTT).<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Not always, Richard.<br>
&gt;&gt; Come to Sofia, Bulgaria, and login at any of the thousands free wi-=
fi<br>
&gt;&gt; locations. No passwords, no registration, not requirements (like in=
<br>
&gt;&gt; other EU countries) to give your personal data. Yes, the internet<b=
r>
&gt;&gt; access could be also free.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -- <br>
&gt;&gt;<br>
&gt;&gt; Best,<br>
&gt;&gt; Veni Markovski<br>
&gt;&gt; <a href=3D"http://www.veni.com" target=3D"_blank">http://www.veni.c=
om</a><br>
&gt;&gt; <a href=3D"https://www.facebook.com/venimarkovski" target=3D"_blank=
">https://www.facebook.com/venimarkovski</a><br>
&gt;&gt; <a href=3D"https://twitter.com/veni" target=3D"_blank">https://twit=
ter.com/veni</a><br>
&gt;&gt;<br>
&gt;&gt; The opinions expressed above are those of the<br>
&gt;&gt; author, not of any organizations, associated<br>
&gt;&gt; with or related to him in any given way.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; To manage your ISOC subscriptions or unsubscribe,<br>
&gt; please log into the ISOC Member Portal:<br>
&gt; <a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.i=
soc.org/</a><br>
&gt; Then choose Interests &amp; Subscriptions from the My Account menu.<br>=

&gt; <br>
<br>
<br>
-- <br>
David Collier-Brown,         | Always do right. This will gratify<br>
System Programmer and Author | some people and astonish the rest<br>
<a href=3D"https://e.mail.ru/compose?To=3Ddavecb@spamcop.net" target=3D"_bla=
nk">davecb@spamcop.net</a>           |                      -- Mark Twain<br=
>
<br>
-- <br>
David Collier-Brown,         | Always do right. This will gratify<br>
System Programmer and Author | some people and astonish the rest<br>
<a href=3D"https://e.mail.ru/compose?To=3Ddavecb@spamcop.net" target=3D"_bla=
nk">davecb@spamcop.net</a>           |                      -- Mark Twain<br=
>
_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.o=
rg/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br>
</div>
		=09
	=09
	=09
	</div>

=09
</div>



<br></div></div><hr>
<br>=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,<br>mohamm=
ed serrhini<br><a href=3D"mailto:serrhini@mail.ru" target=3D"_blank">serrhin=
i@mail.ru</a><br></div>
<br>_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.o=
rg/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br></blo=
ckquote></div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>To manage your ISOC subscription=
s or unsubscribe,</span><br><span>please log into the ISOC Member Portal:</s=
pan><br><span><a href=3D"https://portal.isoc.org/">https://portal.isoc.org/<=
/a></span><br><span>Then choose Interests &amp; Subscriptions from the My Ac=
count menu.</span></div></blockquote></body></html>=

--Apple-Mail-12D19DFE-423C-4CB5-8C57-795878B866E0--


From nobody Mon Jun  2 07:45:42 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E3C1A00AA; Sun,  1 Jun 2014 15:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 p0Ip3OL5IIGZ; Sun,  1 Jun 2014 15:02:50 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3F531A0097; Sun,  1 Jun 2014 15:02:49 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id jw12so4301715veb.6 for <multiple recipients>; Sun, 01 Jun 2014 15:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=ZLRO0/RIO56RwmstCmol+3YTYMXUG/RONLxBx3bLkC8=; b=gvpksA3lx30ZcAXoQXKmExES8VmFBK4rvsepd7bd+ljMI+9+ER4SDcpQHK09Yp5I+T JjVTDstoXyBfXch9NwOAHZN46R4JrpEssneQ+GOVL7WpW11OJP4Bz/9u081Va9nCpy7D ONv4nqSZ5+7dP1nkMLE5fWfkgCMRTnf6WiI2H4W0d23+DFy56Yt8ncBiN2c82dxZInXJ 1rNqGAoTalFgXJhkss8v3wawNasToxnXs7UGemYA1Rv9KNZ4rzKNPe2GlLkf4B2EgABC 1m1w8EAL8chaVIMzz2YRrPyVm4UDt8QnWeb0SX9Pc7Gc4prQML0gEXuWdbGJw25N2yhs 9Wzw==
MIME-Version: 1.0
X-Received: by 10.58.56.71 with SMTP id y7mr26717607vep.24.1401660164031; Sun, 01 Jun 2014 15:02:44 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Sun, 1 Jun 2014 15:02:43 -0700 (PDT)
Date: Mon, 2 Jun 2014 01:02:43 +0300
Message-ID: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
Subject: LLN Plugfest at IETF 90
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b3a9b742ce9d904facd703b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nJHLJsEWLrmmlpiI3rnGkS0qCCw
X-Mailman-Approved-At: Mon, 02 Jun 2014 07:45:38 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, 6tisch-security@ietf.org, lwip@ietf.org, roll <roll@ietf.org>, ace@ietf.org, dtls-iot@ietf.org, Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>, coman@ietf.org, core@ietf.org, 6lo@ietf.org, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 22:02:53 -0000

--047d7b3a9b742ce9d904facd703b
Content-Type: text/plain; charset=UTF-8

Dear all,

We would like to announce the plugfest event at the 90th IETF Meeting in
Toronto.

We call for participants. The deadline to receive topics to present or
demonstrate in the event is 06/13/2014. Interested audience is also welcome
and we encourage audience to participate in the feedback session.

Please find next the plugfest information.

We hope to see you there!

Xavier and Ines.

-----------------------
Low Power and Lossy Networks plugfest at IETF90

The IETF 6TiSCH <https://datatracker.ietf.org/wg/6tisch/charter/>, IETF 6lo
<https://datatracker.ietf.org/wg/6lo/charter/> and IETF ROLL
<https://datatracker.ietf.org/wg/roll/charter/> working groups are hosting
an informal "plugfest" event at the IETF90 meeting, in Toronto, CA, during
the week of July 20-25 2014.
Goals

The goal of this event is to bring together people interested in hands-on
experience around the technology developed by the 6TiSCH, 6lo and ROLL
working groups, with a particular focus on the TSCH mode of IEEE802.15.4e,
6lowpan, RPL and new WG specifications.
When and where ?

   - *Date*: Sunday July 20 2014, 0900-1300 EDT.
   - *Location*: Meeting Room TBD, Fairmont Royal York Hotel 100 Front
   Street W, Toronto, CA.

*Early access: TBD if the plugfest room will be open starting 8am EDT on
Sunday 20 2014 to allow people to set up.*
Topology proposed - TBD

   - Star topology
   - IPv6

Complementary angles

This event will feature the following complementary angles:

   - Interoperation
   - Demonstration
   - Tools

Focus 1: Interoperation

Download the interoperation guidelines:

   - - TBD for Toronto - interoperation guidelines, version 1 (London)
   <https://bitbucket.org/6tisch/meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_guidelines_v01.pdf>

The goal is to achieve interoperation between different hardware and
software implementations on the different aspects addressed by 6lo, 6TiSCH
and ROLL WGs. This include 6TiSCH minimal draft implementation,
demonstrating TSCH synchronization and OF0 for RPL on a minimal network.
6lowpan to demostrate cross link layer inter-operability by means of
bridges or backbones routers. Storing and non-storing RPL implementation
including its coexistance in different sub-networks.

The focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH
drafts implementations, including but not limited to: e.g. - 6TiSCH minimal
draft: http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00. - TBD

Participants are encouraged to bring devices which implement parts or all
of the listed drafts.

Levels of interoperation are proposed:

   - *Level 1*, star topology. A single BBR devices acts as the time source
   neighbor for all other nodes. Nodes need to demonstrate frame-based and
   acknowledgement-based synchronization. The static TSCH schedule, as well as
   all slot timings are taken from draft-ietf-6tisch-minimal-00.
   - *Level 2*, multi-hop topology. This level builds upon level 1. The
   goal of this level is full compliance to draft-ietf-6tisch-minimal-00,
   including multi-hop routing (RPL).
   - *Level 3*, on-the-fly scheduling. [optional] Preliminary
   implementations of
   http://tools.ietf.org/html/draft-dujovne-6tisch-on-the-fly can be shown.
   - *Level 4*, drafts from ROLL, such as:
   draft-ietf-roll-mpl-parameter-configuration,
   draft-ko-roll-mix-network-pathology, Opportunistic routing, selective DIS,
   and others that participants want to show
   - *Level 5*, drafts from 6lo, such as: draft-ietf-6lo-btle,
   draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz, and others that participants
   want to show.
   - *Level 6* Other drafts, such as draft-thubert-6man-flow-label-for-rpl,
   etc.

Focus 2: Demonstration

Participants are encouraged to bring devices and technology based on
6TiSCH, 6lo and ROLL which they believe can be of interest for the other
participants. These devices may or may not participate in the
interoperation event. Demonstration of more complete systems are
encouraged, for example systems which show the interconnection of a 6TiSCH
based mesh to traditional networks.
Focus 3: Tools

Participants are encouraged to bring and present different tools developed
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not
limited to:

   - acquisition devices (i.e. "sniffers")
   - packet analysis tools (e.g. Wireshark)
   - simulation/emulation platforms

Important Dates

The preparation of this event will be held during a portion of the
bi-weekly 6TiSCH call (*To Be Decided how and when!!!*). In particular:

   - *06/02/2014* Announcement of the plugfest event to the WG/ML related
   with constrained devices, such as: 6tisch, 6lo, roll, core, lwig, dtls-iot,
   coman, ace, etc.
   - *06/06/2014* Adoption of the plugfest call by the WGs, and call for
   participants at each group.
   - *06/02/2014-06/13/2014* Participants have contacted the plugfest
   chairs (Xavier or Ines) with a tentative description of what they wish to
   participate in.
   - *06/20/2014* Synchronization point 1. Participants can share the state
   of advancement of the implementation and raise blocking points.
   - *07/11/2014* Synchronization point 2. Participants can share the state
   of advancement of the implementation and raise blocking points.
   - *07/20/2014*. Plugfest at IETF90.

Tentative Agenda from 9:00 to 13:00

   - *[09.00]* Welcome and Initial Instructions
   - *[09.05]* Participants Pitch (5 min per Participant)
   - *[09.45]* Participants Pitch Tools (5 min per Participant)
   - *[10.15]* Interoperation (Islands)
   - *[11.50]* Feedback and open discussion.
   - *[12.40]* Acknowledgements and Plugfest End

For More Information

   - *Contact*: Xavi Vilajosana xvilajosana@eecs.berkeley.edu - Ines Robles
   mariainesrobles@gmail.com

Note Well

This event is organized as part of the IETF90 standardization meeting. You
need to register to the IETF90 conference to be able to participate. Daily
passes are available. The IETF Note Well applies to this plugfest, see
http://www.ietf.org/about/note-well.html.
About

The IETF 6TiSCH working group standardizes mechanisms focusing on enabling
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the
charter at http://datatracker.ietf.org/wg/6tisch/charter/, which also
contains links to the mailing list and the Internet-Drafts published by the
group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is
open, and is subject to the IETF Note Well.

The IETF 6lo working group focuses on the work that facilitates IPv6
connectivity over constrained node networks with the characteristics of:
limited power, memory and processing resources;. You can access the charter
at https://datatracker.ietf.org/wg/6lo/charter/, which also contains links
to the mailing list and the I-D published by the group.

The IETF ROLL working group is focused on routing issues for LLN (Low Power
and Lossy Networks), in IPv6 routing architectural framework for the
industrial, connected home, building and urban sensor networks application
scenarios. You can access the charter at
https://datatracker.ietf.org/wg/roll/charter/, which also contains links to
the mailing list and the I-D published by the group.

--047d7b3a9b742ce9d904facd703b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><span style=3D"font-family:arial,helvetica,sans-=
serif;color:rgb(0,0,0)">Dear all,</span><br></div><font face=3D"arial, helv=
etica, sans-serif"><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(=
0,0,0)">We would like to announce the plugfest event at the 90th IETF Meeti=
ng in Toronto.</span></font><div>

<span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif=
"><br></font></span></div></div><div><span style=3D"color:rgb(0,0,0)"><font=
 face=3D"arial, helvetica, sans-serif">We call for participants. The deadli=
ne to receive topics to present or demonstrate in the event is 06/13/2014. =
Interested audience is also welcome and we encourage audience to participat=
e in the feedback session.</font></span></div>

<div><div><span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, =
sans-serif"><br></font></span></div><div><span style=3D"color:rgb(0,0,0)"><=
font face=3D"arial, helvetica, sans-serif">Please find next the plugfest in=
formation.=C2=A0</font></span><div>

<font face=3D"arial, helvetica, sans-serif"><br></font></div><div><span sty=
le=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif">We hope=
 to see you there!</font></span><div><font color=3D"#000000" face=3D"arial,=
 helvetica, sans-serif"><br>

</font></div><div><div style=3D"color:rgb(0,0,0)"><font face=3D"arial, helv=
etica, sans-serif">Xavier and Ines.</font></div></div></div></div><div styl=
e=3D"font-family:&#39;Times New Roman&#39;;font-size:13px;color:rgb(0,0,0)"=
>
<font size=3D"3"><br>
</font></div><div style=3D"font-family:&#39;Times New Roman&#39;;font-size:=
13px;color:rgb(0,0,0)"><font size=3D"3">-----------------------</font></div=
><div><h1 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-si=
ze:24px;margin:20px 0px 10px;padding:0px;font-weight:normal;line-height:1.2=
5">

Low Power and Lossy Networks plugfest at IETF90</h1><p style=3D"color:rgb(5=
1,51,51);font-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;pa=
dding:0px;word-wrap:break-word;line-height:20px">The=C2=A0<a href=3D"https:=
//datatracker.ietf.org/wg/6tisch/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6TiSCH</a>,=C2=A0<a href=3D"htt=
ps://datatracker.ietf.org/wg/6lo/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6lo</a>=C2=A0and=C2=A0<a href=
=3D"https://datatracker.ietf.org/wg/roll/charter/" style=3D"color:rgb(59,11=
5,175);text-decoration:none" target=3D"_blank">IETF ROLL</a>=C2=A0working g=
roups are hosting an informal &quot;plugfest&quot; event at the IETF90 meet=
ing, in Toronto, CA, during the week of July 20-25 2014.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Goals=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">

The goal of this event is to bring together people interested in hands-on e=
xperience around the technology developed by the 6TiSCH, 6lo and ROLL worki=
ng groups, with a particular focus on the TSCH mode of IEEE802.15.4e, 6lowp=
an, RPL and new WG specifications.</p>

<h3 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:18p=
x;margin:20px 0px 0px;padding:0px;line-height:1.3888888888888888;font-weigh=
t:normal">When and where ?</h3><ul style=3D"color:rgb(51,51,51);font-family=
:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>Date</strong>: Sunday July 20 20=
14, 0900-1300 EDT.</li><li style=3D"word-wrap:break-word"><strong>Location<=
/strong>: Meeting Room TBD, Fairmont Royal York Hotel 100 Front Street W, T=
oronto, CA.</li>

</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
"><strong>Early access: TBD if the plugfest room will be open starting 8am =
EDT on Sunday 20 2014 to allow people to set up.</strong></p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Topol=
ogy proposed - TBD</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,s=
ans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word">Star topology</li><li style=3D"word-wrap=
:break-word">IPv6</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Ari=
al,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:no=
rmal;line-height:1.5">

Complementary angles</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,=
sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-w=
ord;line-height:20px">This event will feature the following complementary a=
ngles:</p>

<ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14p=
x;margin:10px 0px 0px;line-height:20px"><li style=3D"word-wrap:break-word">=
Interoperation</li><li style=3D"word-wrap:break-word">Demonstration</li><li=
 style=3D"word-wrap:break-word">

Tools</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-seri=
f;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-he=
ight:1.5">Focus 1: Interoperation</h2>
<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Dow=
nload the interoperation guidelines:</p><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px">

<li style=3D"word-wrap:break-word"><a href=3D"https://bitbucket.org/6tisch/=
meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_gui=
delines_v01.pdf" style=3D"color:rgb(59,115,175);text-decoration:none" targe=
t=3D"_blank"> - TBD for Toronto - interoperation guidelines, version 1 (Lon=
don)</a></li>

</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">The goal is to achieve interoperation between different hardware and soft=
ware implementations on the different aspects addressed by 6lo, 6TiSCH and =
ROLL WGs. This include 6TiSCH minimal draft implementation, demonstrating T=
SCH synchronization and OF0 for RPL on a minimal network. 6lowpan to demost=
rate cross link layer inter-operability by means of bridges or backbones ro=
uters. Storing and non-storing RPL implementation including its coexistance=
 in different sub-networks.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH draft=
s implementations, including but not limited to: e.g. - 6TiSCH minimal draf=
t:=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00"=
 rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00</a>. =
- TBD</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Par=
ticipants are encouraged to bring devices which implement parts or all of t=
he listed drafts.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Lev=
els of interoperation are proposed:</p><ul style=3D"color:rgb(51,51,51);fon=
t-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20=
px">

<li style=3D"word-wrap:break-word"><strong>Level 1</strong>, star topology.=
 A single BBR devices acts as the time source neighbor for all other nodes.=
 Nodes need to demonstrate frame-based and acknowledgement-based synchroniz=
ation. The static TSCH schedule, as well as all slot timings are taken from=
 draft-ietf-6tisch-minimal-00.</li>

<li style=3D"word-wrap:break-word"><strong>Level 2</strong>, multi-hop topo=
logy. This level builds upon level 1. The goal of this level is full compli=
ance to draft-ietf-6tisch-minimal-00, including multi-hop routing (RPL).</l=
i>

<li style=3D"word-wrap:break-word"><strong>Level 3</strong>, on-the-fly sch=
eduling. [optional] Preliminary implementations of=C2=A0<a href=3D"http://t=
ools.ietf.org/html/draft-dujovne-6tisch-on-the-fly" rel=3D"nofollow" style=
=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http://to=
ols.ietf.org/html/draft-dujovne-6tisch-on-the-fly</a>=C2=A0can be shown.</l=
i>

<li style=3D"word-wrap:break-word"><strong>Level 4</strong>, drafts from RO=
LL, such as: draft-ietf-roll-mpl-parameter-configuration, draft-ko-roll-mix=
-network-pathology, Opportunistic routing, selective DIS, and others that p=
articipants want to show</li>

<li style=3D"word-wrap:break-word"><strong>Level 5</strong>, drafts from 6l=
o, such as: draft-ietf-6lo-btle, draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz,=
 and others that participants want to show.</li><li style=3D"word-wrap:brea=
k-word">

<strong>Level 6</strong>=C2=A0Other drafts, such as draft-thubert-6man-flow=
-label-for-rpl, etc.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:=
Arial,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight=
:normal;line-height:1.5">

Focus 2: Demonstration</h2><p style=3D"color:rgb(51,51,51);font-family:Aria=
l,sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break=
-word;line-height:20px">Participants are encouraged to bring devices and te=
chnology based on 6TiSCH, 6lo and ROLL which they believe can be of interes=
t for the other participants. These devices may or may not participate in t=
he interoperation event. Demonstration of more complete systems are encoura=
ged, for example systems which show the interconnection of a 6TiSCH based m=
esh to traditional networks.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Focus=
 3: Tools</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">

Participants are encouraged to bring and present different tools developed =
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not limite=
d to:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font=
-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word">acquisition devices (i.e. &quot;sniffers=
&quot;)</li><li style=3D"word-wrap:break-word">packet analysis tools (e.g. =
Wireshark)</li><li style=3D"word-wrap:break-word">simulation/emulation plat=
forms</li>

</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Important Dates</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-=
serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;l=
ine-height:20px">

The preparation of this event will be held during a portion of the bi-weekl=
y 6TiSCH call (<strong>To Be Decided how and when!!!</strong>). In particul=
ar:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-s=
ize:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>06/02/2014</strong>=C2=A0Announc=
ement of the plugfest event to the WG/ML related with constrained devices, =
such as: 6tisch, 6lo, roll, core, lwig, dtls-iot, coman, ace, etc.</li><li =
style=3D"word-wrap:break-word">

<strong>06/06/2014</strong>=C2=A0Adoption of the plugfest call by the WGs, =
and call for participants at each group.</li><li style=3D"word-wrap:break-w=
ord"><strong>06/02/2014-06/13/2014</strong>=C2=A0Participants have contacte=
d the plugfest chairs (Xavier or Ines) with a tentative description of what=
 they wish to participate in.</li>

<li style=3D"word-wrap:break-word"><strong>06/20/2014</strong>=C2=A0Synchro=
nization point 1. Participants can share the state of advancement of the im=
plementation and raise blocking points.</li><li style=3D"word-wrap:break-wo=
rd">
<strong>07/11/2014</strong>=C2=A0Synchronization point 2. Participants can =
share the state of advancement of the implementation and raise blocking poi=
nts.</li>
<li style=3D"word-wrap:break-word"><strong>07/20/2014</strong>. Plugfest at=
 IETF90.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-s=
erif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line=
-height:1.5">

Tentative Agenda from 9:00 to 13:00</h2><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px"><li style=3D"word-wrap:break-word"><em>[09.00]</em>=C2=A0Welcome and I=
nitial Instructions</li>

<li style=3D"word-wrap:break-word"><em>[09.05]</em>=C2=A0Participants Pitch=
 (5 min per Participant)</li><li style=3D"word-wrap:break-word"><em>[09.45]=
</em>=C2=A0Participants Pitch Tools (5 min per Participant)</li><li style=
=3D"word-wrap:break-word">

<em>[10.15]</em>=C2=A0Interoperation (Islands)</li><li style=3D"word-wrap:b=
reak-word"><em>[11.50]</em>=C2=A0Feedback and open discussion.</li><li styl=
e=3D"word-wrap:break-word"><em>[12.40]</em>=C2=A0Acknowledgements and Plugf=
est End</li></ul>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">For M=
ore Information</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans=
-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>Contact</strong>: Xavi Vilajosan=
a=C2=A0<a href=3D"mailto:xvilajosana@eecs.berkeley.edu" style=3D"color:rgb(=
59,115,175);text-decoration:none" target=3D"_blank">xvilajosana@eecs.berkel=
ey.edu</a>=C2=A0- Ines Robles=C2=A0<a href=3D"mailto:mariainesrobles@gmail.=
com" style=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank"=
>mariainesrobles@gmail.com</a></li>

</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Note Well</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">

This event is organized as part of the IETF90 standardization meeting. You =
need to register to the IETF90 conference to be able to participate. Daily =
passes are available. The IETF Note Well applies to this plugfest, see=C2=
=A0<a href=3D"http://www.ietf.org/about/note-well.html" rel=3D"nofollow" st=
yle=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http:/=
/www.ietf.org/about/note-well.html</a>.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">About=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">

The IETF 6TiSCH working group standardizes mechanisms focusing on enabling =
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the c=
harter at=C2=A0<a href=3D"http://datatracker.ietf.org/wg/6tisch/charter/" r=
el=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" target=
=3D"_blank">http://datatracker.ietf.org/wg/6tisch/charter/</a>, which also =
contains links to the mailing list and the Internet-Drafts published by the=
 group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is=
 open, and is subject to the IETF Note Well.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF 6lo working group focuses on the work that facilitates IPv6 connectiv=
ity over constrained node networks with the characteristics of: limited pow=
er, memory and processing resources;. You can access the charter at=C2=A0<a=
 href=3D"https://datatracker.ietf.org/wg/6lo/charter/" rel=3D"nofollow" sty=
le=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">https:/=
/datatracker.ietf.org/wg/6lo/charter/</a>, which also contains links to the=
 mailing list and the I-D published by the group.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF ROLL working group is focused on routing issues for LLN (Low Power an=
d Lossy Networks), in IPv6 routing architectural framework for the industri=
al, connected home, building and urban sensor networks application scenario=
s. You can access the charter at=C2=A0<a href=3D"https://datatracker.ietf.o=
rg/wg/roll/charter/" rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-d=
ecoration:none" target=3D"_blank">https://datatracker.ietf.org/wg/roll/char=
ter/</a>, which also contains links to the mailing list and the I-D publish=
ed by the group.</p>

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

--047d7b3a9b742ce9d904facd703b--


From nobody Mon Jun  2 07:46:25 2014
Return-Path: <stephen@tolerantnetworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E78B91A0673; Fri, 30 May 2014 15:42:40 -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] autolearn=ham
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 Dve8PUHKguq3; Fri, 30 May 2014 15:42:39 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 405B81A024B; Fri, 30 May 2014 15:42:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6C173BED7; Fri, 30 May 2014 23:42:33 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yn1gSdwekDXK; Fri, 30 May 2014 23:42:32 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.42.20.19]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1FFEBBED6; Fri, 30 May 2014 23:42:32 +0100 (IST)
Message-ID: <53890957.3090407@tolerantnetworks.com>
Date: Fri, 30 May 2014 23:42:31 +0100
From: Stephen Farrell <stephen@tolerantnetworks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>,  "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Subject: Re: [secdir] secdir review of draft-moonesamy-sshfp-ed25519-01
References: <2ACBFFE4-BCEB-4F6D-A2D3-861BADF543DE@cisco.com> <6.2.5.6.2.20140530040300.0bb93070@elandnews.com> <D1342262-144C-4939-B005-5E042CAF7394@cisco.com> <20140530141618.kgnw4u9b4gw80o4s@webmail.mit.edu> <6.2.5.6.2.20140530114625.0c0d1aa8@elandnews.com> <868A3427-6B46-4110-8D4B-45857D260C1D@cisco.com> <6.2.5.6.2.20140530135131.0c7bdba0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140530135131.0c7bdba0@elandnews.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D4BSF4wpJPjb4yOoyh2CnA0cErQ
X-Mailman-Approved-At: Mon, 02 Jun 2014 07:46:21 -0700
Cc: iesg@ietf.org, Uri Blumenthal <uri@mit.edu>, secdir@ietf.org, ietf@ietf.org, draft-moonesamy-sshfp-ed25519.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 22:42:41 -0000

On 30/05/14 23:22, S Moonesamy wrote:
> Hi Joe,
> At 13:42 30-05-2014, Joseph Salowey (jsalowey) wrote:
>> [Joe] My concern is that there is not enough information in the draft
>> to know what goes into the hash that is the subject of the code point
>> assignment.  Perhaps it is obvious to someone who implemented the SSH
>> code that is not documented in this draft, but it is not obvious to me
>> as a reader of the draft.
> 
> That's a fair point.  I propose adding the following text in Section 2
> as a warning to the reader:
> 
>   The format of the ED25519 public key with SHA-256 fingerprint is
>   not documented in an authoritative specification.

Why? Why not just look at the code and write down what that does
in terms of formatting the input.

If >1 implementation interoperates it can't be that hard.

S.

> 
> Regards,
> S. Moonesamy 


From nobody Mon Jun  2 07:46:57 2014
Return-Path: <uri@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36D191A015B; Sat, 31 May 2014 19:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 3VCa9u0YMiyL; Sat, 31 May 2014 19:53:20 -0700 (PDT)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by ietfa.amsl.com (Postfix) with ESMTP id BEB5A1A010E; Sat, 31 May 2014 19:53:19 -0700 (PDT)
X-AuditID: 12074422-f79376d000000c58-8a-538a959ac300
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 36.89.03160.A959A835; Sat, 31 May 2014 22:53:14 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id s512rB6s024431; Sat, 31 May 2014 22:53:11 -0400
Received: from [192.168.1.107] (chostler.hsd1.ma.comcast.net [24.62.227.134]) (authenticated bits=0) (User authenticated as uri@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s512r6Ox009593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 31 May 2014 22:53:09 -0400
References: <2ACBFFE4-BCEB-4F6D-A2D3-861BADF543DE@cisco.com> <6.2.5.6.2.20140530040300.0bb93070@elandnews.com> <D1342262-144C-4939-B005-5E042CAF7394@cisco.com> <20140530141618.kgnw4u9b4gw80o4s@webmail.mit.edu> <6.2.5.6.2.20140530114625.0c0d1aa8@elandnews.com> <868A3427-6B46-4110-8D4B-45857D260C1D@cisco.com> <6.2.5.6.2.20140530135131.0c7bdba0@elandnews.com> <53890957.3090407@tolerantnetworks.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <53890957.3090407@tolerantnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <129646BF-9249-4AE7-AEA8-D43A2E3BD4E3@mit.edu>
X-Mailer: iPad Mail (11D201)
From: Uri Blumenthal <uri@MIT.EDU>
Subject: Re: [secdir] secdir review of draft-moonesamy-sshfp-ed25519-01
Date: Sat, 31 May 2014 22:53:06 -0400
To: Stephen Farrell <stephen@tolerantnetworks.com>
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBKsWRmVeSWpSXmKPExsUixCmqrDtralewwdGZ8hYz7/pZzPgzkdni 2cb5LBZdR9eyW3xY+JDF4lX/TVaL7klTmB3YPab83sjqce/NRyaPJUt+Mnlsa29k9fhy+TNb AGsUl01Kak5mWWqRvl0CV8blszuZCz5zVHTcXcXYwNjM3sXIySEhYCKx4t5PNghbTOLCvfVA NheHkMBsJomvTy+xQzgbGSU2vtzNBOHsY5JombudFcLpY5bo3NHA0sXIwcErIC5x9aAPyChO oLHbp99gAwkzC+hITF7ICBJmFtCWWLbwNTNEtZVE+3kTkCnMAqeYJJ7O3Qc2RUJARuLJZ2WQ cjYBJYnm5i2sILawgLvEid0TmEFsFgFVie/bX4PFRQSMJL72vmSfwCg4C+GGWQh7ZyHZu4CR eRWjbEpulW5uYmZOcWqybnFyYl5eapGuqV5uZoleakrpJkZQJLC7KO1g/HlQ6RCjAAejEg+v gl1XsBBrYllxZe4hRkkOJiVR3ux+oBBfUn5KZUZicUZ8UWlOavEhRgkOZiURXr4ioBxvSmJl VWpRPkxKmoNFSZz3rbVVsJBAemJJanZqakFqEUxWhoNDSYJ34RSgRsGi1PTUirTMnBKENBMH J8hwHqDhPSA1vMUFibnFmekQ+VOMuhzn5pxqYxJiycvPS5US5709GahIAKQoozQPbg4sgb1i FAd6S5h3FsgoHmDyg5v0CmgJE9CSt1WdIEtKEhFSUg2Mtpx7mSPj70+aNnt7XMemf3zRnzmv eKu27z4iwbvlk6jC1+BdZz/cDLQvYDXIkTTk7u1RfGcn7iL2XPnwZff2i0zq1ZH2R0vjY9Zb 6El8FMl/e3di2cqSxCmiFrZ6917aXvhfHFPp8Oaar/N5JUvr5MWLVtwT8us2P3jgrJ5/Y2/c tn82yWpKLMUZiYZazEXFiQCZCc9DOwMAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HTwnJ7ci1yp-SGdpTRzL9oG5PkU
X-Mailman-Approved-At: Mon, 02 Jun 2014 07:46:54 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "draft-moonesamy-sshfp-ed25519.all@tools.ietf.org" <draft-moonesamy-sshfp-ed25519.all@tools.ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 02:53:21 -0000

I reject S. Moonesamy's proposal, and strongly support Stephen's recommendat=
ion.

Sent from my iPad

> On May 30, 2014, at 18:42, Stephen Farrell <stephen@tolerantnetworks.com> w=
rote:
>=20
>=20
>=20
>> On 30/05/14 23:22, S Moonesamy wrote:
>> Hi Joe,
>> At 13:42 30-05-2014, Joseph Salowey (jsalowey) wrote:
>>> [Joe] My concern is that there is not enough information in the draft
>>> to know what goes into the hash that is the subject of the code point
>>> assignment.  Perhaps it is obvious to someone who implemented the SSH
>>> code that is not documented in this draft, but it is not obvious to me
>>> as a reader of the draft.
>>=20
>> That's a fair point.  I propose adding the following text in Section 2
>> as a warning to the reader:
>>=20
>>  The format of the ED25519 public key with SHA-256 fingerprint is
>>  not documented in an authoritative specification.
>=20
> Why? Why not just look at the code and write down what that does
> in terms of formatting the input.
>=20
> If >1 implementation interoperates it can't be that hard.
>=20
> S.
>=20
>>=20
>> Regards,
>> S. Moonesamy=20


From nobody Mon Jun  2 08:50:28 2014
Return-Path: <nd@syndicat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABEF91A0382 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 08:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.252
X-Spam-Level: 
X-Spam-Status: No, score=-4.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 SRp_U702PqVm for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 08:50:24 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 763971A024A for <ietf@ietf.org>; Mon,  2 Jun 2014 08:50:24 -0700 (PDT)
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 4.82) (envelope-from <nd@syndicat.com>) id 1WrUV4-00013g-BS; Mon, 02 Jun 2014 17:50:14 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVv0hyUecBNO; Mon,  2 Jun 2014 17:50:14 +0200 (CEST)
Received: from p508c7938.dip0.t-ipconnect.de ([80.140.121.56] helo=[10.1.1.105]) by mail.syndicat.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Syndicat.com PostHamster 4.82) (envelope-from <nd@syndicat.com>) id 1WrUV3-0003vW-Ur; Mon, 02 Jun 2014 17:50:14 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: "Niels Dettenbach (Syndicat IT&Internet)" <nd@syndicat.com>
Date: Mon, 02 Jun 2014 17:50:02 +0200
To: Kelvin Githira <kelvin@skysys.co.ke>,Arnaud AMELINA <amelnaud@gmail.com>
Message-ID: <2a8820ba-fa4c-4a20-b2e5-c40be6257cc3@email.android.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oQfwAnzNJn4QPEuRkP6cQ1vTss8
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 15:50:26 -0000

On 2. Juni 2014 01:13:49 MESZ, Kelvin Githira <kelvin@skysys.co.ke> wrote:
>A free sevice will have its cons while a paid service will center on
>its pros
A "free of charge" internet is an illusion, because running a internet network requires significant human as energy resources which are not "free" available on any market. A "free of charge" in the meaning of "free of money charge" works usually in two ways:

 - the user have to "pay" with other "goods" - i.e. his personal data and/or awareness/lifetime (i.e. to consume ads or similiar)

 - the service has to be paid by others which wont use that service (or won't use the ressources they have to pay for)

btw: There still ARE networks / projects offering "money cost free" or "cost free" internet services on a commercial and even private / non-commercial level which are by principle available around the globe. I.e. paying broadband customers are offering "free" hot spot networks or meshed network access against each other  constributor and/or "external" users (he spend bandwidth for "free" to others). There is no government required which generates additional costs for others and destroys free markets of IP access services.

And not at least:
There is no "internet access" type or service nor access media for "all" as usage profiles highly differ and differentiation is rising more and more. 

A "public free" service must cover most or any of them to be "network neutral" on a minimum level - but even this would be just overkill.

If YOU mean that "many" others would an autonomous system / internet access network system providing "free" service in a kind you and your colleagues want it you are free to found an non commercial or commercial organisation which builds that network and runs it "for free" for you or the ones who want it "free" while others in your  organisation are "free" to pay for you.

This is freedom - pressing others to pay for you would be robbery instead even if you do it with a "democratic majority" against any minority in your country.


cheerioh,


Niels.
-- 
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com


From dbourdoukis@hol.net  Mon Jun  2 08:04:15 2014
Return-Path: <dbourdoukis@hol.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812FB1A0362 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 08:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 ZQsC1SaMVdf5 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 08:04:13 -0700 (PDT)
Received: from SPARK.hol.net (mailin02mx.hol.net [62.38.103.56]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCE671A0360 for <ietf@ietf.org>; Mon,  2 Jun 2014 08:04:12 -0700 (PDT)
Received: from gumball.hol.net (10.30.10.34) by SPARK.hol.net (10.30.253.56) with Microsoft SMTP Server id 14.3.158.1; Mon, 2 Jun 2014 18:04:04 +0300
Received: from mail.hol.net ([10.30.10.33]) by gumball.hol.net (PGP Universal service);  Mon, 02 Jun 2014 17:44:21 +0300
X-PGP-Universal: processed; by gumball.hol.net on Mon, 02 Jun 2014 17:44:21 +0300
Received: from SPINDLE.hol.net ([fe80::a021:b927:6c4:e462]) by SPARKY.hol.net ([fe80::f8a0:3486:4481:880a%11]) with mapi id 14.03.0158.001; Mon, 2 Jun 2014 18:04:06 +0300
From: Bourdoukis Dimitrios <dbourdoukis@hol.net>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Multiple equivalent P-CSCF discovery issues
Thread-Topic: Multiple equivalent P-CSCF discovery issues
Thread-Index: Ac972FTwwiVJY5Q0SJuVvOcxLMfpbwCmydfA
Date: Mon, 2 Jun 2014 15:04:04 +0000
Message-ID: <94BCEFC356CCB34788F5213414EC02D80DF674@SPINDLE.hol.net>
References: <94BCEFC356CCB34788F5213414EC02D80DD4AD@SPINDLE.hol.net>
In-Reply-To: <94BCEFC356CCB34788F5213414EC02D80DD4AD@SPINDLE.hol.net>
Accept-Language: en-GB, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.0.102.130]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_94BCEFC356CCB34788F5213414EC02D80DF674SPINDLEholnet_"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cUopeUoTM3kCHsR_yk_NaCplWrg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 16:00:14 -0000

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

Hello team

I have deployed in the network an SBC acting as A-ALG and I am trying to lo=
ad-balance the REGISTER requests coming from the UEs towards multiple cores=
 (P-CSCFs) by means of DNS which resolves the P-CSCFs hosts with equal prio=
rity and weight.

I am using Digest authentication without TLS for the UEs and the problem I =
am facing  is the following:

After a UE is challenged by the network with 401 Unauthorized, it resubmits=
 the REGISTER request with the appropriate credentials and same Call-Id as =
appropriate. However this new REGISTER request is routed individually by th=
e SBC A-ALG towards the core side  by executing again DNS procedures. The e=
ffect is that this 2nd REGISTER request may be routed to a different P-CSCF=
 which in turn results again to a new challenge for obvious reasons (differ=
ent contact reaches the S-CSCF), and so on.

Note that this is not the case for the Re-REGISTER requests, where in that =
case my A-ALG remembers where the initial Registration has been concluded a=
s it uses that address:port when a binding is refreshed by the UE.

I was not able to find any explicit reference in the specs on how a UE Prox=
y Registrar (in my case an A-ALG) should route a REGISTER request following=
 the challenge from the network with 401, in case of multiple equivalent co=
re targets.

Can anybody help on that?  Is there any RFC reference or other spec  that c=
larify this? Note that the SIP multicast Registrar discovery is not an opti=
on in my implementation.

Thanks in advance

Dimitris

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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=3D"EL" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello team<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I have deployed in the network =
an SBC acting as A-ALG and I am trying to load-balance the REGISTER request=
s coming from the UEs towards multiple cores (P-CSCFs) by means of DNS whic=
h resolves the P-CSCFs hosts with equal
 priority and weight.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I am using Digest authenticatio=
n without TLS for the U<span style=3D"color:#1F497D">Es</span> and the prob=
lem I am facing<span style=3D"color:#1F497D">
</span>&nbsp;is the following:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">After a UE is challenged by the=
 network with 401 Unauthorized, it resubmits the REGISTER request with the =
appropriate credentials and same Call-Id as appropriate. However this new R=
EGISTER request is routed individually
 by the SBC A-ALG towards the core side <span style=3D"color:#1F497D">&nbsp=
;</span>by executing again DNS procedures. The effect is that this 2nd REGI=
STER request may be routed to a different P-CSCF which in turn results agai=
n to a new challenge for obvious reasons
 (different contact reaches the S-CSCF), and so on.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Note that this is not the case =
for the Re-REGISTER requests, where in that case my A-ALG remembers where t=
he initial Registration has been concluded as it uses that address:port whe=
n a binding is refreshed by the UE.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I was not able to find any expl=
icit reference in the specs on how a UE Proxy Registrar (in my case an A-AL=
G) should route a REGISTER request following the challenge from the network=
 with 401, in case of multiple equivalent
 core targets.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Can anybody help on that? &nbsp=
;Is there any RFC reference or other spec &nbsp;that clarify this? Note tha=
t the SIP multicast Registrar discovery is not an option in my implementati=
on.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks in advance<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dimitris<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_94BCEFC356CCB34788F5213414EC02D80DF674SPINDLEholnet_--


From nobody Mon Jun  2 10:04:37 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F77D1A0256 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 8Pj1ADiR2EBf for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:04:33 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399521A023A for <ietf@ietf.org>; Mon,  2 Jun 2014 10:04:33 -0700 (PDT)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s52H43N3001062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 2 Jun 2014 10:04:07 -0700 (PDT)
Message-ID: <538CAE86.7080900@isi.edu>
Date: Mon, 02 Jun 2014 10:04:06 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Internet 2020 Goals
References: <CAMm+LwiNxZYcT5QEseyUfQAXuZ28ufvr5V4c=chuT5d9gJSgeA@mail.gmail.com>	<5383933A.8050804@gmail.com>	<5383F53B.7050308@meetinghouse.net>	<5384D2DA.7030900@isi.edu>	<538598E0.4040003@tana.it>	<538614C2.8080909@isi.edu>	<538647EE.8050902@gmail.com>	<53864A61.302@isi.edu>	<CAMm+LwhcY6BV245n5b6MM8Awu_ugU0pDo_XqnDWJr3NEZ0rx3Q@mail.gmail.com>	<53875D0E.7080003@isi.edu> <CAMm+LwhpDyN2ryiVjLRZoMEUU6cqza0-1wvD_h-18ru6c4-eQQ@mail.gmail.com>
In-Reply-To: <CAMm+LwhpDyN2ryiVjLRZoMEUU6cqza0-1wvD_h-18ru6c4-eQQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_5nCOWJ9M2-NQZJEyOlKNmciePI
Cc: Carlos Martinez <carlos@lacnic.net>, IETF Discussion Mailing List <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 17:04:36 -0000

On 5/29/2014 5:51 PM, Phillip Hallam-Baker wrote:
> On Thu, May 29, 2014 at 12:15 PM, Joe Touch <touch@isi.edu> wrote:
>
>> I'm talking about whether the IETF/ISOC is a useful home for the discussion.
>> I don't think it is, because for every 100 network researchers there are 101
>> such documents "predicting the future", none of which have done much without
>> associated money.
>
> Well you completely missed the difference between a goal and a prediction:
>
> A goal is an outcome that is desired.
> A prediction is an outcome that is expected.

I think you have it reversed:
	- a goal is an outcome towards which a community is working
	(with funding to back it up)

	- prediction is what groundhogs do early February, and people
	do with about as much accuracy and utility

> As I pointed out at the start, the money concern here is what to spend it on.

The people with the money get to decide that.

Joe


From nobody Mon Jun  2 10:36:33 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AA11A02AA for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 SV2qAcYoC7s2 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:36:28 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C941A0024 for <ietf@ietf.org>; Mon,  2 Jun 2014 10:36:27 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Mon, 2 Jun 2014 13:36:21 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 2 Jun 2014 13:36:19 -0400
Received: from b01cxnp22034.gho.pok.ibm.com (b01cxnp22034.gho.pok.ibm.com [9.57.198.24]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 32E4E38C8027; Mon,  2 Jun 2014 13:36:18 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s52HaIDf8389050; Mon, 2 Jun 2014 17:36:18 GMT
Received: from d01av01.pok.ibm.com (localhost [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s52HaHwH005434; Mon, 2 Jun 2014 13:36:17 -0400
Received: from cichlid.raleigh.ibm.com ([9.80.111.183]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s52HaGwB005384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Jun 2014 13:36:17 -0400
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s52HaBeG021925; Mon, 2 Jun 2014 13:36:15 -0400
Date: Mon, 02 Jun 2014 13:36:11 -0400
Message-ID: <m3d2erdxis.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14060217-5806-0000-0000-00002507BD34
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3ojS1XJDM11jWjQwYDyb6s4VEZA
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 17:36:29 -0000

I've followed the discussion on this thread and want to  go back to
something folk may have forgotten.

More than a year ago, the WG made a considered and conscious decision
to "ship" the framework documemnt more or less "as is" and start work
on a followup architecure document. It was known and expected that the
architecture document would become the focus of work moving forward
and that substantive additions/changes would go there. Even if it
meant the framework document would be less complete.

Sadly, it has been more than a year since that decision was made, yet
the framework document appears stalled and unable to get
published. I'll note that the problem statement document to which the
framework is a companion, has been languishing in the RFC editor queue
for almost a year now, blocked on a normative reference to the
definitions in the framework document.

FWIW, I think the framework is good enough to publish more-or-less as
is. Or more to the point, there just isn't energy to make significant
changes to the document given that the focus of the WG has long since
moved to the architecture document.
 
If folk have substantive issues with the framework, I'd strongly
suggest first looking at the architecture
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
there, and of so, whether the archictecture document would be a better
place to address the concern.

Thomas


From nobody Mon Jun  2 10:52:03 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 191491A03AF for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 Dg_tv5bIDzok for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 10:51:54 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF0891A03D6 for <ietf@ietf.org>; Mon,  2 Jun 2014 10:51:43 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id u56so5611766wes.28 for <ietf@ietf.org>; Mon, 02 Jun 2014 10:51:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jA0OhGfVPeOft7YGhflv5M8SUZHl/R0966pO1b9d3U8=; b=k92x/+8gXBQRH+DzN4KDDvGaX3ZTAgR37iJkr7z3JbrvkdoLxxwJpaqiysptr4tFov CWt4ndXD+UuJbMNvvqPO5m+tzkOl6SEaS1p72A19FFhIVOLjJy/Jf4XomK15xuSWyyXI RYq5EA7zVjKvp+oFCZqru9g01bD2sLo6TkbCeh2SdANvLSTYDmieaVklJmxf400clFZQ wlpvlI8bY9kRFUISjNznEFeXt0xBSU68anBh1UT6dcS4Mj4YWaqO7kV7m2EoA7fi6WPd 1CcqC0DE5QYPxRK05m2RUkutOklQ1fV/OpBDh/vPMYfLCcHsSZgw1gF4FPmzrFk7JxD9 hpUw==
MIME-Version: 1.0
X-Received: by 10.194.175.106 with SMTP id bz10mr6105990wjc.96.1401731497325;  Mon, 02 Jun 2014 10:51:37 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Mon, 2 Jun 2014 10:51:37 -0700 (PDT)
In-Reply-To: <538CAE86.7080900@isi.edu>
References: <CAMm+LwiNxZYcT5QEseyUfQAXuZ28ufvr5V4c=chuT5d9gJSgeA@mail.gmail.com> <5383933A.8050804@gmail.com> <5383F53B.7050308@meetinghouse.net> <5384D2DA.7030900@isi.edu> <538598E0.4040003@tana.it> <538614C2.8080909@isi.edu> <538647EE.8050902@gmail.com> <53864A61.302@isi.edu> <CAMm+LwhcY6BV245n5b6MM8Awu_ugU0pDo_XqnDWJr3NEZ0rx3Q@mail.gmail.com> <53875D0E.7080003@isi.edu> <CAMm+LwhpDyN2ryiVjLRZoMEUU6cqza0-1wvD_h-18ru6c4-eQQ@mail.gmail.com> <538CAE86.7080900@isi.edu>
Date: Mon, 2 Jun 2014 13:51:37 -0400
X-Google-Sender-Auth: hifCCRGoj0WQHReuvyOr1jhBHv8
Message-ID: <CAMm+LwgK0bUeduKxGtdFwjivAxpVkLhKkDKewxzEnodan99Y=Q@mail.gmail.com>
Subject: Re: Internet 2020 Goals
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mm09kdfeZh72T6O33aElZY_aa64
Cc: Carlos Martinez <carlos@lacnic.net>, IETF Discussion Mailing List <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 17:51:55 -0000

On Mon, Jun 2, 2014 at 1:04 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 5/29/2014 5:51 PM, Phillip Hallam-Baker wrote:
>>
>> On Thu, May 29, 2014 at 12:15 PM, Joe Touch <touch@isi.edu> wrote:
>>
>>> I'm talking about whether the IETF/ISOC is a useful home for the
>>> discussion.
>>> I don't think it is, because for every 100 network researchers there are
>>> 101
>>> such documents "predicting the future", none of which have done much
>>> without
>>> associated money.
>>
>>
>> Well you completely missed the difference between a goal and a prediction:
>>
>> A goal is an outcome that is desired.
>> A prediction is an outcome that is expected.
>
>
> I think you have it reversed:
>         - a goal is an outcome towards which a community is working
>         (with funding to back it up)
>
>         - prediction is what groundhogs do early February, and people
>         do with about as much accuracy and utility
>
>
>> As I pointed out at the start, the money concern here is what to spend it
>> on.
>
>
> The people with the money get to decide that.

Joe, I know you think you have a point here but you don't.

Back when I did high energy physics we did experiments costing over $1
billion for no particular reason than to satisfy our curiosity.

The Web has added over a trillion dollars a year to global GDP. There
is no shortage of governments willing to back efforts to build the
next generation Web. There is no shortage of companies either.

That does not mean that every government is always willing to fund
every type of project. Coming from the UK I know all about governments
who don't have a clue when it comes to funding research.

But I also know about it from the other side and the problem that the
type of research the academics want to do is not the type of research
the funders are interested in. The type of projects that gets
publications and tenure in academia are low risk incremental studies
of irrelevancies.

I am currently working on usable secure email, S/MIME and PGP done
right. Now that would not get tenure in any university and it
certainly would not get a published paper in a journal. But it is what
we need right now in the Internet community.

Fortunately for me, I can do that work because I have commercial
backing for my research (Comodo) and independent private means. But
most people who might want to do that type of work are not so
fortunate. Even in the IETF most people are working on near run
products not thinking about the future.

The whole point of proposing an Internet 2020 type program is
precisely to tell the politicians who make the real decisions on
funding that there are people they can talk to with a vision aligned
with theirs.

Funding is really not the problem here. The politicians would be only
too happy to write us physicist sized cheques for a next generation
Internet research project if they think there is a reasonable chance
it will deliver something they value.


The physicists got the cash for the LHC because they put up a very
simple proposition that the politicians could understand: Find the
Higgs Boson. That sales pitch got them the $10 billion they needed.

If you think money is the problem then you are not talking to the
right people, you don't understand the concerns of the people with the
money. Get the vision thing right and the money will flow.


From nobody Mon Jun  2 11:30:41 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D7C1A03C4; Mon,  2 Jun 2014 11:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 KcRB_9XBs_ca; Mon,  2 Jun 2014 11:30:34 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 541321A035A; Mon,  2 Jun 2014 11:30:34 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id oz11so5670540veb.31 for <multiple recipients>; Mon, 02 Jun 2014 11:30:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4Jqvtt4Y7NOGlRyoLNDSjZkWRg+p2Wjq4f4iMgCLUyw=; b=kbwJuhN0HTcTSyqmBtIL/3J1u7pwDbcC2Nqmn6JrFFpMweBRJvHqixrSI0vIZbg7/N aUhddk8woh46oQAT9pPTSsR6UTdPPu9uC38z9ndj0aNrqYOsIY/ouVPD+oNPN/DVnDj9 FSB8I7uPNT5pgnG+3O9TzUIfcynVtVjrhW1VAVtA1rCAcufhG6hTxLSfAYDaG2cMQ3uD esSHveV2sVbFlucjrwF+daGppub3zzjLAhb9U4Z6gGwDIw7FiEwPaQwbGH61OxIpjuZG +u65kNNlqJ8eiC4oXg6ZPAjMSplTaCi07CwpjnM0Pzy8cH71k8jcUp7S53mr6aYw3IEG naeQ==
MIME-Version: 1.0
X-Received: by 10.58.19.138 with SMTP id f10mr13814639vee.12.1401733828508; Mon, 02 Jun 2014 11:30:28 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.33.199 with HTTP; Mon, 2 Jun 2014 11:30:28 -0700 (PDT)
In-Reply-To: <m3d2erdxis.wl%narten@us.ibm.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com>
Date: Mon, 2 Jun 2014 14:30:28 -0400
X-Google-Sender-Auth: vGOtzNGv6XETJz8B56ucyG2lMLM
Message-ID: <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UbEiBUp_1wkVB639Tbl8T-dIMio
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 18:30:36 -0000

> If folk have substantive issues with the framework, I'd strongly
> suggest first looking at the architecture
> (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
> there, and of so, whether the archictecture document would be a better
> place to address the concern.

Does that mean that the working group would be willing to pull the
architecture document back out of the RFC Editor queue for rework,
should it come to that?

Barry


From nobody Mon Jun  2 11:44:37 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 057361A038C; Mon,  2 Jun 2014 11:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 05OWY-Uy1ZSF; Mon,  2 Jun 2014 11:44:30 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49B4F1A025F; Mon,  2 Jun 2014 11:44:30 -0700 (PDT)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s52IiDZH012100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Jun 2014 14:44:14 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s52IiDZH012100
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1401734655; bh=zv13MM5Kgvm+VsSi0xcLSeABCWQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=Xt6bsbzwqbRMROvFrCvY2ZCXI6//9e2vIbdy8FVe86Cso84yJUZZ7b205N+THMvCI Du+lpiQEcuz6My5i0DJtmXl0EtUjy9G6/bO+iMyqpZiFTv9zH0hyOzpkYs8126oKPz blyJq8F8iPDvOYZ8aBVC7QTwJxH39gbpFy9/6zX4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s52IiDZH012100
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd04.lss.emc.com (RSA Interceptor); Mon, 2 Jun 2014 11:44:03 -0700
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s52Ii2Zb001667 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Jun 2014 14:44:03 -0400
Received: from mx15a.corp.emc.com ([169.254.1.248]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Mon, 2 Jun 2014 14:44:02 -0400
From: "Black, David" <david.black@emc.com>
To: Barry Leiba <barryleiba@computer.org>, Thomas Narten <narten@us.ibm.com>
Date: Mon, 2 Jun 2014 14:44:01 -0400
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: Ac9+kMJdvh60ronDQbmZ0Vz82Ttm3gAAOosw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076FD33A83@MX15A.corp.emc.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oXLUwr9zYrO8lfwjDUxOUUkUTP4
Cc: "Black, David" <david.black@emc.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 18:44:33 -0000

Barry,

> Does that mean that the working group would be willing to pull the
> architecture document back out of the RFC Editor queue for rework,
> should it come to that?

There appears to be some confusion here:

The nvo3 architecture draft is not in RFC Editor queue, it's still with the=
 WG:
http://datatracker.ietf.org/doc/draft-ietf-nvo3-arch/


The nvo3 problem statement draft is in the RFC Editor queue:
http://datatracker.ietf.org/doc/draft-ietf-nvo3-overlay-problem-statement/

I haven't seen anything in this discussion that suggests pulling
the latter draft back from the RFC Editor.

Thanks,
--David (co-author of both of the above drafts)

> -----Original Message-----
> From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Barry Leiba
> Sent: Monday, June 02, 2014 2:30 PM
> To: Thomas Narten
> Cc: nvo3@ietf.org; ietf@ietf.org; Linda Dunbar
> Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framew=
ork
> for DC Network Virtualization) to Informational RFC
>=20
> > If folk have substantive issues with the framework, I'd strongly
> > suggest first looking at the architecture
> > (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
> > there, and of so, whether the archictecture document would be a better
> > place to address the concern.
>=20
> Does that mean that the working group would be willing to pull the
> architecture document back out of the RFC Editor queue for rework,
> should it come to that?
>=20
> Barry
>=20
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3


From nobody Mon Jun  2 11:48:24 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695BD1A025F for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 11:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 vV0eeZDe8fid for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 11:48:14 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB32B1A03CF for <ietf@ietf.org>; Mon,  2 Jun 2014 11:48:13 -0700 (PDT)
Received: from /spool/local by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Mon, 2 Jun 2014 12:48:07 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 2 Jun 2014 12:48:05 -0600
Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 98A913E4003E; Mon,  2 Jun 2014 12:48:04 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.ahe.boulder.ibm.com [9.17.195.167]) by b03cxnp07029.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s52GigWe6095270; Mon, 2 Jun 2014 18:44:42 +0200
Received: from d03av01.boulder.ibm.com (localhost [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s52Im3Rq021663; Mon, 2 Jun 2014 12:48:04 -0600
Received: from cichlid.raleigh.ibm.com ([9.80.111.183]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s52Im2hH021498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Jun 2014 12:48:03 -0600
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s52Im10s032315; Mon, 2 Jun 2014 14:48:01 -0400
Date: Mon, 02 Jun 2014 14:48:00 -0400
Message-ID: <m3bnubdu73.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
In-Reply-To: <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14060218-3532-0000-0000-0000022F1F0A
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zvm29j6pssfs70J3AjWOrbHjHG4
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 18:48:18 -0000

At Mon, 2 Jun 2014 14:30:28 -0400, Barry Leiba wrote:
> 
> > If folk have substantive issues with the framework, I'd strongly
> > suggest first looking at the architecture
> > (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
> > there, and of so, whether the archictecture document would be a better
> > place to address the concern.
> 
> Does that mean that the working group would be willing to pull the
> architecture document back out of the RFC Editor queue for rework,
> should it come to that?

Not necessary.

To clarify, the problem statement document
(draft-ietf-nvo3-overlay-problem-statement-04.txt) is in the RFC
editor queue. It has a normative dependence on the framework document
- it shares common terminology.

The architecure document is a relatively new document and is still in
the WG and will surely be there for some time. The architecture would
be published along with solutions (which the WG isn't even chartered
to do yet!) because the architecture and solutions clearly have to
very much be in sync.

AFAICT, none of discussions in the last year on the framework document
would have any impact the problem statement.

Thomas


From nobody Mon Jun  2 11:55:18 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D411A03DF; Mon,  2 Jun 2014 11:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 z6ye9Ed_DYZ1; Mon,  2 Jun 2014 11:55:15 -0700 (PDT)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 487C41A03EB; Mon,  2 Jun 2014 11:55:14 -0700 (PDT)
Received: by mail-vc0-f174.google.com with SMTP id ik5so5410962vcb.19 for <multiple recipients>; Mon, 02 Jun 2014 11:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=E3iDLLbgxlZPQMQ6CaB1r1zS5D6Hub6LsFVqOlXGshw=; b=RpYaaoZgvLWTZJd1U2TT+Soi+vREfJu4SUs1TM90D7SjALz4dJpmdI6fyNsI2q9PKK rG3wfv9JLjxgm+XF4SxFOu5KTfETv7fkNWZOmRw2A51QudlQvhdXHm4hCjfUnexQCEdy 274AxPXG/qz9VblyQvXJc8hJLnOjZwyH/Iwo2pOVNrqM29ZwCLLk5Qi0tRWjOMFIN7ez eugSaMIZQt0jPPgc3Mzhfc8W7zdrotdG1h9ghQnoY/6jpoaIV+UhrsaTDLhIWqX5pOUc U14DC3B/cKpt9zYbv010oOnZuXV7LiZLJxpsZ+ds2hwLUWbv8n9YK1AoM3ZBRAzbdP4t c4IA==
MIME-Version: 1.0
X-Received: by 10.58.198.46 with SMTP id iz14mr2515509vec.53.1401735308375; Mon, 02 Jun 2014 11:55:08 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.33.199 with HTTP; Mon, 2 Jun 2014 11:55:08 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076FD33A83@MX15A.corp.emc.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAC4RtVCLj2Gp7w6=2iEUY3WJed7tbu5s8vyQq5au6pt-6TmGuQ@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712076FD33A83@MX15A.corp.emc.com>
Date: Mon, 2 Jun 2014 14:55:08 -0400
X-Google-Sender-Auth: Jre7AEv3JzH3W3kWKmnkQWPoKzk
Message-ID: <CAC4RtVDoo4PPUzcfPJ+zudo1tvJ_nF7CnrYU6dk5Epcmn3397Q@mail.gmail.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cwWZQMH2JCWxx478DqCGXeBA-as
Cc: Thomas Narten <narten@us.ibm.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 18:55:16 -0000

> There appears to be some confusion here:

There does, indeed: I didn't read Thomas's note carefully enough, and
misunderstood.  Got it now; thanks.

Barry


From nobody Mon Jun  2 11:58:49 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D29C1A0341; Mon,  2 Jun 2014 11:58:46 -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, SPF_PASS=-0.001] autolearn=ham
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 R0C6HqY8kVB3; Mon,  2 Jun 2014 11:58:44 -0700 (PDT)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 833931A025F; Mon,  2 Jun 2014 11:58:44 -0700 (PDT)
Received: by mail-yk0-f171.google.com with SMTP id 142so4008121ykq.30 for <multiple recipients>; Mon, 02 Jun 2014 11:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w9RjrsWsQA1bNtawXhQisBDzqDcK9Va0uWuGGGgbOrY=; b=yEBanSyIGH7GnS89r2OUEqZQi3ouLUOldKcZPG5P26DW14tBcs8vqXybhsT0cD3muB HZ71wTDPmri8ACW6cHpXM+go0W9Blze4YOE45yj6RjOBVn8YWs4Z+wddtgqlULo2QLCl 0UR3KAwbjArchKZnH6I98bdAAVpC8gBO2LEjqKLmobPSmfNXPmWEs1ZbdxNBLvUwyQK2 wGGKUuxl+92HDPzox7gWpLUHmvKrbPoomZejjmwLFzL4E2+HN5i5HJSJjT550SkWDJGl 3Ef5DtC/GZG944lTG6t999Ogtom/nemfgqQxvt7yCpYSUgJ1dkfoHOJKL99qkZS/8rzT WLmQ==
MIME-Version: 1.0
X-Received: by 10.236.81.10 with SMTP id l10mr54456632yhe.18.1401735518891; Mon, 02 Jun 2014 11:58:38 -0700 (PDT)
Received: by 10.170.194.2 with HTTP; Mon, 2 Jun 2014 11:58:38 -0700 (PDT)
In-Reply-To: <m3d2erdxis.wl%narten@us.ibm.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com>
Date: Mon, 2 Jun 2014 14:58:38 -0400
Message-ID: <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
From: Alia Atlas <akatlas@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary=20cf3011dca5ac37b004fadefb52
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YHbCfOGbeRnm6bZiq0XTkj9vrJU
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 18:58:46 -0000

--20cf3011dca5ac37b004fadefb52
Content-Type: text/plain; charset=UTF-8

Thomas,

The NVO3 Framework draft is in IETF Last Call, which isn't precisely
stalled.
It is true that Linda and Lucy have raised some concerns about it.

I have not yet heard from the WG chairs or authors whether the desired
changes
have been previously discussed and had consensus determined in the WG.
 Linda indicated that her
comments had already been discussed on the nvo3 mailing list.  Lucy is
requesting that different
technology be indicated as examples - perhaps to give a sense of future
possible solutions to the
readers of the draft.

If there is WG consensus to make a few minor edits, that can be done before
the
IESG review next week.  It is on the next telechat, so I would appreciate
speed in
resolving the minor comment.

Regards,
Alia


On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <narten@us.ibm.com> wrote:

> I've followed the discussion on this thread and want to  go back to
> something folk may have forgotten.
>
> More than a year ago, the WG made a considered and conscious decision
> to "ship" the framework documemnt more or less "as is" and start work
> on a followup architecure document. It was known and expected that the
> architecture document would become the focus of work moving forward
> and that substantive additions/changes would go there. Even if it
> meant the framework document would be less complete.
>
> Sadly, it has been more than a year since that decision was made, yet
> the framework document appears stalled and unable to get
> published. I'll note that the problem statement document to which the
> framework is a companion, has been languishing in the RFC editor queue
> for almost a year now, blocked on a normative reference to the
> definitions in the framework document.
>
> FWIW, I think the framework is good enough to publish more-or-less as
> is. Or more to the point, there just isn't energy to make significant
> changes to the document given that the focus of the WG has long since
> moved to the architecture document.
>
> If folk have substantive issues with the framework, I'd strongly
> suggest first looking at the architecture
> (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
> there, and of so, whether the archictecture document would be a better
> place to address the concern.
>
> Thomas
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>

--20cf3011dca5ac37b004fadefb52
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thomas,<div><br></div><div>The NVO3 Framework draft is in =
IETF Last Call, which isn&#39;t precisely stalled.</div><div>It is true tha=
t Linda and Lucy have raised some concerns about it.</div><div><br></div><d=
iv>
I have not yet heard from the WG chairs or authors whether the desired chan=
ges</div><div>have been previously discussed and had consensus determined i=
n the WG. =C2=A0Linda indicated that her</div><div>comments had already bee=
n discussed on the nvo3 mailing list. =C2=A0Lucy is requesting that differe=
nt</div>
<div>technology be indicated as examples - perhaps to give a sense of futur=
e possible solutions to the</div><div>readers of the draft.</div><div><br><=
/div><div>If there is WG consensus to make a few minor edits, that can be d=
one before the</div>
<div>IESG review next week. =C2=A0It is on the next telechat, so I would ap=
preciate speed in</div><div>resolving the minor comment.</div><div><br></di=
v><div>Regards,</div><div>Alia</div></div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">
On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <span dir=3D"ltr">&lt;<a href=
=3D"mailto:narten@us.ibm.com" target=3D"_blank">narten@us.ibm.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
I&#39;ve followed the discussion on this thread and want to =C2=A0go back t=
o<br>
something folk may have forgotten.<br>
<br>
More than a year ago, the WG made a considered and conscious decision<br>
to &quot;ship&quot; the framework documemnt more or less &quot;as is&quot; =
and start work<br>
on a followup architecure document. It was known and expected that the<br>
architecture document would become the focus of work moving forward<br>
and that substantive additions/changes would go there. Even if it<br>
meant the framework document would be less complete.<br>
<br>
Sadly, it has been more than a year since that decision was made, yet<br>
the framework document appears stalled and unable to get<br>
published. I&#39;ll note that the problem statement document to which the<b=
r>
framework is a companion, has been languishing in the RFC editor queue<br>
for almost a year now, blocked on a normative reference to the<br>
definitions in the framework document.<br>
<br>
FWIW, I think the framework is good enough to publish more-or-less as<br>
is. Or more to the point, there just isn&#39;t energy to make significant<b=
r>
changes to the document given that the focus of the WG has long since<br>
moved to the architecture document.<br>
<br>
If folk have substantive issues with the framework, I&#39;d strongly<br>
suggest first looking at the architecture<br>
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists<br>
there, and of so, whether the archictecture document would be a better<br>
place to address the concern.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Thomas<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><br>
</div></div></blockquote></div><br></div>

--20cf3011dca5ac37b004fadefb52--


From nobody Tue Jun  3 06:31:35 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BC21A026D; Tue,  3 Jun 2014 06:31:30 -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, SPF_PASS=-0.001] autolearn=ham
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 OjZqHFku5O-B; Tue,  3 Jun 2014 06:31:28 -0700 (PDT)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B62C51A01F6; Tue,  3 Jun 2014 06:31:27 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id 29so5071436yhl.37 for <multiple recipients>; Tue, 03 Jun 2014 06:31:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mECdWv/1n1aUiMdL+kodxM2mu2Mwus8ZJQcfJ9l0CIA=; b=u1ntx9Qhh4NIYHtfmaT3SqDovQTOWDYFaDmTlJmacdyMPQmisnqreyX4WSrvlhxDpb c3m55eVzgF9pv0BD+AtAsiaei9qXiF7RYspbVMUfWnte+K2lTRJnpQJZdzX8sppLhnPH lEm1d+w4hxpTe4AqQPkq2tqU34YSS1+IoNq68j7tq9aGfRT6fpLSjYaJu2MnKxQ54g02 5AZcqwa/mCMVk+LnokiXUVY+knRVT/RY07lz8WDPlqc9hDqFxZ35oKOoiQrUBP9ry5HY ksMPutgX3ft+F5OBNh3CCgjp3/aJKYV6EiLmqRS37eCDtzlGCgsLpWDiMFil3T0VQt08 tNmQ==
MIME-Version: 1.0
X-Received: by 10.236.150.205 with SMTP id z53mr63022560yhj.75.1401802281708;  Tue, 03 Jun 2014 06:31:21 -0700 (PDT)
Received: by 10.170.194.2 with HTTP; Tue, 3 Jun 2014 06:31:21 -0700 (PDT)
In-Reply-To: <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com> <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Date: Tue, 3 Jun 2014 09:31:21 -0400
Message-ID: <CAG4d1rfKk_b=DqYwj+rd-KjbJzfqgd86kbzApd+Ae19Gve1SKQ@mail.gmail.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
From: Alia Atlas <akatlas@gmail.com>
To: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=20cf303a2d610bf22504faee879b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/m1ihRWuOGJXK2yrGk2t4HZjHHAs
Cc: Thomas Narten <narten@us.ibm.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 13:31:30 -0000

--20cf303a2d610bf22504faee879b
Content-Type: text/plain; charset=UTF-8

Marc,

An updated draft would be excellent -before Thursday, preferably.

Thanks,
Alia


On Tue, Jun 3, 2014 at 4:01 AM, LASSERRE, MARC (MARC) <
marc.lasserre@alcatel-lucent.com> wrote:

>  Alia,
>
> I have replied and suggested some minor edits to address Linda and Lucy's
> comments. I have suggested to be protocol agnostic rather than giving
> specific examples in the multi-homing case.
> Some of Linda's comments have been discussed at length in the past and
> there was clear WG consensus that the framework draft addressed NVO3's
> problem.
>
> Let me know if you want me to post a revised draft based on these minor
> edits and some other suggested edits from other IETF reviewers received
> last week prior to next week IESG review.
>
> Regards,
> Marc
>
>  ------------------------------
> *From:* nvo3 [mailto:nvo3-bounces@ietf.org] * On Behalf Of *Alia Atlas
> *Sent:* Monday, June 02, 2014 8:59 PM
>
> *To:* Thomas Narten
> *Cc:* nvo3@ietf.org; ietf@ietf.org; Linda Dunbar
> *Subject:* Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt>
> (Framework for DC Network Virtualization) to Informational RFC
>
>  Thomas,
>
>  The NVO3 Framework draft is in IETF Last Call, which isn't precisely
> stalled.
> It is true that Linda and Lucy have raised some concerns about it.
>
>  I have not yet heard from the WG chairs or authors whether the desired
> changes
> have been previously discussed and had consensus determined in the WG.
>  Linda indicated that her
> comments had already been discussed on the nvo3 mailing list.  Lucy is
> requesting that different
> technology be indicated as examples - perhaps to give a sense of future
> possible solutions to the
> readers of the draft.
>
>  If there is WG consensus to make a few minor edits, that can be done
> before the
> IESG review next week.  It is on the next telechat, so I would appreciate
> speed in
> resolving the minor comment.
>
>  Regards,
> Alia
>
>
> On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <narten@us.ibm.com> wrote:
>
>> I've followed the discussion on this thread and want to  go back to
>> something folk may have forgotten.
>>
>> More than a year ago, the WG made a considered and conscious decision
>> to "ship" the framework documemnt more or less "as is" and start work
>> on a followup architecure document. It was known and expected that the
>> architecture document would become the focus of work moving forward
>> and that substantive additions/changes would go there. Even if it
>> meant the framework document would be less complete.
>>
>> Sadly, it has been more than a year since that decision was made, yet
>> the framework document appears stalled and unable to get
>> published. I'll note that the problem statement document to which the
>> framework is a companion, has been languishing in the RFC editor queue
>> for almost a year now, blocked on a normative reference to the
>> definitions in the framework document.
>>
>> FWIW, I think the framework is good enough to publish more-or-less as
>> is. Or more to the point, there just isn't energy to make significant
>> changes to the document given that the focus of the WG has long since
>> moved to the architecture document.
>>
>> If folk have substantive issues with the framework, I'd strongly
>> suggest first looking at the architecture
>> (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
>> there, and of so, whether the archictecture document would be a better
>> place to address the concern.
>>
>> Thomas
>>
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
>>
>
>

--20cf303a2d610bf22504faee879b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Marc,<div><br></div><div>An updated draft would be excelle=
nt -before Thursday, preferably.</div><div><br></div><div>Thanks,</div><div=
>Alia</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">
On Tue, Jun 3, 2014 at 4:01 AM, LASSERRE, MARC (MARC) <span dir=3D"ltr">&lt=
;<a href=3D"mailto:marc.lasserre@alcatel-lucent.com" target=3D"_blank">marc=
.lasserre@alcatel-lucent.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">
<u></u>





<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Alia,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>=C2=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">I have replied and suggested some minor edits to address Linda and Lucy&#=
39;s comments. I have suggested to be protocol agnostic rather than giving =
specific
 examples in the multi-homing case.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Some of Linda&#39;s comments have been discussed at length in the past an=
d there was clear WG consensus that the framework draft addressed NVO3&#39;=
s problem.</font></span></div>

<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>=C2=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Let me know if you want me to post a revised draft based on these minor e=
dits and some other suggested edits from other IETF reviewers received last=
 week
 prior to next week IESG review.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>=C2=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Marc</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT:#0000ff 2px solid;PADDING-LEFT:5px;MARGIN-=
LEFT:5px;MARGIN-RIGHT:0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" align=3D"left">
<hr>
<font face=3D"Tahoma"><b>From:</b> nvo3 [mailto:<a href=3D"mailto:nvo3-boun=
ces@ietf.org" target=3D"_blank">nvo3-bounces@ietf.org</a>] <b>
On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Monday, June 02, 2014 8:59 PM<div class=3D""><br>
<b>To:</b> Thomas Narten<br>
<b>Cc:</b> <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org=
</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>;=
 Linda Dunbar<br>
</div><b>Subject:</b> Re: [nvo3] Last Call: &lt;draft-ietf-nvo3-framework-0=
6.txt&gt; (Framework for DC Network Virtualization) to Informational RFC<br=
>
</font><br>
</div><div><div class=3D"h5">
<div></div>
<div dir=3D"ltr">Thomas,
<div><br>
</div>
<div>The NVO3 Framework draft is in IETF Last Call, which isn&#39;t precise=
ly stalled.</div>
<div>It is true that Linda and Lucy have raised some concerns about it.</di=
v>
<div><br>
</div>
<div>I have not yet heard from the WG chairs or authors whether the desired=
 changes</div>
<div>have been previously discussed and had consensus determined in the WG.=
 =C2=A0Linda indicated that her</div>
<div>comments had already been discussed on the nvo3 mailing list. =C2=A0Lu=
cy is requesting that different</div>
<div>technology be indicated as examples - perhaps to give a sense of futur=
e possible solutions to the</div>
<div>readers of the draft.</div>
<div><br>
</div>
<div>If there is WG consensus to make a few minor edits, that can be done b=
efore the</div>
<div>IESG review next week. =C2=A0It is on the next telechat, so I would ap=
preciate speed in</div>
<div>resolving the minor comment.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Alia</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:narten@us.ibm.com" target=3D"_blank">narten@us.ibm.co=
m</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
I&#39;ve followed the discussion on this thread and want to =C2=A0go back t=
o<br>
something folk may have forgotten.<br>
<br>
More than a year ago, the WG made a considered and conscious decision<br>
to &quot;ship&quot; the framework documemnt more or less &quot;as is&quot; =
and start work<br>
on a followup architecure document. It was known and expected that the<br>
architecture document would become the focus of work moving forward<br>
and that substantive additions/changes would go there. Even if it<br>
meant the framework document would be less complete.<br>
<br>
Sadly, it has been more than a year since that decision was made, yet<br>
the framework document appears stalled and unable to get<br>
published. I&#39;ll note that the problem statement document to which the<b=
r>
framework is a companion, has been languishing in the RFC editor queue<br>
for almost a year now, blocked on a normative reference to the<br>
definitions in the framework document.<br>
<br>
FWIW, I think the framework is good enough to publish more-or-less as<br>
is. Or more to the point, there just isn&#39;t energy to make significant<b=
r>
changes to the document given that the focus of the WG has long since<br>
moved to the architecture document.<br>
<br>
If folk have substantive issues with the framework, I&#39;d strongly<br>
suggest first looking at the architecture<br>
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists<br>
there, and of so, whether the archictecture document would be a better<br>
place to address the concern.<br>
<span><font color=3D"#888888"><br>
Thomas<br>
</font></span>
<div>
<div><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div></div></blockquote>
</div>

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

--20cf303a2d610bf22504faee879b--


From nobody Tue Jun  3 08:09:35 2014
Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF331A016C; Tue,  3 Jun 2014 01:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 TDW-33ItEWpm; Tue,  3 Jun 2014 01:01:35 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CE2D1A0162; Tue,  3 Jun 2014 01:01:35 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s5381GxJ017464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 3 Jun 2014 03:01:18 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s53817be010384 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Jun 2014 10:01:15 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 3 Jun 2014 10:01:15 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Alia Atlas <akatlas@gmail.com>, Thomas Narten <narten@us.ibm.com>
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: AQHPdQIKiFgojcPjTkKOT8QRrMyEo5tMzYgAgBE5NoCAABcJAIAA+uBw
Date: Tue, 3 Jun 2014 08:01:14 +0000
Message-ID: <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com>
In-Reply-To: <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408CBA0FR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5xyzznTxSa8jaSJdc7fCwSf4sHU
X-Mailman-Approved-At: Tue, 03 Jun 2014 08:09:28 -0700
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 08:01:37 -0000

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

Alia,

I have replied and suggested some minor edits to address Linda and Lucy's c=
omments. I have suggested to be protocol agnostic rather than giving specif=
ic examples in the multi-homing case.
Some of Linda's comments have been discussed at length in the past and ther=
e was clear WG consensus that the framework draft addressed NVO3's problem.

Let me know if you want me to post a revised draft based on these minor edi=
ts and some other suggested edits from other IETF reviewers received last w=
eek prior to next week IESG review.

Regards,
Marc

________________________________
From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Monday, June 02, 2014 8:59 PM
To: Thomas Narten
Cc: nvo3@ietf.org; ietf@ietf.org; Linda Dunbar
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framewor=
k for DC Network Virtualization) to Informational RFC

Thomas,

The NVO3 Framework draft is in IETF Last Call, which isn't precisely stalle=
d.
It is true that Linda and Lucy have raised some concerns about it.

I have not yet heard from the WG chairs or authors whether the desired chan=
ges
have been previously discussed and had consensus determined in the WG.  Lin=
da indicated that her
comments had already been discussed on the nvo3 mailing list.  Lucy is requ=
esting that different
technology be indicated as examples - perhaps to give a sense of future pos=
sible solutions to the
readers of the draft.

If there is WG consensus to make a few minor edits, that can be done before=
 the
IESG review next week.  It is on the next telechat, so I would appreciate s=
peed in
resolving the minor comment.

Regards,
Alia


On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <narten@us.ibm.com<mailto:nar=
ten@us.ibm.com>> wrote:
I've followed the discussion on this thread and want to  go back to
something folk may have forgotten.

More than a year ago, the WG made a considered and conscious decision
to "ship" the framework documemnt more or less "as is" and start work
on a followup architecure document. It was known and expected that the
architecture document would become the focus of work moving forward
and that substantive additions/changes would go there. Even if it
meant the framework document would be less complete.

Sadly, it has been more than a year since that decision was made, yet
the framework document appears stalled and unable to get
published. I'll note that the problem statement document to which the
framework is a companion, has been languishing in the RFC editor queue
for almost a year now, blocked on a normative reference to the
definitions in the framework document.

FWIW, I think the framework is good enough to publish more-or-less as
is. Or more to the point, there just isn't energy to make significant
changes to the document given that the focus of the WG has long since
moved to the architecture document.

If folk have substantive issues with the framework, I'd strongly
suggest first looking at the architecture
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
there, and of so, whether the archictecture document would be a better
place to address the concern.

Thomas

_______________________________________________
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.23588">
</head>
<body>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Alia,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">I have replied and suggested some=
 minor edits to address Linda and Lucy's comments. I have suggested to be p=
rotocol agnostic rather than giving specific
 examples in the multi-homing case.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Some of Linda's comments have bee=
n discussed at length in the past and there was clear WG consensus that the=
 framework draft addressed NVO3's problem.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Let me know if you want me to pos=
t a revised draft based on these minor edits and some other suggested edits=
 from other IETF reviewers received last week
 prior to next week IESG review.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218335607-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Marc</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> nvo3 [mailto:nvo3-bounces@iet=
f.org] <b>
On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Monday, June 02, 2014 8:59 PM<br>
<b>To:</b> Thomas Narten<br>
<b>Cc:</b> nvo3@ietf.org; ietf@ietf.org; Linda Dunbar<br>
<b>Subject:</b> Re: [nvo3] Last Call: &lt;draft-ietf-nvo3-framework-06.txt&=
gt; (Framework for DC Network Virtualization) to Informational RFC<br>
</font><br>
</div>
<div></div>
<div dir=3D"ltr">Thomas,
<div><br>
</div>
<div>The NVO3 Framework draft is in IETF Last Call, which isn't precisely s=
talled.</div>
<div>It is true that Linda and Lucy have raised some concerns about it.</di=
v>
<div><br>
</div>
<div>I have not yet heard from the WG chairs or authors whether the desired=
 changes</div>
<div>have been previously discussed and had consensus determined in the WG.=
 &nbsp;Linda indicated that her</div>
<div>comments had already been discussed on the nvo3 mailing list. &nbsp;Lu=
cy is requesting that different</div>
<div>technology be indicated as examples - perhaps to give a sense of futur=
e possible solutions to the</div>
<div>readers of the draft.</div>
<div><br>
</div>
<div>If there is WG consensus to make a few minor edits, that can be done b=
efore the</div>
<div>IESG review next week. &nbsp;It is on the next telechat, so I would ap=
preciate speed in</div>
<div>resolving the minor comment.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Alia</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:narten@us.ibm.com" target=3D"_blank">narten@us.ibm.co=
m</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
I've followed the discussion on this thread and want to &nbsp;go back to<br=
>
something folk may have forgotten.<br>
<br>
More than a year ago, the WG made a considered and conscious decision<br>
to &quot;ship&quot; the framework documemnt more or less &quot;as is&quot; =
and start work<br>
on a followup architecure document. It was known and expected that the<br>
architecture document would become the focus of work moving forward<br>
and that substantive additions/changes would go there. Even if it<br>
meant the framework document would be less complete.<br>
<br>
Sadly, it has been more than a year since that decision was made, yet<br>
the framework document appears stalled and unable to get<br>
published. I'll note that the problem statement document to which the<br>
framework is a companion, has been languishing in the RFC editor queue<br>
for almost a year now, blocked on a normative reference to the<br>
definitions in the framework document.<br>
<br>
FWIW, I think the framework is good enough to publish more-or-less as<br>
is. Or more to the point, there just isn't energy to make significant<br>
changes to the document given that the focus of the WG has long since<br>
moved to the architecture document.<br>
<br>
If folk have substantive issues with the framework, I'd strongly<br>
suggest first looking at the architecture<br>
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists<br>
there, and of so, whether the archictecture document would be a better<br>
place to address the concern.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Thomas<br>
</font></span>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>

--_000_B30152B129674240ADF67727A967301408CBA0FR711WXCHMBA03zeu_--


From nobody Tue Jun  3 08:10:36 2014
Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872EB1A0167; Tue,  3 Jun 2014 01:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 TFR1PSOnsK7V; Tue,  3 Jun 2014 01:08:07 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A241A0162; Tue,  3 Jun 2014 01:08:06 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s5387qIc006285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 3 Jun 2014 03:07:54 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s5387HJv014086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Jun 2014 10:07:50 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 3 Jun 2014 10:07:27 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "Larry Kreeger (kreeger)" <kreeger@cisco.com>, "Ken Gray (kegray)" <kegray@cisco.com>
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: AQHPdQIKiFgojcPjTkKOT8QRrMyEo5tMzYgAgAAXToCAAAXwAIABD1GAgABBcQCAAZtmgIAGlzUAgAAUtACAAl8ssIAAQpoAgAX2RmA=
Date: Tue, 3 Jun 2014 08:07:27 +0000
Message-ID: <B30152B129674240ADF67727A967301408CBAF@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <CFA3BF05.2C990%kegray@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D23D42@dfweml701-chm.china.huawei.com> <74FD38F4-0824-45A0-8B56-40A02B903430@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D254E4@dfweml701-chm.china.huawei.com> <CFA4FAC6.2D25F%kegray@cisco.com> <CFABA416.FE778%kreeger@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D27721@dfweml701-chm.china.huawei.com> <B30152B129674240ADF67727A967301408C6F7@FR711WXCHMBA03.zeu.alcatel-lucent.com> <4A95BA014132FF49AE685FAB4B9F17F645D2975D@dfweml701-chm.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645D2975D@dfweml701-chm.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408CBAFFR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uuKDFsaTBmO4-8eNNJKN2Wjsqnc
X-Mailman-Approved-At: Tue, 03 Jun 2014 08:10:31 -0700
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 08:08:09 -0000

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

Linda,

It is a local decision to assign whatever VNI value is best suited. As I ha=
ve mentioned before, it is a locally significant value that is used as a de=
multiplexer.
An NVE can use a VLAN ID as a locally significant value if it wants to.

Marc

________________________________
From: Linda Dunbar [mailto:linda.dunbar@huawei.com]
Sent: Friday, May 30, 2014 5:02 PM
To: LASSERRE, MARC (MARC); Larry Kreeger (kreeger); Ken Gray (kegray)
Cc: nvo3@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framewor=
k for DC Network Virtualization) to Informational RFC

Marc,

Questions inserted below:

From: LASSERRE, MARC (MARC) [mailto:marc.lasserre@alcatel-lucent.com]


-       Page 13 Second bullet: the text says that each VNI is automatically=
 generated by the egress NVE. Isn't each VNI supposed to match a local virt=
ual network (e.g. represented by VLAN)? When the same NVE acts as Ingress N=
VE for the attached VMs, aren't the VNI for ingress direction statically pr=
ovisioned? Why need automatic egress VNI generation?

The value of the VN context identifier is a value locally significant to an=
 NVE and does not have to match a local virtual network. It is simply used =
as a demultiplexer. This value can be automaticaly computed or provisioned.

[Linda]If the NVE's VAPS (VNI) are connected to VMs via Ethernet where VLAN=
 is used, it is much easier to use locally significant VLAN. Why require eg=
ress to automatically generate local VNI value?  It would be better to chan=
ge the text to:

"Each VNI value on egress NVE is either mapped to locally significant Virtu=
al Network identifier (e.g. VLAN for Ethernet), or generated by NVA or Cont=
rol Plane".

Linda

nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-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.micros=
oft.com/office/2004/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.23588">
<style>@font-face {
	font-family: SimSun;
}
@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Consolas;
}
@font-face {
	font-family: @SimSun;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
P.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SI=
ZE: 12pt; mso-style-priority: 34
}
LI.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SI=
ZE: 12pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SI=
ZE: 12pt; mso-style-priority: 34
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
P.emailquote {
	FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 1pt; FONT-SIZE: 12pt;=
 MARGIN-RIGHT: 0in; mso-style-name: emailquote; mso-margin-top-alt: auto; m=
so-margin-bottom-alt: auto
}
LI.emailquote {
	FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 1pt; FONT-SIZE: 12pt;=
 MARGIN-RIGHT: 0in; mso-style-name: emailquote; mso-margin-top-alt: auto; m=
so-margin-bottom-alt: auto
}
DIV.emailquote {
	FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 1pt; FONT-SIZE: 12pt;=
 MARGIN-RIGHT: 0in; mso-style-name: emailquote; mso-margin-top-alt: auto; m=
so-margin-bottom-alt: auto
}
SPAN.EmailStyle21 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal
}
SPAN.EmailStyle22 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal
}
SPAN.EmailStyle23 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal
}
SPAN.EmailStyle25 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Linda,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">It is a local decision to assign =
whatever VNI value is best suited. As I have mentioned before, it is a loca=
lly significant value that is used as a demultiplexer.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">An&nbsp;NVE&nbsp;can use a VLAN I=
D as a locally significant value if it wants to.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"890320408-03062014"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Arial">Marc</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> Linda Dunbar [mailto:linda.du=
nbar@huawei.com]
<br>
<b>Sent:</b> Friday, May 30, 2014 5:02 PM<br>
<b>To:</b> LASSERRE, MARC (MARC); Larry Kreeger (kreeger); Ken Gray (kegray=
)<br>
<b>Cc:</b> nvo3@ietf.org; ietf@ietf.org; IETF-Announce<br>
<b>Subject:</b> RE: [nvo3] Last Call: &lt;draft-ietf-nvo3-framework-06.txt&=
gt; (Framework for DC Network Virtualization) to Informational RFC<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Marc,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Questions inserted below:<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1p=
t solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class=3D"MsoNormal"><b><span style=3D"FONT-FAMILY: 'Tahoma','sans-serif'=
; FONT-SIZE: 10pt">From:</span></b><span style=3D"FONT-FAMILY: 'Tahoma','sa=
ns-serif'; FONT-SIZE: 10pt"> LASSERRE, MARC (MARC) [mailto:marc.lasserre@al=
catel-lucent.com]
<br>
<br>
</span><o:p></o:p></p>
</div>
</div>
<blockquote style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1pt soli=
d; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 2.5pt; PADDING-LEFT: 3pt; PADDI=
NG-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-=
TOP: 0in">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: Consolas; COLOR: black; =
FONT-SIZE: 10.5pt">&nbsp;</span><span style=3D"COLOR: black"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: Consolas; COLOR: black; =
FONT-SIZE: 10.5pt">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Page 13 Second bul=
let: the text says that each VNI is automatically generated by the egress N=
VE. Isn&#8217;t each VNI supposed to match a local virtual network (e.g.
 represented by VLAN)? When the same NVE acts as Ingress NVE for the attach=
ed VMs, aren&#8217;t the VNI for ingress direction statically provisioned? =
Why need automatic egress VNI generation?&nbsp;</span><span style=3D"FONT-F=
AMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">&nbsp;</span><o:=
p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Arial','sans-serif'; CO=
LOR: blue; FONT-SIZE: 10pt">The value of the VN context identifier&nbsp;is =
a value locally significant to an NVE and does not have to match a local vi=
rtual network. It is simply&nbsp;used as a demultiplexer.&nbsp;This
 value can be automaticaly computed or provisioned.</span><span style=3D"FO=
NT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">[Linda]If the NVE&#8217;s VAPS (VNI) are c=
onnected to VMs via Ethernet where VLAN is used, it is much easier to use l=
ocally significant VLAN. Why require egress
 to automatically generate local VNI value? &nbsp;It would be better to cha=
nge the text to:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">&#8220;Each VNI value on egress NVE is eit=
her mapped to locally significant Virtual Network identifier (e.g. VLAN for=
 Ethernet), or generated by NVA or Control
 Plane&#8221;. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Linda<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">&nbsp;<o:p></o:p></span></p>
<blockquote style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1pt soli=
d; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 2.5pt; PADDING-LEFT: 3pt; PADDI=
NG-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-=
TOP: 0in">
<div>
<div>
<div>
<blockquote style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: Consolas; COLOR: black; =
FONT-SIZE: 10.5pt">nvo3 mailing list</span><span style=3D"COLOR: black"><o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"COLOR: black; FONT-SIZE: 10.5pt"><a h=
ref=3D"mailto:nvo3@ietf.org"><span style=3D"FONT-FAMILY: Consolas">nvo3@iet=
f.org</span></a></span><span style=3D"COLOR: black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"COLOR: black; FONT-SIZE: 10.5pt"><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/nvo3"><span style=3D"FONT-FAMI=
LY: Consolas">https://www.ietf.org/mailman/listinfo/nvo3</span></a></span><=
span style=3D"COLOR: black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"COLOR: black; FONT-SIZE: 10.5pt">&nbs=
p;</span><span style=3D"COLOR: black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_B30152B129674240ADF67727A967301408CBAFFR711WXCHMBA03zeu_--


From nobody Tue Jun  3 10:48:04 2014
Return-Path: <pouzin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BACA1A0431 for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 14:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.922
X-Spam-Level: 
X-Spam-Status: No, score=0.922 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 UWWWBO7B2m_T for <ietf@ietfa.amsl.com>; Mon,  2 Jun 2014 14:17:45 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28DE01A03DF for <ietf@ietf.org>; Mon,  2 Jun 2014 14:17:45 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hi2so5053186wib.2 for <ietf@ietf.org>; Mon, 02 Jun 2014 14:17:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:from:date:message-id:subject:to:cc:content-type;  bh=aF0ZRA9DDGKDbw5JCDqTe/xkKPQ8HS21S0CXLKt7Mro=; b=K+jRYd6NBzazEyIHY6OXeyDchnamizciX26DwOh6WKdYcS2lgg5FsJLt7WN7Kx2jSM zeVMaGbjh8EPuqDyoCA+M7OWztHdiVqmB5ittW9B/gu9z0pAsXmJrpeFFBKvKFp2UBig M3m5leNtz/bbgidxhaJGZLlguczsUmeBe20fXR7fifB2n+KXsAPKD9uGgKdKe1UuoFc6 NQ7dC11YTn1Y3wY35HM0cY7vSMkVu0vdtWHdTq4muH9fpIZSrJxbQyKmE5Sxy7v12kxW af/awZ2BxBFl0vUConFXUS367uxPtqO7lOTRBzO4yG/7FZ+EgpqAbNBlIdwUPy9XnZ65 +oqg==
X-Received: by 10.194.242.136 with SMTP id wq8mr53896208wjc.4.1401743858477; Mon, 02 Jun 2014 14:17:38 -0700 (PDT)
MIME-Version: 1.0
Sender: pouzin@gmail.com
Received: by 10.194.219.225 with HTTP; Mon, 2 Jun 2014 14:16:58 -0700 (PDT)
From: "Louis Pouzin (well)" <pouzin@well.com>
Date: Mon, 2 Jun 2014 23:16:58 +0200
X-Google-Sender-Auth: Vni1zoWXtSYxBo15O4p7_jZzQnA
Message-ID: <CA+EjHYpH56OpPKAL9-8jxuAPrDqou7z=JDudDvoGExZaOfChnw@mail.gmail.com>
Subject: [Internet Policy] root justification for net neutrality?
To: =?ISO-8859-1?Q?Ol=E9vi=E9_Kouami?= <olivierkouami@gmail.com>
Content-Type: multipart/alternative; boundary=089e013d172ec0317404fae0ec63
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kkCmsyVjYUhYH0NdP95v-15IX6A
X-Mailman-Approved-At: Tue, 03 Jun 2014 10:48:01 -0700
Cc: Kelvin Githira <kelvin@skysys.co.ke>, "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 21:17:46 -0000

--089e013d172ec0317404fae0ec63
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Un Roi, (one King)
Une Foi, (one Faith)
Une Loi, (one Law).

That was a French monarchy mantra.
Interesting that ICANN is picking the same dogma.

Cheers. Louis. ;-((
- - -

On Mon, Jun 2, 2014 at 10:06 PM, Ol=E9vi=E9 Kouami <olivierkouami@gmail.com=
>
wrote:

> Hi !
> Yes 4 One World, One Internet ! we said at ICANN.
> Cheer !
> -Olevie-
>
>

--089e013d172ec0317404fae0ec63
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Un Roi, (one King)<br>Une Foi, (one Faith)<br>Une Loi=
, (one Law).<br><br>That was a French monarchy mantra.<br>Interesting that =
ICANN is picking the same dogma.<br><br>Cheers. Louis. ;-((<br>- - -<br></d=
iv>

<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 2, 20=
14 at 10:06 PM, Ol=E9vi=E9 Kouami <span dir=3D"ltr">&lt;<a href=3D"mailto:o=
livierkouami@gmail.com" target=3D"_blank">olivierkouami@gmail.com</a>&gt;</=
span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>Hi !<div>Yes 4 One World, One Internet =
! we said at ICANN.</div><div>Cheer !</div><div>-Olevie-</div><br></div></b=
lockquote>

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

--089e013d172ec0317404fae0ec63--


From nobody Tue Jun  3 12:17:59 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570741A025B; Tue,  3 Jun 2014 12:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 C27ZS8PiJEzs; Tue,  3 Jun 2014 12:17:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBAA91A0032; Tue,  3 Jun 2014 12:17:53 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7C6F920029; Tue,  3 Jun 2014 15:20:55 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 260A363B0E; Tue,  3 Jun 2014 15:17:47 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 111D263AED; Tue,  3 Jun 2014 15:17:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org, WG Chairs <wgchairs@ietf.org>
Subject: second call: NomCom 2014-2015 Call for Volunteers
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 03 Jun 2014 15:17:47 -0400
Message-ID: <15721.1401823067@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TSobNlMPaSQBEFt9C6C94DPIONI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 19:17:56 -0000

--=-=-=


The IETF nominating committee (nomcom) process for 2014-15 has begun. The
IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

This is the second call for volunteers. (and you may have seen it more than
once)

If your name is on the below, then you have volunteered and are qualified.
If you have heard from me, but are not on the list, then there is some
problem, and you should have gotten a query from me to determine your
eligibility.
If you have volunteered and not heard from him, then please resend;
it got lost.

Ten voting members for the nomcom are selected in a verifiably random
way from a pool of volunteers. The more volunteers, the better chance we have
of choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!
We are at 54 volunteers so far.

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
         86(Orlando),       \
         87(Berlin),         *** ANY THREE!
         88(Vancouver),     /
         89(London)        /

If you qualify, please volunteer.   However, much as we want this, before you
decide to volunteer, please be sure you are willing to forgo appointment
to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
There will be activities to collect requirements from the community, review
candidate questionnaires, review feedback from community members about
candidates, and talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is also
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct interviews.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following information in the email body:

Your Full Name: __________--
Current Primary Affiliation:
    // Typically what goes in the Company field
    // in the IETF Registration Form
Emails: _______________
[<All email addresses used to register for the past 5 IETF meetings>]
 <Preferred email address first>
Telephone: _______________________
    // For confirmation if selected

You should expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive this response,
please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider
that nomcom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
    https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details
of the randomness seeds to be used for the RFC 3797 selection process,
within the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in alphabetical order by first name
ANM Zaheduzzaman Sarker
Adam Montville
Bill VerSteeg
Carl Williams
Carlos Martinez
Charles Eckel
DHRUV DHODY
Dacheng Zhang
Dapeng Liu
Donald Eastlake
Eric VYNCKE
Fernando Gont
Fred Baker
Gonzalo Salgueiro
Hongyu Li
Hosnieh Rafiee
Hugo Salgado
John E Drake
John Levine
John Scudder
Linda Dunbar
Lingli Deng
Louis (Lou) Berger
Luca Martini
Lucy Yong
Mach Chen
Mark Townsley
Matt Lepinski
Mehmet Ersue
Melinda Shore
Min Ye
Ning Zong
Ole Troan
Pascal Thubert
Paul Hoffman
Peter Yee
Ralph Droms
Ron Bonica
Ross Callon
Ross Finlayson
Sam K. Aldrin
Sanjay Mishra
Sheng JIANG
Shucheng Liu
Stephan Friedl
Stephan Wenger
Stephen Kent
Suhas Nandakumar
Tim Wicinski
Tissa Senevirathne
Toerless Eckert
Wassim Haddad
Xiaohu XU
Yuanlong Jiang












--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU44fWICLcPvd0N1lAQIarQf+LFgWpLCcumLdP0kpqr0bP6yYnoLjPHWK
t14P6wZ//5batKwRR7WOUlwnje4HL2w48N0i39y9KUaRguRQOoYGUjtgW0uCFoZU
rz/yAzW6X5r2jHCAcFPU5NR+YanIpXYz95z8RiG/b+tQnxmdWImuoQLblmdB5fsf
M/egVlq5H8rYkQgx6K7rLDyaq1YIgvCC/b1fwiffirF03diwBbK7NxrwixI8Q6f/
BBULBH6s1uH36zUcD/xN/wQj631v6k3aFc8afn9ErR5XDpWsjTbjJIki7j6qtYOf
E3Wc8RGVJ0MTa0aWiAnDt4iaZXRS294BYilCV9XOR9P31IbxXX/nzQ==
=/zo7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jun  3 14:00:10 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCA61A0363; Tue,  3 Jun 2014 14:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 WYNpYbw-u9-j; Tue,  3 Jun 2014 14:00:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44C5D1A0348; Tue,  3 Jun 2014 14:00:04 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s53KxsSa021656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 3 Jun 2014 13:59:57 -0700
Message-ID: <538E371C.8090602@dcrocker.net>
Date: Tue, 03 Jun 2014 13:59:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
References: <20140603201356.20543.80362.idtracker@ietfa.amsl.com>
In-Reply-To: <20140603201356.20543.80362.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 03 Jun 2014 13:59:57 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Cs9dl-_AY0bBfVolzgrjnSLmhoQ
Cc: ramk@brocade.com, diego@tid.es, dilikris@in.ibm.com, nfvrg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 21:00:09 -0000

On 6/3/2014 1:13 PM, IETF Secretariat wrote:
> The goal of Network Functions Virtualization Research Group (NFVRG) is to bring together researchers and grow the community around the world in both academia and industry to explore this new research area through workshops, research group meetings etc. at premier conferences such as IEEE ICC, IEEE Globecom and inviting special issues in well-known journals.


This is opening sentence smacks more of marketing than of IRTF work.

The topic is important, but serious work will not be be aided by such
language.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Jun  3 22:24:48 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2521A008A for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 22:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level: 
X-Spam-Status: No, score=-7.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ljEep1AxdAHk for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 22:24:46 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19CAE1A007F for <ietf@ietf.org>; Tue,  3 Jun 2014 22:24:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.98,970,1392192000";  d="asc'?scan'208";a="168157150"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx12-out.netapp.com with ESMTP; 03 Jun 2014 22:24:40 -0700
Received: from HIOEXCMBX02-PRD.hq.netapp.com (10.122.105.35) by vmwexceht05-prd.hq.netapp.com (10.106.77.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 3 Jun 2014 22:24:40 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 3 Jun 2014 22:24:38 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::d865:b6fe:275f:ffef%21]) with mapi id 15.00.0847.030; Tue, 3 Jun 2014 22:24:39 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
Thread-Topic: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
Thread-Index: AQHPf2hu37cXMsLew0WOC3DZW/EWS5tgU9oAgACNPAA=
Date: Wed, 4 Jun 2014 05:24:38 +0000
Message-ID: <EC39C028-BBBF-4248-A770-B75B83A6015F@netapp.com>
References: <20140603201356.20543.80362.idtracker@ietfa.amsl.com> <538E371C.8090602@dcrocker.net>
In-Reply-To: <538E371C.8090602@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.120.60.36]
Content-Type: multipart/signed; boundary="Apple-Mail=_ABD4054D-1EFA-42AD-BA76-438DAEA7CEC6"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Frirdf1KyApJoFBzjmI9WUmnbNQ
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 05:24:47 -0000

--Apple-Mail=_ABD4054D-1EFA-42AD-BA76-438DAEA7CEC6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2014-6-3, at 22:59, Dave Crocker <dhc@dcrocker.net> wrote:
> This is opening sentence smacks more of marketing than of IRTF work.

The list is supposed to be under irtf.org. I think it got mistakenly =
created under ietf.org. Opened a ticket to have this fixed.

Lars

--Apple-Mail=_ABD4054D-1EFA-42AD-BA76-438DAEA7CEC6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQCVAwUBU46tltZcnpRveo1xAQLoKgP/XqxLmHfXx6o85v+rW2I2GbNyOoGAgOfL
i8Kz6Q8NUSxr+yoHGGsxb8JKPdpiz+Lg/p4Lzg9lpYk6uRswVZAacTUIICNr+HZd
rCWlChku2hxPkjY9iAu52DCJFeONgPZqCnvJD4oGnGp+IgjV35P8Fa0bmL891h+X
Xddio3Pggz8=
=R28z
-----END PGP SIGNATURE-----

--Apple-Mail=_ABD4054D-1EFA-42AD-BA76-438DAEA7CEC6--


From evanleibovitch@gmail.com  Tue Jun  3 10:40:45 2014
Return-Path: <evanleibovitch@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68B21A023A for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 10:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.977
X-Spam-Level: 
X-Spam-Status: No, score=-0.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 S364j2h3E8hu for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 10:40:44 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFEF51A025E for <ietf@ietf.org>; Tue,  3 Jun 2014 10:40:42 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id uq10so5188007igb.2 for <ietf@ietf.org>; Tue, 03 Jun 2014 10:40:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HTrNPzvWkkyTmXrfucREa5T7kSvHZKDMPZWCpkYctBk=; b=aIFYexGj4+gh/cY/dgrAguuJ1LOBWsvLiYyDT6zBCcr/zqgmxUsjDdAg5nSH6Cov+6 4Rx751fAJJjtboxINVEdFMItHYZllDg5WPxOyPD65z3byv/fSzD2jdugN0EQLq+CdOAp rYkhGYL00ptJaJirdy/WB3z8lwofzxRmXLa7E6zUQhc4or1uohKpwi5gMo6baI6/Lcxz +kGXX6+18eHetE0hJUkleGnVxP4vUD6svOPeF0vC3vz83lK2dLxHBt+fS8Ug8CWnVMt7 7F35/MDthsIDcqpOiozd9pT0Bic6KZt5X4hxhF+kmwAeJNaX6cleDOfK1NLeDrZraEkd Wr+Q==
X-Received: by 10.50.131.136 with SMTP id om8mr19931310igb.49.1401817236901; Tue, 03 Jun 2014 10:40:36 -0700 (PDT)
MIME-Version: 1.0
Sender: evanleibovitch@gmail.com
Received: by 10.50.154.36 with HTTP; Tue, 3 Jun 2014 10:40:15 -0700 (PDT)
In-Reply-To: <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com>
From: Evan Leibovitch <evan@telly.org>
Date: Tue, 3 Jun 2014 13:40:15 -0400
X-Google-Sender-Auth: 3jDKpaq0wbOdJ0e_N6yvUxWW2io
Message-ID: <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
To: =?UTF-8?B?T2zDqXZpw6kgS291YW1p?= <olivierkouami@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b3a9b587217f304faf20292
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ComQwI4KRdI6LgYU8ixv4dEiNlw
X-Mailman-Approved-At: Wed, 04 Jun 2014 08:04:33 -0700
Cc: Kelvin Githira <kelvin@skysys.co.ke>, "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 17:52:51 -0000

--047d7b3a9b587217f304faf20292
Content-Type: text/plain; charset=UTF-8

Right now NN is being seen mostly from the supplier end. If overridden, it
will inevitably be seen soon enough at the end-user's side.

If you are looking to explain Net Neutrality to Internet end-users, and
especially why it is under attack in the US, I suggest this video segment
<https://www.youtube.com/watch?v=fpbOEoRrHyU>. Hosted by Jon Oliver, the
former Daily Show correspondent with his own show now on HBO, this
13-minute segment provides what is IMO one of the clearest (and cleverest)
explanations of the concepts, what is at stake, and a call to action for
Americans.

Note: Profanity exists in the original HBO broadcast, but it is bleeped out
in the YouTube version.

-- 
Evan Leibovitch
Toronto Canada

Em: evan at telly dot org
Sk: evanleibovitch
Tw: el56

--047d7b3a9b587217f304faf20292
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Right now NN is being seen mostly from the supplier end. I=
f overridden, it will inevitably be seen soon enough at the end-user&#39;s =
side.<br><br>If you are looking to explain Net Neutrality to Internet end-u=
sers, and especially why it is under attack in the US, I suggest=C2=A0<a hr=
ef=3D"https://www.youtube.com/watch?v=3DfpbOEoRrHyU">this video segment</a>=
. Hosted by Jon Oliver, the former Daily Show correspondent with his own sh=
ow now on HBO, this 13-minute segment provides what is IMO one of the clear=
est (and cleverest) explanations of the concepts, what is at stake, and a c=
all to action for Americans.<br>

<br>Note: Profanity exists in the original HBO broadcast, but it is bleeped=
 out in the YouTube version.<div class=3D"gmail_extra"><div><br></div>-- <b=
r><div style=3D"text-align:center"><div style=3D"text-align:left">Evan Leib=
ovitch</div>

<div style=3D"text-align:left">Toronto Canada</div></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div style=3D"text-align:cen=
ter"><div style=3D"text-align:left">Em: evan at telly dot org</div></div><d=
iv style=3D"text-align:center">

<div style=3D"text-align:left">Sk: evanleibovitch</div></div><div style=3D"=
text-align:center"><div style=3D"text-align:left">Tw: el56</div></div></blo=
ckquote>
</div></div>

--047d7b3a9b587217f304faf20292--


From ineedsales@gmail.com  Tue Jun  3 17:00:41 2014
Return-Path: <ineedsales@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FBB1A03A7 for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 17:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.123
X-Spam-Level: 
X-Spam-Status: No, score=0.123 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 1SLQKoFdaImG for <ietf@ietfa.amsl.com>; Tue,  3 Jun 2014 17:00:39 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE4E71A00C9 for <ietf@ietf.org>; Tue,  3 Jun 2014 17:00:39 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id va2so6971543obc.9 for <ietf@ietf.org>; Tue, 03 Jun 2014 17:00:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XT4+SkRMPcMbmZWdwruzjaeyWGSxWaGIItZt8wZTFrc=; b=pvPTuvz43CLbeFhKvRr8zEP7rF5JbgM4wrcqbe5mqrS0y5mqJchSpRDx5z8n+IUmWY 85vdVeXD/ELg2M9GbD3YEWxhndCbVNIl2VLZ2km80Gz8EmEWep4HeroSg/7p8jTJ4w5v lia77fmFxJJS7nHH7kqFEAsvSbNK3UkAwjzpLwBFSX6US5lWaJOJxAb79snAcneJCvOv +/7POG+iM0qEoHzsWjozmuqKoZDZLiJfJL09mKoxndh9WAckrrTPzyNR4mYtdeFD35/u 4N5UBQWdhRaukfmTL6kUF7T8D5w3SMIg2KWA3JZ8z4qMw3SFfRBYQuMkU1FpttB0csCB BknQ==
MIME-Version: 1.0
X-Received: by 10.182.114.194 with SMTP id ji2mr48260817obb.25.1401840033675;  Tue, 03 Jun 2014 17:00:33 -0700 (PDT)
Sender: ineedsales@gmail.com
Received: by 10.76.76.197 with HTTP; Tue, 3 Jun 2014 17:00:33 -0700 (PDT)
In-Reply-To: <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com>
Date: Tue, 3 Jun 2014 19:00:33 -0500
X-Google-Sender-Auth: LxfcYXXGd6pjhNN2yC-4i02qyGI
Message-ID: <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: Clyde C McElroy <info@articlecontentprovider.com>
To: Evan Leibovitch <evan@telly.org>
Content-Type: multipart/alternative; boundary=001a11c2ff5a3d428e04faf751a7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3LPN-oiAJ2LOusuybigTHprNk9U
X-Mailman-Approved-At: Wed, 04 Jun 2014 08:04:57 -0700
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>, =?UTF-8?B?T2zDqXZpw6kgS291YW1p?= <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 02:07:59 -0000

--001a11c2ff5a3d428e04faf751a7
Content-Type: text/plain; charset=UTF-8

Thanks for that video. That's a great way to get people to understand it,
but the FCC link provided doesn't exactly make it easy to comment. Just an
email address. Not so public. Anyone know a link where the comments can
actually be viewed by the public?


On Tue, Jun 3, 2014 at 12:40 PM, Evan Leibovitch <evan@telly.org> wrote:

> Right now NN is being seen mostly from the supplier end. If overridden, it
> will inevitably be seen soon enough at the end-user's side.
>
> If you are looking to explain Net Neutrality to Internet end-users, and
> especially why it is under attack in the US, I suggest this video segment
> <https://www.youtube.com/watch?v=fpbOEoRrHyU>. Hosted by Jon Oliver, the
> former Daily Show correspondent with his own show now on HBO, this
> 13-minute segment provides what is IMO one of the clearest (and cleverest)
> explanations of the concepts, what is at stake, and a call to action for
> Americans.
>
> Note: Profanity exists in the original HBO broadcast, but it is bleeped
> out in the YouTube version.
>
> --
> Evan Leibovitch
> Toronto Canada
>
> Em: evan at telly dot org
> Sk: evanleibovitch
> Tw: el56
>
>
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.
>

--001a11c2ff5a3d428e04faf751a7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for that video. That&#39;s a great way to get peopl=
e to understand it, but the FCC link provided doesn&#39;t exactly make it e=
asy to comment. Just an email address. Not so public. Anyone know a link wh=
ere the comments can actually be viewed by the public?</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jun 3=
, 2014 at 12:40 PM, Evan Leibovitch <span dir=3D"ltr">&lt;<a href=3D"mailto=
:evan@telly.org" target=3D"_blank">evan@telly.org</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Right now NN is being seen mostly from the supplier end. I=
f overridden, it will inevitably be seen soon enough at the end-user&#39;s =
side.<br><br>If you are looking to explain Net Neutrality to Internet end-u=
sers, and especially why it is under attack in the US, I suggest=C2=A0<a hr=
ef=3D"https://www.youtube.com/watch?v=3DfpbOEoRrHyU" target=3D"_blank">this=
 video segment</a>. Hosted by Jon Oliver, the former Daily Show corresponde=
nt with his own show now on HBO, this 13-minute segment provides what is IM=
O one of the clearest (and cleverest) explanations of the concepts, what is=
 at stake, and a call to action for Americans.<br>


<br>Note: Profanity exists in the original HBO broadcast, but it is bleeped=
 out in the YouTube version.<span class=3D"HOEnZb"><font color=3D"#888888">=
<div class=3D"gmail_extra"><div><br></div>-- <br><div style=3D"text-align:c=
enter">
<div style=3D"text-align:left">Evan Leibovitch</div>

<div style=3D"text-align:left">Toronto Canada</div></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div style=3D"text-align:cen=
ter"><div style=3D"text-align:left">Em: evan at telly dot org</div></div><d=
iv style=3D"text-align:center">


<div style=3D"text-align:left">Sk: evanleibovitch</div></div><div style=3D"=
text-align:center"><div style=3D"text-align:left">Tw: el56</div></div></blo=
ckquote>
</div></font></span></div>
<br>_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.=
org/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br></bl=
ockquote></div><br></div>

--001a11c2ff5a3d428e04faf751a7--


From nobody Wed Jun  4 08:05:13 2014
Return-Path: <ramk@Brocade.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6961A0081; Tue,  3 Jun 2014 21:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 v6Hq7OKJoSCh; Tue,  3 Jun 2014 21:58:21 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDD941A007F; Tue,  3 Jun 2014 21:58:20 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id s544wAka025649; Tue, 3 Jun 2014 21:58:10 -0700
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1m9nn7r7ma-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jun 2014 21:58:10 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 3 Jun 2014 21:58:09 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::a540:dc22:25c4:398e]) by HQ1WP-EXHUB01.corp.brocade.com ([fe80::55ee:533:4b9d:a097%12]) with mapi; Tue, 3 Jun 2014 21:58:09 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 3 Jun 2014 21:58:08 -0700
Subject: RE: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
Thread-Topic: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
Thread-Index: Ac9/bsfga3asbedhTN2KM4Wr2D8nNQAQk9og
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2C005006085@HQ1-EXCH01.corp.brocade.com>
References: <20140603201356.20543.80362.idtracker@ietfa.amsl.com> <538E371C.8090602@dcrocker.net>
In-Reply-To: <538E371C.8090602@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.14,  0.0.0000 definitions=2014-06-04_01:2014-06-02,2014-06-04,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406040063
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SMB8t7IapiB_2jZ2MfOtB-QjtIY
X-Mailman-Approved-At: Wed, 04 Jun 2014 08:05:11 -0700
Cc: "diego@tid.es" <diego@tid.es>, "dilikris@in.ibm.com" <dilikris@in.ibm.com>, "nfvrg@ietf.org" <nfvrg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 04:58:22 -0000

SGkgRGF2ZSwNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLg0KDQpIb3cgYWJvdXQgd2UgdXNl
IHRoZSBmaXJzdCAyIGxpbmVzIGZyb20gdGhlIGJhY2tncm91bmQgc2VjdGlvbiBpbiB0aGUgd2lr
aSAtIGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL2dyb3VwL2lydGYvdHJhYy93aWtpL25mdnJn
DQoNCiJOZXR3b3JrIEZ1bmN0aW9uIFZpcnR1YWxpemF0aW9uIGlzIGEga2V5IGVtZXJnaW5nIGFy
ZWEgZm9yIG5ldHdvcmsgb3BlcmF0b3JzLCBoYXJkd2FyZSBhbmQgc29mdHdhcmUgdmVuZG9ycywg
Y2xvdWQgc2VydmljZSBwcm92aWRlcnMsIGFuZCBpbiBnZW5lcmFsIG5ldHdvcmsgcHJhY3RpdGlv
bmVycyBhbmQgcmVzZWFyY2hlcnMuIFRoaXMgYXJlYSByZXF1aXJlcyBleHBsb3JpbmcgbmV3IGRp
cmVjdGlvbnMgYW5kIHdvcmtpbmcgY29sbGFib3JhdGl2ZWx5IG9uIGhvdyB0byBjcmVhdGUgbmV0
d29yayBzZXJ2aWNlcyB0aGF0IHV0aWxpemUgYSB2aXJ0dWFsaXplZCBpbmZyYXN0cnVjdHVyZS4i
DQoNClRoYW5rcywNClJhbWtpDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBE
YXZlIENyb2NrZXIgW21haWx0bzpkaGNAZGNyb2NrZXIubmV0XSANClNlbnQ6IFR1ZXNkYXksIEp1
bmUgMDMsIDIwMTQgMTo1OSBQTQ0KVG86IGlldGZAaWV0Zi5vcmcNCkNjOiByYW1raSBLcmlzaG5h
bjsgZGllZ29AdGlkLmVzOyBkaWxpa3Jpc0Bpbi5pYm0uY29tOyBuZnZyZ0BpZXRmLm9yZw0KU3Vi
amVjdDogUmU6IE5ldyBOb24tV0cgTWFpbGluZyBMaXN0OiBOZnZyZyAtLSBOZXR3b3JrIEZ1bmN0
aW9uIFZpcnR1YWxpemF0aW9uIFJlc2VhcmNoIEdyb3VwIChORlZSRykgZGlzY3Vzc2lvbiBsaXN0
DQoNCk9uIDYvMy8yMDE0IDE6MTMgUE0sIElFVEYgU2VjcmV0YXJpYXQgd3JvdGU6DQo+IFRoZSBn
b2FsIG9mIE5ldHdvcmsgRnVuY3Rpb25zIFZpcnR1YWxpemF0aW9uIFJlc2VhcmNoIEdyb3VwIChO
RlZSRykgaXMgdG8gYnJpbmcgdG9nZXRoZXIgcmVzZWFyY2hlcnMgYW5kIGdyb3cgdGhlIGNvbW11
bml0eSBhcm91bmQgdGhlIHdvcmxkIGluIGJvdGggYWNhZGVtaWEgYW5kIGluZHVzdHJ5IHRvIGV4
cGxvcmUgdGhpcyBuZXcgcmVzZWFyY2ggYXJlYSB0aHJvdWdoIHdvcmtzaG9wcywgcmVzZWFyY2gg
Z3JvdXAgbWVldGluZ3MgZXRjLiBhdCBwcmVtaWVyIGNvbmZlcmVuY2VzIHN1Y2ggYXMgSUVFRSBJ
Q0MsIElFRUUgR2xvYmVjb20gYW5kIGludml0aW5nIHNwZWNpYWwgaXNzdWVzIGluIHdlbGwta25v
d24gam91cm5hbHMuDQoNCg0KVGhpcyBpcyBvcGVuaW5nIHNlbnRlbmNlIHNtYWNrcyBtb3JlIG9m
IG1hcmtldGluZyB0aGFuIG9mIElSVEYgd29yay4NCg0KVGhlIHRvcGljIGlzIGltcG9ydGFudCwg
YnV0IHNlcmlvdXMgd29yayB3aWxsIG5vdCBiZSBiZSBhaWRlZCBieSBzdWNoIGxhbmd1YWdlLg0K
DQpkLw0KDQotLQ0KRGF2ZSBDcm9ja2VyDQpCcmFuZGVuYnVyZyBJbnRlcm5ldFdvcmtpbmcNCmJi
aXcubmV0DQo=


From nobody Wed Jun  4 08:26:28 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D799A1A00DF; Wed,  4 Jun 2014 08:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 RrisaLaU8mJT; Wed,  4 Jun 2014 08:26:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 902EE1A02DA; Wed,  4 Jun 2014 08:26:23 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s54FQCn8010458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 4 Jun 2014 08:26:15 -0700
Message-ID: <538F3A65.1080209@dcrocker.net>
Date: Wed, 04 Jun 2014 08:25:25 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ramki Krishnan <ramk@Brocade.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: New Non-WG Mailing List: Nfvrg -- Network Function Virtualization Research Group (NFVRG) discussion list
References: <20140603201356.20543.80362.idtracker@ietfa.amsl.com> <538E371C.8090602@dcrocker.net> <C7634EB63EFD984A978DFB46EA5174F2C005006085@HQ1-EXCH01.corp.brocade.com>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2C005006085@HQ1-EXCH01.corp.brocade.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 04 Jun 2014 08:26:15 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HDhy8p51BHhXOIvsE5OR0qVANmc
Cc: "diego@tid.es" <diego@tid.es>, "dilikris@in.ibm.com" <dilikris@in.ibm.com>, "nfvrg@ietf.org" <nfvrg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 15:26:26 -0000

On 6/3/2014 9:58 PM, ramki Krishnan wrote:
> How about we use the first 2 lines from the background section in the wiki - http://trac.tools.ietf.org/group/irtf/trac/wiki/nfvrg
> 
> "Network Function Virtualization is a key emerging area for network operators, hardware and software vendors, cloud service providers, and in general network practitioners and researchers. This area requires exploring new directions and working collaboratively on how to create network services that utilize a virtualized infrastructure."


That's definitely better.  Thanks.

On reflection I realized that the candidate text also does not give even
a brief explanation of what "network function visualization" means.

Announcements to broad, diverse communities need to be careful not to
assume too much prior knowledge.  So basic tutorial explanations can be
quite helpful.

Happily, the entire first paragraph of the wiki you cite provides some
reasonable text:

     Network Function Virtualization is a key emerging area for network
operators, hardware and software vendors, cloud service providers, and
in general network practitioners and researchers. This area requires
exploring new directions and working collaboratively on how to create
network services that utilize a virtualized infrastructure. Network
functions that are traditionally implemented in dedicated hardware
appliances will need to be decomposed and executed in virtual machines
running in data centers. One key goal of this new area is to reduce
capital and operating expenditures for future deployments for networks
and associated services. Another important goal is for the network
operators to be able to offer value added cloud services to their
customers. Finally, new business models will open for the provision of
network services.


So I suggest simply inserting that paragraph as the first text to
describe the list, with the revised paragraph you have suggested as the
second.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Jun  4 09:13:27 2014
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BC71A0312 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 09:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 z15AlF8H18vc for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 09:13:23 -0700 (PDT)
Received: from mip.polyamory.org (mip.polyamory.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id B47461A02FE for <ietf@ietf.org>; Wed,  4 Jun 2014 09:13:23 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 407A410760; Wed,  4 Jun 2014 12:13:17 -0400 (EDT)
Date: Wed, 4 Jun 2014 12:13:17 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Clyde C McElroy <info@articlecontentprovider.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
Message-ID: <20140604161317.GN371@mip.aaaaa.org>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FcZ0gCIg9TXUDhjw2Y3ox3nrSzE
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>, =?iso-8859-1?B?T2zDqXZpw6k=?= Kouami <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 16:13:25 -0000

Clyde C McElroy <info@articlecontentprovider.com> wrote:
> Thanks for that video. That's a great way to get people to understand it,
> but the FCC link provided doesn't exactly make it easy to comment. Just an
> email address. Not so public. Anyone know a link where the comments can
> actually be viewed by the public?

Are you referring to http://fcc.gov/comments ?
That's not just an email address.

"Net Neutrality" is there at the top as:
14-28		 Protecting and Promoting the Open Internet

You click on the "14-28" link to make a comment.
You click on the large number on the right to search already submitted
comments.  The large number is how many comments have already been
submitted for this issue.
  -- Cos


From nobody Wed Jun  4 10:12:26 2014
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C091A0306 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 eFNGSHi8cKjc for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:12:23 -0700 (PDT)
Received: from mip.polyamory.org (mip.polyamory.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id ACA861A0259 for <ietf@ietf.org>; Wed,  4 Jun 2014 10:12:23 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 9702E10760; Wed,  4 Jun 2014 13:12:14 -0400 (EDT)
Date: Wed, 4 Jun 2014 13:12:14 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Clyde C McElroy <info@articlecontentprovider.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
Message-ID: <20140604171214.GO371@mip.aaaaa.org>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <20140604161317.GN371@mip.aaaaa.org> <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JgjbKZEnaT0svRFlKQDPMgscjrs
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>, =?iso-8859-1?B?T2zDg8KpdmnDg8Kp?= Kouami <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 17:12:25 -0000

Clyde C McElroy <info@articlecontentprovider.com> wrote:
> Yeah, it wasn't working when I went there yesterday. There wasn't even a
> list of filings. Today, it just takes 10 minutes to load the comments page.

Yesterday, the front page of reddit had several of these posts:

http://www.reddit.com/r/technology/comments/275mqp/reddit_there_are_only_45000_comments_on_the_fccs/

http://www.reddit.com/r/funny/comments/275tln/john_oliver_suggests_renaming_net_neutrality/

http://www.reddit.com/r/politics/comments/2747kv/john_olivers_dramatic_appeal_to_monster_internet/

leading to this:

http://www.cnet.com/news/john-olivers-net-neutrality-rallying-cry-swamps-fcc/

  -- Cos


From nobody Wed Jun  4 16:53:00 2014
Return-Path: <serrhini@mail.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 417F51A03D8 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 16:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.15
X-Spam-Level: ***
X-Spam-Status: No, score=3.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 XKx67po_IQFA for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 16:52:55 -0700 (PDT)
Received: from f215.i.mail.ru (f215.i.mail.ru [94.100.178.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0531A03D9 for <ietf@ietf.org>; Wed,  4 Jun 2014 16:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2;  h=References:In-Reply-To:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=MO3ArXd1yMOCNv4Rxng+AB9E6etvrcYqqlZCCZQz5Ys=;  b=DA3olKdwIf6P4uHuEm4/Q5+UBSYXijVQLYfNeanJJ7zSVDtd7WpBoO40iinStbpKk3xY47P2CNns57kaDyTvoz69DKAc+nkm+T9ocmQzSmRA3T5HwfELC6bal/z+4nDoiOuNToP0UjeFRZnrLYOIeaVkl/AU7GxKAwdQRZLgWE4=;
Received: from mail by f215.i.mail.ru with local (envelope-from <serrhini@mail.ru>) id 1WsKz5-000506-DR; Thu, 05 Jun 2014 03:52:43 +0400
Received: from [41.137.68.47] by e.mail.ru with HTTP; Thu, 05 Jun 2014 03:52:43 +0400
From: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
To: =?UTF-8?B?Q2x5ZGUgQyBNY0Vscm95?= <info@articlecontentprovider.com>, =?UTF-8?B?aWV0ZkBpZXRmLm9yZw==?= <ietf@ietf.org>, =?UTF-8?B?aW50ZXJuZXRwb2xpY3k=?= <internetpolicy@elists.isoc.org>, =?UTF-8?B?aXNvYw==?= <isoc@isoc.org>
Subject: =?UTF-8?B?UmVbMl06IFtJbnRlcm5ldCBQb2xpY3ldIEZ3ZDogUmU6IHJvb3QganVzdGlm?= =?UTF-8?B?aWNhdGlvbiBmb3IgbmV0IG5ldXRyYWxpdHk/?=
Mime-Version: 1.0
X-Mailer: Mail.Ru Mailer 1.0
X-Originating-IP: [41.137.68.47]
Date: Thu, 05 Jun 2014 03:52:43 +0400
X-Priority: 3 (Normal)
Message-ID: <1401925963.788219402@f215.i.mail.ru>
Content-Type: multipart/alternative; boundary="--ALT--UUyfAAMN1401925963"
X-Mras: Ok
X-Spam: undefined
In-Reply-To: <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E1xMwQtXpiq7UPhewWG0B4eeA4s
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 23:52:57 -0000

----ALT--UUyfAAMN1401925963
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

IEZyZW5zaCB0cmFuc2NyaXB0aW9uIG9mIHZpZGVvIG9mIEhvc3RlZCBieSBKb24gT2xpdmVyIAoK
dHJhbnNjcmlyZSBldCBzb3VzLXRpdHJlciBlbiBmcmFuw6dhaXMgbGEgc8OpcXVlbmNlIGRlIEpv
aG4gT2xpdmVyIMOgIHByb3BvcyBkZSBsYSBuZXV0cmFsaXTDqSBkdSBOZXQgYXV4IFVTCsKgCmh0
dHA6Ly93d3cuZGFpbHltb3Rpb24uY29tL3ZpZGVvL3gxeWJvY2Zfam9oIEzDpnRpdGlhCgpNb2hh
bW1lZCBTZXJyaGluaQpNb3JvY2NhbiBjaGFwdGVyCgoKVHVlLCAzIEp1biAyMDE0IDE5OjAwOjMz
IC0wNTAwINC+0YIgQ2x5ZGUgQyBNY0Vscm95IDxpbmZvQGFydGljbGVjb250ZW50cHJvdmlkZXIu
Y29tPjoKPlRoYW5rcyBmb3IgdGhhdCB2aWRlby4gVGhhdCdzIGEgZ3JlYXQgd2F5IHRvIGdldCBw
ZW9wbGUgdG8gdW5kZXJzdGFuZCBpdCwgYnV0IHRoZSBGQ0MgbGluayBwcm92aWRlZCBkb2Vzbid0
IGV4YWN0bHkgbWFrZSBpdCBlYXN5IHRvIGNvbW1lbnQuIEp1c3QgYW4gZW1haWwgYWRkcmVzcy4g
Tm90IHNvIHB1YmxpYy4gQW55b25lIGtub3cgYSBsaW5rIHdoZXJlIHRoZSBjb21tZW50cyBjYW4g
YWN0dWFsbHkgYmUgdmlld2VkIGJ5IHRoZSBwdWJsaWM/Cj4KPgo+T24gVHVlLCBKdW4gMywgMjAx
NCBhdCAxMjo0MCBQTSwgRXZhbiBMZWlib3ZpdGNoICA8IGV2YW5AdGVsbHkub3JnID4gd3JvdGU6
Cj4+UmlnaHQgbm93IE5OIGlzIGJlaW5nIHNlZW4gbW9zdGx5IGZyb20gdGhlIHN1cHBsaWVyIGVu
ZC4gSWYgb3ZlcnJpZGRlbiwgaXQgd2lsbCBpbmV2aXRhYmx5IGJlIHNlZW4gc29vbiBlbm91Z2gg
YXQgdGhlIGVuZC11c2VyJ3Mgc2lkZS4KPj4KPj5JZiB5b3UgYXJlIGxvb2tpbmcgdG8gZXhwbGFp
biBOZXQgTmV1dHJhbGl0eSB0byBJbnRlcm5ldCBlbmQtdXNlcnMsIGFuZCBlc3BlY2lhbGx5IHdo
eSBpdCBpcyB1bmRlciBhdHRhY2sgaW4gdGhlIFVTLCBJIHN1Z2dlc3TCoCB0aGlzIHZpZGVvIHNl
Z21lbnQgLiBIb3N0ZWQgYnkgSm9uIE9saXZlciwgdGhlIGZvcm1lciBEYWlseSBTaG93IGNvcnJl
c3BvbmRlbnQgd2l0aCBoaXMgb3duIHNob3cgbm93IG9uIEhCTywgdGhpcyAxMy1taW51dGUgc2Vn
bWVudCBwcm92aWRlcyB3aGF0IGlzIElNTyBvbmUgb2YgdGhlIGNsZWFyZXN0IChhbmQgY2xldmVy
ZXN0KSBleHBsYW5hdGlvbnMgb2YgdGhlIGNvbmNlcHRzLCB3aGF0IGlzIGF0IHN0YWtlLCBhbmQg
YSBjYWxsIHRvIGFjdGlvbiBmb3IgQW1lcmljYW5zLgo+Pgo+Pk5vdGU6IFByb2Zhbml0eSBleGlz
dHMgaW4gdGhlIG9yaWdpbmFsIEhCTyBicm9hZGNhc3QsIGJ1dCBpdCBpcyBibGVlcGVkIG91dCBp
biB0aGUgWW91VHViZSB2ZXJzaW9uLgo+Pgo+Pi0tIAo+PkV2YW4gTGVpYm92aXRjaAo+PlRvcm9u
dG8gQ2FuYWRhCj4+PkVtOiBldmFuIGF0IHRlbGx5IGRvdCBvcmcKPj4+U2s6IGV2YW5sZWlib3Zp
dGNoCj4+PlR3OiBlbDU2Cj4+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KPj5UbyBtYW5hZ2UgeW91ciBJU09DIHN1YnNjcmlwdGlvbnMgb3IgdW5zdWJzY3Jp
YmUsCj4+cGxlYXNlIGxvZyBpbnRvIHRoZSBJU09DIE1lbWJlciBQb3J0YWw6Cj4+aHR0cHM6Ly9w
b3J0YWwuaXNvYy5vcmcvCj4+VGhlbiBjaG9vc2UgSW50ZXJlc3RzICYgU3Vic2NyaXB0aW9ucyBm
cm9tIHRoZSBNeSBBY2NvdW50IG1lbnUuCj4KCgrQoSDRg9Cy0LDQttC10L3QuNC10LwsCm1vaGFt
bWVkIHNlcnJoaW5pCnNlcnJoaW5pQG1haWwucnUK

----ALT--UUyfAAMN1401925963
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

CjxIVE1MPjxCT0RZPjxzcGFuPkZyZW5zaCB0cmFuc2NyaXB0aW9uIG9mIHZpZGVvIG9mIEhvc3Rl
ZCBieSBKb24gT2xpdmVyIDxicj48YnI+dHJhbnNjcmlyZSBldCBzb3VzLXRpdHJlciBlbiBmcmFu
w6dhaXMgbGEgc8OpcXVlbmNlIGRlIEpvaG4gT2xpdmVyIMOgIHByb3BvcyBkZSBsYSBuZXV0cmFs
aXTDqSBkdSBOZXQgYXV4IFVTPC9zcGFuPjxkaXYgaWQ9Im1hZ2ljZG9taWQ2Ij4mbmJzcDs8YnI+
PC9kaXY+PHNwYW4gY2xhc3M9IiI+PC9zcGFuPjxzcGFuIGNsYXNzPSIgdXJsIj48YSBocmVmPSJo
dHRwOi8vd3d3LmRhaWx5bW90aW9uLmNvbS92aWRlby94MXlib2NmX2pvaEwlQzMlQTZ0aXRpYSI+
aHR0cDovL3d3dy5kYWlseW1vdGlvbi5jb20vdmlkZW8veDF5Ym9jZl9qb2g8L2E+PC9zcGFuPjxz
cGFuIGNsYXNzPSJhdXRob3ItYS14YWx6ODJ6bWtkZzF6ODF6bjFkczY3IHVybCI+PGEgaHJlZj0i
aHR0cDovL3d3dy5kYWlseW1vdGlvbi5jb20vdmlkZW8veDF5Ym9jZl9qb2hMJUMzJUE2dGl0aWEi
PkzDpnRpdGlhPC9hPjwvc3Bhbj48c3BhbiBjbGFzcz0iYXV0aG9yLWEteGFsejgyem1rZGcxejgx
em4xZHM2NyI+PC9zcGFuPjxicj48YnI+TW9oYW1tZWQgU2Vycmhpbmk8YnI+TW9yb2NjYW4gY2hh
cHRlcjxicj48YnI+PGJyPlR1ZSwgMyBKdW4gMjAxNCAxOTowMDozMyAtMDUwMCDQvtGCIENseWRl
IEMgTWNFbHJveSAmbHQ7aW5mb0BhcnRpY2xlY29udGVudHByb3ZpZGVyLmNvbSZndDs6PGJyPgo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyLWxlZnQ6MXB4IHNvbGlkICMwODU3QTY7IG1hcmdpbjox
MHB4OyBwYWRkaW5nOjAgMCAwIDEwcHg7Ij4KCTxkaXYgaWQ9IiI+CgkKCgoKICAgIAoKCgoKCgoK
CgoJCgkKCgoJCgkKCQoJCgkKCgkKCQoKCQoJCgoKCjxkaXYgY2xhc3M9ImpzLWhlbHBlciBqcy1y
ZWFkbXNnLW1zZyI+Cgk8c3R5bGUgdHlwZT0idGV4dC9jc3MiPjwvc3R5bGU+CiAJPGRpdj4KCQk8
YmFzZSB0YXJnZXQ9Il9zZWxmIiBocmVmPSJodHRwczovL2UubWFpbC5ydS8iPgoJCQoJCQk8ZGl2
IGlkPSJzdHlsZV8xNDAxODk0MzUwMDAwMDAwMTAwNl9CT0RZIj48ZGl2IGRpcj0ibHRyIj5UaGFu
a3MgZm9yIHRoYXQgdmlkZW8uIFRoYXQncyBhIGdyZWF0IHdheSB0byBnZXQgcGVvcGxlIHRvIHVu
ZGVyc3RhbmQgaXQsIGJ1dCB0aGUgRkNDIGxpbmsgcHJvdmlkZWQgZG9lc24ndCBleGFjdGx5IG1h
a2UgaXQgZWFzeSB0byBjb21tZW50LiBKdXN0IGFuIGVtYWlsIGFkZHJlc3MuIE5vdCBzbyBwdWJs
aWMuIEFueW9uZSBrbm93IGEgbGluayB3aGVyZSB0aGUgY29tbWVudHMgY2FuIGFjdHVhbGx5IGJl
IHZpZXdlZCBieSB0aGUgcHVibGljPzwvZGl2Pgo8ZGl2Pjxicj48YnI+PGRpdj5PbiBUdWUsIEp1
biAzLCAyMDE0IGF0IDEyOjQwIFBNLCBFdmFuIExlaWJvdml0Y2ggPHNwYW4gZGlyPSJsdHIiPiZs
dDs8YSBocmVmPSIvL2UubWFpbC5ydS9jb21wb3NlLz9tYWlsdG89bWFpbHRvJTNhZXZhbkB0ZWxs
eS5vcmciIHRhcmdldD0iX2JsYW5rIj5ldmFuQHRlbGx5Lm9yZzwvYT4mZ3Q7PC9zcGFuPiB3cm90
ZTo8YnI+PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFw
eCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPgo8ZGl2IGRpcj0ibHRyIj5SaWdodCBub3cg
Tk4gaXMgYmVpbmcgc2VlbiBtb3N0bHkgZnJvbSB0aGUgc3VwcGxpZXIgZW5kLiBJZiBvdmVycmlk
ZGVuLCBpdCB3aWxsIGluZXZpdGFibHkgYmUgc2VlbiBzb29uIGVub3VnaCBhdCB0aGUgZW5kLXVz
ZXIncyBzaWRlLjxicj48YnI+SWYgeW91IGFyZSBsb29raW5nIHRvIGV4cGxhaW4gTmV0IE5ldXRy
YWxpdHkgdG8gSW50ZXJuZXQgZW5kLXVzZXJzLCBhbmQgZXNwZWNpYWxseSB3aHkgaXQgaXMgdW5k
ZXIgYXR0YWNrIGluIHRoZSBVUywgSSBzdWdnZXN0Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly93d3cu
eW91dHViZS5jb20vd2F0Y2g/dj1mcGJPRW9Sckh5VSIgdGFyZ2V0PSJfYmxhbmsiPnRoaXMgdmlk
ZW8gc2VnbWVudDwvYT4uIEhvc3RlZCBieSBKb24gT2xpdmVyLCB0aGUgZm9ybWVyIERhaWx5IFNo
b3cgY29ycmVzcG9uZGVudCB3aXRoIGhpcyBvd24gc2hvdyBub3cgb24gSEJPLCB0aGlzIDEzLW1p
bnV0ZSBzZWdtZW50IHByb3ZpZGVzIHdoYXQgaXMgSU1PIG9uZSBvZiB0aGUgY2xlYXJlc3QgKGFu
ZCBjbGV2ZXJlc3QpIGV4cGxhbmF0aW9ucyBvZiB0aGUgY29uY2VwdHMsIHdoYXQgaXMgYXQgc3Rh
a2UsIGFuZCBhIGNhbGwgdG8gYWN0aW9uIGZvciBBbWVyaWNhbnMuPGJyPgoKCjxicj5Ob3RlOiBQ
cm9mYW5pdHkgZXhpc3RzIGluIHRoZSBvcmlnaW5hbCBIQk8gYnJvYWRjYXN0LCBidXQgaXQgaXMg
YmxlZXBlZCBvdXQgaW4gdGhlIFlvdVR1YmUgdmVyc2lvbi48c3Bhbj48Zm9udCBjb2xvcj0iIzg4
ODg4OCI+PGRpdj48ZGl2Pjxicj48L2Rpdj4tLSA8YnI+PGRpdiBzdHlsZT0idGV4dC1hbGlnbjpj
ZW50ZXIiPgo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPkV2YW4gTGVpYm92aXRjaDwvZGl2
PgoKPGRpdiBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0Ij5Ub3JvbnRvIENhbmFkYTwvZGl2PjwvZGl2
PjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW46MCAwIDAgNDBweDtib3JkZXI6bm9uZTtwYWRkaW5n
OjBweCI+PGRpdiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPjxkaXYgc3R5bGU9InRleHQtYWxp
Z246bGVmdCI+RW06IGV2YW4gYXQgdGVsbHkgZG90IG9yZzwvZGl2PjwvZGl2PjxkaXYgc3R5bGU9
InRleHQtYWxpZ246Y2VudGVyIj4KCgo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPlNrOiBl
dmFubGVpYm92aXRjaDwvZGl2PjwvZGl2PjxkaXYgc3R5bGU9InRleHQtYWxpZ246Y2VudGVyIj48
ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPlR3OiBlbDU2PC9kaXY+PC9kaXY+PC9ibG9ja3F1
b3RlPgo8L2Rpdj48L2ZvbnQ+PC9zcGFuPjwvZGl2Pgo8YnI+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+ClRvIG1hbmFnZSB5b3VyIElTT0Mgc3Vic2Ny
aXB0aW9ucyBvciB1bnN1YnNjcmliZSw8YnI+CnBsZWFzZSBsb2cgaW50byB0aGUgSVNPQyBNZW1i
ZXIgUG9ydGFsOjxicj4KPGEgaHJlZj0iaHR0cHM6Ly9wb3J0YWwuaXNvYy5vcmcvIiB0YXJnZXQ9
Il9ibGFuayI+aHR0cHM6Ly9wb3J0YWwuaXNvYy5vcmcvPC9hPjxicj4KVGhlbiBjaG9vc2UgSW50
ZXJlc3RzICZhbXA7IFN1YnNjcmlwdGlvbnMgZnJvbSB0aGUgTXkgQWNjb3VudCBtZW51Ljxicj48
L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2PgoKPC9kaXY+CgkJCQoJCQoJCTxiYXNlIHRhcmdl
dD0iX3NlbGYiIGhyZWY9Imh0dHBzOi8vZS5tYWlsLnJ1LyI+Cgk8L2Rpdj4KCgkKPC9kaXY+CgoK
PC9kaXY+CjwvYmxvY2txdW90ZT4KPGJyPgo8YnI+0KEg0YPQstCw0LbQtdC90LjQtdC8LDxicj5t
b2hhbW1lZCBzZXJyaGluaTxicj5zZXJyaGluaUBtYWlsLnJ1PGJyPjwvQk9EWT48L0hUTUw+Cg==

----ALT--UUyfAAMN1401925963--


From nobody Thu Jun  5 00:39:38 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE78B1A00EF for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 00:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 q-vgzgQFFi_u for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 00:39:35 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56B501A009E for <ietf@ietf.org>; Thu,  5 Jun 2014 00:39:35 -0700 (PDT)
Received: from dyn-fg145.sth.netnod.se (dyn-fg145.sth.netnod.se [77.72.226.145]) by mail.frobbit.se (Postfix) with ESMTPSA id 0B4C922098; Thu,  5 Jun 2014 09:39:26 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_E8293CE8-1306-4C35-A15F-C687BB38B995"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com>
Date: Thu, 5 Jun 2014 09:39:25 +0200
Message-Id: <0F816BDA-5FE8-4891-B18A-2113518FF3D5@frobbit.se>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru> <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com> <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com>
To: Evan Leibovitch <evan@telly.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9jUjgRibZJWjK1rBeetw0lWxVzQ
Cc: isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>, "6Advocate ." <gobe.khanda@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 07:39:36 -0000

--Apple-Mail=_E8293CE8-1306-4C35-A15F-C687BB38B995
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2A2F1CEF-ED5B-4FF9-9ED9-940B61868178"


--Apple-Mail=_2A2F1CEF-ED5B-4FF9-9ED9-940B61868178
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 5 jun 2014, at 09:36, Evan Leibovitch <evan@telly.org> wrote:

> I see NN as helping to preserve innovation, smaller businesses, and =
local content. In this respect it also prevents the diminishing of local =
culture by refusing to allow its Internet traffic be denigrated to the =
benefit of larger multinationals.

+1000

   Patrik


--Apple-Mail=_2A2F1CEF-ED5B-4FF9-9ED9-940B61868178
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 5 =
jun 2014, at 09:36, Evan Leibovitch &lt;<a =
href=3D"mailto:evan@telly.org">evan@telly.org</a>&gt; wrote:<br><div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"font-family: LucidaSans-Typewriter; font-size: 10px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">I see =
NN as helping to preserve innovation, smaller businesses, and local =
content. In this respect it also prevents the diminishing of local =
culture by refusing to allow its Internet traffic be denigrated to the =
benefit of larger =
multinationals.</div></blockquote></div><br><div>+1000</div><div><br></div=
><div>&nbsp; &nbsp;Patrik</div><div><br></div></body></html>=

--Apple-Mail=_2A2F1CEF-ED5B-4FF9-9ED9-940B61868178--

--Apple-Mail=_E8293CE8-1306-4C35-A15F-C687BB38B995
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFTkB6trMabGguI180RAgLJAJ9j6CswZLtvNTbSy3BBlXW2Nsjd0gCfcRNg
b56jzo11MEdK/sdxxuC0aZg=
=hrEG
-----END PGP SIGNATURE-----

--Apple-Mail=_E8293CE8-1306-4C35-A15F-C687BB38B995--


From nobody Thu Jun  5 01:54:20 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B70B21A0438 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 01:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level: 
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=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 BUNMZXjMz_0U for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 01:54:17 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0084.outbound.protection.outlook.com [213.199.154.84]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 712141A0365 for <ietf@ietf.org>; Thu,  5 Jun 2014 01:54:17 -0700 (PDT)
Received: from DB3PRD0210HT005.eurprd02.prod.outlook.com (157.56.253.69) by DB4PR07MB249.eurprd07.prod.outlook.com (10.242.231.146) with Microsoft SMTP Server (TLS) id 15.0.954.9; Thu, 5 Jun 2014 08:54:09 +0000
Message-ID: <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
CC: ietf <ietf@ietf.org>
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de>
Subject: Mailing List reminders
Date: Thu, 5 Jun 2014 09:51:05 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.69]
X-ClientProxiedBy: DB3PR07CA004.eurprd07.prod.outlook.com (10.242.134.44) To DB4PR07MB249.eurprd07.prod.outlook.com (10.242.231.146)
X-Microsoft-Antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID:
X-Forefront-PRVS: 0233768B38
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(199002)(189002)(12213003)(93916002)(86362001)(83322001)(50466002)(50226001)(83072002)(46102001)(74662001)(85852003)(4396001)(89996001)(93886002)(92726001)(92566001)(81542001)(44736004)(104166001)(61296002)(62966002)(1671002)(74502001)(31966008)(87286001)(99396002)(77156001)(81816999)(81686999)(50986999)(76176999)(87976001)(81342001)(77982001)(84392001)(14496001)(102836001)(88136002)(21056001)(101416001)(20776003)(47776003)(64706001)(76482001)(66066001)(80022001)(42186004)(62236002)(33646001)(44716002)(79102001)(23756003)(74416001)(437434002)(7726001)(59246002)(223123001); DIR:OUT; SFP:; SCL:1; SRVR:DB4PR07MB249; H:DB3PRD0210HT005.eurprd02.prod.outlook.com; FPR:; MLV:nov; PTR:InfoNoRecords;  A:0; MX:1; LANG:en; 
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iH59dQWAqfQnLUxkbdSsSvM7zxc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 08:54:18 -0000

I used to get a reminder once a month of the mailing lists to which I am
subscribed, such as this one, but, around the time of IETF89, this
stopped working.  I see that the option on every one of the lists to
which I am subscribed has been reset to not send a reminder, not
something that I would intentionally ever do

Is this a change of policy, an announcement somewhere that I missed?

I note that the IETF web site page on Email Lists still talks of monthly
reminders without even mentioning that they are optional, which suggests
to me that it is not the policy that has changed.

Tom Petch


From nobody Thu Jun  5 04:16:36 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 227EE1A02D2 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 04:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 2cbNH9X2SbMD for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 04:16:32 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A92681A0189 for <ietf@ietf.org>; Thu,  5 Jun 2014 04:16:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1401966984; bh=nlma9F4QOTy4fokTVbDh4vz+b/O2Il8cA1QjEiNpoCE=; l=1143; h=Date:From:To:References:In-Reply-To; b=gRLRFbRcJs0FUxulUM+TTGLWvituDuvJEJSMZrow3xIgYf8GCDKY8hVk58b3svkhP eZjAK+m0SCCIng+6QQogGQevVuJd5kTN0fuqaaFCgUjPKznzTfnNbGTUFVvWVPwPEW oISaRQekMcAHdse5UakrnyKOUHoJKGUheV9eQhpE=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Thu, 05 Jun 2014 13:16:24 +0200 id 00000000005DC03F.0000000053905188.00003138
Message-ID: <53905188.7000006@tana.it>
Date: Thu, 05 Jun 2014 13:16:24 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Mailing List reminders
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
In-Reply-To: <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YEzm0hb8NC0KjxzqM2MU_zAv-XY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 11:16:34 -0000

On Thu 05/Jun/2014 10:51:05 +0200 T.p. wrote:
> I used to get a reminder once a month of the mailing lists to which I am
> subscribed, such as this one, but, around the time of IETF89, this
> stopped working.  I see that the option on every one of the lists to
> which I am subscribed has been reset to not send a reminder, not
> something that I would intentionally ever do

I'd be curious to know some more on the usefulness of reminders.
They're what I call a time-distributed database.  When subscribers
need to query the status of their subscription, they simply perform a
time seek --by waiting at most one month-- and voilÃ !

Since we've been discussing how DMARC is going to affect the fate of
mailing lists, recently on this list, I wonder why 21st century
technology doesn't offer anything better.  The outcome of that
discussion was that mailbox providers don't know the status of their
clients' subscriptions too, hence they cannot deploy any cooperative
solution such as whitelisting, weak signatures, or 3rd party auths.

Ale
-- 
"Never expect the people who caused a problem to solve it."
                                         - Albert Einstein




From nobody Thu Jun  5 04:58:09 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD431A008F for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 04:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 HHvwrx00vP2s for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 04:58:05 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id CECE21A008A for <ietf@ietf.org>; Thu,  5 Jun 2014 04:57:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id EB1DACC086 for <ietf@ietf.org>; Thu,  5 Jun 2014 07:57:52 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iEXYOIp4bZfD for <ietf@ietf.org>; Thu,  5 Jun 2014 07:57:43 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (static-173-56-67-50.nycmny.fios.verizon.net [173.56.67.50]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A64C2CC081 for <ietf@ietf.org>; Thu,  5 Jun 2014 07:57:43 -0400 (EDT)
Message-ID: <53905B37.6070300@meetinghouse.net>
Date: Thu, 05 Jun 2014 07:57:43 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Mailing List reminders
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net> <53905188.7000006@tana.it>
In-Reply-To: <53905188.7000006@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IXrQXCdf2os33zcosCDrgbnPCsw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 11:58:06 -0000

Alessandro Vesely wrote:
> On Thu 05/Jun/2014 10:51:05 +0200 T.p. wrote:
>> I used to get a reminder once a month of the mailing lists to which I am
>> subscribed, such as this one, but, around the time of IETF89, this
>> stopped working.  I see that the option on every one of the lists to
>> which I am subscribed has been reset to not send a reminder, not
>> something that I would intentionally ever do
> I'd be curious to know some more on the usefulness of reminders.
> They're what I call a time-distributed database.  When subscribers
> need to query the status of their subscription, they simply perform a
> time seek --by waiting at most one month-- and voilÃ !
>
> Since we've been discussing how DMARC is going to affect the fate of
> mailing lists, recently on this list, I wonder why 21st century
> technology doesn't offer anything better.  The outcome of that
> discussion was that mailbox providers don't know the status of their
> clients' subscriptions too, hence they cannot deploy any cooperative
> solution such as whitelisting, weak signatures, or 3rd party auths.
>

Well that's just wrong.  All the mailing lists that I administer send 
all kinds of warnings when addresses bounce, when spam is captured, and 
so forth.  I run sympa, but I expect mailman and other list managers 
provide similar administrative tools.

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Jun  5 06:31:04 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E471F1A0075; Thu,  5 Jun 2014 06:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 S7f39dJ52bkv; Thu,  5 Jun 2014 06:31:00 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 70E361A0091; Thu,  5 Jun 2014 06:31:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 94DF41E45BE; Thu,  5 Jun 2014 06:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2G6QB3fhPrUn; Thu,  5 Jun 2014 06:29:21 -0700 (PDT)
Received: from [10.30.0.121] (unknown [83.150.71.93]) by c8a.amsl.com (Postfix) with ESMTPSA id E8C541E45BC; Thu,  5 Jun 2014 06:29:20 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Subject: BOF requests due tomorrow
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: IETF Chair <chair@ietf.org>
Date: Thu, 5 Jun 2014 16:30:50 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C488C6D2-43A3-4EFD-A26E-5CE77247400F@ietf.org>
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6hxHt8hF-5CG5JMv8oHgZ0xu-yw
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF discussion list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 13:31:02 -0000

I wanted to send a reminder that all BOF requests are due tomorrow for =
the next IETF meeting - IETF-90 in Toronto.

> =95 2014-06-06 (Friday): Cut-off date for BOF proposal requests to =
Area Directors at UTC 23:59. To request a BOF, please see instructions =
on Requesting a BOF.
> =95 2014-06-13 (Friday): Cut-off date for Area Directors to approve =
BOFs at UTC 23:59.
> =95 2014-06-20 (Friday): Preliminary agenda published for comment.

More information about the IETF-90 schedule can be found here: =
http://www.ietf.org/meeting/important-dates-2014.html#IETF90

And you can of course register at =
http://www.ietf.org/meeting/register.html

Jari Arkko
Chair, IETF


From nobody Thu Jun  5 07:02:01 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822201A016B for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 07:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.251
X-Spam-Level: **
X-Spam-Status: No, score=2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.021, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=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 53FPfctVfAo5 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 07:01:55 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (unknown [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA6A1A0090 for <ietf@ietf.org>; Thu,  5 Jun 2014 07:01:55 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id E95AD41412 for <ietf@ietf.org>; Thu,  5 Jun 2014 13:59:51 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s55E1mPs022321 for <ietf@ietf.org>; Thu, 5 Jun 2014 07:01:48 -0700
Date: Thu, 5 Jun 2014 07:01:48 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Mailing List reminders
In-Reply-To: <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
Message-ID: <alpine.LRH.2.01.1406050700470.20640@egate.xpasc.com>
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mSOL0NMrjZcUvxj4EqLMshOGQ_A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 14:02:00 -0000

I seem to recall this was changed in response to the fact that the
password is included in clear text.

On Thu, 5 Jun 2014, t.p. wrote:

> I used to get a reminder once a month of the mailing lists to which I am
> subscribed, such as this one, but, around the time of IETF89, this
> stopped working.  I see that the option on every one of the lists to
> which I am subscribed has been reset to not send a reminder, not
> something that I would intentionally ever do
>
> Is this a change of policy, an announcement somewhere that I missed?
>
> I note that the IETF web site page on Email Lists still talks of monthly
> reminders without even mentioning that they are optional, which suggests
> to me that it is not the policy that has changed.
>
> Tom Petch
>


From nobody Thu Jun  5 08:03:54 2014
Return-Path: <evanleibovitch@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1534E1A00DF for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 l-9OYUYp55EO for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:08:12 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FD6C1A0312 for <ietf@ietf.org>; Wed,  4 Jun 2014 10:07:46 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id h3so6540766igd.1 for <ietf@ietf.org>; Wed, 04 Jun 2014 10:07:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=U5gmKXoGiv/zr6NuHFfIP3x+a3Ahsc3B9Pmo0ttUr04=; b=s9cUoCGlJqn29nDDznXeeL9EUWWlNAk+5x8gNMCtuBolSNnXTy8AvcAz+07mKbhy9I PimkytInaHMl9j5vBIyA2peufNQGUSSjg3WWde4ijR/8SamcZln0anRU8ZxqKok/2O6u a/BVeF/vLPr0m6/scX9suObAiNgQytkEo0iThJrD1fMxUjYvTnE7ht7Nj4knImakm35b Qei4BT6O6dTPc7sroOi16H1ar5dwZe8GhiXYrCmNNxIF8hi41NRHvKc38wx/baG+AKO6 RvJJJSBYb6LfbuvesFiiXBGhtmmMo+YpsHPNEpfuMTF51WejKzsopi8w9N/KVHBM60XT 5glw==
X-Received: by 10.50.78.8 with SMTP id x8mr9218331igw.45.1401901660000; Wed, 04 Jun 2014 10:07:40 -0700 (PDT)
MIME-Version: 1.0
Sender: evanleibovitch@gmail.com
Received: by 10.50.154.36 with HTTP; Wed, 4 Jun 2014 10:07:19 -0700 (PDT)
In-Reply-To: <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <20140604161317.GN371@mip.aaaaa.org> <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
From: Evan Leibovitch <evan@telly.org>
Date: Wed, 4 Jun 2014 13:07:19 -0400
X-Google-Sender-Auth: bAHXq7QBoHWEaNh4o47YKvFdHLM
Message-ID: <CAMguqh0h68yxzNCZLG80AXRqJmM9CxB_WYewLvsiMOMX-vEORw@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
To: Clyde C McElroy <info@articlecontentprovider.com>
Content-Type: multipart/alternative; boundary=089e01183a4c74922504fb05aaf9
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o-_NMLqVD6-SU798Ghfhldowff4
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:03:52 -0700
Cc: Ofer Inbar <cos@aaaaa.org>, "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>, =?UTF-8?B?T2zDg8KpdmnDg8KpIEtvdWFtaQ==?= <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 17:08:14 -0000

--089e01183a4c74922504fb05aaf9
Content-Type: text/plain; charset=UTF-8

www.cbc.ca/newsblogs/yourcommunity/2014/06/john-olivers-net-neutrality-rant-crashes-fcc-website.html

--089e01183a4c74922504fb05aaf9
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><a href="http://www.cbc.ca/newsblogs/yourcommunity/2014/06/john-olivers-net-neutrality-rant-crashes-fcc-website.html">www.cbc.ca/newsblogs/yourcommunity/2014/06/john-olivers-net-neutrality-rant-crashes-fcc-website.html</a><br>

<div class="gmail_extra"><br>
</div></div>

--089e01183a4c74922504fb05aaf9--


From nobody Thu Jun  5 08:04:04 2014
Return-Path: <evanleibovitch@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9331A0254 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 uVJl3z-On30i for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:41:16 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 212E51A0259 for <ietf@ietf.org>; Wed,  4 Jun 2014 10:41:16 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id uq10so6559448igb.14 for <ietf@ietf.org>; Wed, 04 Jun 2014 10:41:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=GzuR+0LXU7cznx/YmI1jDb7Pt5ylphzGaiOGBVli5ug=; b=OIGNYu9xX3pEIASU3ZfNZGyiDXQx5Wi+NJbs4xXZxjBviCqW6IL1OPhL+m0e/tys/0 e/t2JaYxkvwaKWE3/XXPf5mUM3H3NELxMP1SYO2HAgdXNMMzFD4co4lSQBjRqdozZMXo VqTHnyzl7WwXBDPdfRjy0g21JqVvWoQkxd1X6NhCQA6n8OFSnY+O9COqZdEd2E/bXQuz O+cS9YflEFBy8mmbG2H5ondT5pChJWw2RtEL5ryhm7Vl2WCPBB/BmT1GAwrYq+2gN0kU yNHWgDC2nnI3RvzjnD4HNkKeB7RJ9zxqadVwlE4oWdfb6Fy3fyx+S0SIkMnGPRZZmFi/ wpyg==
X-Received: by 10.50.66.169 with SMTP id g9mr9391480igt.49.1401903669841; Wed, 04 Jun 2014 10:41:09 -0700 (PDT)
MIME-Version: 1.0
Sender: evanleibovitch@gmail.com
Received: by 10.50.154.36 with HTTP; Wed, 4 Jun 2014 10:40:49 -0700 (PDT)
In-Reply-To: <FF8FFA1E-2CD7-4F33-BF09-95778831C6E9@christopherwilkinson.eu>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <FF8FFA1E-2CD7-4F33-BF09-95778831C6E9@christopherwilkinson.eu>
From: Evan Leibovitch <evan@telly.org>
Date: Wed, 4 Jun 2014 13:40:49 -0400
X-Google-Sender-Auth: 2ZigMNRZbqcle3UOWREqskzjlGw
Message-ID: <CAMguqh0=x8XS0pM1i6H7QazvO-WqZ6e8tk+EAUGG46QCbdFmJA@mail.gmail.com>
Subject: Re: [Internet Policy] root justification for net neutrality?
To: CW Mail <mail@christopherwilkinson.eu>
Content-Type: multipart/alternative; boundary=047d7bd6be0240151204fb062208
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NVMMvv-R_3cghg6YXfaMgRDFFg8
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:04:03 -0700
Cc: Clyde C McElroy <info@articlecontentprovider.com>, "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 17:41:17 -0000

--047d7bd6be0240151204fb062208
Content-Type: text/plain; charset=UTF-8

I think your confusion appears to stem from accidental miscommunication.

The term "root" here, from what I can read, is used in the context of "root
causes", not *THE* root in the DNS sense.


On 4 June 2014 13:36, CW Mail <mail@christopherwilkinson.eu> wrote:

> Hello: Could someone please state in one message what this thread is about?
> I do not understand the relationship between the Root and NN.
> (I am probably not alone)
>
> Just a thought
>
> CW
>
>
> On 04 Jun 2014, at 02:00, Clyde C McElroy <info@articlecontentprovider.com>
> wrote:
>
> Thanks for that video. That's a great way to get people to understand it,
> but the FCC link provided doesn't exactly make it easy to comment. Just an
> email address. Not so public. Anyone know a link where the comments can
> actually be viewed by the public?
>
>
> On Tue, Jun 3, 2014 at 12:40 PM, Evan Leibovitch <evan@telly.org> wrote:
>
>> Right now NN is being seen mostly from the supplier end. If overridden,
>> it will inevitably be seen soon enough at the end-user's side.
>>
>> If you are looking to explain Net Neutrality to Internet end-users, and
>> especially why it is under attack in the US, I suggest this video segment
>> <https://www.youtube.com/watch?v=fpbOEoRrHyU>. Hosted by Jon Oliver, the
>> former Daily Show correspondent with his own show now on HBO, this
>> 13-minute segment provides what is IMO one of the clearest (and cleverest)
>> explanations of the concepts, what is at stake, and a call to action for
>> Americans.
>>
>> Note: Profanity exists in the original HBO broadcast, but it is bleeped
>> out in the YouTube version.
>>
>> --
>> Evan Leibovitch
>> Toronto Canada
>>
>> Em: evan at telly dot org
>> Sk: evanleibovitch
>> Tw: el56
>>
>>
>> _______________________________________________
>> To manage your ISOC subscriptions or unsubscribe,
>> please log into the ISOC Member Portal:
>> https://portal.isoc.org/
>> Then choose Interests & Subscriptions from the My Account menu.
>>
>
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.
>
>
>


-- 
Evan Leibovitch
Toronto Canada

Em: evan at telly dot org
Sk: evanleibovitch
Tw: el56

--047d7bd6be0240151204fb062208
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think your confusion appears to stem from accidental mis=
communication.<div><br></div><div>The term &quot;root&quot; here, from what=
 I can read, is used in the context of &quot;root causes&quot;, not <b>THE<=
/b> root in the DNS sense.</div>

</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 4 Ju=
ne 2014 13:36, CW Mail <span dir=3D"ltr">&lt;<a href=3D"mailto:mail@christo=
pherwilkinson.eu" target=3D"_blank">mail@christopherwilkinson.eu</a>&gt;</s=
pan> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">Hello: C=
ould someone please state in one message what this thread is about?<div>I d=
o not understand the relationship between the Root and NN.</div>

<div>(I am probably not alone)</div><div><br></div><div>Just a thought</div=
><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>CW</div=
></font></span><div><div class=3D"h5"><div><br></div><div><br><div><div>On =
04 Jun 2014, at 02:00, Clyde C McElroy &lt;<a href=3D"mailto:info@articleco=
ntentprovider.com" target=3D"_blank">info@articlecontentprovider.com</a>&gt=
; wrote:</div>

<br><blockquote type=3D"cite"><div dir=3D"ltr">Thanks for that video. That&=
#39;s a great way to get people to understand it, but the FCC link provided=
 doesn&#39;t exactly make it easy to comment. Just an email address. Not so=
 public. Anyone know a link where the comments can actually be viewed by th=
e public?</div>


<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jun 3=
, 2014 at 12:40 PM, Evan Leibovitch <span dir=3D"ltr">&lt;<a href=3D"mailto=
:evan@telly.org" target=3D"_blank">evan@telly.org</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">


<div dir=3D"ltr">Right now NN is being seen mostly from the supplier end. I=
f overridden, it will inevitably be seen soon enough at the end-user&#39;s =
side.<br><br>If you are looking to explain Net Neutrality to Internet end-u=
sers, and especially why it is under attack in the US, I suggest=C2=A0<a hr=
ef=3D"https://www.youtube.com/watch?v=3DfpbOEoRrHyU" target=3D"_blank">this=
 video segment</a>. Hosted by Jon Oliver, the former Daily Show corresponde=
nt with his own show now on HBO, this 13-minute segment provides what is IM=
O one of the clearest (and cleverest) explanations of the concepts, what is=
 at stake, and a call to action for Americans.<br>




<br>Note: Profanity exists in the original HBO broadcast, but it is bleeped=
 out in the YouTube version.<span><font color=3D"#888888"><div class=3D"gma=
il_extra"><div><br></div>-- <br><div style=3D"text-align:center">
<div style=3D"text-align:left">Evan Leibovitch</div>

<div style=3D"text-align:left">Toronto Canada</div></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div style=3D"text-align:cen=
ter"><div style=3D"text-align:left">Em: evan at telly dot org</div></div><d=
iv style=3D"text-align:center">




<div style=3D"text-align:left">Sk: evanleibovitch</div></div><div style=3D"=
text-align:center"><div style=3D"text-align:left">Tw: el56</div></div></blo=
ckquote>
</div></font></span></div>
<br>_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.=
org/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br></bl=
ockquote></div><br></div>
_______________________________________________<br>To manage your ISOC subs=
criptions or unsubscribe,<br>please log into the ISOC Member Portal:<br><a =
href=3D"https://portal.isoc.org/" target=3D"_blank">https://portal.isoc.org=
/</a><br>

Then choose Interests &amp; Subscriptions from the My Account menu.</blockq=
uote></div><br></div></div></div></div></blockquote></div><br><br clear=3D"=
all"><div><br></div>-- <br><div style=3D"text-align:center"><div style=3D"t=
ext-align:left">

Evan Leibovitch</div><div style=3D"text-align:left">Toronto Canada</div></d=
iv><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><div sty=
le=3D"text-align:center"><div style=3D"text-align:left">Em: evan at telly d=
ot org</div>

</div><div style=3D"text-align:center"><div style=3D"text-align:left">Sk: e=
vanleibovitch</div></div><div style=3D"text-align:center"><div style=3D"tex=
t-align:left">Tw: el56</div></div></blockquote>
</div>

--047d7bd6be0240151204fb062208--


From nobody Thu Jun  5 08:04:22 2014
Return-Path: <evanleibovitch@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD391A009E for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 00:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.352
X-Spam-Level: **
X-Spam-Status: No, score=2.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FB_INCREASE_VOL=3.629, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 T-LUVUXggiCH for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 00:36:54 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 326BD1A006B for <ietf@ietf.org>; Thu,  5 Jun 2014 00:36:54 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id rp18so560864iec.12 for <ietf@ietf.org>; Thu, 05 Jun 2014 00:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Hvi4HTSFV3ue+CLKtY2h2nWEPhoZ+RWWwFvL3Tl+Myo=; b=jNpphtyrDC4yzW8rAp952AasMtM88vRKCEEDIjbXDVI9uxBhM9362Ak4wu/K++Etvv F1DIWYgApR7ZUBC3A3Oa+GuqpUa/eQf0TtqeZwo73fseAlaXSXU/SeC6YSsAPfqvFdmt whmFRFn4rMwRLFqUScAm47eS5Fs72DvWijtiaCcWPYk1BOCyBdyYVoHlqRzZXRgQuqPb 2Wl0mDW22lQZG2sFvyaORo/srPgTDgYFPSvLqXRKz6oPhFQrpslkMqaadfgNQOPjkw3E r5bf3sShc2/p/tODZgzObbHm1Fuejy9Y/Xazc87Oor4w43tiwIZj3emFmn9l+znnyKWa tpNw==
X-Received: by 10.50.36.106 with SMTP id p10mr17140503igj.9.1401953807713; Thu, 05 Jun 2014 00:36:47 -0700 (PDT)
MIME-Version: 1.0
Sender: evanleibovitch@gmail.com
Received: by 10.50.154.36 with HTTP; Thu, 5 Jun 2014 00:36:27 -0700 (PDT)
In-Reply-To: <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru> <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com>
From: Evan Leibovitch <evan@telly.org>
Date: Thu, 5 Jun 2014 03:36:27 -0400
X-Google-Sender-Auth: t3rkuAqM4Yck6ywBMHoSxuZm67M
Message-ID: <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
To: "6Advocate ." <gobe.khanda@gmail.com>
Content-Type: multipart/alternative; boundary=089e0115ebd0b3588604fb11ce15
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gStKehzCgHjOIaEl_--FJ4yohf0
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:04:21 -0700
Cc: isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 07:36:55 -0000

--089e0115ebd0b3588604fb11ce15
Content-Type: text/plain; charset=UTF-8

On 5 June 2014 01:03, 6Advocate . <gobe.khanda@gmail.com> wrote:

> What about the developing world, wouldn't NN define more problems
> towards ISP's, note increased traffic, also slow speeds being
> experienced currently would worsen . It would be a drag and a half.
>

I don't follow.

As I interpret the threat... without NN policy in place, a developing-world
ISP could be paid off by a foreign content firm to have its streams
delivered faster and more reliably than, say, those of domestic providers
lacking the same resources. During peak demand times the prioritized
content could even force an effective stoppage of the non-prioritized.

I see NN as helping to preserve innovation, smaller businesses, and local
content. In this respect it also prevents the diminishing of local culture
by refusing to allow its Internet traffic be denigrated to the benefit of
larger multinationals.

Please elaborate on what you see as the problems raised by NN. I'm not sure
the issue is about overall increase in volumes of traffic -- that is a
generic infrastructure issue -- but, rather, about the paid prioritization
of some types of content at the expense of others.

- Evan

--089e0115ebd0b3588604fb11ce15
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 5=
 June 2014 01:03, 6Advocate . <span dir=3D"ltr">&lt;<a href=3D"mailto:gobe.=
khanda@gmail.com" target=3D"_blank">gobe.khanda@gmail.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">

What about the developing world, wouldn&#39;t NN define more problems<br>
towards ISP&#39;s, note increased traffic, also slow speeds being<br>
experienced currently would worsen . It would be a drag and a half.<br></bl=
ockquote><div><br></div><div>I don&#39;t follow.</div><div><br></div><div>A=
s I interpret the threat... without NN policy in place, a developing-world =
ISP could be paid off by a foreign content firm to have its streams deliver=
ed faster and more reliably than, say, those of domestic providers lacking =
the same resources. During peak demand times the prioritized content could =
even force an effective stoppage of the non-prioritized.</div>

<div><br></div><div>I see NN as helping to preserve innovation, smaller bus=
inesses, and local content. In this respect it also prevents the diminishin=
g of local culture by refusing to allow its Internet traffic be denigrated =
to the benefit of larger multinationals.</div>

<div><br></div><div>Please elaborate on what you see as the problems raised=
 by NN. I&#39;m not sure the issue is about overall increase in volumes of =
traffic -- that is a generic infrastructure issue -- but, rather, about the=
 paid prioritization of some types of content at the expense of others.</di=
v>

<div><br></div><div>- Evan</div><div><br></div><div><br></div></div>
</div></div>

--089e0115ebd0b3588604fb11ce15--


From gobe.khanda@gmail.com  Wed Jun  4 22:03:28 2014
Return-Path: <gobe.khanda@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACE21A03CF for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 22:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=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 d2q4ldj3natS for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 22:03:27 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7D91A01A6 for <ietf@ietf.org>; Wed,  4 Jun 2014 22:03:27 -0700 (PDT)
Received: by mail-qg0-f50.google.com with SMTP id z60so768846qgd.9 for <ietf@ietf.org>; Wed, 04 Jun 2014 22:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=E3BVn4A8CVmNQx96xK5BUqeDYvgo+FfCW8WRevTG/EE=; b=ftaRU2kZ/Yl5t/DcEzQW9hgR/H2Z2SXe6EvGBjTay0nNNqbaITCAu5M4KGUQSD19PJ IUHj5Uv1lLCHK6k1WKazywYGdaDgcdYRHU6RbHvWR6WIAg0p7KERXLB6ANy2T763Iw9v 6IwoyY0jfEab0JHfilRHQbByLaPzapStvTq4uSB1IKtJMz8ZUpHQpm7+YyPuauUxLqdo HTzDQVtrzdoHd3vnKcxkhu9icpwcjHgSXiSxebNjIYSh1xNqNaggcbCmMXAvDKWWPsgt SZZ28SOBgvndXXtQVT7tmrAofngFbvzetX8cXHRL2NJHGicYXGUBk/z18jZKbnsBSYbs 9zdA==
MIME-Version: 1.0
X-Received: by 10.140.18.180 with SMTP id 49mr75310053qgf.105.1401944600842; Wed, 04 Jun 2014 22:03:20 -0700 (PDT)
Received: by 10.224.75.73 with HTTP; Wed, 4 Jun 2014 22:03:20 -0700 (PDT)
In-Reply-To: <1401925963.788219402@f215.i.mail.ru>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru>
Date: Thu, 5 Jun 2014 07:03:20 +0200
Message-ID: <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: "6Advocate ." <gobe.khanda@gmail.com>
To: mohammed serrhini <serrhini@mail.ru>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6_vbgwIbaeSa5E6vIxOxqDgqR6o
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:04:33 -0700
Cc: Clyde C McElroy <info@articlecontentprovider.com>, isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 05:17:42 -0000

What about the developing world, wouldn't NN define more problems
towards ISP's, note increased traffic, also slow speeds being
experienced currently would worsen . It would be a drag and a half.

On 6/5/14, mohammed serrhini <serrhini@mail.ru> wrote:
>  Frensh transcription of video of Hosted by Jon Oliver
>
> transcrire et sous-titrer en fran=C3=A7ais la s=C3=A9quence de John Olive=
r =C3=A0 propos de
> la neutralit=C3=A9 du Net aux US
>
> http://www.dailymotion.com/video/x1ybocf_joh L=C3=A6titia
>
> Mohammed Serrhini
> Moroccan chapter
>
>
> Tue, 3 Jun 2014 19:00:33 -0500 =D0=BE=D1=82 Clyde C McElroy
> <info@articlecontentprovider.com>:
>>Thanks for that video. That's a great way to get people to understand it,
>> but the FCC link provided doesn't exactly make it easy to comment. Just =
an
>> email address. Not so public. Anyone know a link where the comments can
>> actually be viewed by the public?
>>
>>
>>On Tue, Jun 3, 2014 at 12:40 PM, Evan Leibovitch  < evan@telly.org > wrot=
e:
>>>Right now NN is being seen mostly from the supplier end. If overridden, =
it
>>> will inevitably be seen soon enough at the end-user's side.
>>>
>>>If you are looking to explain Net Neutrality to Internet end-users, and
>>> especially why it is under attack in the US, I suggest=C2=A0 this video
>>> segment . Hosted by Jon Oliver, the former Daily Show correspondent wit=
h
>>> his own show now on HBO, this 13-minute segment provides what is IMO on=
e
>>> of the clearest (and cleverest) explanations of the concepts, what is a=
t
>>> stake, and a call to action for Americans.
>>>
>>>Note: Profanity exists in the original HBO broadcast, but it is bleeped
>>> out in the YouTube version.
>>>
>>>--
>>>Evan Leibovitch
>>>Toronto Canada
>>>>Em: evan at telly dot org
>>>>Sk: evanleibovitch
>>>>Tw: el56
>>>_______________________________________________
>>>To manage your ISOC subscriptions or unsubscribe,
>>>please log into the ISOC Member Portal:
>>>https://portal.isoc.org/
>>>Then choose Interests & Subscriptions from the My Account menu.
>>
>
>
> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
> mohammed serrhini
> serrhini@mail.ru
>


From nobody Thu Jun  5 08:04:49 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2881A015D; Thu,  5 Jun 2014 06:52:22 -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] autolearn=ham
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 r_qpLq4vsh2c; Thu,  5 Jun 2014 06:52:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5DA1A0078; Thu,  5 Jun 2014 06:52:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Google to Host IETF 92 in Dallas!
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140605135221.27106.15826.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jun 2014 06:52:21 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y4yG2_oYtGNjxm0NcpeMXxzf2JE
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:04:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 13:52:23 -0000

The IAOC is pleased to announce that Google will be the Host for IETF 92 in Dallas.  
The meeting will be at the Fairmont Dallas March 22 - 27, 2015.  Google is also 
sponsoring the Welcome Reception.

Google first hosted the IETF when it hosted IETF 73 in Minneapolis, and has since 
hosted the IETF at IETF 84 in Vancouver.  

Thanks Google.  We cannot support the RFC Editor, Secretariat and the IETF meetings 
without the commitment and contribution of our many Hosts and Sponsors.  

Many sponsorship opportunities are still available:  
<http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf>.  
If interested contact Andrew Dvorshak, dvorshak@isoc.org.

Just 45 days until IETF 90 in Toronto!
Register at: <http://www.ietf.org/meetings/90/>

See you in Toronto!

Ray
IAD

2014 Meeting Venues

IETF 89  London  Hilton Metropole  March 2 - 7                 Host:  ICANN
IETF 90  Toronto  Fairmont Royal York Hotel  July 20 - 25  Host:  Ericsson
IETF 91  Honolulu  Hilton Hawaiian Village  Nov 9 - 14       Host: Cisco

2015

IETF 92  Dallas  March 22 - 27     Host:  GOOGLE
IETF 93  Prague	  July 19 - 24       Host:  ?
IETF 94  Yokohama  Nov 1 - 6     Host:  WIDE

2016

IETF 95  Latin America  Host:  ?
IETF 96  Berlin		    Host:  ?
IETF 97  Asia		    Host:  ?


From nobody Thu Jun  5 08:05:48 2014
Return-Path: <ineedsales@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AEA1A00DF for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 09:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 C7dAuhjdPE5n for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 09:20:46 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B059A1A02B5 for <ietf@ietf.org>; Wed,  4 Jun 2014 09:20:46 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id va2so8037442obc.9 for <ietf@ietf.org>; Wed, 04 Jun 2014 09:20:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Be9vQ23KLfnRQv2Dm9CLRLyAU79L8JHIOTvZYBnHDEw=; b=VN+1/6LQOatBuobxdFfVHAde5BU5hmeU8c/OecYFK8pv8NWVArdO1HLMJnFBDCkvXS QiLAouy/+gp1OniAqQ0gQLAGKd9pXOTamGVqty3lBSSrpYtDA+GeP2KH45Guyphd1Sui 5ft6ARwLIP2ZIQvdX6uchroi1wPAhJTcez0ItMTY+6aVzkRKTUaal+5OxdbsN7fKiQPI qjWk7MR2ydx/MRC5kShnxkhFExdt7yhQqOfiHIVFFKjt3EV7Ih3rf5EyxfGJUsdNzsw4 LMpjwZyFnoW3cpnTzgRBf5oDfD5Pvo42+Rhrq5UQ/zDSAJxw+80UoSxYMguyHEasfGpn bBfg==
MIME-Version: 1.0
X-Received: by 10.182.219.166 with SMTP id pp6mr11581155obc.65.1401898840520;  Wed, 04 Jun 2014 09:20:40 -0700 (PDT)
Sender: ineedsales@gmail.com
Received: by 10.76.76.197 with HTTP; Wed, 4 Jun 2014 09:20:40 -0700 (PDT)
In-Reply-To: <20140604161317.GN371@mip.aaaaa.org>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <20140604161317.GN371@mip.aaaaa.org>
Date: Wed, 4 Jun 2014 11:20:40 -0500
X-Google-Sender-Auth: jomtdC40ZAVM4FvX2rv6ix6bLZI
Message-ID: <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: Clyde C McElroy <info@articlecontentprovider.com>
To: Ofer Inbar <cos@aaaaa.org>
Content-Type: multipart/alternative; boundary=089e0149455466e04a04fb0502ba
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/alx6KvXxZ_zZmwnoeS1H2ZvtYYY
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:05:47 -0700
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>, =?UTF-8?B?T2zDg8KpdmnDg8KpIEtvdWFtaQ==?= <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 16:20:48 -0000

--089e0149455466e04a04fb0502ba
Content-Type: text/plain; charset=UTF-8

Yeah, it wasn't working when I went there yesterday. There wasn't even a
list of filings. Today, it just takes 10 minutes to load the comments page.


On Wed, Jun 4, 2014 at 11:13 AM, Ofer Inbar <cos@aaaaa.org> wrote:

> Clyde C McElroy <info@articlecontentprovider.com> wrote:
> > Thanks for that video. That's a great way to get people to understand it,
> > but the FCC link provided doesn't exactly make it easy to comment. Just
> an
> > email address. Not so public. Anyone know a link where the comments can
> > actually be viewed by the public?
>
> Are you referring to http://fcc.gov/comments ?
> That's not just an email address.
>
> "Net Neutrality" is there at the top as:
> 14-28            Protecting and Promoting the Open Internet
>
> You click on the "14-28" link to make a comment.
> You click on the large number on the right to search already submitted
> comments.  The large number is how many comments have already been
> submitted for this issue.
>   -- Cos
>

--089e0149455466e04a04fb0502ba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yeah, it wasn&#39;t working when I went there yesterday. T=
here wasn&#39;t even a list of filings. Today, it just takes 10 minutes to =
load the comments page.</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">
On Wed, Jun 4, 2014 at 11:13 AM, Ofer Inbar <span dir=3D"ltr">&lt;<a href=
=3D"mailto:cos@aaaaa.org" target=3D"_blank">cos@aaaaa.org</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
<div class=3D"">Clyde C McElroy &lt;<a href=3D"mailto:info@articlecontentpr=
ovider.com">info@articlecontentprovider.com</a>&gt; wrote:<br>
&gt; Thanks for that video. That&#39;s a great way to get people to underst=
and it,<br>
&gt; but the FCC link provided doesn&#39;t exactly make it easy to comment.=
 Just an<br>
&gt; email address. Not so public. Anyone know a link where the comments ca=
n<br>
&gt; actually be viewed by the public?<br>
<br>
</div>Are you referring to <a href=3D"http://fcc.gov/comments" target=3D"_b=
lank">http://fcc.gov/comments</a> ?<br>
That&#39;s not just an email address.<br>
<br>
&quot;Net Neutrality&quot; is there at the top as:<br>
14-28 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Protecting and Promoting the=
 Open Internet<br>
<br>
You click on the &quot;14-28&quot; link to make a comment.<br>
You click on the large number on the right to search already submitted<br>
comments. =C2=A0The large number is how many comments have already been<br>
submitted for this issue.<br>
=C2=A0 -- Cos<br>
</blockquote></div><br></div>

--089e0149455466e04a04fb0502ba--


From nobody Thu Jun  5 08:06:10 2014
Return-Path: <ineedsales@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24C51A02E1 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 11:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 eTqspBnYtIL9 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 11:05:42 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35AA21A0319 for <ietf@ietf.org>; Wed,  4 Jun 2014 11:05:42 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wo20so8071194obc.21 for <ietf@ietf.org>; Wed, 04 Jun 2014 11:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2z2SDLt06jqQ+/ou56MO10QPZJvlyUUkcC64cwCRKTU=; b=UQUV3iUVlnghJ9F0rPTqt4FW5lKPdg7lO8wZUEphXzZmO8i9SwyOpECmcXba+ND+wa Ws+td2QyulUqFcc9ss6Fv0E65Z0VV2cbmjnIjHUQWE1PQxvjXbjEpEcYQEVuGfdNnxFy xLwM9QY8kHgxg/TTAGee/nCToLAxlY6e94iQgOgGsckyU93sJnelzH9x9TYLuEYxK+MF P9IuJTn5JN9bPClKbS5t2fd1XjZXnJUP5cKVyE9CThTz1Hn0HbuZ9+FPI2giltl+NFyr m0NLi8TfF3nxljmFx0+f1nljONRC2nmzKY1sSDp/i9T5htLiTOQdkAzuaQxpEJ4mFQuO psEw==
MIME-Version: 1.0
X-Received: by 10.60.173.228 with SMTP id bn4mr60976006oec.27.1401905135909; Wed, 04 Jun 2014 11:05:35 -0700 (PDT)
Sender: ineedsales@gmail.com
Received: by 10.76.76.197 with HTTP; Wed, 4 Jun 2014 11:05:35 -0700 (PDT)
In-Reply-To: <CAMguqh0h68yxzNCZLG80AXRqJmM9CxB_WYewLvsiMOMX-vEORw@mail.gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <20140604161317.GN371@mip.aaaaa.org> <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com> <CAMguqh0h68yxzNCZLG80AXRqJmM9CxB_WYewLvsiMOMX-vEORw@mail.gmail.com>
Date: Wed, 4 Jun 2014 13:05:35 -0500
X-Google-Sender-Auth: A8kpM3BTUrF6Sx4D9lGqQ8yCkuc
Message-ID: <CAMPgnKGWuDkh4t4tRSw7kBF_AJcvb15E1PMzP5bfQL0_LsxX9A@mail.gmail.com>
Subject: Re: [Internet Policy] Fwd: Re: root justification for net neutrality?
From: Clyde C McElroy <info@articlecontentprovider.com>
To: Evan Leibovitch <evan@telly.org>
Content-Type: multipart/alternative; boundary=089e0118254aa280cb04fb06791e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DrU-TpuoGQ4n0zd0SRwPr9GCg9o
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:06:07 -0700
Cc: Ofer Inbar <cos@aaaaa.org>, "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>, =?UTF-8?B?T2zDg8KpdmnDg8KpIEtvdWFtaQ==?= <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 18:05:44 -0000

--089e0118254aa280cb04fb06791e
Content-Type: text/plain; charset=UTF-8

That's great. Good message to send the FCC that the deal isn't popular
among users. Glad he did that video. Maybe that'll make it harder to
approve, who knows?


On Wed, Jun 4, 2014 at 12:07 PM, Evan Leibovitch <evan@telly.org> wrote:

>
> www.cbc.ca/newsblogs/yourcommunity/2014/06/john-olivers-net-neutrality-rant-crashes-fcc-website.html
>
>

--089e0118254aa280cb04fb06791e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">That&#39;s great. Good message to send the FCC that the de=
al isn&#39;t popular among users. Glad he did that video. Maybe that&#39;ll=
 make it harder to approve, who knows?</div><div class=3D"gmail_extra"><br>=
<br>
<div class=3D"gmail_quote">On Wed, Jun 4, 2014 at 12:07 PM, Evan Leibovitch=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:evan@telly.org" target=3D"_blank">=
evan@telly.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><a href=3D"http://www.cbc.ca/newsblogs/yourcommunity/2014/=
06/john-olivers-net-neutrality-rant-crashes-fcc-website.html" target=3D"_bl=
ank">www.cbc.ca/newsblogs/yourcommunity/2014/06/john-olivers-net-neutrality=
-rant-crashes-fcc-website.html</a><br>


<div class=3D"gmail_extra"><br>
</div></div>
</blockquote></div><br></div>

--089e0118254aa280cb04fb06791e--


From mail@christopherwilkinson.eu  Wed Jun  4 10:36:35 2014
Return-Path: <mail@christopherwilkinson.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF50A1A0306 for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.019
X-Spam-Level: 
X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 zd1NBsTq3h5M for <ietf@ietfa.amsl.com>; Wed,  4 Jun 2014 10:36:33 -0700 (PDT)
Received: from authsmtp.register.it (authsmtp11.register.it [81.88.48.50]) by ietfa.amsl.com (Postfix) with ESMTP id D02D31A0359 for <ietf@ietf.org>; Wed,  4 Jun 2014 10:36:18 -0700 (PDT)
Received: from [192.168.1.33] ([88.9.226.16]) by paganini33 with  id AHc81o00V0MrLGQ01Hc9s5; Wed, 04 Jun 2014 19:36:11 +0200
X-Rid: smtp@christopherwilkinson.eu@88.9.226.16
Content-Type: multipart/alternative; boundary="Apple-Mail=_7A2ED951-94F1-43FA-A7CE-122B4D4995F2"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Internet Policy] root justification for net neutrality?
From: CW Mail <mail@christopherwilkinson.eu>
In-Reply-To: <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
Date: Wed, 4 Jun 2014 19:36:07 +0200
Message-Id: <FF8FFA1E-2CD7-4F33-BF09-95778831C6E9@christopherwilkinson.eu>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com>
To: Clyde C McElroy <info@articlecontentprovider.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nm-Y-OoaDKXXO6QhDWRLWkfIFf0
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:06:43 -0700
Cc: "internetpolicy@elists.isoc.org" <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 17:42:04 -0000

--Apple-Mail=_7A2ED951-94F1-43FA-A7CE-122B4D4995F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello: Could someone please state in one message what this thread is =
about?
I do not understand the relationship between the Root and NN.
(I am probably not alone)

Just a thought

CW


On 04 Jun 2014, at 02:00, Clyde C McElroy =
<info@articlecontentprovider.com> wrote:

> Thanks for that video. That's a great way to get people to understand =
it, but the FCC link provided doesn't exactly make it easy to comment. =
Just an email address. Not so public. Anyone know a link where the =
comments can actually be viewed by the public?
>=20
>=20
> On Tue, Jun 3, 2014 at 12:40 PM, Evan Leibovitch <evan@telly.org> =
wrote:
> Right now NN is being seen mostly from the supplier end. If =
overridden, it will inevitably be seen soon enough at the end-user's =
side.
>=20
> If you are looking to explain Net Neutrality to Internet end-users, =
and especially why it is under attack in the US, I suggest this video =
segment. Hosted by Jon Oliver, the former Daily Show correspondent with =
his own show now on HBO, this 13-minute segment provides what is IMO one =
of the clearest (and cleverest) explanations of the concepts, what is at =
stake, and a call to action for Americans.
>=20
> Note: Profanity exists in the original HBO broadcast, but it is =
bleeped out in the YouTube version.
>=20
> --=20
> Evan Leibovitch
> Toronto Canada
> Em: evan at telly dot org
> Sk: evanleibovitch
> Tw: el56
>=20
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.
>=20
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.


--Apple-Mail=_7A2ED951-94F1-43FA-A7CE-122B4D4995F2
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello: Could someone please state in one message what this thread is about?<div>I do not understand the relationship between the Root and NN.</div><div>(I am probably not alone)</div><div><br></div><div>Just a thought</div><div><br></div><div>CW</div><div><br></div><div><br><div><div>On 04 Jun 2014, at 02:00, Clyde C McElroy &lt;<a href="mailto:info@articlecontentprovider.com">info@articlecontentprovider.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Thanks for that video. That's a great way to get people to understand it, but the FCC link provided doesn't exactly make it easy to comment. Just an email address. Not so public. Anyone know a link where the comments can actually be viewed by the public?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 12:40 PM, Evan Leibovitch <span dir="ltr">&lt;<a href="mailto:evan@telly.org" target="_blank">evan@telly.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Right now NN is being seen mostly from the supplier end. If overridden, it will inevitably be seen soon enough at the end-user's side.<br><br>If you are looking to explain Net Neutrality to Internet end-users, and especially why it is under attack in the US, I suggest&nbsp;<a href="https://www.youtube.com/watch?v=fpbOEoRrHyU" target="_blank">this video segment</a>. Hosted by Jon Oliver, the former Daily Show correspondent with his own show now on HBO, this 13-minute segment provides what is IMO one of the clearest (and cleverest) explanations of the concepts, what is at stake, and a call to action for Americans.<br>


<br>Note: Profanity exists in the original HBO broadcast, but it is bleeped out in the YouTube version.<span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><div><br></div>-- <br><div style="text-align:center">
<div style="text-align:left">Evan Leibovitch</div>

<div style="text-align:left">Toronto Canada</div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div style="text-align:center"><div style="text-align:left">Em: evan at telly dot org</div></div><div style="text-align:center">


<div style="text-align:left">Sk: evanleibovitch</div></div><div style="text-align:center"><div style="text-align:left">Tw: el56</div></div></blockquote>
</div></font></span></div>
<br>_______________________________________________<br>
To manage your ISOC subscriptions or unsubscribe,<br>
please log into the ISOC Member Portal:<br>
<a href="https://portal.isoc.org/" target="_blank">https://portal.isoc.org/</a><br>
Then choose Interests &amp; Subscriptions from the My Account menu.<br></blockquote></div><br></div>
_______________________________________________<br>To manage your ISOC subscriptions or unsubscribe,<br>please log into the ISOC Member Portal:<br><a href="https://portal.isoc.org/">https://portal.isoc.org/</a><br>Then choose Interests &amp; Subscriptions from the My Account menu.</blockquote></div><br></div></body></html>
--Apple-Mail=_7A2ED951-94F1-43FA-A7CE-122B4D4995F2--


From nobody Thu Jun  5 08:17:22 2014
Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615371A00F8; Thu,  5 Jun 2014 01:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 UgMiz0SOpreY; Thu,  5 Jun 2014 01:11:39 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1F1A1A00F0; Thu,  5 Jun 2014 01:11:38 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s558BPgS009310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jun 2014 03:11:26 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s558BIqL005124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Jun 2014 10:11:24 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Thu, 5 Jun 2014 10:10:59 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Alia Atlas <akatlas@gmail.com>
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: AQHPdQIKiFgojcPjTkKOT8QRrMyEo5tMzYgAgBE5NoCAABcJAIAA+uBwgAA8BICAAuxEMA==
Date: Thu, 5 Jun 2014 08:10:59 +0000
Message-ID: <B30152B129674240ADF67727A967301408DF69@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com> <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com> <CAG4d1rfKk_b=DqYwj+rd-KjbJzfqgd86kbzApd+Ae19Gve1SKQ@mail.gmail.com>
In-Reply-To: <CAG4d1rfKk_b=DqYwj+rd-KjbJzfqgd86kbzApd+Ae19Gve1SKQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408DF69FR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oid6nrWZTM7zLp_t9K5QghGbOE0
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:17:20 -0700
Cc: Thomas Narten <narten@us.ibm.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 08:11:47 -0000

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

Alia,

As discussed, a revised -07 draft has been posted.

Thanks,
Marc

________________________________
From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Tuesday, June 03, 2014 3:31 PM
To: LASSERRE, MARC (MARC)
Cc: Thomas Narten; nvo3@ietf.org; ietf@ietf.org; Linda Dunbar
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framewor=
k for DC Network Virtualization) to Informational RFC

Marc,

An updated draft would be excellent -before Thursday, preferably.

Thanks,
Alia


On Tue, Jun 3, 2014 at 4:01 AM, LASSERRE, MARC (MARC) <marc.lasserre@alcate=
l-lucent.com<mailto:marc.lasserre@alcatel-lucent.com>> wrote:
Alia,

I have replied and suggested some minor edits to address Linda and Lucy's c=
omments. I have suggested to be protocol agnostic rather than giving specif=
ic examples in the multi-homing case.
Some of Linda's comments have been discussed at length in the past and ther=
e was clear WG consensus that the framework draft addressed NVO3's problem.

Let me know if you want me to post a revised draft based on these minor edi=
ts and some other suggested edits from other IETF reviewers received last w=
eek prior to next week IESG review.

Regards,
Marc

________________________________
From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] On =
Behalf Of Alia Atlas
Sent: Monday, June 02, 2014 8:59 PM

To: Thomas Narten
Cc: nvo3@ietf.org<mailto:nvo3@ietf.org>; ietf@ietf.org<mailto:ietf@ietf.org=
>; Linda Dunbar
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framewor=
k for DC Network Virtualization) to Informational RFC

Thomas,

The NVO3 Framework draft is in IETF Last Call, which isn't precisely stalle=
d.
It is true that Linda and Lucy have raised some concerns about it.

I have not yet heard from the WG chairs or authors whether the desired chan=
ges
have been previously discussed and had consensus determined in the WG.  Lin=
da indicated that her
comments had already been discussed on the nvo3 mailing list.  Lucy is requ=
esting that different
technology be indicated as examples - perhaps to give a sense of future pos=
sible solutions to the
readers of the draft.

If there is WG consensus to make a few minor edits, that can be done before=
 the
IESG review next week.  It is on the next telechat, so I would appreciate s=
peed in
resolving the minor comment.

Regards,
Alia


On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <narten@us.ibm.com<mailto:nar=
ten@us.ibm.com>> wrote:
I've followed the discussion on this thread and want to  go back to
something folk may have forgotten.

More than a year ago, the WG made a considered and conscious decision
to "ship" the framework documemnt more or less "as is" and start work
on a followup architecure document. It was known and expected that the
architecture document would become the focus of work moving forward
and that substantive additions/changes would go there. Even if it
meant the framework document would be less complete.

Sadly, it has been more than a year since that decision was made, yet
the framework document appears stalled and unable to get
published. I'll note that the problem statement document to which the
framework is a companion, has been languishing in the RFC editor queue
for almost a year now, blocked on a normative reference to the
definitions in the framework document.

FWIW, I think the framework is good enough to publish more-or-less as
is. Or more to the point, there just isn't energy to make significant
changes to the document given that the focus of the WG has long since
moved to the architecture document.

If folk have substantive issues with the framework, I'd strongly
suggest first looking at the architecture
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
there, and of so, whether the archictecture document would be a better
place to address the concern.

Thomas

_______________________________________________
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.23588">
</head>
<body>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014">Alia,</span></font></div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014"></span></font>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014">As discussed, a&nbsp;revised -07 =
draft has been posted.</span></font></div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014"></span></font>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014">Thanks,</span></font></div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" size=3D"2" face=3D"=
Arial"><span class=3D"046300908-05062014">Marc</span></font></div>
<font color=3D"#0000ff" size=3D"2" face=3D"Arial"></font><br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> nvo3 [mailto:nvo3-bounces@iet=
f.org] <b>
On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Tuesday, June 03, 2014 3:31 PM<br>
<b>To:</b> LASSERRE, MARC (MARC)<br>
<b>Cc:</b> Thomas Narten; nvo3@ietf.org; ietf@ietf.org; Linda Dunbar<br>
<b>Subject:</b> Re: [nvo3] Last Call: &lt;draft-ietf-nvo3-framework-06.txt&=
gt; (Framework for DC Network Virtualization) to Informational RFC<br>
</font><br>
</div>
<div></div>
<div dir=3D"ltr">Marc,
<div><br>
</div>
<div>An updated draft would be excellent -before Thursday, preferably.</div=
>
<div><br>
</div>
<div>Thanks,</div>
<div>Alia</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Tue, Jun 3, 2014 at 4:01 AM, LASSERRE, MARC (=
MARC) <span dir=3D"ltr">
&lt;<a href=3D"mailto:marc.lasserre@alcatel-lucent.com" target=3D"_blank">m=
arc.lasserre@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<u></u>
<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Alia,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">I have replied and suggested some minor edits to address Linda and Lucy's=
 comments. I have suggested to be protocol agnostic rather than giving spec=
ific examples in the multi-homing case.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Some of Linda's comments have been discussed at length in the past and th=
ere was clear WG consensus that the framework draft addressed NVO3's proble=
m.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Let me know if you want me to post a revised draft based on these minor e=
dits and some other suggested edits from other IETF reviewers received last=
 week prior to next week IESG review.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
">Marc</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" align=3D"left">
<hr>
<font face=3D"Tahoma"><b>From:</b> nvo3 [mailto:<a href=3D"mailto:nvo3-boun=
ces@ietf.org" target=3D"_blank">nvo3-bounces@ietf.org</a>]
<b>On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Monday, June 02, 2014 8:59 PM
<div><br>
<b>To:</b> Thomas Narten<br>
<b>Cc:</b> <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org=
</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">
ietf@ietf.org</a>; Linda Dunbar<br>
</div>
<b>Subject:</b> Re: [nvo3] Last Call: &lt;draft-ietf-nvo3-framework-06.txt&=
gt; (Framework for DC Network Virtualization) to Informational RFC<br>
</font><br>
</div>
<div>
<div class=3D"h5">
<div></div>
<div dir=3D"ltr">Thomas,
<div><br>
</div>
<div>The NVO3 Framework draft is in IETF Last Call, which isn't precisely s=
talled.</div>
<div>It is true that Linda and Lucy have raised some concerns about it.</di=
v>
<div><br>
</div>
<div>I have not yet heard from the WG chairs or authors whether the desired=
 changes</div>
<div>have been previously discussed and had consensus determined in the WG.=
 &nbsp;Linda indicated that her</div>
<div>comments had already been discussed on the nvo3 mailing list. &nbsp;Lu=
cy is requesting that different</div>
<div>technology be indicated as examples - perhaps to give a sense of futur=
e possible solutions to the</div>
<div>readers of the draft.</div>
<div><br>
</div>
<div>If there is WG consensus to make a few minor edits, that can be done b=
efore the</div>
<div>IESG review next week. &nbsp;It is on the next telechat, so I would ap=
preciate speed in</div>
<div>resolving the minor comment.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Alia</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:narten@us.ibm.com" target=3D"_blank">narten@us.ibm.co=
m</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
I've followed the discussion on this thread and want to &nbsp;go back to<br=
>
something folk may have forgotten.<br>
<br>
More than a year ago, the WG made a considered and conscious decision<br>
to &quot;ship&quot; the framework documemnt more or less &quot;as is&quot; =
and start work<br>
on a followup architecure document. It was known and expected that the<br>
architecture document would become the focus of work moving forward<br>
and that substantive additions/changes would go there. Even if it<br>
meant the framework document would be less complete.<br>
<br>
Sadly, it has been more than a year since that decision was made, yet<br>
the framework document appears stalled and unable to get<br>
published. I'll note that the problem statement document to which the<br>
framework is a companion, has been languishing in the RFC editor queue<br>
for almost a year now, blocked on a normative reference to the<br>
definitions in the framework document.<br>
<br>
FWIW, I think the framework is good enough to publish more-or-less as<br>
is. Or more to the point, there just isn't energy to make significant<br>
changes to the document given that the focus of the WG has long since<br>
moved to the architecture document.<br>
<br>
If folk have substantive issues with the framework, I'd strongly<br>
suggest first looking at the architecture<br>
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists<br>
there, and of so, whether the archictecture document would be a better<br>
place to address the concern.<br>
<span><font color=3D"#888888"><br>
Thomas<br>
</font></span>
<div>
<div><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>

--_000_B30152B129674240ADF67727A967301408DF69FR711WXCHMBA03zeu_--


From nashton@consensus.pro  Thu Jun  5 02:51:13 2014
Return-Path: <nashton@consensus.pro>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B31E31A0420 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 02:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.583
X-Spam-Level: 
X-Spam-Status: No, score=-1.583 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 ghjqEkyOD41x for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 02:51:12 -0700 (PDT)
Received: from mx03.mykolab.com (mx01.mykolab.com [95.128.36.1]) (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 C382D1A0151 for <ietf@ietf.org>; Thu,  5 Jun 2014 02:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at kolabsys.net
Sender: nashton@consensus.pro
Content-Type: multipart/signed; boundary="Apple-Mail=_488FF2E5-D07B-4360-B6CE-53FF0497C853"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Re: [Internet Policy] root justification for net neutrality?
From: Nick Ashton-Hart <nashton@consensus.pro>
In-Reply-To: <0F816BDA-5FE8-4891-B18A-2113518FF3D5@frobbit.se>
Date: Thu, 5 Jun 2014 11:50:32 +0200
Message-Id: <CED7FEEC-238E-4F18-AF76-3C767A496031@consensus.pro>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru> <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com> <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com> <0F816BDA-5FE8-4891-B18A-2113518FF3D5@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fLKTk757fyx5cTA-xZiv_WRKq30
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:17:31 -0700
Cc: isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 09:52:23 -0000

--Apple-Mail=_488FF2E5-D07B-4360-B6CE-53FF0497C853
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2F0F02D3-612B-4109-85A6-1D10B84C1475"


--Apple-Mail=_2F0F02D3-612B-4109-85A6-1D10B84C1475
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

+1001 :)

On 5 Jun 2014, at 09:39, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:

> On 5 jun 2014, at 09:36, Evan Leibovitch <evan@telly.org> wrote:
>=20
>> I see NN as helping to preserve innovation, smaller businesses, and =
local content. In this respect it also prevents the diminishing of local =
culture by refusing to allow its Internet traffic be denigrated to the =
benefit of larger multinationals.
>=20
> +1000
>=20
>    Patrik
>=20
> _______________________________________________
> To manage your ISOC subscriptions or unsubscribe,
> please log into the ISOC Member Portal:
> https://portal.isoc.org/
> Then choose Interests & Subscriptions from the My Account menu.


--Apple-Mail=_2F0F02D3-612B-4109-85A6-1D10B84C1475
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">+1001 =
:)<br>
<br><div style=3D""><div>On 5 Jun 2014, at 09:39, Patrik F=E4ltstr=F6m =
&lt;<a href=3D"mailto:paf@frobbit.se">paf@frobbit.se</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 5 =
jun 2014, at 09:36, Evan Leibovitch &lt;<a =
href=3D"mailto:evan@telly.org">evan@telly.org</a>&gt; wrote:<br><div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"font-family: LucidaSans-Typewriter; font-size: 10px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">I see =
NN as helping to preserve innovation, smaller businesses, and local =
content. In this respect it also prevents the diminishing of local =
culture by refusing to allow its Internet traffic be denigrated to the =
benefit of larger =
multinationals.</div></blockquote></div><br><div>+1000</div><div><br></div=
><div>&nbsp; =
&nbsp;Patrik</div><div><br></div></div>___________________________________=
____________<br>To manage your ISOC subscriptions or =
unsubscribe,<br>please log into the ISOC Member Portal:<br><a =
href=3D"https://portal.isoc.org/">https://portal.isoc.org/</a><br>Then =
choose Interests &amp; Subscriptions from the My Account =
menu.</blockquote></div><br></body></html>=

--Apple-Mail=_2F0F02D3-612B-4109-85A6-1D10B84C1475--

--Apple-Mail=_488FF2E5-D07B-4360-B6CE-53FF0497C853
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQGcBAEBCgAGBQJTkD1pAAoJEEVwc7dMrV004vcL/0YKamaM1ghvHtQSc8sf3wJu
qwGDifs1ShBEiunjRSXRWfQUpLRVNzMCAr55tK05ybvoHs0evSgYTfXEmhx/Uis+
igb3EzMwyo5TAYjPHJn//PcdALgtIcm0fTMfnZrwYlnlhpfIR7IHOsztQzqyCVnf
4kbcYA2LgXrNLvncLINmca/XATb28QmvDGb1YQmm+yWKZpuEbLvP7FHSI1LVQZsT
R1Fii9+kPvrIXS0aFfe6AJeURZTqoz5uyG6355mIXE8CbyBsBrtPCjnuiLyhpuO/
peISMn2thfdVuXS23XbgU58Y979k/sN6AXTix5h3QucR9+H5cVy/kbR3vOOlLKW6
ePwnFCC2qacHZOczK4zJgPB6tCgB5nZf3Pz0r/ZGNuOuA2P8jXMj6eEap6mzvnUj
+TeaN7uoxHlElMOCkeGWTbdIovnZxdrQnHR5D4ndAZdiOLYE7Q90oh6yXofm19je
DxhjlRP4/JAhzRBTxWT435GAtLKwMdiSK2xCLUhaeA==
=+q7e
-----END PGP SIGNATURE-----

--Apple-Mail=_488FF2E5-D07B-4360-B6CE-53FF0497C853--


From nobody Thu Jun  5 08:17:52 2014
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88BEA1A00ED for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 05:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 1IReTzN1Y6kR for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 05:39:32 -0700 (PDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B0151A00EA for <ietf@ietf.org>; Thu,  5 Jun 2014 05:39:31 -0700 (PDT)
Received: from [193.110.157.228] (unknown [76.10.157.65]) by bofh.nohats.ca (Postfix) with ESMTPSA id 1E93B800C9; Thu,  5 Jun 2014 08:39:24 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1401971964; bh=RJHbSN73b9Wrjc2fA0DjadYFf1/6+Mlje1cAVTrt7tY=; h=References:In-Reply-To:Cc:From:Subject:Date:To; b=ISoQuVAnErYGp9dIAmZxbIKpqJBX+xSPw9m8xE0IAuS+mNsvjdIl91fggS8ST5CiA 50ZF7gMmj395R5LLjas6wiaDFIgmThb6VDsydOvYXowBuwbhBBy9xsrH4wYnsOkmNp cS75PlA2cHtS1lLuuEttB3sguXIYcrM+i80PGRKg=
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E79741D-3A4A-45CA-931F-4064D438A732@nohats.ca>
X-Mailer: iPhone Mail (11D201)
From: Paul <paul@nohats.ca>
Subject: Re: Mailing List reminders
Date: Thu, 5 Jun 2014 08:39:25 -0400
To: "t.p." <daedulus@btconnect.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EcVEC7A2qR5UlJhFG6EwEkV7M4M
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:17:40 -0700
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 12:39:34 -0000

Sent from my iPhone

>=20
> I note that the IETF web site page on Email Lists still talks of monthly
> reminders=20

I unfortunately still got one from the ietf mailman on June 1st. But perhaps=
 I was grandfathered in.=20

Paul=


From nobody Thu Jun  5 08:18:08 2014
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B161A02F0; Wed,  4 Jun 2014 13:26:35 -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, SPF_PASS=-0.001] autolearn=ham
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 1DTVCfptiHHA; Wed,  4 Jun 2014 13:26:32 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 584491A0085; Wed,  4 Jun 2014 13:26:32 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id a13so1503053igq.15 for <multiple recipients>; Wed, 04 Jun 2014 13:26:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=T2y1ay30n2BlO5i7aEusTsh8a9iYN/KrVLDtohm+9yY=; b=ZBBRpq0qOhvK94tr2pziM9XRkK4GEVjeleZ86iSMHst9w/Lyrs941o7aFNQ+Tz48gv GY7Z0jQ/wsrBia0Y2Z89w0T1drnJ3lFVIBh2V6NBIbGAvm41rDY+xZibG+4PL1h5ZcDg AARmLzSOGbrRoC5gFul+vzvXmSJ4TmA0PVG44IdgRfUQ6nRcJYfUE4vned4RMAK9IFd4 d4KgvlOXRQHvEbiYsew79B4aLJ+rY79t9v5IPc/rUDIB/dldjwvyT9g+Vvn5Pe4YkBSL rL3DqFYlM6HbHa9LATEuZS7wtQIcFHfshU7iottpdpFpsGKo3IqQNMhkFgjLIpwE8uuB C4BQ==
X-Received: by 10.50.79.131 with SMTP id j3mr11034737igx.23.1401913586054; Wed, 04 Jun 2014 13:26:26 -0700 (PDT)
Received: from [192.168.1.103] (CPE0013100e2c51-CM001cea35caa6.cpe.net.cable.rogers.com. [99.231.3.110]) by mx.google.com with ESMTPSA id l5sm31669063igr.15.2014.06.04.13.26.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Jun 2014 13:26:25 -0700 (PDT)
Message-ID: <538F80EC.2@gmail.com>
Date: Wed, 04 Jun 2014 16:26:20 -0400
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: WG Review: Authentication and Authorization for Constrained Environments (ace)
References: <20140604191407.685.47510.idtracker@ietfa.amsl.com>
In-Reply-To: <20140604191407.685.47510.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------000506070105050605050504"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mpVYElTJ5KJuSg6YmugP5sSUpz8
X-Mailman-Approved-At: Thu, 05 Jun 2014 08:18:02 -0700
Cc: ace WG <ace@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 20:26:35 -0000

This is a multi-part message in MIME format.
--------------000506070105050605050504
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Kathleen:

I do not want to be a pain, but in the rev-06 doc the timeline is still 
the old one (see excerpt copied in .txt reference). I believe it should 
have been the one below from one of the previous messages:

Dec 2014 Submit "Use cases and Requirements" as a WG item.

Dec 2014 Submit "Authentication and Authorization Solution" as a WG item.

Apr 2015 Optionally, submit "Use cases and Requirements" documentto the 
IESG for publication as an Informational RFC.

Jul 2016 Submit "Authentication and Authorization Solution"specification 
to the IESG for publication as a Proposed Standard.


Milestones (as mentioned in http://www.ietf.org/charter/charter-ietf-ace-00-06.txt):

Jul 2014 Submit "Use cases and Requirements" as a WG item.
Dec 2014 Submit "Authentication and Authorization Solution" as a WG item.
Apr 2015 Optionally, submit "Use cases and Requirements" document to the IESG for publication as an Informational RFC.
Jul 2016 Submit "Authentication and Authorization Solution"
specification to the IESG for publication as a Proposed Standard.



On 6/4/2014 3:14 PM, The IESG wrote:
> A new IETF working group has been proposed in the Security Area. The IESG
> has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please send
> your comments to the IESG mailing list (iesg at ietf.org) by 2014-06-14.
>
> Authentication and Authorization for Constrained Environments (ace)
> ------------------------------------------------
> Current Status: Proposed WG
>
> Chairs:
>    Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
>    Kepeng Li <likepeng@huawei.com>
>
> Assigned Area Director:
>    Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
>
> Mailing list
>    Address: ace@ietf.org
>    To Subscribe: https://www.ietf.org/mailman/listinfo/ace
>    Archive: http://www.ietf.org/mail-archive/web/ace/current/maillist.html
>
> Charter:
>
> Authentication and Authorization for Constrained
> Environment (ACE)
>
> The IETF has recently developed protocols for use in constrained
> environments, where network nodes are limited in CPU, memory and power.
> REST architecture is widely used for such constrained environments.
> It has been observed that Internet protocols can be applied to these
> constrained environments, often only requiring minor tweaking and
> profiling. In other cases, new protocols have been defined to address
> the specific requirements of constrained environments. An example of
> such a protocol is the Constrained Application Protocol (CoAP).
>
> As in other environments, authentication and authorization questions
> also arise in constrained environments. For example, a door lock has to
> authorize the person seeking access using a "digital key". Where is the
> authorization policy stored? How does the digital key communicate with
> the lock? Does the lock interact with an authorization server to obtain
> authorization information? How can access be temporarily granted to
> other persons? How can access be revoked? These types of questions have
> been answered by existing protocols for use cases outside constrained
> environments, however in constrained environments, additional and
> different requirements pose challenges for the use of various security
> protocols. In particular, the need arises for a dynamic and fine grained
> access control mechanism, where clients and/or resource servers are
> constrained.
>
> The IETF has a long history in developing three-party authentication and
> authorization protocols for distributed environments. Examples include
> Kerberos, the Public Key Infrastructure (PKI), the Authentication,
> Authorization and Accounting (AAA) infrastructure, and the Web
> Authorization Protocol (OAuth). All these protocols enjoy widespread
> deployment on the Internet. Although they all aim to solve a similar
> goal, at an abstract level, they offer quite different functions and
> utilize different message exchanges. These differences result from the
> main deployment use cases they were designed for respectively.
>
> Requirements derived from use cases may indicate that existing work is
> useful as basis for a solution for constrained environments. These
> protocols, however, were not optimized for constrained environments.
> Additional requirements that need to be taken into account are the lack
> of a suitable user-interface and the inability of embedded devices to
> contact an authorization server in real-time with every resource access
> request due to intermittent connectivity, etc.
>
> This working group therefore aims to produce a standardized solution for
> authentication and authorization to enable authorized access (Get, Put,
> Post, Delete) to resources identified by a URI and hosted on a resource
> server in constrained environments. As a starting point, the working
> group will assume that access to resources at a resource server by a
> client device takes place using CoAP and is protected by DTLS. Both
> resource server and client may be constrained. This access will be
> mediated by an authorization server, which is not considered to be
> constrained.
>
> Existing authentication and authorization protocols will be evaluated
> and used where applicable to build the constrained-environment solution.
> This requires relevant specifications to be reviewed for suitability,
> selecting a subset of them and restricting the options within each of
> the specifications. Some functionality, however, may not be available in
> existing protocols, in which case the solution may also involve new
> protocol work. Leveraging existing work means the working group benefits
> from available security analysis, implementation, and deployment
> experience. Moreover, a standardized solution for federated
> authentication and authorization will help to stimulate the deployment
> of constrained devices that provide increased security.
>
> Once progress in identifying suitable candidate solutions has been made,
> the working group will verify whether the same mechanisms are also
> applicable beyond the use of CoAP and DTLS, which are the two main
> protocols the group will focus on for access to resources. In
> particular, the ability to use the developed solution over HTTP and TLS
> will be investigated. Note that the initial focus is on CoAP and HTTP
> with DTLS and TLS. Other security protocols may be considered as long as
> the primary focus is maintained. The group is scoped to work only on the
> web protocols and data carried within them. Furthermore, to guarantee
> smooth transition, the integration with existing deployments will be
> studied, particularly concerning the use of protocol translation
> proxies.
>
> This work does not make the assumption that the party offering
> application layer services is always the same party offering network
> access services.
>
> The working group has the following tasks:
>
> 1) Produce use cases and requirements
>
> 2) Identify authentication and authorization mechanisms suitable for
> resource access in constrained environments.
>
> Milestones:
>
> Jul 2014 Submit "Use cases and Requirements" as a WG item.
> Dec 2014 Submit "Authentication and Authorization Solution" as a WG
>           item.
> Apr 2015 Optionally, submit "Use cases and Requirements" document to the
>           IESG for publication as an Informational RFC.
> Jul 2016 Submit "Authentication and Authorization Solution"
>           specification to the IESG for publication as a Proposed
>           Standard.
>


-- 
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363


--------------000506070105050605050504
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Kathleen:<br>
      <br>
      I do not want to be a pain, but in the rev-06 doc the timeline is
      still the old one (see excerpt copied in .txt reference). I
      believe it should have been the one below from one of the previous
      messages:<br>
      <br>
      <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
          lang="EN-US">Dec 2014 Submit "Use cases and Requirements" as a
          WG item.</span></p>
      <div>
        <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
            lang="EN-US">Dec 2014 Submit "Authentication and
            Authorization Solution" as a WG item.</span></p>
      </div>
      <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
          lang="EN-US">Apr 2015 Optionally, submit "Use cases and
          Requirements" document</span><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
          lang="EN-US"> to the IESG for publication as an Informational
          RFC.</span> </p>
      <div>
        <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
            lang="EN-US">Jul 2016 Submit "Authentication and
            Authorization Solution"</span><span
style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
            lang="EN-US"> specification to the IESG for publication as a
            Proposed Standard.</span></p>
      </div>
      <br>
      <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space: pre-wrap;">Milestones (as mentioned in <a class="moz-txt-link-freetext" href="http://www.ietf.org/charter/charter-ietf-ace-00-06.txt">http://www.ietf.org/charter/charter-ietf-ace-00-06.txt</a>):

Jul 2014 Submit "Use cases and Requirements" as a WG item.
Dec 2014 Submit "Authentication and Authorization Solution" as a WG item.
Apr 2015 Optionally, submit "Use cases and Requirements" document to the IESG for publication as an Informational RFC.
Jul 2016 Submit "Authentication and Authorization Solution"
specification to the IESG for publication as a Proposed Standard.</pre>
      <br>
      <br>
      On 6/4/2014 3:14 PM, The IESG wrote:<br>
    </div>
    <blockquote
      cite="mid:20140604191407.685.47510.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">A new IETF working group has been proposed in the Security Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2014-06-14.

Authentication and Authorization for Constrained Environments (ace)
------------------------------------------------
Current Status: Proposed WG

Chairs:
  Hannes Tschofenig <a class="moz-txt-link-rfc2396E" href="mailto:Hannes.Tschofenig@gmx.net">&lt;Hannes.Tschofenig@gmx.net&gt;</a>
  Kepeng Li <a class="moz-txt-link-rfc2396E" href="mailto:likepeng@huawei.com">&lt;likepeng@huawei.com&gt;</a>

Assigned Area Director:
  Kathleen Moriarty <a class="moz-txt-link-rfc2396E" href="mailto:Kathleen.Moriarty.ietf@gmail.com">&lt;Kathleen.Moriarty.ietf@gmail.com&gt;</a>

Mailing list
  Address: <a class="moz-txt-link-abbreviated" href="mailto:ace@ietf.org">ace@ietf.org</a>
  To Subscribe: <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ace">https://www.ietf.org/mailman/listinfo/ace</a>
  Archive: <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/ace/current/maillist.html">http://www.ietf.org/mail-archive/web/ace/current/maillist.html</a>

Charter:

Authentication and Authorization for Constrained
Environment (ACE)

The IETF has recently developed protocols for use in constrained
environments, where network nodes are limited in CPU, memory and power.  
REST architecture is widely used for such constrained environments.
It has been observed that Internet protocols can be applied to these
constrained environments, often only requiring minor tweaking and
profiling. In other cases, new protocols have been defined to address
the specific requirements of constrained environments. An example of
such a protocol is the Constrained Application Protocol (CoAP).

As in other environments, authentication and authorization questions
also arise in constrained environments. For example, a door lock has to
authorize the person seeking access using a "digital key". Where is the
authorization policy stored? How does the digital key communicate with
the lock? Does the lock interact with an authorization server to obtain
authorization information? How can access be temporarily granted to
other persons? How can access be revoked? These types of questions have
been answered by existing protocols for use cases outside constrained
environments, however in constrained environments, additional and
different requirements pose challenges for the use of various security
protocols. In particular, the need arises for a dynamic and fine grained
access control mechanism, where clients and/or resource servers are
constrained.

The IETF has a long history in developing three-party authentication and
authorization protocols for distributed environments. Examples include
Kerberos, the Public Key Infrastructure (PKI), the Authentication,
Authorization and Accounting (AAA) infrastructure, and the Web
Authorization Protocol (OAuth). All these protocols enjoy widespread
deployment on the Internet. Although they all aim to solve a similar
goal, at an abstract level, they offer quite different functions and
utilize different message exchanges. These differences result from the
main deployment use cases they were designed for respectively.

Requirements derived from use cases may indicate that existing work is
useful as basis for a solution for constrained environments. These
protocols, however, were not optimized for constrained environments. 
Additional requirements that need to be taken into account are the lack 
of a suitable user-interface and the inability of embedded devices to 
contact an authorization server in real-time with every resource access 
request due to intermittent connectivity, etc.

This working group therefore aims to produce a standardized solution for
authentication and authorization to enable authorized access (Get, Put,
Post, Delete) to resources identified by a URI and hosted on a resource
server in constrained environments. As a starting point, the working
group will assume that access to resources at a resource server by a
client device takes place using CoAP and is protected by DTLS. Both
resource server and client may be constrained. This access will be
mediated by an authorization server, which is not considered to be
constrained.

Existing authentication and authorization protocols will be evaluated 
and used where applicable to build the constrained-environment solution. 
This requires relevant specifications to be reviewed for suitability,
selecting a subset of them and restricting the options within each of 
the specifications. Some functionality, however, may not be available in
existing protocols, in which case the solution may also involve new
protocol work. Leveraging existing work means the working group benefits
from available security analysis, implementation, and deployment
experience. Moreover, a standardized solution for federated
authentication and authorization will help to stimulate the deployment
of constrained devices that provide increased security.

Once progress in identifying suitable candidate solutions has been made,
the working group will verify whether the same mechanisms are also
applicable beyond the use of CoAP and DTLS, which are the two main
protocols the group will focus on for access to resources. In
particular, the ability to use the developed solution over HTTP and TLS
will be investigated. Note that the initial focus is on CoAP and HTTP
with DTLS and TLS. Other security protocols may be considered as long as 
the primary focus is maintained. The group is scoped to work only on the 
web protocols and data carried within them. Furthermore, to guarantee 
smooth transition, the integration with existing deployments will be 
studied, particularly concerning the use of protocol translation 
proxies.

This work does not make the assumption that the party offering
application layer services is always the same party offering network
access services.

The working group has the following tasks:

1) Produce use cases and requirements

2) Identify authentication and authorization mechanisms suitable for
resource access in constrained environments.

Milestones:

Jul 2014 Submit "Use cases and Requirements" as a WG item.
Dec 2014 Submit "Authentication and Authorization Solution" as a WG 
         item.
Apr 2015 Optionally, submit "Use cases and Requirements" document to the
         IESG for publication as an Informational RFC.
Jul 2016 Submit "Authentication and Authorization Solution"
         specification to the IESG for publication as a Proposed 
         Standard.

</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
email: <a class="moz-txt-link-abbreviated" href="mailto:rstruik.ext@gmail.com">rstruik.ext@gmail.com</a> | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363</pre>
  </body>
</html>

--------------000506070105050605050504--


From nobody Thu Jun  5 10:41:12 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0071A0123 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 10:41:09 -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, SPF_PASS=-0.001] autolearn=ham
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 xcEQfF8ncV0g for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 10:41:07 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D410A1A011F for <ietf@ietf.org>; Thu,  5 Jun 2014 10:41:06 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so11020139wib.5 for <ietf@ietf.org>; Thu, 05 Jun 2014 10:40:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=SpAZyrEpOl2sy17ArKfp/PFJ2RvuzqCV1SrfXVXfk1w=; b=xoFwqhmoi6g0TlUSBokKS3vT4Vjv33i13jVufswWtDQhpi7GuABnJwDEqtBcR4Z5bV Tv2hm9HP53LsskYTuFZFac4nwqUm/HrWYFTeryxqaaAggGCE/FDuZ4NHJP7SBQQg2/O+ ZSIGEF0EOSEcbwMAFXgYQkgxTRc1/bFoUM1pxGUkcugvzqRPaG+AnNa22HU5IQq0+9od /SHPdV2IEO0b9sYywBubpQTJPdSmbf+++3ZGSStzLQIHk8plYK/IDvqhvlIf4rHfdVxZ LxVgJquprdCLo/qKJtOd6f0HjfDvgMrCqOd8tZYMMSRydU5gCBSxivu7R1hkFMyNdUUw rYrg==
X-Received: by 10.180.93.163 with SMTP id cv3mr18137457wib.3.1401990058201; Thu, 05 Jun 2014 10:40:58 -0700 (PDT)
Received: from [192.168.1.102] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id na4sm55296101wic.21.2014.06.05.10.40.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 10:40:57 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_73585953-1475-44B3-90FC-0056116A3633"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [Internet Policy] root justification for net neutrality?
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com>
Date: Thu, 5 Jun 2014 20:40:53 +0300
Message-Id: <E954E0D7-DEBF-411A-9D3E-4AE500737CD2@gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru> <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com> <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com>
To: Evan Leibovitch <evan@telly.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/80HnWou94yWpgnTE1tUPCf_oy0o
Cc: isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, "ietf@ietf.org" <ietf@ietf.org>, "6Advocate ." <gobe.khanda@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 17:41:09 -0000

--Apple-Mail=_73585953-1475-44B3-90FC-0056116A3633
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jun 5, 2014, at 10:36 AM, Evan Leibovitch <evan@telly.org> wrote:

> On 5 June 2014 01:03, 6Advocate . <gobe.khanda@gmail.com> wrote:
> What about the developing world, wouldn't NN define more problems
> towards ISP's, note increased traffic, also slow speeds being
> experienced currently would worsen . It would be a drag and a half.
>=20
> I don't follow.

<snip />

> Please elaborate on what you see as the problems raised by NN.=20

I think the issue 6Advocate refers to is the fear that in the developing =
world (where bandwidths are supposedly smaller and/or more expensive), =
one person who is downloading the entire season of Game of Thrones in =
Full HD could hog the entire bandwidth allocated to his village, and =
because of net neutrality, the ISP will not be able to throttle down =
that connection to make room for other people=92s connections.

I think this is a non-issue because:
 (a) upstream bandwidth from the ISP to the Internet is usually not the =
big issue, even in the developing world.=20
 (b) net neutrality does not necessarily mean packet-level FCFS on every =
router. Some QoS scheme imposing fairness between customers or between =
devices does not violate net neutrality.

Yoav


--Apple-Mail=_73585953-1475-44B3-90FC-0056116A3633
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Jun 5, 2014, at 10:36 AM, Evan =
Leibovitch &lt;<a href=3D"mailto:evan@telly.org">evan@telly.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On 5 June 2014 01:03, 6Advocate . <span =
dir=3D"ltr">&lt;<a href=3D"mailto:gobe.khanda@gmail.com" =
target=3D"_blank">gobe.khanda@gmail.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">

What about the developing world, wouldn't NN define more problems<br>
towards ISP's, note increased traffic, also slow speeds being<br>
experienced currently would worsen . It would be a drag and a =
half.<br></blockquote><div><br></div><div>I don't =
follow.</div></div></div></div></blockquote><div><br></div>&lt;snip =
/&gt;</div><div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">

<div>Please elaborate on what you see as the problems raised by =
NN.&nbsp;</div></div></div></div></blockquote><br></div><div>I think the =
issue 6Advocate refers to is the fear that in the developing world =
(where bandwidths are supposedly smaller and/or more expensive), one =
person who is downloading the entire season of Game of Thrones in Full =
HD could hog the entire bandwidth allocated to his village, and because =
of net neutrality, the ISP will not be able to throttle down that =
connection to make room for other people=92s =
connections.</div><div><br></div><div>I think this is a non-issue =
because:</div><div>&nbsp;(a) upstream bandwidth from the ISP to the =
Internet is usually not the big issue, even in the developing =
world.&nbsp;</div><div>&nbsp;(b) net neutrality does not necessarily =
mean packet-level FCFS on every router. Some QoS scheme imposing =
fairness between customers or between devices does not violate net =
neutrality.</div><div><br></div><div>Yoav</div><br></body></html>=

--Apple-Mail=_73585953-1475-44B3-90FC-0056116A3633--


From nobody Thu Jun  5 11:16:59 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A576B1A02BF for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 11:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 CcV1LDwJSrf1 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 11:16:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250E91A02B5 for <ietf@ietf.org>; Thu,  5 Jun 2014 11:16:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 607342002A; Thu,  5 Jun 2014 14:20:03 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 48DC963B0E; Thu,  5 Jun 2014 14:16:48 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3168263AED; Thu,  5 Jun 2014 14:16:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: [Internet Policy] root justification for net neutrality?
In-Reply-To: <E954E0D7-DEBF-411A-9D3E-4AE500737CD2@gmail.com>
References: <1401657201.842471284@f416.i.mail.ru> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <1401925963.788219402@f215.i.mail.ru> <CAAM9TmAVu+WkJnTM6fbi5MTt7B30nrmEJixF_RMKDGr8N6wxPQ@mail.gmail.com> <CAMguqh1NakxhYCQ4oQxx8tgBop0Ge1yQ+E1FJX0OqdO-et6jQA@mail.gmail.com> <E954E0D7-DEBF-411A-9D3E-4AE500737CD2@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 05 Jun 2014 14:16:48 -0400
Message-ID: <22156.1401992208@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0mXcLYNhTFdspTcOnB_65NgGoPM
Cc: isoc <isoc@isoc.org>, internetpolicy <internetpolicy@elists.isoc.org>, Evan Leibovitch <evan@telly.org>, "ietf@ietf.org" <ietf@ietf.org>, "6Advocate ." <gobe.khanda@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 18:16:57 -0000

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


Yoav Nir <ynir.ietf@gmail.com> wrote:
    > I think the issue 6Advocate refers to is the fear that in the
    > developing world (where bandwidths are supposedly smaller and/or more
    > expensive), one person who is downloading the entire season of Game of
    > Thrones in Full HD could hog the
    > entire bandwidth allocated to his village, and because of net
    > neutrality, the ISP will not be able to throttle down that connection
    > to make room for other people=E2=80=99s connections.

My opinion is that this is due to lack of end-user controlled QoS.
(end-user =3D=3D the people who pay the ISP).

If the *other* people in the village were able to make bandwidth reservatio=
ns,
then the ISP would have to take some bandwidth away from the downlowder to
satisfy things.  To do otherwise would be not-neutral.

    > I think this is a non-issue because:
    > (a) upstream bandwidth from the ISP to the Internet is usually not the
    > big issue, even in the developing world.

I think you mean, downstream bandwidth from the Internet to the ISP.
I think you used the term "upstream" to mean, the link "up" from the
end-user, vs the link from the ISP to the villager.

Bandwidth from the Internet to the ISP has regularly been a problem in every
ISP I've worked for.

    > (b) net neutrality does not necessarily mean packet-level FCFS on eve=
ry
    > router. Some QoS scheme imposing fairness between customers or between
    > devices does not violate net neutrality.

Agreed.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU5C0DYCLcPvd0N1lAQK5LggAgCrk6+1NRrXZ1N381H/VKbFYsgRNT8sC
IdgjNKYGK78snnc0Li/3JemOaDU0FtDXT73tSHgZct4ffaP7OQ8b6MDpvpxyPepp
7rfG4ns1aAYKxF50y2tUJJ143rBGtRJIpvd/5hSemP3B1agLp7JWAvUokYwVMiY7
4IUMv2Yk6AB1h6mHncSKhJ4n5In7q7pwTj9FKB9wlJ4x6de2rVu5leFS+AVQE8oF
UbZL72aHYnULPsseo5W3C3Uc8tBLsXZ538ub1oe1g4khSQEDOVt9WCi13OBO34Mm
15kRYuLWu5LI87FSK6TbbuvZy2uiylqgAKThD90J4xzoJ6Zs4NJ9hA==
=67ma
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jun  5 11:38:12 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2741A0265; Thu,  5 Jun 2014 11:38:07 -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
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 oArEd3wr5MRW; Thu,  5 Jun 2014 11:38:06 -0700 (PDT)
Received: from p3plsmtpa09-03.prod.phx3.secureserver.net (p3plsmtpa09-03.prod.phx3.secureserver.net [173.201.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 40B0C1A024D; Thu,  5 Jun 2014 11:38:06 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-03.prod.phx3.secureserver.net with  id Aidw1o00S1huGat01idx66; Thu, 05 Jun 2014 11:37:59 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-idr-bgp-enhanced-route-refresh-06
Date: Thu, 5 Jun 2014 11:38:02 -0700
Message-ID: <00e101cf80ed$4a0e9d70$de2bd850$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+A6uuiaVlJWZTWRceARV1M5CoFfw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MAaBxk0JP55cOnaqX1wM42gLa_Q
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 18:38:08 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-idr-bgp-enhanced-route-refresh-06
Reviewer: Peter Yee
Review Date: June-04-2014
IETF LC End Date: June-03-2014
IESG Telechat date: June-12-2014

This review is a couple of days late owing to my being unavailable during
most of the review period.

Summary: This draft is basically ready for publication as a Standards Track
RFC, but has some nits that should be fixed before publication. [Ready with
nits.]

No major complaints with this draft -- just a few consistency nits and a
couple of questions.

Questions:

Page 3, Section 3.2: the set of available values is enumerated.  Is the
encoding format of these values understood from other context?  Older BGP
specifications seem to give guidance such as "unsigned integer" at a
minimum.

Page 3, Section 3.2, table of values: the value is a "should" in RFC 2918.
That RFC indicated that it was to be ignored by recipients.  Now that values
will actually matter, is there any concern about senders that don't abide by
the "should" clause in RFC 2918?

Page 4, 1st full paragraph, 3rd sentence: the behavior for receipt of a BoRR
is described.  What happens if an EoRR is somehow received prior to receipt
of a BoRR?  Is it just ignored?  Or should an error notification be
returned?

Nits:

Page 3, Section 4, 4th paragraph, 2nd sentence: change "comprise of both,
the" to "comprise both the".

Page 4, 1st partial paragraph: change "ADJ-RIB-Out" to "Adj-RIB-Out" for
consistency.

Page 4, 1st full paragraph, 3rd sentence: change "anytime" to "any time".

Page 4, 3rd paragraph, 2nd sentence: use upper/lower case consistently for
the term 'EoR'.  RFC 4724 does not give specific guidance, but the spelled
out form would tend to indicate that 'EoR' is preferred.

Page 5, Section 6, table: value 255 is shown reserved.  This clashes with
the text in Section 3.2 which indicates all values outside of 0 - 2 are
reserved.

Page 5, last paragraph, 2nd sentence: change "need" to "needs".

Page 7, authors' addresses: drop "95124" from both addresses.



From nobody Thu Jun  5 12:01:15 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7041A02EA; Thu,  5 Jun 2014 12:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 KYTFEl9-7seW; Thu,  5 Jun 2014 12:01:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0FAE71A031D; Thu,  5 Jun 2014 12:00:56 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s55J0nxv017809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 5 Jun 2014 14:00:49 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66] claimed to be unnumerable.local
Message-ID: <5390BE61.4050407@nostrum.com>
Date: Thu, 05 Jun 2014 14:00:49 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-v6ops-enterprise-incremental-v6@tools.ietf.org, v6ops@ietf.org
Subject: Gen-art LC review: draft-ietf-v6ops-enterprise-incremental-ipv6-05
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/P3ZNqdJ7spQL_KRg1OYxj65GUuE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 19:01:13 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-v6ops-enterprise-incremental-ipv6-05
Reviewer: Robert Sparks
Review Date: 5 June 2014
IETF LC End Date: 9 June 2014
IESG Telechat date: not yet scheduled

Summary: This draft is basically ready for publication as an 
Informational RFC,
but has nits that should be considered before publication.

I had a mixed overall impression after my first read-through of this draft.

Overall, the list of issues to consider, and the compendium of 
references is very useful, but there are large stretches of text that 
really aren't helping the reader, and they make the good stuff harder to 
see.

I encourage the group to take one more editorial pass, focusing on 
removing as much text as possible without losing the message.

Please help the IESG and the RFC-Editor out: the shepherd's writeup 
should say something about why deviating from the style guide's 
restriction on number of authors is is appropriate for this document.

Here are specific nits to consider in document order:

The first paragraph of section 1.3 starts talking about phases as if 
they've already been described. As written, it says that beginning with 
the External Phase is recommended in RFC5211. But the words "External 
Phase" do not appear in 5211, and its not clear on a quick read exactly 
what in 5211 you were hoping to point out here.  Please introduce the 
phases before this point, and change the callout to 5211 to make it more 
clear how what 5211 is saying ties into this document.

Why is "Other Phases" capitalized in 2.1? The number of phases defined 
in this document is small - I suspect this text is older and left room 
for the group to decide to define more phases. Consider just listing 
what you ended up with explicitly.

Section 2.1 contains sentences like "The project manager will need to 
spend some time on planning." That is obvious, and you've already 
established that planning needs to happen. This paragraph (perhaps much 
of this section) would be improved by removing as much text as you can. 
It already speaks mostly in terms of the benefits of planning. Making 
that a more explicit goal in the writing structure would help identify 
what can be taken away without losing the message. Overall, trying to 
describe what good project management entails is a bit out of place. 
Perhaps you should just say "This requires good project management skills"?

In 2.2.2 you say "Applications should be made to use APIs". That seems 
an odd construct for an IETF document. Perhaps you could observe, rather 
than command, here? Would saying something like "Applications that use 
APIs to hide the specifics ... will be easier to take through the 
migration" make the point?

In 2.3, why do you need the hyperbole in "IPv6 adoption will be a 
multifacted undertaking that will touch everyone in the organization 
unlike almost any other project."? How does the "unlike almost any other 
project" help the reader?

In 2.4.1, please rephrase "pretty much like". Are there any differences 
in the use of IPSec dependent on the address family that are important 
to call out? If not, why doesn't this say "the same as in"?

Section 2.4.2: As written, this says Etc. is an attack. Please change 
the introduction to the list to say "for example" or "in particular" and 
remove the Etc. If the point was to cause the reader to think about 
attacks beyond these listed, say that explicitly.

The 6th paragraph of 2.6 states the problem is "how to get host DNS 
records updated." The text in the rest of the paragraph only addresses 
this by implication. It looks more like the general discussion of SLAAC 
vs DHCPv6 instead of straightforwardly noting that a DHCPv6 server can 
be made to update DNS records.

The reference to RFC6866 in paragraph 7 of section 2.6 is unclear - what 
was it trying to point out?  I think the last sentence was trying to say 
'static address assignment (even if achieved with DHCP) is usually used' 
where it currently says 'SLAAC is rarely used'?

Section 3: The second paragraph doesn't add anything to the document.

Section 3.1 paragraph 2: I don't understand why the paragraph ends with 
"which is an important consideration". Can you delete the phrase without 
losing the message? If not, say why an enterprise would care whether or 
not _other_ enterprises had already deployed using BGP on their own.

Section 3.1 paragraph 4 : "will prefer to use" is out of place. Perhaps 
this should be stated as "will likely get better results using"?

Section 3.1 paragraph 5: Can you add a reference to a discussion of how 
keeping the MTU congruent simplifies operations?

In section 3.2 consider using the names from 4890 in the list ('Packet 
Too Big' rather than 'Unreachable packet-to-big')

Please check whether the sentence "To be fully compliant with [RFC5095], 
all packets containing the routing extension header type 0 must be 
dropped." is perhaps too simple a description of 5095? Does context keep 
you out of the "Segments left is zero" branch of that RFCs requirement?

In section 3.4, please remove "this may seem too time-consuming and too 
risky" or restate it with details. How is this observation supposed to 
help the reader?

In section 4.1 paragraph 3 "But the major issue is probably linked to 
all threats" would read better as "One major issue is threats"

In section 5 paragraph 3, please provide a reference to where these 
significant implications are discussed, or add some discussion. 
(Otherwise, what is the reader supposed to do with this observation?)





From nobody Thu Jun  5 13:16:16 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A246B1A007B for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 13:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 1F2mM07kbcMy for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 13:16:04 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8826B1A012D for <ietf@ietf.org>; Thu,  5 Jun 2014 13:16:04 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id y13so1543236pdi.25 for <ietf@ietf.org>; Thu, 05 Jun 2014 13:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=V76lCLmnwMRpFW9yxcW7sQMlT9QF8cmUX8p62ioOPDQ=; b=qDJGq55ypUG5MHHPpzB/+bfgQjIASPjjUUWsvhl6YbLqKEl3WdeXbJy4mTc/eX+0Wm jr73KbszTkGJhH6DbDCblSUxUeiMjPlzxR7AkI5MbcNBy0Mn9c0h2f6RslH68EU9Z7WF 2rIAApb4OlbyNrpotHjIdfDcKVZOhsPKVJz/qpOWsDeVzSYgeqhVbinE14+a12YvQ4fW KDewVevoy4qFPHuJFwHdqAaeNXeZV4GpqX//yqy/iZC8+ynWNWJ4hAuqvEnE2G0jtnoz fS27+c/ew5dou8heT89Lkwpg1ZY3DMppTS4ezGFrRnCFF0ZNaEx+H/V02/ECiH8Jp3x0 q6Dw==
X-Received: by 10.68.170.66 with SMTP id ak2mr79303011pbc.5.1401999358092; Thu, 05 Jun 2014 13:15:58 -0700 (PDT)
Received: from [192.168.178.23] (13.199.69.111.dynamic.snap.net.nz. [111.69.199.13]) by mx.google.com with ESMTPSA id kj1sm26499233pbd.20.2014.06.05.13.15.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 13:15:57 -0700 (PDT)
Message-ID: <5390D005.1010005@gmail.com>
Date: Fri, 06 Jun 2014 08:16:05 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Mailing List reminders
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
In-Reply-To: <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Csv0g-VbpmsyKN4ZRMzJrhsscAY
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 20:16:12 -0000

Tom,

On 05/06/2014 20:51, t.p. wrote:
> I used to get a reminder once a month of the mailing lists to which I am
> subscribed, such as this one, but, around the time of IETF89, this
> stopped working.  I see that the option on every one of the lists to
> which I am subscribed has been reset to not send a reminder, not
> something that I would intentionally ever do
> 
> Is this a change of policy, an announcement somewhere that I missed?

You missed a discussion a few months ago, but the actual change took
place two months ago and afaik was not announced.

If you like your reminders, you need to switch them on again in
the mailman options for any of your subscriptions. There's a button for
making the setting global. Ditto for IRTF lists.

> I note that the IETF web site page on Email Lists still talks of monthly
> reminders without even mentioning that they are optional, which suggests
> to me that it is not the policy that has changed.

You could point out that documentation error to <ietf-action@ietf.org>

   Brian


From nobody Thu Jun  5 14:01:30 2014
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6951A0126 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 14:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 5A88knHEcKen for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 14:01:27 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE921A018E for <ietf@ietf.org>; Thu,  5 Jun 2014 14:01:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 2F2341E12A7; Thu,  5 Jun 2014 13:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id otoUtF01p8o4; Thu,  5 Jun 2014 13:59:46 -0700 (PDT)
Received: from [64.170.98.186] (unknown [64.170.98.186]) by c8a.amsl.com (Postfix) with ESMTPSA id 141521DF11E; Thu,  5 Jun 2014 13:59:46 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Mailing List reminders
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <5390D005.1010005@gmail.com>
Date: Thu, 5 Jun 2014 14:01:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4C4B63E-C787-4D25-BC6F-3A6AAD7CDA55@amsl.com>
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net> <5390D005.1010005@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0rl1NNtv7_y64e3GvnrhGg0U9Hc
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 21:01:28 -0000

Brian, Tom,

On Jun 5, 2014, at 1:16 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

>=20
>> I note that the IETF web site page on Email Lists still talks of =
monthly
>> reminders without even mentioning that they are optional, which =
suggests
>> to me that it is not the policy that has changed.
>=20
> You could point out that documentation error to <ietf-action@ietf.org>
>=20
>   Brian
>=20

My apologies for coming in late to this conversation, and for not =
noticing that the website text still needed to be updated. We will =
update it now.

Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From nobody Thu Jun  5 17:03:53 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 396E31A035F; Thu,  5 Jun 2014 17:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 0k0-8m-FRSKr; Thu,  5 Jun 2014 17:03:46 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id E252C1A035B; Thu,  5 Jun 2014 17:03:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 223AE1E12A7; Thu,  5 Jun 2014 17:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9_ln86muZRk; Thu,  5 Jun 2014 17:02:06 -0700 (PDT)
Received: from [10.30.0.121] (unknown [83.150.71.93]) by c8a.amsl.com (Postfix) with ESMTPSA id F144F1DF121; Thu,  5 Jun 2014 17:02:04 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: IETF Chair <chair@ietf.org>
Date: Fri, 6 Jun 2014 03:03:36 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org>
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Z9RLiMOsYhi_Mb642cXJMlRAtVU
Cc: internetgovtech@iab.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: The IESG <iesg@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 00:03:48 -0000

As you know, the NTIA announced on March 14th, 2014 that a process has =
been started to relinquish the IANA oversight role of the NTIA to the =
multistakeholder Internet community. ICANN was given a facilitator role =
to set up the process, and there has been a proposal and commentary on =
that proposal, including well-received feedback from the IAB.

Now we are at a point where the final details are expected to become =
clear soon. A big part of the overall plan depends on the processes in =
the relevant communities, such as those of the IETF and RIRs. But the =
overall process also includes a coordination group, on which the IETF =
gets 2 seats and the IAB 2 seats. Other seats will be filled by parts of =
the naming and numbering communities. ISOC will also have two seats.

The coordination group is likely to be ultimately responsible for =
delivering a combined transition proposal to NTIA and for ensuring that =
the proposal meets the criteria NTIA previously outlined. Participation =
in the coordination group is likely to entail a significant amount of =
time and travel, although the exact details of how the group will work =
and what its responsibilities will be is not yet available.

The IAB will select two people from the IAB voting members and the IAB =
IANA strategy program participants. I'm sending this email because the =
IESG would like to consult with the community before filling the two =
IETF positions. Given that there is an upcoming ICANN meeting in London =
(starting on June 22nd) and that there might be opportunities for =
discussion during that meeting, timely selection would be useful.

We realize that doing this on a compressed timeline and without complete =
details is not ideal. NTIA has requested that the transition proposal be =
delivered by September 2015, which we view as a relatively short time =
period for developing global community consensus on this topic. Thus, we =
feel that it is imperative for the coordination group to be constituted =
and for it to begin its work as soon as possible, just like how the =
relevant communities should progress their parts of the work.

We would like to fill the two IETF seats with IETF community members who =
have had significant interaction and experience with IANA and its =
oversight. Some IESG, IAB, and IAB IANA strategy program members have =
experience on this matter, and we are already aware of several such =
people who are willing to serve in this role. However, before appointing =
people to these seats, we wanted to find out if there are members of the =
broader community who would be willing to serve. If you would like to =
volunteer, please send a short statement of interest (200 words or less) =
to the IESG <iesg@ietf.org> by 23:59 UTC on June 16, 2014.

Jari Arkko on behalf of the IESG


From nobody Thu Jun  5 21:53:17 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D6C1A01C5 for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 we3nDUUcUK6t for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 21:53:14 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 601CC1A0158 for <ietf@ietf.org>; Thu,  5 Jun 2014 21:53:13 -0700 (PDT)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 6 Jun 2014 00:53:06 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 6 Jun 2014 00:53:05 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 225816E801C for <ietf@ietf.org>; Fri,  6 Jun 2014 00:52:56 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp22035.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s564r40X8782082 for <ietf@ietf.org>; Fri, 6 Jun 2014 04:53:04 GMT
Received: from d01av02.pok.ibm.com (localhost [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s564r4mF026828 for <ietf@ietf.org>; Fri, 6 Jun 2014 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s564r34S026813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 6 Jun 2014 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s564r3pA019449 for <ietf@ietf.org>; Fri, 6 Jun 2014 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s564r29v019394 for ietf@ietf.org; Fri, 6 Jun 2014 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201406060453.s564r29v019394@rotala.raleigh.ibm.com>
Date: Fri, 06 Jun 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14060604-0320-0000-0000-000003793114
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aodjIsN_R8C9k2aSmQRFpmMTqWI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 04:53:16 -0000

Total of 101 messages in the last 7 days.
 
script run at: Fri Jun  6 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.93% |    7 | 17.79% |   242531 | marc.lasserre@alcatel-lucent.com
  7.92% |    8 |  4.04% |    55089 | sm+ietf@elandsys.com
  1.98% |    2 |  7.48% |   102005 | linda.dunbar@huawei.com
  1.98% |    2 |  7.44% |   101503 | david.black@emc.com
  4.95% |    5 |  3.27% |    44555 | drc@virtualized.org
  0.99% |    1 |  6.02% |    82078 | lucy.yong@huawei.com
  3.96% |    4 |  2.81% |    38313 | carlosm3011@gmail.com
  3.96% |    4 |  2.78% |    37929 | evan@telly.org
  2.97% |    3 |  1.99% |    27089 | info@articlecontentprovider.com
  2.97% |    3 |  1.95% |    26538 | rwfranks@acm.org
  2.97% |    3 |  1.76% |    24066 | narten@us.ibm.com
  2.97% |    3 |  1.74% |    23724 | bmanning@isi.edu
  1.98% |    2 |  2.70% |    36827 | ron.even.tlv@gmail.com
  1.98% |    2 |  2.60% |    35451 | serrhini@mail.ru
  2.97% |    3 |  1.58% |    21500 | paf@frobbit.se
  1.98% |    2 |  2.04% |    27834 | akatlas@gmail.com
  1.98% |    2 |  1.49% |    20310 | nd@syndicat.com
  1.98% |    2 |  1.40% |    19108 | uri@mit.edu
  1.98% |    2 |  1.36% |    18527 | mcr+ietf@sandelman.ca
  1.98% |    2 |  1.29% |    17585 | jabley@hopcount.ca
  1.98% |    2 |  1.27% |    17268 | jsalowey@cisco.com
  0.99% |    1 |  2.23% |    30347 | mariainesrobles@googlemail.com
  1.98% |    2 |  0.99% |    13540 | dhc@dcrocker.net
  1.98% |    2 |  0.96% |    13123 | chair@ietf.org
  1.98% |    2 |  0.96% |    13057 | housley@vigilsec.com
  1.98% |    2 |  0.89% |    12110 | cos@aaaaa.org
  1.98% |    2 |  0.89% |    12106 | barryleiba@computer.org
  0.99% |    1 |  1.76% |    23976 | rstruik.ext@gmail.com
  0.99% |    1 |  1.75% |    23894 | kelvin@skysys.co.ke
  0.99% |    1 |  1.60% |    21872 | amelnaud@gmail.com
  0.99% |    1 |  0.92% |    12539 | dbourdoukis@hol.net
  0.99% |    1 |  0.81% |    10997 | mail@christopherwilkinson.eu
  0.99% |    1 |  0.79% |    10724 | rjsparks@nostrum.com
  0.99% |    1 |  0.75% |    10226 | ynir.ietf@gmail.com
  0.99% |    1 |  0.70% |     9544 | phill@hallambaker.com
  0.99% |    1 |  0.68% |     9231 | nashton@consensus.pro
  0.99% |    1 |  0.59% |     8091 | gobe.khanda@gmail.com
  0.99% |    1 |  0.58% |     7946 | ramk@brocade.com
  0.99% |    1 |  0.54% |     7321 | brian.e.carpenter@gmail.com
  0.99% |    1 |  0.53% |     7210 | paul.hoffman@vpnc.org
  0.99% |    1 |  0.53% |     7178 | dcrocker@gmail.com
  0.99% |    1 |  0.52% |     7126 | daedulus@btconnect.com
  0.99% |    1 |  0.52% |     7026 | lars@netapp.com
  0.99% |    1 |  0.51% |     7003 | pouzin@well.com
  0.99% |    1 |  0.51% |     7003 | peter@akayla.com
  0.99% |    1 |  0.50% |     6853 | mfidelman@meetinghouse.net
  0.99% |    1 |  0.49% |     6624 | vesely@tana.it
  0.99% |    1 |  0.48% |     6607 | stephen@tolerantnetworks.com
  0.99% |    1 |  0.48% |     6567 | touch@isi.edu
  0.99% |    1 |  0.45% |     6180 | amorris@amsl.com
  0.99% |    1 |  0.44% |     6021 | dwm@xpasc.com
  0.99% |    1 |  0.44% |     5940 | paul@nohats.ca
  0.99% |    1 |  0.43% |     5805 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |  101 |100.00% |  1363617 | Total


From nobody Thu Jun  5 23:46:23 2014
Return-Path: <marcie@usermail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D214A1A02FC for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 23:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SPF_NEUTRAL=0.779] autolearn=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 YFa-m5tgxuri for <ietf@ietfa.amsl.com>; Thu,  5 Jun 2014 23:46:20 -0700 (PDT)
Received: from mailin01.mxof.net (mailin01.mxof.com [198.24.62.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB8341A02F5 for <ietf@ietf.org>; Thu,  5 Jun 2014 23:46:20 -0700 (PDT)
Received: from mta00.prxy.net (mta.mxof.net [10.1.0.193]) by mailin01.mxof.net (8.13.8/8.13.8) with ESMTP id s566kC28028899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 5 Jun 2014 23:46:12 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 mailin01.mxof.net s566kC28028899
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta00.prxy.net (Postfix) with ESMTP id 137F91B8EE9 for <ietf@ietf.org>; Thu,  5 Jun 2014 23:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mta00.prxy.net
Received: from mta00.prxy.net ([127.0.0.1]) by localhost (mta00.prxy.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BadV6brpHtaZ for <ietf@ietf.org>; Thu,  5 Jun 2014 23:46:14 -0700 (PDT)
Received: from [192.168.1.100] (c-24-4-61-239.hsd1.ca.comcast.net [24.4.61.239]) by mta00.prxy.net (Postfix) with ESMTPSA id DB74D1B8EFC for <ietf@ietf.org>; Thu,  5 Jun 2014 23:46:13 -0700 (PDT)
Message-ID: <539163BD.4090601@usermail.com>
Date: Thu, 05 Jun 2014 23:46:21 -0700
From: marcie@usermail.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Google to Host IETF 92 in Dallas!
References: <20140605135221.27106.15826.idtracker@ietfa.amsl.com>
In-Reply-To: <20140605135221.27106.15826.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN)
X-CanIt-Geo: No geolocation information available for 10.1.0.193
X-CanItPRO-Stream: outgoing:default (inherits from base:default)
X-Canit-Stats-ID: 02MaSKcQL - 6ee0978a3d62 - 20140605
X-Antispam-Training-Forget: https://spamblock.prxy.com/b.php?i=02MaSKcQL&m=6ee0978a3d62&t=20140605&c=f
X-Antispam-Training-Nonspam: https://spamblock.prxy.com/b.php?i=02MaSKcQL&m=6ee0978a3d62&t=20140605&c=n
X-Antispam-Training-Spam: https://spamblock.prxy.com/b.php?i=02MaSKcQL&m=6ee0978a3d62&t=20140605&c=s
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.1.0.129
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mTcTBaROOAhamdhF3iSYGcidseE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 06:46:22 -0000

Classic!


On 6/5/2014 6:52 AM, IETF Administrative Director wrote:
> The IAOC is pleased to announce that Google will be the Host for IETF 92 in Dallas.
> The meeting will be at the Fairmont Dallas March 22 - 27, 2015.  Google is also
> sponsoring the Welcome Reception.
>
> Google first hosted the IETF when it hosted IETF 73 in Minneapolis, and has since
> hosted the IETF at IETF 84 in Vancouver.
>
> Thanks Google.  We cannot support the RFC Editor, Secretariat and the IETF meetings
> without the commitment and contribution of our many Hosts and Sponsors.
>
> Many sponsorship opportunities are still available:
> <http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf>.
> If interested contact Andrew Dvorshak, dvorshak@isoc.org.
>
> Just 45 days until IETF 90 in Toronto!
> Register at: <http://www.ietf.org/meetings/90/>
>
> See you in Toronto!
>
> Ray
> IAD
>
> 2014 Meeting Venues
>
> IETF 89  London  Hilton Metropole  March 2 - 7                 Host:  ICANN
> IETF 90  Toronto  Fairmont Royal York Hotel  July 20 - 25  Host:  Ericsson
> IETF 91  Honolulu  Hilton Hawaiian Village  Nov 9 - 14       Host: Cisco
>
> 2015
>
> IETF 92  Dallas  March 22 - 27     Host:  GOOGLE
> IETF 93  Prague	  July 19 - 24       Host:  ?
> IETF 94  Yokohama  Nov 1 - 6     Host:  WIDE
>
> 2016
>
> IETF 95  Latin America  Host:  ?
> IETF 96  Berlin		    Host:  ?
> IETF 97  Asia		    Host:  ?
>


From nobody Fri Jun  6 07:01:43 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5521A0492 for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 07:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=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 aiimnT58gnSF for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 07:01:40 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0077.outbound.protection.outlook.com [213.199.154.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81BAB1A0092 for <ietf@ietf.org>; Fri,  6 Jun 2014 07:01:39 -0700 (PDT)
Received: from DB3PRD0710HT002.eurprd07.prod.outlook.com (10.255.75.37) by AMSPR07MB001.eurprd07.prod.outlook.com (10.242.81.14) with Microsoft SMTP Server (TLS) id 15.0.954.9; Fri, 6 Jun 2014 14:01:30 +0000
Received: from pc6 (31.51.16.131) by pod51017.outlook.com (10.255.75.37) with Microsoft SMTP Server (TLS) id 14.16.459.0; Fri, 6 Jun 2014 14:01:30 +0000
Message-ID: <021001cf818f$66e93660$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Alessandro Vesely <vesely@tana.it>, <ietf@ietf.org>
References: <201403072039.s27KdawQ5908202@shell01.TheWorld.com> <tagkh9hgilbc76ohdla4q40hhh3sheuldh@hive.bjoern.hoehrmann.de> <531B2CC8.1000201@levkowetz.com> <531B3232.8020007@gmail.com> <jbdmh95s9meah15vdp97jef03td4s0qcbp@hive.bjoern.hoehrmann.de> <017101cf809b$4dd00b80$4001a8c0@gateway.2wire.net> <53905188.7000006@tana.it>
Subject: Re: Mailing List reminders
Date: Fri, 6 Jun 2014 11:24:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [31.51.16.131]
X-Microsoft-Antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID:
X-Forefront-PRVS: 023495660C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(24454002)(12213003)(13464003)(377454003)(51704005)(189002)(199002)(64706001)(20776003)(46102001)(47776003)(81542001)(99396002)(61296002)(62966002)(101416001)(50226001)(44736004)(102836001)(93886002)(80022001)(4396001)(74662001)(66066001)(31966008)(74502001)(87286001)(87936001)(21056001)(83072002)(85852003)(104166001)(79102001)(81686999)(77156001)(76176999)(19580405001)(83322001)(19580395003)(50986999)(81816999)(44716002)(62236002)(92566001)(81342001)(23676002)(76482001)(77982001)(92726001)(14496001)(50466002)(89996001)(93916002)(86362001)(88136002)(33646001)(74416001)(7726001); DIR:OUT; SFP:; SCL:1; SRVR:AMSPR07MB001; H:DB3PRD0710HT002.eurprd07.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords;  MX:1; A:0; LANG:en; 
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wfhcpvnCcBQrRgc9yGeYgbJZOps
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 14:01:41 -0000

----- Original Message -----
From: "Alessandro Vesely" <vesely@tana.it>
To: <ietf@ietf.org>
Sent: Thursday, June 05, 2014 12:16 PM

> On Thu 05/Jun/2014 10:51:05 +0200 T.p. wrote:
> > I used to get a reminder once a month of the mailing lists to which
I am
> > subscribed, such as this one, but, around the time of IETF89, this
> > stopped working.  I see that the option on every one of the lists to
> > which I am subscribed has been reset to not send a reminder, not
> > something that I would intentionally ever do
>
> I'd be curious to know some more on the usefulness of reminders.

They are useful because e-mail is overridingly spam or something else
evil.
Mailing lists have no reliable way of authenticating the From: address.
Therefore mailing lists implement a system to suspend a subscription
when enough inappropriate mail has come with a given From: address.
This happens to me with IETF WG lists (such as, in the past, v6ops).
At the same time, some lists are so quiet, especially now in the
inter-IETF meeting stadia that it is hard to tell whether or not one is
still subscribed. (and I note a number of 'Test' posts to lists which
suggests others have similar concerns).
The monthly reminder enables me to check that I am still subscribed.
Logical.
Tom Petch

> They're what I call a time-distributed database.  When subscribers
> need to query the status of their subscription, they simply perform a
> time seek --by waiting at most one month-- and voilÃ !
>
> Since we've been discussing how DMARC is going to affect the fate of
> mailing lists, recently on this list, I wonder why 21st century
> technology doesn't offer anything better.  The outcome of that
> discussion was that mailbox providers don't know the status of their
> clients' subscriptions too, hence they cannot deploy any cooperative
> solution such as whitelisting, weak signatures, or 3rd party auths.
>
> Ale
> --
> "Never expect the people who caused a problem to solve it."
>                                          - Albert Einstein
>
>
>
>


From nobody Fri Jun  6 10:18:45 2014
Return-Path: <richard@shockey.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E5B1A01BD for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 10:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level: 
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 w0oGiaBMJ7Ep for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 10:18:42 -0700 (PDT)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) by ietfa.amsl.com (Postfix) with SMTP id A9E6A1A016B for <ietf@ietf.org>; Fri,  6 Jun 2014 10:18:42 -0700 (PDT)
Received: (qmail 30468 invoked by uid 0); 6 Jun 2014 17:18:33 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy1.mail.unifiedlayer.com with SMTP; 6 Jun 2014 17:18:33 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by cmgw3 with  id B5JQ1o01D1MNPNq015JTnU; Fri, 06 Jun 2014 11:18:33 -0600
X-Authority-Analysis: v=2.1 cv=XPOjF2RE c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=77ayNAtL17UA:10 a=zsg0ix40YlEA:10 a=8WrITzYgnNwA:10 a=0w_QV-lY4gkA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=doUQZJtgAAAA:8 a=48vgC7mUAAAA:8 a=qerv6Y54AAAA:8 a=I57iI6ZGAAAA:8 a=b7Hhvwm9AAAA:8 a=DtmeJ96pONtVOUe10ukA:9 a=_Y5K9KfmOoI5aVmM:21 a=BR5ogcb8YBaJXrIh:21 a=QEXdDO2ut3YA:10 a=lZB815dzVvQA:10 a=nvUxkuOEDpUA:10 a=u6sSiepMmQ0A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=EmKBYDLffATIvZhMjnAA:9 a=ztYBZwwoWLhQ4doO:21 a=s6zqtZZdFM9DFQhC:21 a=lOvM8D_cpyKsTOI0:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=tXsnliwV7b4A:10 a=-HDD77JRrZoA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us;  s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=l1g7VpXx2VGF3jKxOF5kpz2Rfe/sJr6cWPUjgLH2UNo=;  b=cLbsxKDcZ/eo1VAJjmH7s2XcI4B3knnJjfkAOgmXdEdyoGWGIrcY99k/GaaFPNetPRSG6np2nZlT8HZeLzEe/58tWqNg/sfwlQ5T2Ug2DrEta1kFvRL/+CuRz9cVlFkY;
Received: from [96.255.155.157] (port=59365 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.82) (envelope-from <richard@shockey.us>) id 1WsxmX-0004gM-VE; Fri, 06 Jun 2014 11:18:24 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Clyde C McElroy'" <info@articlecontentprovider.com>, "'Ofer Inbar'" <cos@aaaaa.org>
References: <1401657201.842471284@f416.i.mail.ru> <CAGDMR_eQHegE1BxGD698rC_oHBEHnT722a8+VMhcArmk9Zbn+w@mail.gmail.com> <3959F294-9EA2-43D1-9321-A29A99490649@skysys.co.ke> <CAE0gvYAwWAshVgubnVYgPF4UsFrDDUXM83Sf0pFuKYyhuFa6vQ@mail.gmail.com> <CAMguqh0KN9VhUiSVEdWPeJ+ZdsVRqj3hM9o2CV5=pirDLvOgbg@mail.gmail.com> <CAMPgnKF+doB28iDV_3qf=31sk6dUh=PnpMwR0fakC-POKz0igQ@mail.gmail.com> <20140604161317.GN371@mip.aaaaa.org> <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
In-Reply-To: <CAMPgnKF3ZBkeveKbvY9A8Lw20fg5DhNUEKvua9gKiph7Dy25Xg@mail.gmail.com>
Subject: RE: [Internet Policy] Fwd: Re: root justification for net neutrality?
Date: Fri, 6 Jun 2014 13:18:16 -0400
Message-ID: <00a901cf81ab$50b05d80$f2111880$@shockey.us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AA_01CF8189.CA74D230"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQGpyXrEag1RVNIxBJk4zPStB4stjQJlmf2WAY1tUwcB78p0hwG/YNVNASPL8fIBpwMwWgHnNgQZm00hDgA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.255.155.157 authed with richard@shockey.us}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OU-a2MloJMKzesUohbHTjabIPMo
Cc: internetpolicy@elists.isoc.org, 'Evan Leibovitch' <evan@telly.org>, ietf@ietf.org, =?UTF-8?B?J09sw4PCqXZpw4PCqSBLb3VhbWkn?= <olivierkouami@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 17:18:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00AA_01CF8189.CA74D230
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You go to ECFS to view all the filings

=20

http://apps.fcc.gov/ecfs/comment_search/input?z=3Drcgsw

=20

In the proceeding number you enter the docket which in this case in =
14-28

=20

Unfortunately the docket is so crowded with email messages you =
can=E2=80=99t see the more detailed comments.=20

=20

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Clyde C McElroy
Sent: Wednesday, June 04, 2014 12:21 PM
To: Ofer Inbar
Cc: internetpolicy@elists.isoc.org; Evan Leibovitch; ietf@ietf.org; =
Ol=C3=83=C2=A9vi=C3=83=C2=A9 Kouami
Subject: Re: [Internet Policy] Fwd: Re: root justification for net =
neutrality?

=20

Yeah, it wasn't working when I went there yesterday. There wasn't even a =
list of filings. Today, it just takes 10 minutes to load the comments =
page.

=20

On Wed, Jun 4, 2014 at 11:13 AM, Ofer Inbar <cos@aaaaa.org =
<mailto:cos@aaaaa.org> > wrote:

Clyde C McElroy <info@articlecontentprovider.com =
<mailto:info@articlecontentprovider.com> > wrote:
> Thanks for that video. That's a great way to get people to understand =
it,
> but the FCC link provided doesn't exactly make it easy to comment. =
Just an
> email address. Not so public. Anyone know a link where the comments =
can
> actually be viewed by the public?

Are you referring to http://fcc.gov/comments ?
That's not just an email address.

"Net Neutrality" is there at the top as:
14-28            Protecting and Promoting the Open Internet

You click on the "14-28" link to make a comment.
You click on the large number on the right to search already submitted
comments.  The large number is how many comments have already been
submitted for this issue.
  -- Cos

=20


------=_NextPart_000_00AA_01CF8189.CA74D230
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You go to ECFS to view all the filings<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><a =
href=3D"http://apps.fcc.gov/ecfs/comment_search/input?z=3Drcgsw">http://a=
pps.fcc.gov/ecfs/comment_search/input?z=3Drcgsw</a><o:p></o:p></span></p>=
<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>In the proceeding number you enter the docket which in this case in =
14-28<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Unfortunately the docket is so crowded with email messages you =
can=E2=80=99t see the more detailed comments. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span=
></b><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> ietf =
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Clyde C =
McElroy<br><b>Sent:</b> Wednesday, June 04, 2014 12:21 PM<br><b>To:</b> =
Ofer Inbar<br><b>Cc:</b> internetpolicy@elists.isoc.org; Evan =
Leibovitch; ietf@ietf.org; Ol=C3=83=C2=A9vi=C3=83=C2=A9 =
Kouami<br><b>Subject:</b> Re: [Internet Policy] Fwd: Re: root =
justification for net neutrality?<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Yeah, =
it wasn't working when I went there yesterday. There wasn't even a list =
of filings. Today, it just takes 10 minutes to load the comments =
page.<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Wed, Jun 4, 2014 at 11:13 AM, Ofer Inbar &lt;<a =
href=3D"mailto:cos@aaaaa.org" target=3D"_blank">cos@aaaaa.org</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Clyde C McElroy &lt;<a =
href=3D"mailto:info@articlecontentprovider.com">info@articlecontentprovid=
er.com</a>&gt; wrote:<br>&gt; Thanks for that video. That's a great way =
to get people to understand it,<br>&gt; but the FCC link provided =
doesn't exactly make it easy to comment. Just an<br>&gt; email address. =
Not so public. Anyone know a link where the comments can<br>&gt; =
actually be viewed by the public?<o:p></o:p></p></div><p =
class=3DMsoNormal>Are you referring to <a =
href=3D"http://fcc.gov/comments" =
target=3D"_blank">http://fcc.gov/comments</a> ?<br>That's not just an =
email address.<br><br>&quot;Net Neutrality&quot; is there at the top =
as:<br>14-28 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Protecting and =
Promoting the Open Internet<br><br>You click on the &quot;14-28&quot; =
link to make a comment.<br>You click on the large number on the right to =
search already submitted<br>comments. &nbsp;The large number is how many =
comments have already been<br>submitted for this issue.<br>&nbsp; -- =
Cos<o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00AA_01CF8189.CA74D230--


From nobody Fri Jun  6 10:59:00 2014
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3C01A01F7; Fri,  6 Jun 2014 10:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 SN6FV0xwKWvb; Fri,  6 Jun 2014 10:58:55 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B03C1A01E0; Fri,  6 Jun 2014 10:58:55 -0700 (PDT)
Received: from [10.0.0.103] ([12.193.118.186]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id s56HvjHA001577 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 6 Jun 2014 10:57:57 -0700 (PDT)
Subject: Re: Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org>
Date: Fri, 6 Jun 2014 09:28:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7474D36-5A5A-4D95-8719-D8E84033FD86@isi.edu>
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org>
To: ietf@ietf.org, The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1878.2)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OgnT2dmdjflOokcIF5SbWDMXj8E
Cc: Bill Manning <bmanning@vacation.karoshi.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 17:58:57 -0000

I would like to submit my name for a seat at this table.  I=92ve worked =
with the IETF in various forms over the past 25 years, was involved in =
the transition from the IANA @ USC under the NSF to ICANN=20
under NTIA/DoC.  As a root server operator, I=92ve had regular =
interaction with both IANA and NTIA, as their processes/policies have =
evolved, in most respects ensuring that the end product, the root
zone was always delivered and available to the community at large. =20

/bill
Neca eos omnes.  Deus suos agnoscet.

On 5June2014Thursday, at 17:03, IETF Chair <chair@ietf.org> wrote:

> As you know, the NTIA announced on March 14th, 2014 that a process has =
been started to relinquish the IANA oversight role of the NTIA to the =
multistakeholder Internet community. ICANN was given a facilitator role =
to set up the process, and there has been a proposal and commentary on =
that proposal, including well-received feedback from the IAB.
>=20
> Now we are at a point where the final details are expected to become =
clear soon. A big part of the overall plan depends on the processes in =
the relevant communities, such as those of the IETF and RIRs. But the =
overall process also includes a coordination group, on which the IETF =
gets 2 seats and the IAB 2 seats. Other seats will be filled by parts of =
the naming and numbering communities. ISOC will also have two seats.
>=20
> The coordination group is likely to be ultimately responsible for =
delivering a combined transition proposal to NTIA and for ensuring that =
the proposal meets the criteria NTIA previously outlined. Participation =
in the coordination group is likely to entail a significant amount of =
time and travel, although the exact details of how the group will work =
and what its responsibilities will be is not yet available.
>=20
> The IAB will select two people from the IAB voting members and the IAB =
IANA strategy program participants. I'm sending this email because the =
IESG would like to consult with the community before filling the two =
IETF positions. Given that there is an upcoming ICANN meeting in London =
(starting on June 22nd) and that there might be opportunities for =
discussion during that meeting, timely selection would be useful.
>=20
> We realize that doing this on a compressed timeline and without =
complete details is not ideal. NTIA has requested that the transition =
proposal be delivered by September 2015, which we view as a relatively =
short time period for developing global community consensus on this =
topic. Thus, we feel that it is imperative for the coordination group to =
be constituted and for it to begin its work as soon as possible, just =
like how the relevant communities should progress their parts of the =
work.
>=20
> We would like to fill the two IETF seats with IETF community members =
who have had significant interaction and experience with IANA and its =
oversight. Some IESG, IAB, and IAB IANA strategy program members have =
experience on this matter, and we are already aware of several such =
people who are willing to serve in this role. However, before appointing =
people to these seats, we wanted to find out if there are members of the =
broader community who would be willing to serve. If you would like to =
volunteer, please send a short statement of interest (200 words or less) =
to the IESG <iesg@ietf.org> by 23:59 UTC on June 16, 2014.
>=20
> Jari Arkko on behalf of the IESG
>=20


From nobody Fri Jun  6 12:54:51 2014
Return-Path: <keyupate@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 893C01A00FC; Fri,  6 Jun 2014 12:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 fmr65Q05R04P; Fri,  6 Jun 2014 12:54:49 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05E4F1A024D; Fri,  6 Jun 2014 12:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2777; q=dns/txt; s=iport; t=1402084482; x=1403294082; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Hnpo9X3GMWUatXOLextq917u+1nqumJ7C2hu7B7OCj8=; b=ljFA/QBn20K4WpgnhhkBumDvJmyxGdEk87/1OA9wd/BO17eTL3o/GCQD HRSQw5XZ46oaCmqQSv/1FxPdh2KBNIh3gSg4/Bl0XjKwqK9fTGY4CfKj2 r3y9MO+D8WZvmcWx9poeAOKLY2FY0LtAg8M3ni/OHCVgxYxn4LFDTpF8I M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvZbACEcklOtJA2G/2dsb2JhbABZgw1SWapxBm+YIQGBBxZ1hAo6PxIBCBQiQiUCBAENBYhCDc1OF4VdhxCBfAeEQQEDmh2BQpICgzxsgUM
X-IronPort-AV: E=Sophos;i="4.98,991,1392163200"; d="scan'208";a="331269309"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-4.cisco.com with ESMTP; 06 Jun 2014 19:54:42 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s56JsfrH006384 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Jun 2014 19:54:41 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.72]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Fri, 6 Jun 2014 14:54:41 -0500
From: "Keyur Patel (keyupate)" <keyupate@cisco.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org" <draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org>
Subject: Re: Gen-ART LC review of draft-ietf-idr-bgp-enhanced-route-refresh-06
Thread-Topic: Gen-ART LC review of draft-ietf-idr-bgp-enhanced-route-refresh-06
Thread-Index: AQHPgcEn6/H8S8nfwU6yLqGHmoWlNw==
Date: Fri, 6 Jun 2014 19:54:40 +0000
Message-ID: <CFB76C32.752A3%keyupate@cisco.com>
In-Reply-To: <00e101cf80ed$4a0e9d70$de2bd850$@akayla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [128.107.163.125]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FE30BCA54FA66343824D5BBDFD47458B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F787_BdRNHGQLD-nsZoY0lbbqKw
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 19:54:50 -0000

Hi Peter,

Thank you for the draft review. I have fixed the nits in the draft.

More comments inlined. #Keyur

On 6/5/14 11:38 AM, "Peter Yee" <peter@akayla.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
>Please resolve these comments along with any other Last Call comments you
>may receive.
>
>Document: draft-ietf-idr-bgp-enhanced-route-refresh-06
>Reviewer: Peter Yee
>Review Date: June-04-2014
>IETF LC End Date: June-03-2014
>IESG Telechat date: June-12-2014
>
>This review is a couple of days late owing to my being unavailable during
>most of the review period.
>
>Summary: This draft is basically ready for publication as a Standards
>Track
>RFC, but has some nits that should be fixed before publication. [Ready
>with
>nits.]
>
>No major complaints with this draft -- just a few consistency nits and a
>couple of questions.
>
>Questions:
>
>Page 3, Section 3.2: the set of available values is enumerated.  Is the
>encoding format of these values understood from other context?  Older BGP
>specifications seem to give guidance such as "unsigned integer" at a
>minimum.

#Keyur: Yes.

>
>Page 3, Section 3.2, table of values: the value is a "should" in RFC 2918.
>That RFC indicated that it was to be ignored by recipients.  Now that
>values
>will actually matter, is there any concern about senders that don't abide
>by
>the "should" clause in RFC 2918?

#Keyur: Yes. This functionality is controlled using BGP capabilities.

>
>Page 4, 1st full paragraph, 3rd sentence: the behavior for receipt of a
>BoRR
>is described.  What happens if an EoRR is somehow received prior to
>receipt
>of a BoRR?  Is it just ignored?  Or should an error notification be
>returned?

#Keyur: It would be a no-op operation. 07 version of draft covers it.

Best Regards,
Keyur

>
>Nits:
>
>Page 3, Section 4, 4th paragraph, 2nd sentence: change "comprise of both,
>the" to "comprise both the".
>
>Page 4, 1st partial paragraph: change "ADJ-RIB-Out" to "Adj-RIB-Out" for
>consistency.
>
>Page 4, 1st full paragraph, 3rd sentence: change "anytime" to "any time".
>
>Page 4, 3rd paragraph, 2nd sentence: use upper/lower case consistently for
>the term 'EoR'.  RFC 4724 does not give specific guidance, but the spelled
>out form would tend to indicate that 'EoR' is preferred.
>
>Page 5, Section 6, table: value 255 is shown reserved.  This clashes with
>the text in Section 3.2 which indicates all values outside of 0 - 2 are
>reserved.
>
>Page 5, last paragraph, 2nd sentence: change "need" to "needs".
>
>Page 7, authors' addresses: drop "95124" from both addresses.
>
>


From nobody Fri Jun  6 15:33:13 2014
Return-Path: <john.doyle@fmr.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8821A02AA for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 15:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.402
X-Spam-Level: 
X-Spam-Status: No, score=-6.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 M-S6DMD_A86B for <ietf@ietfa.amsl.com>; Fri,  6 Jun 2014 15:33:09 -0700 (PDT)
Received: from msginmsm10vapp.fmr.com (ltm-fwus409m-410m.fidelity.com [155.199.16.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C3A51A0273 for <ietf@ietf.org>; Fri,  6 Jun 2014 15:33:08 -0700 (PDT)
Received: from msgrtphc05win.DMN1.FMR.COM (MSGRTPHC05WIN.dmn1.fmr.com [10.95.11.185]) by msginmsm10vapp.fmr.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.1) with ESMTP id s56MWtAt017381 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Fri, 6 Jun 2014 22:32:56 GMT
X-DKIM: OpenDKIM Filter v2.1.3 msginmsm10vapp.fmr.com s56MWtAt017381
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fmr.com; s=2012-05-26; t=1402093977; bh=90Bna/5gkJ7ZodZjCdwkaX4CUuSo477C0ikicN3rFUw=; h=From:To:CC:Date:Subject:Message-ID:In-Reply-To:Content-Type: Content-Transfer-Encoding:MIME-Version; b=YLxc/QSMlPkw0z99s7PqUHYLApCjhUrNFEXw2erpe80gc5zwS0XJlt/ZCmB+NmnR7 1dZ0anyDxcAZrDlPrw7cm7t4dVhdHUFbFXJjipsEktfz5Km5/M5AYj4pbrRwtyex/3 6amM66b5EkJsUGSaue9P5/aQixQwF2eM9H6+D6rY=
Received: from MSGRTPCCRD2WIN.DMN1.FMR.COM ([10.95.12.21]) by msgrtphc05win.DMN1.FMR.COM ([10.95.11.185]) with mapi; Fri, 6 Jun 2014 18:32:54 -0400
From: "Doyle, John" <john.doyle@fmr.com>
To: "'ned+ietf@mauve.mrochek.com'" <ned+ietf@mauve.mrochek.com>, "'dhc@dcrocker.net'" <dhc@dcrocker.net>
Date: Fri, 6 Jun 2014 18:32:53 -0400
Subject: Re: [dmarc-ietf] Suggestion: can we test DEMARC deployment with a mailing list?
Thread-Topic: [dmarc-ietf] Suggestion: can we test DEMARC deployment with a mailing list?
Thread-Index: Ac9ptLbD/EHVqF3wRq+CiAFhikt9+gYIor8x
Message-ID: <53A1885CA322CB498E17F4E1242556E101E560EFEF1D@MSGRTPCCRD2WIN.DMN1.FMR.COM>
In-Reply-To: <01P7I8FAW2JY000052@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZU8kxCZROr6DyAVKdmS1g4QeMeY
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 22:33:11 -0000

DQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IG5lZCtpZXRmQG1hdXZlLm1y
b2NoZWsuY29tIFttYWlsdG86bmVkK2lldGZAbWF1dmUubXJvY2hlay5jb21dDQpTZW50OiBXZWRu
ZXNkYXksIE1heSAwNywgMjAxNCAwMTowMSBBTQpUbzogRGF2ZSBDcm9ja2VyIDxkaGNAZGNyb2Nr
ZXIubmV0Pg0KQ2M6IElFVEYgPGlldGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW2RtYXJjLWll
dGZdIFN1Z2dlc3Rpb246IGNhbiB3ZSB0ZXN0IERFTUFSQyBkZXBsb3ltZW50IHdpdGggYSBtYWls
aW5nIGxpc3Q/DQoNCj4gT24gNS81LzIwMTQgNTozNyBQTSwgRnJlZCBCYWtlciAoZnJlZCkgd3Jv
dGU6DQo+ID4+PiBJIGd1ZXNzIHdl4oCZcmUgcnVubmluZyBpdC4gSSB3YXMgaG9waW5nIHRvIGF2
b2lkIHRoZSDigJxldmVyeXRoaW5nDQo+ID4+PiBhcm91bmQgYnJva2XigJ0gcGFydC4NCj4gPj4N
Cj4gPj4gV2VsbC4uIEkgY2FuIGNlcnRhaW5seSB0ZWxsIHlvdSB0aGF0LCBhcyBzb21lb25lIHdo
byBzdXBwb3J0cyBhDQo+ID4+IGNvdXBsZSBvZiBkb3plbiBlbWFpbCBsaXN0cywgYW4gYXdmdWwg
bG90IGJyb2tlDQo+IC4uLg0KPiA+IEFuZCB3aGF0IGNvbWVzIHF1aWNrbHkgdG8gbWluZCBpcyB0
aGUgY29tbWVudCwgZWFybGllciBpbiB0aGlzDQo+ID4gdGhyZWFkLCB0aGF0IOKAnHdlIGhhdmUg
YmVlbiBydW5uaW5nIGl0IGZvciBuaW5lIHllYXJzLuKAnQ0KPiA+DQo+ID4gUnVubmluZyBpdCwg
cGVyaGFwcywgYnV0IG5vdCBsZWFybmluZyBmcm9tIGl0LiBLaW5kIG9mIOKAnFJlYWxseSBOb3QN
Cj4gPiBUaGUgUG9pbnTigJ0uDQoNCg0KPiBJIG1pZ2h0IGJlIGEgYml0IGNvbmZ1c2VkIGFib3V0
IHRoZSAnaXQnIGJlaW5nIHJlZmVyZW5jZWQsIHNvIGl0J3Mgd29ydGgNCj4gZW5zdXJpbmcgc29t
ZSBjbGFyaXR5Og0KDQo+ICAgICAgMS4gIERLSU0gYW5kIFNQRiBoYXZlIGJlZW4gZmllbGRlZCBm
b3IgcGVyaGFwcyAxMiB5ZWFycy4gIERLSU0gaW4NCj4gaXRzIG9yaWdpbmFsLWJ1dC1zaW1pbGFy
IGZvcm0sIERvbWFpbktleXMsIGFuZCB0aGVuIGl0cyBpbml0aWFsDQo+ICdjb25zb3J0aXVtJyBm
b3JtLCBwcmVjZWRlZCB0aGUgMjAwNiBwdWJsaXNoZWQgREtJTSBSRkMgYnkgc2V2ZXJhbA0KPiB5
ZWFycy4gIFNQRiBhcHBlYXJlZCBhcm91bmQgdGhhdCB0aW1lIHRvby4gIFNvIHRoZSByZWZlcmVu
Y2UgdG8gNiB5ZWFycw0KPiBvZiBvcGVyYXRpb25hbCBleHBlcmllbmNlIGlzIHJlYWxseSBvbiB0
aGUgdmVyeSBsb3cgc2lkZS4NCg0KVGhlIHJlbGF0aW9uc2hpcCBvZiB0aW1lIHRvIG9wZXJhdGlv
bmFsIGV4cGVyaWVuY2UgaXMgZmFyIGZyb20gb2J2aW91cywgZXZlbg0KZm9yIHNwZWNpZmljYXRp
b25zIHdlIHZpZXcgYXMgc3VjY2Vzc2Z1bGx5IGRlcGxveWVkLg0KDQo+ICAgICAgMi4gIFVzZSBv
ZiBES0lNIGFuZCBTUEYgaXMgcmVhc29uYWJseSB3ZWxsIHVuZGVyc3Rvb2QgYW5kIGRvZXMgbm90
DQo+IGNhdXNlIGludGVyZXN0aW5nIGVtYWlsIG9wZXJhdGlvbnMgcHJvYmxlbXMuICBJJ20gc3Rh
cnRpbmcgdG8gaGVhciBzb21lDQo+IHVuZm9ydHVuYXRlIHN0b3JpZXMgYWJvdXQgREtJTSBzaWdu
YXR1cmUgYnJlYWthZ2UgaW4gc2NlbmFyaW9zIHRoYXQgSSdkDQo+IGhhdmUgaG9wZSB3b3VsZCBu
b3QgaGF2ZSBpdCwgYnV0IHRoZSBicmVha2FnZSBvZiB0aGUgc2lnbmF0dXJlIGlzIG5vdA0KPiBi
cmVha2luZyBsZWdpdGltYXRlIGVtYWlsIHNjZW5hcmlvcy4NCg0KVGhhdCdzIGluY29ycmVjdC4g
VGhlIG9idmlvdXMgY291bnRlcmV4YW1wbGUgaXMgTUlNRSBkb3duZ3JhZGluZywgd2hpY2ggd2Fz
IGENCmNvcmUgTUlNRSBjYXBhYmlsaXR5IGZyb20gdGhlIHN0YXJ0Lg0KDQpJIG5vdGUgaW4gcGFz
c2luZyB0aGF0IERLSU0gY291bGQgaGF2ZSBiZWVuIGVuZ2luZWVyZWQgdG8gYWNjb21vZGF0ZQ0K
dGhpcyBieSBjYW5vbmljYWxpemluZyB0byBiaW5hcnkgYW5kIHJlbW92ZWQgQ1RFcywgYnV0IHdh
c24ndC4NCg0KPiAgICAgIDMuICBETUFSQydzIGZ1bmN0aW9ucyBhbmQgbGltaXRhdGlvbnMgaGF2
ZSBiZWVuIHJlYXNvbmFibHkgd2VsbA0KPiB1bmRlcnN0b29kIHNpbmNlIGl0J3MgaW5jZXB0aW9u
LiAgSXQgd29ya3MgY29tZm9ydGFibHkgaW4gc3BlY2lmaWMNCj4gc2NlbmFyaW9zIGFuZCBjYXVz
ZXMgcHJvYmxlbXMgaW4gb3RoZXJzLiAgQWdhaW4sIHRoZXJlIGFyZSBubyBzdXJwcmlzZXMNCj4g
YWJvdXQgdGhlc2Ugbm93LiAgVGhleSd2ZSBiZWVuIGNsZWFybHkgdW5kZXJzdG9vZCBieSB0aG9z
ZSB3b3JraW5nIG9uDQo+IHRoZSBzcGVjLg0KDQpJIGNhbid0IHNwZWFrIHRvIHdoYXQgd2FzIGlu
IHRoZSBtaW5kcyBvZiB0aGUgZGV2ZWxvcGVycywgYnV0IEkgdmlldyB0aGUgZmFjdA0KdGhhdCB0
aGUgc3BlY2lmaWNhdGlvbiBpcyBub3RpY2VhYmx5IGxhY2tpbmcgaW4gZGVzY3JpYmluZyB0aGVz
ZSBsaW1pdGF0aW9ucyANCmFzIHByb2JsZW1hdGljLg0KDQpJIGhhdmVuJ3QgaGFkIHRpbWUgdG8g
ZG8gYSBjYXJlZnVsIHJldmlldyBvZiB0aGUgRE1BUkMgc3BlY2lmaWNhdGlvbiwgYnV0IEkgZG8N
Cm5vdGUgb25lIG9idmlvdXMgb21pc3Npb246IFdvdWxkbid0IGl0IGhhdmUgYmVlbiBoZWxwZnVs
IHRvIGRlZmluZSBhbiBlbmhhbmNlZA0Kc3RhdHVzIGNvZGUgZm9yIGEgcD1yZWplY3QgZmFpbHVy
ZSB3aGljaCBtYWlsaW5nIGxpc3RzIGNvdWxkIGRldGVjdCBhbmQgdGFrZQ0KYXBwcm9wcmlhdGUg
YWN0aW9uLCBpLmUuIGNvdW50aW5nIHRoaXMgYXMgYSBmYWlsdXJlIG9mIHRoZSBzZW5kZXIsIG5v
dCB0aGUNCnJlY2lwaWVudD8NCg0KPiAgICAgIDQuICBTUEYgYWN0dWFsbHkgaGFzIHRoZSBwb3Rl
bnRpYWwgZm9yIGNhdXNpbmcgc2ltaWxhciBvcGVyYXRpb25hbA0KPiBwcm9ibGVtcy4gIEl0IGhh
cyBhIHN0cmljdCBtb2RlIHRoYXQgd2lsbCBjYXVzZSByZWNlaXZlci1zaWRlIHJlamVjdGlvbnMN
Cj4gaWYgaG9ub3JlZCwgYW5kIHRoZXkgd2lsbCBvY2N1ciBmb3IgYW55IG11bHRpLWhvcCBzZXF1
ZW5jZS4gIEluIHRoZSBjYXNlDQo+IG9mIFNQRiwgbXVsdGktaG9wIG1lYW5zIC9hbnkvIHNlcXVl
bmNlIHRoYXQgcHJvZHVjZXMgYSBuZXcgY2xpZW50IHNtdHANCj4gSVAgYWRkcmVzcywgcHJlc2Vu
dGVkIHRvIHRoZSBldmFsdWF0aW5nIHJlY2VpdmVyLg0KDQpBbGwgdmVyeSB0cnVlLCBidXQgU1JT
IGFuZCBzaW1pbGFyIHNjaGVtZXMgcHJvdmlkZSBhIHJlYXNvbmFibGUgd2F5IHRvIGFkZHJlc3MN
ClNQRiBpc3N1ZXMuDQoNCj4gSW4gdGhlIGNhc2Ugb2YgRE1BUkMsDQo+IGdpdmVuIHRoZSB1c2Ug
b2YgREtJTSwgdGhlIHByb2JsZW0gaXMgbXVsdGktaG9wIGZvciBzY2VuYXJpb3MgdGhhdCBicmVh
aw0KPiBES0lNIHNpZ25hdHVyZXMuDQoNCkFuZCBBRkFJSyBubyBtaXRpZ2F0aW9uIHN0cmF0ZWd5
IGNvbXBhcmFibGUgdG8gU1JTIGlzIHBvc3NpYmxlIHdpdGggRE1BUkMgYXMgaXQNCmlzIHByZXNl
bnRseSBjb25zdGl0dXRlZC4NCg0KPiAgICAgIDUuICBUaGUgcmVhc29uIFNQRidzIHN0cmljdCBt
b2RlIGhhc24ndCBiZWVuIHByb2JsZW1hdGljIGlzIHRoYXQNCj4gdmlydHVhbGx5IG5vIG9uZSB1
c2VzIGl0Lg0KDQpUaGUgY3VzdG9tZXJzIHdlIGhhdmUgd2hvIGhhdmUgYmVlbiBmb3JjZWQgdG8g
ZGVwbG95IFNSUyBhcmUganVzdCBhIGZpZ21lbnQgb2YNCm15IGltYWdpbmF0aW9uIHRoZW4uDQoN
CkknbGwgYWxzbyBub3RlIHRoYXQgc3RyaWN0IG1vZGUgaXMgc3VmZmljaWVudCBidXQgbm90IG5l
Y2Vzc2FyeSB0byBjYXVzZQ0KcHJvYmxlbXMgdG8gZm9yd2FyZGVycy4gQSBsb3Qgb2YgcGxhY2Vz
IGZhY3RvciBTUEYgZmFpbHVyZXMgaW50byBzcGFtIHNjb3Jlcy4NCkFuIGluY3JlYXNlIGluIHRo
b3NlIHNjb3JlcyBtYXkgcmVzdWx0IGluIGFuIG92ZXJhbGwgaGlnaGVyIGZhaWx1cmUgcmF0ZXMu
DQoNCj4gU28gd2hhdCdzIGRpZmZlcmVudCBub3cgaXMgbm90IHRlY2huaWNhbCwgaXRzIG9wZXJh
dGlvbnMgcG9saWN5Lg0KDQpPcGVyYXRpb25zIHBvbGljaWVzIGFyZW4ndCB0ZWNobmljYWwgaW4g
bmF0dXJlPyBUaGV5IHN1cmUgc2VlbSB0ZWNobmljYWwgdG8gbWUuDQoNCgkJCQlOZWQNCg0K


From nobody Fri Jun  6 23:49:29 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8371A0217; Fri,  6 Jun 2014 23:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 t7nrBM_sr_Oy; Fri,  6 Jun 2014 23:49:25 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDF21A0256; Fri,  6 Jun 2014 23:49:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3A1B62CC5F; Sat,  7 Jun 2014 09:49:17 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
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 NOgeq__bpwRQ; Sat,  7 Jun 2014 09:49:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 8F0A72CC5D; Sat,  7 Jun 2014 09:49:12 +0300 (EEST)
Subject: Re: Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Content-Type: text/plain; charset=us-ascii
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org>
Date: Sat, 7 Jun 2014 09:49:11 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net>
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org>
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q9fO5gLIL5GlYgIIMbUCh-6zCYY
Cc: internetgovtech@iab.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: The IESG <iesg@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 06:49:27 -0000

For your information: additional details about the process and the =
coordination group are now available, here:=20

https://www.icann.org/resources/pages/process-next-steps-2014-06-06-en

Jari Arkko


From nobody Sat Jun  7 04:17:39 2014
Return-Path: <ahmedbakhat@pta.gov.pk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6245C1A0340 for <ietf@ietfa.amsl.com>; Sat,  7 Jun 2014 04:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.243
X-Spam-Level: **
X-Spam-Status: No, score=2.243 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793] autolearn=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 KfO9HQZMceoe for <ietf@ietfa.amsl.com>; Sat,  7 Jun 2014 04:17:33 -0700 (PDT)
Received: from mail.pta.gov.pk (unknown [202.83.166.248]) by ietfa.amsl.com (Postfix) with ESMTP id E60361A01B5 for <ietf@ietf.org>; Sat,  7 Jun 2014 04:17:30 -0700 (PDT)
Subject: AUTO: Ahmed Bakhat Masood is out of the office. (returning 06/14/2014)
Auto-Submitted: auto-generated
From: Ahmed Bakhat Masood <ahmedbakhat@pta.gov.pk>
To: ietf@ietf.org
Message-ID: <OF5B094752.2E457CBC-ON45257CF0.003E253E-45257CF0.003E2585@pta.gov.pk>
Date: Sat, 7 Jun 2014 16:18:48 +0500
X-MIMETrack: Serialize by Router on PTASrv002/PTA/PK(Release 8.5.3|September 15, 2011) at 06/07/2014 04:18:55 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TriIVgyFJdWRc4MCBqWZiDYK6cM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 11:17:35 -0000

I am out of the office until 06/14/2014.

I will not be able to respond to your mail. For urgent queries, please
contact Mr. Shageel Ahmed Dy Director (ICT) at shargeel@pta.gov.pk or Mr.
Anwar Zeb IT Officer at anwar@pta.gov.pk


Note: This is an automated response to your message  "ietf Digest, Vol 73,
Issue 17" sent on 06/07/2014 12:00:10 AM.

This is the only notification you will receive while this person is away.


From nobody Sat Jun  7 05:41:03 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 767C11A034A; Sat,  7 Jun 2014 05:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 vTh4qiZv9Kw9; Sat,  7 Jun 2014 05:40:59 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 299251A0349; Sat,  7 Jun 2014 05:40:59 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id p10so1903780wes.37 for <multiple recipients>; Sat, 07 Jun 2014 05:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:cc:content-type;  bh=vmCfXqRpTCWvYsiVjLKK4liizIAMDyL9xnIDoiNri58=; b=ll6P0H8177Gw0SHxzKmkQmjrJWV8iAAtxTWbxW32qXAPeUfG/Gizgecb07SdIxEr5v s+OTBy7uzswyg39FDBbpKkzqSS8S4NpXQ7D+Njy9m5++1dZh/FYfnOz92VQjjsXG90K+ Lqg8gPzAJCPtLxCvAe4/bn8sHzVcnMbh1aygsJIX76xqwDJ6ENs0ltvmyAGF1/VaUW4t PvmtTmW3S2aR9nRwe587ssu1d1WI6oQXindX4WmrGW4S5Ms2BKcuh1B2gNeIYHnVw8qP Zq8WaEv7R55qh1GP05cizoD1S6DxzsnkRlRNyYyZmMmL9MZ2IEoZO6+AobEo4pqTIHA/ TLGw==
MIME-Version: 1.0
X-Received: by 10.194.24.36 with SMTP id r4mr15619732wjf.39.1402144850866; Sat, 07 Jun 2014 05:40:50 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Sat, 7 Jun 2014 05:40:50 -0700 (PDT)
Date: Sat, 7 Jun 2014 08:40:50 -0400
X-Google-Sender-Auth: pbYUnUZyAVHRU6iilUhvmSG255g
Message-ID: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com>
Subject: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kvU9-WN7AASUAUpfUCpc__LpLGE
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 12:41:00 -0000

On Sat, May 3, 2014 at 2:08 PM, Hector Santos <hsantos@isdg.net> wrote:

> Let me ask, what if a fedex.com employee use this email domain for
> subscribing to the IETF list?

Any subsequent problems are irrelevant unless FedEx, the owner of
fedex.com considers them to be relevant.

That is what folk complaining don't get: you don't have the right to
use your employers email or a public email provider's email any way
you want. The domain name owner makes the rules.

As Craster insists: My domain, my rules.


If you want to make the rules then get your own domain. I think that
is something most IETF participants know how to do.

In the medium term, lets kill the stupidity of mailing lists with a
protocol that works. NNTP was originally designed to replace mailing
lists. It actually works quite well at that. The only problem was the
IT-Dictator mindset that underlies it: newsgroups have to be approved
by the Commune!

The idea that newsgroups work by the mail client PULLING a list of
unread messages and then PULLING those that are to be read is the best
architecture for newsgroups.


I am currently using 8Gb of my primary Gmail account space, 80% of
that is my mailing list mail. Google and Yahoo could both save tens of
millions of dollars worth of hard drives a year with a better
protocol, thats incentive to invest.

The only points that need to change are the mailing list programs need
to offer a very simple network API and the clients need to accept it.
The second is not so difficult to deploy for the 90% of webmail users.


From nobody Sat Jun  7 06:15:28 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8A31A034E; Sat,  7 Jun 2014 06:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Q6Al5lqy711q; Sat,  7 Jun 2014 06:15:22 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A85161A0076; Sat,  7 Jun 2014 06:15:21 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id m15so3899663wgh.8 for <multiple recipients>; Sat, 07 Jun 2014 06:15:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Vt5mrnyXUQ0h+/kaLernYLvlafjA7JfhVkcsm6diBlI=; b=AjWKZ8sGdH9oGJLTNOuzIMgjwNdzZqnQReSRqW+Fheo69jE7vCkwnoNuu15cb6tXFp xKOG/hS3DGDPVrrLzQm/Q1ScUvwXCbbJbBzZDIIk25N2zUuMFas8xOhm6GItLk4PvVL/ YuzEJOzwZVjy6X3Ov+QxPu0JxRfmaWGPR0FFnQJhGSzc8N96MGsPYr6DsCdFS1dFxU2b 98nKvfuHn9VnJa+aBfiHiQWmbXKeNP6FHQcQ29HDuRewdAItv0KxfZcCoBsfQvTRGPZd MHserIaMMT05NyBJWNpuYrRX2eFb1HEXMm03Y0aryyMcBX1n/4cJRyLtfkNHsCqZZjah xEQg==
X-Received: by 10.194.84.208 with SMTP id b16mr15654096wjz.55.1402146913167; Sat, 07 Jun 2014 06:15:13 -0700 (PDT)
Received: from [192.168.1.102] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id p3sm521607wjw.28.2014.06.07.06.15.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 07 Jun 2014 06:15:12 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [TLS] Last Call: <draft-ietf-tls-encrypt-then-mac-02.txt> (Encrypt-then-MAC for TLS and DTLS) to Proposed Standard
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20140606145220.8187.67355.idtracker@ietfa.amsl.com>
Date: Sat, 7 Jun 2014 16:15:13 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com>
References: <20140606145220.8187.67355.idtracker@ietfa.amsl.com>
To: "ietf\\@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ETlnK-3jSyPg38Jo3DuhA08sSm4
Cc: TLS Mailing List <tls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 13:15:24 -0000

Hi

I=92ve read the draft and I have a  few comments:

The motivation for this extension is not clear from the draft. The =
introduction says that the MAC-then-encrypt construction is =93no longer =
regarded as secure=94, and that it has been the subject of =93numerous =
security vulnerabilities and attacks=94. For the latter claim, there are =
no references given either in the document itself or in references. For =
the former two articles are cited.=20
The first (reference [5]) is by Hugo Krawczyk. While that article shows =
a theoretical weakness of MAC-then-encrypt, it also finds that (quoting =
from the abstract) =93On the positive side we show that the =
authenticate-then-encrypt method is secure if the encryption method in =
use is either CBC mode (with an underlying secure block cipher) or a =
stream cipher (that xor the data with a random or pseudorandom pad).=94. =
It also concludes that =93the current practical implementations of [SSL] =
that use the above modes of encryption are safe=94. So this is not a =
great call for action.
The second (reference [6]) is a better reference, but I=92m still =
missing a reference to anything practical or close to practical.

The rationale for the mandate in section 3.1 is not clear to me. Sure, =
EtM is better than MtE, so renegotiating from MtE to EtM is a downgrade, =
but there is no mandate for implementations that are configured to =
support both algorithms to avoid downgrading from AES-256 to single DES, =
so why add this here?   Also, this section uses the terms =93state=94, =
=93status=94 and =93mechanism=94 seemingly interchangeably, and doesn=92t =
explain why changing mechanism during renegotiation is a SHOULD =
NOT-level issue, or how AEAD ciphers figure in this mandate.

One more thing, this time a nit: informative reference number 7 =
describes a document as =93RFC xxxx=94. This is a reference to =
=93draft-bmoeller-tls-downgrade-scsv=94, which according to the =
datatracker is an individual draft that nobody=92s asked to publish yet. =
It should be referenced with the draft name as a work in progress. Since =
it=92s an informative reference, this won=92t block publication of this =
document.

Yoav
=20
On Jun 6, 2014, at 5:52 PM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from the Transport Layer Security WG
> (tls) to consider the following document:
> - 'Encrypt-then-MAC for TLS and DTLS'
>  <draft-ietf-tls-encrypt-then-mac-02.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-06-20. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document describes a means of negotiating the use of the
>   encrypt-then-MAC security mechanism in place of TLS'/DTLS' existing
>   MAC-then-encrypt one, which has been the subject of a number of
>   security vulnerabilities over a period of many years.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
> ID nits found an Obsolete normative reference: "RFC 4366 (ref. '3')=20
> (Obsoleted by RFC 5246, RFC 6066)" which will be replaced.
>=20
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls


From nobody Sat Jun  7 08:50:04 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 756B11A0245; Sat,  7 Jun 2014 08:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 8sl961E5_24w; Sat,  7 Jun 2014 08:49:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9338E1A00D7; Sat,  7 Jun 2014 08:49:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WtIqs-0001l7-L7; Sat, 07 Jun 2014 11:48:14 -0400
Date: Sat, 07 Jun 2014 11:49:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: The IESG <iesg@ietf.org>
Subject: Re: Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
Message-ID: <D542B5617099A08E39845464@JcK-HP8200.jck.com>
In-Reply-To: <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net>
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org> <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qGqDw6jfgydLJRWc7_LEQgbPpE4
Cc: internetgovtech@iab.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 15:50:01 -0000

--On Saturday, June 07, 2014 09:49 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> For your information: additional details about the process and
> the coordination group are now available, here: 
> 
> https://www.icann.org/resources/pages/process-next-steps-2014-
> 06-06-en

Jari,

I find one aspect of this document and the ongoing selection
process very troubling.  The work and schedule of the
Coordinating (nee Steering) Committee seem completely
open-ended, both with respect to time commitment and to resource
requirements (including the potential requirement for travel to
a potentially continual road show of meetings.  This new
document is worse in that regard than its predecessor because
both the schedule of meetings and the mission of the
Coordinating Committee have become open-ended.  Unlike many of
the appointing groups, the IETF is not in a position to
underwrite those costs, i.e., to cover costs of time-salary
and/or travel to the various meetings so as to spread those
costs across the relevant community.   The net effect is that
the only people who can plausibly represent the IETF are those
who:

(i) Work for organizational entities with considerable resources
and willingness to provide open-ended support their employees in
this type of work,

(ii) Have significant (even if not "too much") free time and
resources on their hands, or

(iii) Consider this particular part of the work really, really,
important.

I suggest that most people who fall into one or more of those
categories are not what we would normally consider
representative of the IETF community, much less representatives
of the diversity of this community (and note that "diversity" is
a new criterion).   Especially for the first category above,
there is also a considerable potential for conflicts of
responsibility and interest if organizations with significant
stakes in this process have employees or others appointed
through both IETF (including IAB) and other constituency models.

Perhaps it is the best we can do, but, especially since members
of that committee represent themselves once appointed, I think
it would be wise for the IETF to publicly note the issues and
create some distance from this process.  That would be
especially important if "we" eventually conclude that we have to
reject its final conclusion/ recommendations.

I also suggest that, if current IAB or IESG members decide to do
this and give it priority, the upcoming Nomcom should give
careful consideration to its impact on their current and
potential effectiveness in the roles to which prior Nomcom
appointed them as well as the overall effectiveness of those
bodies.

   best regards,
     john

p.s. Personal note: despite personal interest in this,
involvement as an advisor to IANA since the late 1970s and early
1980s, key roles in ICANN's creation and intermittent
involvement since (as liaison to the Board, advisor on multiple
issues (especially IDNs and i18n), and occasional consultant,
I'd not putting my name forward for this role.  The reasons are
ultimately connected to the remarks above: I have no funding for
an open-ended commitment that could involve significant time and
travel and I'm already overextended on work I feel I need to do
for the IETF. 



Especially with the added requirement for "diversity"



From nobody Sat Jun  7 14:59:07 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9FFB1A0228 for <ietf@ietfa.amsl.com>; Sat,  7 Jun 2014 14:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 MFvAm0zpNRte for <ietf@ietfa.amsl.com>; Sat,  7 Jun 2014 14:59:05 -0700 (PDT)
Received: from listserv.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C91DB1A0225 for <ietf@ietf.org>; Sat,  7 Jun 2014 14:59:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=223; t=1402178333; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=9lBL6XYC/gWNr3CY4f32LXUwl6E=; b=Ei07f9A6P+oFl71juLqr U/AO6yoUaAttsyWR+MpI01eE0I05Z8DodE9m1Cw5sHIAYMziv5jwONeycmzOwuYh 9a+HxI/zDTdkHF/qKsr5JghbM0b4XesqOiiJFsxGtTgvXNC3lHlHyNq6Mmuy9X2x vi2rtRjgmLGacdeFw4yG0b4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 07 Jun 2014 17:58:53 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1658458641.6036.2768; Sat, 07 Jun 2014 17:58:52 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=223; t=1402178169; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=RQs2G3D rg6ugPocZBqLnCqj54j0poVc7Z8RwaZojdpE=; b=nvYTMK2TexcNpgU/mF/hwfx POMn438Iop90Qi5wJsOg/TqXOUJ3HfemF2s7pxq/K+b0HdaN2Xa5MW1kF6zgcKBC Y1/JpZ1xQrFyZ2Pm2+DjHeQquCztt97v9KYkukd1xiy/zILdVsKsp3+58T6AgWKi 4qysQYGgXUHilhdWep30=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 07 Jun 2014 17:56:09 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1674816656.9.5448; Sat, 07 Jun 2014 17:56:08 -0400
Message-ID: <53938B1E.2020002@isdg.net>
Date: Sat, 07 Jun 2014 17:58:54 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dmarc@ietf.org, IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Next IETF Meeting DMARC Related Talks
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gqz3VB5hAe4WFToGKZ_5ND711pU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 21:59:07 -0000

I might be interested in remote participation at the next IETF 90 
meeting if there are any DKIM/DMARC related meetings scheduled.

I have not seen any announcements for any such DKIM/DMARC related 
activity.

-- 
HLS



From nobody Sat Jun  7 21:35:03 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D769C1A02C9; Sat,  7 Jun 2014 21:34:59 -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, SPF_PASS=-0.001] autolearn=ham
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 pwROepnTSg04; Sat,  7 Jun 2014 21:34:58 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E876B1A02C7; Sat,  7 Jun 2014 21:34:57 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hi2so513724wib.4 for <multiple recipients>; Sat, 07 Jun 2014 21:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tbS2RalzHAHtO5iFd9yoNK9Ksxu15YuG4+IlBSWJRDg=; b=acRhyCi/AGNvGfBhNCt+0x9wZeEyICNZnTBkm4CLgAZp4MlwpMP4lmCXCpOl7um//N cZ4FUnbOYu30LCaZbyVGOJI54ZRx6hTKbn+bOTqqTKjtDhPyT0xBC437DV/+yk5PV+Jc q9QkBrgLgcy5KrECdyNOhU2yvJ067M+83AI+PUzM6iSzeTwKkVkD9tmvNbUzNeXTvf6x 3dpEE/m5Bw7u386GMliG8NmJ1KoTzRPkQ+AXTybCE5OHaCGjffV/fLaH/O/X4Q2SVDeN rNtuDDx3Pq0PVNvzLqyVjlnzReT1ZJjDvPtwkP2+K1sR9jKXhaELcv8dJmiwRRglRSB1 9egQ==
MIME-Version: 1.0
X-Received: by 10.194.190.42 with SMTP id gn10mr20162661wjc.9.1402202089533; Sat, 07 Jun 2014 21:34:49 -0700 (PDT)
Received: by 10.180.23.104 with HTTP; Sat, 7 Jun 2014 21:34:49 -0700 (PDT)
In-Reply-To: <53938B1E.2020002@isdg.net>
References: <53938B1E.2020002@isdg.net>
Date: Sat, 7 Jun 2014 21:34:49 -0700
Message-ID: <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com>
Subject: Re: Next IETF Meeting DMARC Related Talks
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=047d7bb708827335c404fb4b9d05
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5eWpVQXb42pJSjSc6iNd7mbmOWA
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 04:35:00 -0000

--047d7bb708827335c404fb4b9d05
Content-Type: text/plain; charset=UTF-8

On Sat, Jun 7, 2014 at 2:58 PM, Hector Santos <hsantos@isdg.net> wrote:

> I might be interested in remote participation at the next IETF 90 meeting
> if there are any DKIM/DMARC related meetings scheduled.
>
> I have not seen any announcements for any such DKIM/DMARC related activity.


None are presently scheduled; there isn't a DMARC working group, no BoF
session has been requested (that I know of), and no related work is going
on in other working groups (that I know of).  Of course, all of that could
change, so "watch this space".

-MSK

--047d7bb708827335c404fb4b9d05
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Jun 7, 2014 at 2:58 PM, Hector Santos <span dir=3D=
"ltr">&lt;<a href=3D"mailto:hsantos@isdg.net" target=3D"_blank">hsantos@isd=
g.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I might be interested in remote participatio=
n at the next IETF 90 meeting if there are any DKIM/DMARC related meetings =
scheduled.<br>

<br>
I have not seen any announcements for any such DKIM/DMARC related activity.=
<span class=3D"HOEnZb"><font color=3D"#888888"></font></span></blockquote><=
div><br></div><div>None are presently scheduled; there isn&#39;t a DMARC wo=
rking group, no BoF session has been requested (that I know of), and no rel=
ated work is going on in other working groups (that I know of).=C2=A0 Of co=
urse, all of that could change, so &quot;watch this space&quot;.<br>
<br>-MSK <br></div></div></div></div>

--047d7bb708827335c404fb4b9d05--


From nobody Sat Jun  7 23:33:11 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E97331A0342; Sat,  7 Jun 2014 23:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 J39gGdCNBuSa; Sat,  7 Jun 2014 23:33:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E43E31A026B; Sat,  7 Jun 2014 23:33:03 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WtWdO-0002V3-D3; Sun, 08 Jun 2014 02:31:14 -0400
Date: Sun, 08 Jun 2014 02:32:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Hector Santos <hsantos@isdg.net>
Subject: Re: Next IETF Meeting DMARC Related Talks
Message-ID: <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com>
In-Reply-To: <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com>
References: <53938B1E.2020002@isdg.net> <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4q6CVNW8GZrxa0ft19oUbp0bpIU
Cc: dmarc@ietf.org, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 06:33:06 -0000

--On Saturday, June 07, 2014 21:34 -0700 "Murray S. Kucherawy"
<superuser@gmail.com> wrote:

> On Sat, Jun 7, 2014 at 2:58 PM, Hector Santos
> <hsantos@isdg.net> wrote:
> 
>> I might be interested in remote participation at the next
>> IETF 90 meeting if there are any DKIM/DMARC related meetings
>> scheduled.
>> 
>> I have not seen any announcements for any such DKIM/DMARC
>> related activity.
> 
> 
> None are presently scheduled; there isn't a DMARC working
> group, no BoF session has been requested (that I know of), and
> no related work is going on in other working groups (that I
> know of).  Of course, all of that could change, so "watch this
> space".

Murray, you didn't mention whether there is any ongoing
discussion in dmarc.org and, if so, how Hector can participate
there.  If there are no further discussions there and dmarc.org
is turning change control over to the IETF, it might be helpful
for people here to know that.  Conversely, if discussions on the
IETF dmarc list (or the IETF list) are simply taken as input to
a change control and decision process that is not described on
the dmarc.org web pages or in any other obvious place, it would
be good to be explicit about that.

   regards,
    john






From nobody Sat Jun  7 23:51:55 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FA71A02FE; Sat,  7 Jun 2014 23:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 4Cb9DScFgIah; Sat,  7 Jun 2014 23:51:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E6BD1A01D1; Sat,  7 Jun 2014 23:51:52 -0700 (PDT)
Received: from [192.168.1.45] (205.195-136-217.adsl-dyn.isp.belgacom.be [217.136.195.205]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s586pdhR025772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 7 Jun 2014 23:51:44 -0700
Message-ID: <539407C6.1070604@dcrocker.net>
Date: Sun, 08 Jun 2014 08:50:46 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Next IETF Meeting DMARC Related Talks
References: <53938B1E.2020002@isdg.net> <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com> <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com>
In-Reply-To: <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 07 Jun 2014 23:51:45 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mH4NvjW17yis_7EP4qOakz9kfI8
Cc: dmarc@ietf.org, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 06:51:53 -0000

On 6/8/2014 8:32 AM, John C Klensin wrote:
> Murray, you didn't mention whether there is any ongoing
> discussion in dmarc.org and, if so, how Hector can participate
> there. 

That's because Hector is already active in the IETF's DMARC discussion
list, which was an addressee of your note, as it is of this one...


> If there are no further discussions there and dmarc.org
> is turning change control over to the IETF, it might be helpful
> for people here to know that.

Discussions continue.

To my non-expert eyes, the IPR statements in the base I-D spec:

   https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/

is standard IETF boilerplate and already shows the IETF Trust as holding
copyright...



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Jun  8 08:41:31 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 022561A0089; Sun,  8 Jun 2014 08:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.351
X-Spam-Level: 
X-Spam-Status: No, score=-1.351 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 T---Ox2yjdDb; Sun,  8 Jun 2014 08:40:13 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6F0A1A00D2; Sun,  8 Jun 2014 08:40:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WtfB0-0003JT-S5; Sun, 08 Jun 2014 11:38:30 -0400
Date: Sun, 08 Jun 2014 11:40:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Next IETF Meeting DMARC Related Talks
Message-ID: <4465008835DE6369E27DA302@JcK-HP8200.jck.com>
In-Reply-To: <539407C6.1070604@dcrocker.net>
References: <53938B1E.2020002@isdg.net> <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com> <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com> <539407C6.1070604@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jbBOKD722PrrAwwaSKqQtY7HXZI
Cc: dmarc@ietf.org, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 15:40:20 -0000

--On Sunday, June 08, 2014 08:50 +0200 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 6/8/2014 8:32 AM, John C Klensin wrote:
>> Murray, you didn't mention whether there is any ongoing
>> discussion in dmarc.org and, if so, how Hector can participate
>> there. 
> 
> That's because Hector is already active in the IETF's DMARC
> discussion list, which was an addressee of your note, as it is
> of this one...

And, because I'm still confused about change control and
decision processes (see below), I deliberately asked about
dmarc.org, not about the IETF's DMARC discussion list.

>> If there are no further discussions there and dmarc.org
>> is turning change control over to the IETF, it might be
>> helpful for people here to know that.
> 
> Discussions continue.
> 
> To my non-expert eyes, the IPR statements in the base I-D spec:
> 
>    https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/
> 
> is standard IETF boilerplate and already shows the IETF Trust
> as holding copyright...

To my non-expert eyes, informed by many years of IETF IPR
discussions and a recent rereading of the IETF Trust policies,
the copyright is important if someone wants to reproduce the
document (not at issue here, AFICT) or if the IETF decides
create a WG that intended to use the work as a starting point,
possibly forking it.  As far as I know, no one has suggested the
latter.  The copyright would be equally irrelevant if the IETF
decided to ignore DMARC (except as a learning experience) and
adopt some other technology.  

I asked about voluntary handoff of change control; I don't see
want your response about copyright has to do with that.  I hope
we are not heading into another round in which the IETF is asked
to adopt another technology and standardize it but told that it
can't make substantive changes in that technology because it has
already been discussed, adopted, and deployed elsewhere but that
possibility is precisely why the question of change control is
relevant.  Copyright in a document not produced in the IETF does
not appear to be.

best,
   john




From nobody Sun Jun  8 08:42:15 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D99F1A0357; Sun,  8 Jun 2014 08:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 46kLvwCpJp5L; Sun,  8 Jun 2014 08:41:54 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CBCB1A0089; Sun,  8 Jun 2014 08:41:54 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id hi2so911857wib.1 for <multiple recipients>; Sun, 08 Jun 2014 08:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zhETK1y6+/hJTcxAlneHnRtDel7z89x/XP7EOTgHnZ0=; b=OTLGGIckX7Im+IAARBQJmHtmDwQptspx3ys57JEDTm9s2z/pvCgRqkBrDGlLTVmxFq IdYirvf4P7IEzP4EOgHtVvEJEvpkOBChaN2CDe/lWlgPeYFtKN3XF+CjSP6A+iVJjMio 2hplYrDDc9ucDQnK1zN8zKoiFzSwUrp5nYXle+axmyanIVN038wR+Ks7h+bRkB9FcB9d tF4G1lLzF9i8RILV755BXEeHhqG8AYJmz/qBHixKwmgwaCbicQZPD1mKwJfcHoq9jemI v6dswU3o9qibeo7f4hgufPrExfZZgIpdzyfJl/IwCHR755BXUX1JoZWEifyqJMZJ7sdT wg5w==
MIME-Version: 1.0
X-Received: by 10.180.212.77 with SMTP id ni13mr23802260wic.5.1402242112975; Sun, 08 Jun 2014 08:41:52 -0700 (PDT)
Received: by 10.180.23.104 with HTTP; Sun, 8 Jun 2014 08:41:52 -0700 (PDT)
In-Reply-To: <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com>
References: <53938B1E.2020002@isdg.net> <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com> <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com>
Date: Sun, 8 Jun 2014 08:41:52 -0700
Message-ID: <CAL0qLwZhV1VBXZr+NMP0bX7CnSj2m2cH3=MoMZZ3ewuwcZpiCw@mail.gmail.com>
Subject: Re: Next IETF Meeting DMARC Related Talks
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c23e5a0879f904fb54efe7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZCWHbqmq0f9ZopcPs3NwixVQ9Y8
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 15:41:59 -0000

--001a11c23e5a0879f904fb54efe7
Content-Type: text/plain; charset=UTF-8

On Sat, Jun 7, 2014 at 11:32 PM, John C Klensin <john-ietf@jck.com> wrote:

> Murray, you didn't mention whether there is any ongoing
> discussion in dmarc.org and, if so, how Hector can participate
> there.  If there are no further discussions there and dmarc.org
> is turning change control over to the IETF, it might be helpful
> for people here to know that.  Conversely, if discussions on the
> IETF dmarc list (or the IETF list) are simply taken as input to
> a change control and decision process that is not described on
> the dmarc.org web pages or in any other obvious place, it would
> be good to be explicit about that.
>

Hi John,

There are two active venues for discussion about DMARC.  This one is the
primary one.  There is a legacy list operated at dmarc.org that has more
casual conversation not geared to specification development and advancement.

We are still discussing the change control transfer, but I can say that do
so was always the end goal.  It has been submitted to the ISE, but it's
always possible to make important changes while it's pending in that queue.

-MSK

--001a11c23e5a0879f904fb54efe7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Jun 7, 2014 at 11:32 PM, John C Klensin <span dir=
=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ie=
tf@jck.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Murray, you didn&#39;t mention whether there=
 is any ongoing<br>
discussion in <a href=3D"http://dmarc.org" target=3D"_blank">dmarc.org</a> =
and, if so, how Hector can participate<br>
there. =C2=A0If there are no further discussions there and <a href=3D"http:=
//dmarc.org" target=3D"_blank">dmarc.org</a><br>
is turning change control over to the IETF, it might be helpful<br>
for people here to know that. =C2=A0Conversely, if discussions on the<br>
IETF dmarc list (or the IETF list) are simply taken as input to<br>
a change control and decision process that is not described on<br>
the <a href=3D"http://dmarc.org" target=3D"_blank">dmarc.org</a> web pages =
or in any other obvious place, it would<br>
be good to be explicit about that.<br></blockquote><div><br></div><div>Hi J=
ohn,<br><br></div><div>There are two active venues for discussion about DMA=
RC.=C2=A0 This one is the primary one.=C2=A0 There is a legacy list operate=
d at <a href=3D"http://dmarc.org">dmarc.org</a> that has more casual conver=
sation not geared to specification development and advancement.<br>
<br></div><div>We are still discussing the change control transfer, but I c=
an say that do so was always the end goal.=C2=A0 It has been submitted to t=
he ISE, but it&#39;s always possible to make important changes while it&#39=
;s pending in that queue.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c23e5a0879f904fb54efe7--


From nobody Sun Jun  8 13:20:56 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685491A03F9; Sun,  8 Jun 2014 13:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 duOigd0bJLne; Sun,  8 Jun 2014 13:20:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 119271A03EA; Sun,  8 Jun 2014 13:20:53 -0700 (PDT)
Received: from [192.168.1.45] ([109.128.169.101]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s58KKif9018047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 8 Jun 2014 13:20:51 -0700
Message-ID: <5394C566.6050808@dcrocker.net>
Date: Sun, 08 Jun 2014 22:19:50 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Next IETF Meeting DMARC Related Talks
References: <53938B1E.2020002@isdg.net> <CAL0qLwYWTfRT_G24CZxfwY5-CigigkdxqYaahPQX2Y_pUaR3Sw@mail.gmail.com> <5F14A8207940865BA1BB5186@JcK-HP8200.jck.com> <539407C6.1070604@dcrocker.net> <4465008835DE6369E27DA302@JcK-HP8200.jck.com>
In-Reply-To: <4465008835DE6369E27DA302@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 08 Jun 2014 13:20:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JshWIBhV_BJxXodRjOCYEmxNylI
Cc: dmarc@ietf.org, IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 20:20:54 -0000

On 6/8/2014 5:40 PM, John C Klensin wrote:
> 
> 
> --On Sunday, June 08, 2014 08:50 +0200 Dave Crocker
> <dhc@dcrocker.net> wrote:
>> That's because Hector is already active in the IETF's DMARC
>> discussion list, which was an addressee of your note, as it is
>> of this one...
> 
> And, because I'm still confused about change control and
> decision processes (see below), I deliberately asked about
> dmarc.org, not about the IETF's DMARC discussion list.

Same answer about that list.  He's active there, too.  It's an open list.


> I asked about voluntary handoff of change control;

You did?  I can't seem to find a recent message from you with either the
word voluntary or handoff.  Which message are you referring to?


>  I hope
> we are not heading into another round in which the IETF is asked
> to adopt another technology and standardize it but told that it
> can't make substantive changes in that technology because it has
> already been discussed, adopted, and deployed elsewhere but that
> possibility is precisely why the question of change control is
> relevant. 

You make it sound as if the IETF hasn't previously taken in protocols
that already had a significant installed base, with the proviso that it
protect it.

You also make it seem that there was work known to be needed on the base
protocol, when in fact there wasn't, after multiple queries in multiple
venues.

I know that requiring a working group to protect and installed base is
pretty outlandish and gets in the way of engineering idealism, but
really...

And given your deep concern about this current situation, please do
indicate what actual protocol work you feel is needed.  It will useful
input to a possible charter.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Jun  9 01:15:14 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACA71A000E; Mon,  9 Jun 2014 01:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.259
X-Spam-Level: 
X-Spam-Status: No, score=0.259 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 9kTdkV-bhXSg; Mon,  9 Jun 2014 01:15:06 -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 F189B1A0016; Mon,  9 Jun 2014 01:15:02 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.158.228]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s598EmTI026249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jun 2014 01:14:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402301702; x=1402388102; bh=ULSeGCMtjWtOvF/OsCUcrRF1UWWkj1y+ksOfOOfFOFs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=A/nGaA3AvSqf+Hm4yRcwcDxHmd/YkQMIp1fHtvLcDffQwBeqJvShmjPAKHaots56J fwFUnDAyebKjbqy4QfnYXG6ICJGqn1KVpH6U1P1Kg8/VLk32tcVQRT7ng2hZ+WZsSE IADcykEIJXCNojIhRrEQsCRuIhPsFiVNP9qLGAZA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402301702; x=1402388102; i=@elandsys.com; bh=ULSeGCMtjWtOvF/OsCUcrRF1UWWkj1y+ksOfOOfFOFs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zdVCbfoswTOdUTKEDgqskGeNZyF0ojoB85a/NYW6XIfNETkNyaKyVphx6dRO29lzA nFvyLPQ9UzpGEPXDW7H2bv4k8Hh2UIhe2WIr+egRq+stnRrZIskV9VqA5OLSfz9YKK TBY3wvZZBEbF87keiOaIUj1GBk/tOdK5rE1Bdu4Y=
Message-Id: <6.2.5.6.2.20140608231017.06ddd160@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 09 Jun 2014 00:29:13 -0700
To: iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
In-Reply-To: <D542B5617099A08E39845464@JcK-HP8200.jck.com>
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org> <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net> <D542B5617099A08E39845464@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AV6kA_36tXUmLPn9Tlao0cMaxyI
Cc: John C Klensin <john-ietf@jck.com>, internetgovtech@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 08:15:08 -0000

Hello,

I think that John Klensin raised some valid points.

At 08:49 07-06-2014, John C Klensin wrote:
>Perhaps it is the best we can do, but, especially since members
>of that committee represent themselves once appointed, I think
>it would be wise for the IETF to publicly note the issues and
>create some distance from this process.  That would be
>especially important if "we" eventually conclude that we have to
>reject its final conclusion/ recommendations.

The "best we can do" will be scrutinized and might highlight IETF 
internal issues.  The pessimistic outlook is that the process will be 
controversial.  Should the IETF be entangled in all that?  It would 
be worthwhile to consider whether the IETF would like to have the 
ability to say "we disagree" and how it would be able to exercise 
that option when it is actively involved in the process.

Regards,
S. Moonesamy 


From nobody Mon Jun  9 03:01:45 2014
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E32E1A004B; Mon,  9 Jun 2014 03:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 49jFmmcnGcey; Mon,  9 Jun 2014 03:01:34 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D514C1A0032; Mon,  9 Jun 2014 03:01:33 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hi2so1650798wib.0 for <multiple recipients>; Mon, 09 Jun 2014 03:01:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=a2mpiRDPZ53ho6/BBcQlzIA1qvA2Kq0PhN9B6v8VCKs=; b=t0p2Gr+zlNSsnYVO7LfcTfTt2MMO7+jtnPTjntgD2rM4DR6zSa4EDu7G/+Fv97yJr9 T042YGwf6sTDrXopz+z7ndYNY049mP0Fr3g498FyzuM9vhJzC+bT5i2xb40mGRcNucbP eBgTzBP1YraE3roVbQWRN7xz9I+Bdsq03xCilM+asmzjLgeq2+pF45roLF2swSqjh7a9 je5R6TznGUPmcy5jLkm1/+W03phGxEIx3+tVa/LogUgu7yYIN8zW9TMhYYJkgnLWr/n/ XNFcqrQxI1ghIgVXf6P8FZ+6cKxkoYRArDdDxHI187o3/kncsX6ieglrL+rcx0k7Rswd A+CQ==
MIME-Version: 1.0
X-Received: by 10.194.186.210 with SMTP id fm18mr29883384wjc.67.1402308092311;  Mon, 09 Jun 2014 03:01:32 -0700 (PDT)
Received: by 10.217.37.200 with HTTP; Mon, 9 Jun 2014 03:01:32 -0700 (PDT)
In-Reply-To: <D542B5617099A08E39845464@JcK-HP8200.jck.com>
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org> <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net> <D542B5617099A08E39845464@JcK-HP8200.jck.com>
Date: Mon, 9 Jun 2014 12:01:32 +0200
Message-ID: <CAKFn1SFjoMPw3vSuOEQjYnWJU-i6okz_n=f28WUFXfyWj3T27w@mail.gmail.com>
Subject: Re: [Internetgovtech] Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
From: =?UTF-8?Q?Roger_J=C3=B8rgensen?= <rogerj@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bhsrkpnqoJEY92MYyA-UmZ_yc0Y
Cc: internetgovtech@iab.org, The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 10:01:35 -0000

On Sat, Jun 7, 2014 at 5:49 PM, John C Klensin <john-ietf@jck.com> wrote:
<snip>
> Coordinating Committee have become open-ended.  Unlike many of
> the appointing groups, the IETF is not in a position to
> underwrite those costs, i.e., to cover costs of time-salary
> and/or travel to the various meetings so as to spread those
> costs across the relevant community.   The net effect is that
> the only people who can plausibly represent the IETF are those
> who:

This part here made me think, can this issue about cost be the first
step on the way to a multi-stakeholder for Internet where only
the rich can participate? Rich as in having money AND time to travel
to endless meetings around the world? ... I hope not.

Personally I would like to get more involved but I can not see a way
to get more involved, have no way to fund it, or see how I can get
time to do more.


Except that, it's great work and good to see discussion  on the
subject (IANA transition) and future for the Internet.


<snip>
> p.s. Personal note: despite personal interest in this,
> involvement as an advisor to IANA since the late 1970s and early
> 1980s, key roles in ICANN's creation and intermittent
> involvement since (as liaison to the Board, advisor on multiple
> issues (especially IDNs and i18n), and occasional consultant,
> I'd not putting my name forward for this role.  The reasons are
> ultimately connected to the remarks above: I have no funding for
> an open-ended commitment that could involve significant time and
> travel and I'm already overextended on work I feel I need to do
> for the IETF.
>
>
>
> Especially with the added requirement for "diversity"

Any discussion without historic view have a possibility to repeat old
mistakes...



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no


From nobody Mon Jun  9 07:26:45 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817431A01BC; Mon,  9 Jun 2014 07:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 nmqyh1Emy8Bt; Mon,  9 Jun 2014 07:26:41 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A4AA1A017C; Mon,  9 Jun 2014 07:26:41 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s59EQdlD000906; Mon, 9 Jun 2014 15:26:39 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s59EQbnr000853 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 9 Jun 2014 15:26:38 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-smp-requirements-05.txt> (Requirements for MPLS-TP Shared Mesh Protection) to Informational RFC
Date: Mon, 9 Jun 2014 15:26:37 +0100
Message-ID: <05fd01cf83ee$d36d6250$7a4826f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+D7tDjzCAoIa+JQDCWHFBixkgLOg==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20748.000
X-TM-AS-Result: No--18.236-10.0-31-10
X-imss-scan-details: No--18.236-10.0-31-10
X-TMASE-MatchedRID: vEvJ7Rh1lGgzx9GDMr0HvzYTypjB3iDVuikHZcC6ceDgq9d1J0a/O0xO 7+3QV5trddLzNY2Nt2JQfV8BOtYTtqNmd7pYp+mtR+GtoiXVeDHomXBvaBu6TpMxNpDOG+h6Cf2 h9A2gFAWPScoCueHJCsSIUbXCYKjGS2my/ooOam/r/EBmiNuXt4GzTdEevOMzEB/Asc4oaYFeSF +P1eXHLQVjXBUVPPkIAGvNFj/ALTkhWGQFjj8epM+ayFtEW0uYhSl7KAXaa8LfUZT83lbkEN/rc nYNDHdsDAy9+p2eZkapekVEr8FUaNcUNjoF7YuVr04R126Gsieau7dML+YtTrV5fSMRD1zqMC/K /e26+Q3s35lYsesx4+x6Uxdi4ACrDCWUT3P4Uqe8coKUcaOOvX0tCKdnhB58vqq8s2MNhPB9j2G wzTE3vSq2rl3dzGQ1A/3R8k/14e0=
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6rmDZnQ9HcK_z1vWn5C06Mzj5d0
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 14:26:43 -0000

Here are some comments from my review as AD that need to get handled as part of
IETF last call.

Thanks,
Adrian

===

Could you expand "p2p" where it is first used?

---

The very first sentence is hard to parse

   MPLS transport networks can be characterized as being a network of
   connections between nodes within a mesh of nodes and the links
   between them. 

Maybe try

   The MPLS Transport Profile (MPLS-TP) provides tools to construct and
   operate a set of connections between nodes in an MPLS network.  The
   MPLS network is a mesh comprising nodes and the links between them.

---

I understand that you want to use RFC 2119 language to clarify the 
requirements, but RFC 2119 was developed for specifying protocols, so 
the direct reference and boilerplate quote is incongruous. I suggest
you use the language as found in RFC 5654, viz.:

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].
   Although this document is not a protocol specification, the use of
   this language clarifies the instructions to protocol designers
   producing solutions that satisfy the requirements set out in this
   document.

---

In Section 5.1 you have

   the control
   protocol SHOULD NOT be used as the primary resilience mechanism.

I agree, but I think that the term "primary resilience mechanism" may be
under defined. Can you do anything to clarify this? Maybe...

   the control
   protocol SHOULD NOT be used as the primary mechanism for detecting or
   reporting network failures, or for initiating or coordinating 
   protection switch-over.  That is, it SHOULD NOT be used as the 
   primary resilience mechanism.

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: 09 June 2014 15:10
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-smp-requirements-05.txt>
> (Requirements for MPLS-TP Shared Mesh Protection) to Informational RFC
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'Requirements for MPLS-TP Shared Mesh Protection'
>   <draft-ietf-mpls-smp-requirements-05.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-06-23.


From nobody Mon Jun  9 09:04:49 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D46A1A0201 for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 09:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 IFYB0Slc_riG for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 09:04:46 -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 B5B3D1A020A for <ietf@ietf.org>; Mon,  9 Jun 2014 09:04:45 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.146]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s59G4Sbe025836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jun 2014 09:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402329880; x=1402416280; bh=OkdUv2ltym54GrBlie5KpiYifIOsi9+/T3sbGq/ydBQ=; h=Date:To:From:Subject:In-Reply-To:References; b=mJI6gIW+dBWZIbp6RYxtloLaXSGPRGL55ZLocoBU/Yj9//KSvPshcx5NPsa/nJ7U8 mMjygPl+pE/hPtrMXdMl9wIfuNn6LiYVVY7PVO58+Mbaoey5WmIN8HRNilHo/Fjjxk DiqALeGZtQZ6inScV+s9qemcCbsjhlHhTx1VdvE8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402329880; x=1402416280; i=@elandsys.com; bh=OkdUv2ltym54GrBlie5KpiYifIOsi9+/T3sbGq/ydBQ=; h=Date:To:From:Subject:In-Reply-To:References; b=OtY2jTp8EjpqpozE9B9gIaD4KaiFzZJ+YYhhEnjtVGRO94z/7C8/6g7/F7YjhFO0I UOiRlgAiuFtS+XtaY5kqhwZo8XTp+/0ekXSGfoXSdyXE/DRlnIw4qhQO6NNJlBG2bR p9zRgh9tqGm3Wmi8bmjOVIzj1C1HrkP7ZlBH1rnA=
Message-Id: <6.2.5.6.2.20140609081221.0b120268@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 09 Jun 2014 08:55:49 -0700
To: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: RFC compliance and the European Parliament
In-Reply-To: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.par l.union.eu>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HmHmz69oYo9l3pG8gS_M1nh6wAs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 16:04:48 -0000

Hi Erik,

I am copying this message to ietf@ietf.org instead of the perpass 
mailing list as the question is not related to surveillance.

At 04:00 09-06-2014, JOSEFSSON Erik wrote:
>I need help from the standards community with regards to 
>RFC-compliance in the European Parliament.
>
>I reach out here because I believe you expect your work on improving 
>the internet will be implemented, maybe in particular by public 
>bodies we hold to a higher standard wrt transparency than others[0].
>
>In an Access to Documents request the EP just stated that 
>"conformity with RFC-5321 section 3.9 is by nature outside EP's 
>responsibilities" [1].
>
>Do you agree? Are there RFCs which correct implementation would, by 
>nature, fall within the responsibilities of the EP?

I read the reply.  In my opinion the text quoted (above) from the 
reply conveys a different meaning.  My understanding of that part of 
the reply is that mailing lists managed outside that email system is 
outside EP's responsibility.  The question you asked could be stated 
as follows:

   Is it the responsibility of the EP to set the standards for email systems
   to adhere to?

>Please find a link to our documentation of the particular issue with 
>RFC-5321 section 3.9 below[2]

The issue in that document is about whether the mail relays for 
europarl.europa.eu can reject a message from a (external) mailing 
list if the "From:" header contains "europarl.europa.eu" as the 
domain part.  There is be a mail delivery problem if the external 
email system implements and follows what is written in RFC 5321.

Regards,
S. Moonesamy 


From nobody Mon Jun  9 09:38:11 2014
Return-Path: <cdel@firsthand.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719F31A01EF; Mon,  9 Jun 2014 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] autolearn=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 jYSyPp8H009o; Mon,  9 Jun 2014 09:38:04 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CD7F1A00D4; Mon,  9 Jun 2014 09:38:04 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=firsthand.net;  b=SYyGtWHCqqnf7jk+Dv4MVpeal1FUbdnlpprOkHQQG1Mp/KeYR1PZm+/M7qmEhWg7s88m8/JzYNLNscXQrPBiLPJOJ3Sx3d6fgF3SzVBiiK+W/FSIB8RuqmEY0mxUBPfY; h=X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type;
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from orionlocal.local (host-2-96-80-208.as13285.net [2.96.80.208]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id A0FFAE0102; Mon,  9 Jun 2014 16:37:55 +0100 (BST)
Message-ID: <5395E2E5.9010300@firsthand.net>
Date: Mon, 09 Jun 2014 17:37:57 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.10 (Macintosh/20140526)
MIME-Version: 1.0
To: =?UTF-8?B?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Re: [Internetgovtech] Coordination Group Members for the Transition of NTIA's Stewardship of the IANA Functions
References: <90B42437-9C59-41ED-83C1-94DA1E58237D@ietf.org> <DD582456-B472-4CC3-BA76-3AC5A39C2A3E@piuha.net> <D542B5617099A08E39845464@JcK-HP8200.jck.com> <CAKFn1SFjoMPw3vSuOEQjYnWJU-i6okz_n=f28WUFXfyWj3T27w@mail.gmail.com>
In-Reply-To: <CAKFn1SFjoMPw3vSuOEQjYnWJU-i6okz_n=f28WUFXfyWj3T27w@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigE985FBEB1D99C5F75A6E4F48"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fziHErjhhJJpaSBylgENH4yPZW0
Cc: John C Klensin <john-ietf@jck.com>, internetgovtech@iab.org, The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cdel@firsthand.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 16:38:06 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE985FBEB1D99C5F75A6E4F48
Content-Type: multipart/alternative;
 boundary="------------040609000209060709030708"

This is a multi-part message in MIME format.
--------------040609000209060709030708
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It would be a good thing for I* bodies to reflect on these points that
John and Roger are making and provide meaningful support for individual
actors to engage effectively and in a balanced way or admit that they
are not multi stakeholder.



Christian

Roger J=C3=B8rgensen wrote:
> On Sat, Jun 7, 2014 at 5:49 PM, John C Klensin <john-ietf@jck.com> wrot=
e:
> <snip>
>> Coordinating Committee have become open-ended.  Unlike many of
>> the appointing groups, the IETF is not in a position to
>> underwrite those costs, i.e., to cover costs of time-salary
>> and/or travel to the various meetings so as to spread those
>> costs across the relevant community.   The net effect is that
>> the only people who can plausibly represent the IETF are those
>> who:
>
> This part here made me think, can this issue about cost be the first
> step on the way to a multi-stakeholder for Internet where only
> the rich can participate? Rich as in having money AND time to travel
> to endless meetings around the world? ... I hope not.
>
> Personally I would like to get more involved but I can not see a way
> to get more involved, have no way to fund it, or see how I can get
> time to do more.
>
>
> Except that, it's great work and good to see discussion  on the
> subject (IANA transition) and future for the Internet.
>
>
> <snip>
>> p.s. Personal note: despite personal interest in this,
>> involvement as an advisor to IANA since the late 1970s and early
>> 1980s, key roles in ICANN's creation and intermittent
>> involvement since (as liaison to the Board, advisor on multiple
>> issues (especially IDNs and i18n), and occasional consultant,
>> I'd not putting my name forward for this role.  The reasons are
>> ultimately connected to the remarks above: I have no funding for
>> an open-ended commitment that could involve significant time and
>> travel and I'm already overextended on work I feel I need to do
>> for the IETF.
>>
>>
>>
>> Especially with the added requirement for "diversity"
>
> Any discussion without historic view have a possibility to repeat old
> mistakes...
>
>
>

--=20
Christian de Larrinaga
FBCS, CITP, MCMA
-------------------------
@ FirstHand
-------------------------
+44 7989 386778
cdel@firsthand.net
-------------------------

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

<html><head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Type">=

</head><body style=3D"font-family: Optima; font-size: 12pt;"=20
bgcolor=3D"#FFFFFF" text=3D"#000000"><div style=3D"font-size:=20
12pt;font-family: Optima;"><span style=3D"font-family: Optima;"></span>It=
=20
would be a good thing for I* bodies to reflect on these points that John
 and Roger are making and provide meaningful support for individual=20
actors to engage effectively and in a balanced way or admit that they=20
are not multi stakeholder. <br><br><br><br>Christian <br><br>Roger=20
J=C3=B8rgensen wrote:<blockquote=20
cite=3D"mid:CAKFn1SFjoMPw3vSuOEQjYnWJU-i6okz_n=3Df28WUFXfyWj3T27w@mail.gm=
ail.com"
 type=3D"cite"><pre wrap=3D"">On Sat, Jun 7, 2014 at 5:49 PM, John C Klen=
sin <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:john-ietf@jck.com">=
&lt;john-ietf@jck.com&gt;</a> wrote:
&lt;snip&gt;
</pre><blockquote type=3D"cite"><pre wrap=3D"">Coordinating Committee hav=
e become open-ended.  Unlike many of
the appointing groups, the IETF is not in a position to
underwrite those costs, i.e., to cover costs of time-salary
and/or travel to the various meetings so as to spread those
costs across the relevant community.   The net effect is that
the only people who can plausibly represent the IETF are those
who:
</pre></blockquote><pre wrap=3D""><!---->
This part here made me think, can this issue about cost be the first
step on the way to a multi-stakeholder for Internet where only
the rich can participate? Rich as in having money AND time to travel
to endless meetings around the world? ... I hope not.

Personally I would like to get more involved but I can not see a way
to get more involved, have no way to fund it, or see how I can get
time to do more.


Except that, it's great work and good to see discussion  on the
subject (IANA transition) and future for the Internet.


&lt;snip&gt;
</pre><blockquote type=3D"cite"><pre wrap=3D"">p.s. Personal note: despit=
e personal interest in this,
involvement as an advisor to IANA since the late 1970s and early
1980s, key roles in ICANN's creation and intermittent
involvement since (as liaison to the Board, advisor on multiple
issues (especially IDNs and i18n), and occasional consultant,
I'd not putting my name forward for this role.  The reasons are
ultimately connected to the remarks above: I have no funding for
an open-ended commitment that could involve significant time and
travel and I'm already overextended on work I feel I need to do
for the IETF.



Especially with the added requirement for "diversity"
</pre></blockquote><pre wrap=3D""><!---->
Any discussion without historic view have a possibility to repeat old
mistakes...



</pre></blockquote><br><div class=3D"moz-signature">-- <br>Christian de=20
Larrinaga <br>
FBCS, CITP, MCMA <br>
-------------------------<br>
 <span style=3D"font-weight: bold;">@ FirstHand</span><br=20
style=3D"font-weight: bold;">
-------------------------<br>
+44 7989 386778<br>
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:cdel@firsthand.net">=
cdel@firsthand.net</a> <br>
-------------------------<br>
</div></div></body></html>

--------------040609000209060709030708--

--------------enigE985FBEB1D99C5F75A6E4F48
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCgAGBQJTleLmAAoJEO8NEF3l27YrEpoH/3/2ufQbCGTsxC9Lv2TbCSaM
gMW0tjSjh0PThzyRA/S61irwPGQ6srhYR7n+Zf7RkVzWE8pC4XLXjlna/dvv5cm2
T/BRWADVPTmMAl0kkeIKBepVHhVFBTSDz45KMgz+S070UfeBL4OR1yz+0+SxDmpa
Jv8a/d4HJK2cpP7rCZcP5mxggEvBqTUPWK/E8pvyeJW0KEMph4/F+Abu4C8reoIS
EvV7HyFVhAxQa3n618EYhZidSpSvCSU3yTPp3/owmJ+pYzo89vKvIeaIk5i8S5zF
Jp2J46XUc2XOhvzhLR0yE+hEF3q4dBAKEkiPJJ4kKuafG8cnaJ93D9HUHLkSNHE=
=HGKb
-----END PGP SIGNATURE-----

--------------enigE985FBEB1D99C5F75A6E4F48--


From nobody Mon Jun  9 12:39:42 2014
Return-Path: <prvs=12377f3c08=erik.josefsson@europarl.europa.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9061A0318 for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 12:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 vRaexqIbAxoP for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 12:39:34 -0700 (PDT)
Received: from smtp30.ep.europa.eu (smtp30.ep.europa.eu [136.173.162.208]) by ietfa.amsl.com (Postfix) with ESMTP id A538C1A0281 for <ietf@ietf.org>; Mon,  9 Jun 2014 12:39:32 -0700 (PDT)
Received: from UCEXBWP007.ep.parl.union.eu ([10.127.249.41]) by smtp30.ep.europa.eu (8.14.5/8.14.5) with ESMTP id s59JdA7P021972; Mon, 9 Jun 2014 21:39:10 +0200
Received: from UCEXBWP009.ep.parl.union.eu ([169.254.7.221]) by UCEXBWP007.ep.parl.union.eu ([169.254.5.25]) with mapi id 14.03.0174.001; Mon, 9 Jun 2014 21:39:10 +0200
From: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>
To: S Moonesamy <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RFC compliance and the European Parliament
Thread-Topic: RFC compliance and the European Parliament
Thread-Index: AQHPg9AKMbR5BfMda0GqrCJzC9NHGJto8XmggAAyWg0=
Date: Mon, 9 Jun 2014 19:39:09 +0000
Message-ID: <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu>,  <6.2.5.6.2.20140609081221.0b120268@resistor.net>
In-Reply-To: <6.2.5.6.2.20140609081221.0b120268@resistor.net>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.127.249.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/g-9NCFS3xhjSxX1IkTg_rEDdx60
Cc: "pawal@blipp.com" <pawal@blipp.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 19:39:37 -0000

Dear Mr Moonesamy,=0A=
Dear Mr Wallstr=F6m, =0A=
=0A=
Thank you for placing my call in the right context. I hope this list <ietf@=
ietf.org> allows me to reply without subscribing first. If not, please advi=
ce on how to subscribe.=0A=
=0A=
Assuming I was already subscribed, the problem is the following: If anyone =
else working in the EP is subscribed to this list with his @europarl mail a=
ddress, he will never receive this email. That's it.=0A=
=0A=
The request asks for the documentation of the reasons for this fact, or mor=
e precisely, access to all documents relating to the EP's policies and serv=
er settings for interacting with RFC 5321 compliant mailing lists.=0A=
=0A=
No such documentation has been provided by the EP.=0A=
=0A=
We are preparing a follow-up request here:=0A=
=0A=
http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance=0A=
=0A=
Grateful for any help and comments on the pad.=0A=
=0A=
Best regards.=0A=
=0A=
//Erik=0A=
=0A=
________________________________________=0A=
From: S Moonesamy [sm+ietf@elandsys.com]=0A=
Sent: Monday 9 June 2014 17:55=0A=
To: JOSEFSSON Erik; ietf@ietf.org=0A=
Subject: Re: RFC compliance and the European Parliament=0A=
=0A=
Hi Erik,=0A=
=0A=
I am copying this message to ietf@ietf.org instead of the perpass=0A=
mailing list as the question is not related to surveillance.=0A=
=0A=
At 04:00 09-06-2014, JOSEFSSON Erik wrote:=0A=
>I need help from the standards community with regards to=0A=
>RFC-compliance in the European Parliament.=0A=
>=0A=
>I reach out here because I believe you expect your work on improving=0A=
>the internet will be implemented, maybe in particular by public=0A=
>bodies we hold to a higher standard wrt transparency than others[0].=0A=
>=0A=
>In an Access to Documents request the EP just stated that=0A=
>"conformity with RFC-5321 section 3.9 is by nature outside EP's=0A=
>responsibilities" [1].=0A=
>=0A=
>Do you agree? Are there RFCs which correct implementation would, by=0A=
>nature, fall within the responsibilities of the EP?=0A=
=0A=
I read the reply.  In my opinion the text quoted (above) from the=0A=
reply conveys a different meaning.  My understanding of that part of=0A=
the reply is that mailing lists managed outside that email system is=0A=
outside EP's responsibility.  The question you asked could be stated=0A=
as follows:=0A=
=0A=
   Is it the responsibility of the EP to set the standards for email system=
s=0A=
   to adhere to?=0A=
=0A=
>Please find a link to our documentation of the particular issue with=0A=
>RFC-5321 section 3.9 below[2]=0A=
=0A=
The issue in that document is about whether the mail relays for=0A=
europarl.europa.eu can reject a message from a (external) mailing=0A=
list if the "From:" header contains "europarl.europa.eu" as the=0A=
domain part.  There is be a mail delivery problem if the external=0A=
email system implements and follows what is written in RFC 5321.=0A=
=0A=
Regards,=0A=
S. Moonesamy=0A=
=0A=


From nobody Mon Jun  9 13:27:31 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF151A02D9 for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 13:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 rOE-kA6nBm2F for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 13:27:27 -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 51C2A1A0212 for <ietf@ietf.org>; Mon,  9 Jun 2014 13:27:27 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.146]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s59KR4Sp021849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jun 2014 13:27:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402345637; x=1402432037; bh=DuuNCBydE4jt9OExfKvTos6TFZ2e4d+CmtdTf/RDtp8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=45duIbUFDxOGb2a2MujCxu8/ONYZOa4yXaYv+j6Mx23wJ0T/5RX//49iYNd6A46TR lRCmX5JRAt3KE3MNUCFccUDgjK6WGDP4L71Ls99PvnMdWxGwJ/URYMZ9updT0K3Tub WmlaCe4rnYb7rYjScXL9mkCSsE+DTw+LJQUHJqEY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402345637; x=1402432037; i=@elandsys.com; bh=DuuNCBydE4jt9OExfKvTos6TFZ2e4d+CmtdTf/RDtp8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zSwWYsUEq3SUH5YsoKp4E9MEizYL51v38Rp09NVjXGp1IrxACVA8BO+yn8P4hFbhv XjJ1peNpAizESpHxag6grL80h4X/ysEm+32tGw76X7cVrWcH7UJdQamSk5ACZQ39/Z 6C8DjfuRimt/W+5NwvRXGAG0WtG+rx3+2MVmTJag=
Message-Id: <6.2.5.6.2.20140609124714.0ae837b8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 09 Jun 2014 13:23:08 -0700
To: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: RFC compliance and the European Parliament
In-Reply-To: <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.par l.union.eu>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu> <6.2.5.6.2.20140609081221.0b120268@resistor.net> <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VxHrJNYZT_CZyB60gHNpTqksQmE
Cc: "pawal@blipp.com" <pawal@blipp.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 20:27:28 -0000

Hi Erik,
At 12:39 09-06-2014, JOSEFSSON Erik wrote:
>Thank you for placing my call in the right context. I hope this list 
><ietf@ietf.org> allows me to reply without subscribing first. If 
>not, please advice on how to subscribe.

Your (reply) message was also delivered by the ietf@ietf.org mailing 
list.  You can subscribe to the mailing list at 
https://www.ietf.org/mailman/listinfo/ietf

>Assuming I was already subscribed, the problem is the following: If 
>anyone else working in the EP is subscribed to this list with his 
>@europarl mail address, he will never receive this email. That's it.

Yes.

>The request asks for the documentation of the reasons for this fact, 
>or more precisely, access to all documents relating to the EP's 
>policies and server settings for interacting with RFC 5321 compliant 
>mailing lists.
>
>No such documentation has been provided by the EP.
>
>We are preparing a follow-up request here:
>
>http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance
>
>Grateful for any help and comments on the pad.

I am not a citizen of the European Union.  I hope that explains why I 
consider it as inappropriate of me to argue in favor or against EP's 
policies.  I'll comment about RFC compliance.  If there is an 
interoperability issue the first question that arises is what 
standards (in this case RFCs) does the server comply with.  It may be 
less difficult to get an answer if the question is clear, i.e. not 
discussing about mailing lists.

Regards,
S. Moonesamy 


From nobody Mon Jun  9 14:02:59 2014
Return-Path: <jaldorakyor@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4C21A018F for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 14:02:58 -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, SPF_PASS=-0.001] autolearn=ham
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 26p7Z2LwNJWY for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 14:02:55 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CBEA1A01C2 for <ietf@ietf.org>; Mon,  9 Jun 2014 14:02:54 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id z11so3437221lbi.13 for <ietf@ietf.org>; Mon, 09 Jun 2014 14:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=yP7Jx/ZIfw7fsDEw70OMaelukXlVKWg/XHc2l12I6+I=; b=RRDdWKOsYaGqAXUWc2eTrA9WZOL2PwFZo6lx7HybOLNvyWxyQTOj7WiT3O/oOwjgSf VXA1crlE/65Xvs1XU0F52u1HGYoaCu+3kaZebOMrMPmnfeYud13/1v3SsxuwSCERnvLH cKItcQgeraUAyIVHOCCgVvfUQf7bhvjAa1CRkRF+/SfS2FZetdxCfff7fFWsgBN4n0i4 BEJsMZ9OJUvZ6zvDKY04dqe0v35FC9EgizyFs4kU3lngmG2ic/oWm2oCfM7O2W25ql1g PUh/jEVQ6+ULzFDi4okF2D7SydFai0AGCS7f3Yfu5SKmVbnQjBNtVY74swgHKl8WaFUk 57HQ==
MIME-Version: 1.0
X-Received: by 10.152.29.133 with SMTP id k5mr3941203lah.44.1402347772161; Mon, 09 Jun 2014 14:02:52 -0700 (PDT)
Received: by 10.112.221.168 with HTTP; Mon, 9 Jun 2014 14:02:52 -0700 (PDT)
Date: Mon, 9 Jun 2014 17:02:52 -0400
Message-ID: <CAL+f+DftdXkWKtDrw=aKj_aq7hK5PGx073PP++kR8ux745QQ=Q@mail.gmail.com>
Subject: RE: RFC compliance and the European Parliament
From: Jaldora Kyor <jaldorakyor@gmail.com>
To: erik.josefsson@europarl.europa.eu, ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e0158c858cfc0f104fb6d883b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6-NVRPd5pmKtuRVTW5eKbLEtaWo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 21:02:58 -0000

--089e0158c858cfc0f104fb6d883b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Erik;

Well, the original message doesn't seem to clearly convey what you wanted
and the follow-up is simply unnecessarily rude.

The original request, as I read it, is for two things:

1. Documents relating to EP mail systems, policies, and server settings
relating to RFC 5321 sec. 3.9;
2. Documents relating to forecasts or plans relating to (1).

The response is "we have not found any documents that meet those criteria".
Now, they may or may not have any of those documents, but berating them for
'forget[ting] to address any of my requests' when as far as I can tell they
exactly answered the question you asked is more than a little unfair.

Reading the follow-up, though, I get the impression that what you asked for
is not really what you wanted to know and there has been a
miscommunication. On re-reading your follow up, it seems clear to me that
the original request was worded ambiguously and doesn't properly convey
what you want to obtain.

 What's wrong with saying, "Sorry, must have been a miscommunication. My
concern is that someone working in the EP with a @europarl mail address
won't receive mailing list messages. Can I have any documents relating to
the EP's mail handling policy and server settings and future changes to
same?"

-Jaldora



-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org <ietf-bounces@ietf.org>] On Behalf
Of JOSEFSSON Erik
Sent: June 9, 2014 3:39 PM
To: S Moonesamy; ietf@ietf.org
Cc: pawal@blipp.com
Subject: RE: RFC compliance and the European Parliament

Dear Mr Moonesamy,
Dear Mr Wallstr=C3=B6m,

Thank you for placing my call in the right context. I hope this list <
ietf@ietf.org> allows me to reply without subscribing first. If not, please
advice on how to subscribe.

Assuming I was already subscribed, the problem is the following: If anyone
else working in the EP is subscribed to this list with his @europarl mail
address, he will never receive this email. That's it.

The request asks for the documentation of the reasons for this fact, or
more precisely, access to all documents relating to the EP's policies and
server settings for interacting with RFC 5321 compliant mailing lists.

No such documentation has been provided by the EP.

We are preparing a follow-up request here:

http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance

Grateful for any help and comments on the pad.

Best regards.

//Erik

________________________________________
From: S Moonesamy [sm+ietf@elandsys.com]
Sent: Monday 9 June 2014 17:55
To: JOSEFSSON Erik; ietf@ietf.org
Subject: Re: RFC compliance and the European Parliament

Hi Erik,

I am copying this message to ietf@ietf.org instead of the perpass mailing
list as the question is not related to surveillance.

At 04:00 09-06-2014, JOSEFSSON Erik wrote:
>I need help from the standards community with regards to RFC-compliance
>in the European Parliament.
>
>I reach out here because I believe you expect your work on improving
>the internet will be implemented, maybe in particular by public bodies
>we hold to a higher standard wrt transparency than others[0].
>
>In an Access to Documents request the EP just stated that "conformity
>with RFC-5321 section 3.9 is by nature outside EP's responsibilities"
>[1].
>
>Do you agree? Are there RFCs which correct implementation would, by
>nature, fall within the responsibilities of the EP?

I read the reply.  In my opinion the text quoted (above) from the reply
conveys a different meaning.  My understanding of that part of the reply is
that mailing lists managed outside that email system is outside EP's
responsibility.  The question you asked could be stated as follows:

   Is it the responsibility of the EP to set the standards for email system=
s
   to adhere to?

>Please find a link to our documentation of the particular issue with
>RFC-5321 section 3.9 below[2]

The issue in that document is about whether the mail relays for
europarl.europa.eu can reject a message from a (external) mailing list if
the "From:" header contains "europarl.europa.eu" as the domain part.  There
is be a mail delivery problem if the external email system implements and
follows what is written in RFC 5321.

Regards,
S. Moonesamy

--089e0158c858cfc0f104fb6d883b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font><span style=3D"font-size:10pt">Erik;<br>

<br>

Well, the original message doesn&#39;t seem to clearly convey what you want=
ed and the follow-up is simply unnecessarily rude.<br>

<br>

The original request, as I read it, is for two things:<br>

<br>

1. Documents relating to EP mail systems, policies, and server settings rel=
ating to RFC 5321 sec. 3.9;<br>

2. Documents relating to forecasts or plans relating to (1).<br>

<br>

The response is &quot;we have not found any documents that meet those=20
criteria&quot;. Now, they may or may not have any of those documents, but=
=20
berating them for &#39;forget[ting] to address any of my requests&#39; when=
 as=20
far as I can tell they exactly answered the question
you asked is more than a little unfair.<br>

<br>

Reading the follow-up, though, I get the impression that what you asked=20
for is not really what you wanted to know and there has been a=20
miscommunication. On re-reading your follow up, it seems clear to me=20
that the original request was worded ambiguously and
doesn&#39;t properly convey what you want to obtain.<br>

<br>

=C2=A0What&#39;s wrong with saying, &quot;Sorry, must have been a miscommun=
ication. My
 concern is that someone working in the EP with a @europarl mail address
 won&#39;t receive mailing list messages. Can I have any documents relating=
=20
to the EP&#39;s mail handling policy and server
settings and future changes to same?&quot;<br>

<br>

-Jaldora<br><br></span></font><br><font><span style=3D"font-size:10pt"><br>

-----Original Message-----<br>

From: ietf [<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">mail=
to:ietf-bounces@ietf.org</a>] On Behalf Of JOSEFSSON Erik<br>

Sent: June 9, 2014 3:39 PM<br>

To: S Moonesamy; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>

Cc: <a href=3D"mailto:pawal@blipp.com">pawal@blipp.com</a><br>

Subject: RE: RFC compliance and the European Parliament<br>

<br>

Dear Mr Moonesamy,<br>

Dear Mr Wallstr=C3=B6m, <br>

<br>

Thank you for placing my call in the right context. I hope this list=20
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt; allows me to rep=
ly without subscribing first. If=20
not, please advice on how to subscribe.<br>

<br>

Assuming I was already subscribed, the problem is the following: If=20
anyone else working in the EP is subscribed to this list with his=20
@europarl mail address, he will never receive this email. That&#39;s it.<br=
>

<br>

The request asks for the documentation of the reasons for this fact, or=20
more precisely, access to all documents relating to the EP&#39;s policies=
=20
and server settings for interacting with RFC 5321 compliant mailing=20
lists.<br>

<br>

No such documentation has been provided by the EP.<br>

<br>

We are preparing a follow-up request here:<br>

<br>

<a href=3D"http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance" target=3D"=
_blank">http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance</a><br>

<br>

Grateful for any help and comments on the pad.<br>

<br>

Best regards.<br>

<br>

//Erik<br>

<br>

________________________________________<br>

From: S Moonesamy [<a href=3D"mailto:sm%2Bietf@elandsys.com">sm+ietf@elands=
ys.com</a>]<br>

Sent: Monday 9 June 2014 17:55<br>

To: JOSEFSSON Erik; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>

Subject: Re: RFC compliance and the European Parliament<br>

<br>

Hi Erik,<br>

<br>

I am copying this message to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a> instead of the perpass mailing list as the question is not related to =
surveillance.<br>

<br>

At 04:00 09-06-2014, JOSEFSSON Erik wrote:<br>

&gt;I need help from the standards community with regards to RFC-compliance=
 <br>

&gt;in the European Parliament.<br>

&gt;<br>

&gt;I reach out here because I believe you expect your work on improving <b=
r>

&gt;the internet will be implemented, maybe in particular by public bodies =
<br>

&gt;we hold to a higher standard wrt transparency than others[0].<br>

&gt;<br>

&gt;In an Access to Documents request the EP just stated that &quot;conform=
ity <br>

&gt;with RFC-5321 section 3.9 is by nature outside EP&#39;s responsibilitie=
s&quot; <br>

&gt;[1].<br>

&gt;<br>

&gt;Do you agree? Are there RFCs which correct implementation would, by <br=
>

&gt;nature, fall within the responsibilities of the EP?<br>

<br>

I read the reply.=C2=A0 In my opinion the text quoted (above) from the repl=
y=20
conveys a different meaning.=C2=A0 My understanding of that part of the rep=
ly
 is that mailing lists managed outside that email system is outside EP&#39;=
s
 responsibility.=C2=A0 The question you asked
could be stated as follows:<br>

<br>

=C2=A0=C2=A0 Is it the responsibility of the EP to set the standards for em=
ail systems<br>

=C2=A0=C2=A0 to adhere to?<br>

<br>

&gt;Please find a link to our documentation of the particular issue with<br=
>

&gt;RFC-5321 section 3.9 below[2]<br>

<br>

The issue in that document is about whether the mail relays for=20
<a href=3D"http://europarl.europa.eu">europarl.europa.eu</a> can reject a m=
essage from a (external) mailing list=20
if the &quot;From:&quot; header contains &quot;<a href=3D"http://europarl.e=
uropa.eu">europarl.europa.eu</a>&quot; as the domain part.=C2=A0
 There is be a mail delivery problem if the external
email system implements and follows what is written in RFC 5321.<br>

<br>

Regards,<br>

S. Moonesamy</span></font></div>

--089e0158c858cfc0f104fb6d883b--


From nobody Mon Jun  9 17:31:01 2014
Return-Path: <ryoo@etri.re.kr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7C521A0286; Mon,  9 Jun 2014 17:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 vDTQnI6wa1zM; Mon,  9 Jun 2014 17:30:52 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr [129.254.27.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 884F91A0274; Mon,  9 Jun 2014 17:30:51 -0700 (PDT)
Received: from SMTP1.etri.info (129.254.28.71) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 10 Jun 2014 09:30:44 +0900
Received: from SMTP2.etri.info ([169.254.2.160]) by SMTP1.etri.info ([10.2.6.30]) with mapi id 14.01.0355.002; Tue, 10 Jun 2014 09:30:45 +0900
From: Jeong Ryoo <ryoo@etri.re.kr>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-smp-requirements-05.txt> (Requirements for MPLS-TP Shared Mesh Protection)
Thread-Topic: Last Call: <draft-ietf-mpls-smp-requirements-05.txt> (Requirements for MPLS-TP Shared Mesh Protection)
Thread-Index: AQHPhEM3NGkTlg/PBk6h7c52YXMigA==
Date: Tue, 10 Jun 2014 00:30:44 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A2874391A@SMTP2.etri.info>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-new-displayname: SmVvbmcgUnlvbw==
x-originating-ip: [129.254.28.46]
Content-Type: multipart/alternative; boundary="_000_5B4A6CBE3924BB41A3BEE462A8E0B75A2874391ASMTP2etriinfo_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/I927ldrJeqsQbBKuUtz7VZRHLSY
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 00:30:58 -0000

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

QWRpcmFuLCB0aGFuayB5b3UgZm9yIHlvdXIgY29tbWVudHMuDQoNClRoZXkgY2VydGFpbmx5IGlt
cHJvdmUgdGhlIGRvY3VtZW50LCBhbmQgd2lsbCBiZSBpbmNvcnBvcmF0ZWQgaW4gdGhlIG5leHQg
dmVyc2lvbi4NCg0KQmVzdCByZWdhcmRzLA0KDQpKZW9uZy1kb25nDQoNCg0KDQoNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQrrs7Trgrgg7IKs656MIDogIkFkcmlhbiBGYXJyZWwi
IDxhZHJpYW5Ab2xkZG9nLmNvLnVrPg0K67O064K4IOuCoOynnCA6IDIwMTQtMDYtMDkgMjM6Mjc6
MDggKCArMDk6MDAgKQ0K67Cb64qUIOyCrOuejCA6IGlldGZAaWV0Zi5vcmcgPGlldGZAaWV0Zi5v
cmc+DQrssLjsobAgOiBtcGxzQGlldGYub3JnIDxtcGxzQGlldGYub3JnPg0K7KCc66qpIDogUkU6
IExhc3QgQ2FsbDogKFJlcXVpcmVtZW50cyBmb3IgTVBMUy1UUCBTaGFyZWQgTWVzaCBQcm90ZWN0
aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQoNCkhlcmUgYXJlIHNvbWUgY29tbWVudHMgZnJv
bSBteSByZXZpZXcgYXMgQUQgdGhhdCBuZWVkIHRvIGdldCBoYW5kbGVkIGFzIHBhcnQgb2YNCklF
VEYgbGFzdCBjYWxsLg0KDQpUaGFua3MsDQpBZHJpYW4NCg0KPT09DQoNCkNvdWxkIHlvdSBleHBh
bmQgInAycCIgd2hlcmUgaXQgaXMgZmlyc3QgdXNlZD8NCg0KLS0tDQoNClRoZSB2ZXJ5IGZpcnN0
IHNlbnRlbmNlIGlzIGhhcmQgdG8gcGFyc2UNCg0KTVBMUyB0cmFuc3BvcnQgbmV0d29ya3MgY2Fu
IGJlIGNoYXJhY3Rlcml6ZWQgYXMgYmVpbmcgYSBuZXR3b3JrIG9mDQpjb25uZWN0aW9ucyBiZXR3
ZWVuIG5vZGVzIHdpdGhpbiBhIG1lc2ggb2Ygbm9kZXMgYW5kIHRoZSBsaW5rcw0KYmV0d2VlbiB0
aGVtLg0KDQpNYXliZSB0cnkNCg0KVGhlIE1QTFMgVHJhbnNwb3J0IFByb2ZpbGUgKE1QTFMtVFAp
IHByb3ZpZGVzIHRvb2xzIHRvIGNvbnN0cnVjdCBhbmQNCm9wZXJhdGUgYSBzZXQgb2YgY29ubmVj
dGlvbnMgYmV0d2VlbiBub2RlcyBpbiBhbiBNUExTIG5ldHdvcmsuIFRoZQ0KTVBMUyBuZXR3b3Jr
IGlzIGEgbWVzaCBjb21wcmlzaW5nIG5vZGVzIGFuZCB0aGUgbGlua3MgYmV0d2VlbiB0aGVtLg0K
DQotLS0NCg0KSSB1bmRlcnN0YW5kIHRoYXQgeW91IHdhbnQgdG8gdXNlIFJGQyAyMTE5IGxhbmd1
YWdlIHRvIGNsYXJpZnkgdGhlDQpyZXF1aXJlbWVudHMsIGJ1dCBSRkMgMjExOSB3YXMgZGV2ZWxv
cGVkIGZvciBzcGVjaWZ5aW5nIHByb3RvY29scywgc28NCnRoZSBkaXJlY3QgcmVmZXJlbmNlIGFu
ZCBib2lsZXJwbGF0ZSBxdW90ZSBpcyBpbmNvbmdydW91cy4gSSBzdWdnZXN0DQp5b3UgdXNlIHRo
ZSBsYW5ndWFnZSBhcyBmb3VuZCBpbiBSRkMgNTY1NCwgdml6LjoNCg0KVGhlIGtleSB3b3JkcyAi
TVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KIlNI
T1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIsIGFuZCAiT1BUSU9OQUwi
IGluIHRoaXMNCmRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4g
UkZDIDIxMTkgW1JGQzIxMTldLg0KQWx0aG91Z2ggdGhpcyBkb2N1bWVudCBpcyBub3QgYSBwcm90
b2NvbCBzcGVjaWZpY2F0aW9uLCB0aGUgdXNlIG9mDQp0aGlzIGxhbmd1YWdlIGNsYXJpZmllcyB0
aGUgaW5zdHJ1Y3Rpb25zIHRvIHByb3RvY29sIGRlc2lnbmVycw0KcHJvZHVjaW5nIHNvbHV0aW9u
cyB0aGF0IHNhdGlzZnkgdGhlIHJlcXVpcmVtZW50cyBzZXQgb3V0IGluIHRoaXMNCmRvY3VtZW50
Lg0KDQotLS0NCg0KSW4gU2VjdGlvbiA1LjEgeW91IGhhdmUNCg0KdGhlIGNvbnRyb2wNCnByb3Rv
Y29sIFNIT1VMRCBOT1QgYmUgdXNlZCBhcyB0aGUgcHJpbWFyeSByZXNpbGllbmNlIG1lY2hhbmlz
bS4NCg0KSSBhZ3JlZSwgYnV0IEkgdGhpbmsgdGhhdCB0aGUgdGVybSAicHJpbWFyeSByZXNpbGll
bmNlIG1lY2hhbmlzbSIgbWF5IGJlDQp1bmRlciBkZWZpbmVkLiBDYW4geW91IGRvIGFueXRoaW5n
IHRvIGNsYXJpZnkgdGhpcz8gTWF5YmUuLi4NCg0KdGhlIGNvbnRyb2wNCnByb3RvY29sIFNIT1VM
RCBOT1QgYmUgdXNlZCBhcyB0aGUgcHJpbWFyeSBtZWNoYW5pc20gZm9yIGRldGVjdGluZyBvcg0K
cmVwb3J0aW5nIG5ldHdvcmsgZmFpbHVyZXMsIG9yIGZvciBpbml0aWF0aW5nIG9yIGNvb3JkaW5h
dGluZw0KcHJvdGVjdGlvbiBzd2l0Y2gtb3Zlci4gVGhhdCBpcywgaXQgU0hPVUxEIE5PVCBiZSB1
c2VkIGFzIHRoZQ0KcHJpbWFyeSByZXNpbGllbmNlIG1lY2hhbmlzbS4NCg0KPiAtLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBtcGxzIFttYWlsdG86bXBscy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgVGhlIElFU0cNCj4gU2VudDogMDkgSnVuZSAyMDE0IDE1OjEwDQo+
IFRvOiBJRVRGLUFubm91bmNlDQo+IENjOiBtcGxzQGlldGYub3JnDQo+IFN1YmplY3Q6IFttcGxz
XSBMYXN0IENhbGw6DQo+IChSZXF1aXJlbWVudHMgZm9yIE1QTFMtVFAgU2hhcmVkIE1lc2ggUHJv
dGVjdGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkMNCj4NCj4gVGhlIElFU0cgaGFzIHJlY2VpdmVk
IGEgcmVxdWVzdCBmcm9tIHRoZSBNdWx0aXByb3RvY29sIExhYmVsIFN3aXRjaGluZyBXRw0KPiAo
bXBscykgdG8gY29uc2lkZXIgdGhlIGZvbGxvd2luZyBkb2N1bWVudDoNCj4gLSAnUmVxdWlyZW1l
bnRzIGZvciBNUExTLVRQIFNoYXJlZCBNZXNoIFByb3RlY3Rpb24nDQo+IGFzIEluZm9ybWF0aW9u
YWwgUkZDDQo+DQo+IFRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4
dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cw0KPiBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlv
bi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gdGhlDQo+IGlldGZAaWV0Zi5v
cmcgbWFpbGluZyBsaXN0cyBieSAyMDE0LTA2LTIzLg0KDQo=

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBpZD0iZXpG
b3JtUHJvY19kaXYiIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiDqtbTrprwi
Pg0KPGRpdiBpZD0ibXNnYm9keSI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6IDIw
cHQiPkFkaXJhbiwgdGhhbmsgeW91IGZvciB5b3VyJm5ic3A7Y29tbWVudHMuPC9kaXY+DQo8ZGl2
IHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSJMSU5F
LUhFSUdIVDogMjBwdCI+VGhleSBjZXJ0YWlubHkgaW1wcm92ZSB0aGUmbmJzcDtkb2N1bWVudCwg
YW5kIHdpbGwgYmUgaW5jb3Jwb3JhdGVkIGluIHRoZSBuZXh0IHZlcnNpb24uPC9kaXY+DQo8ZGl2
IHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSJMSU5F
LUhFSUdIVDogMjBwdCI+QmVzdCByZWdhcmRzLDwvZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlH
SFQ6IDIwcHQiPiZuYnNwOzwvZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6IDIwcHQiPkpl
b25nLWRvbmc8L2Rpdj4NCjxkaXYgc3R5bGU9IkxJTkUtSEVJR0hUOiAyMHB0Ij48YnI+DQo8YnI+
DQombmJzcDs8L2Rpdj4NCjxkaXYgaWQ9Ik1haWxTaWduU2VudCIgc3R5bGU9IkxJTkUtSEVJR0hU
OiAyMHB0Ij48YnI+DQo8L2Rpdj4NCjxkaXYgaWQ9Ik9SR01BSUxfQ09OVEVOVCIgc3R5bGU9IkxJ
TkUtSEVJR0hUOiAyMHB0Ij4NCjxociB0YWJpbmRleD0iLTEiPg0KPGI+67O064K4IOyCrOuejCA6
IDwvYj4mcXVvdDtBZHJpYW4gRmFycmVsJnF1b3Q7ICZsdDthZHJpYW5Ab2xkZG9nLmNvLnVrJmd0
Ozxicj4NCjxiPuuztOuCuCDrgqDsp5wgOiA8L2I+MjAxNC0wNi0wOSAyMzoyNzowOCAoICYjNDM7
MDk6MDAgKTxicj4NCjxiPuuwm+uKlCDsgqzrnowgOiA8L2I+aWV0ZkBpZXRmLm9yZyAmbHQ7aWV0
ZkBpZXRmLm9yZyZndDs8YnI+DQo8Yj7ssLjsobAgOiA8L2I+bXBsc0BpZXRmLm9yZyAmbHQ7bXBs
c0BpZXRmLm9yZyZndDs8YnI+DQo8Yj7soJzrqqkgOiA8L2I+UkU6IExhc3QgQ2FsbDogPERSQUZU
LUlFVEYtTVBMUy1TTVAtUkVRVUlSRU1FTlRTLTA1LlRYVD4oUmVxdWlyZW1lbnRzIGZvciBNUExT
LVRQIFNoYXJlZCBNZXNoIFByb3RlY3Rpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDPGJyPg0KPGJy
Pg0KPGJyPg0KSGVyZSBhcmUgc29tZSBjb21tZW50cyBmcm9tIG15IHJldmlldyBhcyBBRCB0aGF0
IG5lZWQgdG8gZ2V0IGhhbmRsZWQgYXMgcGFydCBvZjxicj4NCklFVEYgbGFzdCBjYWxsLjxicj4N
Cjxicj4NClRoYW5rcyw8YnI+DQpBZHJpYW48YnI+DQo8YnI+DQo9PT08YnI+DQo8YnI+DQpDb3Vs
ZCB5b3UgZXhwYW5kICZxdW90O3AycCZxdW90OyB3aGVyZSBpdCBpcyBmaXJzdCB1c2VkPzxicj4N
Cjxicj4NCi0tLTxicj4NCjxicj4NClRoZSB2ZXJ5IGZpcnN0IHNlbnRlbmNlIGlzIGhhcmQgdG8g
cGFyc2U8YnI+DQo8YnI+DQpNUExTIHRyYW5zcG9ydCBuZXR3b3JrcyBjYW4gYmUgY2hhcmFjdGVy
aXplZCBhcyBiZWluZyBhIG5ldHdvcmsgb2Y8YnI+DQpjb25uZWN0aW9ucyBiZXR3ZWVuIG5vZGVz
IHdpdGhpbiBhIG1lc2ggb2Ygbm9kZXMgYW5kIHRoZSBsaW5rczxicj4NCmJldHdlZW4gdGhlbS4g
PGJyPg0KPGJyPg0KTWF5YmUgdHJ5PGJyPg0KPGJyPg0KVGhlIE1QTFMgVHJhbnNwb3J0IFByb2Zp
bGUgKE1QTFMtVFApIHByb3ZpZGVzIHRvb2xzIHRvIGNvbnN0cnVjdCBhbmQ8YnI+DQpvcGVyYXRl
IGEgc2V0IG9mIGNvbm5lY3Rpb25zIGJldHdlZW4gbm9kZXMgaW4gYW4gTVBMUyBuZXR3b3JrLiBU
aGU8YnI+DQpNUExTIG5ldHdvcmsgaXMgYSBtZXNoIGNvbXByaXNpbmcgbm9kZXMgYW5kIHRoZSBs
aW5rcyBiZXR3ZWVuIHRoZW0uPGJyPg0KPGJyPg0KLS0tPGJyPg0KPGJyPg0KSSB1bmRlcnN0YW5k
IHRoYXQgeW91IHdhbnQgdG8gdXNlIFJGQyAyMTE5IGxhbmd1YWdlIHRvIGNsYXJpZnkgdGhlIDxi
cj4NCnJlcXVpcmVtZW50cywgYnV0IFJGQyAyMTE5IHdhcyBkZXZlbG9wZWQgZm9yIHNwZWNpZnlp
bmcgcHJvdG9jb2xzLCBzbyA8YnI+DQp0aGUgZGlyZWN0IHJlZmVyZW5jZSBhbmQgYm9pbGVycGxh
dGUgcXVvdGUgaXMgaW5jb25ncnVvdXMuIEkgc3VnZ2VzdDxicj4NCnlvdSB1c2UgdGhlIGxhbmd1
YWdlIGFzIGZvdW5kIGluIFJGQyA1NjU0LCB2aXouOjxicj4NCjxicj4NClRoZSBrZXkgd29yZHMg
JnF1b3Q7TVVTVCZxdW90OywgJnF1b3Q7TVVTVCBOT1QmcXVvdDssICZxdW90O1JFUVVJUkVEJnF1
b3Q7LCAmcXVvdDtTSEFMTCZxdW90OywgJnF1b3Q7U0hBTEwgTk9UJnF1b3Q7LDxicj4NCiZxdW90
O1NIT1VMRCZxdW90OywgJnF1b3Q7U0hPVUxEIE5PVCZxdW90OywgJnF1b3Q7UkVDT01NRU5ERUQm
cXVvdDssICZxdW90O01BWSZxdW90OywgYW5kICZxdW90O09QVElPTkFMJnF1b3Q7IGluIHRoaXM8
YnI+DQpkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQyAy
MTE5IFtSRkMyMTE5XS48YnI+DQpBbHRob3VnaCB0aGlzIGRvY3VtZW50IGlzIG5vdCBhIHByb3Rv
Y29sIHNwZWNpZmljYXRpb24sIHRoZSB1c2Ugb2Y8YnI+DQp0aGlzIGxhbmd1YWdlIGNsYXJpZmll
cyB0aGUgaW5zdHJ1Y3Rpb25zIHRvIHByb3RvY29sIGRlc2lnbmVyczxicj4NCnByb2R1Y2luZyBz
b2x1dGlvbnMgdGhhdCBzYXRpc2Z5IHRoZSByZXF1aXJlbWVudHMgc2V0IG91dCBpbiB0aGlzPGJy
Pg0KZG9jdW1lbnQuPGJyPg0KPGJyPg0KLS0tPGJyPg0KPGJyPg0KSW4gU2VjdGlvbiA1LjEgeW91
IGhhdmU8YnI+DQo8YnI+DQp0aGUgY29udHJvbDxicj4NCnByb3RvY29sIFNIT1VMRCBOT1QgYmUg
dXNlZCBhcyB0aGUgcHJpbWFyeSByZXNpbGllbmNlIG1lY2hhbmlzbS48YnI+DQo8YnI+DQpJIGFn
cmVlLCBidXQgSSB0aGluayB0aGF0IHRoZSB0ZXJtICZxdW90O3ByaW1hcnkgcmVzaWxpZW5jZSBt
ZWNoYW5pc20mcXVvdDsgbWF5IGJlPGJyPg0KdW5kZXIgZGVmaW5lZC4gQ2FuIHlvdSBkbyBhbnl0
aGluZyB0byBjbGFyaWZ5IHRoaXM/IE1heWJlLi4uPGJyPg0KPGJyPg0KdGhlIGNvbnRyb2w8YnI+
DQpwcm90b2NvbCBTSE9VTEQgTk9UIGJlIHVzZWQgYXMgdGhlIHByaW1hcnkgbWVjaGFuaXNtIGZv
ciBkZXRlY3Rpbmcgb3I8YnI+DQpyZXBvcnRpbmcgbmV0d29yayBmYWlsdXJlcywgb3IgZm9yIGlu
aXRpYXRpbmcgb3IgY29vcmRpbmF0aW5nIDxicj4NCnByb3RlY3Rpb24gc3dpdGNoLW92ZXIuIFRo
YXQgaXMsIGl0IFNIT1VMRCBOT1QgYmUgdXNlZCBhcyB0aGUgPGJyPg0KcHJpbWFyeSByZXNpbGll
bmNlIG1lY2hhbmlzbS48YnI+DQo8YnI+DQomZ3Q7IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
PGJyPg0KJmd0OyBGcm9tOiBtcGxzIFttYWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBC
ZWhhbGYgT2YgVGhlIElFU0c8YnI+DQomZ3Q7IFNlbnQ6IDA5IEp1bmUgMjAxNCAxNToxMDxicj4N
CiZndDsgVG86IElFVEYtQW5ub3VuY2U8YnI+DQomZ3Q7IENjOiBtcGxzQGlldGYub3JnPGJyPg0K
Jmd0OyBTdWJqZWN0OiBbbXBsc10gTGFzdCBDYWxsOiA8RFJBRlQtSUVURi1NUExTLVNNUC1SRVFV
SVJFTUVOVFMtMDUuVFhUPjxicj4NCiZndDsgKFJlcXVpcmVtZW50cyBmb3IgTVBMUy1UUCBTaGFy
ZWQgTWVzaCBQcm90ZWN0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQzxicj4NCiZndDsgPGJyPg0K
Jmd0OyBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIE11bHRpcHJvdG9j
b2wgTGFiZWwgU3dpdGNoaW5nIFdHPGJyPg0KJmd0OyAobXBscykgdG8gY29uc2lkZXIgdGhlIGZv
bGxvd2luZyBkb2N1bWVudDo8YnI+DQomZ3Q7IC0gJ1JlcXVpcmVtZW50cyBmb3IgTVBMUy1UUCBT
aGFyZWQgTWVzaCBQcm90ZWN0aW9uJzxicj4NCiZndDsgPERSQUZULUlFVEYtTVBMUy1TTVAtUkVR
VUlSRU1FTlRTLTA1LlRYVD5hcyBJbmZvcm1hdGlvbmFsIFJGQzxicj4NCiZndDsgPGJyPg0KJmd0
OyBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtz
LCBhbmQgc29saWNpdHM8YnI+DQomZ3Q7IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQ
bGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGU8YnI+DQomZ3Q7IGlldGZAaWV0
Zi5vcmcgbWFpbGluZyBsaXN0cyBieSAyMDE0LTA2LTIzLjxicj4NCjxicj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5B4A6CBE3924BB41A3BEE462A8E0B75A2874391ASMTP2etriinfo_--


From nobody Mon Jun  9 22:41:08 2014
Return-Path: <prvs=1238146300=erik.josefsson@europarl.europa.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01641A03DB for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 22:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 hpVAz5DPywak for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 22:40:56 -0700 (PDT)
Received: from smtp35.ep.europa.eu (smtp35.ep.europa.eu [136.173.162.209]) by ietfa.amsl.com (Postfix) with ESMTP id 914C81A03D8 for <ietf@ietf.org>; Mon,  9 Jun 2014 22:40:54 -0700 (PDT)
Received: from UCEXBWP012.ep.parl.union.eu ([10.127.249.46]) by smtp35.ep.europa.eu (8.14.5/8.14.5) with ESMTP id s5A5epgi026418 for <ietf@ietf.org>; Tue, 10 Jun 2014 07:40:52 +0200
Received: from UCEXBWP009.ep.parl.union.eu ([169.254.7.221]) by UCEXBWP012.ep.parl.union.eu ([169.254.4.250]) with mapi id 14.03.0174.001; Tue, 10 Jun 2014 07:40:51 +0200
From: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RFC compliance and the European Parliament
Thread-Topic: RFC compliance and the European Parliament
Thread-Index: AQHPg9AKMbR5BfMda0GqrCJzC9NHGJto8XmggAAyWg3///5YgIAAsXy6
Date: Tue, 10 Jun 2014 05:40:51 +0000
Message-ID: <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu>,  <6.2.5.6.2.20140609081221.0b120268@resistor.net> <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu>, <b15d42cf2e134cc4bcc61177bd16884b@BY2PR04MB792.namprd04.prod.outlook.com>
In-Reply-To: <b15d42cf2e134cc4bcc61177bd16884b@BY2PR04MB792.namprd04.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.127.249.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_EzJWQkFmHi-RrHMNYeS8YCC0L8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 05:41:02 -0000

Dear Jaldora, dear Mr Moonesamy,=0A=
 =0A=
I am overwhelmed by your thoughtful feedback!  Thanks for taking time!!=0A=
=0A=
I have tried to edit the pad with your comments in mind.=0A=
=0A=
I do agree the request should not be rude. However, Regulation 1049/2001[0]=
 which provides the legal basis for the Access to Documents requests puts a=
n obligation on the institution to assist citizens exercising their rights,=
 in particular "If an application is not sufficiently precise, the institut=
ion shall ask the applicant to clarify the application and shall assist the=
 applicant in doing so [...]" (art 6.2).=0A=
=0A=
There is another request in the pipeline on transparency in EP security pro=
cedures that you might find interesting to follow (and maybe help with):=0A=
=0A=
http://www.asktheeu.org/en/request/man_in_the_middle_attack_on_the=0A=
http://pad.epfsug.eu/p/epfsug-eod-accessnetwork=0A=
=0A=
Taken together, these requests stem from concerns that despite our efforts[=
1] the EP "does not yet have the necessary means for secure electronic comm=
unications" (see point 4 in [2] below), which explains (but does not justif=
y) why I was reaching out on the perpass list.=0A=
=0A=
Again, thank you for your kind help!=0A=
=0A=
Best regards.=0A=
=0A=
//Erik=0A=
=0A=
=0A=
[0] http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=3DOJ:L:2001:145:0=
043:0048:EN:PDF=0A=
[1] https://wiki.debian.org/DebianParl/GreensEFA =0A=
[2] http://epfsug.eu/wws/arc/epfsug/2014-06/msg00039/DG-IPOL-and-DG-EXPO-pr=
iorities.pdf=0A=
=0A=
________________________________________=0A=
From: Alexander Burton-Vulovic [aburtonvulovic@siliconsteed.com] on behalf =
of jaldorakyor@gmail.com [jaldorakyor@gmail.com]=0A=
Sent: Monday 9 June 2014 22:59=0A=
To: JOSEFSSON Erik; S Moonesamy; ietf@ietf.org=0A=
Cc: pawal@blipp.com=0A=
Subject: RE: RFC compliance and the European Parliament=0A=
=0A=
Erik;=0A=
=0A=
Well, the original message doesn't seem to clearly convey what you wanted a=
nd the follow-up is simply unnecessarily rude.=0A=
=0A=
The original request, as I read it, is for two things:=0A=
=0A=
1. Documents relating to EP mail systems, policies, and server settings rel=
ating to RFC 5321 sec. 3.9;=0A=
2. Documents relating to forecasts or plans relating to (1).=0A=
=0A=
The response is "we have not found any documents that meet those criteria".=
 Now, they may or may not have any of those documents, but berating them fo=
r 'forget[ting] to address any of my requests' when as far as I can tell th=
ey exactly answered the question you asked is more than a little unfair.=0A=
=0A=
Reading the follow-up, though, I get the impression that what you asked for=
 is not really what you wanted to know and there has been a miscommunicatio=
n. On re-reading your follow up, it seems clear to me that the original req=
uest was worded ambiguously and doesn't properly convey what you want to ob=
tain.=0A=
=0A=
 What's wrong with saying, "Sorry, must have been a miscommunication. My co=
ncern is that someone working in the EP with a @europarl mail address won't=
 receive mailing list messages. Can I have any documents relating to the EP=
's mail handling policy and server settings and future changes to same?"=0A=
=0A=
-Jaldora=0A=
=0A=
=0A=
-----Original Message-----=0A=
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of JOSEFSSON Erik=0A=
Sent: June 9, 2014 3:39 PM=0A=
To: S Moonesamy; ietf@ietf.org=0A=
Cc: pawal@blipp.com=0A=
Subject: RE: RFC compliance and the European Parliament=0A=
=0A=
Dear Mr Moonesamy,=0A=
Dear Mr Wallstr=F6m,=0A=
=0A=
Thank you for placing my call in the right context. I hope this list <ietf@=
ietf.org> allows me to reply without subscribing first. If not, please advi=
ce on how to subscribe.=0A=
=0A=
Assuming I was already subscribed, the problem is the following: If anyone =
else working in the EP is subscribed to this list with his @europarl mail a=
ddress, he will never receive this email. That's it.=0A=
=0A=
The request asks for the documentation of the reasons for this fact, or mor=
e precisely, access to all documents relating to the EP's policies and serv=
er settings for interacting with RFC 5321 compliant mailing lists.=0A=
=0A=
No such documentation has been provided by the EP.=0A=
=0A=
We are preparing a follow-up request here:=0A=
=0A=
http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance=0A=
=0A=
Grateful for any help and comments on the pad.=0A=
=0A=
Best regards.=0A=
=0A=
//Erik=0A=
=0A=
________________________________________=0A=
From: S Moonesamy [sm+ietf@elandsys.com]=0A=
Sent: Monday 9 June 2014 17:55=0A=
To: JOSEFSSON Erik; ietf@ietf.org=0A=
Subject: Re: RFC compliance and the European Parliament=0A=
=0A=
Hi Erik,=0A=
=0A=
I am copying this message to ietf@ietf.org instead of the perpass mailing l=
ist as the question is not related to surveillance.=0A=
=0A=
At 04:00 09-06-2014, JOSEFSSON Erik wrote:=0A=
>I need help from the standards community with regards to RFC-compliance=0A=
>in the European Parliament.=0A=
>=0A=
>I reach out here because I believe you expect your work on improving=0A=
>the internet will be implemented, maybe in particular by public bodies=0A=
>we hold to a higher standard wrt transparency than others[0].=0A=
>=0A=
>In an Access to Documents request the EP just stated that "conformity=0A=
>with RFC-5321 section 3.9 is by nature outside EP's responsibilities"=0A=
>[1].=0A=
>=0A=
>Do you agree? Are there RFCs which correct implementation would, by=0A=
>nature, fall within the responsibilities of the EP?=0A=
=0A=
I read the reply.  In my opinion the text quoted (above) from the reply con=
veys a different meaning.  My understanding of that part of the reply is th=
at mailing lists managed outside that email system is outside EP's responsi=
bility.  The question you asked could be stated as follows:=0A=
=0A=
   Is it the responsibility of the EP to set the standards for email system=
s=0A=
   to adhere to?=0A=
=0A=
>Please find a link to our documentation of the particular issue with=0A=
>RFC-5321 section 3.9 below[2]=0A=
=0A=
The issue in that document is about whether the mail relays for europarl.eu=
ropa.eu can reject a message from a (external) mailing list if the "From:" =
header contains "europarl.europa.eu" as the domain part.  There is be a mai=
l delivery problem if the external email system implements and follows what=
 is written in RFC 5321.=0A=
=0A=
Regards,=0A=
S. Moonesamy=0A=
=0A=
=0A=


From nobody Tue Jun 10 00:07:21 2014
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109E61A0426 for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 Qh5ipwd37Ucg for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:07:16 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0861A0439 for <ietf@ietf.org>; Tue, 10 Jun 2014 00:07:16 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id cc10so1052442wib.3 for <ietf@ietf.org>; Tue, 10 Jun 2014 00:07:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3By4Lcdf/TZTfaxJYz0KII1t7dwx/W6RXr9BIoWJCvE=; b=EfDEUiqSh0sGDD0Mr2p61k/rwe+R2OARDX2j5AiJgmWUCcQqKC/b8D4Zv1nf3ceYvp uKWXZDTq2eTLsR9+L5wbBHiNGAbN50IqReUq5DyKi9ItS5Yg5LBLGUqL7PQWtaj72q9q ynFf9wcz6g9TVQkuJgmVHy6rrxECiZ8Z6jaPP7hO8DhZClc056nUfYLZKA4x2eLzoZBv 6OrMwgJwlHcbwvs/qaGVgtIuFahyyyxF+mUR1raPCmJ2IkTEwhBV96QHMTa9H9clppw+ 5WyTBn3H+tNSPtL4UQ9dZzdgwXFVOQlIT1Z2++6yqGl5bkbIZ1jy8SKJrBhedj2lPxzk /zbA==
MIME-Version: 1.0
X-Received: by 10.194.83.39 with SMTP id n7mr15125296wjy.58.1402384034748; Tue, 10 Jun 2014 00:07:14 -0700 (PDT)
Received: by 10.217.37.200 with HTTP; Tue, 10 Jun 2014 00:07:14 -0700 (PDT)
In-Reply-To: <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu> <6.2.5.6.2.20140609081221.0b120268@resistor.net> <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu> <b15d42cf2e134cc4bcc61177bd16884b@BY2PR04MB792.namprd04.prod.outlook.com> <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu>
Date: Tue, 10 Jun 2014 09:07:14 +0200
Message-ID: <CAKFn1SFw9t7wCpG9GLQhHf5endkvhnRS-mFHLTfghNN2=GDUkw@mail.gmail.com>
Subject: Re: RFC compliance and the European Parliament
From: =?UTF-8?Q?Roger_J=C3=B8rgensen?= <rogerj@gmail.com>
To: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4MXBaJqPsflpTU_j8iuqOCF2n_k
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 07:07:18 -0000

Hello Erik,

On Tue, Jun 10, 2014 at 7:40 AM, JOSEFSSON Erik
<erik.josefsson@europarl.europa.eu> wrote:
<snip>
> There is another request in the pipeline on transparency in EP security p=
rocedures that you might find interesting to follow (and maybe help with):
>
> http://www.asktheeu.org/en/request/man_in_the_middle_attack_on_the
> http://pad.epfsug.eu/p/epfsug-eod-accessnetwork
>
> Taken together, these requests stem from concerns that despite our effort=
s[1] the EP "does not yet have the necessary means for secure electronic co=
mmunications" (see point 4 in [2] below), which explains (but does not just=
ify) why I was reaching out on the perpass list.

*confused*

Do you ask IETF how you can make your communication more secure than
it is today?
Or do you ask us to make Internet more secure?



--=20

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no


From nobody Tue Jun 10 00:43:56 2014
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF65D1A044D for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.557
X-Spam-Level: 
X-Spam-Status: No, score=-100.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 A-Dawo63Gquu for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:43:48 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) (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 D11B11A01B1 for <ietf@ietf.org>; Tue, 10 Jun 2014 00:43:47 -0700 (PDT)
Received: from [IPv6:2a04:b900::1:b42c:f324:7e04:9407] ([IPv6:2a04:b900:0:1:b42c:f324:7e04:9407]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id s5A7gY69040280 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Jun 2014 09:42:35 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl s5A7gY69040280
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1402386223; bh=hBagI2T1ZWuv1JlusoWJEcOGBsG/KxkrOZtjNzjBbIk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=pmkgzOhc8mvEkCUUpM6kNUy37Pwq7U20AHbITW+dm0MgfSJKQpDiWYTWimyboOMxT eOLUaOnf7l6Hi6kgBDK8WLwY5paxi8jL5mbIlopK6vNUrBqzf4LqOGE+6ULlj8WuDB UcVmCQybifce/H7qqIPg/xXInAWxmTVRt8TmHcjc=
X-Authentication-Warning: open.nlnetlabs.nl: Host [IPv6:2a04:b900:0:1:b42c:f324:7e04:9407] claimed to be [IPv6:2a04:b900::1:b42c:f324:7e04:9407]
Content-Type: multipart/signed; boundary="Apple-Mail=_AAF219BE-81CD-421A-9918-1C2EDD036C28"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: RFC compliance and the European Parliament
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu>
Date: Tue, 10 Jun 2014 09:42:33 +0200
Message-Id: <264D6324-FCE0-456D-ABAD-7AECBD2A9FDB@NLnetLabs.nl>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu>,  <6.2.5.6.2.20140609081221.0b120268@resistor.net> <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu>, <b15d42cf2e134cc4bcc61177bd16884b@BY2PR04MB792.namprd04.prod.outlook.com> <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu>
To: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>
X-Mailer: Apple Mail (2.1878.2)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Tue, 10 Jun 2014 09:42:36 +0200 (CEST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o2eC2H6ypqB7p1i9G-wfilm9JHA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 07:43:51 -0000

--Apple-Mail=_AAF219BE-81CD-421A-9918-1C2EDD036C28
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


Erik, colleagues,

I am top-posting since I am not responding directly to anything in your =
message but on the general thread.

I=92d like to argue that this is not an IETF issue as such. Regardless =
whether Erik is trying to solve a real problem, this is only an IETF =
issue if there is a problem with the specification or the interpretation =
of the specs. If individual IETFers want to be involved Euro-citizens =
than that is fine (and if it comes to secure communication, a Good Thing =
TM), but lets try to keep the institution out of it. Remember that the =
IETF is about voluntary adoption and that we, as institution, do not do =
certification of implementations.

It is a thin line. Any question about what the IETF can do to make the =
Internet better is fine. In this case I am a bit concerned that the IETF =
could be perceived it is telling the EP how to run its business. Lets =
try to keep clear of the latter and keep the ball on the first.

=97Olaf=20
(no hats)



[ Nothing but rough context below]=20
On 10 jun. 2014, at 07:40, JOSEFSSON Erik =
<erik.josefsson@europarl.europa.eu> wrote:

> Dear Jaldora, dear Mr Moonesamy,
>=20
> I am overwhelmed by your thoughtful feedback!  Thanks for taking =
time!!
>=20
> I have tried to edit the pad with your comments in mind.
>=20
> I do agree the request should not be rude. However, Regulation =
1049/2001[0] which provides the legal basis for the Access to Documents =
requests puts an obligation on the institution to assist citizens =
exercising their rights, in particular "If an application is not =
sufficiently precise, the institution shall ask the applicant to clarify =
the application and shall assist the applicant in doing so [...]" (art =
6.2).
>=20
> There is another request in the pipeline on transparency in EP =
security procedures that you might find interesting to follow (and maybe =
help with):
>=20
> http://www.asktheeu.org/en/request/man_in_the_middle_attack_on_the
> http://pad.epfsug.eu/p/epfsug-eod-accessnetwork
>=20
> Taken together, these requests stem from concerns that despite our =
efforts[1] the EP "does not yet have the necessary means for secure =
electronic communications" (see point 4 in [2] below), which explains =
(but does not justify) why I was reaching out on the perpass list.
>=20
> Again, thank you for your kind help!
>=20
> Best regards.
>=20
> //Erik
>=20
>=20
> [0] =
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=3DOJ:L:2001:145:0043=
:0048:EN:PDF
> [1] https://wiki.debian.org/DebianParl/GreensEFA=20
> [2] =
http://epfsug.eu/wws/arc/epfsug/2014-06/msg00039/DG-IPOL-and-DG-EXPO-prior=
ities.pdf
>=20
> ________________________________________
> From: Alexander Burton-Vulovic [aburtonvulovic@siliconsteed.com] on =
behalf of jaldorakyor@gmail.com [jaldorakyor@gmail.com]
> Sent: Monday 9 June 2014 22:59
> To: JOSEFSSON Erik; S Moonesamy; ietf@ietf.org
> Cc: pawal@blipp.com
> Subject: RE: RFC compliance and the European Parliament
>=20
> Erik;
>=20
> Well, the original message doesn't seem to clearly convey what you =
wanted and the follow-up is simply unnecessarily rude.
>=20
> The original request, as I read it, is for two things:
>=20
> 1. Documents relating to EP mail systems, policies, and server =
settings relating to RFC 5321 sec. 3.9;
> 2. Documents relating to forecasts or plans relating to (1).
>=20
> The response is "we have not found any documents that meet those =
criteria". Now, they may or may not have any of those documents, but =
berating them for 'forget[ting] to address any of my requests' when as =
far as I can tell they exactly answered the question you asked is more =
than a little unfair.
>=20
> Reading the follow-up, though, I get the impression that what you =
asked for is not really what you wanted to know and there has been a =
miscommunication. On re-reading your follow up, it seems clear to me =
that the original request was worded ambiguously and doesn't properly =
convey what you want to obtain.
>=20
> What's wrong with saying, "Sorry, must have been a miscommunication. =
My concern is that someone working in the EP with a @europarl mail =
address won't receive mailing list messages. Can I have any documents =
relating to the EP's mail handling policy and server settings and future =
changes to same?"
>=20
> -Jaldora
>=20
>=20
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of JOSEFSSON Erik
> Sent: June 9, 2014 3:39 PM
> To: S Moonesamy; ietf@ietf.org
> Cc: pawal@blipp.com
> Subject: RE: RFC compliance and the European Parliament
>=20
> Dear Mr Moonesamy,
> Dear Mr Wallstr=F6m,
>=20
> Thank you for placing my call in the right context. I hope this list =
<ietf@ietf.org> allows me to reply without subscribing first. If not, =
please advice on how to subscribe.
>=20
> Assuming I was already subscribed, the problem is the following: If =
anyone else working in the EP is subscribed to this list with his =
@europarl mail address, he will never receive this email. That's it.
>=20
> The request asks for the documentation of the reasons for this fact, =
or more precisely, access to all documents relating to the EP's policies =
and server settings for interacting with RFC 5321 compliant mailing =
lists.
>=20
> No such documentation has been provided by the EP.
>=20
> We are preparing a follow-up request here:
>=20
> http://pad.epfsug.eu/p/epfsug-eod-emailrfccompliance
>=20
> Grateful for any help and comments on the pad.
>=20
> Best regards.
>=20
> //Erik
>=20
> ________________________________________
> From: S Moonesamy [sm+ietf@elandsys.com]
> Sent: Monday 9 June 2014 17:55
> To: JOSEFSSON Erik; ietf@ietf.org
> Subject: Re: RFC compliance and the European Parliament
>=20
> Hi Erik,
>=20
> I am copying this message to ietf@ietf.org instead of the perpass =
mailing list as the question is not related to surveillance.
>=20
> At 04:00 09-06-2014, JOSEFSSON Erik wrote:
>> I need help from the standards community with regards to =
RFC-compliance
>> in the European Parliament.
>>=20
>> I reach out here because I believe you expect your work on improving
>> the internet will be implemented, maybe in particular by public =
bodies
>> we hold to a higher standard wrt transparency than others[0].
>>=20
>> In an Access to Documents request the EP just stated that "conformity
>> with RFC-5321 section 3.9 is by nature outside EP's responsibilities"
>> [1].
>>=20
>> Do you agree? Are there RFCs which correct implementation would, by
>> nature, fall within the responsibilities of the EP?
>=20
> I read the reply.  In my opinion the text quoted (above) from the =
reply conveys a different meaning.  My understanding of that part of the =
reply is that mailing lists managed outside that email system is outside =
EP's responsibility.  The question you asked could be stated as follows:
>=20
>   Is it the responsibility of the EP to set the standards for email =
systems
>   to adhere to?
>=20
>> Please find a link to our documentation of the particular issue with
>> RFC-5321 section 3.9 below[2]
>=20
> The issue in that document is about whether the mail relays for =
europarl.europa.eu can reject a message from a (external) mailing list =
if the "From:" header contains "europarl.europa.eu" as the domain part.  =
There is be a mail delivery problem if the external email system =
implements and follows what is written in RFC 5321.
>=20
> Regards,
> S. Moonesamy
>=20
>=20
>=20


--Apple-Mail=_AAF219BE-81CD-421A-9918-1C2EDD036C28
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: Signature creating using GPG Tools.

iQIcBAEBAgAGBQJTlrbpAAoJEFRqER47aqpkQtQP/AqHiKsY6lwgy8pOMki7pjl/
sjKV8Dz3SouGQyhFPM3oawtRvaBgMl1S52RduWq11DCoPyyfYBw3q/4Lm3v+QIow
Lxm3W+F5CzU6LuY/J47pVL2KoMxFLt3P5cTARemUjaE8phZamv9R8eaP+PgBHVNM
HoRJDYaaXAYkBybhHsMZkQGmeow/Tvt1JowO7OZ7CkMxDXQTxtJ0MS9CToZbCkcm
Hn8zZ6m9XKdcdKxPWN2mxfVxorMy1guJfkavJIp9R4PRXA1J9XHKoU32WkjPCFxa
keqEH8Xqqe6e3355JQ3q3YYNsadVYld5C73uU4RNgyM/FJXGnr2Lj9op4DUbjb8O
w2PLNPreEU6ugZqTbqEGDk2vc+XaXfdzw9MrqH4j5UZLuBHittki96RPqy+I6cv6
LtApZpPwfyZe3mtKaD5dMSPc+aCu7sTCqu72wNTp6P5Ou8v6yzf+1J344oNCZZo/
jhLMr4vdZyR+UPA907zMsg7E7r+za0w9E6iV5KPVVJyYhsFhNJBj0MkAppduVmeN
6p1MEx1qLLcbT3hlLG/hsAE4gfcHXT7gnFor9Xwnm7TAxkyi9iARIRuB/6LfvLJl
q/qb55BzWvGUeTR3v1GcStP+0W+VhULFNqzEgUyhNSTGxVZl2muT3zPUi39utI5f
pr9Bbb/bSl83EiafuOyI
=bXXm
-----END PGP SIGNATURE-----

--Apple-Mail=_AAF219BE-81CD-421A-9918-1C2EDD036C28--


From nobody Tue Jun 10 00:44:10 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146201A0422; Tue, 10 Jun 2014 00:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 u-Gzz46CkGCU; Tue, 10 Jun 2014 00:43:51 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C13FD1A0424; Tue, 10 Jun 2014 00:43:49 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id u56so2547546wes.35 for <multiple recipients>; Tue, 10 Jun 2014 00:43:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=U1nIhWGrI4FR57IsTtBUTLElzNVqOpt/pL+TsFurS18=; b=FUgLSiOf/ilyTynEAbP5L2QRn0iw7c1kkD5HdKvmoDhDYRKqpAmYLpHJOHS0j3GKbM xVo8kbTb7TaVmDLT7itolkE+22pgZZ/zv/0IJFxHZM6dfnJqOq2zbuqcduVD4RMUVgrG mW6TYcJvaJYuB4dbBf7Ejx4AmzjtpxqEln3WTpmRF/SAiV8qjTGvNJe+XUvK5UU6rSVt Y6XfNapPGC3YZHQx76d3DI1s5zkt3a0GycrqdkwhiJE0L2esR164/hD6iwRH+XHcQ7HZ kedr5BXDv05VYZV8Ut9gPAKLWD/ZnAmbcYe64OZMlXmFfYycSx9OLdXrhxS+6s0KEhVD Vv/Q==
X-Received: by 10.180.38.107 with SMTP id f11mr26648702wik.59.1402386228088; Tue, 10 Jun 2014 00:43:48 -0700 (PDT)
Received: from [172.24.249.169] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id cy4sm19117174wib.5.2014.06.10.00.43.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 00:43:47 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [TLS] Last Call: <draft-ietf-tls-encrypt-then-mac-02.txt> (Encrypt-then-MAC for TLS and DTLS) to Proposed Standard
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com>
Date: Tue, 10 Jun 2014 10:43:45 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2262735E-0D70-42B4-8571-75B0A1EC6321@gmail.com>
References: <20140606145220.8187.67355.idtracker@ietfa.amsl.com> <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com>
To: "ietf\\@ietf.org" <ietf@ietf.org>, draft-ietf-tls-encrypt-then-mac.all@tools.ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Owdlewg1bA7fqJ8Euu8tZKcSWW0
Cc: TLS Mailing List <tls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 07:43:56 -0000

[adding draft address]

On Jun 7, 2014, at 4:15 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> Hi
>=20
> I=92ve read the draft and I have a  few comments:
>=20
> The motivation for this extension is not clear from the draft. The =
introduction says that the MAC-then-encrypt construction is =93no longer =
regarded as secure=94, and that it has been the subject of =93numerous =
security vulnerabilities and attacks=94. For the latter claim, there are =
no references given either in the document itself or in references. For =
the former two articles are cited.=20
> The first (reference [5]) is by Hugo Krawczyk. While that article =
shows a theoretical weakness of MAC-then-encrypt, it also finds that =
(quoting from the abstract) =93On the positive side we show that the =
authenticate-then-encrypt method is secure if the encryption method in =
use is either CBC mode (with an underlying secure block cipher) or a =
stream cipher (that xor the data with a random or pseudorandom pad).=94. =
It also concludes that =93the current practical implementations of [SSL] =
that use the above modes of encryption are safe=94. So this is not a =
great call for action.
> The second (reference [6]) is a better reference, but I=92m still =
missing a reference to anything practical or close to practical.
>=20
> The rationale for the mandate in section 3.1 is not clear to me. Sure, =
EtM is better than MtE, so renegotiating from MtE to EtM is a downgrade, =
but there is no mandate for implementations that are configured to =
support both algorithms to avoid downgrading from AES-256 to single DES, =
so why add this here?   Also, this section uses the terms =93state=94, =
=93status=94 and =93mechanism=94 seemingly interchangeably, and doesn=92t =
explain why changing mechanism during renegotiation is a SHOULD =
NOT-level issue, or how AEAD ciphers figure in this mandate.
>=20
> One more thing, this time a nit: informative reference number 7 =
describes a document as =93RFC xxxx=94. This is a reference to =
=93draft-bmoeller-tls-downgrade-scsv=94, which according to the =
datatracker is an individual draft that nobody=92s asked to publish yet. =
It should be referenced with the draft name as a work in progress. Since =
it=92s an informative reference, this won=92t block publication of this =
document.
>=20
> Yoav
>=20
> On Jun 6, 2014, at 5:52 PM, The IESG <iesg-secretary@ietf.org> wrote:
>=20
>>=20
>> The IESG has received a request from the Transport Layer Security WG
>> (tls) to consider the following document:
>> - 'Encrypt-then-MAC for TLS and DTLS'
>> <draft-ietf-tls-encrypt-then-mac-02.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2014-06-20. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  This document describes a means of negotiating the use of the
>>  encrypt-then-MAC security mechanism in place of TLS'/DTLS' existing
>>  MAC-then-encrypt one, which has been the subject of a number of
>>  security vulnerabilities over a period of many years.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>> ID nits found an Obsolete normative reference: "RFC 4366 (ref. '3')=20=

>> (Obsoleted by RFC 5246, RFC 6066)" which will be replaced.
>>=20
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>=20


From nobody Tue Jun 10 00:51:00 2014
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97041A04B7 for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.557
X-Spam-Level: 
X-Spam-Status: No, score=-100.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 Fa5zS8ycyx1x for <ietf@ietfa.amsl.com>; Tue, 10 Jun 2014 00:50:55 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) (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 7943F1A04A7 for <ietf@ietf.org>; Tue, 10 Jun 2014 00:50:55 -0700 (PDT)
Received: from office-dhcp-10.nlnetlabs.nl (office-dhcp-10.nlnetlabs.nl [185.49.140.170]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id s5A7onxW049571 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Jun 2014 09:50:51 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl s5A7onxW049571
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1402386652; bh=PCjehaiJo6L5pX0kwrzlen9O1K2J49hoihDiPyuaUQ0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=UsYsgA4aqbjEXUOZopQmoJvteEby26uz9oeVuht43BUb5TA8DvAHnNR4naXhCe0BR /WmGVGf/AS2KC78hMAytFtfMyd+zLfvYQYMhMTVr7Ro6tWntjidtTT2FetPUAJF+V8 6LWYLwH1koQ+DQT7f9PBSaISVgA3Rbc+KBClzDN8=
Content-Type: multipart/signed; boundary="Apple-Mail=_A58A16EA-9105-46D0-8ACA-E3F8E7A0B72C"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: RFC compliance and the European Parliament
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <264D6324-FCE0-456D-ABAD-7AECBD2A9FDB@NLnetLabs.nl>
Date: Tue, 10 Jun 2014 09:50:48 +0200
Message-Id: <8D3D04B4-D1B2-46AE-A8C5-65C91E954B07@NLnetLabs.nl>
References: <4B654B63C9A4614EA1F088B2490E8F3A069CEDAE@UCEXBWP009.ep.parl.union.eu>,  <6.2.5.6.2.20140609081221.0b120268@resistor.net> <4B654B63C9A4614EA1F088B2490E8F3A069CEEF6@UCEXBWP009.ep.parl.union.eu>, <b15d42cf2e134cc4bcc61177bd16884b@BY2PR04MB792.namprd04.prod.outlook.com> <4B654B63C9A4614EA1F088B2490E8F3A069CF0CC@UCEXBWP009.ep.parl.union.eu> <264D6324-FCE0-456D-ABAD-7AECBD2A9FDB@NLnetLabs.nl>
To: JOSEFSSON Erik <erik.josefsson@europarl.europa.eu>
X-Mailer: Apple Mail (2.1878.2)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Tue, 10 Jun 2014 09:50:51 +0200 (CEST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D8Hy_FmYD3mM7-MxCzQfkqnHYhU
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 07:50:57 -0000

--Apple-Mail=_A58A16EA-9105-46D0-8ACA-E3F8E7A0B72C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 10 jun. 2014, at 09:42, Olaf Kolkman <olaf@nlnetlabs.nl> wrote:
>=20
> It is a thin line. Any question about what the IETF can do to make the =
Internet better is fine. In this case I am a bit concerned that the IETF =
could be perceived it is telling the EP how to run its business. Lets =
try to keep clear of the latter and keep the ball on the first.
>=20


"keep the ball on the first.=94  I must be thinking about the Dutch =
potential in the forthcoming tournament to much.
Should have been something like:  Keep the eye on the first ball, or the =
eye on the ball, or concentrate on the first. You know what I mean ;-)=20=


=97Olaf

--Apple-Mail=_A58A16EA-9105-46D0-8ACA-E3F8E7A0B72C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: Signature creating using GPG Tools.

iQIcBAEBAgAGBQJTlrjZAAoJEFRqER47aqpkHxEP/jf+OEqBGgYMq7xZT20CYTgA
6D94Fz1hhDY3DbTekVt0A/FJSQqNjhQ3tWKMgEAU36blTNQxNY0gBkOx1Fw3moeJ
W/8IfcFTmZWV/d/qUyznoyIZqDwWUTsPnh4suPD4ALwntoRIiVcMoBpi3EZ8GNFe
JsbqyZ3LcvPxJ/KocW1wglyIp1SoWPfdIxDGYBi0VvJvDNdf6JcGFIDOIwC8E2Z5
pJfA3oIrT0jMI48gC/OkK1XlSrjrZLeYQKK0m0AXpk2UpZnXe8lL7uX9yffILxQd
xaivtkdc2r6bp37nQ2YBBlorxhGmpfP2QPyqlCQnFIhNpUGqXs0ExmTTFIlqojI4
CLoTHcySlKu3BZlGalf3RxhluJWHZ5k0a++AwrMsqC8VGSxiY1v1HwoILxt95Ltf
lFCe42IaeO3F7HH1pNIERELhEJYDVVFW256wyuvPE1hBo7oSTDypwcKZOXDLKfw3
SB0D1F0kBHA+1MeaVymMh3eUANJ2nla5H7/cE1IFtWchQZy/MDTbXFyZIagLiu3L
vuOZFwUdqg0x/LB0itRyc2IuCSwdBvn81jRSTQ0Dir5RxbWcAyMFLn7lbWgpxMn9
KFYsjGXOwjFojAI8pf/Sq2lc0Yy0FNfAwkPrpzAfJB31hkwHYeIbfFPpAQqSVEmG
yRVFze09ONUOSMdQKnZ8
=nVhh
-----END PGP SIGNATURE-----

--Apple-Mail=_A58A16EA-9105-46D0-8ACA-E3F8E7A0B72C--


From nobody Tue Jun 10 08:22:27 2014
Return-Path: <hugokraw@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7958E1A01AB; Tue, 10 Jun 2014 08:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 w3ND-kq8BfvE; Tue, 10 Jun 2014 08:02:04 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3151B27DF; Tue, 10 Jun 2014 08:02:04 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id j5so502710qaq.40 for <multiple recipients>; Tue, 10 Jun 2014 08:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=qMi+UPnYOSUMQROXc2H3z23kJykyHOPsViVKmMeSMsk=; b=syPkiklYLunINr73tHX0ZjwICtG1DD5fArk8ZsuxyjDGUphe65CB/dwf+ThIiZfJMx qfAc9p3sUuk+NLN82C3zUyHhWJvJ60v98fBc/XEg5ELy0SxhYO+29yQiTRb2P0zuUzw3 bn/cCXphi0XyH6QPg7FzmP6N+uK5Xx7JbCNREbCMXhjOx0ikwiU6ibUcCPDru1sFkWNI W/u3Pr8uaO9g/7KqC8PT05JusQ6izJ8BtrPVwwM3cuSVU8WNnq5YMrRz/ToOLTHRDN8j FvH8GJvbgQkeORDCvo7i04CeF9aO8tEznqULaPvUhkWrOHMnbn9ee8B0QuHup4HIa4zX kH/Q==
X-Received: by 10.140.48.1 with SMTP id n1mr13696772qga.107.1402412523157; Tue, 10 Jun 2014 08:02:03 -0700 (PDT)
MIME-Version: 1.0
Sender: hugokraw@gmail.com
Received: by 10.96.83.106 with HTTP; Tue, 10 Jun 2014 08:01:32 -0700 (PDT)
In-Reply-To: <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com>
References: <20140606145220.8187.67355.idtracker@ietfa.amsl.com> <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com>
From: Hugo Krawczyk <hugo@ee.technion.ac.il>
Date: Tue, 10 Jun 2014 11:01:32 -0400
X-Google-Sender-Auth: UgyLiWocyaQ8Cvms9qXhc7IGS_A
Message-ID: <CADi0yUN+A7QGZLeSDDXMLhK6mr4O09rGr0ZJy6AafPVSQJX1tA@mail.gmail.com>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-encrypt-then-mac-02.txt> (Encrypt-then-MAC for TLS and DTLS) to Proposed Standard
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a11350eac458a1f04fb7c9c02
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_8jXg4t-OKJ014O9gzUJCOze2Gc
X-Mailman-Approved-At: Tue, 10 Jun 2014 08:22:22 -0700
Cc: "ietf\\@ietf.org" <ietf@ietf.org>, TLS Mailing List <tls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 15:02:06 -0000

--001a11350eac458a1f04fb7c9c02
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The technical results in my 2001 paper are correct but the conclusion
regarding SSL/TLS is wrong. I assumed that TLS was using fresh IVs and that
the MAC was computed on the encoded plaintext, i.e. Encode-Mac-Encrypt
while TLS is doing Mac-Encode-Encrypt which is exactly what my theoretical
example shows is insecure. The later padding attacks showed that the
theoretical example of insecurity had a very practical instantiation in
TLS.  While the paper shows correctly that MAC-then-Encrypt can be secure
with both CBC and stream ciphers, it also shows that it requires a LOT of
care about encoding - it turned out that TLS/SSL was not doing that. So if
you want to keep Mac-then-Encrypt then you must change the encoding as well
as how you apply the MAC. Changing to Encrypt-then-MAC is a much safer
solution.

Hugo




On Sat, Jun 7, 2014 at 9:15 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> Hi
>
> I=E2=80=99ve read the draft and I have a  few comments:
>
> The motivation for this extension is not clear from the draft. The
> introduction says that the MAC-then-encrypt construction is =E2=80=9Cno l=
onger
> regarded as secure=E2=80=9D, and that it has been the subject of =E2=80=
=9Cnumerous security
> vulnerabilities and attacks=E2=80=9D. For the latter claim, there are no =
references
> given either in the document itself or in references. For the former two
> articles are cited.
> The first (reference [5]) is by Hugo Krawczyk. While that article shows a
> theoretical weakness of MAC-then-encrypt, it also finds that (quoting fro=
m
> the abstract) =E2=80=9COn the positive side we show that the
> authenticate-then-encrypt method is secure if the encryption method in us=
e
> is either CBC mode (with an underlying secure block cipher) or a stream
> cipher (that xor the data with a random or pseudorandom pad).=E2=80=9D. I=
t also
> concludes that =E2=80=9Cthe current practical implementations of [SSL] th=
at use the
> above modes of encryption are safe=E2=80=9D. So this is not a great call =
for action.
> The second (reference [6]) is a better reference, but I=E2=80=99m still m=
issing a
> reference to anything practical or close to practical.
>
> The rationale for the mandate in section 3.1 is not clear to me. Sure, Et=
M
> is better than MtE, so renegotiating from MtE to EtM is a downgrade, but
> there is no mandate for implementations that are configured to support bo=
th
> algorithms to avoid downgrading from AES-256 to single DES, so why add th=
is
> here?   Also, this section uses the terms =E2=80=9Cstate=E2=80=9D, =E2=80=
=9Cstatus=E2=80=9D and =E2=80=9Cmechanism=E2=80=9D
> seemingly interchangeably, and doesn=E2=80=99t explain why changing mecha=
nism
> during renegotiation is a SHOULD NOT-level issue, or how AEAD ciphers
> figure in this mandate.
>
> One more thing, this time a nit: informative reference number 7 describes
> a document as =E2=80=9CRFC xxxx=E2=80=9D. This is a reference to
> =E2=80=9Cdraft-bmoeller-tls-downgrade-scsv=E2=80=9D, which according to t=
he datatracker is
> an individual draft that nobody=E2=80=99s asked to publish yet. It should=
 be
> referenced with the draft name as a work in progress. Since it=E2=80=99s =
an
> informative reference, this won=E2=80=99t block publication of this docum=
ent.
>
> Yoav
>
> On Jun 6, 2014, at 5:52 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> >
> > The IESG has received a request from the Transport Layer Security WG
> > (tls) to consider the following document:
> > - 'Encrypt-then-MAC for TLS and DTLS'
> >  <draft-ietf-tls-encrypt-then-mac-02.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2014-06-20. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >   This document describes a means of negotiating the use of the
> >   encrypt-then-MAC security mechanism in place of TLS'/DTLS' existing
> >   MAC-then-encrypt one, which has been the subject of a number of
> >   security vulnerabilities over a period of many years.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then-mac/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> > ID nits found an Obsolete normative reference: "RFC 4366 (ref. '3')
> > (Obsoleted by RFC 5246, RFC 6066)" which will be replaced.
> >
> > _______________________________________________
> > TLS mailing list
> > TLS@ietf.org
> > https://www.ietf.org/mailman/listinfo/tls
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

--001a11350eac458a1f04fb7c9c02
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:small">The technical results in my 2001 paper are corr=
ect but the conclusion regarding SSL/TLS is wrong. I assumed that TLS was u=
sing fresh IVs and that the MAC was computed on the encoded plaintext, i.e.=
 Encode-Mac-Encrypt while TLS is doing Mac-Encode-Encrypt which is exactly =
what my theoretical example shows is insecure. The later padding attacks sh=
owed that the theoretical example of insecurity had a very practical instan=
tiation in TLS.=C2=A0 While the paper shows correctly that MAC-then-Encrypt=
 can be secure with both CBC and stream ciphers, it also shows that it requ=
ires a LOT of care about encoding - it turned out that TLS/SSL was not doin=
g that. So if you want to keep Mac-then-Encrypt then you must change the en=
coding as well as how you apply the MAC. Changing to Encrypt-then-MAC is a =
much safer solution.<br>

<br></div><div class=3D"gmail_default" style=3D"font-family:verdana,sans-se=
rif;font-size:small">Hugo<br><br></div><div class=3D"gmail_default" style=
=3D"font-family:verdana,sans-serif;font-size:small"><br></div></div><div cl=
ass=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">On Sat, Jun 7, 2014 at 9:15 AM, Yoav Nir=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_bl=
ank">ynir.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">

Hi<br>
<br>
I=E2=80=99ve read the draft and I have a =C2=A0few comments:<br>
<br>
The motivation for this extension is not clear from the draft. The introduc=
tion says that the MAC-then-encrypt construction is =E2=80=9Cno longer rega=
rded as secure=E2=80=9D, and that it has been the subject of =E2=80=9Cnumer=
ous security vulnerabilities and attacks=E2=80=9D. For the latter claim, th=
ere are no references given either in the document itself or in references.=
 For the former two articles are cited.<br>


The first (reference [5]) is by Hugo Krawczyk. While that article shows a t=
heoretical weakness of MAC-then-encrypt, it also finds that (quoting from t=
he abstract) =E2=80=9COn the positive side we show that the authenticate-th=
en-encrypt method is secure if the encryption method in use is either CBC m=
ode (with an underlying secure block cipher) or a stream cipher (that xor t=
he data with a random or pseudorandom pad).=E2=80=9D. It also concludes tha=
t =E2=80=9Cthe current practical implementations of [SSL] that use the abov=
e modes of encryption are safe=E2=80=9D. So this is not a great call for ac=
tion.<br>


The second (reference [6]) is a better reference, but I=E2=80=99m still mis=
sing a reference to anything practical or close to practical.<br>
<br>
The rationale for the mandate in section 3.1 is not clear to me. Sure, EtM =
is better than MtE, so renegotiating from MtE to EtM is a downgrade, but th=
ere is no mandate for implementations that are configured to support both a=
lgorithms to avoid downgrading from AES-256 to single DES, so why add this =
here? =C2=A0 Also, this section uses the terms =E2=80=9Cstate=E2=80=9D, =E2=
=80=9Cstatus=E2=80=9D and =E2=80=9Cmechanism=E2=80=9D seemingly interchange=
ably, and doesn=E2=80=99t explain why changing mechanism during renegotiati=
on is a SHOULD NOT-level issue, or how AEAD ciphers figure in this mandate.=
<br>


<br>
One more thing, this time a nit: informative reference number 7 describes a=
 document as =E2=80=9CRFC xxxx=E2=80=9D. This is a reference to =E2=80=9Cdr=
aft-bmoeller-tls-downgrade-scsv=E2=80=9D, which according to the datatracke=
r is an individual draft that nobody=E2=80=99s asked to publish yet. It sho=
uld be referenced with the draft name as a work in progress. Since it=E2=80=
=99s an informative reference, this won=E2=80=99t block publication of this=
 document.<br>


<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jun 6, 2014, at 5:52 PM, The IESG &lt;<a href=3D"mailto:iesg-secretary@i=
etf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; The IESG has received a request from the Transport Layer Security WG<b=
r>
&gt; (tls) to consider the following document:<br>
&gt; - &#39;Encrypt-then-MAC for TLS and DTLS&#39;<br>
&gt; =C2=A0&lt;draft-ietf-tls-encrypt-then-mac-02.txt&gt; as Proposed Stand=
ard<br>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
14-06-20. Exceptionally, comments may be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In=
 either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt; =C2=A0 This document describes a means of negotiating the use of the<b=
r>
&gt; =C2=A0 encrypt-then-MAC security mechanism in place of TLS&#39;/DTLS&#=
39; existing<br>
&gt; =C2=A0 MAC-then-encrypt one, which has been the subject of a number of=
<br>
&gt; =C2=A0 security vulnerabilities over a period of many years.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then=
-mac/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-tls-enc=
rypt-then-mac/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tls-encrypt-then=
-mac/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-=
tls-encrypt-then-mac/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt; ID nits found an Obsolete normative reference: &quot;RFC 4366 (ref. &#=
39;3&#39;)<br>
&gt; (Obsoleted by RFC 5246, RFC 6066)&quot; which will be replaced.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; TLS mailing list<br>
&gt; <a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tls" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/tls</a><br>
<br>
_______________________________________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/tls</a><br>
</div></div></blockquote></div><br></div>

--001a11350eac458a1f04fb7c9c02--


From nobody Tue Jun 10 08:22:55 2014
Return-Path: <jari.arkko@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADD51A0070; Tue, 10 Jun 2014 00:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 9Cji65q-Y-GV; Tue, 10 Jun 2014 00:14:48 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA3DA1A04A7; Tue, 10 Jun 2014 00:14:47 -0700 (PDT)
X-AuditID: c1b4fb2d-f79776d000001085-00-5396b065f85d
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id AD.CE.04229.560B6935; Tue, 10 Jun 2014 09:14:46 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.92) with Microsoft SMTP Server id 14.3.174.1; Tue, 10 Jun 2014 09:14:45 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 6ADEC110206; Tue, 10 Jun 2014 10:14:45 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 130915766D;	Tue, 10 Jun 2014 10:14:52 +0300 (EEST)
Received: from [IPv6:::1] (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 1ACFB57045;	Tue, 10 Jun 2014 10:14:50 +0300 (EEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_38985F33-13C4-4D36-A14D-4FE73FC0983A"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-idr-bgp-enhanced-route-refresh-06
From: Jari Arkko <jari.arkko@ericsson.com>
In-Reply-To: <CFB76C32.752A3%keyupate@cisco.com>
Date: Tue, 10 Jun 2014 10:14:42 +0300
Message-ID: <D5E2F74F-BAB1-4C4D-90F3-AF1A8455924D@ericsson.com>
References: <CFB76C32.752A3%keyupate@cisco.com>
To: "Keyur Patel (keyupate)" <keyupate@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsUyM+JvjW7ahmnBBocXMFv8PnecyeLqq88s Fs82zmexaNx6ns3i3lkmB1aPjmVpHlN+b2T1WLLkJ5PHl8uf2QJYorhsUlJzMstSi/TtErgy bu7bzVTw17pixaYGpgbGBosuRk4OCQETieeP7zNC2GISF+6tZ+ti5OIQEjjKKLHs9CZWCGcD o0T7iU3MEM5eRomGz//ZIZx1jBI9k75AOfMYJdbNvQPmMAtMYZSYN38nC8hkXgEDiXWLj4Ft ERaIkGi/sx3MZhPQkti4fAEbiM0JVHPz7BOgHRwcLAKqEpN6TSHmvGWUmPppGxvEHHuJA0v7 wGwhAX2JzuPXmEBsEQFDiZMz3rNCfCEvMaP9BDuErSZx9RzI3SD1KhK3/p5lm8AoMgvZfbOQ 3AdiMwtoSyxb+JoZwjaQeNr5ihXCNpV4ffQjVI21xIxfB9kgbEWJKd0P2Rcwsq9iFC1OLS7O TTcy1kstykwuLs7P08tLLdnECIzIg1t+6+5gXP3a8RCjAAejEg+vwrepwUKsiWXFlbmHGKU5 WJTEeS9pVAcLCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYGRX/iS/9VhCXaXFrUUn3NgfeagX iB7MPVt9e8kqrfqTO/rL1GcYvfl+5yVz7qmJW24qfjx+dNGuIpcb25Q+VYZ+KWV6Wf2p4fi1 wBnTJAtWnd2t4sBYaFtqseOEuvuhtP6Crfsf75q4N+1zmRa7FaO8uXneiwsbl7UvXL5r5uej GemmTz52f7+kxFKckWioxVxUnAgAF0ojZakCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QHqDlDUrChPPr_z1M77TOu_cmw8
X-Mailman-Approved-At: Tue, 10 Jun 2014 08:22:51 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org" <draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 07:14:50 -0000

--Apple-Mail=_38985F33-13C4-4D36-A14D-4FE73FC0983A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Peter, Keyur,

First: thank you Peter for your review.

I am looking at the changes from the reviewed draft to the most recent =
one:

    =
http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-idr-bgp-enhanced-route-ref=
resh-06.txt&url2=3Ddraft-ietf-idr-bgp-enhanced-route-refresh-09.txt

and I think they cover Peter=92s third item (receiving an EoRR before =
receiving a BoRR).  The second item, is I think, clear without any =
changes. On the first item, I think the situation is also clear when =
looking at both Sections 3.2 and 6.

Thanks, all,

Jari

>> Page 3, Section 3.2: the set of available values is enumerated.  Is =
the
>> encoding format of these values understood from other context?  Older =
BGP
>> specifications seem to give guidance such as "unsigned integer" at a
>> minimum.
>=20
> #Keyur: Yes.
>=20
>>=20
>> Page 3, Section 3.2, table of values: the value is a "should" in RFC =
2918.
>> That RFC indicated that it was to be ignored by recipients.  Now that
>> values
>> will actually matter, is there any concern about senders that don't =
abide
>> by
>> the "should" clause in RFC 2918?
>=20
> #Keyur: Yes. This functionality is controlled using BGP capabilities.
>=20
>>=20
>> Page 4, 1st full paragraph, 3rd sentence: the behavior for receipt of =
a
>> BoRR
>> is described.  What happens if an EoRR is somehow received prior to
>> receipt
>> of a BoRR?  Is it just ignored?  Or should an error notification be
>> returned?
>=20
> #Keyur: It would be a no-op operation. 07 version of draft covers it.


--Apple-Mail=_38985F33-13C4-4D36-A14D-4FE73FC0983A
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINaDCCBEUw
ggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVs
aWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4X
DTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv
1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqT
u3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMc
CYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUb
Az2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB
/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRh
cC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2
MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNV
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb
8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXI
v6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzY
FSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67
OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3k
MXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OY
CMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAw
OjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDgg
VjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVy
YSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5D
uVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe
1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF4
6H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjgh
XYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGj
ggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7ga
YqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0F
BgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7Bgcq
hXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20w
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vv
bi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkww
DgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUE
kUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDC
fkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6b
KuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHn
tP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPd
OI5GtDYPMIIEqjCCA5KgAwIBAgIQTyXs3vXto5joAjtwrbnc3jANBgkqhkiG9w0BAQUFADA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxMB4X
DTEzMDMwNDEzMjUyMVoXDTE2MDMwNDEzMjUxOVowYjERMA8GA1UECgwIRXJpY3Nzb24xEzARBgNV
BAMMCkphcmkgQXJra28xEDAOBgNVBAUTB2xtZmphYXIxJjAkBgkqhkiG9w0BCQEWF2phcmkuYXJr
a29AZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhwriyJIY5Bbz
yZrfnFAjWFLMNc6O6Z6dw5HqexTVyrUymDobuwcFtGl3n+yc6tYcvzM85LJMotJlOJH4NHEqClEc
iMw+gFvN17PXxM2aAPuv1ZUL1wSdQ9dS94zxQEQuh4Myyfy+eqvrEBkzZaDPu4Evz6xsmCYPYSZP
t4Bo6zbwQqkRvSQUO659ytmlyiPOiWN6wxEpwwO43LEw12xFrVSOQw3AG8ULW/xHbQvInuyWQdBC
ug/1n6IJETsMWSrLFnk888IjABXKkmq42EG6RQ0BWLw8lAQwTju7rsDF9HrcTYBcu9z2u/d4cSgH
P9SkRncRm68xrt7bD2RhPf3rkQIDAQABo4IBgzCCAX8wgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3
aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vRXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZx
bGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29tL2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFs
JTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2Uw
IgYDVR0RBBswGYEXamFyaS5hcmtrb0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEw
MTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0O
BBYEFLk/k+8oySkNxYm0GyPaFaKSRQufMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCb
MA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEAECF65IiGH7GS+EEHre+itv2wv0OQ
Z68DWR6G9IqMkBgb8dj6JcfFsu+9p8ID1e1L/0ybeTwz1t4IPhuOuWBPohj5irYiCBJkIokUr09B
rWPyxfBrSoZ+uXVWfmZSdp15pWlEnHhuGuJkZ2a0MKrj+OEM9qfQR5Cvdlmx5PvsIhFkAFcZWldI
xBwHsEeSoGJbVvvNImiY6M27u6rhuR8HanXVdcW4B8gK489LutxKhyhT9QDFUhmyWk2qYCUJgwM/
w44sLz8tv95jDbJxAR/aOwdwF3fQgj8VB5Xwvdn6B0PhfEcd3Ju4yUz6HE6ELZWG4ruE2haUCOn4
8WStKZ/RPDGCApMwggKPAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQTyXs3vXto5joAjtwrbnc3jAJBgUrDgMCGgUAoIIBGzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA2MTAwNzE0NDNaMCMG
CSqGSIb3DQEJBDEWBBTve3TbAbHbOZEzDRfTLU/387LDFDBcBgkrBgEEAYI3EAQxTzBNMDkxETAP
BgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l
7N717aOY6AI7cK253N4wXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l7N717aOY6AI7cK253N4wDQYJ
KoZIhvcNAQEBBQAEggEAJx9Ci6xj+Rc9DYjwgPa2i4ywg67rCdD8+ZJfv4m9cU0ujZa6w8Gj5C/H
jYP+m+2XmqwLy3aghb3EQgkxE1GPE7gbnpDtlrJEgu769j8Zok0JDeYMz2UBzYtSkrJJKp3ZF76U
3Tl9+NJYFUX6GSBTlSFKUHijPb7F9mYLxwvKuOA04xkJPY8B7I9LbmWyZkbPlShkjdxbD0yrcX9i
7DPEIVH3cUHwzmno/5bsIpofZ4GE/w7SaGOyJGtyMc7H26s3HGK/U2fztgCZSWE/UDHWF0JeTToQ
wHfzOKSmgvOlXKs/NfgIWSwn25aXbNw4mwWUPQ2rDaj73WBoSFr91g0M3gAAAAAAAA==

--Apple-Mail=_38985F33-13C4-4D36-A14D-4FE73FC0983A--


From nobody Tue Jun 10 08:22:58 2014
Return-Path: <jari.arkko@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A111A01EB; Tue, 10 Jun 2014 01:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 RN_L9qhjQHnn; Tue, 10 Jun 2014 01:03:37 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9490B1A01BC; Tue, 10 Jun 2014 01:03:36 -0700 (PDT)
X-AuditID: c1b4fb3a-f79746d000006fe2-65-5396bbd69cbf
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 67.A3.28642.6DBB6935; Tue, 10 Jun 2014 10:03:34 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.65) with Microsoft SMTP Server id 14.3.174.1; Tue, 10 Jun 2014 10:03:33 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0D4CF11020B; Tue, 10 Jun 2014 11:03:34 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id B77925766D;	Tue, 10 Jun 2014 11:03:40 +0300 (EEST)
Received: from [IPv6:::1] (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3EF8357045;	Tue, 10 Jun 2014 11:03:40 +0300 (EEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_ED26A79C-BB66-45CF-970C-5540AD16231E"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [Gen-art] Ge-ART LC review of draft-ietf-nvo3-framework-06
From: Jari Arkko <jari.arkko@ericsson.com>
In-Reply-To: <B30152B129674240ADF67727A967301408B68A@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Date: Tue, 10 Jun 2014 11:03:32 +0300
Message-ID: <0E5ACE09-B356-4740-850C-4941ED1A1A0A@ericsson.com>
References: <000a01cf7bd5$7bd76d40$738647c0$@gmail.com> <B30152B129674240ADF67727A967301408B68A@FR711WXCHMBA03.zeu.alcatel-lucent.com>
To: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM+Jvje613dOCDeadN7RY+/0Em8XVV59Z LJ5tnM9icXTSKyaLv+3MDqwerc/2snrsnHWX3WPJkp9MHl8uf2YLYInisklJzcksSy3St0vg ynj+4DdjwXzDii+7PjE1MO7V72Lk4JAQMJG4tU2ti5ETyBSTuHBvPVsXIxeHkMBRRonTfUuY IZwNjBJLOo4xgVQJCexllNh8LBYisY5RYuP7uVBV8xglJj//ywpSxSwwhVHizKFwEJtXwEBi 3eJjjCC2sIC7xOEFH8BsNgEtiY3LF7CB2JwC0RInu9axgNgsAqoSy+a/ZwcZyixwmVHi7qp/ LCC38grYSyxp54W4oo1R4sU8ZhBbRMBO4samz2wQP8hLzGg/wQ5hq0lcPbeJGaJeReLW37Ns ExhFZiE5bxaS8yDi2hLLFr5mngW0jVlAR2LyQqiwqcTrox+hbGuJGb8OskHYihJTuh+yL2Bk X8UoWpxaXJybbmSkl1qUmVxcnJ+nl5dasokRGIkHt/y22sF48LnjIUYBDkYlHl6Fb1ODhVgT y4orcw8xSnOwKInzXtSoDhYSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAWL10e9uiHdpLU7cK np+dwaU2822Evtr9h+bJ/P+nXT3Mu6quKqSY53iJGwdT3Ln0Ky9Xl51P+PmUU7exlHvPuXrm vW5cE8+6PzA4f+HPcYeQz8VL4zQ/bc6X4dptE3n5Sl3K57AnK/lS8iqO6lleUlS6bTZTudVt XduBvWJzFj6Un/XiwqG+zUosxRmJhlrMRcWJAGfEQiKlAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GObJK8wR_zw5i6iBHVrJwBDFqA4
X-Mailman-Approved-At: Tue, 10 Jun 2014 08:22:52 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-nvo3-framework.all@tools.ietf.org" <draft-ietf-nvo3-framework.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 08:03:39 -0000

--Apple-Mail=_ED26A79C-BB66-45CF-970C-5540AD16231E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Roni, many thanks for your review. And Marc for the responses (which =
were sufficient for me).

I have also read this document. I have no concerns either; thanks for a =
well-written document.

Jari


--Apple-Mail=_ED26A79C-BB66-45CF-970C-5540AD16231E
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINaDCCBEUw
ggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVs
aWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4X
DTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv
1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqT
u3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMc
CYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUb
Az2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB
/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRh
cC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2
MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNV
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb
8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXI
v6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzY
FSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67
OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3k
MXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OY
CMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAw
OjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDgg
VjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVy
YSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5D
uVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe
1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF4
6H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjgh
XYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGj
ggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7ga
YqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0F
BgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7Bgcq
hXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20w
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vv
bi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkww
DgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUE
kUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDC
fkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6b
KuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHn
tP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPd
OI5GtDYPMIIEqjCCA5KgAwIBAgIQTyXs3vXto5joAjtwrbnc3jANBgkqhkiG9w0BAQUFADA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxMB4X
DTEzMDMwNDEzMjUyMVoXDTE2MDMwNDEzMjUxOVowYjERMA8GA1UECgwIRXJpY3Nzb24xEzARBgNV
BAMMCkphcmkgQXJra28xEDAOBgNVBAUTB2xtZmphYXIxJjAkBgkqhkiG9w0BCQEWF2phcmkuYXJr
a29AZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhwriyJIY5Bbz
yZrfnFAjWFLMNc6O6Z6dw5HqexTVyrUymDobuwcFtGl3n+yc6tYcvzM85LJMotJlOJH4NHEqClEc
iMw+gFvN17PXxM2aAPuv1ZUL1wSdQ9dS94zxQEQuh4Myyfy+eqvrEBkzZaDPu4Evz6xsmCYPYSZP
t4Bo6zbwQqkRvSQUO659ytmlyiPOiWN6wxEpwwO43LEw12xFrVSOQw3AG8ULW/xHbQvInuyWQdBC
ug/1n6IJETsMWSrLFnk888IjABXKkmq42EG6RQ0BWLw8lAQwTju7rsDF9HrcTYBcu9z2u/d4cSgH
P9SkRncRm68xrt7bD2RhPf3rkQIDAQABo4IBgzCCAX8wgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3
aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vRXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZx
bGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29tL2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFs
JTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2Uw
IgYDVR0RBBswGYEXamFyaS5hcmtrb0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEw
MTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0O
BBYEFLk/k+8oySkNxYm0GyPaFaKSRQufMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCb
MA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEAECF65IiGH7GS+EEHre+itv2wv0OQ
Z68DWR6G9IqMkBgb8dj6JcfFsu+9p8ID1e1L/0ybeTwz1t4IPhuOuWBPohj5irYiCBJkIokUr09B
rWPyxfBrSoZ+uXVWfmZSdp15pWlEnHhuGuJkZ2a0MKrj+OEM9qfQR5Cvdlmx5PvsIhFkAFcZWldI
xBwHsEeSoGJbVvvNImiY6M27u6rhuR8HanXVdcW4B8gK489LutxKhyhT9QDFUhmyWk2qYCUJgwM/
w44sLz8tv95jDbJxAR/aOwdwF3fQgj8VB5Xwvdn6B0PhfEcd3Ju4yUz6HE6ELZWG4ruE2haUCOn4
8WStKZ/RPDGCApMwggKPAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQTyXs3vXto5joAjtwrbnc3jAJBgUrDgMCGgUAoIIBGzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA2MTAwODAzMzNaMCMG
CSqGSIb3DQEJBDEWBBS8Q+/ELN8ezobV+GAJMDYiruR75jBcBgkrBgEEAYI3EAQxTzBNMDkxETAP
BgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l
7N717aOY6AI7cK253N4wXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l7N717aOY6AI7cK253N4wDQYJ
KoZIhvcNAQEBBQAEggEABJg1iIIcl6gekL2W4HCK0AbOUhw21IeCy8Ykum67QL2InKYcuxlcnb7t
suWaO0Ui3SLSfTYuhPE3i8HKqTFGdQ9gWYHqrArgUph6ViPPN2yiPKK5FvS9KByYfS/3OGJY2/SJ
dJZZ3qZVdC1AGj0dxMFRPfd8LbBkhiCmcXQsA8P14u7RnjeFMYyGGbEI0KnSCLP3ZzkyscOzH37V
7d6oSjlrM7K+3fimfUb3fgVYjghBO/e0/aqPPYJd4JW8qEnMV5bLYY2L/f4UmyEyfgJxtpW5ZXbz
GfnfQajDZz5LDB5my2DeEf2dcg0XdEpPg+476aH9OCkaDsU9g/tDccRCAAAAAAAAAA==

--Apple-Mail=_ED26A79C-BB66-45CF-970C-5540AD16231E--


From nobody Tue Jun 10 10:16:55 2014
Return-Path: <dafalla@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C8B1A0332 for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 12:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.177
X-Spam-Level: **
X-Spam-Status: No, score=2.177 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01] autolearn=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 NvV8BVfF-uNq for <ietf@ietfa.amsl.com>; Mon,  9 Jun 2014 12:18:01 -0700 (PDT)
Received: from nm24-vm0.bullet.mail.bf1.yahoo.com (nm24-vm0.bullet.mail.bf1.yahoo.com [98.139.213.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4A251A0327 for <ietf@ietf.org>; Mon,  9 Jun 2014 12:18:00 -0700 (PDT)
Received: from [66.196.81.173] by nm24.bullet.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 19:17:59 -0000
Received: from [98.139.212.244] by tm19.bullet.mail.bf1.yahoo.com with NNFMP;  09 Jun 2014 19:17:59 -0000
Received: from [127.0.0.1] by omp1053.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 19:17:59 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 700949.95295.bm@omp1053.mail.bf1.yahoo.com
Received: (qmail 38635 invoked by uid 60001); 9 Jun 2014 19:17:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1402341479; bh=vYp/FSQTrFYwJSWPzFH1yLJ54VXMoJKzQPkmux01j7E=; h=Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=f1+l90W0VmgpeZ8d+iQUPxwyk3htOU4OV2lp5HDp/qRf+nyYmpLQMkjFGzjPiw096nzYG8VeDqoDhj82ZRCLeRG/UErCyDEc2Gob3aRB8LbfCXJg10qJ7qrlcOOG2+5YJTRff2iR/Ti/L6qyw6CB3lO8PhrSB7nbP2YNBNkVMII=
X-YMail-OSG: cGFWW1cVM1nvU_Lmy9e5dRsnjZHPZUNg_3dLtA0bG9q03F_ 8zPOxAzIAvEVWKt2rcPm6.cbxduwqoeDDRCRJ6g4GsjaZr_oOXUCwP_8PvOX ME8W1RdtJfOX04fNRSWvUJ_wu7TNXqN_t8HoFNZw2HVM1Ycqm5KbZ5lkb2Lm 76iK_dF4rSRbHapvy6umpfBbD7N7OMKuWEiT9GsvRyCMiWLu4bc6PvFNTGay OgGCooLU7.cp6uHvsIBcigyPlhy8ERQefRnfcMq0McA_ebMTm8ASyKlXwFP_ owFdBkLZxdj3AWxSxybCtIQSNh_tvQFFK1BHwW_vu7wM.roNZmhPbZ_kANGb xZLhe.ChWcWQERXxy4_iQiGW8YyusT5IeDFO1ijyaqnuNrowBWEYRsrrMCv9 djrCMZ5neXSaP7rJpTSvhWlAUpWlIbwwTaTdXX13FWOr875SrPGF4ex.KKWc _Pnu6OjH_wtV753R5t6235VxrCHE.sHyKsFfMB2SnUH.MZnRWKJufmMI6aCN y7POo
Received: from [41.223.163.71] by web160104.mail.bf1.yahoo.com via HTTP; Mon, 09 Jun 2014 12:17:59 PDT
X-Rocket-MIMEInfo: 002.001, RGVhciBSdXNzIEhvdXNsZXk7CgrCoMKgwqAgSSBhbSBpbnRlcmVzdGVkIHRvIHNlcnZlIGFzIHZvbHVudGVlciBvZiBMaWFpc29uIE1hbmFnZXIgdG8gRUNNQSBUQzM5wqAgYW5kIEkgYW0gYXZhaWxhYmxlIHRvIGF0dGVuZCBtZWV0aW5ncywgYW5kIEkgaGF2ZSBubyBjb25mbGljdCBvZiBpbnRlcmVzdC4gUGxlYXNlIHNlZSBNeSBDLlYuIEF0dGFjaGVkIGJlbG93LsKgIFBsZWFzZSBjb25maXJtLgoKwqAgVGhhbmtzCgpIYWdvIERhZmFsbGEKU3VkYW7CoCABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.190.668
Message-ID: <1402341479.70931.YahooMailNeo@web160104.mail.bf1.yahoo.com>
Date: Mon, 9 Jun 2014 12:17:59 -0700 (PDT)
From: Hago Dafalla <dafalla@yahoo.com>
Subject: Call for Volunteers for Liaison Manager to ECMA TC39  
To: "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-1615118150-247632436-1402341479=:70931"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/v0IACFBY88ifvHBpwXmpo0MvuDE
X-Mailman-Approved-At: Tue, 10 Jun 2014 10:16:33 -0700
Cc: Hago Dafalla <dafalla@yahoo.com>, Hago Dafalla <hago.dafalla@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Hago Dafalla <dafalla@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 19:18:03 -0000

---1615118150-247632436-1402341479=:70931
Content-Type: multipart/alternative; boundary="-1615118150-1885765737-1402341479=:70931"

---1615118150-1885765737-1402341479=:70931
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Russ Housley;=0A=0A=A0=A0=A0 I am interested to serve as volunteer of =
Liaison Manager to ECMA TC39=A0 and I am available to attend meetings, and =
I have no conflict of interest. Please see My C.V. Attached below.=A0 Pleas=
e confirm.=0A=0A=A0 Thanks=0A=0AHago Dafalla=0ASudan=A0 
---1615118150-1885765737-1402341479=:70931
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo=
nt-size:12pt"><div class=3D"" id=3D"yiv5003803522yui_3_16_0_5_1402337724187=
_4" style=3D""><span class=3D"" id=3D"yiv5003803522yui_3_16_0_5_14023377241=
87_14" style=3D"">Dear Russ Housley;</span></div><div class=3D"" id=3D"yiv5=
003803522yui_3_16_0_5_1402337724187_20" style=3D"color:rgb(0, 0, 0);font-si=
ze:16px;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida=
 Grande, Sans-Serif;background-color:transparent;font-style:normal;"><br cl=
ass=3D"" style=3D"" clear=3D"none"><span class=3D"" id=3D"yiv5003803522yui_=
3_16_0_5_1402337724187_14" style=3D""></span></div><div class=3D"" id=3D"yi=
v5003803522yui_3_16_0_5_1402337724187_24" style=3D"color:rgb(0, 0, 0);font-=
size:16px;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Luci=
da Grande, Sans-Serif;background-color:transparent;font-style:normal;"><spa=
n class=3D""
 id=3D"yiv5003803522yui_3_16_0_5_1402337724187_14" style=3D"">&nbsp;&nbsp;&=
nbsp; I am interested to serve as=0A volunteer of Liaison Manager to ECMA T=
C39&nbsp; and I am </span>available to attend meetings, and I have no confl=
ict of interest. Please see My C.V. Attached below.&nbsp; Please confirm.<b=
r style=3D"" class=3D""><br style=3D"" class=3D"">&nbsp; Thanks<br style=3D=
"" class=3D""><br style=3D"" class=3D"">Hago Dafalla<br style=3D"" class=3D=
"">Sudan&nbsp; </div></div></body></html>
---1615118150-1885765737-1402341479=:70931--
---1615118150-247632436-1402341479=:70931
Content-Type: application/pdf; name="C.V.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="C.V.pdf"

JVBERi0xLjMKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nM1cWa8dxRHWTXACFwtss+PtxMb4
DOaOe18gyUOUKFKUF9B9gzyRgIREIsj/l1I1M9319Zmec64vEGE/+GiWXmr5
6quqHn+/U6M2O8V/y4+vvjt//nncffPf8+ny7vO/Lj9++Ob8+/M0Wv4zXcDf
X323+9MlvZh2Wo3RebO7/Ppcj0qpoKcH9M5kP1qzS2HUOafd5XfnX+zPBu3H
6I3d/2r4x+Xfzi+McWNOZneh7ajooX+e053Lb2kJwZvRB77yBV0yY/IuB/p1
QctQQemti9qNSvu89eTxX1cfp/vkidu845xH43aXfz+//OgXsi9zzX1dZcaQ
6zimvTg9adLJX1cf5/8140VMwY+hmPDzz7VCJzB6TFXBZ1UiZyK6jYtF3BtP
Hv919XG6T65u857dGK2mLf96uKDt0e/o9y8NtNVsE780775BAPLmaHjz9PrT
tWhGm5NnAJm8+sZwwYOFkPa/Gcj/aQaz/y1dHE20KexfHryyo9OpN1EY6WYs
Q72Ip1zHsY+a0SQfk1x0AWzmpYExTZtkeaO0TxKl5o2OmV7StFG6PUkShn95
oF+eAHH/ynDhxpSSjfsv/z1okkm2ev8qXw0kw7i/SfMHR9dusEqMc3r/5Q/y
0muDHZPJMTZXZdGvD4GEGSJL3JB2Y077W4Oid3yg27Dk2/Skzdni5Hd4RTmF
xtPfoL3ZpH15OZEaaR2aET675irs7hUa3kRDYl42YuKGZ12YNGZlKFiQmbGP
seZpJD8mZbMh2VLEiMpolpgaQ6ZgFEmketSRxSNm/ipdS1GbTFIkMeVsPHoG
SYx0Ezw9+RoNpIJT1mYSGZlmSDq3E9wavA1jMLpjpj5SVHNZzPQY9LR2VK6+
OVyQrYdk3P6tOXqS0N5m+fGqPN13o88s1LfqL7h9Vi++IwO9Wwd6r97ekHnZ
wcXi2ryN28OFJfej3ZMhiHxE/m+wUkh+nqVPXm+9Q/n2xV+UQ9I3oyPjSmw8
ZPh0txU9w4aLOhwXfR5tsP4QIRpcJ4nTBM559Iz3h0h+aQgCwQm6Bi8+9Cr9
ctGTEd9BHyqOeVcuojfeo1hC5EglnP7+JBziWfsH8pZMD2uCUX/aOOiDK694
a8s4ITS3+9ayCB099E3eZchm8tAC86BQdDH0KzEnNDKxk7d4XBM8jdZ/bb6a
MseSt9kOlQ+a3ICC0Egm17GZQGM77bo2c9xLX588TjvjUUMVo2/yxpM6wOiu
1aAyujIui0SPfJf8iEShPLieCOI9Hj17TZISNIRAW91MXhZy8D49R1aqyIxE
iNPYIXvb6AY1KZ6NV3F1kynQilFN+OyCEjmSoZd57zHyaOcpqM784y+X55+d
++R3FKEo+thdomQi7n741/nXV8heWsm26UskLe+cD6Nyc+5yg9amM0neA4Dd
Z1CNcY7dHdE+qEuX268PmdSeVRNzHlZI3glO7yo6/464UBiTDR2rjTSwDpVW
9enIw+HCjLz6aQJH1qKm5XPeZR1PwGsOpNR63+67bEaICwCQkIgHFapu8u68
jgRvjwZG7OynOFPsm11Bs3yJW9zt4auwIZhpMhyt7Nb7s1OFKcpPfMWpLf9r
R114mWDcYzY21q3DoRZBOQJG4Esy/yweMmGmJmV5clEm+oDHzIFMisya7kaF
k3eZYH8ZhR/qJIAz6yNbRytjkzHGklCrjaAUYCRQ0z22R221xkjwZLL76AzJ
JhLX43dE3icXKlK4zfcjmBgJ7kOmj1oFjzM+ZbP1xhoNb2M4ZfDQVtFWe5tH
Fr2viwdx14m+HCrcCA+FtS9mTbjUMvM6+6JOogOgRVnJzIOz0bXykTlgMLGi
h2etSOgv3qgOA8Ys1pCLwRFAw7OLLiSK5EWsKueIuc3jQZNrugllK6kHCGgs
G5y8eP7KtPniyrStRVEXKPmIY0C0zjnwGtzlM36ARkxgW1W3YKL4DuRIMrlA
jcCT5EVy9+OBUghHo6I0Lgh7bWIlIs4IkGA6s6N1UrCzeiNmzyqeSwJdOvSI
Md8kTpOE4Dyu6P9B59eTIxHBcezdCAhl9IaxFKL6iKVI8dfPNJsioqlqYJ5S
Id2D+J7MQSQCH6YQQvDhjLZNiMlMQ0zE24tbBoXBimhCZr9xETUi9lWtQVYm
v9oA08F6eWCFLmzGgk2jvCNRDX2+iTDLkgBTXubhk9IaLX0rfhkmNrGJWtcN
YHUBgmR3MZeYAoKlJEtDAaXA8HNalOGMHaEdN63oJ0mP7AXgrW5fc9BUWhHF
a6LJKsCdBty6YikRdACX4ydsGRGXPZ2ochNVQSMblKIjXOQUK0TaVggP2gbQ
GYx59bQmQ7qPfg4GMVDsm6rgC6NfyEcCTAegn/HZsYPclZ/z3tnIIEbJRcRn
Lson6zbwWTOceQdWibb6jODSGKNjtxwFEHIanyvVE/d7jfHRMijKkj7miGB1
0JgzbQH0qizG6My5YdhAZ0blD6dU3ATd1BokhcLERNKR9mpNsp7ONSnl9QRv
hoxXW6xwDLzx7LLi/UzwaGp5ic38Ix6XsppEZOWdyWQpYIRZ6/MU8tozuXhW
gU3yM1jWe70npcwrQ8I7ksZh/lIXKhfhnV7150jiRqklJ27aer9LP1nmZl2e
smPO3D6eCpMuw3oeLMt1qO63ZQ+iebhfo7RtauJnwLUch7qkIXkVUb/LNpYy
2eGzakEgy5qF35kjbw4ZXn5YA3+TH5akUbjCvcFEsr7Yq5prZgzercuRL8SA
Vg4m4xygFrupgDcMLRCCINFCxzp3kiC6pKhXqkmVTQPRPmIQulQFKYToRrUV
IIqjoEs3rE5MhxN93pm4xK2q+jNBP1Tu+tex3D/RrCEYoXp0j9iUaXR7EjyL
Arq6rasE5Wqa1s5xpqhJxoY8YsWqdEDibQhdyEeCxloBBSw/enrFTpWnbI1p
88k8OZHDvPdF7KGIjO0hLAZxMW/Neaxi313hJSn6uKpG8U2A+1KxVnltOySF
ZXLbItDdTuXoDJVRXP8DmVOyg4dy8d6QOIpq12/ZaUXryJUIgpKrt4o1NCki
5m7CYzus6gUYuVgEpKDCGPrkQkyiqTMBDZZUTTBkVXNlm2kygsIkMSMobzcJ
wYTXVpkePYR1uEm2ysfcLMlD7WjFp/FBZL/4KKYGrTvySkRmq37DiofLXA0T
nxMGNQadip10+pM6tZxciiAFwBduR0Lvc3JQicgXVrIljK1wUUc7vfOfpeRD
erFaH5J94jIEdR7OvGyUfm7VGo+Q+C7Hh8rOgrhT61KI9EHSb33ENsWyJ6O9
B7cGAKgtYOg1wzudaiIjROOMhcr3+1fd/sfiizo5qN9AHEFnPCwITuvqpScy
PCxvBhAG4F61TTVLFbARF7u2Y5UNbHnT7HieVOZb0tbzK0O2upXrQvVhyQG3
quenqw/rt16k+ACKLiWHPoJuFdqx5+A5w7brdJfdT+JPU2m/pqauWYwQDUEx
AhP/RbmQ+RteIqGKcgAAy7oiRXexZfCFRdi0bcAPogOeHrWxx4McCSeW/jhR
g8tvV2dsaJ8pwGmduoJTnrsI1Nrm7AtAw5blV9edKxSx7Qf1iwRl0sDDRx+9
AdUDr9xAqZNLAd136o4HlS1eyFLgJsPYLHBz9qPSvlc/7CdBp2PssbIXpnfF
veYMIB7l/1OptlvQppxdxZpInlVXPluaG14RcoeGYy/pL9vPKv89PAfQdvxL
K7rNwZYO7EYO1q2sQzN03WKFvPp5vSgs/VhenUioZKDrvHpuk5kc0RBvDEaP
hwruW8qRDuVROg0tVJ1JE2RrkbdHma51UKfvnx3rMAsaytdiYB/s3mCleu4n
VDPqpmWJ3YNSoNi0mbBtXD2B0yYyDrdmJU66Xbmh8p1KM3Q6JHivD2xMmI/t
JXG5fp2/jL/l7yVOPFs6sHEUjznt+UcI50bLGHKXbuyVi80hpWXzYUNdG1m0
JV8yKmJVBbzq4aEDlR4CH9KJseu+3QqXOD+k6JAlI1A8ogFS5INbTWnl6LmK
J1eqmyWSq5KGmrDZpllSySYUu1fNEuawB80SlZuuVc3AT5zwvLuRgG+SMhbH
dZo3tzr56XgY9tlUIL0T5lMGb7hhm2YvLO5Bl+V1O/ynMl3gdscqDn6uIlXy
iTBTBm36eeVMBkLGzcW9Azc0IT0u65upTK7n7HnS+5Vw4vZwVNEeQAVusETc
fuSva84TR3TZbcm0h0TdbmTbA5ygWU/lOtF0DXGaww7rfF0bMnk+BbM0x2ZC
nhjkl4MRViUieU12zG7GW6tn5g4zvZVZN4Fk7WY54JhCnvt1adFFmzQXJ1+X
Hw5OR4lzv0D6KyUB7L8vW5oXar3dorUAR2g1UD8UZtKWmmaqXlr1ILsmd5LW
3EHn4CBdhquV9kog6qZj4hyKVx6JKxxGxDkv5iZJLUgVPtuzZyA0bS2wpwE8
+dQJ8X1+3oddeZ1PO0QyiuckWEbIzI5J82RNad4nA39PEuO+mz2vyyg0y6f0
diLRpARlkG7GfpWa2YlM/n7tDAIBOcmUuGjkprZrwyvkLDEcMBay0ft15Qdl
7P73A4vFAGd53CuedzhL6HOWx72C+y+UsxRcqZ9pdPtx3d6OUJfxOqTjKcVN
tu+wx2OiR4L9hOkY7DstxNWRUjYBca/NwHWc/6RRe6WudMqmGJvAFXhH9xCR
zNin+iATeb8HR01LD1C3AwQAuoID92YAdfydhV4XFrcAuFOM+FlQt0i2nETZ
ktcJxQBoz3bhaR8L7Coyxgl2nXK2g7v+oJfU1O9NU6/7lGOYd8kX5wDrC3kV
XqcC2gF5aDc0neVZpfs5ACPodsSayndhDLV0D2fu8BMD+UTk1MHFx1dM705C
5fiLh8oiFCHPwBahrl5Ttd9X64WvrP4A31Z1TxwWLBTHlbpm58wl9u+bhkSP
9L0IbABZm8A/5uUMLt0OB8AxVR1U7tODTb5W8ffH4kUR1OG5tZ8BLWaSVlqf
TpjmJ/wk6zC0wDFV9bYi04ISkZLHceix46sxtit+uvBjGdsG5+p+ErZRHuKs
IW2Uhx538EPR5EFzs08Oy8zLTF73z+RsQU7BFL06jTFlYNNnPMnUz0Apzt2f
zLJ+3hUjn405ffpKYKag0PHTV3r0Ma0ZGbdLljPS7Se8BQwgXEDJ9MQ55uYb
28OmZnueGg9PF+xbMgzdEAssqpYa8sa3JJ2vMcDw4W4pH8C7TcmjGq249Zq6
aaxvL986wafXh7VdmOBOZ3N/ZFynt5rPWyQjA3HCrPJJDBBWcSmYsse0ll6v
mc69FxNZBfelYlOW1HXYzYpXcdnSYIymc8hGH+Jn2cnWZ0KHNYHtDkZTc6u7
uSVVoXljzrSgU0+Lfr+Laj4Fyv9q5/XO8/8fYu38n5hos/vzf+i5z87/B5lb
3UdlbmRzdHJlYW0KZW5kb2JqCjYgMCBvYmoKNDAyOQplbmRvYmoKMTcgMCBv
YmoKPDwvTGVuZ3RoIDE4IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3Ry
ZWFtCnic1V1bryQ3EVaCcjtEZLMBHrLJMsvuwkzC9LHdbl8SxC0gJMQL0b4l
PIGIhBQkwv+XKHe3XZ+7y9M952y4sC/NnG5fq776qlzl/POgOm0OKv3LD3/5
+ub2c3/46l8348+Hz38/P3zz1c0/b0LXp/+NP+DzX74+/OYFfRgOWnXeDubw
4m83ulNKOT2+oA8mDp05BNf1OobDi69vvjj+8qSHzg+mP756+vOLP9ycjbFd
DOZw1n2n6KW/3tBfXvydRuAG07nxly+O7nTW9JkL9jictKYvhnh8eFJdMDZa
f3zMjz+mR+vj4FMXpguDje744Ul3wdPQj6+dzqqL2g/RHN86nW0XQug9/Uyz
MLa3x3fTj95p5/P3Jhzj+CO1f3w09jQ4+vHLf9Cz7o0ehuN30wsuDNTU2/SV
s73GV187Gd1ZNVTffPkN9/8GfeS9j6H+ahyU1Wmk2nXKxjQpbTulB3P86els
OlpKo7H7R9P6jMM706My9Pzdk6NFGWjRyuhePZ1pO5Vz8fi9U09dRo/DgPfy
Ijw9+a5P7x0f8Bjnnh0t9/RxpDUsH0/9OtqBeeKK/l5N/MkpdiE6Z/Nsjcd9
mUc50M4ZGqWOzljqPomOMa5zo6yNIvIsfRSdpj36cVoCNy73N7xwT5IMGRpW
Dy9Msxuo++enJIE9SRhtNglp1MrSEofO9d67efJ2HMfZU0fWm+OXx1GuvDXH
D9KvOqrg8w659NG5pyVJs3s7NR8U7SXOfl49qzQOGpYKXhB7iGmBtR5c2e5e
GXkpYYE+SFqoe61h/h+dzqSZPXW7WL/8/SxY1OnrNOtIEqFxe+w4VzX4CIO6
pd3te0NyB81/kh6T3DroftbLYHy9PXmin9LsArVPwtyVgYDwFZGbGxoGO6rA
KCkqEngUSUGhmCfVx3lSSsU0KBIt5YcRoGyfJjMBlJkaYDSZ19Q4g7hTA8Oo
AaQp79JTH6nPQ/rIOEValpVQ6aLXsf4xI9jWU1FmxocJYW8/1woh2kyo+seb
Fx99cfzR6ew6glVSqldKYz8ZBc04nUafZqpNpD/n4cE3h5PtCEhpyvz1z+gT
UpR4fJMetE/o9fikTacGp4/fGWWUICKUBo3c4AF/HG0GieAHJ+MHGlCYJlaZ
nkCPpLJ5kxm2PpwU2/aIkjMYDLRgb6S/xz5EhN6H/FhZgRYwJFScAIp+8jSL
QJvRJ6knSQtxsMdf0HukkiTqPKBiVjR8w7aGm/7oNHSkzjTGH6a/WtX3A61b
6IwOuj++dzrHBL1k/hinQDcngaWxIQg+KGrEwD2tBTVfY3BWUv7zI1yf0g93
vrYQlmWcuswLY1Fv2Fpgl3lsk5UKFkHrFwl0CDXYsI8A8rBMjXR9RICeXvMu
Cwc3yk19L0l9wioH01xayzTJ95I0kzzU1uX19I0m+1FhJkJ5w77l/sGac/8J
MwiTaCIzLaHfHvPSPsJ5jm0ObsA9xkWhsdDbhv5fNfDlnpqoehhWbQHwBcDI
Xqcd9kDivkCZJBTxSVvM8eME/bGPNgAwvrWkQWlCHTO69RDGn9EKZfCpFjFT
mcdllRrkrbbNeWGYM4GIfnBKgqSQFq2Ht4AN7OrB0nbZqq2Z5xJBJp4LYJQ/
gr2fBhXMaCUL+jO2zFvvoq55bvmVZQvpRJvnLvmIzHOb8sZbPJE33w1ZHVmM
8XuZBf70pEmsYqi4057B5i3eqfG6xrXC48QN3GK+0jpUWgrIsOD51BEQTu79
GbWvY1Q18ZDbX7lEM9+dqStvOlq1MmOTBtIPE90lnTahJ0EuitDiuK4zPhG/
iuIuKRJukyvqZUImL+dJToB78WDRv5n9K9sLhDeRs3m0PgBWzIzU2qXDsBNr
7IkIqdMWvcOK72bL/wkZb9dHhQ4l6GFeFeeBu810V9OqId1deXHsIi49ywXD
lWh7DRiTRNFG0ojO1KoL2i6o7AjjbIySj5zJrKmZZ1EdFrjqxyzb+GeJrSaS
qiWSOg7MRcIvX7HU/PcfFSZZcdxMYr+fdMpFE81kuX2vkybRmyROsXQ0er25
oWfc0DNofQ859eTkehXX5BR2wpHsEAJZC/542ee1yzyYCs0ry5P34TZhAHGm
0dPMsoNbqqad1sEDDX47jWnQnn7UBAh60D2K7qdp6WiNteCJVXZhYQyKvgto
Ccjw89rCJtH4GSlQsPR3/oDbAJPIwwFZY5wD4/rlqTBiVtlPqWdHXnHqkKCh
1057dPGh0feJ6MbeEPoKk9EJEZVWccB5ASPmb7rJGFqTBJClo/TDnFfopzLb
2TEBSlhBbLZGsLmPpN3DrxQ90pYTvMjTTLKhlN4BN9exyeSiqobHnR03pduh
PP6Zg4XwAjNP9rmTphh6E1iDi8V002xXa1EFyaYtpx1HFBR3ZSYdhDYChjeA
t7zJTBb81/nNnjYVXoB9ZtWvQkgC52RkgfaX+pzQRqDBoDMPZEIo07yrYlEs
ZROJpB6tyXrDLhi2lB1nwEK215Np9uiH1YEogTjN+EfUe2WaFwrGvK4V/QTU
ltSF/XaZ7okazrx+ts1LOysa5N1WWvzmshE/5406Gw7pg1l+Klno/Qb+yaaB
J5/QxaGvDXxW06eSWX9WzDqM82L4aaCV5giDqF6yXc9EGVSusuts03KTFVjJ
Zv0yWLFR3+Cb34JRzzIFeAEqw45YZdenxx4l8Rq7XhSWmURl13Ob74zBNZ1i
OzD3HL6I16kxYOQUgvKdiiU+WaFu8dTgUVxxCSyvA96MSBU2FLPbu0lJo+GT
uFUAuevJovZ5IqAfT4Rw8OilJTlQyRUcfQ2T/l5C3EygO4nnr4m6SrSKVt4n
+vUK8+enpaEGUc9P91XjWcgSG+GgLp55CIaGPWtg/JW4ZT2WNfoaaWsa9uSj
b0uYQL9fioCtrEKgjXWzwM1G4TnvnCkB8QbSZwk5TwEIO6TguEr8RRO7esSP
b6aALfEj/KgCfUFunuySFhe7geBtQdz3OHNboP+/4MxVh9kwunv6cgD793Lm
8gJv+3I6rZbXI+bPZ7w8oPeT+BiTOMF9fTkecPbqAp86Lly5YJRfuXJ9bLpy
5WwXmWYOt4G8fFuuXGHWc8Df0OoHVN1l6HiMm8FRJgeaKhcup11A5JN/rNw3
jsvn0wSOxd03P0NWqOoMcUb8qqG8/h8TrTDGaC9FYJNui2cJh3GrLdF60PKQ
9IOWSQ/gF0K8rVs6UXOAnxdvzjRZpwtQ6zkq6dB0MGbLB6AN8yAd5YGvNjlo
tGzOcpxf9Hagoez1sSKDPnxyon7G0D8gQtNdg8QByV3bZLbSWdlGCsQs4uSm
tNw10OLMKSt3LcmDMXgis+2kSV7Y5aeGjzbtFag0ULvufi5aL32+x3DPGQQY
jhW9NWYIO1keiZHZsNscqBGONe7oreUIOh5e3MlbY6stQf+93bWLbsaW4f5v
eGvZKDbP3ViHEYRms1aBpeCtzahsfAS05CP5DsFyxN/eCyHJbQRFUJbodQOV
D6f0eex1S7nJ5+pUaAZg7qyehVcXM/9UUMpr1dNRF8r4i+p5NyesZAewLjWc
sGLlIQZ8jRNWhhySKTAu6JY9l9M9N0RHiJS2ZEdII7jGS8ubAXahwmBBchRN
2WlNNPu9NDw3xKFhKx5LYP9O2jtasKihTZM6Ilnr8WyODUwHoYey9K8lvIs2
GFdCD+nAkxpK59WYofbGiOa+Dw6S1XBEMeVa9KGON0iSLnqQgoxrm0IYcOaz
ODudz2YL68ySWSWuCTnDq8S1u/s46/SwTmp8nRRWIf97Yz6grkMYjSC2nIgD
mTCPG6dbxfA9XBjgNALITEXNgGaFRbnCcDLZ4z7RIckjak66eOg8vXdnK2TJ
iy/RqCrjRVqIXek3efx1rhKev6XTauVfRsZrgbkqhWoiF5V3OGeRhMt50kNf
HQjJ/t2MklMib8nchDTp8pGYX89pEEtLDf7T0M4ZaR1/pmHMkuhJG+SckUT/
3dDnFGkdEQ7wnHDp6FxJCuFcShKSzWOpUTh16s6J+fcoGLmDxgkVuzx3OYLa
7ybxm7L7M88GGdLTDf9nti/aYqJ0bV9mgrRpX0aLl2SAjVtl8YRcaeHUbDwH
J1al+ogGla3w/UYExg9/lDJlJOq3jN2acJEFakdzGoScmXdIfLx1KSFt5Y9V
cW3RcAl/hW/lbDV4lDMFN03N2pbezdIUHeM+VweMKcYoW9JGZvDSa11kVrPi
1knOrQzilXvSyuTMRyKiGyn5pZggPsWXQufXSd2rLNzFMjFJmPKRabdLOG2s
G4HUlLVsuDHBnBwqonAr0xlpDCSzmAj9q8kVcVwj46yXigAgnlklT2dzKlsc
Bugq7goHHZNhFSkkkzyMm0Lrv0butTQqtTlmS/SbEYQcIU6evFcaBvBIInTQ
5nfSVpAYk5Kj/auTu8kfj7HK63lL5Au8PvAjgwlKjXDg8GbqMyitrRgOl4OD
GI0QMpBLcDQmUF4nQYuxRQ6gTA5l0EGuruKcEcjMrQrVanqUdAPCG7DLbKbl
4iyUkzseGy59X+OviDBv0ZX8uT35zg4DLVgrwlyygaAwDSLMOaJTpwOB2uet
BMY8s7Ew5KgzpEILSVVjttrFUEMzD3nFzasCxzUzTxq4qkXrG7wo5d8uU2m8
Mro6gmesuUQAbhtpvKv0AGQXcxCqj7oOQq0Zy1YmAMcKnmJGT0iQpdOQJAqi
6M9DiQIKWAqxXxFWNyOPFb8X4sitQrT1cVfTvSzJg+VVTgfYIByCWl8sdxkW
TV4od6liA/DX1QHXCBV8dg6tcwCWEbdRCgL6zHQFCkAYLVYlRJGLwsdQL9fi
5MoygrhSW3qx/MRV1XJ8XAQko1EdzAIhk1XMX7x8mrcgLJZwwssFFoA7ywrx
KcN03hJw8/nodoFlNVfsy0ZVp8Sj6uaSR7lYEywJTK+iA4uuQgTUZIQUU2Gl
otHHy1V0sXnkU6Zx0RefqvRHAunxoAgKUoCAgo8DbBWzAApPljJlUSBzoCrB
vlgarMddzrL8SpGpV+ZinPnv6CPfszhDTP18acUZt/crzmikbl7wrIYqTCNW
A+5I47k603x/tdDdTgOFiwe2jgPzKBqngaWOrJHHU9YIE3ngNLB8/y0HuYXy
DJnzb6ac5wCkePsBJnqfhWssGone2SiBUeH1ZC+XX5RDlbsi8/L1CtvkYSrm
26jvgJUCEwILvZCxNGpODsIXxehySOfuJviAFBy0k80CK28rf2ZPzaDsitTf
t1NcJFI4rvf1Yd9FCh/UCu4+05yE1ETdEtKtWG+WvUY1QjNEmxJStLVCVdRL
yHRJDTcOw8Vygv0WTYwUv7RqhFv0Xe6QxrxWtLU4MIHi88XLSWcsjauw4ZTz
VsqaOAMGWioSKhM90SCL59py4EYsn7/fJQmzPcsCuyrIWN54tJV+WWwTt3nv
vNQ8YvHQ9vls2RTR5pK/DMIB+/gm+cj9EEOVgQyptCsmndqHFeH4yQVAj2O2
Z+bENaCvXFCOgMl3AAA8zUI+2D05MkRoXCP/TcyQafDUZW3CZlbM7d6sGBVW
VaK7ktaklNSXkG4OMi2mm8tMdWmt+r0J52OvAiX+Pykevm/a2jo8vJW1djcl
lEJX+5VwfT/FVYlq5GJ12nsoQqrU8PZ+tln/T9vmhYjN8QdAYilngB2LKruN
z0qvym7bLW0CSkBWwTUiJpwgFPWbeXvUe4A+C/h2GrVcjTRvi4z/z/9T+H9O
JnAIYwnd6DNZyRSYzgZdRKhOe5w1ns02x9Q2C5QKeG9mOrOILc9xa8LIFgnj
EUJt+qMVN5sKJ5Z5PfoimzV1CYZYWdqSP4HGbILckmiYpvzJyZXzRsrJlfsD
anqV/jgW12B6ylx5uZ2e0s7InLJBNtAwPz3fRWq00t3gwxoMpdJJllnGP5D4
z0qP/LSJhPnpt2M7Kignn9OI4gGQ25K/FfpJOAfOCvfIFhQYPDoV1whaXuck
aINbFVveJXQrpv6+Nrp60blQpUTZdC0gDf+OIrcvw2ivxFUciU3ZZ+UEMCmI
JVcgX2g8DPOFxpqMhLIHAneilNOFxm+nGZmETw9PQ/IgotRndS0ySREpO9HH
keF8XXP5hsAWFKy4+JVBHM53SBjNuA+SWB/eyXc4Chk1YoRZ9uf47FEKf1Zp
XFKgnWk6DxVVcvN4slUqyKGrdcKkfHNJM1awzigR735shF2rbOYp0ZLUR4WF
xDrHx6fSQaVMx6SAtWhF8WxVSonbH6hI5UvGN+/+ad2726fc58FilHj2rAiH
1oY9HSnCLeBwfSRnSkzenPMW7xOXErH4eqe1M+eUW2H4lJ2UzRQE1tpEOGmg
wGguWAIPpylsCcZrf6pL2KZwbev639Wtvxm5p3BedOPNvaS4tGB9nTkq1Urc
kywAv85eFORxTLaITHtw2ZpEL5oDIWZrMHeEr46A+qUfTlkk3oLfB4OvXMC9
t0wc9vmApDdkZAXaI1ZLMOZVV6XyJbGs84xOV0AiJ0jVUJHhG6Ikv0vyqT39
g+93X53LtK1Zpr64wqBqicvUxQOvDoM55fGt4sjIVmj7kiYJ0CGkLcRG1jfz
r28pvWRv8gEINRL6xgUCy7vgKuwM6XhUI3a+vOt4S+5YdZa2vKogFbZusQ4h
8AGJKvPgAhbGVU5ivqsM2FGV57L47ySkejQeh1hS/3gFr7uu0xRwHMgb79aD
/XxA8hJAqh6IhEQ8EwFPHisEp/A/oVAoKFSECYifINziDRUPxbDhpaBMH5sx
wHlYslMsGq8tr+XpScxC/DYr0Q+7vJFVJbrk/5Ztlx3g/PQZD+gH/Li/0vW3
kyiR3R/2l7eKh8IsDeIdk9V/iWIt5zzL6rprKRmCfYS63kCCfIzQ1FHo3724
+RP9+zfCX1/7ZW5kc3RyZWFtCmVuZG9iagoxOCAwIG9iago1MTM1CmVuZG9i
agoyMiAwIG9iago8PC9MZW5ndGggMjMgMCBSL0ZpbHRlciAvRmxhdGVEZWNv
ZGU+PgpzdHJlYW0KeJztXNvP3UYRVwJpmy9Vm6QXShPyneRLxTlNj7P3iypa
RCgFxAtV3hKeiqiEVKSW/19ixvbuzNrjY3+5FCGRPMQ59q73MvOb31zWP+xU
p81O4d9y8e33Z4+/ibvv/n3W/7z75uvx4sfvzn44S53FP/0P/Prb73e/ewoN
006rLjpvdk//caY7pVTQ/QN6Z7LvzC6Fzuqcdk+/P3u2f3LQvove2P3Vw9+e
/vnsaIzrcjK7o7adgof+fgZ3nv4TOtaK96x2wZsu9E88258fjqHzIRm3t3R5
5aBdp7TP++f/OqguZBhL3N846C5FbTLcN13yLgdo7zqfTbR7LTV//3CM0Nxk
s38D2viQvd2/e8idi8nG/XuHo++Cz35/E16TstfalM5N2l/Uzh9S5+fDxKH1
Q/7G0ubuwUQPw0y4KJNFzaELQQVY0n7uV8dhmv3Hh6PtjEnZ7d+EnmKMOe3f
hqvgrMaZwZKqDPN5AMN0MXsYUj9i4wO8880DrHm2Ke87+vHq4Qi7rELIMI/Y
2WRyhD7hR69jivtrBxiZcU7vn/94OOrQKZft/s5Ba9jGEPpfXZcSrtMd6vYN
2IQME9Vl+MuPXu0XxQcHKx5gEUI04/SydezqNjW5Th3dgDYuBthj6sccbKdz
gAWvi0Pd0MjqzWuHo+qyTriFt7DrGJStiwgi1c5hvgjjInpr2XgiiEWChbUw
3NCZaGBjbmDvITnVvrSOZMO6osAYC0JqY5GQuzDfHJXm4/jVoAWwmfdqn2wF
+dvFvfgcVcKD/BuQltIBG37TqKzOp6go0VoVJzMpS/boAFc26cS7qrN/gG2C
U75pA7oNPxsYLKoSoEcAERnnbGB4MGYDj0bf44s1uUP0QXwxw/IwtRmnHUFd
YTX6EcKuFB2AsQwiGF0dH+gFPcibswXge8X2ouj6sBWAo7AVtc3tuj5jpyE3
i7rDLk1QJrOeBgydQqUZcPIvZ08/fTaDsqiMHqEsw8JyKNOmUz5oQKU6fQ5l
5epcgjdCMtieo0ZN0SgfiOqWoBfuH3H1Y7QwvQ8JPe/Ut78Fq6MjAswqopYf
6fZd7Fw7nyy0FqBUgxBlk4qiiDvBwHBQXg87zRBwlFnbIiCDWAGLacvo5jsg
GYiucaKm44r16wj21Cojq6ysfL3l06Bx7ZhIkZ8f6BUieI0IbyLCarlNOv2H
Yf9CcC16lUZspaiRQSkERQUoZxAMd51VaTDhKBINotwHIU0Z37MwJwnmbk83
D5G3k3HubVyIpNCUsRfcGhDVWOjRFkFZXOuCRLS+/QYnA5A3bHByzQB/fTiC
FhpEjMH+OsWNDBvqPXlTJaCkt5P8sOVj2zwsijMF5U2Gl96H+4AtzvL7Exh1
sL1Wcxidg5/LLsowmvsJwn3+JCnAoBQofHVK45Lo0FCOccFH3SsYSzo1M10D
evQSWzUGSdg4ZWB2nBGREhA3ui69h0jDaII0TG0qj8ihOMIsm13CemeiZQxv
tLooYd2a5m8wu2Uij/ABkLweoouWMLNbVQwaFarCZfAh/Kozis4OrlLOvQwu
2KJqii4Iux++CGknmBc5/2hYHFw2hqVeypaFjUmycOXqCu3pKa6e4KHk45yr
gwaAA5C1cgABqQsWIHQfUAqjB39o/xjU1Vpc6Mf4I+AG7NMTGt1v6khIsN/F
HXXaGY/rBWbeEidDIf899ARWFUjnhIqDjVQWnQ6QLp1VD9Wl03MEKJRtRkMZ
FDHhIHpGQsS0pUHqyYsQqs5hGYxO2pbBx8wtDg2TCSEbCGHmmgwey6YcDXmQ
H+CQAAAauXhUWQiXRbr/Zo8a0aYwjGQqV+/i/ZB01kwuF0SM/Vg8QyZjw/tT
xlfdqNSd5PYaKmN2yXCS5WBFYemsOymiWuNwzVxEG3EqxIfhsJeJUbVBdfAy
xymvedxLZYa5MQvI5JNZI/LSbuELYTcC2/fGEhZT3pq9IosrnObTg+/gZmo8
ZdnQTg25NVqeBkdR4gl8UBxRi2BbjsjyohTwNUyXPulFBOw2Rw/CGWYQ2LCf
7wfJSa5V0J7/ONsRjH2G7a0OOvLdI67xOWxz0FZPOirLS9afvT2gD6KsczL0
jf6O7r3pgYJ47MT0WnwiUGQ6C+yjMrcLHikiMC82pXorKldFsq0HVLTz8czb
gfYKNiNoDUtInpSsuy1gwChhPgUwcO4LNqm8/VxCkZNqrqDnnEjNq3rC6zNs
AhDvz0DukwMp5bov+Soirxrl12jvOYliBoiU/gs0zqAAlrtHnIyT/0sKzu93
0xGg2L+D0oaiE5gOFmXltHjKP6f0XWBBd0S+RTrLBfyzHlRcjBwLHsHiGlxl
CUhY723opaxCw8lre+bGrQXPGLcQA1t+jBxlNBkkJaX5F4eIgNl7eWVtiPVy
l0JEP9HiNwxVo9F2LUGVuCab/e2DQHYLIJHn6luPce4poEEZ32sR8hEBwGq7
mc8DGJgy93l+jouaQ6yBSHztPXJpBPPRE8beMYgUXYXJnKMWWlSDcYEngSPm
R5PrUIICJiXubhQtcz0FVlF7roV+JmuDv0G+jqDmSKoG+nOpcJOWQHKN2H8i
APN1hNOkbOZwSRgreQVibIgQ9BRYRt1ZmHarBjjlJ7WjqkS3JSx8Cw1bUhqE
iHHUSbgZQYOiwGQARxjTTFO5JDBflVxhhudk52kn6WoWrfW9cAmIMKEpJ/Wb
ESEMKI02bg7CMmMXw8p3iAI11IHcJlAYmFEsDn3oIUUCrIoYMp2Tg0AMcW/W
Nbs7ouTElrJwyzh11nohln77YDA2GdsIOGtHs2bWeCFgtRC5o2cbptrKxwB/
QmqmbhpBfuPucZwcF4D6FiNLHIcnvY8xprGfiLoLKm5dpXsKyJh3C+hLmMkI
fZsvaK1jD88aRqu9Ru5NxqaYqhrF6yFrjJI6u9TX9Zl34XS73TMsDQsIisC5
exHgXAjFF89zWJocXF7A0BUXdR4FOYmhARO7eY6hX9bm7zOgp9/qu9fhtMg/
x9MqOIzxkN8p68zgJXoTuUVsKDJc+QyoRHgtckj+IgFSmURKmsDmxnBA8gu5
MWnwrfQvqaSo7hSVlnhpE1o8zUVPZxkbPCwRdRUq07zDwqFSiJL8eNb9JlwU
WHELjAVlGw9+wgtDkHFRsixNmkVA3fVEDU1gfDY0AwUZ12AltaeqiQyro8NP
CI759YHjZRKblWiK3vgaXmqBaH6EMwQsAKJJ4T8WyHsHulSwbtbmftjlejMD
Pd/GQGGbhtKaCXoSUn5AvS+43qK/TbG6JqTKfKKS6phrDMIi28sGIRlCF5Vh
PgtolO9UzplLL6e8hJu1DZO7Bj5K7E7CYqbEIi1k6U6WhPxlv6jactykwSlY
B1h7EFq5KkMEySVsIICu0NDU7cwY81C3oxVY6KZuZyCigH++lgIRbInhkYSm
HqYeM2O06xlQGpNI3teqS5ZLGqaMuInxUZBAjOFbjNKhM26wHkuI7b1UQml7
FdgDfBLc70xPmiX+JMTuTuaOPCxGDHMI+KiWMmCa3NlQS+28H0vtdEBD4BLo
dxgq7fpQARhLDErdPHjQRpulMGFTsadDAg3ZgT8GGjf0w3SeRsTcsjs8OFFB
SaycmHkqCC+TnG7rdW5EpTKsWUx+0v4S3EciZpSnYqIvUQd2O+NCaO3DKlLR
4KhLKfHwHlopP2Rp6oBZsFFIxXGcmIdZV4sb5tkBlCZXwyXMFjDDfk/ijwTm
0xDd1nAD9SDzCVpQtsoEdE3AoyEvUn3alA0qVShRGvzgQtHAq8pY9qEzi0Ly
+oymJM2Blja1FCxY2JQZFqSiMoKxd9jKhmNRKQY9wFJ3oo9b6yKaqGAJUhyH
ohxPAY02aiik12B5dz0wOKN5FcOy19u9Bq8XBg6X2YLKfVgJ3WoZwCugcAlY
Q1Z+jt8bHNOykpQLW4gAcmJYR/r16y4OKDs5iHlEii8yI1I+MYQkBc7E1Cz9
SFczBqKyrOwLbONIVWYcQyS1v3YwGrlgrPJseFByqcxg3H+kKLkWSfV5eu08
E2VWRnAVB+WAYkSWfmT3ZS9jHqI5P3gVumSDIJcBBBZmPZfLIWscVOCJVzKc
DD8W/epLV2bZwAYgl7quBdhn5dOTgq7NjMI2lprHTeaFeVSA0Oapao1mm7Mq
wk9Xz/eoO7DEwI7uIp7oIUXJghul2p0a0fub4guh7mFSgNgbe7EAcZZ2wOzp
26N3gf93RVBaXKoCIntpvAinvmtVZTDIC1jcVOY0me4XrPMaY52bK5nPN0U4
A7xCmSik1GXHdi2XIwk/Ye3ortpaEuJ7iSdevRL0IihvckUCQxYKlpkOno6p
jRSeEX8pWc1TRDNu23iZRcuk2hZmR1mPdLqDuDa7jVUuY3sxKU3N2dB5PYCc
cxGXeeDG6NNWbiyWCQmLsHnBS6qOueuzzhqTSxRV41GLNnQql6+2rPYlzL0Q
ICDb2th76p0euDV4maaMbX66w4DPrILnVHrKasf65FKUPKe1kwcEXgtLW3kt
j4NerZi0zHA/goYZOSiiFXBro/saLMxtK98cgfhFb+FCNmG0YMnry0QZhUrV
tSpCBpp0e1sVYe6rJ/zmKsLQWbAOghlr0tGbzkkMZ9PGXb45DcC1dUdNoEKu
/DlVTi8mleUwalvvJ5frz431qo8qVxSeDmQwvSN0I/RhjqOccWGgIB7hELGA
T7ogIQhfcISEJX/PxsdCrQKODSkJE6flTvMUDa0oq8USTvtRUIJFTCdntNqC
saZkEWYEdx2nQ+Sx1XCmXw5i4oBSE8S8z7X5NN2hA1xMccnH5ee7avqiiVe2
HnbFhXpGq6rX+cwvN1gtiAYENou50PemKRPT0jLp+Gwdkm1CqJuPeElRTAug
rgUXZ5bjG3yRIgRUeSMGLOnHpYDg/LDpYvWHEBxkOkWC6evVqqLypK+Yy5Sw
4x7vnx2qrNorxeii4NYtv4KdjxWJClsCyrS3AFr9KhrN6sLIx5ybwRRcshSn
mZeutuR1vZBSeBXhB6udZqxUSqKUikBeIcNJJyPMpXaRL9TiCVgfOwAFzpHG
OkEQPB559CfOtfZZXSp5JLpU0rd5KWmLJOh8BeO2R/web07UvKrj+hebXMPc
k34tnvu5dO07wdfXNKIv12J8cxeR+2Wr5/KloBpn7Qvnw4vA/7Hv3igYCum5
XH63UoGxQKTaGo45QRO87DbhMDtRMDPPZRPrCYOGvj8q9H1TccAYeDDsAIF4
+udioz5MTv9gKR6YAIQKzCZki6d/YCKd1nE9NP0zXEugj9GF/SpzZ+d/TlWS
bqburEiZQhAsLtLUoSxmYgbSx44cFXbLolrcKBcpoN+YcysF/MgNXXD82xL0
UXWlcHUj+sJJbxb/8EinYFtsOROtDfetF4rEeDHugr2dn3Ri0/9iPPIDw9A1
cEGeA4+VSMe4DUid0nahTKyp39/8lZA5mcgNXaIkKPuRBvoxmlIFTZg3UKyi
GZNw/e4ufBdCOJDMPqeyUPQ0+8YJPDqcsPGuqXMhsZc/OyAdJH4Jh0TZbab5
/suZ5k9eaw3FxUvWUCzk4ChEW2LabaS77jNlB1bNb8XGhUSEBGXSlo8ncbVr
i+gYQmiQfGvQeShZW0bpBa+WznvJn7jxp7K7vQldO2k7Lj+zoD9VBuzifyUD
1qS1/ssZsLa04v8ZsFeVAduc7LqYF0D4VczthDJWhSPFL0VggZDvvNJuqZJi
/SQqC7OeVrlNrhFcJmeErNmVLXVtqYtmB34F/tMXpD0YBDrpXudgtzBUuV7Z
FoF0hh3w6C7NCtvko1hSfu0S+bulGrmimRKJnh86ndiRJs5Z4gok76c/7LF4
6JTFtkpoaTGPN5JWMY83ry0TU27kVspnfeWyVKbBv0XeA1LflnARKi5klihw
Lx9jKOk7r6T0HQuLNcc0ZzHmJhAzTpmBN42CxdkZ+2PJiZHAObsUXAEaC86S
TtzgvuRJIjFA06BLe8596qXeE77ktXDMXcIW5hhvApcAIqHyPO6yBVuiwypX
HXNfrjNgC4zTjMZsO7RkrLrV0QvAUgj6NHSIsOElM/+ypbUtbtRW9IIGOOiw
OgOOeUZJPmP46oDjdJm5UM/OmjTV+kxFJYqy1mmZ5VKfFHZmwLRq+LUCZ1Rb
rqSv6Jy0bx0sWOOItotFqIgMlOCnaw288FlSAoP7G70u21mX0lwL2aEkvnrk
95Tgu22/j1mfpNLFQUJt4h+fkY+mbKsCR/+vMcGTI1i+JfoLWZ+VMvAiZH9C
Zu18G8MQTAeJP/3WHssuUr3wbVUhaUEcuKlIEg4g85M29VQlJWgodnSZU9eD
UU0dSGORDzF/3By/Lu5sU0h/XDp+2cyNJrEQSBY/rPBixy9fLDs+w+rAhaFJ
YtU8D1OegSr0x6vZs4OEocxPsj9gjYFE8zjX6PRGiuepKjAwL7bjtLtUWsXa
jKVV2BMviiFOMXxJTPv1L4kxgRGUW/7oYzFoLE4itpbrNThbHYtTFk4d9o7D
/Bt2P9mRo1eVybp/glGBuYj4je7CkWL1v1wHFAm6GM4D7cdvLp08QxQBWVib
Z/svaTj83K/AfsoGJg5BzWdNygYzHnWZzyW3UImvnEGYbyzUat67KWBvzySd
yMxPKhAwBCFGNda+BibSLSqZpObsRCjFecaNgdvv1w+zX6m/PalXzafC5pnr
dQ7FcilDnAWGlWs+iqOjSNFCpw1+JZr33n+NQqe4zNAGAr8q486ZzppGYJHS
KTXwZmz/1dOzv8Lf/wB0rOhhZW5kc3RyZWFtCmVuZG9iagoyMyAwIG9iago1
MDQ2CmVuZG9iagoyNyAwIG9iago8PC9MZW5ndGggMjggMCBSL0ZpbHRlciAv
RmxhdGVEZWNvZGU+PgpzdHJlYW0KeJzdXe+vJDexFYkC7E3EhrsQEHfZnewG
MZPNdNq/bSFAAgES4gvofkv4BA8kpDyJvP9feuXutuu4XT3T9y7Kk17y5WZm
2nbbVadOHZedfx/GQenDmP8tf/ztq5vP/xIO//yfm+njw1/+sPzx9T9v/n0T
B5P/mT7Av//21eE39/RgPKhxCNbpw/0/btQwjqNX0w/UQSc36EP0g1EpHu6/
uvni+IeTckNw2hzfOf31/o83Z63tkKI+nJUZRvrR32/om/t/UcNqxJbHg3d6
8NMvvjh+cjr7wfmo7fE1//mtk7LDqFw6/vhkBu3d6I5vTuMQk1NKH5+e0mBD
og+/dzorGmry6XhL34/ejsYkel4P0dnkqVE7uKSDoZ7KXy+5o4/rh8sjOh6/
/G9qycdkoj++f1JDDCqFOiR9fI/6HIfkvcpf08sanY72dKaX8sHr4/OTDo6e
inlaVtOa/BDi6GlSp7d/pzb69HS2g1VWO2rU09s5evnv5w+DVz4cXX577TyN
7/38qY/OhOMHNGhvjaKGyui/Q3+FEFKkuTH0SAqBvj3Tgo+eZunnpzh4E4Kn
H9LY6SVzN7SwKZnpD0vL7o9ffk0v6YfR0qfTfCgzhvlvmm+dVB2GHdUyYk/T
vfTkTPvYPKhkbHlj6uK7ecbiqJQ9vqJf0nq60D713olmTlvdvP0T6ksHTbOD
Y4QWPswjTNFvDoZ/AK8wT6DzlsZFDzmy5GPIdmKcpWHbUxisc+1rkyGQHaiY
zaeuxF1tPY/PDjFGWqg7foFvk0klWins86fVzD6ZnEkbas2FYiavcptk2q55
D551XjduEmfnDqakft/MyNq45ikpS/WU2g/WB716J3xTYSWwizo/n1BbKqVR
w1jYPCabNUoZXDz+If2lqZ/gJsQhvxusiRPi6HmmwKhup5eyyYbji3mkZDMf
00AnPKmrF8j9y0i1cq55mcVHaIrvuLXnNMYUxhCL19HX8XR2BARWOTCvpQef
FL8+9TQhlo4RPPAFL0B1Rnbp2TrMbMb16cU7bNsmIVIgB6fen5/OgWZ6jEFs
Crq8lUYMFnugIaXFvGZMaxFdU+uH+z/d3H/6BYL455fx/CPG85/n2Yvj6BR+
+iNyREKasAAyjSCEDWSvHb2sHz4E2cv3d9w5f70T2dXoBjImRvbSqM8mFxyF
ysUkpzl9c6KIqnV+O3ApcB7GcXAd+mHyk0eUuPHZZKw2BLAxfvRFXdmBuwbP
mkNEtGqxRYqe1Ax97VSY7KYgwDOaDhOVa0bLSEafVlQWAfwJ+xQibXXWFh/N
oEYT4XHuCfBpiY6jwQ8BlGAg/CI6e0XylrAM5ivbZKLWDRmNoReHBhfEsE0Q
qSCAKJmm8RBEZHvWA1EjrWj1JzwnbhS9LsbxOfEXY/Js8V+H/LT2atPLzsYQ
wTHhQEyr0qfXSGUEd6uu40MxaS3To0F6/Id5tshdySG+S0+rkOEGiBg6FP1A
07u4DOd5ykL+8AX/lht4mr+nnlwC39tN1C46IQ3cmZ5d/ep0NjlSG4PsqbHf
atXsPXeAiwVrO0POY4f1lp4Gr2aHfCITLOQUQLb6AeZoeYdO3QfTO4kJMQFc
4ESRwTqJEgG5rE//tBJeZh/gIRBUOOLB0PFNoXv2IZlfwAB8pv4UaC1gl9gV
jKrOqVeLb2maegrlxVB+NnlGsPr4KcEyAU5EzwSYahy7wjrPfWNnZX4Y0Hpq
kQEXVrEBzPImzeLV/plHLYtnUlk8j3x0RZmMyqNCygTWWRbfN0TpBVOfD/Kg
42jFVZ3Y0zysODH9OemgEf6E2HMymv6ajTOvaR2gynM2jolmumHxdVLYpQYG
9+PpnAZa/YS5D4By+Qjyqsb3YOyTj62sBzIvTsduRcLL2MC9fpoJTSArtS1L
LkHyTf6eUFNO5oDuX/ed5zkPV0SZ0U7YeC/gyRVLnOMWUYFY3IRTL7Z4TVOu
kieEFrOheXEVrW7LR4u/E0ekqJHiNI9aZdcOzeBWpCbDmjtp6pOsuPnhau3z
2GK2RYL32BKE+o4wi+x4mezGlIzaCsPLnOQo7HwXhcUwuj8Ki5z5/0sU/vWp
/JjSyWCNr0KTc4vQpJIeLH1vyOdmnWn2nzB6cj+nHeVGUo+NWkWwOFhLjajc
1tQKKCAYQWheCRH1xQjifNrIi/jNiPqRFyY12paATmmZGTVEA0EoAOtsSWsx
5M8yXBjlVQBnnTGEHvJN65W831U3Qc+E4UOEFIWQL081B2Lnq8NvUtZCxAVW
vAOAWV1ihBTJ/a2oreDrcb8cyeGV8bE3i9JC/62qICfRnx6OnXcIpg0aXwO5
gjOr9xbZXYnry1Pk1A39XOU0usyEczZ28TVqU2KFiWtW4G3WUJEV5DFnejXN
79S7sZeAOS+KqzJLC8xzgGIZkiY3ZplCE3wg5+ih2WB43SFDJF10iJcSkI6T
mwZFA3hG5kHkxvo1OE/01lyETEUw8CgdomLQIyXmONCEGntFhyAXcq5HX4DA
1ydFKGHJsnrlz5kg0yegwUsWYA0wO8CopidC2CxCg+UDywN6gGItAg/LEou9
NbAl6M4inWFUY/ivLSKAOBksoFMxG4LvZY4M+ossTEAIeZZjuMtzDsjBKAQg
W0eyZtgNVCsyHOXGcRpRkZetqukPRwrUpmvbsLICG4M4wPRchEF4Q05CeTlQ
FKnYc5WNEZgNPuiJji2aSOP6xUuvUbBOLqTPxrx89Jcy23CxNNTCxcLAGoYF
LiFRrB4uLm4j0Z/Ranby2voejuXjEO3BhVDp0d2crxhnHsCyaHSEty7MPPir
LdFz7WaZRLm1Z+ZnWD+7a5yl5GdSqnQn4hcmpKJUiiwq67BjFCN/kw9tcKhE
6+4JV+Q9MBnJKkdjRoQcaqXbI2o11ElURWX4weELmRJ74WOb5/TpmoyZhfIQ
3JaM+X8draddbZMF3jMNhJwq0tOCMwRDTmJTcUEAN7a4X+SlzAAScdFR4Ia0
QpAJznmINFc11M0qxGx9xoPvvM6BlFjY1YD+k/xDSmGTlXYY5kih2p0I3tBi
1B+k0IoJT7sjUJgy0Ff2l1uprWXqQtQwNe3eb68TimkMaGYfNsG9tAWDugXJ
kRUOacegOLO8Ifvxop7k3X5VTGQ34+/2cYVd5B172wIe+ZMeyeZ3kJ9O03TN
9Laa5kVl+t3cgY6eWJ64443D7zclTbvWoHAyIVolMyM110qcuNULG7m3NV+B
zMROnjTSepcpbPak2q3uMoInHdKWbWUUF1e7ym1qWhzOo7duLn6zo7lEuq6u
ofV8OSSX5GojItMEqLz0EDuXmJb3kNdMdJZXiomBX/H8MY61kaRXUw8n7Yim
Wi1FEUL4zFdm1yKAvv8XBZblM6CCr69UF+0X5sxGhGKCSAzKu+TWud2SIDxO
grsSoS5lgdRwiv1u9C938MOQyDoOjnLEhR5OwJ4zhpAxdC8/jBSziR/mVa4q
3DXBrBqzTPYEA9/J9bK3oeouyHHXuR4knlOVRUibZE/Qy3qqBw8LpOxlrn9Q
URl5WwixQXhaZNMQasU0GRBe3oTAqdlB9WiNjU9bWvkG6/ODVyrazqUu51wS
6SttQkePz7kCjYs8uRdWGCUBBgVyxXyaQW5DmzxPdQiuphXI+zj4VyVpXwBY
awQr5rdrF27mfnKBnbRXjcH9SRfGW033cZRro1DjrTbOeWuZv2Wv5ZG0tW4z
5TNZWGtxNz8Oaj2QnCcyi81LnnyTNGAtpFBCgGyvdAkTskl8S+9gXHXG5U2z
y4UGWwxdQpgVaNFykfNTQ2Ec2yo8geCadJ311ZwIKRnsa3P1HjoRy9l9/tv5
26Sb+YQ/WFdN+Hb7CEFg2u9sX1UghFxIuYpxTTFAkcubOuGeasGeFhhXv+/S
bnxzn1tVpRt4JIxlB7tcKNOva4X5D2b8ppX61gTVinLf39bPJD1Ujp2zh7rB
cilWG0WFrXQe5WPjKC/jIxWTMmSZ2L6dxvlkLr00CYVLjrwcWJvtZPrh6Lz6
ZnaTybNNiILWua4FyqXuuJNbbFrcyI1Y3s013/O2oXcGO8Ki+RI5sSpFdDkh
v36YAvBWKiLCtLgfAgYulC0u2JmFTfQK1gtrLvmIMqwgV6QvRTM0PRtF9Bvx
e/bqXCFRbAReZKs0tApVjI3boWn1yrentUqxWk/webEBAGnxjMOWWjvFO73U
vucEJMFpm6b4vYfhSfHoZ3OuDcZ92xVC0WwvmzAp7aj//hiptkDvz7NhWfrz
2zQAF0atsO76o4ot/DVw+le5TR2zfHntjI9Y2PqWZ3xo3INSQUSpMIzJFgt8
N09ezDXj39gRH7HirWzstdWmEjlu6UZ1D67Kqnu1Fj3lQykSysRSrFLZcLDi
qXV7ZuOIiYiHn+Ts3CC0PGALUyC6XB4Kc8vB5zMaY7Q0oFqVmGMo+O285UoA
pap9XC28F2ZlQ7IVAsbFnTR1da+LFwotYcW3bd4cSci3l0kmlwRsmRdQ2Shy
ZBBjW41WOK/DaizIn6xFCjltX6KkGnV1Xlc/+paKFkuBxmlhy0+vVaGsik8e
VZX/8rLs+IOcHvukaaYmkPSJ6Mp8JjK7HLO3DxdctdflxSIqDsDJpI3nTFW1
6nXFH+7RFTWZiolkpf5tdMWQtQFqx+Qiv+3qvj55Xsvc9SE+37ZVny/VCG8k
aNwZaCpbiEmvrEZl2j0oETH7Wnx+VcTLKjO0Qy1inlBQ0xTi/2cQswt1+R0a
WBF5sHhKUuBiwO+goA4a+mDBXJWTwGKs/OpieQqwp7lz5yzOzbDWqafhz9zI
u7gBB2djUmYP3+SpnR+TMaVMorLkTQwgnzJ7OlUSRXJMij3Zmmlp2hPTOwtU
hl1JW6RZ0T70OMHBEkyeJfqeGU9nbrjuHHx2H8256LRwmHIRY3qfzaj49ixH
KIdFz8ACYImdbZwfLq1eUTb3nPUVqn5fNORB2qSVtMJrgiqXgwkn4+7kLt+2
fLrYHI+oqZ6W2NDqSOze4unydswZoZoNIAYS7BWxykgdG2IF5AXO4jBJgpPO
7VbqZNO2iS6ZyeR0JoSKggoPMvMBYRAt2T/BAeeTHzQs8NRW2u7duwde4rUv
86wk8onQUdzcOe+FyNL1jrLgvPfUHU8WqdV+5D3sZmZNzlpeemNLimlY/foi
zBK59sH3MCuf2O+Fi7YWX1JpwWZhUTbFaUnzZmfqSn26A9IUpGgEYV6dELQH
wL1++QB/KlayrnW8FZXZEoh6RVHWd6XqFnkThrtvwkl/RHoD2IWSWvng8/sS
yF6onuxBtHRVNHqLY25QtGyJP3ZLXahX+tkMVtFuFKIzBZ6XNt8rALLuUp9N
5rRkxN7HwmyNdSWtsz4uyBSjsguMEBDnWUAchkse+EaJcVKKvIrrgxLS6cgG
cgto7Gy2P3RZ+M2ygzBq3KlBMKSIEvK9PSUjC0sqFcasHeoYpoMTOZNyFCpp
lex0vpWWccyjfpMX1MdJ76eRhJFmbEIYY72e7uChBaXxh2lt0pBS9uC77MvJ
EBQ8m+i6zQEAGng+uZjPoWYusPzd/c2fb1y0B21i3og42DAe4uHr/7r5x47b
i1b1QU3KuLyn1zlxnN5zDdSTzviKgDiGvEEupeIH8S95GyavHY0+gXjIGfh7
2R6SJX7c3DKx53BHJOsYUxD2QjhuzydwQ3vuvC2tEcRHNhxRh6u3kmxsVsrJ
JvYqhfZ+37XRbwAI5L2DWwkT4cyEnHGO9CcthLYIr8JhCTGd3QAy/BiL3Xpm
uaSzTTEkcG5sqDlYf+XoXDkOXq7j0mausq65r0TF6/Q2N3H0IbRd9JJsNRdA
bRSI7wzMnMXLm6w8VcCbxRsI5iCr01j7NEj7Yfb4w3lIeUmWdJ+I07JOOnbC
Zw5z0R1y4FVLYOiPe6/2Ui6roG2plZDALsPS3gBTZ41V2gXgnAfS2IZKw0m+
smLgmoVVY5vPMrjTlNl1agiJ9oohuQYP2sJWAUbm4xSuLXQTbypiEHt3iiPW
OgSxjdz5smTXditfNPYAQ57ccKQZc1UvFQELrFeke+yx8uU7TT4unc7YEA/q
oLdS6SJEXANM6QzfXpDdvPptxzUowr42NCeVhTTH9Hrp4vrp3Cv3uG1EB65l
L3clLmaRj5jE2GX5MpGEzRLBeLsfS2dx+dPOEDKJ4CjTXwqCe5G4GQmYAXUW
8Kd4y1mv80zvIi9f6cqtRZlVp6Dd7XTZ9qWHzjudblTCjZsDq3kx0oFu3Fq4
sAXHt/cJUvdtPUlCWQMWLcn37ZXmxVoMEFcF/N6nOJZxdTeVtdwCE+ilqM/o
xj0uS4fsiZLLco8wDDERf8C9j5vJ8INhsKluRQ4DNKKsaKYR2s7L2nWw456c
Fgn2Hj1pLzRsvE64NBD8Qrhj7s2JGjdx1ZF8VcMlGdtphJoePdst7ktQ5YPt
kojs6c09XMKpZXhPIRtBU0ISL1xTKdcXNTFtU8oSp2rGABq9dn1pcXOUqhgr
dsZuudx4op3fHbTaad86tiVkZHL5sCwuXSwrfeD9rXuSqctlMeKG6OYsCYxO
Wkez6336Ku6tqrj2KincyJiv/yrXnFkvXSMr5BnTi+ck0pvrx+6tyT/Iu5rU
49w67Dp+VHYdty72zNmmT9ovnUenNiSXKq8coCTiERdqFL1H20aYX+k9tIgb
nRdd/rBPl1c0ucTxel1e1NVDHge9hmmFBkn1a66FK03xdRxS3RjfNCpXlQli
K2xZcaQT9zi54skdxa10EfG3Tu8K+6FIOR+iBgFikYkqCnnbnAxuaSoatlRI
+wuCUa+Msm3Fby/xbJX8ImuYNRr6WYg9ovNKMN7+noUP/pCHBEdmyhZftA3i
bNys+B/XoHxzro2ztDn26BRZYbdZcg+NlLJ4QNbsQSq5rSctELkWtSBJgDsR
G2gBbyEqQLN1S99Kttlynb2yjcGrQuXaTeHYIgscrWrDJS69ngpch6P3plQD
h4fKndHiIWSxmvC6UiO5yFIWa1H8ZFdra3mYD8zsJ19AXOsn5RLVDf70mBIj
+a7HzcvNJdnl7dMtScK4RmJFKXajjBbst9CJK2nfQypJ5BQAKCjzUglFG/5Y
b3xs6CMoWFX1/c7CfMbBrHW36XsgSW1GRn0SGEzC7vwQ1FrId6QCEqxli+Zy
+A10uixGTmK1cEVFc+27VOGENxALu+2Xi8fl+3QgMQWI4VXhNueJ9mklAK8y
85Vu1Ccd7XVlbNzckZwxoHm8mndQ846ucC2huMMvFxM2sWE2LmrEJ6FmSXKZ
K1svG57bW5aoDYvSbUcSH5rliTXp3bU166aai2vme9Q3ZH5uSj5BfA1Z8H+X
8RidDdOb0uY7vAf955v/BeXMi0BlbmRzdHJlYW0KZW5kb2JqCjI4IDAgb2Jq
CjU0ODkKZW5kb2JqCjMyIDAgb2JqCjw8L0xlbmd0aCAzMyAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nLVYW68URRAOIAiLgcPxAni4LGDi
DLJt3y9BQ6IxJOqLZN/AJ4wkJpiA/z/x65nprurdXsyBeM5LZ6e7qrouX33V
b9ZSKL2W+b8sXr5effssrF/9s5p+Xj97uizevlq9WUVh8t/0A1+/fL3+YYuD
ca2kCNbp9fbPlRJSSq+mDWqtkxN6Hb0wKsX19vXq+fD5qJwITpvh7Pj79ufV
RmsrUtTrjTJCYtMfK3zZ/gXBSnLJcu2dFn7a8XzYjBsjAr6l4YtRipicUno4
oeXFUWkY6+xwZtzAbOmlGu6OGy+cj9oO69kOE7CywiUdzCDo85lRi+hs8sOL
vyHUJ9wqDJdHJWJQKZTvOhZLTFKwBDql82rHEKGCtYqdaewo2mll6urWqIOD
yphdtetqCb8GB0dPHjlbpX80bpRIPhg7nB9xQGfln2QvOBViGI5Hhe/R+0Fi
Jy6n8GN35+XRCxscnHx2caJPuNAGmqRSFtcski6MCJ+SJg4v3kKoF9Imw77P
knzKq41FGK3MmhBQaxSkKyukwr72NJyonceV5ss5b4evs3akj1bDx6N20KnM
cA2HnEha5RgWlXfo+BRDZWSA1I5+Va7njBlu55tIo1M+tYEwaaSGsCKWvJdt
tSLGaAKXeh+6bEgumMbsKLwJobn/ySELi6+qg26NRqQgG0NfjDUbz48bKZKK
OWXu5ehrnDIwOqeNNvmsL3lyiRwMpbiLxsHhq2xV8ipZZjQcjMxOyKMr0B91
tI0BF3En41C7/CJtIhT3sA3s/k0ocCxKKDhwDHJFQnYrZt9ybedsXLbqJA0i
VJfYq3HZ4CaoMVbCYAWocbMvHsy1S0YhvRf/ORh1NIca6T9Lt8mGxSk5/pfI
UPqR7Fxcqr1G+JCeak60KdOdHh5OcQBI8DLil/9mBHhqrWpyZbCqGXE/n/FW
uubMkkYaPoF+L5AckMqKdzY0pLiENIXAbHo0bhyw2qsmoTeAIxOzw7mqagkh
xzp/1V7qxNDoUzjEROV26nFKPKOagge8BlQJLJ5rKGpcj8J9IDPujQlu9NjA
AsKUHXdz71y2OgabGPg8nutFJRFkxVXBj1NhlnTlpceL+ACQUXncGjcB8ZEx
MAuuZQODR+YuXtXhAKBycDo/aiWsNAf3nrqkpuuccB8WWaz+yQnMr4S/jWeY
XR9S6pMwchfDMr7BjRpORqRyRqLyLECgA2uhgbXy9cbUfJVxw2fTyspUqcqS
GVkmqNOUHk0/wsWSSTWMCpRBEHLcoSWvU4Y95JpSSqn0PpvcYsYuMQJ/8uvt
r6vtw4YWXcAxF6RuyAjRmruMd3RIUUOFKn/a4UJTnzSHuBBjZYUWcS5UIeku
Y2IdWsQseTcbAmKAZFY2xPjK+7WpQn166EuQ2a84gr+U5SjlmqRYktXDT9fy
dzi0qSxiC9SCCRoYIrXlWrK+aeZVKCU7CaWEowJYmmIGVFbXjFYc1Wsyf83J
DxDab4tZ0V5bzMatx9wAk2lYxbv6hZrC5YUOmgJzkHO1kZ2pEL6lUJLkVJ2j
QP+57HIdvZK8daSZgSrJuzmzqg/XTC1b7rQUdvOaaeTthiRXJ9L3K7nNgM1G
W1AM85swaUYxbf8XFCNaXeDm/jxpRGWLgpgYBeGSJJYoHTAKXie19Fg5clpV
y323djLXaW5C88FuL9WR1z2bg6icr+JzsD5oblubaEzqrndcxRifEmvxDZup
dUY516P/D0bENdqpD1dD358JLGjIu+RUMRYzRlKlYnoNs8+v6HIss3uz33fE
g0q9+MDECzZD7p9mJdatiT1Ez+5kFjGHdsNxzMurFDtDSA5SLQ/vl23Bw5Me
odqtWgPBzBO367xHRPO/8YoNRsyqhV+oyYAeq9iUyGMhwkJ2buAqKbfyNNys
Tf0mdfqrOXlR5Emx95fr03uBT+Bg11GbUJ8rd5N7lQPMn6n05szY6evQHm2h
N83LxlR+ASSBNReawwh6qP93Rl8CFI5cJRdM20Su5AxISbbVRVzgat5qldWO
Yc/RLiGeu34FJAYN+8kGobUfsuNTGQL3DP/xUm2MDS0ugDCHWc9PaLM7lxcE
Y0zjTjYB36kTcN93bMYlh1MQ+IxZSeQHvB/t0bFTThKWKFP22DvrHK7fex4g
HpRL4AAPKoHf40H5R86D8njuDQUm6RKYh3kOR5bb6iJcfP9tQNnYzd72beDD
wlbc9ggaowXU8gC0LwP7Ax75OvIeVmR+mf2rdUxNp+ezZqey+vVCjxBtsys2
dbTfrsnfh9AmUVpin29cw1bLiaXLBL469nofAsXYFD0xkfvZYxNJOjdRFGsd
vdek4ecsU+VADk/qwPSUBqbrdbQK+Uegsck/lp1P2Kqe+bH++H1n443ekZvs
vXr3UcNpBsDMChZRih1PcYKzhXHDDw3RO+4BK2ucp6HZv0zdCur4eMI3UK1T
D6cVDTKMvhGB8k4XAkVTHGVS9yXocf7R5Tcwqut29CjHj/rjIG+KhVawrr+f
6NMpInicwLHGcsB7AjI1V0pz7c47UEcWM6vxXzG7yCovID9tV7/h/1838QKb
ZW5kc3RyZWFtCmVuZG9iagozMyAwIG9iagoxOTEyCmVuZG9iago0IDAgb2Jq
Cjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NS4yOCA4NDEuODldCi9S
b3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BE
RiAvSW1hZ2VDIC9UZXh0XQovRXh0R1N0YXRlIDEzIDAgUgovWE9iamVjdCAx
NCAwIFIKL0ZvbnQgMTUgMCBSCj4+Ci9Db250ZW50cyA1IDAgUgo+PgplbmRv
YmoKMTYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1LjI4
IDg0MS44OV0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwv
UHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDE5IDAgUgovRm9udCAy
MCAwIFIKPj4KL0NvbnRlbnRzIDE3IDAgUgo+PgplbmRvYmoKMjEgMCBvYmoK
PDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1LjI4IDg0MS44OV0KL1Jv
dGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERG
IC9UZXh0XQovRXh0R1N0YXRlIDI0IDAgUgovRm9udCAyNSAwIFIKPj4KL0Nv
bnRlbnRzIDIyIDAgUgo+PgplbmRvYmoKMjYgMCBvYmoKPDwvVHlwZS9QYWdl
L01lZGlhQm94IFswIDAgNTk1LjI4IDg0MS44OV0KL1JvdGF0ZSAwL1BhcmVu
dCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0
R1N0YXRlIDI5IDAgUgovRm9udCAzMCAwIFIKPj4KL0NvbnRlbnRzIDI3IDAg
Ugo+PgplbmRvYmoKMzEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFsw
IDAgNTk1LjI4IDg0MS44OV0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVz
b3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDM0IDAg
UgovRm9udCAzNSAwIFIKPj4KL0NvbnRlbnRzIDMyIDAgUgo+PgplbmRvYmoK
MyAwIG9iago8PCAvVHlwZSAvUGFnZXMgL0tpZHMgWwo0IDAgUgoxNiAwIFIK
MjEgMCBSCjI2IDAgUgozMSAwIFIKXSAvQ291bnQgNQovUm90YXRlIDA+Pgpl
bmRvYmoKMSAwIG9iago8PC9UeXBlIC9DYXRhbG9nIC9QYWdlcyAzIDAgUgo+
PgplbmRvYmoKNyAwIG9iago8PC9UeXBlL0V4dEdTdGF0ZQovT1BNIDE+PmVu
ZG9iagoxMyAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagoxNCAwIG9iago8
PC9SMTIKMTIgMCBSPj4KZW5kb2JqCjEyIDAgb2JqCjw8L1N1YnR5cGUvSW1h
Z2UKL0NvbG9yU3BhY2UvRGV2aWNlUkdCCi9XaWR0aCA5MAovSGVpZ2h0IDkw
Ci9CaXRzUGVyQ29tcG9uZW50IDgKL0ZpbHRlci9EQ1REZWNvZGUvTGVuZ3Ro
IDE4MDg+PnN0cmVhbQr/2P/uAA5BZG9iZQBkAAAAAAH/2wBDAAwICQsJCAwL
CgsODQwOEh4UEhEREiUbHBYeLCcuLisnKyoxN0Y7MTRCNCorPVM+QkhKTk9O
LztWXFVMW0ZNTkv/2wBDAQ0ODhIQEiQUFCRLMisyS0tLS0tLS0tLS0tLS0tL
S0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0v/wAARCABaAFoD
ASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QA
tRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0Kx
wRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZ
WmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKz
tLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6
/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQD
BAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLR
ChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6
wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIR
AxEAPwD1Siik70ALRRVe/u4rGzluZziOJSzUAPubmK1iaWeRY416sxwK5HUv
iRpVqzJbLJdMO6jC/nXJa1qd74nuS8ztDZKf3cQ7j1NVk0K3ZQMn60nKKGoS
kbFx8UrksfIsY1X/AG2JqKL4pX4b95ZwFfQZBrP/AOEbt2Hyu2aim8LxggiV
gKn2qH7FnZ6X8SdPu22XMElu3qPmFddZXtvexCW3lWRD3U14yuhxQHIlY1o6
VPeaPOJrSUlf4kPQ/hVKUWS4Siev0VQ0nUYtTtFnhYMMYbHY9xV/NMAoopCe
aAFrkPiPM66VBAH2pNLh/cAZrr64D4nXEU9vBDDJulglzIo7AigDnYBuVAvI
A4rVtLYvy3ANY0ZeDZsXcQOlWBrVxaqDJFC3PRX5rC1zo2N2O0Ctw1SSWueM
iqumarFfYEsXlt2w2avXVxa2yF2YtgcLms7amt1Yz7uxVV4IJNZskZjJPpUk
3iJJZTHHakHsS1QPcSTHDx7fcHIqrNGd02dF4AuG+33UA/1bKHx713VcF4Fk
t7a7ufNbbJIwROOtd9W8djne4UhHIpaKoQGvNfFYFvqk6SLxPJy/oK9KrH1v
Q01MrICqygYyR1FRNXRpTdnqcHaQpMpjI3Z75pJdEgSERluA+4AjJz9afdQy
aVfvBIeVPUd6urc26xB55kVj0LGsbO5tdWKUls/nLKrBW4GFXH6UahbyXTru
k6djUDaraWt4A06Sr1LZOTS3+vWUs6KpUL3OaTUhqULEpsEmuFlJUSom0fKO
lILVbSNlHJPc1Ziu7Tygq3CSuOVOecVGN15OsScliBT1FoiTQVMmowxKpI3h
i1el1i6RoKWDrIzB2UccdK2q1gmtzGpJN6BSE0tIa0MxaazAdTQx9KoWSPIh
ll3b3Y9ew7UWJbOM8dXMTaqqKPmRBuPrXI3Nm15Kp83CgdK6/wCIWnPBdxak
ATA4Ecv+z6GuZFs5AkgfI9Kh2uaw1RLaaXbxJlg5P+5mn3GlW06fccN/1z4p
0d7fwqAFyPamvqV7ggqwzUGt/Iy/7KMEoaJyMHvXbeCViN47SYLKvBNcsgll
fc/T0rpvCNrK96ZwMQqNp9zVx13Mp6bHoKsD0OaWqpj+QBCQQOtIJJ8dAa0s
Y8xZcEqQDg9jTYgyRASPvYDlsYzUlMk+430pFMTd8uaXGPpTFH7oCmz3KxEK
AXc9FFFhXI9Rs4r+0ltp13RyLgivLNS0+Xw/e+TJuNs5/dyensa9LurW7vY2
RrhrdWH/ACy+8PxqjPohbSTazD7cV5BlPzN+NDjccZNM4YSMRnhvcUxyW5K1
rS+HpIYfOtVkKd4ZPvL+PeqkYUERiBmnbgIF5NczTTsdcZRkrlACWWaOJBhp
G2qBXpek2K2VpFCg+6Ofc1l6H4d+zyfa7oBrgj5E7R//AF63HuBA6q0ble7K
MgVvBWRzVJXZcApPLFKhDDIp1URYWmsCQcfrTqKCiLbIOyfrTQkgJIWPJ+tT
0UARYm9I/wAzSYl9I/zNTUU7gQFJT/DF+tNELBtwigDeuOas0Uh3IgJe4j/D
NKFf/ZqSigQzDeopdrf3v0p1FAH/2QplbmRzdHJlYW0KZW5kb2JqCjE1IDAg
b2JqCjw8L1I4CjggMCBSL1IxMAoxMCAwIFI+PgplbmRvYmoKMTkgMCBvYmoK
PDwvUjcKNyAwIFI+PgplbmRvYmoKMjAgMCBvYmoKPDwvUjgKOCAwIFIvUjEw
CjEwIDAgUj4+CmVuZG9iagoyNCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9i
agoyNSAwIG9iago8PC9SOAo4IDAgUi9SMTAKMTAgMCBSPj4KZW5kb2JqCjI5
IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjMwIDAgb2JqCjw8L1I4Cjgg
MCBSL1IxMAoxMCAwIFI+PgplbmRvYmoKMzQgMCBvYmoKPDwvUjcKNyAwIFI+
PgplbmRvYmoKMzUgMCBvYmoKPDwvUjgKOCAwIFIvUjEwCjEwIDAgUj4+CmVu
ZG9iagozOCAwIG9iago8PC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoIDU5
OT4+c3RyZWFtCnicXZTNbttADITvfgq9gZekfhwg2Et6yaFF0fYFZHkV+BDZ
cJxD374zw7qHHkbAaEktP+6K+5fXL6/b+d7tv98uy89279bzdrq1j8vnbWnd
sb2dt515dzov979Oz+V9vu72L1/n66/f19YhoK3pv83vbf8jDnpjmbNcTu3j
Oi/tNm9vbfdcSn1e17pr2+m/pSky47g+Qq2mSliF9ZoqXmijpkrMtH1Nlf5A
O9RUGZU71lQZJ9qppsq40h5qqvQD7VNNlXGhnWuqTD3tsabKqOClpsrktKea
KuMTbaupMo60a02V/gRr6AWFVdZsYDXxjloFq4l35L4GVhNvLwtWE2+wGwZW
E2+wKgOridcJaGA18QarMrCaAINVGeBMgAObY4CzBGy0gDMBOrthgDMBDkEL
OBPgpH0BZwnIbuCgJOTyUw44T0DmOuBcgJMs4FyAAwEdcC7AiTU74FyAzl45
4DwBieCAcwH2+hQAXQfqygWri7dXMFg9eVmzg9XFO2kVrC7ent1wsLp4J14z
cEiwbDu6KyGYgDgKCavMxbWVwHukBWuId2BugDXEO/LLAdbIC8w+4xglrLKT
OCgJq7zPAdYQr/OqBFgjL7A2AmskL/Hxf0jYl60LsIZ4e96NACvlxRQM1hBv
KBisId5BZYA1xBu0PVh78Q5sHUqTgM8icQUkrLIqnIyEXJ4RfjUJwdwIJyMh
mGWg9xKCeRnwT0uomb0ClgR89hnvJFhtBLg+AYsGzWOicOZweD1mVbd83m5t
u2vCaYJxcp239m8IXi9XZnXQ7g/OCDxuCmVuZHN0cmVhbQplbmRvYmoKOCAw
IG9iago8PC9CYXNlRm9udC9OTFRKR0IrQ2FsaWJyaS9Gb250RGVzY3JpcHRv
ciA5IDAgUi9Ub1VuaWNvZGUgMzggMCBSL1R5cGUvRm9udAovRmlyc3RDaGFy
IDEvTGFzdENoYXIgNzUvV2lkdGhzWyA1MDcgMjI2IDI2OCA2MjMgNDc5IDQ3
MSA1MjcgNDg4IDIyOSAzMzUgNDk4IDM0OSAyMjkgMzA1IDg1NQo1MjUgNzk5
IDUyNSA2MTUgNTA3IDUwNyAzODYgNTA3IDUwNyA1MDcgODkwIDUyNSAyNTAg
NDU5IDUyNSA1NDQKMjUyIDQyMyAzOTEgNDg3IDQ1MyAzMDMgNjgyIDUzMyAz
MDMgNDU5IDY0MiA0NTIgNjMxIDM5NSA1MjUgNjQ2CjcxNSA0NTUgNTE3IDIz
OSA0MjAgNTI1IDU3OSAzMDYgNTIwIDI1MiA1MTkgNjYyIDI1MCA1MDcgNTQz
IDUwNwo1NjcgNTI1IDMwNyA1MDcgNTU3IDQzMyA0ODcgNTA3IDMxOSAyMjEg
NDk4IDg5NF0KL0VuY29kaW5nIDM5IDAgUi9TdWJ0eXBlL1RydWVUeXBlPj4K
ZW5kb2JqCjM5IDAgb2JqCjw8L1R5cGUvRW5jb2RpbmcvQmFzZUVuY29kaW5n
L1dpbkFuc2lFbmNvZGluZy9EaWZmZXJlbmNlc1sKMS9nMTAwNS9nMy9nODU1
L2c0NC9nMjU4L2czMzYvZzM4MS9nMjgvZzM2Ny9nNDEwL2cyODYvZzM5Ni9n
MzQ5L2cyOTYvZzY4L2czNDYKL2czNzMvZzI4Mi9nMjQvZzEwMDQvZzEwMDkv
Zzg3Ni9nMTAxMy9nMTAxMC9nMTAxMS9nMTE2L2czNzQvZzg1My9nOTQvZzQz
Ny9nMTcvZzg1NgovZzI3Mi9nNDAwL2cxMDAvZzQ1NS9nODk0L2c5MjAvZzE4
L2c4OTUvZzM4L2cxMDQvZzQ0OC9nMzkvZzQ2MC9nMzkzL2c2OS9nNDQ5Ci9n
MzY0L2c4Ny9nMzYxL2c2Mi9nMjcxL2c0L2c4ODIvZzYwL2c0Ny9nMTIxL2c3
NS9nODU5L2cxMDEyL2c5MC9nMTAwNi9nMTE1Ci9nMzk1L2c4OTYvdW5pMDAz
My9nNDE1L2c0NTQvZzEyMi91bmkwMDM0L2c1OC9nOTE4L2cxMDg1L2c5MjNd
Pj4KZW5kb2JqCjQwIDAgb2JqCjw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5n
dGggNDgzPj5zdHJlYW0KeJxd08FunEAQBND7fgV/sNMNDGvJmotz8SFRlOQH
WBgsDmYRXh/y96mqzuaQQ1kqNwu8Geb88vrldVvvzfn7cZt+1nuzrNt81I/b
5zHV5lrf1u1k3szrdP/b9Hd6H/fT+eXruP/6vdcGF9Ql+rfxvZ5/dEn/sfjN
dJvrxz5O9Ri3t3p6Tqk8L0s51W3+b9R38Yvr8rjUSiR5KqheIqlrWdsSSV5Z
uxJJfWbtSyR1muYSSdlYhxJJeWa9lEjKPetTiaSuYx1LJA2q1xJJeWGdSiRl
PXcukdQ5ay2RlJ9YlxJJA6eGtWAwvbDCavL29BqsJm+eWGE1eTP5BqvJ25Fg
sJq8vaawmrwDRQaryTtoCqvJ23E1DFaTNxNosJq8vaawWni5kgaryduOrLCa
vAP5BquFV0BYTd6Wt8I2KqhcDYfV5W35Vg6ryztoCqvL2/JWDqvL23JxHFaX
t+XSOawub0+Cw+qxvwMrrC6vcyUdVpe31xRWlzdfWWF1eQc9CFaXtyPQYfXY
X/Lx6Sl4DT0XVg8vL8abKriYnwrWQMGUzwVLwVtxB7EGCqbcMtxPwWvoYljb
+J41hbWN/b3oLD0ODY8Vz+fjODbT53HU7a5DrEPKw7lu9d853287f9Ugpz+p
mf3FCmVuZHN0cmVhbQplbmRvYmoKMTAgMCBvYmoKPDwvQmFzZUZvbnQvVEFN
U1RXK0NhbGlicmksQm9sZC9Gb250RGVzY3JpcHRvciAxMSAwIFIvVG9Vbmlj
b2RlIDQwIDAgUi9UeXBlL0ZvbnQKL0ZpcnN0Q2hhciAxL0xhc3RDaGFyIDU0
L1dpZHRoc1sgMjI2IDUyOSAyNjcgNTkxIDY1OSA0OTQgODEzIDUwMyA2MzAg
MzQ3IDUzOCAzMTYgNTYxIDI0NiAzNTUKNTM3IDUzMiAyNDYgNDE4IDg3NCA0
NzMgNTM3IDM5OSA2MDYgNTM3IDY4NiA1MzcgMjc2IDQ3MyA1MzcgNTA3CjUw
NyA1MDcgNDc0IDUwNyA1MDcgNTA3IDQ5NSA0NzQgMjU4IDkwNiA0ODAgNTM3
IDQ1OSAzMzEgNTA3IDUwNwo2NzYgNTA3IDMwNiA1MDcgNzQ1IDQ4OCA0NTld
Ci9FbmNvZGluZyA0MSAwIFIvU3VidHlwZS9UcnVlVHlwZT4+CmVuZG9iago0
MSAwIG9iago8PC9UeXBlL0VuY29kaW5nL0Jhc2VFbmNvZGluZy9XaW5BbnNp
RW5jb2RpbmcvRGlmZmVyZW5jZXNbCjEvZzMvZzE4L2c4NTYvZzExNS9nNjkv
ZzI1OC9nMzczL2cyODYvZzI0L2c0MTAvZzM4MS9nMjk2L2cxNy9nMzQ5L2cz
OTYvZzM0NgovZzg3L2czNjcvZzI3Mi9nNjgvZzk0L2c0MzcvZzQwMC9nNC9n
MjgyL2c4OS9nMzc0L2c4NTUvZzQ0OC9nMjcxL2cxMDA1L2cxMDEzCi9nMTAw
Ny9nNDU1L2cxMDA2L2cxMDA0L2cxMDEyL2cxMDAvZzMzNi9nODUzL2cxMTYv
ZzM2NC9nMzkzL2czOC9nNTgvZzEwMDgvZzEwMTAvZzc1Ci9nMTAxMS9nODgy
L2cxMDA5L2c0NDkvZzI4L2c0NTRdPj4KZW5kb2JqCjkgMCBvYmoKPDwvVHlw
ZS9Gb250RGVzY3JpcHRvci9Gb250TmFtZS9OTFRKR0IrQ2FsaWJyaS9Gb250
QkJveFstMjAgLTE3OCA4NTkgNzE3XS9GbGFncyA0Ci9Bc2NlbnQgNzE3Ci9D
YXBIZWlnaHQgNzE3Ci9EZXNjZW50IC0xNzgKL0l0YWxpY0FuZ2xlIDAKL1N0
ZW1WIDEyOAovTWlzc2luZ1dpZHRoIDUwNgovRm9udEZpbGUyIDM2IDAgUj4+
CmVuZG9iagozNiAwIG9iago8PC9GaWx0ZXIvRmxhdGVEZWNvZGUKL0xlbmd0
aDEgNDY1OTYvTGVuZ3RoIDE5OTI2Pj5zdHJlYW0KeJzsvQd4XMXVNz5z7/Z6
tzdt0zatVtKqd0uralXbkixbsi3bcrdx79jGGEw1EDoJJZSE0EywJNtYhhBM
4oSQxEAIAVIg8KZACCaQQghGq/+ZO3ck2Zi87/v8v+95v/d5vOOz5zdzy945
c86ZM+XKCCOE9Ggf4tGsmT3JQiR+HlwAX3OWrhvcSPPfeBUhvGbp9q2BobtP
vgIFv0FInrFi48p1n3zSqQP8KUJq98q1F6+g5xetQqgrvGr54LI/RtLTEDr6
UygsXQUF+m+bGxEyWiEfXrVu607p944gJHy6dsPSQZq/4nqEfM3rBnduDDbw
X4Xzy6EwsH5w3XLp/BR8uTZu2LKV5o8+To5v3Lx840WHuDSc3we3FxBS3otQ
+lY09TMLrUFboL770FXoBnQrehb9Gi1B+wHdie5HD6FH0RB6Dr2AXkf/Bz/p
i+XrkI4/hhTIgtD4Z+On0w8BjcoNU0puhZxFFpgsGRfGPzyn7MP0reNCelRh
RhrxWj33CpT+DY+Nf8bVkvx4KclzVwM2ild8rLw3fSj98Dky6ELz0Hy0AA2g
xWgQ6r8MrUKrQTIXobVoHVov5tbDsZXwvQJyi+CspXAWwZNnbUAbgTajrWgb
2g5pI+AtUo4c2yTmt6EdkHaii9EutBvtQZdI3zvEkj1wZJeY3wm0F10KLXMZ
ulxEjNOS/egKdCW02tXoGnTtv81dO4EOoOvQ9dDOX0E3fim+4azcTZBuRreA
PtyGbkd3oK+BXtyN7jmn9Kti+V3oXnQf6Aw5djuU3CcicvQ76IfoKHoCHUJP
irJcClKjEmFyWSHKcCPIYA/UcP+UJ6by2zEhrb1Qd1K3A1JNd0L55VOu2C7J
kZy5H86kd6HtQO5yyTmSuAnqQPFkjWjudrH+k6VTpfLvSpk87pkimbvFHEHn
ln4ZvgN9HSzwAfgmUiXoG4Apuk/EU8vvnTj3fjH/TfQg+ha0xcMiYpyWPAT4
YfQI2PZj6CB6HNIknooofwJ9W2y5ITSMRtBhdARa8kl0DI2K5f/u2PnKD0vl
IxMlx9FT6GnQkO+iE+BpvgeJlTwDZc9KpSfFMpr/Hvo+5MlZNPdD9Dx4qB+j
n6CfopfQDyD3ovj9I8i9jF5BP0evYz2gn6E/wfcYeln+e2RAdeCnnwI534MW
ooWp6csWLRxYMH9ef1/v7J7urlkzZ3R2tLe1tkxvbmpsqK9L1dZMq66qrCgv
Ky1J5uXmZEUj4VCm32k1CUa9VqNWKRVyGc9hlNMUal4cGIouHpJFQy0tuSQf
GoSCwSkFi4cCUNR89jlDgcXiaYGzz0zBmSvOOTNFz0xNnImFQDWqzs0JNIUC
Q6caQ4FRPK+rD/ANjaH+wNBpEXeKWBYVM3rIBINwRaDJuaoxMIQXB5qGmrev
OtC0uBHuN6zVNIQalmtyc9CwRgtQC2goK7RxGGfVYBFwWU2VwxxS6cnPDvGR
psFlQ7O6+poaPcFgv1iGGsR7DSkahpTivQKryTOj6wLDOScOXD8qoCWLE7pl
oWWDC/qG+EG46ADfdODA1UOmxFA81DgU3/V7J1R5+VBOqLFpKBGCm7V3T/wA
HpJHhFDgwD8QPHzo9AdnlwxKJYqI8A9EIKnihJjgOMMIng2eEOoXDJJnuW40
hZZAZmhfVx/NB9ASzwhKJRP9Q9xicuQEO2LrJUf2sSMTly8OBUlTNS2W/m1f
5RzatySQmwPSF/9F4B8cDwzx0cVLlq4ifHD5gVBjI5Xb7L6hVCOA1KBU16bh
/CScP7gYKrGaiKGrbygZ2jhkDdXTE6AgQNpgdU+feIl02ZC1YQgtXipdNZRs
aiTPFWg6sLiRPiC5V6ir7zgqGn97uDjgOVyEilE/eY4hewM0SrTpQN+yFUP+
xZ5loJ8rAn2e4FCqH8TXH+pb3k9aKSQMxd+GnwuKvyheBXU752x2Mqm5MqIK
9HEevp+0FhQEmuErVF8NBwRoLjFLWrS+OtCHPYidBr8inUHQWfeBDB9paCGH
eHJpQ4sn2B+kn3/zSB7pmeSRIdWUewlQMPFM9He+9NHo2eSB4oGm5Y1THvCs
m8qlB5Tudv7n5IgspB+GK1SkOVvYIT4ClgtlHNxGLCKt6AwMoVmBvtDyUH8I
dCg1q4/UjchabN/2nlB717w+sbUlLZl9Vo4eL6e5IRSEwyzDNYAONic8rFnF
/HQxP5FtOedwKzscOKAKtfccIDcPSTdEAbAgqLQi2jp4Xbm5GEyzGbxbqHkw
FBACzQcGR8f3LTkwnEod2Ni0eFUluUeoddmBUE9ftUd81u6+Szy7yE+ZUTtu
n12fmwO+p344hK/pGk7ha3rm9R2HADdwzey+EQ5zDYvr+4fDcKzveAChlFjK
kVJSSDIBkiF36oaMSjzfcxyi6H3iUZlYIOaXjmIklqlYGUZLRzlaJrAyDspk
tCwllpEPNJJzFYgY3G1TYBlpnj39qw4s7ifGhezQlPAPD+FQDRriQjXDmFPo
hjSh5fVD2lA9Ka8l5bW0XEHKlaAY2I5BOMQnHVgcAj8FCtWHPJiqIk9uGRgd
H5/dFzzlOd0fBFVbADSvb0idAN8vj7TBedMJLYbi6UP7lg6S50C9feRaZaR1
aT+oLbshnNI6pIY7qKU7wBnN4jVEHeGipdA20IDi9fsgM7Svf6g/QX60b3W/
qM7CEGoJVUKz03vKo+SHkv0HzKFC0TbBFDSRqwlTw7Ohnj5a4oEs/Fg/FZJS
B0++NASHli4OgLRlaGkPqDr1pRoPLVkOLlEWXS6SxiMdRKRafESr1wyp8+CG
8I9gbR4xSXlE2d9PH17MXS2dAL8tDGnhiaJTRCldANKBQ63kWeDf1fCo5NTn
yG26RlF3aCd4FvLQ4p2UcHhIH2kdBOdPr9dCSaicXawiPkIr3eMkLVWSmutA
7nxk9uj4w6GLg1M+uTkh0jkQxUSe46DYqP/AuQVD8xO5OapzS/Vi8YEDKv35
L6DyUuknOCkMNEGvASfCmFiB0gif1Nx/5rPP7ld/QEqmfmQ1pMSYiQNIgNhM
CfYgoCSC0anppvFxaB08ouYDo9wVR9RO3AZgPwOXM3AZA/sYuJSBvQxcwsAe
BnYzsIuBixnYycAOBrYzsI2BrQxsYWATAxsZ2MDAegbWMbCWgYsYWMPAagZW
MbCSgRUMLGdgGQNLGVjCwCADixlYxMBCBgYYWMDAfAbmMdDPQB8DcxmYw0Av
A7MZ6GGgm4EuBmYxMJOBGQx0MtDBQDsDbQy0MtDCwHQGmhloYqCRgQYG6hmo
YyDFQC0DNQxMY6CagSoGKhmoYKCcgTIGShkoYaCYgSIGChkoYCCfgSQDeQzk
MpDDQIKBbAbiDGQxEGMgykCEgTADIQYyGQgyEGDAz4CPAS8DGQx4GHAz4GLA
yYCDATsDNgasDFgYMDNgYkBgwMiAgQE9AzoGtAxoGFAzoGJAyYCCATkDMgZ4
BjgGMANIAnicgTQDYwx8zsAZBj5j4F8MfMrAPxn4hIF/MPB3Bv7GwF8Z+JiB
jxj4CwMfMnCagQ8Y+DMD7zPwJwbeY+BdBv7IwB8Y+D0Dv2PgPxh4h4G3Gfgt
A28x8CYDv2Hg1wz8ioFfMvAGA68z8BoDv2DgVQZ+zsArDPyMgZcZeImBFxk4
xcBPGfgJAz9m4AUGfsTA8wz8kIEfMHCSge8z8D0GnmPgBAPPMvBdBp5h4DsM
PM3AUwwcZ2CUgWMMPMnAUQaOMHCYgREGhhkYYuAQA08w8G0GHmfgIAOPMfAo
A48w8DADDzHwLQYeZOCbDHyDgQcYuJ+B+xi4l4GvM3APA3czcBcDdzLwNQa+
ysAdDNzOwG0M3MrALQzczMBNDNzIwFcYuIGB6xm4joEDDFzLwDUMXM3AVQxc
yQALezALezALezALezALezALezALezALezALezALezALezALezALezALezAL
ezALezALezALe/BmBlj8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8
g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8g1n8
g1n8g1n8g1n8g1n8g1n8g1n8g1nYg1nYg1nYg1m0g1m0g1m0g1m0g1m0g1m0
g1m0g1m0g1m0gxsOEwBR84ivxg8x84jPBuxymrtsxFcJbB/NXUrZ3hGfDtgl
NLeHst2U7aLs4hFvHbCdI94GYDso207ZNnpsK81toWwzLdw04q0HtpGyDZSt
p6eso2wtZReNZDQBW0PZaspWUbaSshUjGY3AltPcMsqWUraEskHKFlO2iLKF
9LoBmltA2XzK5lHWT1kfZXMpm0NZL2WzKeuhrJuyLspmUTaTshmUdVLWQVk7
ZW0jnlZgrZS1jHjagE2nrHnE0w6sacTTAayRsgbK6umxOnpdirJael0NZdMo
q6ZnVlFWSS+voKycsjLKSikroTcrpqyI3qWQsgLK8unNkpTl0etyKcuhLEFZ
NmVxyrIoi9FbRymL0HuGKQtRlklvHaQsQK/zU+ajzEtZBmUeytwj7hnAXJQ5
R9wzgTkos9NCG2VWWmihzEyZiR4TKDPSQgNlesp09JiWMg1lanpMRZmSMsWI
axYw+YirC5iMMp4WcjSHKUMiw+OUpcVT8BjNfU7ZGco+o8f+RXOfUvZPyj6h
7B8jztnA/j7i7AH2N5r7K2UfU/YRPfYXmvuQstOUfUCP/Zmy92nhnyh7j7J3
KfsjPeUPNPd7mvsdzf0HZe9Q9jY99lvK3qKFb1L2G8p+Tdmv6Cm/pLk3KHt9
xDEX2GsjjjnAfkHZq7Tw55S9QtnPKHuZnvISZS/SwlOU/ZSyn1D2Y3rKC5T9
iBY+T9kPKfsBZScp+z4983s09xxlJyh7lh77LmXP0MLvUPY0ZU9RdpyyUXrm
MZp7krKjlB2h7PCIvRbYyIh9PrBhyoYoO0TZE5R9m7LHKTtI2WMjdvDX+FF6
l0coe5gee4iyb1H2IGXfpOwblD1A2f2U3Udvdi+9y9cpu4ceu5uyuyi7k7Kv
0Qu+SnN3UHY7ZbfRY7fSu9xC2c302E2U3UjZVyi7gbLr6ZnX0dwByq6l7BrK
rqbsqhHbILArR2xLgF1B2f4R2wpgl1N22YitF9i+ERs4Y3zpiK0U2F7KLqGX
76HX7aZs14htGbCL6eU7KdtB2XbKtlG2lbIt9Nab6eWbKNs4YlsKbAO92Xp6
5jrK1lJ2EWVrKFtNr1tF2Ur6ZCvo5cspW0bPXErZEsoGKVtM2SLKFtJKD9An
W0DZfFrpefTW/fSH+iibSx93Dv2hXnqX2ZT1UNZNWdeINQVs1oiV/MLMEStR
7xkj1v3AOkesucA66CntlLWNWCEuwK0010LZdFrYPGLdC6xpxHo1sMYR66XA
Gkas+4DVj5ibgdVRlqKslrKaETP073gazVWPmPqBVVFWOWIiqlFBWfmIaTqw
shFTH7DSEdM8YCX0WDFlRSOmHGCF9MyCEROpWP6IidhmkrI8enku/YUcyhL0
ZtmUxenNsiiLURalLDJiIlIKUxai98yk9wzSmwXoXfyU+eh1XsoyKPNQ5qbM
NSIMAHOOCAuBOUaERcDslNkos1JmocxMLzDRCwRaaKTMQJmeMh09U0vP1NBC
NWUqypSUKeiZcnqmjBbylHGUYcpQaty4xE8obVzqHzMu838O+AzQZ0D/grJP
oeyfQJ8A/QPo71D+N6C/wrGPIf8R0F+APgQ6DeUfAP0Zjr0P+T8BvQf0LtAf
DSv9fzCs8v8e6HdA/wH0DpS9Dfy3QG8BvQn53wD/NdCvgH4J9Ib+Iv/r+gL/
a8B/oV/rf1Uf9f8c6BXAP9Mn/C8DvQT0Ihw/BWU/1a/z/wTwjwG/APhH+jX+
5/Wr/T/Ur/L/QL/SfxKu/T7c73tAzwGlxk/A97NA3wV6RrfJ/x3dZv/Tui3+
p3Rb/ceBRoGOQfmTQEfh2BE4dhjKRoCGgYaADmkv9j+h3eX/tnaP/3HtJf6D
2r3+x4AeBXoE6GGgh4C+pc31Pwj8m0DfgGseAH6/9iL/fYDvBfx1oHsA3w33
ugvudSfc62tQ9lWgO4BuB7oN6FagW+C6m+F+N2lm+G/UzPR/RbPSf4PmW/7r
NQ/7r+Qj/iv4cv9+XO6/vHdf72UH9/Ve2ntJ796Dl/RqL8HaSzyXtF+y+5KD
l/z6kpRZodnTu6t398FdvRf37ujdeXBH71PcVWgFd2Wqunf7wW29sm3WbVu3
8X/fhg9uw43bcP42zKFtwrbANl63tXdz75aDm3vR5lmb920e2iyrGtr89mYO
bcaa0fEThzd7fM3AU3s264XmTb0bejce3NC7fsW63jXwgKvLV/auOriyd0X5
st7lB5f1Li1f0jtYvrh3UflA78KDA70Lyuf1zj84r7e/vK93Lpw/p3x2b+/B
2b095V293Qe7emeWz+idAeWd5e29HQfbe9vKW3pbD7b0Ti9v7m2CyqMMISOQ
wQvkAWZkwJMgD67P96Q8b3s+8siQZ8hzwsObjW6/m4sbXbhhpgtvcF3qutHF
G50vObmUM57TbHS85Pit4y8OmSXliOc1I7tgD9h5G6mbvXN2s8hrGykvKBHr
2mkPRZuNNmy0+W1ck9+Gkelt00cm3vas8JLAGY3YaBw3cikjnG40+A0c+Ro3
8ClDQVmzUe/Xc+RrXM/bU3ooIXeM6WbNbjZq/Vqut1Y7U8ultLUNzSltbn4z
4nEAY4QFYLyKPAW2+ZvBrg/bsRxDfz48uyeRaB9Voe72IdWs+UP4mqFID/lO
dc0bUlwzhHrnze8bxvgr/cOYa5g9ZCWrvmL+yhtuQPXe9iFvT9/Q/d7+9qF9
AFIEjANA3mE7qu9PLNyybUsisXUhfC3csjUh/oMc3kZyCVJI/m3ZCnmStol5
lPi3H3oasEVb4LOVFW7991f9v/7B/9MP8L//M4zIRoW6ce4KtIzbD3Q50GVA
+4AuBdoLdAnQHqDdQLuALgbaCbQDaDvQNqCtQFuANgFtBNoAtB5oHdBaoIuA
1gCtBloFtBJoBdByoGVAS4GWAA0CLQZaBLQQaABoAdB8oHlA/UB9QHOB5gD1
As0G6gHqBuoCmgU0E2gGUCdQB1A7UBtQK1AL0HSgZqAmoEagBqB6oDqgFFAt
UA3QNKBqoCqgSqAKoHKgMqBSoBKgYqAioEKgAqB8oCRQHlAuUA5QAigbKA6U
BRQDigJFgMJAIaBMoCBQAMgP5APyAmUAeYDcQC4gJ5ADyA5kA7ICWYDMQCYg
AcgIZADSA+mAtEAaIDWQCkgJpACSA8nqxuGbB+KAMBBCyzCU4TTQGNDnQGeA
PgP6F9CnQP8E+gToH0B/B/ob0F+BPgb6COgvQB8CnQb6AOjPQO8D/QnoPaB3
gf4I9Aeg3wP9Dug/gN4Behvot0BvAb0J9BugXwP9CuiXQG8AvQ70GtAvgF4F
+jnQK0A/A3oZ6CWgF4FOAf0U6CdAPwZ6AehHQM8D/RDoB0Angb4P9D2g54BO
AD0L9F2gZ4C+A/Q00FNAx4FGgY4BPQl0FOgI0GGgEaBhoCGgQ0BPAH0b6HGg
g0CPAT0K9AjQw0APAX0L6EGgbwJ9A+gBoPuB7gO6F+jrQPcA3Q10F9CdQF8D
+irQHUC3A90GdCvQLUA3A90EdCPQV4BuALoe6DqgA0DXAl0DdDXQVUBXomV1
+zDYPwb7x2D/GOwfg/1jsH8M9o/B/jHYPwb7x2D/GOwfg/1jsH8M9o/B/jHY
Pwb7x5uBwAdg8AEYfAAGH4DBB2DwARh8AAYfgMEHYPABGHwABh+AwQdg8AEY
fAAGH4DBB2DwARh8AAYfgMEHYPABGHwABh+AwQdg8AEYfAAGH4DBB2DwARh8
AAYfgMH+Mdg/BvvHYPsYbB+D7WOwfQy2j8H2Mdg+BtvHYPsYbP9/2g//L//0
/08/wP/yj3PRQiRHKL2Ff0VuQDxSogrUiWag+d9BelBpO6rER4/aGhtVucrv
grpyKAAKr0IYN6SMMk5/zO2uDR0rUdzAm1ph8H6kVnkDuPLasbfGXkyOvXXa
XJE8jZNvvvPWO8LHL5oqkkXvvPpOQT42BU0iWQ2cUmlVhDLzuJJYtLSoqLCG
KymOhjINnFhWXFpWwxcV+jjeykpqOJLH/Cufz+Nnjim4vaHaOUVyn9to1Svk
XIbTnFsdEXrmR6rzvEpeqeDlKmVWWX1m+9qmzF8pTV6b3WtWqcxeu81rUo79
Wm747K9yw5kG2dozt/GKqgW1Yf5rGhUnUyhGfU5XdlWwdY7RIsi0FsFkVynN
Jl1W44Kxq2wZ5B4ZNhu911gniCU0/plsr9yKMlEUff04Co+/d0Qn4I7QqASi
o+MfHdEC0DIAY6qPUm6CIgL51ovfOvE7lYUj5HCOFneGQ9HI33VanTPTG9Lo
sV2mQzpBxx0KPRt6KcSHdCGd2dtt7pX3otraWnNFRTI5MGByVJgAmoqE04Wm
IpB4YoA2N0TrEbtdIYo8xgd5Ax/KjEZLyzCVs0MZ4oOybSosRPz+iEUt2zD2
xzW8xhLK8EaMWIVHZHpXzBfIdhtku/Fv8fem2T0GGa/UqXFV+gW1Xi2TGzx2
2YjWoOJ5lVF7w9huBDr1OEIyDNrlQwlUjn6UcvudAu70C0bypYcvpw6+AlBX
sg6SynLbUnDcloLjNps2h5ycQ07OISfnkJNzyMk5T0Hcg8ZPHAWMokUg6cNw
JvCPDhslrhf5J4d1In/vsJZwTkjp79ee0HJad+zvBQXKsDjz0lU8irXDytmo
9nStqLcVODnwjii0wlcTFEBxIlFBMQjVapCFgpnRElNxaVEQpGcj+uzjcXEe
FwqZiDJbJqEM+8tnLt3Umn7CEY87cHTrbUsL7Ym67JIFTVnpMXf5vLaRkw3d
pa4ZkekXdb34WVVfQxRvmbayuybb5o/JLo/5c2bv6sybPb3crCnpXs/hZEdJ
RnogVDVz7M3Kvmp/ujyjrBthNDj+kUwn94EVLzmcgaoSklQSklSAf0CkAvxD
IpWEJJXEdyGONCAnTqIgiuKcEUuP7GmcjUpQPs4bVs8Bk371NCGcpNUXXjtZ
kB+xGhRTzFJhk8yUGLDN6uNIvYlayXScXGVNLdrduvcnN3b23PGzS8vXzGv2
qOS8TKVVGQpnbpo554ZlZSVLb5rfuaWr2KjUKPhjgtNssMZjntkPfvz1Bz4/
tMAWyPYYLG6zNcOijiVjTVc9t2f3M5fWRZNRhckHFki07EbQMjPyox0pb20Q
W4jmWIjmWKxQZ4sZKmxxQm0tTxPNQW4qG7ckG7ekMW5JY9ySbNxPQ2yrBtno
RgxdnlEcHZZTLWGyeJVpxADxaGephHKKAtw451sfPZT+UGz+yCPvfb3raPGG
x646NLznsc0V3F2PnPlWN23oud98787VR69o+9xUs+85suMTasbvgZrloO3D
7pjUojHpqWPSU8ekp45JTx0b5UwptdoSsATg4d2jWJXS74viE1H8chRHowoX
mYTUd8WADSsmtH5g02aoVlJ0I4Kk/WI7c1/Q9FDQdA7k98g0etXYraSG3AqV
XiWXw1dagUdU4BpkasAzOKzSa2TTzR6zitZWZfZYzR6TKr1GLWRYzG5BmS5Q
mTxivcc/42dDvWNowbDSItXbItXbItXbItXbItXbAvU+qvcin1cJVTtssbgU
ozjrcGaXizhIqUdKnjRVTNQOf6EyrLdh1eVnQ8WUaZCeEh5exCmVNeB2ZlpV
UNVmsfSkJQNq0aIUPDaLx6Qe+4NSr5TL4Uv2BKmll9Ro/viHsp3yAKpF30h5
MzKMTqKhTqKhTuLbnBodQVALJ2k9PXo2hgOxVGxxjI8ZpfobpfobJUs2SpZs
lOpvJDsgk8W42DmKNUcyMyuSNU9jDfTxGhwfqeixjuKc4eQc0t5gzSYqDsnP
vTowcHLC0UlyOcuaS8tMRAuItYvSMhEPOGn/MtlOmUqn1JUv3D/vose21zbt
enR59e6S9Ksmk0wNfcTdWrtZY65csGRZwR0ffHPOwKOnb2q7fHmTWyNbaPFa
VNG86IwD392w58QVjV4vvjgzDGJUqYQMc9rijnoznbqBxz+67a7Phgbdobg7
k+qHbBb0uUk0eqS2AId0koh0koh0koroJBXRSSLSEeFmOMJaIn0tkb6WSF9L
pK8l/kFL+ggHStmgY0lZyJdggng+BceRg0zMwQHCn4Rjjuxu6EByUsYTOvyy
DuvO7o3BoE7XYug1XiVilVRu0rAGIhOqNlXrqNe0QRmDslkqa9DpDlhVY4cB
uYjmqayZTlfQquI6RV0E5Abpg8rpVFzN2PcYlv2KobHPOAXDkn3hPpCfDc06
VuuY6Tjk4JEkQiSJEEkiRJIIkSRC9BT4RM34iWMgCY3QLVYXqjnhCCNfqAzu
Y8+ttgUdrqlPO/mE5KmU4x/i38NTZaG+49C9/9cfxwuPY8KdXkOoW/00LkQW
cNl5w3Kp7wKjT0zpucnTKVg4Kcadk0/6+4zGDd0ZZXmZWqWc46GHUrlCef7M
/IBAq2BR4+bOffMK1EaTTmdyme0QSxrNRlNeVx1/L6kPsQLJf30KNSlCS1Km
AmLW+US7kgQFNZKkNVLVNFLVNFLVNFLVNERZdbZYd1AjeLqFyTivlnU/oEfw
TSUejcbweRRJCu9sVoUSY7ud/1RpzfSEcuzKdPhcbcI/VgiOoNsdsCj15nQP
ftGkzCCuXCFouKvHLp5wapNa9RxXq9YpZXIo0LsdY+Njd7ktUq/VDrV3o5bj
yEYra5Mqa5Mqa5Mqa5MqayO7kpHa2G0bxQmpW8LJU6zdpvRDEyZC3HM79C3q
sZOO+EQlXibBaLvVY1FDL/MEe9QzD6hNGZLmKxLQs1Sjx1PC4pqNNZw+P9+R
TGrynE736H8xLCAN4wsX6HQa4kc0xI9oiB/RED+iIS2tIWoJEWrKRXQ0XNql
dTr0SWdBnsKf1eXvZW6i1gzhehFUlMWZELMLE8hUMS1ZVESi+ClWFcIkcocY
HofO6q3EIB4XkfYW5aNIqKx+lyNoUXHpIl5r81ptPquWS0/H4DNcTmjkHM+q
QH7YqcY75Pgqrdsfda0zeiy6SeNceeY2pUbJyyAog2HSnRPlD2WHde4sz+dz
+Yd82S6t2uK1ST55r9yEpqErD8eMRqskTJEbJa4X+UdEmFZJmFZRmD5NXl4h
EWah00i+4MRCQUcQnFJIThGQr7xbk2eMyVykRycaIoqPCO8LsksWSSpDJQW2
EbLbbeeRl493FEWnaJVsr97m1pe5Y6GQLb0qUJfBcZzK4nc6/WZVjrvbG/N7
TbjSW1pY4MQQ0Fj8LnvArJpuhXGh1lsY496uuKSq5Y62z/82YS2PZWVqHHH/
2I+Kly4eSM48OJP7LoyaICYCR0HeWBs/LXtPHgSXFUN7Um4rkYGVKJSVBK5W
ErhanVRMRSl1AOWLfxXDJwnXJ2mqTwoJfFJI4JOE63sagnsNckEAYOwJEcuS
zzk7gB04xzNODLTF+HVKNC97r+3Wt2675RfXNbbd9tZtN756Q9PR2Pyvbdz4
tUXx6Lyvbt5018Is7o6vfz68aO5Dn9x/52eHFs351t8eXf/MdTNmX//0ys0n
ruucfeN3SKwOnvF5sL8MFEc7h8MKqSIKqSIKyeQUkskppIooiAo4TF4iHi8R
j1fQ6XGHl4wGvWR7HTJFIOo5rFDooJraw7Yu3ZSgjyqIcHbcFzo32JNNCdn5
51M7vr3zVrUl6CJeJduNbdmdq9d1xI9WzR3Iue/uGSubw/ytg/esr07nTdgF
NLXSUbvg4rkz1xQbxv6VNX0pojWWaaHGpagR3ZzyCXmmMhU8dRmpRZlYizJS
qzLSymXQysfiZAwcrzURUQAySaIxSaIxSaIxSaIxkW13GXkCxPlPbkzhVMox
DSRwNNjlkJyMGN2TQe0XxrQVkpWIUwJ5/BdEYnf4eGlo67DY7bg4GotG2aBG
q7CGfe6gVSvbYcutmV21hQkLBjmWgjp3+5YZsVD9gopAcW6WdatBlR5rnOWq
Lbr5kcal9X5wMtBZqsHEC4rn1obGfjkhRAiZ5by+fM6GhrqVMyuthkT1jIL0
78Je/sqO1Q6lIt0RrJoF3mb6+Gl+KdhNK3r3OKobf++IUcAddZKI6iTR1Um+
pk4SVd0ol5NKFKYsVtxRmIKIIVwYLtR5nORaD3HgHkEgX3CJhzSH5ymugHjx
wx4x4Dhx2CVxK+VPGklwqMt7GsdQGYTZ0ZTWFCjDZSmtDneYyJqvhqAyU5nJ
Xg1jkqN1Hnm8xz6K45IdQhOcNpERVyIxIJwWiKpORotmeuAcA5WdFboUT4Qy
5w7BFfzShh0PDNRtmFvl0EJYojIUzdrUVj7QEC7sXr1+VXdR1eqbZyfmdlZb
FDKOV2iV2mTjQGXprGJ3Yc+a9Wt6ivBF87+ytNAeyHRG/HavWZmZFfKVzSoq
m1FVUFQze9PMrkvn5BpdfovW5LSYYWSeEfJ68+sjpTOqC4um9WyCNjKCrb8O
mp+Jlh9zpsgox0SkdoSEcf9lwycdqWn8xFGi+QozGdB5JdsuhLDzY1E4P0gI
JxMTw7nJwJq5MzFUeF0cht7Goh5A0jCVv0IcpIqjuDP3TijiEpUpw2KhE30k
cngMPPXFENUk0J0p7+JcHCBWGyBWHCCqEyB9f4BoDXmvKmWaOoYATUN2qcJ2
qcJ2qcJ2qcJ2qcL2pziBxNdkpEE2X6TUcAtNtFvo9kzqjTiwkDx4YlJFBvAX
A0DruUGu7OKmfaPbLhra20gHshZVTs+21vZtXQlRNEGIcd/afnxffc3FT+7g
Q0wcn/913lX9uTl9l8/lHVNj9kzwbqtAKmG0PuUNE8eWFcZuwqNunOXAUT3O
ceEcJ3aNSkYqAuL2nKyEgJSZFLmcLmc04u92ys10ZGGuqDWZMTUEUkM0MIAH
BgYSA4mIGAbJSOdeWjol+Cm02xVK7pjM4Ip57UGnSafk0/0qbM7KzAia1TK8
BePVvApclz+s51U+MmGJIYLVqmQj4pSmSq8586yslpSTKU1Sx2kQM74NdaxG
Kw9Hq3Hh6PinqQZi2BFQQRUBWUkcEcSSCM50EhDPxM4AAbkFODcf54ZxbgiX
dWd3h/K1/NSBIkQwtdBy8CFTtVKKTMR4PEPnVvPsCsv3y4SMuM+fyDDI0h9z
n/EGdzwQzMkw8unHFNgUDfjDFiWHQxhbebU14ssIWtU8jnPYyyssIa8vJGB5
1GAicYnJwP/s8yTDsoMON5GKQXvmpKxSayRDHKP2zA9lVRrAcoPbQSSUD5b+
iTgez09540kcz8NRJ446cMyOsxCOd4e0Jm+3acoQBqx1QPxMTkpjPDEnPaW2
E1XE/O/1cnM8MxC2aWXpt9NvynW2sC8YNcr1eDB9SKcUwEFF7RoFtmOrXGPJ
9PpjJpkuPVRjdxvlMJhTc/zYGIRdvNzotnM9XK3dY5TxSnAKGfj3Kr1SbO+x
H5D6+MQoxYqyUf9/bySqA8N1iPMNJ1I6MgER6fYozN0KSZfxVH8+6agmqwu9
rKOotLTMMqHJrXRkY1Olb9HKjbGgL2LXyg+7Ct2co8B1hNdaMt3huCDX4n+m
J4wVv8n9ijSbTKnXpK8v2VpVsakMb9cYlKTB7BCTLIDes5b/MYxPU2goFTDW
++uT9bxW7SjWQY2KiT8rJq6sWCD2WTyK/5kyoFjMiLAOEY+HKqWetVKK6isl
IVQym64c5VQpq8nxA1QsFHNVJ4oxKsbFxXl12aPYkzK+nIkzM2Xe9/Papv1G
1ylDSTYLKU5MDWxaOMBC1JOJhQMV0oxkIQQsC2EsRBQGovYSxeQcdFGJFK9K
JTLR1ylpZ2gnE1h8rZDhcfsNVTd3Td/SlVuz9ZHVe+wFMyqmDbYW6FQQkis9
9XNWFA9eMzv64A2Ny+r9/bPqNkxz6nQQU+rm1TZHmlfUdWxsizQXzyrxeENe
leAyurzukNeS07t39klHbm28uae+EaR7J0j3F/JNoD0wFjoKzloTLJWUpVRS
nlJJXiQvyqt0FH+a8tgSJOBPBMg8PZF/gvQxCUGcvuc0KTWyaUpLgjJ5/iiW
Pxlt8zQLHRUAh+WdYq8AInRUTIyHJmU20S/EbF/sIKgzYeG+0mS3iwHwL4qW
3jSQaG1ujqnMHhsMcBRKS8DpgtFOVntLS9aS6+ZmPWErnpMK1KSaYo17Gmr6
ylz43W1PX9FsilbG14MqgvrpVPJyFZ0WUY39IV4eEmbsH9rWdPmyaebs+sL0
nT1zq5fuBnubBxIL8C+gEnTtcIYYYVGDe1sytPeOEAM7zwT4h2dPfI+/TyfE
OW1KnzRgg+tdf0qjb/GHRzF3xNLG/7mAxB9qfUtBzihWDKs7yQxR4rT4NTEZ
enJi6vucJQ4FDa8UUxc4+AAnV7qq2/uSg3csL6nbdGd/oquxxKlWcGa9MVbd
W7nj0mBqoLpiTm1CRwbT3zC5THpXxGtO7T687cpnd1UJ7kynweI0x/zBrOCx
J+bu70uEEyGVxUvGDotBLvfI16EoqkDXpfy1VVjrqSDWWUGijQoSrVYQ7agg
ylLxNP4XQihJpZaUhJWUhJWULDYpCStJFEpjCTZrK2IemSGbbDR2toGpyw4b
OuUdJMAS1an2nLUOUZ8mpiOmmiAMFya0io9Gpw4ey/h7lKYMK1k+nX7n/KXX
z80qXHLzopn7U0qrn+iU+qGGSxprQYNAo+qC01LNMRdToB2dczr3Dy/Z+vQV
05saOC0bV481ge4s2ZNqvHw56FJDAZHWAEjrTvBqCVSMnkhlJ0trSzeU8hZi
TZYAWTiwBHNIbJ9DpEWXFEX/Brrwr6ONiQcTHFksO0qsrVgmKZ9M0jExrxU5
dXAyIr9gMOf5fbKbZNwJGX5ZhmWyjORvom3O9xcbNho4g/r9DFHBBqausFCj
fDNBlU1cVxQNVBEKTlEr29nKx9lipaJAlfydMdfYiK95Y1dqWWtSp9QqeI5X
akvnbEpteHhzZfWm+5euuX1x7kP8xTumLajJ5DguFmzfOSfP5rYpDS6z3mLU
aV1OS82u0V1bj1/W1Ljl7j7L5bfldSwvI/1eZPwz7ir5Toh0lo3YBWKAouF5
JK/lYd7KI7kzj6RMHvJKVX52ZHT85ZSZzJhHNKdLp7ujp/NbAh1CizgKLSSz
DomTRR9TGys6ec46g02ap5w6Cg1Jaw5FbJ2BuwpiNYXS5ot7IsUBwwvQq8vN
xhdU4JqcAYvqUkEgrubSUMu6tlB9WAcxnNHiMMjVWrWzqKtyidLktoQDn/+Z
hHtkAZK3BcIWt0k5sPDqOXG9UWfxkFXrkvSt/LX8j1ANmoEWoZdTNnPudGJl
01VQ5ekBwYI7phfVQhRIRFAr2Rfwt58kh2qVMwGm9EYz7pjpkRnz+SKlkmiP
IMrrREoPILdI6fEoi3JlRMapYiLkPvITfQEBLuvLjqS0wCPGfCVf3vYrXc97
Ntvicv5P1S3ZgfpflrfN/2VgprRwV0uXcl6jrj9RdIoI1wEBMwmZTVAonErA
vwT7IlIHGdvttCuIxhTgz+wOaaTPdK4MutfiUvGbWnawkAz/J7pTssAdjcUM
vJTjr7UYLwtlFA7sm1G21GN21JX+uWFjd17xRQ9tWnfnkhwhWBAoSBZG/OHi
BZd1xKf7sWAypdPLB/KnJx3L5xe0JB09i7r+FIg71Vdsb19e4+G3hvzhuckZ
O3tyvHZzni+Ux2m44LT+qpqNvQWRVH9xsKa8yOXqyJm2OBoZqO/cNTtXrQqm
P16wMlDemtW/wl/WMrawspZTuXLjWba6Bm9+DdHvOyGuux965kJ08ZHaYpw9
uXQoKfaUNUVpjRG6ZYePLhCJS0XiKpHoNrTkmIauDfmyXQL0KMdy28LNrg7R
fYoTLxNrD7Qzrjh7gUTsTZTnmbWn0aCNv19lpn2uM681v2ZPI2TFqVvWFU+/
qXXe7o6gi+kzZ+xc2Bju6x27jpVM7X/bW6etuHaQeMorxz/DXfIksqEguv5Y
bWhmaEOIt0ux3FkjUovI3z5n5EpHqk9zm1AGsn3ZhL4kUhuI6UmNn+zpIC8X
HXEJraJ8XjudkLyh1LOcf/XIQrpdooyghbjmXAFYcqoqE4QmRMBfwdZhcH5l
drwCCGo8/ov0rXgZ1DiM8tFVh2cWkl02YrAA/K/kuSPMsZPtN6QCEfKedUKH
pPOmhPu0XhNxP/i+lMblQoV5pI55UMfDWf5WK/Skw3LRSqGmpqIiFs/S2kJd
5WdN6NjPHqWfVe0uX2rZ9ECuE4avvFKtVIQcwaTPwJwekUF2oqoq27hs9+yE
SqM3mfVkNV1uzW1p5Q9+URzUDvaAHRSj21O62lIcL8AFKTPuhPDoZbFyBVL3
V0BqrxO52P0VPM3FUCYMc6gMvnydFUzDbc/NRUQk1ETsmVp5VmtGs4mZBwwD
cRKCLYjuxT6h8G2mBRNq8F9a0tqjgjGQJ+Q0KtJXnKsfeLbK7ILxU6ZNrTem
n8Lr9Vpx6hGGfWr817T+i2by+SswUtKreehU1TqnkH4qHTHZJN+Ba0BmNpQS
10w3iGum5x8KTuoI/vSIRmgWaywpwPnXSL+g2a4vPpr0FPKXIcaZhd5Pecxk
PVHc1xIVZx9i4tTDxm7c/MW9EXRGdMoeivcn/JvPZydrB75Cun4lrmSJi1ii
m9OAfh+bReawZtV8casJve0XtqQ8jT8FJytgxUh7GwTfipS+rq2mObe8NbfD
NaX9py5FVEjz0qYKtlxLvKX4ksm/c5lf5kNt0ohaUhb5y9SVWlTWnMa8ii1N
xHocQYvSntOQV7F1wrMqzBkOu1dQdtzYWt7fmC/kdrVPD8/d3uqf9LGhinN8
7BdL+CsgMOF5tVa1o3emO1mXVdCYbQHn28H6IGjBQnRbykhbkHxJ3dG5rfQl
O13IYNGnFQTWK4lbGabsYsCfHpM6JtItpTS5bdmucCsTPYkaJlfFhbOk/V/o
nmz/Wfc0IcSvdv4n3dNZggIBLSa9ExkNvgUSImtij6QyauM4y4zjJjKXGNXh
qApHlThbnL06zzrY2+ddByPBui+pwZopC2yBsxfYnuI0ZK7/mBF1boRmcpG3
K41tIRg5SsNrMkKURJacWDYbYJ//bP2Mf6tyy7c3b/jW+tKKLY9vAV72hKdm
zczW1Y1BT+2amS1rGgP4D+uPX9Vev/fIZuBtwPe0Xr6konjR5Z1tlw9WFC+8
nMwtpG/jfwGyIXML+8jcQrD0PPsHqPeZ3EhAghgbnVYQJxjEFQ86w3DeeYVW
YeaXziucb1rhPDry5dMKtyzMaqxLhacoi9XmMSvjHZ1duUsOkGmFInFaoTnW
uKuhpr/Mjf+0/Tv7pwuZxaF0DfOFsj+BzvBkVu/i7Jq4reOKQ9uaLltWbYk3
FKTv6umrXrZHHD+DtO6RpHVVygPi8msTxGASGh2bYhGdXIKMnbNREVWbKTtJ
35d2krIdpmwnKYydbZFW7bSEXybkkbGzu62cjJ2FTtLnn3/sfJbMSkx0Zpfp
i6Pky8fOamJmfqsy3tbSGiMiKlx686Ks5qbp2WQzsjXDpPzC+Dl9hEkKn4pX
hIxsDG2KVMXXMdGl/0EH0XRCBgbRonfiHhZnBpce2ViCo0ZJqSY3mUnKZZS0
zkiUyzxloYNoGXKDzkVS6kRb1GgLtNo6kOTuxQ4/MRELTx0Ans/RiEqk4B7m
FGqVyuEN21z5JZWhc91MpK6ywqsPhr06GY/5JXafSa1Wq6x5HWVjQ190NPtL
G2NGXqXRqA3iXsOu8dPci1DjVvRiSpdsr22f2X5p+6F2+ZTFxE+kRURRKerI
9JTlnEVGcXER/yblpyuK4loiUTFpQZEMkYnP8TyFPxG3hWhIWKRLaaWp4ijc
r1Z3SMfp8t4s0/zZNMu02LTRxNOFw1+TVcM2+3vUGCeWDKUFwwGyBDRlwXAy
lv7vLhhyLxYtvHxG/tymfLtGRhYEE7VzyrMbCz2x1KzerlQs3r27O9xSGbcp
eYiONAp1ZmlrMjsVt2Wlunt7UjFsaFoL7e1wWcN+C8SfnoDHHCqNRIuz/JmJ
mjnVJYOtOTqzTdAZ7YLJJSjtLrsllJ8RK8kKZGZXzyZtERz/C7dO9m1UiRYc
iSNTKFeSea7UFrlSW+RKBpkraWUuUUKdQ597OtTi1Z92tBSQ6FtJ3fYponZF
0uzVqZN0ak92/gmGs6ch7Gw6hlunEgLxPEfzspR3r9FMVg0vYYHau2Tu2Gx8
t2y6I5xhVcnVctl8b6ZgUCsi7VtmcAY6w/Aa2/TxGp2DSGsGFqk1arnBicbH
Sb35v8iTXBQ/ghBSchHuXiTJg/8NyKMOTRtJ1gkkmkz4fAkjGXLo+JJEXYuQ
OF1V0kIGG4cjnWo6bXfqdCF4nsI33zGTifNCsqGzcOrul+CUmtn+nSj4R3x2
iJMcJGxKJ6dU8MulwR/zuD//6uT8ymQ9zd6g6UuFAnW9jcx18t+BuOiWlB+i
IW2MWFGMWFGMrCfGREcdE8SwE//rSept/JJm+CXNAP6p6J8IOCy+WCA5LL9k
p34iPLUltzWmlbtaITiVT054Tt1cN2FW553wPGeBtbRscurzHqXZa3N4TYrO
O8TwR2ml4zRHsiW/ZneT0uoH72VWT0RFO3pnVK+8dgmXyTzU2N9nLmqI9PVy
21iJtNLK7wb55KDfHUehcejRSbDvF9cfI37so8CH7VI9bRK3Tg4BRG6e2Dcy
/lGqjGw6gcjKhGMCzpLjzCwomJaJw5k4SGBtEIeDOCCWBnA4gGNGvD2Ig2Si
T22ytQQD4LmCZP1WDeYYJLOsJEdaIkjuryMbHrNag1p3q7Zjcg0sQd5HGRCj
pwT9J64GUrmTFdCE+IbQxFa3Kd2kxUEXx3wcvxtzPJc+JdO7s3y+LJdBln5R
JiebshzekEUtS8v4M5zGEvQ4fCYlf59MrdEpP3+ULOzKVAYNP1dnVvMwLubg
Sz3m1um4P6p1Kp5TaYm0S2CcdQVIuwm9dRxNBxc9DapWTiYA4+W4jPBIHo4G
cTSAo34c9eGoF8cycJYMx3lcWYWrKnFVLq4m/yeEDXcK0hQK4SkNqKsQgDsI
RqmYcHG50EiKjXWt4nlEmLXCTGGDcKkgE1Jme4tQ1BpprbwpB+eQYzmk5xAs
9paVOTtyuCYodXSIHuAXRJIDJ2trT4Ekqbwnl8/pAjr9UEErJuTMx5RT1pvP
I/IpUH6FTJ7+J693ZPn82S4d/wzHHeL17rjPH4Nc+l/gJMBzZGSCS/glxz3P
qc2g9n6zinudw69xakvQ7fSSZlFajZONwt2gVo9tmWwio1Wp1kILwWh9zK1W
QwvpofMhW0+dLMepNKS94mAd7dBeSXTVcVQAgjGRNQ7iN/KIx6jKw07QxyfJ
mqYTOyTfYGdFdqwm2ppNxu7kmmqEy0O4VIu1ATLEIq2i1Rbkx1vJOnaraWIY
RXcnJCd2JhDlpfqbiNit7GUr/jzr2hbL5Lp2g8oS8/tCNq3sjddlWltmhjdi
wmrsTP9ThS2xgDdk1chOvSzTmPweb8TMqdP/yjFYdHJeqVXi5em7gfFyncWA
j+GHDRa9jFdolOlhPFNB9m5qrcb0QuI9IBLeA/IJo+7jyAN1LSGW78FxD3aK
EwhOHDWUGriYGrtJWFLpxq5yIjgX9re6NJZWTbtsJmqXBu5kx0KCGi0x3iBP
q1pmIbuQo8UTOxUs4syW3arkinYqCgrdAROn2KMW+PSzKiHs82Va1XKM+U8V
psxARtikSB8VTHKd1YArZGYNv8DmNMh5lVE/lse9ZtHKSR8CNemHwP51/hhK
oKrjSICa2MnOkai4ky4Jx4vVjWpOHTHBwO2wq8UYEwdw8OBkAaIQ4qVTA2TX
9MSGYnG2G5/1coO45Q0TyL2uUBlUY6/ZPEQf8Q3pSwUL2XHMybQmnZKUpbfh
h1R6taLZ4jEpM4KZBrvdJXBrghEz5BUGuylgcDrcwtgdSsFDRiSIPybOvGqR
DlmPQ8mmIwo1r2tBtW+dgp6Hzs5PTPzhLja/mT4kOyXN36WHoZbZ6bfwFvQ2
8iDNiNaRgYRXT9HNfEolteAyy8Qrk1sUBofpWrne4rKYHBosu1LrDLtdYYf2
Rn9xXq7rRaVGJRoVtuzzBASFQgiQJ316/J/4Bv52cRTuGUbWUW73MY0v5OqQ
G+FpT9WeIkFV4Rc3jprOyeMb1K4sfyALLNaZFfBnudTn5vlAIMej1XpyApm5
hOeOZQVpQTCYC47ZnUss/KvwPOuhxlrkGCbbx048SbaJqXkwRXiUxHOk+lNE
tz5ZU51HaN30ZF4TELlHNr8Nb5HvBKmpQWrT4Ur6/P8docmj/qJkrvNFpU50
RWpsudQdMCsU5gD5BZx+l9fIv4tsSDUsyFESgi+HdG9p3lL5iExv9dpcQbNM
wQ3I9BafDQInmfxjvVElU+otesVuvVENd7bq4X5N+AiXx01DRmQ4gpTa0zJE
NrRKqzhBWltRU/PMpvRCM3zwN0Af5fhfMZ8/GvUpTG64y5Xph/Hf5NehEMpM
2XjiEHkyHOFFo+Ftfu2VqDYJ7Uk3piggKjQ7Jvbl5PGijdCnx39ZNLBovhwb
vC6z26LjS7vLM/wV3UVYLWTYHRkCJ1/yQrr/tdfT836iM2nlnEIlX/GzN97c
tOk3v3xlpUyhAOckEDntgid6F54oiIqOIzONVMxStE/4UfJkZnGTpVYcT9In
TBRO7IVUMq9aai4p5mJRqbOym/G7GeVdpbzO4ja7vXosX7Bw4UIZJ2Q4bBkm
FbdyG+fa9OYbP1shVyk4OZjxj/HDr7+GH35BLWjg6RSyU+mZ8HzPpk9wHvkO
5EeGo64fGd3PE8EnTzO5swgwODFYEIcJHqNhHOnsZq3WbNdhpIAIz2j45jcJ
T38e9IAPsCoSxFMoBIcpkPFZtcIo7p+6jl+BK+TbQGvUI3JhUi9FO+LZjBLO
VBqdZrPLoHRobEGHM2hTY/6qiXH+S+LEtprME8tgkPmh3C9vQ7PRKvF/YUum
NK1bin07XfOUxvWjmD86ozMeN1aMYsXRxs5lHxib2XuA4sRFQb6FNDlt+aLJ
F1wdNXzJ5PCAlkHwKy4m0riB7srDVnHmle3J4dlURh4PJ+C1vtTK1qyKiJA9
cMuqvst6E9HZ+wcyZ82dnwORsk4p+F12vxUihAJfbkPSr9GYtdBSuoDbmp/q
rcgeWL2loXbT4o4SCLiM/lx/69Jqjy2vuaCkNWnfGmpc0RCfMT3lKV65uD9S
2BA3p9/BvWVLB+bmlPZ1NIVqNs0tijYvnVa1ZMH8wnj/vLlZnqbOWfGwRq+W
cUqj3lW+duXCrHC+T8epnC6Xz6hRGULVeZmVcYc9XjNzCc95yqc1J+JNqVTY
WxJ3enKrx7KK59SGTN64I3dwyWBeoLY2xV+JeGgBvWKnPA9tFP8fwDWHN+13
RkbxulRBns6ZW452O3udvah56dZ3/Fn+gr0fmuZ9OGtWu1K3P29TWG7yQ1o4
7cO1V3S1/2UhaF7tq6fF0T20TaGpInlafLubDP+fO0mKnxN+9pqpouIdE9nS
jaUhndQWbDOUo4x2y0peQUZ/MqlxztrNQrcdhMXYTyFGeeJclExa5S3Dip2m
aM28HZ3x5tKIMqu9pSmYqC8KOzWGQHnP5o5AVWmh2yTLiIKOyrl+Ib8hXl+Y
adckNz970/bR65c1ZduVRXtffaB1+9xSjUIt57BMqasYvHzG0+mxb7Zo/eX9
l377tzc8+Jd7Osa+E51VlN1YGLKrS2qdheW10TOf87jxK1ftmFdkCVdEsirC
gimYX92SndiwfVN/mTGQH+wzGGRKCH2K5/bEmwdWri2c+/Ud04v7t+6/9tKN
sQ2jV7WZLCal0WEymI06jdVq6Hvwj18pvvrO+7529fLKmTe9dCLVGK/rntPl
b5tlClXE+G7oAy+CMekz8gAqRi3ozuOoDeJKh5HrXNyGE9tq8Ypa3FCLi2tx
uBbXjnINKasuI0O3qwSvKcHtJbiyBCdKcAkceHIjwgEwcxLu0x2E7x2D26B8
HdaNjn+W0kBGVzmeny+PjmI0YulvHMW2YfmiiTfSwfENvAqR5cA7YtwujutF
RN4kTEyZ6JGdO7GjPGcels1GP1O89qFNXXsWTIsI5ryZOx5aH+lI5RiUMg4r
tWpttLSzaOCq3jjvruucU7D6pv7oE47SefWRtqZad7B2YW1qYY0Xf7P3votb
s9rWHnhwYc9j9163slptNGv1RovB7BZUBpOhY9+jC4w+p7Fi+bWLKxfVh/UO
v/myJ1bn5nctJ7ssukG2T8mDiGydn44vP45KyUDdRLbCASDuv2RUKilhJcWs
pJiViFO1pskp21ZxWz40USvOZ+fksymAqSXicmb+KOdKuaxZYj+YJU4wSJi8
WJI1yjlTbp8x5PORt5Ks4pfP6tOUi+eUk0GwzQvDQvFCqZBcWP4U1wD2/+ph
0siTjT7x3oC0u+2EtHZ4QtxkU09GIBpyj/p8uGk9e+h69tD10kPXE1UzaUiU
rimZJs8dc/U3jU0oS8XEy5iv0uH0WS8TABOmzOIT7Zn4M25TA7kvun6+eGLv
m6O0lPx5A7b7o5R/qnrTQxctu3d9ZVb7+qbqBalgwdI7Vyy5cSCHbH2bvqE9
9oa3vKdk7QZPxdzq5WuzM5tWNtYumua/8op9+3HH7P3z8rK7d3ZOWzGnPdPf
1LWgtHFHX1Gya31t0cLZrYFQW+8iblF2Y75rSW+sobrCX7x37Bt57XXTgv6a
+tacwTUXgZ22gC49L75FlUDvp1znLBdF2HJRLhkxR4h25OIpC0Fk9dNK5pms
pPGs5M9MWJ/myP+5FKDTjAFJuQLSekBAmmwC/h6JQsMBTP5HmZRaQ17QSiFe
/AsfarLrTjNTwyFxtkR8SZAqxAnR4pEGaXJzPOSPgBp7yNtL7OWsyR3vMLoC
Q5+6Sic22b9Zc5JNWTqQ8c8n1w1dtuvhFYn8tUP7dgMfMngS1Z35vWum2X11
y1vKe6dBHM4duP2T4cG5j/7z/tv+KfLHB+/a3lvmmnX9d9be/JN9leGGhZuv
BPf1BJjtfXIHykN/SIXDPhz24nAGDnlw2I3DLmnHd1yUvZmMm/PF3U5E3PkY
EdGiuDRvG5cEGpdm7+KSQOPSwDxOXvcy+JzkIqeWfGtNkh0BF+3KJNnRlPIT
0mtRIHq44n4TNlnMo7j2cKg7LoxiJX2rtLB27JQ4a04+p8hGNPYOCTWGydmR
AWmMyF4igahNQWdFyiLSqrIY9fH3KTR65dgCpU6rUKj1Kmz4jOw54xVaNc6W
6cxOsxPGB++rDGp5I5kXVwpui9ltUvNv3K6R6X0Ok1PQKZ7lZTLoDbWKMzeq
IWQHaW8Gad8DOl2Dbkvp46U44cNxL5lpSo2ybiiF7USL7aLnsQfEGQ0u98mi
CCRUIcm64inuUqSlwtGSeSUtWSs2lVcEAhWgfHlPFtkVeT0ChIJZTEJ0jSFJ
nQk4kFMTfxRClJE4g3SWcMik0DkbsBUTvkMpvn5zj1xtVI+VGGxGJa8x6s7M
XV1hziiZVSxuv1ZqoeeRq5xV/RdVLbxhIM8+/aoNp7gilVErbyPvFikFn93q
czj0WLPglp1LEonOyszMrEyV2Wcz2gWDLRxylizY1VSz+8ZDm19Tm8V1nZXg
E24B+fVh+XE0D0SWQUQ2DxeoQCgFxPALRLkVELkVjHIlKc2MnuiMGU4L7kyR
Gc0onBIlE20pKI2meINHJbB1HPFKT0Dc+khV1gOSPypOHon7lYl9GyTVNEja
biANZ4FmMFSRbTFVKXHKogqLqiupMO0BqkxVJnvpKNZC1N6T87dAQN5KXhvT
Trw2ljxdIUy8OQauO0n9veTrxe1/ZCuFuWLSz0+++l46ZTWIviJLJ/5Zyfka
0QY9wC01Wx+7qG5TX6VRpeANenVJz4bG+mWNmYmeizt3Q1spFVqDelP96taY
u7irpHKwo1BD5qZgDGip7N2QmnfN/NxAzbyqhg2zcvHm/htXlNm8foMBxsLh
jEAkkFnTW1jWl8oE87BZXEZlZqq/LKu11B/KCsmNHjsJ3CzQznmzt02ftrqr
QsspS2YR30/ePfm5+K5GHjqTqiTTsrk4loPDMRyO4kgGjnpwSHRQESeOOHDU
jqM2HLXiqIChicNyHJbhhAeL3spMvVWu3QnAHhCk3W9019vbx8iuuIy8PGF0
/POUF84QiPkJRCMEslghkE5EIMNrgfzlmBiSUV8lgw6AbSJOacguYll+MubJ
ExtYlggKgibYraHviIDVFZ0uLJTmFRPSuhV5ufmUyCct8JwPPnvr7IRp4klf
ZcchHOR/bjXfwt4BH3tfJ+hhlK5R4lfkFl+ODwZdwi0mW/oBLj0fP4w3BqPp
j9hCBRYUgs9p8bkcet6sIptrVXr15z8McX8aqyQWtxws7g65ATzWcyl9rAzH
SsXNGrzosZ6kDqtM8kpl4h/DIi+/ktdmskD0WVCaRewiyzCzcEPhpYV84flf
932KKxLfyZH60qPiDjPLKNm6QXZwWpyl5K9y6HIq/x4gb5nIc7qcZ5nOwGli
OskEFl6TLObkwKvUeKhwiXTP+4ciaAgUOuvP4ShCQWm7Jn9H877htdVrZ5ca
FeJfj1BqsqevbmnY2JUX69ozZ1pfNMPp93LTVEaN3GpOe0Ot+Rse2lCB71/1
jQ2VJpfToDO5zSaPSeXyugONK9tqFtX6de4IZwwG1OAEw1np2+VcyeCB8XE2
LuEU/I/FdcKlYAOHQPJ+9PpxZALfpTEFcYdJEKTXhM9+ffg9qZ/8VNTFreLy
jzDKrhIEulAhXiVIV4mHtWSFaZtADEchLS4FWcsG8ZTA9g0xoLVJPfKUHaHv
SX8C4u2jcI1NbhrFuYfdXdqJ1znFLllshYS0GsQWhSbXg8SJ9KnztfwhXq5W
pPPkRkfYnRk1cQr8/titFotcY1BzfzXYtArZSbPX4zKceVFnVPMKvUUva8sK
W6BfUZgzQJrSSASk+VNEZj5J/iHoOfJRPXomZYnn4Ww5josrO9lRHNXgRuIq
AqTajdCd6FlP4t1VgCsKWgtWF/CJAlxAXjZWI4MhgDYijg4D6HDgCNHYKtJv
wKVVJF4RX37cVoVLq5qrVlTx4SpcNcolUoZkBEdSfw0ElKV/z+4BLVYNK+dM
GRSKw0HxhZUBaURYOFWHRS2WnbsFoGzqKxvSS++Tf+eHf8ia37X70Y2Jrroc
KwhLq9JmTesuGryuL4cruW3x2lv7Y4VrHtzcdcmCVMx0KLN+cW3dgqoMV/m8
+vbruadmP37fdauqtILZ7Hfb3Qa50Wxs3/vQAn9+1Yrre+bcvb053rnuwAPN
+w6tzU/OXFZStaQxIs7tNqO1/JMyO0oi60h22Ef+QJVOYUbJolNjp4r+3Yu9
5/w5kCcVGoMqPaoyZdisXhMgtV6jgOhMhVtVJq+VTAAC0mvlXMriMZN3gLXk
HWBwbWtVZo+F/G0qQHq1XE7fFSaRBEIP0ISTX5r+wC2Zkl6iiW8/Tzoimz+R
zpAkbz5vOig/qMiGtHMyKSPKE5NJVf4laZgk9QKaNHlT0u00QTx9vnSLLjSR
rtOduZCmJv1jX5YMDYaXvpiMK2gSlOdJB/7PJtOO86QzJJm3fkk6Q5LldjG9
MZmsx21tZ6U3zp/sG+wbHCrHZTQ5p58nfX8ivXRucjV9afrF+ZL7es+yifT3
jP6JNPq/Lv3mQrqQ/u8lrx5Sr3eHmB75T9PLU9Lfzp981b7rfd//b6QPfB/4
v01S4Mb/myk4LTgtc+n/vxSyh06F10UGo9Hor6O/i10eO5DV8P9YuuVCupAu
pAvpQrqQLqQL6UK6kC6kC+lCupAupAvpQrqQLqQL6UL6fzuRZWTEISxyK3k7
AD5HkALdL+7faOdPI56fi3Iwh2fhS1AG3oDvwj58PR7AWagRz8PbsBs5+Q/4
j/m1/D/4v/J/Q1vxdr4XLcRHkYnvw4L4/28+z+/lv4bM/P/Xvv28RBGGcQD/
vu/zzo5CtOAlughO1qaXPChEaJeyBL3UpfIH+Stq0Q6tSbQEdfGQS7dIRUyi
W5jVRSQPKliHCDpl/0FESe2hLqlMz+vOsD+ahRlkcYV54TMz77wz8zzzvsPA
vDD3cQw3xApi4qN4iFaxKoZxScRxWkShKIFmnMBdjtpFv9FJPzEiUvSAfolZ
8R5JSuMUPVEtNA2FBei/SZTOPN1u27wUesl1BZRp1tjJr4r7W/JWBCZwpm84
3p+IZ1rAUQ34LRX51TTSdt6OzJhCHcwSn3j9DEcC68ScOos+TxvcloO++fQS
c8YBdBVSW3wdh1QBPIKpqeN8LqMeb5EvHLe+iA4MBKEsjuW6nI/v77ynr4jm
Miy88EuNwzKr0VJIxdDA16oOhYr6jO6gVCOmqJ/faT7wsb25aBM9fshbOFrO
aA1Nfui+col1jAXy3V530XPucwe3eYoMZmN5OsnjEUT23F75AVO5qAYX/JDz
qCmkRkukEY/9ohlYxiKaCtEd1NEsrP/U4UqotPgZRigUCu1LNuo1WYslaWDC
5e7fDToE4UWOoDWQmxhjSXkby6Ug1pDSjFHAZcb2L/4+HnJc3GNtbJ4l2HXW
wK45uQ2UQX5lj7ZwzpnLKl70/IjxdPHN61dvr0ab/+BwZkJl6cc9/bcN3lmT
yc2/26nKDXOBq5U7czZc/gG6jwBXCmVuZHN0cmVhbQplbmRvYmoKMTEgMCBv
YmoKPDwvVHlwZS9Gb250RGVzY3JpcHRvci9Gb250TmFtZS9UQU1TVFcrQ2Fs
aWJyaSxCb2xkL0ZvbnRCQm94WzAgLTE3OCA4ODQgNjgzXS9GbGFncyA0Ci9B
c2NlbnQgNjgzCi9DYXBIZWlnaHQgNjgzCi9EZXNjZW50IC0xNzgKL0l0YWxp
Y0FuZ2xlIDAKL1N0ZW1WIDEzMgovTWlzc2luZ1dpZHRoIDUwNgovRm9udEZp
bGUyIDM3IDAgUj4+CmVuZG9iagozNyAwIG9iago8PC9GaWx0ZXIvRmxhdGVE
ZWNvZGUKL0xlbmd0aDEgMzgxODAvTGVuZ3RoIDE0NzczPj5zdHJlYW0KeJzt
vQl8lMX9+D/zPHvfR/a+s1eSTXY3m2RzkjzkIickJMEECCRcgmJBICIoSq0n
ilrvox71bEXLEq4VrFpFbau0fltqra2ttrZVaypetQWz+X/mmd1coEXrt7//
7/VjJ599PzPPPPPMfOb6zDzPAsIIISXailjUMacrEkP859Kj8DVv6TmDa6n/
W0mEsHHpeRvckeaSZgj4HUIiyYq1Z57z3XdrH4XjtxCS6s9cvWkFje9/FaGa
21YuH1z2F1GqEaGb3oPA+EoIUG7X5SGk/if4fSvP2XA+jX9ZE4RdsnrN0kHq
Xw73dTaeM3j+WruW7UBIY4dA9zcGz1mezt/L8OVcu2b9Buq/6SVyfu265Wtf
OLohDPGrEDJ8ByHx3QilbkQTn2+C+w7agfaiA+hH6Kfol+gjLEMD6DL0FPoT
ehd9iI5jhMXYgO04F31tn9S3hOcgJfs0EiETQmPHxt5JfX/sHYSEqkkhN4LP
JAhMhIzpxkamh6VuTCVTPxPJkYa/VsO8CKFH8cjYMaaG+MfixM9cQY75K46K
707tTN0zJTtr0To0hM5Hm9BmdAHagi5CF6NvocvRFehKdBXo4mI4vhpdg7aj
a9F16Hr0bXQDuhHdhG5Gt6Bb0W3odnQHuhP0eBe6G92TPkf8d4O7hT9LztyH
HkLfR48C70cPoAfRw+h74H8EtP8o+gGE0RDqfwxC7kXfhdCHIJTEImE7wSXQ
LjSMdqM9UGfUn/El0dNoH9oPfBxq8yB6Av0QPQn1+DTU7DN8GAnJ+D8/Jv1+
Fh1Cz6Hn0Qvox+gn0DJeRC+hw+hn6Odf6cxz4yHE9zL6H/QLaGtH0K/QK+jX
6Dfot+j36A/oDfRHaHXvnXD+VYjxGsR5PR3rTYj1Z/QOxByBmDQejfM7/uzb
fApH4No30FtYgj7BDDqOxuCI1N4tfA3dztcjqT1SOw/weib1sRP8pIYeHq+b
x0DHj0F9Eh85viNdGz+AuLtAgxn9nVxrP0vXDtX3ExCH6IKcOZzWxQvpmiDp
PDl+7Yv8uWH+umfGU53QKC3hryZp53eTdPhn9BdeM1R79OyE9kiMtyAO0TJJ
Y6pu/wjXUu2Ta0n45GvIudfA/w6MDu+Bpgn/xtfE39Bfx4//mj4/gv6O3kef
8N9H0QcwnnyEPgb/PyDkKPhODJ0e8im4f6J/oWNQg5+h0Um+0WlnRlEK6hhh
jBnMotTE0UQoLwIsxCIY0yRYimVYgZVYhdVYAyFTz8jHz2hPOKM4yTkpH6LD
epwF46UJm7EV22DcdGAndmEPzp50zjJ+xg1nvNiH/elzRv5Ky/i1LohhmhQ3
F0fxRvgO4TCOwHEhLsYluBSXQ0gB+GPgr4BzUZ61qAMtQavRMeHbzEuQfhaM
Kru4xsWL+hcumN/X29PdNbezY87s9rbWluamWY0N9XW1M7ma6hlVlRXlZaXx
kki4ID8n4Pd5s13mLK1GrZTLpBKxSChgGYzyG7yNA+5EYCAhCHibmgqI3zsI
AYOTAgYSbghqnBon4R7go7mnxuQg5oppMTkakxuPiTXuKlRVkO9u8LoTh+u9
7iSe39kLx9vrvX3uxAh/3M4fCwK8RwkejweucDeYV9a7E3jA3ZBoPG/ltoaB
ekhvl1xW561bLivIR7tkcjiUw1Eix7t2F86pxvwBk9NQsYtBEiW5bYL1Nwwu
S3R09jbU2zyePj4M1fFpJUR1CTGflnsVyTO62r0r/+lt1yQ1aMlASLHMu2xw
YW+CHYSLtrEN27ZdkdCGErne+kTu5rfMUOTliXxvfUMi5IXEWueO3wAnhH6N
173tEwSZ9468NzVkMB0i8ms+QeSQFHFcTXA+c4wgb5BDKJ/HQ/JydZJDS8CT
2NrZS/1utMQ2jLhIqC/BDJAzT2fOGHrIma2ZM+OXD3g9pKoaBtJ/5600J7Yu
cRfkg/b5Pz/8wXl3gg0MLFm6knBw+TZvfT3VW3dvgquHA24wXdaGXdEIxB8c
gEKsImro7E1EvGsTWd5aGgEC3KQOVnX18pekL0tk1SXQwNL0VYlIQz3Jl7th
20A9zSBJy9vZ+zgqGntjV7HbtrsIFaM+ko+EsQ4qJdCwrXfZioRrwLYM2ucK
d6/Nk+D6QH193t7lfaSWvJpE7htwOw9/R/4qKNu02JnIpORiv8Tdy9jYPlJb
EOBuhC9vbRWc0EB18V5So7VV7l5sQ5locJd0DHI0JR3wsP66JnKKJZfWNdk8
fR76+YIs2dJ5EvoTkklpaSBgPE/0Pp+bNRqbZCjX3bC8flIGpyQqTGcwndrJ
88kQXaRvDFdISHU2ZU6xfui5EMZAMnwQqUWzO4E63L3e5d4+L7QhrqOXlI3o
mq/f1i5va+f8Xr62062ke4qPni+jvgTywOmMh6mDNtgYsmWqlffP4v3j3qZp
p5szp93bJN7Wrm0kcW86QeSGHgSFFgWaB68u0xVD12yE0c3bOOh1a9yN2waT
Y1uXbNvFcdvWNgysrCBpeJuXbfN29VbZ+LzO7d1i20xupUOtuLW7tiAfxp7a
XV58ZecuDl/ZNb/3cbBl3Vd29w4zmKkbqO3b5YNzvY+7EeL4UIaEkkDicRMP
SWkueCR8fNvjHEJb+bMCPoD3L01ixIdJMmEYLU0yNEyTCWMgTEDDOD6MfKCS
zCtBxTDcNriXkeq5sG/ltoE+0rmQEaoS/nACe6tRgvFW78KMSJGQeZfXJuTe
WhJeQ8JraLiIhIuhYcBcCMohY9K2AS+MU9CgepEN06bIkiTdybGx7l7PYdtI
nwea2kKQ+b0JaQjGfqG/BeLNIjIAwbMSW5cOknygnl5yrdjfvLQPmm0mQYjS
nJBCCtJ0ChCjkb+GNEe4aCnUDVQgf/1W8CS29iX6QuSmvav6+OasSaAmbwVU
O01TGCA3ivRt03ljfN+EriDzX0Eghbyhrl4aYgMv3KyPKkmsgJwv9cKppQNu
0LYALe2Cpk7HUpmNhiyHIVEQWM6LzJY+iUixWL9cKUtIw5Ag/JFjeZh0SaFf
3NdHM8/7rkhHgHtrEnLIUWCSKtMXgHbgVDPJC/xdAVklUX9EkulMorne82Fk
IZnmUxLD6YTS3zwIgz+9Xg4h3rLMxRIyRsjTaRyioWJScgXonfV3J8ce9m7y
TPoU5HvJ5EAaJrI9Dg0b9W2bHpBYECrIl0wPVfLB27ZJlCe/gOpLohwnBMJy
HlbtYCriQ7J7j7927HLpeyRk8od9kYSos7EbVpI/RGLoCBoUgbUyUiwdG4Nq
wbukbJL517DT4Uoy/xx2hgCfDjvzAf+g+ITiY3ruI+r7kOIDiqMU71P8ncYc
oXiPBv6N4l2KdyjepvgrxV8o/kzx1rBTCvgT9f2R4s1hhw7wxrDDAvjDsCMC
+D3F6xS/o/gtjfIa9f2G4lWKX1O8QvEriiMUv6T4BcX/ULxM8XOKn9FMHKZ4
ieJFip/S2/6ExvwxxQsUz1M8R3GI4lmKZyh+RPE0xVM0zScpfkgDn6A4SHGA
4nGKJMV+in0Ueyn2UOymGKbYNWyPARIUO4ftRYAfUDxG8SjFDopHhu2FgO9T
fI9e9zDFQxQPUjxAcT/FffTy71LcS3EPxd0Ud1F8hyZ9J8Ud9PLbKW6juJXi
Foqb6XU3UdxIcQPFtymup7iO4lqa9HZ6+TUUV1Nso7iK4kp6wRUUl1NcRnEp
xbcoLhm2FQO+SbGV4mKKiyi2UFxIcQHFZopNFOdTbKQ4j2KIYgPFeop1FOdS
rKVYM2wtAXyD4hyK1RRnU5xFsYpiJcWZFCsollMso1hKsYRikGKAYjHFIop+
ioUUCyjmU/QNW0oBvRRnUMyj6KHopuiimEvRSdFBMYdiNkU7RRtFK0ULRTNF
E8UsikaKBop6ijqKWoqZFBxFDUU1xQyKKopKigqK8mFzOaCMopQiTlFCUUxR
RBGjKKSI8mDxsDkMvggNDFMUUORThCjyKHIpciiCFAEK/7CpEuCj8A6bSIPO
HjZVADw00E3honBSOCjsFDYKK4WFwkxhojBSGOgdsugd9DRQR6Gl0FCoKVQU
SgoFhZxCRiGlaUooxDRQRCGkEFCwFAwFpkA88BhFimKU4jOK4xTHKP5F8U+K
T/nb4n/wJcKf0MCPKT6i+JDiA4qjFO9T/J1ihOI9ir9RvEvxDsXbFH+l9/vL
sNEL+DPFW8NGaGD4TxR/HDaWAd6keGPYWAf4w7CxHvB7itcpfjdsbAD8dtjY
CHiN4jcUr9Kkf03xCk3sVzSxIxS/pPgFTex/6HUvU/yc4mcUhyleoniRXvdT
mvRPKH5MM/8CxfP0fs8NG2sBh+gFz9IbPUNz/SOa2NMUT1E8SfFDiicoDlIc
oEk/TpNO0qT306T3Ueyl2ENvtJtimGIXvW2CYifFD2jSj1E8SrGD4hGK7w8b
YNzF3xs2zAQ8TPHQsKEd8OCwYTbggWHDHMD9w4a5gPuGDRzguzTKvTTKPTTK
3TTKXfTcd2jMO6nvDhrzdorb6AW3UtwybOgA3Ewvv4niRoobaJa+TWNeT2Ne
R3HtsKETsJ3GvIbiaoptw1m9gKuGs/oAVw5nLQRcMZzVD7h8OKsFcNlw1gLA
pfTct2jMS2iUb3I7gUfVDa73VU2uNxSzXc+A/AjkaZCn5PNcwyC7QBIgO0F+
APIYyKMgO0AeAfk+yPdAHgZ5CORBkAdA7ge5D+S7IPeC3ANyt2yl6w6Q20Fu
A7kV5BaQm0FuArkR5AaQb4NcL13pug7kWpDtINeAzJQynzHH0DzkYo4DVyIX
vnhYT7rjRcM60rQ2UKwf1pKmtY7iXIq1FGsovkFxDsVqirMpzqKooqgc1hBU
UJRTlFGUUsQpSiiKKYooYsNq0k4LKaIUOgothYZCTaGiUA5DpSSxgkJOIaOQ
UkgoxMNKUtUibgHw7yAjIO+B/A3kXZB3oDr/APJ7kNdBfgfyW5DXQH4D1fIq
yK9BngT5IcgTIAdBDoDcBVXxHZAk3ko1vXlYS5r8Jqqc8yk2UpxHMURRR1FL
9TCTgqOooaimmEGLbKDIotATPM6yLDPMuR54kmXQHpBDICyLaF4uoOiitT6X
5qyTooNiDsVsinaKNopWihaKZoomilkUjRQNFPUU2RQemnk3hYvCSeGgsFPY
KKwUFgozLaaJwsjdCRwF+QzkOMgxkH9BBf8T5FOQf4B8AvIxyEdQqx+CfADy
V5C/gPwZ5C2QP4H8EeRNqN3DIC+BvAjyU5CfgPwY5AWQ50GeAzkE8ixIEmQ/
1Pg+kL0ge0B2g9xJap8ZpTreQnEhxaphLZhCeCXFmVQtKyiWUyyjWEqxhGKQ
YoBiMcUiin6KhRQLKOZT9FH0UpxBMY+ih6KbIkIRpqouoMinCFHkUeRS5FAE
KQIUflo3PgovhZBCQMFSMBSY9kjE3QccA0mBvA2KfQXkVyBHQH4J8guQ/wF5
GeTnID8DRT8Ochnrd13Khl3fwmHXJU1be765Y2vPxU1bei7asaVHvqVyS+sW
Vr7FBrhgy44tv90iurBpc88FOzb3CDZnbWZkm5o29py/Y2OPfCNWnNc01NM9
9NbQx0Ns1lD30LKhDUM3DR2BAPEDQ3uGDg2xybGnOd1QWWXj1qHrh5gsOM+g
IawmwZ4huapxQ9O6nvU71vUI1hWvYyo/XoffWIeZ6DrcsW5gHQOxdq/z5TSS
2CXrjNZGzbroOm4de27Tmp61O9b0zFmzZs3Fa+5Z89Qa4cVrrlvD7IQjhlsj
VTZ+o+mcnj+cg9ETzBjSgDzNjA2zsjUHmRTC6H0mxY3hs0EBZ4EiVoXP7Fm5
48yeFeFlPct3LOtZGl7SMxge6Fkc7u9ZtKO/Z2F4fs+CHfN7+sK9PWdA/Hnh
7p6eHd09XeHOnrk7OnvmhGf3zIbw9nBrT9uO1p6WcFNP846mno4mPCvc2NPA
xl0wgyAn/K11bnUedQrkA461Dmat4w3HUQe71n7Uzlxsw2rrxdbrrKwavhj6
ZXFZrrPcY9lpEar5A1axVrdVx6zVbtUyUS2nfVn7hlaAtPdqGfV16nvUO9Xs
HPVi9fvqMbVgpxrvVD2l+rmKnaNarFqjYtUq4mc1nCpc2KhWupTcrIiSrYoo
a5RzlOx1Sswpw7FGTukLNtYo5igWK9h7FJhTBHIb35eNyRhOBifel45JmTEp
Rix2Y4ywBsBKSB1hg6sR2uNuIxZiMC12dXeFQq1J8djc1oSkY0ECX5nwd5Fv
rnN+QnRlAvXMX9C7C+Nr+3Zhpq47kUU2n3n/Zdu3o1pHa8LR1Zu419HXmtgK
Bxw5GIMD5NhlRLV9oUXrh9av3xBaH4IvkEXrIWTDEPzxwPANHNpAzmxYjyBK
6HM+JMZ6giE+0vqhxUOQBpyA4PV8MPEt4qN8Xhr/1c/nluS/8cH/J2/+//bH
vHgREiKUWs/+VqhCLBKjctSOZqPuJ5AS34VMqAK/uKe+XlIgfhK8DHLjF5EE
YXwXpxcwSputxlsiuobt1DbXiK9hulHN6O9ffx6+DuvKI4dx5PWRV0Y0o89r
yyMjR0YKo1jr0fKSpWLEYpHImx1mSoKBeFFRrJopKQ54s1UMH1YcL61mi2JO
hs3KhFQzxI/Z3342h20Y9TGbPJVdhUIc8ptceomEdTmV/iK3urXdG8+xCgUS
ESuUiIPxWm/Pxpbsn8nMQbsjaJYBHXbg6DNC1bEPharjZwjqjz/BvF3eW+0T
bVLKGaFUcleO0+ArtM9oVaqVQpXNZLWLJVqVLK9pcPR2q98kk5n8VrufpOUf
rQSNmMaOCZ4VZqFsFEBvkmGnp/dx5Bt7e49cjdu8ybG3OSc58iuUXrMSGbHK
GJDLvNky5BZ4sdYb8MNUzjk5OVJgHatQBB0+r9cpUxqRN9ss1jnm6nqEPchc
U1OjM5WXaYu0oNnFi/qLrO0jMWyJLOq3mg/HirZccegQNh9a1E8PC6MwONmm
ZmMvOfhP7lYYDYX6/EYjrbcg6xGrWG92IBAvxbSyTGIv6xHsUoiMZYVF5U6F
4IyUda5A6SgJhYuzRAp8nUjjrS6qbAxqRc/g/XjNEl+eQchKNUosGFXp5QKR
Kc8ruFBrkLOs3Kh/fvQ1aI/bERLEoWU6UQiVoXsy+nUxN+61yg0GOSJ7ufmB
IrK7KbcGwaDZXVgo9iXTBfeBEcRJNZ3FZuIrJuYSJ+6GAkKBQjUjISjeSDmO
jMQiI9BIdeXQSG27vmIyhdE+aNgCryc7UKItjhd5QCUG0tKdLC4OM16vljRz
/cShIB6o61978ezU9zwFBR7csPHBc6vM4bpQaX9DTupRc7R5xmU3ltcXGOuc
FfObvvNkaWupC1/asHZedY4+mC9YmR/M6bywO9JVX6yRxeachf8QrM41phK2
SM3ovwpmRa2p600FdeTpzZyxvwkUQi/07Kup/obtKPQk8wJSITMeRB4USBcz
QGxafZcADNb9JVG+rFFi9HLSeXxZR0NHRmrIF2jsCDQy2xNfNQHQlT9LRQeA
Yl08Ds1HZEj3dTIKGLKcDFERaVYCBSuSGWsWDNVf9sotHb13v35ZfFlPvU0m
YgUylVQdbl7e2L6pJz9yxgXtjSuaI0qZQiI4ZPFadCafxzj3/o/vexCjH8zX
OQI2nT1gd+ZZFd6Qt2booZXrHl5d4slxS8whBP2YtLSnoaXpkAudS/X0FNIz
dyKErMwNSIrM6UKawS7npKpOG18+G7HZOeGkxoDpYAfd71SvoC2HmdJyhJPa
ydP9P/jXo6kX+VbS9tgHD85LHQ0tvnnTZVetvmlpIXPH8Oi9rbRBdN7z7v0L
794w87Pry879HtQ8lIm9BsqUjxK0RKRtMzdwaqnerXdDmaxmJeTIegDnkjrc
p8TtgYDIkmn2Fj7fys4gn+8gWY9woqnNPkTKCx2nPBLRkCHCtu/rSJI2D+aE
ruT1aKcdQvFkaunoeUQ3zOVSlUwohEaRiuErpGpyrJamNuFfkOMzYQKQUzXJ
LEEnTAPy1CG5CSaGgEmWulFuDpK+sn3sGLsUNBZEj6c1JtYnmZs4o9KBnA5x
jhq3i80KJW4Ta+RweACfgfRjR/fBsV5vESXH3tgNMUR8aVW4TQQrwD1cdqeF
H1NJEdMFDBGtHdKW8yrjtF9juuNtabKmMrNoRpdQRDloqQ9vl6rkQv54vcIV
CwaKnErQ4yAJFdznzDUrUg/IzDlOZ45VnnLKNXKRCL4EN+cH5ZY80BY79h5j
g7kvB/VlRmbE3LTHofLOlcJKer/ebE63/+XQ4ieNAVB60kWG/128TGmyw6KM
CcDbCtq0x8DYPHO2LnJWFvoUEhHDipUyqdmZY7Pl2lRKR3EgEHMp8cre7UuL
pSqNUmXKtmZHbHKlSqn2Vxeym2S0jcjSNS86F2q+Cv2GloWTK6NRUyQiC5vN
1iSzbI+vUKGQwcF+5It3WhRy80FcgDgUHju6R+Nl2gqTY0c5Nzkyaci3kn6b
ItHCsMiV0+nqGZ9cyexKrC8yrcZioI0jIzFtkYZ8actnRIqKtEWgnb1f710y
nYpvCF5MJm+YxrF3Suvg53FcRGZ0Xr+ic+WOqN8XtSuY1FUCnSuanR116djU
LYzcGYFwhzxe8Gi4NupWYLMAZytduWX+XbagRemTaWQiEXwJHMffUmplrJC0
HPvxP42Hf7MorvaW5302yuK8Cp9aBVel60GQFOrQDLSX1sO+oFoWVquzyNMt
ZzgG2IOcZXNziSJ06gDTlpsTzlZoyJFCLlIn8Zb90MNJ5wiTDZ/x4QX0UV4O
03x5CKya8hDVOug8oqXqHv4a0szomKo2EAh6jUbDiQrWO1lTUSAw0YwFSY3N
r1/rLQrlWFJP2itMjEAgt4V93rBVVpqzPVCc69N/ZgzlBHSYZRX2sC87bJEt
NPnMcpW/Jsb0x7dUNl3XNrpARruoTHB1JKJ0lgRTwVBXV0dO420NzGKZRiEU
KjQymOs6xt4RWoR+pIdxbnyuy2KegbnOCd8yZJkYrhdyUnWX10zNSNw/3j+n
zXWnesVEjx436vmpbtKkL7R03P3O7be+eUsr8I4b37y1PfWeu33rwOAlHR53
29ZBQuaW76Z29c+579iOu44nFs2+79N9Kx7eOLN58/0Lzvr++TVNFz5IZnRo
SSz0aDvKRVvTo7lPdJC5EWmRg/kRJ0VaP59LMIpDu0UihTc5bi/j0B7O0KkY
H1+JhRciLSY9y325CzOF9k4fiQWTp3m2/pIfbl2tdPLjsKIwBxeGuzZs7M5P
jUQb23PXnlfTE7ezl53zvfVVqaXjveiaSERsql588ZL63jx5qjl7Rg9fv0bh
jVC/QVSJttOS75Z5dDnkFRBkhy70zB6dR6YsyGS7gFSa3NTlF5Ty5Srlq02Z
qbYjh/mZuZw3+0bgADSw+ytcD2oQphUQTK/+Mh2At5OFeHpLuFGsUEk8Z1/4
zdLwtzoyLeLbf7h9jimfy60emBk0ylLrpreNC3z5ZrGvbrDG4Gq/7/hjdx3f
uWj2d//xvTNuv2R1brzMrjQUMa8uf2jjzKbN988/+xHSWh6Ccadm7B0wJvyo
GR3MzGUzmVv3+mK+mMJGVhlIESZDcSmS4YJ92lJwxqqMAqqSuIBTzLQJc7uM
vAaMZJt3UsMnw0RIS80kzQhpSLzNNMIb0eGvKdmJviWYMlsWj8+e041sEXtN
2yU/WFq3vrfSKheAmaQq6ljTHG0rsUfbl6xc0h5tGLqnL7ywozpLLCSzq1we
bVxYGuJChsicZSuXzY7iS1fccWax0ZVtLQy78qxyT47HlFcdyK8pDEVn9Gzo
7N/eH1aZnVkqk9fqyLEq7B6bwV/sCNHz60HvCrC43oVemo160n0UicDi2m3W
inQZPeh4e8cxqVvFcOTQ6GGyWvvCWBPW0HjH82SaHW8IvcubiE8onTAcg/GT
ekJGTUgZez0xGgX3OXItiuMj491Nr7DkOpx5FjkxgCD3RhhjHgILyIe60msr
ZAFjoX0f57O4FRYTsR3lnNLimmsW6ubSiVlXXgMrd/MRyKGu3Kp53QqAkuyf
FofMJfwkLSAzCb9GykzNMViFi1mtUOOrjuWU51i0UkHqYoXQUhUPF9vlQlyJ
cYlA4YhHwkV6sSJMltRYIFFolYILyJpbIMtSf2Zl39QaFPyiG8oRGjsmzoJy
VKGL09aPNCJToKpoVAHDRTsnq1KYzEq/16vITjI3czrOrCidmzc36pWz03YN
aiYVzhIpL9eVmzVH+GNdOR06OPXnXjpeZibIetmMiTJeen2RPr3VkD4iehD+
QWTIqy0qb8jRCX/OHBLqgnWlFeARpV6TMpbyokipXcb+Cb8nULriBdFyl0rw
MfMnVmYvjuQXGllpndmhFgrVDjNb/NlLJoeGPxas8uUahazcoP/Mw76qNyuF
AqU567Mc9ncak1IoNIb8MMrOghHjPPbXqAhxODdd+1JTcZJZsAcFg6giyTRw
Gi1rwh+ZsCmpKMafFeNi8sRBSgz94uLwzLwkNnO2N7IxuyV7ezbDZXdkD2Sz
6mxXNqMQZGcLHGD4cyoFtG2HWYPbHcfCLTPIjpIUPDPe4hTtAmSOZGbWEN2r
6e9f3D9C9m1C/eeO9J8LY/ahcrI2o5r/P5wb3j4iQz8YPyWTpoCikvTInw4R
8JOCmI5SxqJYvJQ9LyuUV5CrLd0+b9bGM6IzNu3ZeIY2ODNas7StSCPXykUy
e+OiNZWrbh7I/3Rgxry4ZVZNSV/YpdKIxRrVrMpaf/PqptnrW33xvJq8LHu2
XWUNmFw+h9epz+25fOFrOl+Rp4yLF5OdgIvG3hEg4VqUBzboLel6lXniB5kB
ZEAh5lIwHAyyeIlHIIxmhp5oErdyykCLrVHTVs6P1OXkwSwnbM+M1DVkCjSV
p00IUhn7vmoak0yooGHCoEjPpFraQzJGlVhrNPLWBSpect2CgtmzGnwwdDld
uRaZAix7f9ShyK6vb8pZuu2MnNRxbV5dkSVaFHeWDJYU1hdk4fc2Pnl5kzZQ
kTsoV8sEAplaLvRmjMyUHtYCqjmX7x4qP2tuoSo7npN6tX5WrGMFjCdNY++y
HvYVVILuGt9zCj7JbOD3nFzINb416SOPnvUtggO4CRVCa5TDkrcwny9+Pnl+
zUnbM8vB0Pjm06FYevPpP0tpyi5UZn4U0elRNHkLCooiFJsrWs4In3nP6tK6
8x9YktNeV2KUCtksjTZQ3BRbstJa1F5U3FoWUEoVYkHC6jWrTR6rhtuyZ8Pl
z26thinQqDZ7LRURaHq33tD0jRa/K+CS2fJIe2uFceQl4TkogMrRzWltyW3l
B5lFYI9HmHWcTO9plJcHbQJVXqaxQF9t5qTmlvEdyeY9nKpd2JaZ+WhLqeHt
c9r1pV81jcnrxsl9NmY0jTc6NhCYbLeVsi/JzLlOd45F3nDrwhXb+3KKltyw
uHVzlZxvcnbFsfjSeOGskEGXW19sLSyKu7MzzWtpy1xoUUtJs5tRif+UaWuj
xfVNhXOXl5Sd1RVTZ5fmEL21gN72wfgbQsVYmLZy9XpPPnnfMlQsSBLNedh8
fT5jy39WQIY6kxK3I4FGwLR1CAYEzL2ChAAWWvYIaITsrxBybogTeSvQYv4H
UmlUjJZVSc0K3C41QwTpvzh7phGFjsDwNpIe6frPXdQfGlnUT7aSX4fJLsJr
/L97b35YEHk9k9qtYWrrZgzBOF9PYnZfrm/0TVtl/8zaZc1RtVQhYRmBRFkx
f0Ptxt3nV1af9/2z1t6zIvoxu2BxdFbEwuBj4fzy/pnZepNerPNYjC6jWmU2
aas2H9iy8anLGmuH7l3kPmuTb0ZXBPq+ZewYc5vwfLAl1qdrxahBYEIv3h3N
88uS2LE7PssaSE7sGbv2cdEmd5umiTcEeMOtBrr5oaLRQ0WH+NWl7BQvmjQ0
8u3RQLUgmrzygsknM+fwWhEwtwkkMpFYa8k22YJWxf3E8MvS36+wx3y+Qod8
rV4vhKA1vvaNncHGHJVUIPjQ4dWLxRKx1l8Zmisz5ThKI6PhzGYS84tIqSPH
JGtdcNWCsFKttAQRi2ypG9n72F+iajQbLcZM2saao46K2TJvS1HLsy2sqwW3
vPkTBYYaV/ykCzu7sLkLd31w2IBNBowMGgOjNhgGyth/VTXlufNrn6hlUC2u
PVzWol6ANeyClzj3HDpRQNuoGenvBxOSn3nJJAze/ld48POHjeuZfGd5C/73
N5+4d1XtS7WMoBarv/D+iyZyMCUD/ZkZDCrFaKTzVwCWgzDPm0xO1jBpc6AU
rITiOP9NxxtPzIiLA+NWAXmaEggGVWzax95n1Kwy6osHr+oOzTYo9EXh37Rt
7AxVbNg5tO67Z0a0nqgrFImHvHmlS66cm9fuwTatIfXDjmZ/mV/XMStQ5tdX
NtXstrr0ouULy2dHs9iBaNg8wzN7U1fIoFL6jA4/I2H9dYuqaofmxXxcX4mn
qjRmMs2JVA4GvUuaZ1/QUyCT5qf+1dRhCZW76ueY80pH5xVEGaHe63ZqYsWm
QISsGS6CFc8vwL6IoXMyK005s3g4lpeVZAZ2w+JCk2nmmiRu56RcQYuv0dJG
B+bMrgIZafitl+FTiz9l94+3DaDFn2g8UEPbwP5CYS/0+QvtCr2vPBBdUpKx
FTKceUXzgi3t2dmZRo9HZ7aUOBrrRndmQibbCVxN1cqrl5Ix++yxY3i7cDYY
Uh7UkNl5MjJPITsygH0lQy58wV7OommmuX8FMj+xx3TiuamlShdCT+Zw0nKg
yeDN03Our+7uqZzR0101nnd2M8w7kFMoRbStoqy5rbI8XUsHoZaK0ZJMPgsh
h9lIAd9G5GX27S4oMMqSzH5OxSFjtlyY02xv1I6rnd8vocugyIhmNPYW6Xby
k0WbVIggPkmdpB+vwjAmxthoZA/KHbGc3CKPTpz69fTSYYkky1MY8Be5FGp1
6jgOK+QeWOEKBeQx6yupnBNr57MP8FKFjg+Vq7P1qVdTBVkOWn68GcpvQDXp
0UqtNGAwquQyrERYLkDQWvdyMk0jLQqO8PXB2/z9tt2Z4JPW0Im1kn1ixmge
RFKY4TvQjvTeQKOezCNOZ0xGfhnSUR0kVnkMaSZ1gOHWlskPbtuhema2VDcW
lDUXtFkm633SJmb5EfL8lzzDhWb2HyX2b/rZ53U8Q3qFm65qkVRhj/oDUYdc
6y3xFyyMg558RE/a7LgvvHC8O8qsuS53nknWcmNHaW9DTJvT3toa7Nvc6h7X
J6MtmNYxTwxhL8wcndnRYQpV+UPVQX3Vmdvax0crqIMY+ma6DvL0ROlOftBC
Thh8ju4GU5sfhBSZQUgOg1Cexdc8riMd1VB6DzWj6C9z5amNYIZ/N4KNq+z2
rn8zgk1RC6hjEMavJlgbCkAb03bOh/id86GpO+dWTqpuGd8Ht09eyX3OzvkX
XnEKO+cCQdXm5AUbExvKZmzef8H5ifVlqVFDrKumrDtuMxZ2V5d3x634nXVP
XNlSe1HyvHU/vKJl5kXJb9aumRvOnbNmFrAgd/YasgJO3SxAUMrJK2BPXJZZ
AV/2RSvgZs2c/3gF/O/SmLwCPkkT+LwVMCxCFgVnzqhyj7cFS67LCSvhYOvs
rsgSsgI+ps2ti1kKyQp4oLiwId+ARzY+dXmT2hV2pRaOP135faZhrMqZkZvV
fvnwxvJVcwvVZAX8Wl1zrHMF7TfMQX53aG263wTUMGJyCmRVy1yyiIxVsjJi
/EMPAKO4i5NxoZaA2uBuNrTRHUDa7heTVcWhdI+R/fv400zgk3URXj8i5iBY
/DJJlsWpM+QVQEeZ1kG81WVldqXTbZYLBQzb6gtbZcTk9VXljx45sYusic0M
qFmxVKYwkCfDzWPvMB9C6ZvROxO76eHx3fR6DuZRQRiH3yqF6UT2V20pRwaC
Uncpw/Jb4OoqXEUextn4bfC3yBZ4i1FDdqqQEWsExg/HGwXoJ70P3s9vhC/u
D2lG+uFvyiY75/5fvttX2HtnPixfeW1XbEFT1KgQSBRSeYjriWeXBLP8M9o7
22f4Y4uu6M6bw+XrJQKWFSsk0kB5azQ75tYEqud0zqkOYGfbhtlBtclsKMh3
eA1ii9OqsuZYnSG3PTufm1/Dnd2Wp9AZ1GqDy2TLzhIbzAaV1ZvlynPbPflc
H9SSaew95lrBLlSBbqS1tF+rVVbmIm8BmV1NUx7wuHZ7mxzKTICSbLaYmgrJ
Lw04cVo50DkP80Nb0WjsUExLl8GPo4Kvkggd7QUnX7JNXdgZM8td5lq5zhsp
tbd+oyn7bH0WaZZnyR10FnhGxq/qng1XZrktWrFILhJuzo/owfALzDl/Lv4J
XbO9AF1cKIQu/gJd1aX6m5vFUrHY4ANtbSL7NOzzMBOene7R8iDdpHExizm1
vqA5KBdamn3mjLEwbTuF9FB+2OdXYKpTiX6yvZcJw5Af9eOlE7swL5EBzZNr
hslt7sIt7R6+8NCldX6YAgdLM7sv2ZPntZVXrWDGA1KSRn4SZDrHX43gn3Gw
u6Hc+ZknNMMajyvJXLqPM3jcIo83yfRzCg65PTnNHrm1Wd428ZDDan59+lOO
aZHS/UY8/j7CxOxm0ptK0/v97G7MCgWpj4XaYF28pC6gFaY+BmtYbi/058Yc
CsGLItGPWaU9EvBHrDL2HqFKa1R99hvyfEOoMGjYYJZbJYLCCIRSrWL0XIuF
uU6hBaNYpiYWjnfsmPCXUL4GdGu6F9gdunB+viYvydRxcoemTKURsBUVmqok
E+KUHKuZ2VzUrInK1U0VybGXdwPzgZyKHFRoWJO/2dQmbcs81QiFQlOfifDP
QTIPRcgDEn5nnqR5kqtrqIZE4szTEDY4cZhZGU/R1aRD4S9Fkr8LNZ4ZhYXV
Xo3gFobZJlD7qgtjM8D3nlQI7cOfE7PL2V0M8xCrtEb8/rBNzg6zzCMMMUD9
EZuMvVfudk7oknFKpaN/nNCswyOH9YVAICOKVSiIYoma1bLR1fK0TyBVg5bd
0Iq2g5Yj6Bqq5SdQNrMNmZGPyeOkYTM4ZJIrkswgp+bIe7KsUe6OIK9XDqb+
XhLmluc2e+VaR7N2wjSc0sqIaq1mzeswSJPWppt4Lgorr5NdS7qXMW1HsGmt
lurZiedN4w+ZWPYyCbZXRAtKXWrBgw8KVI7ivPxiM5Z++pYUW8sL80ucKuE9
d7MKa0Ewv8SE5b8vhiYoZKVKGZ6RelamlLJClVGL9+Pv6CwqEStSylKv4DyJ
QiIQqCxZqbNJP0vdzO4BDfnQyvSbL1gqVSErzJe1+zif1S2zmpPMelCFyupq
tsj0zbJWwRzUmlmDnPhUkbyFTQqvOGl0KL2HpYNKqT4QCOJA8aTnbGTDxZgl
Zr61WtrRnhM1M+KNSoMwdVhpLo+EYnaV+Bfs0yJ9fmmo3CZJHbIYxRqzFodE
FhVb7PUbJKzCYhrdwQxatRKJ0c+/2WNK/Q4/hD3Ihgy7NLB6vHa3Tm6yI82R
wzAqPl8Y9fOvhWdqYfyV74ckOrvhcrHWnG11+DRYuFmTXez3xjzqZM7MilLH
0zKVBEYqjRxn3Z2dZxSLjXlgwd479hE+wO7k7XTbLpSVZJL7ZU4vLCrUTajm
cA3csoi8yTHdotZO8+MDKk88NzfuUSgoVdP9rDGvzKdW+8ryQhU+jcZXMdqU
V04CyvPyKgkrSdm3QH4ewjlIjqTDUrYNskDKO2mf4qGZ3d3czJ4u7vp+rqZ3
EVdDrqrE1zFlTD9SI+0wEssfB+UJUGQEk1rl93rp5eRJNlNmNKcGLEajBd+r
0CqE+NOKcKS8LCwz83vl3TB3vSz0oWLUhN7KWGQtY0/vVzPtqAWHapLMjj0K
u11RcoD5JkLkQR85Q/5dFwVWs4qKzJxdkcTVu6NRYSC97Ju8JVvDSfV99fx8
Vk9+KskJF08sXzKv0EDnPNIfIrsi/Ks0/SHbXsiAmv267gCagVtMNsYE040v
8bQFQnr1xL5cteGRNfMvX1LtV6lDsy/YeX6gvTaslggZVqKSKQLx5mjn2kY3
NpbXzc5fck1fXiqly6mN2OPFUYM5MisSbgibcWLJw5sactu/se2+BW0P3fvt
czipSqfU6O1ZrlyTTKlRVJ15ZZvKnqWML7t2bVF7iU0Gw8HZ13V7s6u7EGLR
DL6eyJs7pWgWdmZqqnns6X2kPppx9CCzBmWhHGYNJ3Oqvc4scLKyA8wOvtJk
tNLULKpNMpfskZXMEE624fSc1NLXwKuvgfxedYr60i/4EAuX2s3wRUdPqCOu
WVqHpbVYOhNLOCwTYNEsLGrEogYsqseiUiyKY1EJFhVjURGWhrG0AEvzsTSE
pXlY5MGsG8sh72r2S+aH1iXit5QmfzD/PWU5XBpmp75MRF+6p8/xTPE4ee8+
s1McZ1+esTGx/hsPrS3zzBysKZpb4Sw954HVZ9++JOIqm1s8Y6DWm/p9Vqgm
1D3XkN8YbZ7jtJR0lIQbw6bly5YM4gW92xYX5vds6Swd7Gr22Ge2L4zPvrg/
Fu4emhXp65jlcDd1LWJmeMuCWe317ng0bA0tGd3nnxGPWS2x0hne2XO7SY8s
h5p+hX8HL4ReyNRzQbqeC3DWAeZmqNIjk6rUfRCCZMhG14C2jB7J++TQW7v8
Zggdfy+tZ9JrQnznGK9bWp86uIfUjaUyzGRhhqRvS37FhOmWHyR7sv0JwaT9
CQH7Suzcvd+67AcrcovO3XvJZTtX5KQ+lRlc+WXZle0FOmOkpThYVeDUi5lr
7jyWWLRgx6ffueM4z+8v3L6yCVrEukfO3bb37JAl1rbsIhibboIukxCaUDjz
riinlOZiaQ6WBDHW4Sj/egPoj4tiFuUmmRt2O81ybXLs93shUKvXJfEWTuqd
m6vWYLlQQ35aO/5mJxQqVjMK00To8KEi8qYRrPQQ3/BsnDk3B+fCfSbditzh
VNIjLbofZRpw+iX3zEsQsCwRUZOu1J/eCNTy1m9CJFdJR+MSFaxa4OiDl00O
rYiRqBTYKFSbg65AxCz5pVQtFy6zB8kvlPhfO8nZlvVyoTYvYHYZVZI9AiGL
YRUpPf5L8qo7Rr2guyeg/VVjXVp3KkE+FkCXrcDSciznkum2yGFjkvn7viI/
OFR+gPk7ko+9S5ulHJqNPC+JV+3TlpW73eUna0KrOGWRURTu0ozv6PRNeuU/
RhfTIf7XN+Uj/PQQGjlMLTfSUknnx0Tp+im5g1yp2a/zzhNDDZ5eMaWl1ey0
91NE4+OMmH+N7AkwQGSjZqM7SyrSWLLeqJsb1hpyq/MqFzSElVKlRMiKZJa6
Jedxy29dVmhu27buVpwCi1l0tiPXKpeY8r2eiN9rONq4fnGHz1OZb3H6XQp7
JNvkMmnNfq+5aMGWpprN23ece6fCkgt110OefEPd9eKZ6RWLZBaWNWL5/Eyl
zceFSeYnnHJ2V2A2F5g9O8CxKtsB5h0YUt7eQyKoyPNmvhJVoElVw0E8D1Ui
KV60T1sJzhhPKzSeUWicdP3mrvwkFnBat1vYTF5JxO3j7yXOmzIu8L+I0vDq
HX/nkVTtEZhbTBAS0erKJyrYxinTBYCMq9n//cxM1Pak3xfEJ23a0Fe4abfM
hJys+g1Olt3XcmnynNoNfRU6qZjVaGSFbStmlnZXOrwNq2atVeoUQqFcqzi3
Yv4MtzFUHy5e2FykIHY/I5JmVS+6oGnRt5cWOSvOKK9f3ZqDLxi8ZUWJ3u7U
ZNlyYbVuc9mskbrcgqYiu9gYdDn8WRJbbFbIUxmyuPxucVbAafEYNfqAz5Lf
tamtckVHmYqVlHQsh/nFB+utt4RZKA9Gx4/SPTxLHMbiEBbZsViDxSosUmI5
P0jKSUOIgurDHk2SOXNPUCBABQcYKaz9P+SUcNJoC4//ZGfeHgGUMpTEy/dw
nrmyzNuWoOWi0dChGAyZ0IGJeR3jHweF0tO3jYsH1TgYxsEQDthxUIODKhxQ
4pPkic/Kqd+R1uZUK4E+YB5/mlwy3pnxxMhqxF7sYd8y6NYrnNEAedaf0qqM
ajH5GQm+QWgO1UaKmkJZ6zWm1ComtQOfgTcUlbyb2Rl5V2yJBN2RQLaeeU6q
lArIDxw++6SQuXT0MWI3D0AfTQhVqBq9ne6jwjgWlkwZWEuTjGJvTiwnpnIc
YA7xFhxfE7RPgiHs352dLZzc6pcN53dKk3jJpJ/MzJv6kxn6yjm1s0PjG6CZ
fqbPi+O8UpzOCj+K/ie3mTpqnvSnOtQK8075JResXNJPmtlE82UH11Wtnleq
BTtbIFVIZLl1A3UVi2t9Tm5Fc8XiPIfFlc0sl2rkQkNWqtjbEFh1/5oK/MCq
B8+tUptMap0lYCU/6TXZTeaSjrJoa7FV4QgysRyvwhpyVsVTfxMwhYu3o7Gx
zBqIEbE/RaSGOvknvCrkQndnakiHhVos92RqyIOhN7y4WyQyaA8y5CJDpoYM
oDiDUJtRmZZvmtZO+eQXlEnb518GmqR/VfoWkLSa/cLrpw1RmQ2yUuxJb4by
E89BgVghSc0T6bNLgiXVDkaCfzr6hsFAHmazWGdWiQX3OEJ+j/4zv1IjZcVq
k5b9sLTKGbIrxOZ80El6vQE6If8vBoNqwf8UzCxRVItezVil9el1Yj12wKzy
7d1IpULJKauNyiSzab+f49sKl8Q5u91u8eT2lMdJ87rGmxKYReJ5kw19fmE4
cogobPKysB6S5si+vAzG9onEOSlJXTNtPvjCW9B7TFobCqZv1JdO+UGCYOqT
tTj7lKZgzpbdm0M9jYVGGQvdXZFf01HYvaEpmwlf0n3m9fNzK9Y9snb+FYMz
/erUcXO0KRqpLzDqc2sjFWcyz8z5/n03nMMpdFmGHJ8nxyhW6VRVKy5vcYTi
K25YOHj/xtq82WuuvDt29vXzfJ6quYUlnSVWL/mHVe+mDrd/rnufuWSSe486
9rITncB+iu6SE52wUfjPCSc6+3Pc26K3xZdknKR6krvri5wUS+887T7Pya74
PCfPlT91olMsoE4ZPInb9fU61f4TnbqEd9u+yGlkvGubcFqV9ubJTif5HPcI
cfrctPvsRJd141dxBvVJ3cXG2Lh71lR02p12p91J3Spwu0wvfQX3wf9dzvyc
+TnLgf/MWRdaj9letb/reMS53nmBc9QldL102p12p91pd9qddqfdaXfanXan
3Wl32p12p91pd9qddqfdaXfanXZfxvH/QSeT/h87sxDLcxsSofP4dyDiEKJj
e9F61IAZPISdyIzvwFtwDtLifnwNno/OwGuwBtWjRXgvvh4JsBX14fPYM/DT
WM2OsJ+w7+MX2L+z77Efo2W4g+1BG/BqfBUKoAr2KPshamU/YtexH+AfITt+
HgnQNXBXAfkfQRE6Gh8bg29MvsEvIP+R6H8xL4i/qw50wyDyH5wqEKobXL1q
ybpV+bVrVi/jzyK4ixCd6kcy1XsUHR2bEpD+X1MFqgnBPwf+Bpm+tFyItguq
0JyTiVCOtk8W9q+nKI9+vcI8hNhTEVEK8tnwObIKdXwZEdSCXkCEW8A/Tdgf
o5qTyj+Q4quK4CAyijkUOi2n5csK+xGa9WVF0IouYvtQ06kIxG2dImLUcirC
XIks/38W9kVkOxUhusoI/hSd/VWF/TXoPC3gP6mILpm410mlHerjy8ika5lX
pwpbiJpPRZjnkem/JZDPTacq7E+QUfgP5J0u7GPIzf4UGU/LaTktp+W0nJZT
FUYD8xCREnQv40Vb/iuyHlWelv89gfVxN7gZ/6ErRzehXtSDfGgAUuuEkFp+
p+GLP2StLrw7uSux88BiddUnyEIX9wf/diG/o/Jc9m3rjr82ul36nvg5iCvl
9xDg8/8B1A+AvwplbmRzdHJlYW0KZW5kb2JqCjIgMCBvYmoKPDwvUHJvZHVj
ZXIoTml0cm8gUERGIFByaW1vUERGKQovQ3JlYXRpb25EYXRlKEQ6MjAxNDA2
MDkyMTUzMTItMDMnMDAnKQovTW9kRGF0ZShEOjIwMTQwNjA5MjE1MzEyLTAz
JzAwJykKL1RpdGxlKE1pY3Jvc29mdCBXb3JkIC0gQy5WLmRvY3gpCi9DcmVh
dG9yKFByaW1vUERGIGh0dHA6Ly93d3cucHJpbW9wZGYuY29tKQovQXV0aG9y
KHVzZXIpPj5lbmRvYmoKeHJlZgowIDQyCjAwMDAwMDAwMDAgNjU1MzUgZiAK
MDAwMDAyMzA0NiAwMDAwMCBuIAowMDAwMDYzNjEzIDAwMDAwIG4gCjAwMDAw
MjI5NTAgMDAwMDAgbiAKMDAwMDAyMjA4OCAwMDAwMCBuIAowMDAwMDAwMDE1
IDAwMDAwIG4gCjAwMDAwMDQxMTQgMDAwMDAgbiAKMDAwMDAyMzA5NCAwMDAw
MCBuIAowMDAwMDI2MTQyIDAwMDAwIG4gCjAwMDAwMjgzMzYgMDAwMDAgbiAK
MDAwMDAyNzYwNiAwMDAwMCBuIAowMDAwMDQ4NTQ5IDAwMDAwIG4gCjAwMDAw
MjMxOTcgMDAwMDAgbiAKMDAwMDAyMzEzNSAwMDAwMCBuIAowMDAwMDIzMTY1
IDAwMDAwIG4gCjAwMDAwMjUxNTAgMDAwMDAgbiAKMDAwMDAyMjI3OCAwMDAw
MCBuIAowMDAwMDA0MTM0IDAwMDAwIG4gCjAwMDAwMDkzNDEgMDAwMDAgbiAK
MDAwMDAyNTE5MSAwMDAwMCBuIAowMDAwMDI1MjIxIDAwMDAwIG4gCjAwMDAw
MjI0NDYgMDAwMDAgbiAKMDAwMDAwOTM2MiAwMDAwMCBuIAowMDAwMDE0NDgw
IDAwMDAwIG4gCjAwMDAwMjUyNjIgMDAwMDAgbiAKMDAwMDAyNTI5MiAwMDAw
MCBuIAowMDAwMDIyNjE0IDAwMDAwIG4gCjAwMDAwMTQ1MDEgMDAwMDAgbiAK
MDAwMDAyMDA2MiAwMDAwMCBuIAowMDAwMDI1MzMzIDAwMDAwIG4gCjAwMDAw
MjUzNjMgMDAwMDAgbiAKMDAwMDAyMjc4MiAwMDAwMCBuIAowMDAwMDIwMDgz
IDAwMDAwIG4gCjAwMDAwMjIwNjcgMDAwMDAgbiAKMDAwMDAyNTQwNCAwMDAw
MCBuIAowMDAwMDI1NDM0IDAwMDAwIG4gCjAwMDAwMjg1MzggMDAwMDAgbiAK
MDAwMDA0ODc1NSAwMDAwMCBuIAowMDAwMDI1NDc1IDAwMDAwIG4gCjAwMDAw
MjY2MDIgMDAwMDAgbiAKMDAwMDAyNzA1NSAwMDAwMCBuIAowMDAwMDI3OTg5
IDAwMDAwIG4gCnRyYWlsZXIKPDwgL1NpemUgNDIgL1Jvb3QgMSAwIFIgL0lu
Zm8gMiAwIFIKL0lEIFs8NzA2QjQ3RDc3MkJBOTRENDRENTY4NUI2MkFCRjY3
NjM+PDcwNkI0N0Q3NzJCQTk0RDQ0RDU2ODVCNjJBQkY2NzYzPl0KPj4Kc3Rh
cnR4cmVmCjYzODI1CiUlRU9GCg==

---1615118150-247632436-1402341479=:70931--


From nobody Tue Jun 10 12:36:56 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5ED1A02A2; Tue, 10 Jun 2014 12:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 kv9WTYYMDCFN; Tue, 10 Jun 2014 12:36:36 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891891A02AF; Tue, 10 Jun 2014 12:36:22 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id nu7so2015826obb.30 for <multiple recipients>; Tue, 10 Jun 2014 12:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=yv4Cd5gPDG181TEi80DAqh7Gt7CBHJ0MbPzDPX7g26U=; b=dS21FSzpVCbiD574dGY0aa4GZap+kGfHjKZ2k0Yl40Nbw7t6Trgv6iV301P1N90NtP tqnClvZ+vqJAnvAj/Vrov0VodZYbAI3SWFZkDZriNnoIqRi63zX741uXOHWwcITPK3mm /mKROcVwjdP2WoShEFVpcE26TRVfkW6ygDF1Cbugxrjl64gvkH9xI8y1+8iLA54WdBqU swXRwMd2gQP+IWEWXKNbJ7TTFQqj7ffF/7MxDZyTgdh1QPQju6aaM07dLBWnit4oVkQy +9/aJk0X2RHoq/Gl8j7P+4ayWQndl+GVaJ8YszLswELhuNEnsZyAH+keSQRbJP5PauBS 0Fzw==
X-Received: by 10.60.133.203 with SMTP id pe11mr24154168oeb.24.1402428981944;  Tue, 10 Jun 2014 12:36:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Tue, 10 Jun 2014 12:36:01 -0700 (PDT)
In-Reply-To: <20140610180244.23213.49514.idtracker@ietfa.amsl.com>
References: <20140610180244.23213.49514.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 10 Jun 2014 15:36:01 -0400
Message-ID: <CAF4+nEH3PoD+gCSrwVY603UxKhN0RJr9fqrBLd56pxvJtwKWsw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-netext-wifi-epc-eap-attributes-08.txt> (EAP Attributes for WiFi - EPC Integration) to Informational RFC
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2z1xLDpBM3CoH6YxiS2peCYU6es
Cc: netext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 19:36:37 -0000

Hi,

A few comments:

This reads to me like a protocol specification and it was produced by
an IETF WG so I would expect it to be Standards Track rather than
Informational.

Wi-Fi is hyphenated. Please globally replaced "WiFi" with "Wi-Fi".

There seems to be an empty bullet point near the top of page 6.

"shall" -> MUST

Section 5: I think the usual IETF style would be to specify Length
after each diagram but, admittedly, that's pretty redundant in this
case...

References:
   It seems to me that the references to the 3GPP document or
documents that specify these protocol blobs being added to EAP AKA and
EAP SIM, and probably most of the references to EAP, should be
Normative References.
   I believe there should be a reference to IEEE Std 802.11-2012.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Jun 10, 2014 at 2:02 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Network-Based Mobility
> Extensions WG (netext) to consider the following document:
> - 'EAP Attributes for WiFi - EPC Integration'
>   <draft-ietf-netext-wifi-epc-eap-attributes-08.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-06-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    With WiFi emerging as a trusted access network for service providers,
>    it has become important to provide functions commonly available in 3G
>    and 4G networks in WiFi access networks as well.  Such functions
>    include Access Point Name (APN) Selection, multiple Packet Data
>    Network (PDN) connections and seamless mobility between WiFi and
>    3G/4G networks.
>
>    The EAP/AKA (and EAP/AKA') protocol is required for mobile devices to
>    access the mobile Evolved Packet Core (EPC) via trusted WiFi
>    networks.  This document defines a few new EAP attributes to enable
>    the above-mentioned functions in trusted WiFi access networks.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-netext-wifi-epc-eap-attributes/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-netext-wifi-epc-eap-attributes/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From nobody Tue Jun 10 13:00:02 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F5D1A0332; Tue, 10 Jun 2014 12:59:40 -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, SPF_PASS=-0.001] autolearn=ham
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 oI-LS20CL9bU; Tue, 10 Jun 2014 12:59:39 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AD3A1A02D0; Tue, 10 Jun 2014 12:59:38 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so3141283wgh.11 for <multiple recipients>; Tue, 10 Jun 2014 12:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=7CReMo8ryZyMUI0fhbyfXjBIF3PAEYIRz3f30gGCuJI=; b=Czve1MmkGyAUgKzqxu51it/hbnVepVWHcWCvAtZnU0CxZr19KF+rb/bNZHpF3EVGNx zt9nDK5rsNle7pYEvW3v/W9e1/30E+YqyKAPH7sZ93XwOJB6V8cO+JbfZlqDIZhlIPSv sO8VXjptn+6wvc/59aQvfzsy4Fr1cX58QJzzY646E0eTWYvegchamz7oDwJaVrztoIK9 1YRwcdNkpBZKSrOqeStPchm9OVQT747euPeFsyd45V4YzIV91PVr/dW3E80OS3t0Bebq 0Xv1gE/vsY4qSo5MF+/qVnZxWqepIkbQ42zk0U95onNtN2gnMwqoZ5DoqkvwbLgDmCd+ 42tQ==
X-Received: by 10.194.175.106 with SMTP id bz10mr7342333wjc.96.1402430377180;  Tue, 10 Jun 2014 12:59:37 -0700 (PDT)
Received: from [192.168.1.101] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id ey16sm1915527wid.14.2014.06.10.12.59.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 12:59:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_745AF1FA-2345-468C-B408-26F610CF7747"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [TLS] Last Call: <draft-ietf-tls-encrypt-then-mac-02.txt> (Encrypt-then-MAC for TLS and DTLS) to Proposed Standard
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CADi0yUN+A7QGZLeSDDXMLhK6mr4O09rGr0ZJy6AafPVSQJX1tA@mail.gmail.com>
Date: Tue, 10 Jun 2014 22:59:32 +0300
Message-Id: <7E22B933-C3EE-4F58-873D-88FEE7C9778F@gmail.com>
References: <20140606145220.8187.67355.idtracker@ietfa.amsl.com> <36137A9A-3503-4AF8-80D0-1FB53A7949EA@gmail.com> <CADi0yUN+A7QGZLeSDDXMLhK6mr4O09rGr0ZJy6AafPVSQJX1tA@mail.gmail.com>
To: Hugo Krawczyk <hugo@ee.technion.ac.il>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HMkKylOP04R_qf_lH6w3bP7dBoA
Cc: "ietf\\@ietf.org" <ietf@ietf.org>, TLS Mailing List <tls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 19:59:40 -0000

--Apple-Mail=_745AF1FA-2345-468C-B408-26F610CF7747
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 10, 2014, at 6:01 PM, Hugo Krawczyk <hugo@ee.technion.ac.il> =
wrote:

> The technical results in my 2001 paper are correct but the conclusion =
regarding SSL/TLS is wrong. I assumed that TLS was using fresh IVs and =
that the MAC was computed on the encoded plaintext, i.e. =
Encode-Mac-Encrypt while TLS is doing Mac-Encode-Encrypt which is =
exactly what my theoretical example shows is insecure. The later padding =
attacks showed that the theoretical example of insecurity had a very =
practical instantiation in TLS.  While the paper shows correctly that =
MAC-then-Encrypt can be secure with both CBC and stream ciphers, it also =
shows that it requires a LOT of care about encoding - it turned out that =
TLS/SSL was not doing that. So if you want to keep Mac-then-Encrypt then =
you must change the encoding as well as how you apply the MAC. Changing =
to Encrypt-then-MAC is a much safer solution.
>=20
> Hugo

Thanks

Yoav=

--Apple-Mail=_745AF1FA-2345-468C-B408-26F610CF7747
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div style=3D""><div>On Jun 10, 2014, at 6:01 =
PM, Hugo Krawczyk &lt;<a =
href=3D"mailto:hugo@ee.technion.ac.il">hugo@ee.technion.ac.il</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_default" =
style=3D"font-family:verdana,sans-serif;font-size:small">The technical =
results in my 2001 paper are correct but the conclusion regarding =
SSL/TLS is wrong. I assumed that TLS was using fresh IVs and that the =
MAC was computed on the encoded plaintext, i.e. Encode-Mac-Encrypt while =
TLS is doing Mac-Encode-Encrypt which is exactly what my theoretical =
example shows is insecure. The later padding attacks showed that the =
theoretical example of insecurity had a very practical instantiation in =
TLS.&nbsp; While the paper shows correctly that MAC-then-Encrypt can be =
secure with both CBC and stream ciphers, it also shows that it requires =
a LOT of care about encoding - it turned out that TLS/SSL was not doing =
that. So if you want to keep Mac-then-Encrypt then you must change the =
encoding as well as how you apply the MAC. Changing to Encrypt-then-MAC =
is a much safer solution.<br>

<br></div><div class=3D"gmail_default" =
style=3D"font-family:verdana,sans-serif;font-size:small">Hugo<br></div></d=
iv></blockquote></div><br><div>Thanks</div><div><br></div><div>Yoav</div><=
/body></html>=

--Apple-Mail=_745AF1FA-2345-468C-B408-26F610CF7747--


From nobody Wed Jun 11 08:08:37 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4B31A02C7; Tue, 10 Jun 2014 14:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.522
X-Spam-Level: *
X-Spam-Status: No, score=1.522 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 zw3BLi_mTpUE; Tue, 10 Jun 2014 14:21:22 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C39BF1A02C6; Tue, 10 Jun 2014 14:21:21 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id db12so6053079veb.7 for <multiple recipients>; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MIncnq8sQIs7wApfWhyJ1pDH3g44HBtTe1VPntgmmIY=; b=RmQ163Kb1LdwnqbGkLCTHOT5nEJK5pSKnyvSe7gUlIHdaUsfIzYbgNvlAk9qJTuMrm kvMPZJS5K8fot0mmIQTPcLrPuMfUiCc+txP21GjjiqjgB4xy7el0jFXsDkLsB6i25m49 EHelGRsh9+YUfGKdUn1Cg/OtuMvFGgs7uAXLiLI1UQ4hcq9Nv0s9UL9LgU2GZgs9Lz2r 3Wb8hbhync1NgyIC5xgFmmLYFZQy7GN/azrII2s1buskHWEsnavoL5cTV6B2YLSy1M/y UVbXyOBIVEAZolR95qeskC4QFtPiR1uVHHYUp3CfrBbKIlt71foPRIB0r7EcjXgT4mRT DgmA==
MIME-Version: 1.0
X-Received: by 10.221.20.199 with SMTP id qp7mr35108377vcb.24.1402435280720; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
In-Reply-To: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
References: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
Date: Wed, 11 Jun 2014 00:21:20 +0300
Message-ID: <CAP+sJUcFC_-mJfTBaR=SZ28LbyzYmEc_WK3hSDsBhsiXqws10g@mail.gmail.com>
Subject: Re: LLN Plugfest at IETF 90
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11339e2eba82fc04fb81e825
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MFG48FfwnaGSUzi-LaAQ7_2SAm4
X-Mailman-Approved-At: Wed, 11 Jun 2014 08:08:34 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, 6tisch-security@ietf.org, lwip@ietf.org, roll <roll@ietf.org>, ace@ietf.org, dtls-iot@ietf.org, Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>, coman@ietf.org, core@ietf.org, 6lo@ietf.org, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 21:21:25 -0000

--001a11339e2eba82fc04fb81e825
Content-Type: text/plain; charset=UTF-8

Dear all,

This is a kindly reminder :-) .

We call for participants. The deadline to receive topics to present or
demonstrate in the event is 06/20/2014 :-). Interested audience is also
welcome and we encourage audience to participate in the feedback session.

More information:
https://bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest

We hope to see you there!

Xavier and Ines.


2014-06-02 1:02 GMT+03:00 Ines Robles <mariainesrobles@googlemail.com>:

> Dear all,
>
> We would like to announce the plugfest event at the 90th IETF Meeting in
> Toronto.
>
> We call for participants. The deadline to receive topics to present or
> demonstrate in the event is 06/13/2014. Interested audience is also welcome
> and we encourage audience to participate in the feedback session.
>
> Please find next the plugfest information.
>
> We hope to see you there!
>
> Xavier and Ines.
>
> -----------------------
> Low Power and Lossy Networks plugfest at IETF90
>
> The IETF 6TiSCH <https://datatracker.ietf.org/wg/6tisch/charter/>, IETF
> 6lo <https://datatracker.ietf.org/wg/6lo/charter/> and IETF ROLL
> <https://datatracker.ietf.org/wg/roll/charter/> working groups are
> hosting an informal "plugfest" event at the IETF90 meeting, in Toronto, CA,
> during the week of July 20-25 2014.
> Goals
>
> The goal of this event is to bring together people interested in hands-on
> experience around the technology developed by the 6TiSCH, 6lo and ROLL
> working groups, with a particular focus on the TSCH mode of IEEE802.15.4e,
> 6lowpan, RPL and new WG specifications.
> When and where ?
>
>    - *Date*: Sunday July 20 2014, 0900-1300 EDT.
>    - *Location*: Meeting Room TBD, Fairmont Royal York Hotel 100 Front
>    Street W, Toronto, CA.
>
> *Early access: TBD if the plugfest room will be open starting 8am EDT on
> Sunday 20 2014 to allow people to set up.*
> Topology proposed - TBD
>
>    - Star topology
>    - IPv6
>
> Complementary angles
>
> This event will feature the following complementary angles:
>
>    - Interoperation
>    - Demonstration
>    - Tools
>
> Focus 1: Interoperation
>
> Download the interoperation guidelines:
>
>    - - TBD for Toronto - interoperation guidelines, version 1 (London)
>    <https://bitbucket.org/6tisch/meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_guidelines_v01.pdf>
>
> The goal is to achieve interoperation between different hardware and
> software implementations on the different aspects addressed by 6lo, 6TiSCH
> and ROLL WGs. This include 6TiSCH minimal draft implementation,
> demonstrating TSCH synchronization and OF0 for RPL on a minimal network.
> 6lowpan to demostrate cross link layer inter-operability by means of
> bridges or backbones routers. Storing and non-storing RPL implementation
> including its coexistance in different sub-networks.
>
> The focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH
> drafts implementations, including but not limited to: e.g. - 6TiSCH minimal
> draft: http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00. - TBD
>
> Participants are encouraged to bring devices which implement parts or all
> of the listed drafts.
>
> Levels of interoperation are proposed:
>
>    - *Level 1*, star topology. A single BBR devices acts as the time
>    source neighbor for all other nodes. Nodes need to demonstrate frame-based
>    and acknowledgement-based synchronization. The static TSCH schedule, as
>    well as all slot timings are taken from draft-ietf-6tisch-minimal-00.
>    - *Level 2*, multi-hop topology. This level builds upon level 1. The
>    goal of this level is full compliance to draft-ietf-6tisch-minimal-00,
>    including multi-hop routing (RPL).
>    - *Level 3*, on-the-fly scheduling. [optional] Preliminary
>    implementations of
>    http://tools.ietf.org/html/draft-dujovne-6tisch-on-the-fly can be
>    shown.
>    - *Level 4*, drafts from ROLL, such as:
>    draft-ietf-roll-mpl-parameter-configuration,
>    draft-ko-roll-mix-network-pathology, Opportunistic routing, selective DIS,
>    and others that participants want to show
>    - *Level 5*, drafts from 6lo, such as: draft-ietf-6lo-btle,
>    draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz, and others that participants
>    want to show.
>    - *Level 6* Other drafts, such as
>    draft-thubert-6man-flow-label-for-rpl, etc.
>
> Focus 2: Demonstration
>
> Participants are encouraged to bring devices and technology based on
> 6TiSCH, 6lo and ROLL which they believe can be of interest for the other
> participants. These devices may or may not participate in the
> interoperation event. Demonstration of more complete systems are
> encouraged, for example systems which show the interconnection of a 6TiSCH
> based mesh to traditional networks.
> Focus 3: Tools
>
> Participants are encouraged to bring and present different tools developed
> around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not
> limited to:
>
>    - acquisition devices (i.e. "sniffers")
>    - packet analysis tools (e.g. Wireshark)
>    - simulation/emulation platforms
>
> Important Dates
>
> The preparation of this event will be held during a portion of the
> bi-weekly 6TiSCH call (*To Be Decided how and when!!!*). In particular:
>
>    - *06/02/2014* Announcement of the plugfest event to the WG/ML related
>    with constrained devices, such as: 6tisch, 6lo, roll, core, lwig, dtls-iot,
>    coman, ace, etc.
>    - *06/06/2014* Adoption of the plugfest call by the WGs, and call for
>    participants at each group.
>    - *06/02/2014-06/13/2014* Participants have contacted the plugfest
>    chairs (Xavier or Ines) with a tentative description of what they wish to
>    participate in.
>    - *06/20/2014* Synchronization point 1. Participants can share the
>    state of advancement of the implementation and raise blocking points.
>    - *07/11/2014* Synchronization point 2. Participants can share the
>    state of advancement of the implementation and raise blocking points.
>    - *07/20/2014*. Plugfest at IETF90.
>
> Tentative Agenda from 9:00 to 13:00
>
>    - *[09.00]* Welcome and Initial Instructions
>    - *[09.05]* Participants Pitch (5 min per Participant)
>    - *[09.45]* Participants Pitch Tools (5 min per Participant)
>    - *[10.15]* Interoperation (Islands)
>    - *[11.50]* Feedback and open discussion.
>    - *[12.40]* Acknowledgements and Plugfest End
>
> For More Information
>
>    - *Contact*: Xavi Vilajosana xvilajosana@eecs.berkeley.edu - Ines
>    Robles mariainesrobles@gmail.com
>
> Note Well
>
> This event is organized as part of the IETF90 standardization meeting. You
> need to register to the IETF90 conference to be able to participate. Daily
> passes are available. The IETF Note Well applies to this plugfest, see
> http://www.ietf.org/about/note-well.html.
> About
>
> The IETF 6TiSCH working group standardizes mechanisms focusing on enabling
> IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the
> charter at http://datatracker.ietf.org/wg/6tisch/charter/, which also
> contains links to the mailing list and the Internet-Drafts published by the
> group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is
> open, and is subject to the IETF Note Well.
>
> The IETF 6lo working group focuses on the work that facilitates IPv6
> connectivity over constrained node networks with the characteristics of:
> limited power, memory and processing resources;. You can access the charter
> at https://datatracker.ietf.org/wg/6lo/charter/, which also contains
> links to the mailing list and the I-D published by the group.
>
> The IETF ROLL working group is focused on routing issues for LLN (Low
> Power and Lossy Networks), in IPv6 routing architectural framework for the
> industrial, connected home, building and urban sensor networks application
> scenarios. You can access the charter at
> https://datatracker.ietf.org/wg/roll/charter/, which also contains links
> to the mailing list and the I-D published by the group.
>

--001a11339e2eba82fc04fb81e825
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div>This is a kindly reminder :-)=
 .</div><div><br></div><div><span style=3D"color:rgb(0,0,0);font-family:ari=
al,helvetica,sans-serif">We call for participants. The deadline to receive =
topics to present or demonstrate in the event is 06/20/2014 :-). Interested=
 audience is also welcome and we encourage audience to participate in the f=
eedback session.</span></div>

<div><span style=3D"color:rgb(0,0,0);font-family:arial,helvetica,sans-serif=
"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-family:arial,h=
elvetica,sans-serif">More information:=C2=A0</span><font color=3D"#000000" =
face=3D"arial, helvetica, sans-serif"><a href=3D"https://bitbucket.org/6tis=
ch/meetings/wiki/140720a_ietf90_toronto_plugfest" target=3D"_blank">https:/=
/bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest</a></fo=
nt></div>

<div><br></div><div><span style=3D"color:rgb(0,0,0);font-family:arial,helve=
tica,sans-serif">We hope to see you there!</span><br></div><div><span style=
=3D"color:rgb(0,0,0);font-family:arial,helvetica,sans-serif"><br></span></d=
iv>

<div><font color=3D"#000000" face=3D"arial, helvetica, sans-serif">Xavier a=
nd Ines.</font></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">2014-06-02 1:02 GMT+03:00 Ines  Robles <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesrobl=
es@googlemail.com</a>&gt;</span>:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div><div><span style=3D"font-family:aria=
l,helvetica,sans-serif;color:rgb(0,0,0)">Dear all,</span><br>

</div><font face=3D"arial, helvetica, sans-serif"><br style=3D"color:rgb(0,=
0,0)"><span style=3D"color:rgb(0,0,0)">We would like to announce the plugfe=
st event at the 90th IETF Meeting in Toronto.</span></font><div>

<span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif=
"><br></font></span></div></div><div><span style=3D"color:rgb(0,0,0)"><font=
 face=3D"arial, helvetica, sans-serif">We call for participants. The deadli=
ne to receive topics to present or demonstrate in the event is 06/13/2014. =
Interested audience is also welcome and we encourage audience to participat=
e in the feedback session.</font></span></div>



<div><div><span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, =
sans-serif"><br></font></span></div><div><span style=3D"color:rgb(0,0,0)"><=
font face=3D"arial, helvetica, sans-serif">Please find next the plugfest in=
formation.=C2=A0</font></span><div>



<font face=3D"arial, helvetica, sans-serif"><br></font></div><div><span sty=
le=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif">We hope=
 to see you there!</font></span><div><font color=3D"#000000" face=3D"arial,=
 helvetica, sans-serif"><br>



</font></div><div><div style=3D"color:rgb(0,0,0)"><font face=3D"arial, helv=
etica, sans-serif">Xavier and Ines.</font></div></div></div></div><div styl=
e=3D"font-family:&#39;Times New Roman&#39;;font-size:13px;color:rgb(0,0,0)"=
>


<font size=3D"3"><br>
</font></div><div style=3D"font-family:&#39;Times New Roman&#39;;font-size:=
13px;color:rgb(0,0,0)"><font size=3D"3">-----------------------</font></div=
><div><h1 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-si=
ze:24px;margin:20px 0px 10px;padding:0px;font-weight:normal;line-height:1.2=
5">



Low Power and Lossy Networks plugfest at IETF90</h1><p style=3D"color:rgb(5=
1,51,51);font-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;pa=
dding:0px;word-wrap:break-word;line-height:20px">The=C2=A0<a href=3D"https:=
//datatracker.ietf.org/wg/6tisch/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6TiSCH</a>,=C2=A0<a href=3D"htt=
ps://datatracker.ietf.org/wg/6lo/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6lo</a>=C2=A0and=C2=A0<a href=
=3D"https://datatracker.ietf.org/wg/roll/charter/" style=3D"color:rgb(59,11=
5,175);text-decoration:none" target=3D"_blank">IETF ROLL</a>=C2=A0working g=
roups are hosting an informal &quot;plugfest&quot; event at the IETF90 meet=
ing, in Toronto, CA, during the week of July 20-25 2014.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Goals=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">



The goal of this event is to bring together people interested in hands-on e=
xperience around the technology developed by the 6TiSCH, 6lo and ROLL worki=
ng groups, with a particular focus on the TSCH mode of IEEE802.15.4e, 6lowp=
an, RPL and new WG specifications.</p>



<h3 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:18p=
x;margin:20px 0px 0px;padding:0px;line-height:1.3888888888888888;font-weigh=
t:normal">When and where ?</h3><ul style=3D"color:rgb(51,51,51);font-family=
:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>Date</strong>: Sunday July 20 20=
14, 0900-1300 EDT.</li><li style=3D"word-wrap:break-word"><strong>Location<=
/strong>: Meeting Room TBD, Fairmont Royal York Hotel 100 Front Street W, T=
oronto, CA.</li>



</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
"><strong>Early access: TBD if the plugfest room will be open starting 8am =
EDT on Sunday 20 2014 to allow people to set up.</strong></p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Topol=
ogy proposed - TBD</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,s=
ans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word">Star topology</li><li style=3D"word-wrap=
:break-word">IPv6</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Ari=
al,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:no=
rmal;line-height:1.5">



Complementary angles</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,=
sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-w=
ord;line-height:20px">This event will feature the following complementary a=
ngles:</p>



<ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14p=
x;margin:10px 0px 0px;line-height:20px"><li style=3D"word-wrap:break-word">=
Interoperation</li><li style=3D"word-wrap:break-word">Demonstration</li><li=
 style=3D"word-wrap:break-word">



Tools</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-seri=
f;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-he=
ight:1.5">Focus 1: Interoperation</h2>
<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Dow=
nload the interoperation guidelines:</p><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px">



<li style=3D"word-wrap:break-word"><a href=3D"https://bitbucket.org/6tisch/=
meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_gui=
delines_v01.pdf" style=3D"color:rgb(59,115,175);text-decoration:none" targe=
t=3D"_blank"> - TBD for Toronto - interoperation guidelines, version 1 (Lon=
don)</a></li>



</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">The goal is to achieve interoperation between different hardware and soft=
ware implementations on the different aspects addressed by 6lo, 6TiSCH and =
ROLL WGs. This include 6TiSCH minimal draft implementation, demonstrating T=
SCH synchronization and OF0 for RPL on a minimal network. 6lowpan to demost=
rate cross link layer inter-operability by means of bridges or backbones ro=
uters. Storing and non-storing RPL implementation including its coexistance=
 in different sub-networks.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH draft=
s implementations, including but not limited to: e.g. - 6TiSCH minimal draf=
t:=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00"=
 rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00</a>. =
- TBD</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Par=
ticipants are encouraged to bring devices which implement parts or all of t=
he listed drafts.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Lev=
els of interoperation are proposed:</p><ul style=3D"color:rgb(51,51,51);fon=
t-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20=
px">



<li style=3D"word-wrap:break-word"><strong>Level 1</strong>, star topology.=
 A single BBR devices acts as the time source neighbor for all other nodes.=
 Nodes need to demonstrate frame-based and acknowledgement-based synchroniz=
ation. The static TSCH schedule, as well as all slot timings are taken from=
 draft-ietf-6tisch-minimal-00.</li>



<li style=3D"word-wrap:break-word"><strong>Level 2</strong>, multi-hop topo=
logy. This level builds upon level 1. The goal of this level is full compli=
ance to draft-ietf-6tisch-minimal-00, including multi-hop routing (RPL).</l=
i>



<li style=3D"word-wrap:break-word"><strong>Level 3</strong>, on-the-fly sch=
eduling. [optional] Preliminary implementations of=C2=A0<a href=3D"http://t=
ools.ietf.org/html/draft-dujovne-6tisch-on-the-fly" rel=3D"nofollow" style=
=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http://to=
ols.ietf.org/html/draft-dujovne-6tisch-on-the-fly</a>=C2=A0can be shown.</l=
i>



<li style=3D"word-wrap:break-word"><strong>Level 4</strong>, drafts from RO=
LL, such as: draft-ietf-roll-mpl-parameter-configuration, draft-ko-roll-mix=
-network-pathology, Opportunistic routing, selective DIS, and others that p=
articipants want to show</li>



<li style=3D"word-wrap:break-word"><strong>Level 5</strong>, drafts from 6l=
o, such as: draft-ietf-6lo-btle, draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz,=
 and others that participants want to show.</li><li style=3D"word-wrap:brea=
k-word">



<strong>Level 6</strong>=C2=A0Other drafts, such as draft-thubert-6man-flow=
-label-for-rpl, etc.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:=
Arial,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight=
:normal;line-height:1.5">



Focus 2: Demonstration</h2><p style=3D"color:rgb(51,51,51);font-family:Aria=
l,sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break=
-word;line-height:20px">Participants are encouraged to bring devices and te=
chnology based on 6TiSCH, 6lo and ROLL which they believe can be of interes=
t for the other participants. These devices may or may not participate in t=
he interoperation event. Demonstration of more complete systems are encoura=
ged, for example systems which show the interconnection of a 6TiSCH based m=
esh to traditional networks.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Focus=
 3: Tools</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">



Participants are encouraged to bring and present different tools developed =
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not limite=
d to:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font=
-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word">acquisition devices (i.e. &quot;sniffers=
&quot;)</li><li style=3D"word-wrap:break-word">packet analysis tools (e.g. =
Wireshark)</li><li style=3D"word-wrap:break-word">simulation/emulation plat=
forms</li>



</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Important Dates</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-=
serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;l=
ine-height:20px">



The preparation of this event will be held during a portion of the bi-weekl=
y 6TiSCH call (<strong>To Be Decided how and when!!!</strong>). In particul=
ar:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-s=
ize:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>06/02/2014</strong>=C2=A0Announc=
ement of the plugfest event to the WG/ML related with constrained devices, =
such as: 6tisch, 6lo, roll, core, lwig, dtls-iot, coman, ace, etc.</li><li =
style=3D"word-wrap:break-word">



<strong>06/06/2014</strong>=C2=A0Adoption of the plugfest call by the WGs, =
and call for participants at each group.</li><li style=3D"word-wrap:break-w=
ord"><strong>06/02/2014-06/13/2014</strong>=C2=A0Participants have contacte=
d the plugfest chairs (Xavier or Ines) with a tentative description of what=
 they wish to participate in.</li>



<li style=3D"word-wrap:break-word"><strong>06/20/2014</strong>=C2=A0Synchro=
nization point 1. Participants can share the state of advancement of the im=
plementation and raise blocking points.</li><li style=3D"word-wrap:break-wo=
rd">


<strong>07/11/2014</strong>=C2=A0Synchronization point 2. Participants can =
share the state of advancement of the implementation and raise blocking poi=
nts.</li>
<li style=3D"word-wrap:break-word"><strong>07/20/2014</strong>. Plugfest at=
 IETF90.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-s=
erif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line=
-height:1.5">



Tentative Agenda from 9:00 to 13:00</h2><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px"><li style=3D"word-wrap:break-word"><em>[09.00]</em>=C2=A0Welcome and I=
nitial Instructions</li>



<li style=3D"word-wrap:break-word"><em>[09.05]</em>=C2=A0Participants Pitch=
 (5 min per Participant)</li><li style=3D"word-wrap:break-word"><em>[09.45]=
</em>=C2=A0Participants Pitch Tools (5 min per Participant)</li><li style=
=3D"word-wrap:break-word">



<em>[10.15]</em>=C2=A0Interoperation (Islands)</li><li style=3D"word-wrap:b=
reak-word"><em>[11.50]</em>=C2=A0Feedback and open discussion.</li><li styl=
e=3D"word-wrap:break-word"><em>[12.40]</em>=C2=A0Acknowledgements and Plugf=
est End</li></ul>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">For M=
ore Information</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans=
-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>Contact</strong>: Xavi Vilajosan=
a=C2=A0<a href=3D"mailto:xvilajosana@eecs.berkeley.edu" style=3D"color:rgb(=
59,115,175);text-decoration:none" target=3D"_blank">xvilajosana@eecs.berkel=
ey.edu</a>=C2=A0- Ines Robles=C2=A0<a href=3D"mailto:mariainesrobles@gmail.=
com" style=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank"=
>mariainesrobles@gmail.com</a></li>



</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Note Well</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">



This event is organized as part of the IETF90 standardization meeting. You =
need to register to the IETF90 conference to be able to participate. Daily =
passes are available. The IETF Note Well applies to this plugfest, see=C2=
=A0<a href=3D"http://www.ietf.org/about/note-well.html" rel=3D"nofollow" st=
yle=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http:/=
/www.ietf.org/about/note-well.html</a>.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">About=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">



The IETF 6TiSCH working group standardizes mechanisms focusing on enabling =
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the c=
harter at=C2=A0<a href=3D"http://datatracker.ietf.org/wg/6tisch/charter/" r=
el=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" target=
=3D"_blank">http://datatracker.ietf.org/wg/6tisch/charter/</a>, which also =
contains links to the mailing list and the Internet-Drafts published by the=
 group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is=
 open, and is subject to the IETF Note Well.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF 6lo working group focuses on the work that facilitates IPv6 connectiv=
ity over constrained node networks with the characteristics of: limited pow=
er, memory and processing resources;. You can access the charter at=C2=A0<a=
 href=3D"https://datatracker.ietf.org/wg/6lo/charter/" rel=3D"nofollow" sty=
le=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">https:/=
/datatracker.ietf.org/wg/6lo/charter/</a>, which also contains links to the=
 mailing list and the I-D published by the group.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF ROLL working group is focused on routing issues for LLN (Low Power an=
d Lossy Networks), in IPv6 routing architectural framework for the industri=
al, connected home, building and urban sensor networks application scenario=
s. You can access the charter at=C2=A0<a href=3D"https://datatracker.ietf.o=
rg/wg/roll/charter/" rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-d=
ecoration:none" target=3D"_blank">https://datatracker.ietf.org/wg/roll/char=
ter/</a>, which also contains links to the mailing list and the I-D publish=
ed by the group.</p>



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

--001a11339e2eba82fc04fb81e825--


From nobody Wed Jun 11 10:00:25 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5C5B1A01F9; Wed, 11 Jun 2014 10:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level: 
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 5JQJA-ZUn7g6; Wed, 11 Jun 2014 10:00:20 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13B3C1A01ED; Wed, 11 Jun 2014 10:00:19 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s5BH04Sx000426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jun 2014 19:00:04 +0200 (MEST)
Subject: Re: Change the mailing list protocol, not DMARC.
In-Reply-To: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 11 Jun 2014 19:00:04 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/08tLbhP6bqc9M_449vso1OpkUBs
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 17:00:23 -0000

Phillip Hallam-Baker wrote:
> Hector Santos <hsantos@isdg.net> wrote:
>> 
>> Let me ask, what if a fedex.com employee use this email domain for
>> subscribing to the IETF list?
> 
> Any subsequent problems are irrelevant unless FedEx, the owner of
> fedex.com considers them to be relevant.
> 
> That is what folk complaining don't get: you don't have the right to
> use your employers email or a public email provider's email any way
> you want. The domain name owner makes the rules.
> 
> As Craster insists: My domain, my rules.

Strange concept!

Does your jurisdiction allow your landlord to interfere with
postal/snail mail that is delivered from or to your rented appartment?

And unless your jurisdiction is hopelessly outdated, the same
rules ought to apply to interference with telecommunications.


> 
> In the medium term, lets kill the stupidity of mailing lists with a
> protocol that works. NNTP was originally designed to replace mailing
> lists. It actually works quite well at that. The only problem was the
> IT-Dictator mindset that underlies it: newsgroups have to be approved
> by the Commune!

Set up your own mail2news gateway.

/usr/lib/aliases  http://www.tldp.org/LDP/nag/node213.html
main2news script  http://www.sirlab.de/linux/descr_m2n.html


-Martin


From nobody Thu Jun 12 05:47:33 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7113D1B2A04; Thu, 12 Jun 2014 05:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.276
X-Spam-Level: 
X-Spam-Status: No, score=-1.276 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, SPF_PASS=-0.001] autolearn=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 nrl5sNzxTSs3; Thu, 12 Jun 2014 05:47:30 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C55F1B2A02; Thu, 12 Jun 2014 05:47:29 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id n3so7115115wiv.15 for <multiple recipients>; Thu, 12 Jun 2014 05:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/IKTZAy4/7/22q6xWKTe/C9reX88LKT9H6rq28a4uXs=; b=GRSjAR8QTEs6oTgKr9JapJw+X8Hma8qcXDr3ZxvpX2esrGprAZiEJhl9QhpxeqUXqJ AHjhjufrqCxVCJxpZXEWfUyLzYQ6LCVv6bBqkeFCUlc2usyURAPTvpRVB3cGb8KsNgYf D9G+igUV1xLg5bPWoCODb86zZhOe6p3hCqpE6AkqMTNY2nlxxgcSJRElefg6Vc1drSch X6AjVKYwfNpCXJ3YvIJoIPDgiuYiUyIwNfDI9TQ48tP6Ocn4UfMffc4vB0SjG817esUf Wcw9LyadxUUtboQICe6GaKNsqyZQTsEftidSEkXn/4vQprzvCk5jasUjfv8Bz/mA4y04 m9IQ==
MIME-Version: 1.0
X-Received: by 10.194.62.176 with SMTP id z16mr42136734wjr.76.1402577247984; Thu, 12 Jun 2014 05:47:27 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Thu, 12 Jun 2014 05:47:27 -0700 (PDT)
In-Reply-To: <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp>
Date: Thu, 12 Jun 2014 08:47:27 -0400
X-Google-Sender-Auth: 3AHxoAiqZetEY3mLGDYPA_OO74k
Message-ID: <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
Subject: Re: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Martin Rex <mrex@sap.com>
Content-Type: multipart/alternative; boundary=047d7ba979c2a2e2e104fba2f6c4
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_JBsWm4EIzxHLf2CLIh68d_u_TI
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 12:47:31 -0000

--047d7ba979c2a2e2e104fba2f6c4
Content-Type: text/plain; charset=UTF-8

On Wed, Jun 11, 2014 at 1:00 PM, Martin Rex <mrex@sap.com> wrote:

> Phillip Hallam-Baker wrote:
> > Hector Santos <hsantos@isdg.net> wrote:
> >>
> >> Let me ask, what if a fedex.com employee use this email domain for
> >> subscribing to the IETF list?
> >
> > Any subsequent problems are irrelevant unless FedEx, the owner of
> > fedex.com considers them to be relevant.
> >
> > That is what folk complaining don't get: you don't have the right to
> > use your employers email or a public email provider's email any way
> > you want. The domain name owner makes the rules.
> >
> > As Craster insists: My domain, my rules.
>
> Strange concept!
>
> Does your jurisdiction allow your landlord to interfere with
> postal/snail mail that is delivered from or to your rented appartment?
>

Absent specific government action to protect the tenant, the landlord can
abuse them in almost any way they choose. Which is why we have voluminous
legislative protections for tenants. There is an entire field of law
concerning that.

The reason that is necessary is that the alternative to renting is very
expensive and requires a large amount of capital. But if houses were $6
then it would be perfectly reasonable for society to tell tenants that they
are on their own because they should become freeholders.



> > In the medium term, lets kill the stupidity of mailing lists with a
> > protocol that works. NNTP was originally designed to replace mailing
> > lists. It actually works quite well at that. The only problem was the
> > IT-Dictator mindset that underlies it: newsgroups have to be approved
> > by the Commune!
>
> Set up your own mail2news gateway.
>
> /usr/lib/aliases  http://www.tldp.org/LDP/nag/node213.html
> main2news script  http://www.sirlab.de/linux/descr_m2n.html


My point is that mail is an old protocol and people who expect that it can
be kept going unaltered in its original form serving all the purposes that
it was never designed for but have emerged over time are going to be upset
no matter what.

Spam is an attack. The people who send spam are hardened criminals who have
murdered at least two people in the past five years. It is futile to expect
that the mail system can continue to operate without changes.

The major ISPs can and will and SHOULD consider the interests of the
majority of their customers as they move forward. If they don't, open email
systems based on SMTP will go the same way as USENET and die because people
don't want to put up with them any more.


The possibility that SAP might force you to subscribe to IETF lists through
a different address does not worry me in the slightest. That is not one of
the uses of email that I consider any sort of priority. I am quite happy
making you change your mail config.

But looking further ahead, it is becoming clear that maintaining mailing
list capabilities is going to become increasingly difficult in the face of
escalating anti-spam controls. Which is why I suggest that rather than the
IETF community reacting to DMARC by refusing to consider any change that
inconveniences members of its club, IETF instead designs a protocol that
addresses the actual needs.


In the SMTP/IMAP model the message is pushed to the sender outbound MTA,
pushed to the receiver outbound MTA and pulled by the client from the
outbound MTA.

The SMTP/IMAP model is thus PUSH/PUSH/PULL

The model of NNTP and Dropbox and many of the blogging comments apps is
PUSH/PULL/PULL. That is a message pattern that we can and should support in
IETF protocols. Because when someone is sending 10Gb of data, the PUSH/PUSH
model is not viable. Better to leave that data siting on the outbound
server rather than have it clog up hundreds of inbound servers and sit
unread.


US6192407 has a priority date of Oct 24, 1996, now would be a good time to
work on such a protocol.

--047d7ba979c2a2e2e104fba2f6c4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Jun 11, 2014 at 1:00 PM, Martin Rex <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mrex@sap.com" target=3D"_blank">mrex@sap.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"">Phillip Hallam-Baker wrote:<br>
&gt; Hector Santos &lt;<a href=3D"mailto:hsantos@isdg.net">hsantos@isdg.net=
</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Let me ask, what if a <a href=3D"http://fedex.com" target=3D"_blan=
k">fedex.com</a> employee use this email domain for<br>
&gt;&gt; subscribing to the IETF list?<br>
&gt;<br>
&gt; Any subsequent problems are irrelevant unless FedEx, the owner of<br>
&gt; <a href=3D"http://fedex.com" target=3D"_blank">fedex.com</a> considers=
 them to be relevant.<br>
&gt;<br>
&gt; That is what folk complaining don&#39;t get: you don&#39;t have the ri=
ght to<br>
&gt; use your employers email or a public email provider&#39;s email any wa=
y<br>
&gt; you want. The domain name owner makes the rules.<br>
&gt;<br>
&gt; As Craster insists: My domain, my rules.<br>
<br>
</div>Strange concept!<br>
<br>
Does your jurisdiction allow your landlord to interfere with<br>
postal/snail mail that is delivered from or to your rented appartment?<br><=
/blockquote><div><br></div><div>Absent specific government action to protec=
t the tenant, the landlord can abuse them in almost any way they choose. Wh=
ich is why we have voluminous legislative protections for tenants. There is=
 an entire field of law concerning that.</div>
<div><br></div><div>The reason that is necessary is that the alternative to=
 renting is very expensive and requires a large amount of capital. But if h=
ouses were $6 then it would be perfectly reasonable for society to tell ten=
ants that they are on their own because they should become freeholders.</di=
v>
<div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex"><div class=3D"">
&gt; In the medium term, lets kill the stupidity of mailing lists with a<br=
>
&gt; protocol that works. NNTP was originally designed to replace mailing<b=
r>
&gt; lists. It actually works quite well at that. The only problem was the<=
br>
&gt; IT-Dictator mindset that underlies it: newsgroups have to be approved<=
br>
&gt; by the Commune!<br>
<br>
</div>Set up your own mail2news gateway.<br>
<br>
/usr/lib/aliases =C2=A0<a href=3D"http://www.tldp.org/LDP/nag/node213.html"=
 target=3D"_blank">http://www.tldp.org/LDP/nag/node213.html</a><br>
main2news script =C2=A0<a href=3D"http://www.sirlab.de/linux/descr_m2n.html=
" target=3D"_blank">http://www.sirlab.de/linux/descr_m2n.html</a></blockquo=
te><div><br></div><div>My point is that mail is an old protocol and people =
who expect that it can be kept going unaltered in its original form serving=
 all the purposes that it was never designed for but have emerged over time=
 are going to be upset no matter what.</div>
<div><br></div><div>Spam is an attack. The people who send spam are hardene=
d criminals who have murdered at least two people in the past five years. I=
t is futile to expect that the mail system can continue to operate without =
changes.</div>
<div><br></div><div>The major ISPs can and will and SHOULD consider the int=
erests of the majority of their customers as they move forward. If they don=
&#39;t, open email systems based on SMTP will go the same way as USENET and=
 die because people don&#39;t want to put up with them any more.=C2=A0</div=
>
<div><br></div><div><br></div><div>The possibility that SAP might force you=
 to subscribe to IETF lists through a different address does not worry me i=
n the slightest. That is not one of the uses of email that I consider any s=
ort of priority. I am quite happy making you change your mail config.</div>
<div><br></div><div>But looking further ahead, it is becoming clear that ma=
intaining mailing list capabilities is going to become increasingly difficu=
lt in the face of escalating anti-spam controls. Which is why I suggest tha=
t rather than the IETF community reacting to DMARC by refusing to consider =
any change that inconveniences members of its club, IETF instead designs a =
protocol that addresses the actual needs.</div>
<div><br></div><div><br></div><div>In the SMTP/IMAP model the message is pu=
shed to the sender outbound MTA, pushed to the receiver outbound MTA and pu=
lled by the client from the outbound MTA.</div><div><br></div><div>The SMTP=
/IMAP model is thus PUSH/PUSH/PULL</div>
<div><br></div><div>The model of NNTP and Dropbox and many of the blogging =
comments apps is PUSH/PULL/PULL. That is a message pattern that we can and =
should support in IETF protocols. Because when someone is sending 10Gb of d=
ata, the PUSH/PUSH model is not viable. Better to leave that data siting on=
 the outbound server rather than have it clog up hundreds of inbound server=
s and sit unread.</div>
<div>=C2=A0</div></div><br></div><div class=3D"gmail_extra"><span style=3D"=
font-family:Arial,sans-serif;font-size:12.727272033691406px;background-colo=
r:rgb(245,245,245)">US6192407 has a priority date of=C2=A0</span><span styl=
e=3D"font-family:Arial,sans-serif;font-size:12.727272033691406px;background=
-color:rgb(245,245,245)">Oct 24, 1996, now would be a good time to work on =
such a protocol.</span><br>
</div></div>

--047d7ba979c2a2e2e104fba2f6c4--


From nobody Thu Jun 12 07:20:58 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 032791A0132 for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 07:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level: 
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 5zAASTJx5edQ for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 07:20:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 924441A00EA for <ietf@ietf.org>; Thu, 12 Jun 2014 07:20:52 -0700 (PDT)
Received: from [172.16.22.13] (217.64.246.155.mactelecom.net [217.64.246.155]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s5CEKlVv026291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 12 Jun 2014 07:20:52 -0700
Message-ID: <5399B704.5090007@dcrocker.net>
Date: Thu, 12 Jun 2014 16:19:48 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
CC: IETF <ietf@ietf.org>
Subject: Re: Change the mailing list protocol, not DMARC.
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com>	<20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
In-Reply-To: <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 12 Jun 2014 07:20:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V7v8cZrci0iDanm5WytWJTK3lPM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 14:20:55 -0000

> My point is that mail is an old protocol and people who expect that it
> can be kept going unaltered in its original form serving all the
> purposes that it was never designed for but have emerged over time are
> going to be upset no matter what.


This is a variant of the usual refrain, over the last 20 years, about
dealing with some limitation or other to email.  It goes along the lines
of "We need to throw out SMTP and start over."

To this and the above I have my own usual refrain:

     There will come a point at which SMTP (or IMAP, or the email object
or...) do need to be replaced.  An appropriate procedure for deciding
when that point has been reached needs to be:

     1.  Get community (rough) consensus about the non-technical
characteristics for the functional change; that is, agreement about what
the community wants to do with/for email that it cannot currently do.

     2.  The email technical community has been successfully making
enhancements to the same continuously running end-to-end service for
30-40 years (depending upon how one counts); so give it a chance to find
a way to incrementally improve the existing service to support whatever
is needed.

     3.  When the technical community fails, it will be time to develop
the relevant protocol/format/whatever.

On the average, those calling for replacing SMTP (or whatever) have been
stopped at the first step.

Someday, they won't be.

But until then, meta-declarations about needing to replace Internet Mail
(or any other existing Internet service) don't have much practical purpose.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Jun 12 07:50:29 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D929B1B2A6F for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 07:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 30xGLfRloXWs for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 07:50:26 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 252B21B2A70 for <ietf@ietf.org>; Thu, 12 Jun 2014 07:50:26 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Wv6Ip-000BVS-Ig; Thu, 12 Jun 2014 10:48:31 -0400
Date: Thu, 12 Jun 2014 10:50:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Change the mailing list protocol, not DMARC.
Message-ID: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com>
In-Reply-To: <5399B704.5090007@dcrocker.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UW8bBXGxQQgGvEcQVBNk-CYjqEs
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 14:50:28 -0000

--On Thursday, June 12, 2014 16:19 +0200 Dave Crocker
<dhc@dcrocker.net> wrote:

>> My point is that mail is an old protocol and people who
>> expect that it can be kept going unaltered in its original
>> form serving all the purposes that it was never designed for
>> but have emerged over time are going to be upset no matter
>> what.
> 
> This is a variant of the usual refrain, over the last 20
> years, about dealing with some limitation or other to email.
> It goes along the lines of "We need to throw out SMTP and
> start over."
> 
> To this and the above I have my own usual refrain:
> 
>      There will come a point at which SMTP (or IMAP, or the
> email object or...) do need to be replaced.  An appropriate
> procedure for deciding when that point has been reached needs
> to be:
>...

FWIW, +1 to Dave's "usual refrain".
The other three things that occurred to me when reading the "old
protocol..." statement were:

(1) "kept going unaltered in its original form..." has rarely
been the expectation and, indeed, many changes have been
successfully introduced to deal with evolving needs.

(2) One of those changes --support for remote body parts-- was
incorporated into MIME in its very first version and contains
most of the mechanism needed to support what I understand PHB is
recommending for PUSH-PULL-PULL.  It has been implemented in
several places but has gotten very little traction in the mail
sending and receiving community.  IMO, it ought to be incumbent
on anyone proposing a different "get notification, then retrieve
mail from server" model explain why their ideas will be more
successful than that 20-odd-year-old MIME mechanism.

(3) Even though adjustments have been made to deal with changing
knowledge and needs, we have been using the old, Newtonian, view
of mechanics for circa 300 years, not merely 30 or 40.  Perhaps
the argument for dumping old things because not every issue and
bit of future knowledge was originally designed into those
laws/theories should be used to dump them too.  Perhaps they
should even have been dumped in the middle of the 19th century
before relativity and quantum theory came along.

Final Ultimate Solution to the [Alleged] Email Problem (FUSAEP)
anyone?

    john






From nobody Thu Jun 12 08:05:08 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C581A0515 for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 08:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 4RdzwYkse3DC for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 08:04:59 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E68571A0263 for <ietf@ietf.org>; Thu, 12 Jun 2014 08:04:59 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 674011B8034 for <ietf@ietf.org>; Thu, 12 Jun 2014 08:04:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 488FA190064; Thu, 12 Jun 2014 08:04:59 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Jun 2014 08:04:59 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Change the mailing list protocol, not DMARC.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5399B704.5090007@dcrocker.net>
Date: Thu, 12 Jun 2014 11:04:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <E5D2B1A5-9CD5-4543-908E-F90F0D0DE721@nominum.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com>	<20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net>
To: <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MmLb2nvZX95F-f200IgaPQh0A_Q
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 15:05:05 -0000

On Jun 12, 2014, at 10:19 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> But until then, meta-declarations about needing to replace Internet =
Mail
> (or any other existing Internet service) don't have much practical =
purpose.

On the contrary, they keep us thinking about it and trying to envision =
different ways of solving the problem.


From nobody Thu Jun 12 08:14:23 2014
Return-Path: <c-sai@bx.jp.nec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E77B11B29FB; Thu, 12 Jun 2014 05:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level: 
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 wXaVatVzyZDh; Thu, 12 Jun 2014 05:39:35 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [210.143.35.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CCB71B29F2; Thu, 12 Jun 2014 05:39:34 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.193]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5CCdW1F020786; Thu, 12 Jun 2014 21:39:32 +0900 (JST)
Received: from mailsv4.nec.co.jp (imss61.nec.co.jp [10.7.69.156]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id s5CCdWJ19112; Thu, 12 Jun 2014 21:39:32 +0900 (JST)
Received: from mail03.kamome.nec.co.jp (mail03.kamome.nec.co.jp [10.25.43.7]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5CCdWX7028811; Thu, 12 Jun 2014 21:39:32 +0900 (JST)
Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.144] [10.38.151.144]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-224829; Thu, 12 Jun 2014 21:38:50 +0900
Received: from BPXM18GP.gisp.nec.co.jp ([169.254.2.157]) by BPXC16GP.gisp.nec.co.jp ([10.38.151.144]) with mapi id 14.02.0328.011; Thu, 12 Jun 2014 21:38:50 +0900
From: Zhenlong Cui <c-sai@bx.jp.nec.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [mpls] I-D Action: draft-ietf-mpls-smp-requirements-06.txt
Thread-Topic: [mpls] I-D Action: draft-ietf-mpls-smp-requirements-06.txt
Thread-Index: AQHPhHutNkgrELnVbkObxDn6WHeuXJttaMCg
Date: Thu, 12 Jun 2014 12:38:49 +0000
Message-ID: <E703759D9A8E6446BEA7F57C9A91381A7283D6@BPXM18GP.gisp.nec.co.jp>
References: <20140610071412.6466.24044.idtracker@ietfa.amsl.com>
In-Reply-To: <20140610071412.6466.24044.idtracker@ietfa.amsl.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.38.126.83]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ga5gICltJr1qBcw-slm8_NXDQWk
X-Mailman-Approved-At: Thu, 12 Jun 2014 08:14:20 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 12:39:36 -0000

Hi authors,

  Both 1:n and n:1 are described in your draft.

  Could you explain "n:1, 1:n, m:n" where it is first used?
  1:n protection and m:n protection are defined in G.808.1 and RFC 4427, bu=
t I can't find a definition for n:1.

Best regards,
zhenlong

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of internet-drafts@ie=
tf.org
> Sent: Tuesday, June 10, 2014 4:14 PM
> To: i-d-announce@ietf.org
> Cc: mpls@ietf.org
> Subject: [mpls] I-D Action: draft-ietf-mpls-smp-requirements-06.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the Multiprotocol Label Switching Working G=
roup of the IETF.
>=20
>         Title           : Requirements for MPLS-TP Shared Mesh Protection
>         Authors         : Yaacov Weingarten
>                           Sam Aldrin
>                           Ping Pan
>                           Jeong-dong Ryoo
>                           Greg Mirsky
> 	Filename        : draft-ietf-mpls-smp-requirements-06.txt
> 	Pages           : 14
> 	Date            : 2014-06-10
>=20
> Abstract:
>    This document presents the basic network objectives for the behavior
>    of shared mesh protection (SMP) which are not based on control plane
>    support. This is an expansion of the basic requirements presented in
>    RFC 5654 "Requirements for the Transport Profile of MPLS" and RFC
>    6372 "MPLS Transport Profile (MPLS-TP) Survivability Framework".
>    This document is to be used as a basis for the definition of any
>    mechanism that would be used to implement SMP for MPLS-TP data paths,
>    in networks that delegate executive action for resiliency to the data
>    plane.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-smp-requirements/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mpls-smp-requirements-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mpls-smp-requirements-06
>=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
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From nobody Thu Jun 12 08:18:30 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D78E1B2A70 for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 08:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 udlqEU7uwPHM for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 08:18:26 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9E131B2A83 for <ietf@ietf.org>; Thu, 12 Jun 2014 08:18:26 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D10A81B8035 for <ietf@ietf.org>; Thu, 12 Jun 2014 08:18:26 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id CA06E190064; Thu, 12 Jun 2014 08:18:26 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Jun 2014 08:18:26 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Change the mailing list protocol, not DMARC.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com>
Date: Thu, 12 Jun 2014 11:18:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7BC8O2r-th8JDpZvUdVNudxknRo
Cc: dcrocker@bbiw.net, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 15:18:28 -0000

On Jun 12, 2014, at 10:50 AM, John C Klensin <john-ietf@jck.com> wrote:
> IMO, it ought to be incumbent
> on anyone proposing a different "get notification, then retrieve
> mail from server" model explain why their ideas will be more
> successful than that 20-odd-year-old MIME mechanism.

Implementing this 20-year-old MIME mechanism would be very difficult, =
would have limited potential payoff, and would be pretty obviously =
privacy-violating.   And in order for it to do any good, recipients =
would have to refuse large attachments.   So there really isn't a viable =
transition path from what we have now to this, and if we had this, it =
would make things a lot worse in some respects, and make things better =
in almost no respect.

This functionality is very similar to the behavior of modern MUAs that =
will fetch images in email messages given the URL, which is in =
ubiquitous use as a way of bugging mail recipients to see if they =
actually read the message.    I disable it in my MUA.

Point being, the fact that this technology hasn't taken off is no =
indication of a lack of demand for the technology PHB was describing.


From nobody Thu Jun 12 09:15:09 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E781A0150; Thu, 12 Jun 2014 09:14:59 -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
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 SkUY6SG_LqlO; Thu, 12 Jun 2014 09:14:52 -0700 (PDT)
Received: from p3plsmtpa12-04.prod.phx3.secureserver.net (p3plsmtpa12-04.prod.phx3.secureserver.net [68.178.252.233]) by ietfa.amsl.com (Postfix) with ESMTP id 55C6E1B2AAF; Thu, 12 Jun 2014 09:14:52 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa12-04.prod.phx3.secureserver.net with  id DUEo1o00P1huGat01UEohq; Thu, 12 Jun 2014 09:14:52 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-idr-bgp-enhanced-route-refresh.all@tools.ietf.org>
Subject: Gen-ART Telechat review of draft-ietf-idr-bgp-enhanced-route-refresh-08
Date: Thu, 12 Jun 2014 09:14:50 -0700
Message-ID: <014b01cf8659$723549e0$569fdda0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+GWTIjoOFskeNoT5q/xUHUg8bUjw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1Qahi-qwsKTAJtvjY4XjInIP6M4
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 16:15:00 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-idr-bgp-enhanced-route-refresh-08
Reviewer: Peter Yee
Review Date: June-12-2014
IETF LC End Date: June-03-2014
IESG Telechat date: June-12-2014

Summary: This draft is ready for publication as a Standards Track RFC.
[Ready.]

All of the issues of concern raised in my LC review have been addressed by
this version of the specification.



From nobody Thu Jun 12 09:16:58 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB411B2AA9 for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 09:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 xTPKH1xSdbLd for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 09:16:47 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 024221A0150 for <ietf@ietf.org>; Thu, 12 Jun 2014 09:16:46 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id x13so1502795wgg.3 for <ietf@ietf.org>; Thu, 12 Jun 2014 09:16:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6rlv1svcSva69IQWHOuJWJdbrONLWUmZefpYUvj+vUw=; b=cJvlqkTf7KLaK8wSQiGH4NLoDJ4piKuUAwvGD3ss1cIoWZLEzRQECdpy2hV4exmtfh Z2YXGqx7RvGogjRFR//HDAoV4UZlaVXat7BpjqPU2YmpFQTEuO6yfYmKOHx3LMlnNJy4 YB+QmeHPDCs/dxzpXiRtfgjcmgYsxrc9QTEmjsJbMYCl1zDY+5uvSWgRzZvpetXOYfcd lfK0LYtGq7DMgGLB93tBp3LG5RHp5+WbXM+ZcLxhPvddR8lw9QJMW5ohP9L8oURs1QfD W3Kt4onjTuNhgEaLQNE/A2ynig50XIK97CVy5GnTDwFnj5sWPqlQq8lhDQJLcYjA/tQ5 9JnA==
MIME-Version: 1.0
X-Received: by 10.194.62.176 with SMTP id z16mr43674804wjr.76.1402589805293; Thu, 12 Jun 2014 09:16:45 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Thu, 12 Jun 2014 09:16:45 -0700 (PDT)
In-Reply-To: <5399B704.5090007@dcrocker.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net>
Date: Thu, 12 Jun 2014 12:16:45 -0400
X-Google-Sender-Auth: ig1MOyFZPUeD6sdW6yPr3_Djx00
Message-ID: <CAMm+LwjVa+PPmZjYLi+-hVHzDhpXWUJU25BeKRTOfpPr1TQBqQ@mail.gmail.com>
Subject: Re: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7ba979c21c3bf904fba5e3bd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cOS3TXcdgDaGFt_anWbNhT7MV2E
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 16:16:50 -0000

--047d7ba979c21c3bf904fba5e3bd
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 12, 2014 at 10:19 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>
> > My point is that mail is an old protocol and people who expect that it
> > can be kept going unaltered in its original form serving all the
> > purposes that it was never designed for but have emerged over time are
> > going to be upset no matter what.
>
>
> This is a variant of the usual refrain, over the last 20 years, about
> dealing with some limitation or other to email.  It goes along the lines
> of "We need to throw out SMTP and start over."
>

No, not quite. Think of it as we have a dying patient on the operating
table and we are going to amputate parts to keep them alive, replacing them
with prosthetics as we go.

Eventually the prosthetics will take over and we can replace the head. But
thats not where we are starting.




> To this and the above I have my own usual refrain:
>
>      There will come a point at which SMTP (or IMAP, or the email object
> or...) do need to be replaced.  An appropriate procedure for deciding
> when that point has been reached needs to be:
>
>      1.  Get community (rough) consensus about the non-technical
> characteristics for the functional change; that is, agreement about what
> the community wants to do with/for email that it cannot currently do.
>
>      2.  The email technical community has been successfully making
> enhancements to the same continuously running end-to-end service for
> 30-40 years (depending upon how one counts); so give it a chance to find
> a way to incrementally improve the existing service to support whatever
> is needed.
>
>      3.  When the technical community fails, it will be time to develop
> the relevant protocol/format/whatever.
>
> On the average, those calling for replacing SMTP (or whatever) have been
> stopped at the first step.
>
> Someday, they won't be.
>
> But until then, meta-declarations about needing to replace Internet Mail
> (or any other existing Internet service) don't have much practical purpose.


In the AI community they like to talk about problems being AI-complete,
that is if you can solve that problem you can solve all AI problems.

Pointing out that an approach is less likely to succeed than replacing some
of the email infrastructure seems a useful approach to me.


We do in fact have emergent quasi-mail systems including Dropbox like
things and blogs with subscriptions to comments that don't really fit well
in the email infrastructure either. My proposal was not to replace the
email core, it was to design a purpose built protocol for things email has
always done rather badly.

--047d7ba979c21c3bf904fba5e3bd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jun 12, 2014 at 10:19 AM, Dave Crocker <span dir=3D"ltr">&l=
t;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br>
&gt; My point is that mail is an old protocol and people who expect that it=
<br>
&gt; can be kept going unaltered in its original form serving all the<br>
&gt; purposes that it was never designed for but have emerged over time are=
<br>
&gt; going to be upset no matter what.<br>
<br>
<br>
</div>This is a variant of the usual refrain, over the last 20 years, about=
<br>
dealing with some limitation or other to email. =C2=A0It goes along the lin=
es<br>
of &quot;We need to throw out SMTP and start over.&quot;<br></blockquote><d=
iv><br></div><div>No, not quite. Think of it as we have a dying patient on =
the operating table and we are going to amputate parts to keep them alive, =
replacing them with prosthetics as we go.</div>
<div><br></div><div>Eventually the prosthetics will take over and we can re=
place the head. But thats not where we are starting.</div><div><br></div><d=
iv><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

To this and the above I have my own usual refrain:<br>
<br>
=C2=A0 =C2=A0 =C2=A0There will come a point at which SMTP (or IMAP, or the =
email object<br>
or...) do need to be replaced. =C2=A0An appropriate procedure for deciding<=
br>
when that point has been reached needs to be:<br>
<br>
=C2=A0 =C2=A0 =C2=A01. =C2=A0Get community (rough) consensus about the non-=
technical<br>
characteristics for the functional change; that is, agreement about what<br=
>
the community wants to do with/for email that it cannot currently do.<br>
<br>
=C2=A0 =C2=A0 =C2=A02. =C2=A0The email technical community has been success=
fully making<br>
enhancements to the same continuously running end-to-end service for<br>
30-40 years (depending upon how one counts); so give it a chance to find<br=
>
a way to incrementally improve the existing service to support whatever<br>
is needed.<br>
<br>
=C2=A0 =C2=A0 =C2=A03. =C2=A0When the technical community fails, it will be=
 time to develop<br>
the relevant protocol/format/whatever.<br>
<br>
On the average, those calling for replacing SMTP (or whatever) have been<br=
>
stopped at the first step.<br>
<br>
Someday, they won&#39;t be.<br>
<br>
But until then, meta-declarations about needing to replace Internet Mail<br=
>
(or any other existing Internet service) don&#39;t have much practical purp=
ose.</blockquote><div><br></div><div>In the AI community they like to talk =
about problems being AI-complete, that is if you can solve that problem you=
 can solve all AI problems.</div>
<div><br></div><div>Pointing out that an approach is less likely to succeed=
 than replacing some of the email infrastructure seems a useful approach to=
 me.</div><div><br></div><div><br></div><div>We do in fact have emergent qu=
asi-mail systems including Dropbox like things and blogs with subscriptions=
 to comments that don&#39;t really fit well in the email infrastructure eit=
her. My proposal was not to replace the email core, it was to design a purp=
ose built protocol for things email has always done rather badly.</div>
<div>=C2=A0</div></div></div></div>

--047d7ba979c21c3bf904fba5e3bd--


From nobody Thu Jun 12 09:33:34 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B24F1B27AE for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 09:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 DBbbFTrQqVSQ for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 09:33:31 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52B341A0880 for <ietf@ietf.org>; Thu, 12 Jun 2014 09:33:31 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id q59so1593868wes.12 for <ietf@ietf.org>; Thu, 12 Jun 2014 09:33:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=VYGM1i1GWQAd1l5wkrBCjN39hbpY9KefaWpyREwW49s=; b=t94pUPzAPSGF9jSiLoRCSFerMhuONERum+yc2Ni042uN18dhqltsyUeyCGp8sh9jHd lpwduP8FU3lQRin/mgt+hMFucNCMT0NmhkUSBaTS6aUzKBSZBmqKFvUz8E9vaO7w46e9 CX67d1F7NfqOB2Qeq4AggUoq0jf+Qd7H5tchc0D60IE6F2FtUVryJg2WwPi2o01gAA+M 86TpKvLBZqhrupc/tpdKkdHG8rND4ejEsdqE24Fb+bPWgJIjPZv33hQPTCtrmMctev7k IqyxDbefvkPM24v6t/ITg4A5f6e8Q9aZ6f1TFcjpqjr8lWqYKx5fIF90lEn0CnSs3lJU 9liA==
MIME-Version: 1.0
X-Received: by 10.180.7.227 with SMTP id m3mr7761442wia.59.1402590809840; Thu, 12 Jun 2014 09:33:29 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Thu, 12 Jun 2014 09:33:29 -0700 (PDT)
In-Reply-To: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com>
Date: Thu, 12 Jun 2014 12:33:29 -0400
X-Google-Sender-Auth: _AyBGeEyaH44MIjdrW-DNbUX3D4
Message-ID: <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com>
Subject: Re: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=f46d04440208fc664d04fba61e13
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oxwiL6VfacJdUtxJBAN10S3cixw
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 16:33:33 -0000

--f46d04440208fc664d04fba61e13
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin <john-ietf@jck.com> wrote:

>
> --On Thursday, June 12, 2014 16:19 +0200 Dave Crocker
> <dhc@dcrocker.net> wrote:
> (2) One of those changes --support for remote body parts-- was
> incorporated into MIME in its very first version and contains
> most of the mechanism needed to support what I understand PHB is
> recommending for PUSH-PULL-PULL.  It has been implemented in
> several places but has gotten very little traction in the mail
> sending and receiving community.  IMO, it ought to be incumbent
> on anyone proposing a different "get notification, then retrieve
> mail from server" model explain why their ideas will be more
> successful than that 20-odd-year-old MIME mechanism.
>

In a word - WebMail.

Updating mail clients is a long and tedious process so it is not surprising
that updates take a lot of time to percolate through. It was 5 years after
the initial deployment of MIME before mail clients to support it became
common. And the first of those that did were actually combined mail/NNTP
readers.

WebMail is a much more fluid environment. A change in the specs can be
pushed out to half the mail userbase very quickly. With DKIM we saw changes
pushed out to around a tenth of the mail user base in a few hours.

All it would take to make a change stick is to up update mailman and a few
other mailing list managers and get buy in from the companies that are
pushing DMARC. And the proposal would save them a lot of money because they
would only need to pull and store data once per list rather than for every
subscriber they support.

I don't read all my mail in Webmail, but I read all my mailing list mail in
WebMail.



> (3) Even though adjustments have been made to deal with changing
> knowledge and needs, we have been using the old, Newtonian, view
> of mechanics for circa 300 years, not merely 30 or 40.  Perhaps
> the argument for dumping old things because not every issue and
> bit of future knowledge was originally designed into those
> laws/theories should be used to dump them too.  Perhaps they
> should even have been dumped in the middle of the 19th century
> before relativity and quantum theory came along.
>

Actually Newton made the exact same arguments as Einstein concerning
relativity. The only difference was that Newton concluded that the speed of
light must be infinite which was consistent with the empirical observations
possible in his day.

The starting point for this discussion was that people claimed that DMARC
would cause a loss of email functionality that really matters. There are
thus three possible outcomes:

1) Google and Yahoo abandon use of an important anti-spam tool because the
ability for anyone to send mail from a domain from anywhere they choose
really matters.

2) Google and Yahoo continue use of an important anti-spam tool they have
developed and deployed because said ability does not matter enough.

3) The IETF community develops a new protocol that meets the needs that
will be negatively impacted by DMARC.


Now I think it abundantly clear that arguments in favor of 1 have lost
already and should lose. So we are really arguing between choice 2 or 3.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jun 12, 2014 at 10:50 AM, John C Klensin <span dir=3D"ltr">&lt;<a href=
=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><br>
--On Thursday, June 12, 2014 16:19 +0200 Dave Crocker<br>
<div class=3D"">&lt;<a href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net</a=
>&gt; wrote:<br></div>
(2) One of those changes --support for remote body parts-- was<br>
incorporated into MIME in its very first version and contains<br>
most of the mechanism needed to support what I understand PHB is<br>
recommending for PUSH-PULL-PULL. =C2=A0It has been implemented in<br>
several places but has gotten very little traction in the mail<br>
sending and receiving community. =C2=A0IMO, it ought to be incumbent<br>
on anyone proposing a different &quot;get notification, then retrieve<br>
mail from server&quot; model explain why their ideas will be more<br>
successful than that 20-odd-year-old MIME mechanism.<br></blockquote><div><=
br></div><div>In a word - WebMail.</div><div><br></div><div>Updating mail c=
lients is a long and tedious process so it is not surprising that updates t=
ake a lot of time to percolate through. It was 5 years after the initial de=
ployment of MIME before mail clients to support it became common. And the f=
irst of those that did were actually combined mail/NNTP readers.</div>
<div><br></div><div>WebMail is a much more fluid environment. A change in t=
he specs can be pushed out to half the mail userbase very quickly. With DKI=
M we saw changes pushed out to around a tenth of the mail user base in a fe=
w hours.</div>
<div><br></div><div>All it would take to make a change stick is to up updat=
e mailman and a few other mailing list managers and get buy in from the com=
panies that are pushing DMARC. And the proposal would save them a lot of mo=
ney because they would only need to pull and store data once per list rathe=
r than for every subscriber they support.=C2=A0</div>
<div><br></div><div>I don&#39;t read all my mail in Webmail, but I read all=
 my mailing list mail in WebMail.</div><div><br></div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">

(3) Even though adjustments have been made to deal with changing<br>
knowledge and needs, we have been using the old, Newtonian, view<br>
of mechanics for circa 300 years, not merely 30 or 40. =C2=A0Perhaps<br>
the argument for dumping old things because not every issue and<br>
bit of future knowledge was originally designed into those<br>
laws/theories should be used to dump them too. =C2=A0Perhaps they<br>
should even have been dumped in the middle of the 19th century<br>
before relativity and quantum theory came along.<br></blockquote><div><br><=
/div><div>Actually Newton made the exact same arguments as Einstein concern=
ing relativity. The only difference was that Newton concluded that the spee=
d of light must be infinite which was consistent with the empirical observa=
tions possible in his day.</div>
<div><br></div><div>The starting point for this discussion was that people =
claimed that DMARC would cause a loss of email functionality that really ma=
tters. There are thus three possible outcomes:</div><div><br></div><div>
1) Google and Yahoo abandon use of an important anti-spam tool because the =
ability for anyone to send mail from a domain from anywhere they choose rea=
lly matters.</div><div><br></div><div>2) Google and Yahoo continue use of a=
n important anti-spam tool they have developed and deployed because said ab=
ility does not matter enough.<br>
</div><div><br></div><div>3) The IETF community develops a new protocol tha=
t meets the needs that will be negatively impacted by DMARC.</div><div><br>=
</div><div><br></div><div>Now I think it abundantly clear that arguments in=
 favor of 1 have lost already and should lose. So we are really arguing bet=
ween choice 2 or 3.=C2=A0</div>
</div></div></div>

--f46d04440208fc664d04fba61e13--


From nobody Thu Jun 12 11:55:49 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7AC1A023A for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 11:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 FORc29XgIs5K for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 11:55:46 -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 583061A0236 for <ietf@ietf.org>; Thu, 12 Jun 2014 11:55:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.25]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s5CItWEr019840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 12 Jun 2014 11:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402599344; x=1402685744; bh=pfmZYa+oyawQlaSDpfW8WX769LbpKGlEFwKkVxDVBdw=; h=Date:To:From:Subject:In-Reply-To:References; b=AXr8b0d5EBRscz1RxoPvGZKY7HD9HFseSI87MCy63M2DZyuUpq2fSXSZ/fJ8Du5Fz pnf1yzs/5qZPaSFRJ2REJZ9r00n2p9FcGqZLWmGdN7i40SM+plEuUq12ziHSeJgtHx EIwARLNKYhFKrDeXKU6Fd094Av2V0zfNYfkzhBrU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402599344; x=1402685744; i=@elandsys.com; bh=pfmZYa+oyawQlaSDpfW8WX769LbpKGlEFwKkVxDVBdw=; h=Date:To:From:Subject:In-Reply-To:References; b=Hdy1rZfJQzSkxgeUytu+XUuFz2Do3lUt3RbpY2Hm6WXiQn22C70ZdmfTCUmkyrJtQ 6Yc3dNl2Eju5jEqbtYiSjX3Mn0bFHF8YFnqtv/ga9CnIepuvFLQXL1HGUmx6qoCHQN yIoMQkZw9hiqI5qrMVTefpqAKr6Mo7LV+qxhu0ms=
Message-Id: <6.2.5.6.2.20140612102110.0e4fa980@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 12 Jun 2014 11:34:25 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
In-Reply-To: <20140612132656.8100.57197.idtracker@ietfa.amsl.com>
References: <20140612132656.8100.57197.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Iyfs9Ejl9-bJRyOzJQA7rdQSiio
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 18:55:48 -0000

At 06:26 12-06-2014, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IETF Working Groups' Secretaries'
>   <draft-secretaries-good-practices-06.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2014-07-10. Exceptionally, comments may be

I would give credit the anonymous reviewer who pointed this out.  A 
Working Group Chair has the responsibility to make decisions on 
behalf of the working group.  There are times where one or more 
participants disagree with a decision which was taken.  The question 
of who is responsible comes into play if the WG Secretary took the 
decision.  There is the word "responsibility" in the heading of 
Section 3 of the draft.  I suggest avoiding that word in the draft as 
I don't think it is okay to blame the WG Secretary for process 
issues.  Some people may consider that it is fair game to do that.  I 
suggest also reviewing the usage of the word "accountable".

In Section 3.1.1:

   "Note that WG Chairs may wish to set policies for accepting
    discussion's slot requests."

I suggest using the word "guidelines" instead of "policies".

Section 3.2 uses the term "WG document's adoption polls".  I suggest 
avoiding the word "polls" as it sounds like voting.

   "Decisions are sometimes taken by WG Chairs during WG sessions."

It has been said that decisions are taken on the mailing list.  The 
above can be a problem when BCP 25 is invoked.

I would like to thank the authors for putting the effort in doing this work.

Regards,
S. Moonesamy 


From nobody Thu Jun 12 12:03:27 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89C641B2AF7; Thu, 12 Jun 2014 12:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.881
X-Spam-Level: 
X-Spam-Status: No, score=-2.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 iAnX-LtYL2cA; Thu, 12 Jun 2014 12:03:20 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA5E1B2AE9; Thu, 12 Jun 2014 12:03:20 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A4FEECC094; Thu, 12 Jun 2014 15:03:19 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id avliuCg1VV6Q; Thu, 12 Jun 2014 15:03:15 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1FF56CC087; Thu, 12 Jun 2014 15:03:15 -0400 (EDT)
Message-ID: <5399F971.8010605@meetinghouse.net>
Date: Thu, 12 Jun 2014 15:03:13 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
In-Reply-To: <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rOqS2oa6gfkTMBVN-K_FLw8Bg-c
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 19:03:22 -0000

Phillip Hallam-Baker wrote:
>
>
>
> On Wed, Jun 11, 2014 at 1:00 PM, Martin Rex <mrex@sap.com 
> <mailto:mrex@sap.com>> wrote:
>
>     Phillip Hallam-Baker wrote:
>     > Hector Santos <hsantos@isdg.net <mailto:hsantos@isdg.net>> wrote:
>     >>
>     >> Let me ask, what if a fedex.com <http://fedex.com> employee use
>     this email domain for
>     >> subscribing to the IETF list?
>     >
>     > Any subsequent problems are irrelevant unless FedEx, the owner of
>     > fedex.com <http://fedex.com> considers them to be relevant.
>     >
>     > That is what folk complaining don't get: you don't have the right to
>     > use your employers email or a public email provider's email any way
>     > you want. The domain name owner makes the rules.
>     >
>     > As Craster insists: My domain, my rules.
>
>     Strange concept!
>
>     Does your jurisdiction allow your landlord to interfere with
>     postal/snail mail that is delivered from or to your rented appartment?
>
>
> Absent specific government action to protect the tenant, the landlord 
> can abuse them in almost any way they choose. Which is why we have 
> voluminous legislative protections for tenants. There is an entire 
> field of law concerning that.
>
>
Though, in the case of mail, it's Federal law that prevents "mail 
tampering" and other unauthorized interference with US mail.  I'm not 
100% sure, but I expect that an employer might not be legally allowed to 
interfere with a letter addressed to you, at your workplace.

When it comes to email - there are (or at least used to be) the Email 
Privacy Act - which forbid employers from reading your mail, in the 
absence of a clearly stated policy that reserved the right to do so.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Jun 12 18:14:27 2014
Return-Path: <ryoo@etri.re.kr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 056FF1B2815; Thu, 12 Jun 2014 18:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 OgGRSOhab0oh; Thu, 12 Jun 2014 18:14:22 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr [129.254.27.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2447F1A00DF; Thu, 12 Jun 2014 18:14:22 -0700 (PDT)
Received: from SMTP4.etri.info (129.254.28.74) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 13 Jun 2014 10:14:15 +0900
Received: from SMTP2.etri.info ([169.254.2.160]) by SMTP4.etri.info ([10.2.6.33]) with mapi id 14.01.0355.002; Fri, 13 Jun 2014 10:14:17 +0900
From: Jeong Ryoo <ryoo@etri.re.kr>
To: Zhenlong Cui <c-sai@bx.jp.nec.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [mpls] I-D Action: draft-ietf-mpls-smp-requirements-06.txt
Thread-Topic: [mpls] I-D Action: draft-ietf-mpls-smp-requirements-06.txt
Thread-Index: AQHPhHuwKsEsUoX+VU2zuiKoviH3D5ts1q2AgAFfhFk=
Date: Fri, 13 Jun 2014 01:14:16 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A28744EF6@SMTP2.etri.info>
References: <20140610071412.6466.24044.idtracker@ietfa.amsl.com>, <E703759D9A8E6446BEA7F57C9A91381A7283D6@BPXM18GP.gisp.nec.co.jp>
In-Reply-To: <E703759D9A8E6446BEA7F57C9A91381A7283D6@BPXM18GP.gisp.nec.co.jp>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-new-displayname: SmVvbmcgUnlvbw==
x-originating-ip: [129.254.28.46]
Content-Type: multipart/alternative; boundary="_000_5B4A6CBE3924BB41A3BEE462A8E0B75A28744EF6SMTP2etriinfo_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/leNisfeMFC4QKsN14cK2Fm6Ct5o
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 01:14:26 -0000

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

RGVhciBaaGVubG9uZywNCg0KVGhhbmtzIGZvciB0aGUgY29tbWVudC4NCm46MSBpcyBtZWFudCB0
byBiZSBhIHNwZWNpYWwgY2FzZSBvZiBtOm4sIHdoZXJlIG0gcHJvdGVjdGlvbiBwYXRocyBhcmUg
cHJlcGFyZWQgdG8gcHJvdGVjdCBuIHdvcmtpbmcgcGF0aHMsDQphbmQgbWF5IGJlIGV4cHJlc3Nl
ZCBiZXR0ZXIgaWYgbToxIGlzIHVzZWQgaW5zdGVhZC4NCkluIG15IG9waW5pb24sIHRoZSBuZXh0
IHZlcnNpb24gb2YgdGhpcyBkcmFmdCBuZWVkcyB0byBpbmNvcnBvcmF0ZSB5b3VyIGNvbW1lbnRz
Lg0KDQpCZXN0IHJlZ2FyZHMsDQoNCkplb25nLWRvbmcNCg0KDQoNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCuuztOuCuCDsgqzrnowgOiAiWmhlbmxvbmcgQ3VpIiA8Yy1zYWlA
YnguanAubmVjLmNvbT4NCuuztOuCuCDrgqDsp5wgOiAyMDE0LTA2LTEyIDIxOjQwOjAyICggKzA5
OjAwICkNCuuwm+uKlCDsgqzrnowgOiBpZXRmQGlldGYub3JnIDxpZXRmQGlldGYub3JnPg0K7LC4
7KGwIDogbXBsc0BpZXRmLm9yZyA8bXBsc0BpZXRmLm9yZz4NCuygnOuqqSA6IFJlOiBbbXBsc10g
SS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1tcGxzLXNtcC1yZXF1aXJlbWVudHMtMDYudHh0DQoNCkhp
IGF1dGhvcnMsDQoNCkJvdGggMTpuIGFuZCBuOjEgYXJlIGRlc2NyaWJlZCBpbiB5b3VyIGRyYWZ0
Lg0KDQpDb3VsZCB5b3UgZXhwbGFpbiAibjoxLCAxOm4sIG06biIgd2hlcmUgaXQgaXMgZmlyc3Qg
dXNlZD8NCjE6biBwcm90ZWN0aW9uIGFuZCBtOm4gcHJvdGVjdGlvbiBhcmUgZGVmaW5lZCBpbiBH
LjgwOC4xIGFuZCBSRkMgNDQyNywgYnV0IEkgY2FuJ3QgZmluZCBhIGRlZmluaXRpb24gZm9yIG46
MS4NCg0KQmVzdCByZWdhcmRzLA0KemhlbmxvbmcNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPiBGcm9tOiBtcGxzIFttYWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQo+IFNlbnQ6IFR1ZXNkYXksIEp1bmUgMTAs
IDIwMTQgNDoxNCBQTQ0KPiBUbzogaS1kLWFubm91bmNlQGlldGYub3JnDQo+IENjOiBtcGxzQGll
dGYub3JnDQo+IFN1YmplY3Q6IFttcGxzXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLW1wbHMtc21w
LXJlcXVpcmVtZW50cy0wNi50eHQNCj4NCj4NCj4gQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZh
aWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KPiBU
aGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBNdWx0aXByb3RvY29sIExhYmVsIFN3aXRj
aGluZyBXb3JraW5nIEdyb3VwIG9mIHRoZSBJRVRGLg0KPg0KPiBUaXRsZSA6IFJlcXVpcmVtZW50
cyBmb3IgTVBMUy1UUCBTaGFyZWQgTWVzaCBQcm90ZWN0aW9uDQo+IEF1dGhvcnMgOiBZYWFjb3Yg
V2VpbmdhcnRlbg0KPiBTYW0gQWxkcmluDQo+IFBpbmcgUGFuDQo+IEplb25nLWRvbmcgUnlvbw0K
PiBHcmVnIE1pcnNreQ0KPiBGaWxlbmFtZSA6IGRyYWZ0LWlldGYtbXBscy1zbXAtcmVxdWlyZW1l
bnRzLTA2LnR4dA0KPiBQYWdlcyA6IDE0DQo+IERhdGUgOiAyMDE0LTA2LTEwDQo+DQo+IEFic3Ry
YWN0Og0KPiBUaGlzIGRvY3VtZW50IHByZXNlbnRzIHRoZSBiYXNpYyBuZXR3b3JrIG9iamVjdGl2
ZXMgZm9yIHRoZSBiZWhhdmlvcg0KPiBvZiBzaGFyZWQgbWVzaCBwcm90ZWN0aW9uIChTTVApIHdo
aWNoIGFyZSBub3QgYmFzZWQgb24gY29udHJvbCBwbGFuZQ0KPiBzdXBwb3J0LiBUaGlzIGlzIGFu
IGV4cGFuc2lvbiBvZiB0aGUgYmFzaWMgcmVxdWlyZW1lbnRzIHByZXNlbnRlZCBpbg0KPiBSRkMg
NTY1NCAiUmVxdWlyZW1lbnRzIGZvciB0aGUgVHJhbnNwb3J0IFByb2ZpbGUgb2YgTVBMUyIgYW5k
IFJGQw0KPiA2MzcyICJNUExTIFRyYW5zcG9ydCBQcm9maWxlIChNUExTLVRQKSBTdXJ2aXZhYmls
aXR5IEZyYW1ld29yayIuDQo+IFRoaXMgZG9jdW1lbnQgaXMgdG8gYmUgdXNlZCBhcyBhIGJhc2lz
IGZvciB0aGUgZGVmaW5pdGlvbiBvZiBhbnkNCj4gbWVjaGFuaXNtIHRoYXQgd291bGQgYmUgdXNl
ZCB0byBpbXBsZW1lbnQgU01QIGZvciBNUExTLVRQIGRhdGEgcGF0aHMsDQo+IGluIG5ldHdvcmtz
IHRoYXQgZGVsZWdhdGUgZXhlY3V0aXZlIGFjdGlvbiBmb3IgcmVzaWxpZW5jeSB0byB0aGUgZGF0
YQ0KPiBwbGFuZS4NCj4NCj4NCj4gVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9y
IHRoaXMgZHJhZnQgaXM6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWlldGYtbXBscy1zbXAtcmVxdWlyZW1lbnRzLw0KPg0KPiBUaGVyZSdzIGFsc28gYSBodG1saXpl
ZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaWV0Zi1tcGxzLXNtcC1yZXF1aXJlbWVudHMtMDYNCj4NCj4gQSBkaWZmIGZyb20gdGhlIHBy
ZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPiBodHRwOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1pZXRmLW1wbHMtc21wLXJlcXVpcmVtZW50cy0wNg0KPg0KPg0KPiBQ
bGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUg
dGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFy
ZSBhdmFpbGFibGUNCj4gYXQgdG9vbHMuaWV0Zi5vcmcuDQo+DQo+IEludGVybmV0LURyYWZ0cyBh
cmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj4gZnRwOi8vZnRwLmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy8NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gbXBsc0BpZXRmLm9yZw0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1wbHMgbWFpbGluZyBsaXN0
DQptcGxzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21w
bHMNCg==

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBpZD0iZXpG
b3JtUHJvY19kaXYiIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiDqtbTrprwi
Pg0KPGRpdiBpZD0ibXNnYm9keSI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6IDIw
cHQiPkRlYXIgWmhlbmxvbmcsPC9kaXY+DQo8ZGl2IHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+
Jm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+VGhhbmtzIGZvciB0
aGUgY29tbWVudC48L2Rpdj4NCjxkaXYgc3R5bGU9IkxJTkUtSEVJR0hUOiAyMHB0Ij5uOjEgaXMg
bWVhbnQgdG8gYmUgYSBzcGVjaWFsIGNhc2Ugb2YgbTpuLCB3aGVyZSBtIHByb3RlY3Rpb24gcGF0
aHMgYXJlIHByZXBhcmVkIHRvIHByb3RlY3QgbiB3b3JraW5nIHBhdGhzLDwvZGl2Pg0KPGRpdiBz
dHlsZT0iTElORS1IRUlHSFQ6IDIwcHQiPmFuZCBtYXkgYmUgZXhwcmVzc2VkIGJldHRlciBpZiBt
OjEgaXMgdXNlZCBpbnN0ZWFkLjwvZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6IDIwcHQi
PkluIG15IG9waW5pb24sIHRoZSBuZXh0IHZlcnNpb24gb2YgdGhpcyBkcmFmdCBuZWVkcyB0byBp
bmNvcnBvcmF0ZSB5b3VyIGNvbW1lbnRzLjwvZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6
IDIwcHQiPiZuYnNwOzwvZGl2Pg0KPGRpdiBzdHlsZT0iTElORS1IRUlHSFQ6IDIwcHQiPkJlc3Qg
cmVnYXJkcyw8L2Rpdj4NCjxkaXYgc3R5bGU9IkxJTkUtSEVJR0hUOiAyMHB0Ij4mbmJzcDs8L2Rp
dj4NCjxkaXYgc3R5bGU9IkxJTkUtSEVJR0hUOiAyMHB0Ij5KZW9uZy1kb25nPC9kaXY+DQo8ZGl2
IHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+PGJyPg0KPGJyPg0KJm5ic3A7PC9kaXY+DQo8ZGl2
IGlkPSJNYWlsU2lnblNlbnQiIHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+PGJyPg0KPC9kaXY+
DQo8ZGl2IGlkPSJPUkdNQUlMX0NPTlRFTlQiIHN0eWxlPSJMSU5FLUhFSUdIVDogMjBwdCI+DQo8
aHIgdGFiaW5kZXg9Ii0xIj4NCjxiPuuztOuCuCDsgqzrnowgOiA8L2I+JnF1b3Q7Wmhlbmxvbmcg
Q3VpJnF1b3Q7ICZsdDtjLXNhaUBieC5qcC5uZWMuY29tJmd0Ozxicj4NCjxiPuuztOuCuCDrgqDs
p5wgOiA8L2I+MjAxNC0wNi0xMiAyMTo0MDowMiAoICYjNDM7MDk6MDAgKTxicj4NCjxiPuuwm+uK
lCDsgqzrnowgOiA8L2I+aWV0ZkBpZXRmLm9yZyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDs8YnI+DQo8
Yj7ssLjsobAgOiA8L2I+bXBsc0BpZXRmLm9yZyAmbHQ7bXBsc0BpZXRmLm9yZyZndDs8YnI+DQo8
Yj7soJzrqqkgOiA8L2I+UmU6IFttcGxzXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLW1wbHMtc21w
LXJlcXVpcmVtZW50cy0wNi50eHQ8YnI+DQo8YnI+DQpIaSBhdXRob3JzLDxicj4NCjxicj4NCkJv
dGggMTpuIGFuZCBuOjEgYXJlIGRlc2NyaWJlZCBpbiB5b3VyIGRyYWZ0Ljxicj4NCjxicj4NCkNv
dWxkIHlvdSBleHBsYWluICZxdW90O246MSwgMTpuLCBtOm4mcXVvdDsgd2hlcmUgaXQgaXMgZmly
c3QgdXNlZD88YnI+DQoxOm4gcHJvdGVjdGlvbiBhbmQgbTpuIHByb3RlY3Rpb24gYXJlIGRlZmlu
ZWQgaW4gRy44MDguMSBhbmQgUkZDIDQ0MjcsIGJ1dCBJIGNhbid0IGZpbmQgYSBkZWZpbml0aW9u
IGZvciBuOjEuPGJyPg0KPGJyPg0KQmVzdCByZWdhcmRzLDxicj4NCnpoZW5sb25nPGJyPg0KPGJy
Pg0KJmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsgRnJvbTogbXBscyBb
bWFpbHRvOm1wbHMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGludGVybmV0LWRyYWZ0
c0BpZXRmLm9yZzxicj4NCiZndDsgU2VudDogVHVlc2RheSwgSnVuZSAxMCwgMjAxNCA0OjE0IFBN
PGJyPg0KJmd0OyBUbzogaS1kLWFubm91bmNlQGlldGYub3JnPGJyPg0KJmd0OyBDYzogbXBsc0Bp
ZXRmLm9yZzxicj4NCiZndDsgU3ViamVjdDogW21wbHNdIEktRCBBY3Rpb246IGRyYWZ0LWlldGYt
bXBscy1zbXAtcmVxdWlyZW1lbnRzLTA2LnR4dDxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQom
Z3Q7IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIElu
dGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy48YnI+DQomZ3Q7IFRoaXMgZHJhZnQgaXMgYSB3b3Jr
IGl0ZW0gb2YgdGhlIE11bHRpcHJvdG9jb2wgTGFiZWwgU3dpdGNoaW5nIFdvcmtpbmcgR3JvdXAg
b2YgdGhlIElFVEYuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRpdGxlIDogUmVxdWlyZW1lbnRzIGZv
ciBNUExTLVRQIFNoYXJlZCBNZXNoIFByb3RlY3Rpb248YnI+DQomZ3Q7IEF1dGhvcnMgOiBZYWFj
b3YgV2VpbmdhcnRlbjxicj4NCiZndDsgU2FtIEFsZHJpbjxicj4NCiZndDsgUGluZyBQYW48YnI+
DQomZ3Q7IEplb25nLWRvbmcgUnlvbzxicj4NCiZndDsgR3JlZyBNaXJza3k8YnI+DQomZ3Q7IEZp
bGVuYW1lIDogZHJhZnQtaWV0Zi1tcGxzLXNtcC1yZXF1aXJlbWVudHMtMDYudHh0PGJyPg0KJmd0
OyBQYWdlcyA6IDE0PGJyPg0KJmd0OyBEYXRlIDogMjAxNC0wNi0xMDxicj4NCiZndDsgPGJyPg0K
Jmd0OyBBYnN0cmFjdDo8YnI+DQomZ3Q7IFRoaXMgZG9jdW1lbnQgcHJlc2VudHMgdGhlIGJhc2lj
IG5ldHdvcmsgb2JqZWN0aXZlcyBmb3IgdGhlIGJlaGF2aW9yPGJyPg0KJmd0OyBvZiBzaGFyZWQg
bWVzaCBwcm90ZWN0aW9uIChTTVApIHdoaWNoIGFyZSBub3QgYmFzZWQgb24gY29udHJvbCBwbGFu
ZTxicj4NCiZndDsgc3VwcG9ydC4gVGhpcyBpcyBhbiBleHBhbnNpb24gb2YgdGhlIGJhc2ljIHJl
cXVpcmVtZW50cyBwcmVzZW50ZWQgaW48YnI+DQomZ3Q7IFJGQyA1NjU0ICZxdW90O1JlcXVpcmVt
ZW50cyBmb3IgdGhlIFRyYW5zcG9ydCBQcm9maWxlIG9mIE1QTFMmcXVvdDsgYW5kIFJGQzxicj4N
CiZndDsgNjM3MiAmcXVvdDtNUExTIFRyYW5zcG9ydCBQcm9maWxlIChNUExTLVRQKSBTdXJ2aXZh
YmlsaXR5IEZyYW1ld29yayZxdW90Oy48YnI+DQomZ3Q7IFRoaXMgZG9jdW1lbnQgaXMgdG8gYmUg
dXNlZCBhcyBhIGJhc2lzIGZvciB0aGUgZGVmaW5pdGlvbiBvZiBhbnk8YnI+DQomZ3Q7IG1lY2hh
bmlzbSB0aGF0IHdvdWxkIGJlIHVzZWQgdG8gaW1wbGVtZW50IFNNUCBmb3IgTVBMUy1UUCBkYXRh
IHBhdGhzLDxicj4NCiZndDsgaW4gbmV0d29ya3MgdGhhdCBkZWxlZ2F0ZSBleGVjdXRpdmUgYWN0
aW9uIGZvciByZXNpbGllbmN5IHRvIHRoZSBkYXRhPGJyPg0KJmd0OyBwbGFuZS48YnI+DQomZ3Q7
IDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBm
b3IgdGhpcyBkcmFmdCBpczo8YnI+DQomZ3Q7IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWlldGYtbXBscy1zbXAtcmVxdWlyZW1lbnRzLzxicj4NCiZndDsgPGJyPg0KJmd0
OyBUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDo8YnI+DQomZ3Q7
IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbXBscy1zbXAtcmVxdWlyZW1l
bnRzLTA2PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJz
aW9uIGlzIGF2YWlsYWJsZSBhdDo8YnI+DQomZ3Q7IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LWlldGYtbXBscy1zbXAtcmVxdWlyZW1lbnRzLTA2PGJyPg0KJmd0OyA8YnI+
DQomZ3Q7IDxicj4NCiZndDsgUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv
ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQg
dmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlPGJyPg0KJmd0OyBhdCB0b29scy5pZXRmLm9y
Zy48YnI+DQomZ3Q7IDxicj4NCiZndDsgSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJs
ZSBieSBhbm9ueW1vdXMgRlRQIGF0Ojxicj4NCiZndDsgZnRwOi8vZnRwLmlldGYub3JnL2ludGVy
bmV0LWRyYWZ0cy88YnI+DQomZ3Q7IDxicj4NCiZndDsgX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IG1wbHMgbWFpbGluZyBsaXN0PGJyPg0K
Jmd0OyBtcGxzQGlldGYub3JnPGJyPg0KJmd0OyBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21wbHM8YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxicj4NCm1wbHMgbWFpbGluZyBsaXN0PGJyPg0KbXBsc0BpZXRmLm9y
Zzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBsczxicj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5B4A6CBE3924BB41A3BEE462A8E0B75A28744EF6SMTP2etriinfo_--


From nobody Thu Jun 12 21:53:18 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0FF11B28B6 for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 5QnHbAkYZ9-x for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 21:53:06 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDD11B28BB for <ietf@ietf.org>; Thu, 12 Jun 2014 21:53:06 -0700 (PDT)
Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 12 Jun 2014 22:53:05 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 12 Jun 2014 22:53:04 -0600
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 2014F19D8026 for <ietf@ietf.org>; Thu, 12 Jun 2014 22:52:56 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s5D4r4QL9109760 for <ietf@ietf.org>; Fri, 13 Jun 2014 06:53:04 +0200
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id s5D4uvLP013682 for <ietf@ietf.org>; Thu, 12 Jun 2014 22:56:57 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id s5D4uv0Q013666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 12 Jun 2014 22:56:57 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s5D4r2C3010734 for <ietf@ietf.org>; Fri, 13 Jun 2014 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s5D4r27H010706 for ietf@ietf.org; Fri, 13 Jun 2014 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201406130453.s5D4r27H010706@rotala.raleigh.ibm.com>
Date: Fri, 13 Jun 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14061304-1344-0000-0000-0000022EA5C8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rt3l20p1DLqDz961PMVWFzscMto
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 04:53:11 -0000

Total of 53 messages in the last 7 days.
 
script run at: Fri Jun 13 00:53:01 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  1.89% |    1 | 16.02% |    97029 | dafalla@yahoo.com
  7.55% |    4 |  7.96% |    48201 | phill@hallambaker.com
  7.55% |    4 |  4.87% |    29519 | john-ietf@jck.com
  7.55% |    4 |  4.76% |    28840 | sm+ietf@elandsys.com
  5.66% |    3 |  4.66% |    28219 | ynir.ietf@gmail.com
  5.66% |    3 |  3.34% |    20238 | dhc@dcrocker.net
  3.77% |    2 |  5.15% |    31201 | ryoo@etri.re.kr
  3.77% |    2 |  4.52% |    27385 | jari.arkko@ericsson.com
  3.77% |    2 |  3.89% |    23573 | olaf@nlnetlabs.nl
  1.89% |    1 |  5.47% |    33137 | mariainesrobles@googlemail.com
  3.77% |    2 |  3.24% |    19654 | erik.josefsson@europarl.europa.eu
  3.77% |    2 |  2.70% |    16338 | superuser@gmail.com
  3.77% |    2 |  2.47% |    14964 | rogerj@gmail.com
  3.77% |    2 |  2.17% |    13150 | ted.lemon@nominum.com
  1.89% |    1 |  2.94% |    17808 | hugo@ee.technion.ac.il
  1.89% |    1 |  2.56% |    15482 | jaldorakyor@gmail.com
  1.89% |    1 |  2.39% |    14476 | richard@shockey.us
  1.89% |    1 |  2.13% |    12882 | cdel@firsthand.net
  1.89% |    1 |  1.64% |     9935 | john.doyle@fmr.com
  1.89% |    1 |  1.55% |     9386 | narten@us.ibm.com
  1.89% |    1 |  1.49% |     9003 | keyupate@cisco.com
  1.89% |    1 |  1.44% |     8703 | daedulus@btconnect.com
  1.89% |    1 |  1.42% |     8574 | bmanning@isi.edu
  1.89% |    1 |  1.41% |     8523 | c-sai@bx.jp.nec.com
  1.89% |    1 |  1.38% |     8345 | d3e3e3@gmail.com
  1.89% |    1 |  1.28% |     7755 | marcie@usermail.com
  1.89% |    1 |  1.28% |     7742 | adrian@olddog.co.uk
  1.89% |    1 |  1.22% |     7409 | mfidelman@meetinghouse.net
  1.89% |    1 |  1.08% |     6530 | hsantos@isdg.net
  1.89% |    1 |  1.00% |     6071 | mrex@sap.com
  1.89% |    1 |  0.88% |     5353 | peter@akayla.com
  1.89% |    1 |  0.88% |     5306 | jari.arkko@piuha.net
  1.89% |    1 |  0.83% |     5000 | ahmedbakhat@pta.gov.pk
--------+------+--------+----------+------------------------
100.00% |   53 |100.00% |   605731 | Total


From nobody Fri Jun 13 04:55:38 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECAA1B279B; Fri, 13 Jun 2014 04:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 pMs05pgpkE-9; Fri, 13 Jun 2014 04:55:36 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 10CB51A024D; Fri, 13 Jun 2014 04:55:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id CF867CC07F; Fri, 13 Jun 2014 07:55:34 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lv2S47jkz7xf; Fri, 13 Jun 2014 07:55:26 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id EA6DFCC081; Fri, 13 Jun 2014 07:55:25 -0400 (EDT)
Message-ID: <539AE6AD.9090601@meetinghouse.net>
Date: Fri, 13 Jun 2014 07:55:25 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp>
In-Reply-To: <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ACsMe58T2YOul0HX7TYsBK6ugbQ
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 11:55:37 -0000

Stephen J. Turnbull wrote:
> Phillip Hallam-Baker writes:
>
>   > My point is that mail is an old protocol and people who expect that
>   > it can be kept going unaltered in its original form serving all the
>   > purposes that it was never designed for but have emerged over time
>   > are going to be upset no matter what.
>
> True, as far as it goes.  However, there is need for a push protocol
> that allows you to receive contacts from authors you don't know yet,
> in other words, a medium that is designed to be flexible enough to
> accomodate new modes of communication.
>
> It's not obvious to me that this need can be satisfied while at the
> same time denying spam.  If it is indeed impossible, I don't see why
> that purpose can't continue to be served by email, while most mail
> (which is correspondence among acquaintances) gets redirected into
> authenticated channels.
>
Just a quick reminder here:  Postal mail is still going strong, after 
100s of years.



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Jun 13 05:18:11 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2071B284E; Fri, 13 Jun 2014 05:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.277
X-Spam-Level: 
X-Spam-Status: No, score=-3.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 5UOR4UcIl2nE; Fri, 13 Jun 2014 05:18:05 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C00A1A04CA; Fri, 13 Jun 2014 05:18:05 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so2615687wgh.28 for <multiple recipients>; Fri, 13 Jun 2014 05:18:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WDor3paAr6+TJGv7JUsvwwyiHWNDu+5cktNfEQtJ7Fo=; b=yWTZ7fekYyDNNxy/yGSjGvZvIzXYu2PoDFmQvUiJO1LNUXLGeNzeYHLMxfrjjuuB6T N2HOizvmaQZj2vAgelWdJx1SHaJE4yMEqwaSsXN/HECNekDVpn7+eJeexbdI6pfkzr0Z KnG5pr+xJR4XGvugmf/ECY50gnfXclbS/+4/I/0JJRQ1A/H0i3bj08umfzpKNy80SDK4 B3utii1O87pzVi/tK3qISBO/aXLMmSktiQkQDqTqOLdFF5iu2aysIzWivCaMkP1Tvu/h JJ91C3Vzd2yMPy599xgKMnMMrKStzdGMiFEXfrNza++eI0rdFbiqxSEqke4KiVgkYUeG GPkg==
MIME-Version: 1.0
X-Received: by 10.180.105.72 with SMTP id gk8mr4338623wib.32.1402661883841; Fri, 13 Jun 2014 05:18:03 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Fri, 13 Jun 2014 05:18:03 -0700 (PDT)
In-Reply-To: <539AE6AD.9090601@meetinghouse.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp> <539AE6AD.9090601@meetinghouse.net>
Date: Fri, 13 Jun 2014 08:18:03 -0400
X-Google-Sender-Auth: 1phTXN4sPs0lPvSanjwbTmPCtH0
Message-ID: <CAMm+Lwhi+7o-GYa7Y4U-iZ=jyWX+rE4nWHrV83csO-qQOCxTVw@mail.gmail.com>
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=f46d0442685a53946404fbb6abed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YNaWPvdp-VtikmqH1Kc2HdiM-3I
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 12:18:07 -0000

--f46d0442685a53946404fbb6abed
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 13, 2014 at 7:55 AM, Miles Fidelman <mfidelman@meetinghouse.net>
wrote:

> Stephen J. Turnbull wrote:
>
>> Phillip Hallam-Baker writes:
>>
>>   > My point is that mail is an old protocol and people who expect that
>>   > it can be kept going unaltered in its original form serving all the
>>   > purposes that it was never designed for but have emerged over time
>>   > are going to be upset no matter what.
>>
>> True, as far as it goes.  However, there is need for a push protocol
>> that allows you to receive contacts from authors you don't know yet,
>> in other words, a medium that is designed to be flexible enough to
>> accomodate new modes of communication.
>>
>> It's not obvious to me that this need can be satisfied while at the
>> same time denying spam.  If it is indeed impossible, I don't see why
>> that purpose can't continue to be served by email, while most mail
>> (which is correspondence among acquaintances) gets redirected into
>> authenticated channels.
>>
>>  Just a quick reminder here:  Postal mail is still going strong, after
> 100s of years.
>
>
Only because we haven't got email security properly sorted.

I can't remember the last time I received a real letter. All I get is junk
mail and bills. And the bills arrive because we haven't got the standards
for doing it electronically established yet.

Within a decade postal mail and the telephone will have become as
functionally obsolete as fax. It will take a lot longer for them to
disappear, the telegram only stopped last year, about a hundred years after
it was utterly obsolete.

The postal service will continue of course until Bezos works out how to get
his drones to work.


Technology does change over time. There is a very clear demand for an open
Dropbox like solution. There is a clear need for a protocol that allows
email like subscriptions to blog comments without the mailbox clog that
results.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jun 13, 2014 at 7:55 AM, Miles Fidelman <span dir=3D"ltr">&=
lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelma=
n@meetinghouse.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">Step=
hen J. Turnbull wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Phillip Hallam-Baker writes:<br>
<br>
=C2=A0 &gt; My point is that mail is an old protocol and people who expect =
that<br>
=C2=A0 &gt; it can be kept going unaltered in its original form serving all=
 the<br>
=C2=A0 &gt; purposes that it was never designed for but have emerged over t=
ime<br>
=C2=A0 &gt; are going to be upset no matter what.<br>
<br>
True, as far as it goes. =C2=A0However, there is need for a push protocol<b=
r>
that allows you to receive contacts from authors you don&#39;t know yet,<br=
>
in other words, a medium that is designed to be flexible enough to<br>
accomodate new modes of communication.<br>
<br>
It&#39;s not obvious to me that this need can be satisfied while at the<br>
same time denying spam. =C2=A0If it is indeed impossible, I don&#39;t see w=
hy<br>
that purpose can&#39;t continue to be served by email, while most mail<br>
(which is correspondence among acquaintances) gets redirected into<br>
authenticated channels.<br>
<br>
</blockquote></div></div>
Just a quick reminder here: =C2=A0Postal mail is still going strong, after =
100s of years.<div class=3D"HOEnZb"><div class=3D"h5"><br></div></div></blo=
ckquote><div><br></div><div>Only because we haven&#39;t got email security =
properly sorted.</div>
<div><br></div><div>I can&#39;t remember the last time I received a real le=
tter. All I get is junk mail and bills. And the bills arrive because we hav=
en&#39;t got the standards for doing it electronically established yet.</di=
v>
<div><br></div><div>Within a decade postal mail and the telephone will have=
 become as functionally obsolete as fax. It will take a lot longer for them=
 to disappear, the telegram only stopped last year, about a hundred years a=
fter it was utterly obsolete.=C2=A0</div>
<div><br></div><div>The postal service will continue of course until Bezos =
works out how to get his drones to work.</div><div><br></div><div><br></div=
><div>Technology does change over time. There is a very clear demand for an=
 open Dropbox like solution. There is a clear need for a protocol that allo=
ws email like subscriptions to blog comments without the mailbox clog that =
results.</div>
<div>=C2=A0</div></div></div></div>

--f46d0442685a53946404fbb6abed--


From nobody Fri Jun 13 06:42:21 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A26A1B2878 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 sfRm7CPSJ2sd for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:42:10 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f51]) (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 2D2FA1B2912 for <ietf@ietf.org>; Fri, 13 Jun 2014 06:42:10 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:45324) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WvRjz-0003Fv-Wd (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 13 Jun 2014 14:41:59 +0100
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WvRjz-0006ck-1v (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 13 Jun 2014 14:41:59 +0100
Date: Fri, 13 Jun 2014 14:41:59 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Change the mailing list protocol, not DMARC.
In-Reply-To: <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com>
Message-ID: <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xTfgwvIN3dHDQyNojQoRD7HNxlg
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 13:42:16 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:
>

On external body parts:

> Implementing this 20-year-old MIME mechanism would be very difficult,
> would have limited potential payoff, and would be pretty obviously
> privacy-violating. And in order for it to do any good, recipients would
> have to refuse large attachments.

In practice message size limits are typically a few dozen MB, and people
hit this frequently enough for it to be annoying. They also have problems
with security restrictions on attachment file types.

So a number of sites have implemented systems which strip large
attachments, put them on a web server, and modify the message to include a
link to the detached file.

https://fileexchange.imperial.ac.uk/

http://fluff.bris.ac.uk/fluff/

https://webdropoff.auckland.ac.nz/

http://turin.nss.udel.edu/wiki/dropbox/doku.php

etc.

BUT! These systems do not use the MIME external body mechanism, because it
is common for mail servers to reject these messages on the grounds that
they are too difficult to properly scan for viruses.

The end result is something pretty simiilar to MIME external bodies, but
a complete mess from the protocol architecture point of view.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Lundy, Fastnet: Variable, becoming north, 3 or 4. Slight or moderate. Fair.
Good, occasionally moderate.


From nobody Fri Jun 13 06:51:08 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB9D1B2919 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 afAAX17MZb1v for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E11A01B2917 for <ietf@ietf.org>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C7F641B81FD for <ietf@ietf.org>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B73A019005C; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Jun 2014 06:51:05 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Change the mailing list protocol, not DMARC.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk>
Date: Fri, 13 Jun 2014 09:51:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BYjavd3AtCo4CGsW7GEhIMuTrbo
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 13:51:07 -0000

On Jun 13, 2014, at 9:41 AM, Tony Finch <dot@dotat.at> wrote:
> BUT! These systems do not use the MIME external body mechanism, =
because it
> is common for mail servers to reject these messages on the grounds =
that
> they are too difficult to properly scan for viruses.
>=20
> The end result is something pretty simiilar to MIME external bodies, =
but
> a complete mess from the protocol architecture point of view.

Ouch.   Yet another reason why a flag day may be necessary to improve =
the situation.


From nobody Fri Jun 13 07:59:38 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013131B28AB for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 07:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 CAaDzcT_Nayv for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 07:59:34 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34021A0132 for <ietf@ietf.org>; Fri, 13 Jun 2014 07:59:33 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id u56so2847883wes.7 for <ietf@ietf.org>; Fri, 13 Jun 2014 07:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=haUQF5g5uUsMH5atot3BCEvx+4x9yfcco3FmNv1EvxE=; b=kTPk8K5HuwQfh02mNgXHalrgyAeoZEKwIsFNRnFg7FKmxg7w+r+nlqIbUDxMSqnJt/ RSK7G37KfMH0dSVo/prMbKGTCHKT3/JSGWegwsmMRB+vtKypQ4RjHOWYeVNfCTIrHSLN S/W7XrWvGw6xvq/2emGByN5gUs0RmJJnzATE49iOgdwC79n61Zi1OhzT3cHtNvk3pvOk fGXC19m0auDE0+aPGJlUYhZ5iH+5dzKHYZA/wZ44NFtBEDJ9oVcsGk4hS2QjFDqUk9uI FskSah6ITPwDLtP2mXreHuiagSaUXI1AGgBqILcNzp/dQNTVGhCq0hZwxYJXMS6ffOyF cwSg==
MIME-Version: 1.0
X-Received: by 10.180.105.72 with SMTP id gk8mr5592147wib.32.1402671572429; Fri, 13 Jun 2014 07:59:32 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Fri, 13 Jun 2014 07:59:32 -0700 (PDT)
In-Reply-To: <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk> <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com>
Date: Fri, 13 Jun 2014 10:59:32 -0400
X-Google-Sender-Auth: uHxw7h6Bw4wrMvEoX-yHcAw5rHc
Message-ID: <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com>
Subject: Re: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=f46d0442685acfb6c504fbb8ec53
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8_HmmYpwQ66IElB6kqAHdSJMhjo
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 14:59:36 -0000

--f46d0442685acfb6c504fbb8ec53
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 13, 2014 at 9:51 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Jun 13, 2014, at 9:41 AM, Tony Finch <dot@dotat.at> wrote:
> > BUT! These systems do not use the MIME external body mechanism, because
> it
> > is common for mail servers to reject these messages on the grounds that
> > they are too difficult to properly scan for viruses.
> >
> > The end result is something pretty simiilar to MIME external bodies, but
> > a complete mess from the protocol architecture point of view.
>
> Ouch.   Yet another reason why a flag day may be necessary to improve the
> situation.
>
>
Now I will note that this is the sort of use of mail that people think we
can fix and that the only difference between this use and the ones people
think we can't change is where they got invented and by who[1].

What really needs to happen is that the external body mechanism needs to be
integrated into the virus scanning mechanism and both have to support use
of digital signatures so that senders can be appropriately whitelisted.

At the moment the mail systems make no distinction between someone outside
my company sending me a ZIP file and me sending a ZIP file to my engineers.
That is due to the mail protocols being defective.

Maybe the value of DMARC lies in that it will impose some pain on the
community that has the ability to make changes to the mail system for a
change.


[1] Strictly speaking it 'should' be whom but I think that particular word
has been de facto deprecated.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jun 13, 2014 at 9:51 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Jun 13, 2014, at 9:41 AM,=
 Tony Finch &lt;<a href=3D"mailto:dot@dotat.at">dot@dotat.at</a>&gt; wrote:=
<br>

&gt; BUT! These systems do not use the MIME external body mechanism, becaus=
e it<br>
&gt; is common for mail servers to reject these messages on the grounds tha=
t<br>
&gt; they are too difficult to properly scan for viruses.<br>
&gt;<br>
&gt; The end result is something pretty simiilar to MIME external bodies, b=
ut<br>
&gt; a complete mess from the protocol architecture point of view.<br>
<br>
</div>Ouch. =C2=A0 Yet another reason why a flag day may be necessary to im=
prove the situation.<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Now I will note tha=
t this is the sort of use of mail that people think we can fix and that the=
 only difference between this use and the ones people think we can&#39;t ch=
ange is where they got invented and by who[1].</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">What really=
 needs to happen is that the external body mechanism needs to be integrated=
 into the virus scanning mechanism and both have to support use of digital =
signatures so that senders can be appropriately whitelisted.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">At the mome=
nt the mail systems make no distinction between someone outside my company =
sending me a ZIP file and me sending a ZIP file to my engineers. That is du=
e to the mail protocols being defective.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Maybe the v=
alue of DMARC lies in that it will impose some pain on the community that h=
as the ability to make changes to the mail system for a change.</div><div c=
lass=3D"gmail_extra">
<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">[=
1] Strictly speaking it &#39;should&#39; be whom but I think that particula=
r word has been de facto deprecated.</div></div>

--f46d0442685acfb6c504fbb8ec53--


From nobody Fri Jun 13 08:03:57 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47FE21A02ED for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 08:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Xb0-_WU6KZWd for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 08:03:53 -0700 (PDT)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f40]) (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 52BE51A0132 for <ietf@ietf.org>; Fri, 13 Jun 2014 08:03:53 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:46427) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WvT14-0006Xs-lC (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 13 Jun 2014 16:03:42 +0100
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WvT14-00063a-Ge (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 13 Jun 2014 16:03:42 +0100
Date: Fri, 13 Jun 2014 16:03:42 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Change the mailing list protocol, not DMARC.
In-Reply-To: <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1406131600440.3035@hermes-1.csi.cam.ac.uk>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk> <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com> <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7daTRBFr-yFvNsThCQ2Mc_rREwc
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 15:03:55 -0000

Phillip Hallam-Baker <phill@hallambaker.com> wrote:
>
> At the moment the mail systems make no distinction between someone outside
> my company sending me a ZIP file and me sending a ZIP file to my engineers.
> That is due to the mail protocols being defective.

No, that's poor configuration by your postmasters. It's straightforward
and quite common to configure distinct security policies for internal and
external mail, based on whether the message arrived via your submission
service or your MX service.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Humber: Northwest, veering northeast, 3 or 4. Smooth, becoming slight or
moderate. Fog patches for a time. Moderate or good, occasionally very poor.


From nobody Fri Jun 13 08:06:09 2014
Return-Path: <stephen@xemacs.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303911A035E; Thu, 12 Jun 2014 17:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.609
X-Spam-Level: 
X-Spam-Status: No, score=0.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265] autolearn=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 sFeT6DW-myWv; Thu, 12 Jun 2014 17:11:49 -0700 (PDT)
Received: from mgmt1.sk.tsukuba.ac.jp (mgmt1.sk.tsukuba.ac.jp [130.158.97.223]) by ietfa.amsl.com (Postfix) with ESMTP id 815A71A0328; Thu, 12 Jun 2014 17:11:49 -0700 (PDT)
Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt1.sk.tsukuba.ac.jp (Postfix) with ESMTP id BC7363FA0B1E; Fri, 13 Jun 2014 09:11:48 +0900 (JST)
Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id AE94E1A32C5; Fri, 13 Jun 2014 09:11:48 +0900 (JST)
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
In-Reply-To: <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>
X-Mailer: VM undefined under 21.5  (beta34) "kale" acf1c26e3019 XEmacs Lucid (x86_64-unknown-linux)
Date: Fri, 13 Jun 2014 09:11:48 +0900
Message-ID: <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eah11A4KIuM_4YWPRK8qi3sBu8I
X-Mailman-Approved-At: Fri, 13 Jun 2014 08:05:59 -0700
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 00:11:55 -0000

Phillip Hallam-Baker writes:

 > My point is that mail is an old protocol and people who expect that
 > it can be kept going unaltered in its original form serving all the
 > purposes that it was never designed for but have emerged over time
 > are going to be upset no matter what.

True, as far as it goes.  However, there is need for a push protocol
that allows you to receive contacts from authors you don't know yet,
in other words, a medium that is designed to be flexible enough to
accomodate new modes of communication.

It's not obvious to me that this need can be satisfied while at the
same time denying spam.  If it is indeed impossible, I don't see why
that purpose can't continue to be served by email, while most mail
(which is correspondence among acquaintances) gets redirected into
authenticated channels.


From nobody Fri Jun 13 09:58:00 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738401B27DF for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 09:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 XYBKPUtXAi1s for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 09:57:58 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D5AC1B27AE for <ietf@ietf.org>; Fri, 13 Jun 2014 09:57:58 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id q59so3019539wes.26 for <ietf@ietf.org>; Fri, 13 Jun 2014 09:57:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jIvTfCDEsYAYPcyYefLk/waVWsqfo7cIpM4502XogUI=; b=M4nnFjsexBl5Djaw2r1BoMce4tjlMSFFQNRxppZ6FyZlbvkvAyJ0SRRJ6n4KtKHJSN Rbp4s816ErY40+E2NYqjaGepyJbCFanXf+uym4j+60wEUBQ7ElPByoXmGL8OhAihjzTs UoGrU60cQukezyoiM5Ji+75KPEws35VpmHneLO3TSwnj8XLFDIlgJKO72SpdFiVn2EJH QuShI8SfN4603TT51HkBsjYA3RMWXaqTq+8SW4Go4bdSrOk4JJ8ZlAwOfPzMRYXrvlBP 4wW1WIlDUJ/7j5rw7MkyFDvLmZYj321QcRCR1S9qJe2bhCUjawsASYToDOddQ1tnD5df TDKA==
MIME-Version: 1.0
X-Received: by 10.194.175.106 with SMTP id bz10mr6017235wjc.96.1402678676945;  Fri, 13 Jun 2014 09:57:56 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Fri, 13 Jun 2014 09:57:56 -0700 (PDT)
In-Reply-To: <alpine.LSU.2.00.1406131600440.3035@hermes-1.csi.cam.ac.uk>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk> <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com> <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com> <alpine.LSU.2.00.1406131600440.3035@hermes-1.csi.cam.ac.uk>
Date: Fri, 13 Jun 2014 12:57:56 -0400
X-Google-Sender-Auth: UVhvMjg3eEShPEYN4SqE9TZL2Zk
Message-ID: <CAMm+Lwi1eX_krQ9ir6vJfr1Czv_-W_S=5qdAvAWSno8ufHVu1A@mail.gmail.com>
Subject: Re: Change the mailing list protocol, not DMARC.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Tony Finch <dot@dotat.at>
Content-Type: multipart/alternative; boundary=089e01419d9246044d04fbba94d8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FBVyzzYDnaCRAvMnrtUtmX32_8o
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 16:57:59 -0000

--089e01419d9246044d04fbba94d8
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 13, 2014 at 11:03 AM, Tony Finch <dot@dotat.at> wrote:

> Phillip Hallam-Baker <phill@hallambaker.com> wrote:
> >
> > At the moment the mail systems make no distinction between someone
> outside
> > my company sending me a ZIP file and me sending a ZIP file to my
> engineers.
> > That is due to the mail protocols being defective.
>
> No, that's poor configuration by your postmasters. It's straightforward
> and quite common to configure distinct security policies for internal and
> external mail, based on whether the message arrived via your submission
> service or your MX service.
>
>
Actually it is quite a bit more complicated than that and has to do with
being a security company and the difference between what we think is
correct and what we can prove to our auditors at reasonable cost.

--089e01419d9246044d04fbba94d8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jun 13, 2014 at 11:03 AM, Tony Finch <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dot@dotat.at" target=3D"_blank">dot@dotat.at</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">Phillip Hallam-Baker &lt;<a =
href=3D"mailto:phill@hallambaker.com">phill@hallambaker.com</a>&gt; wrote:<=
br>
&gt;<br>
&gt; At the moment the mail systems make no distinction between someone out=
side<br>
&gt; my company sending me a ZIP file and me sending a ZIP file to my engin=
eers.<br>
&gt; That is due to the mail protocols being defective.<br>
<br>
</div>No, that&#39;s poor configuration by your postmasters. It&#39;s strai=
ghtforward<br>
and quite common to configure distinct security policies for internal and<b=
r>
external mail, based on whether the message arrived via your submission<br>
service or your MX service.<br>
<div class=3D""><br></div></blockquote><div><br></div><div>Actually it is q=
uite a bit more complicated than that and has to do with being a security c=
ompany and the difference between what we think is correct and what we can =
prove to our auditors at reasonable cost.</div>
</div></div></div>

--089e01419d9246044d04fbba94d8--


From nobody Fri Jun 13 11:06:36 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB351A0201; Fri, 13 Jun 2014 11:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.881
X-Spam-Level: 
X-Spam-Status: No, score=-2.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 L_12thP06tOl; Fri, 13 Jun 2014 11:06:28 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id D20A71B293A; Fri, 13 Jun 2014 11:06:28 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E746FCC0AD; Fri, 13 Jun 2014 14:06:27 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KQJPbT39TDms; Fri, 13 Jun 2014 14:06:19 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 17CF2CC08E; Fri, 13 Jun 2014 14:06:19 -0400 (EDT)
Message-ID: <539B3D9A.7040104@meetinghouse.net>
Date: Fri, 13 Jun 2014 14:06:18 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com>	<20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp>	<CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com>	<87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp>	<539AE6AD.9090601@meetinghouse.net> <CAMm+Lwhi+7o-GYa7Y4U-iZ=jyWX+rE4nWHrV83csO-qQOCxTVw@mail.gmail.com>
In-Reply-To: <CAMm+Lwhi+7o-GYa7Y4U-iZ=jyWX+rE4nWHrV83csO-qQOCxTVw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_6eCoTuGglRAhXd_tTSXKAufxJo
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 18:06:31 -0000

Phillip Hallam-Baker wrote:
>
>
>
> On Fri, Jun 13, 2014 at 7:55 AM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Stephen J. Turnbull wrote:
>
>         Phillip Hallam-Baker writes:
>
>           > My point is that mail is an old protocol and people who
>         expect that
>           > it can be kept going unaltered in its original form
>         serving all the
>           > purposes that it was never designed for but have emerged
>         over time
>           > are going to be upset no matter what.
>
>         True, as far as it goes.  However, there is need for a push
>         protocol
>         that allows you to receive contacts from authors you don't
>         know yet,
>         in other words, a medium that is designed to be flexible enough to
>         accomodate new modes of communication.
>
>         It's not obvious to me that this need can be satisfied while
>         at the
>         same time denying spam.  If it is indeed impossible, I don't
>         see why
>         that purpose can't continue to be served by email, while most mail
>         (which is correspondence among acquaintances) gets redirected into
>         authenticated channels.
>
>     Just a quick reminder here:  Postal mail is still going strong,
>     after 100s of years.
>
>
> Only because we haven't got email security properly sorted.
>
> I can't remember the last time I received a real letter. All I get is 
> junk mail and bills. And the bills arrive because we haven't got the 
> standards for doing it electronically established yet.

Bills are "real" - they're transactional.  So are checks.  Some of us 
actually do things like send proposals, signed contracts, and so forth.  
And, of course, packages.  And the higher the value, the more likely 
that they'll be sent via physical mail.  It ain't going away anytime soon.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Jun 13 11:25:49 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8BA1B29C3 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.753
X-Spam-Level: 
X-Spam-Status: No, score=-0.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_SUBJECT=1.799, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 lJi-4tRrsxus for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:25:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B5871B29CE for <ietf@ietf.org>; Fri, 13 Jun 2014 11:25:44 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED88F20028 for <ietf@ietf.org>; Fri, 13 Jun 2014 14:29:25 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 7066263B0E; Fri, 13 Jun 2014 14:25:43 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5E51063B0B for <ietf@ietf.org>; Fri, 13 Jun 2014 14:25:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Date: Fri, 13 Jun 2014 14:25:43 -0400
Message-ID: <22740.1402683943@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o0yl-GT8Ps-7HlF1_BeXaF5xe0I
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 18:25:47 -0000

Reply-To mcr+nomcom@sandelman.ca

Subject: third call: NomCom 2014-2015 Call for Volunteers
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub#
 z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
FCC: +ietf/nomcom/nomcom2014
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
--------
--=-=-=


This is the third call for volunteers.
VOLUNTEER NOW: we need to make 200.
The DEADLINE is June 26 to volunteer.

The IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

If your name is on the below, then you have volunteered and are qualified.
In addition to those who volunteered by email, it also includes those who
indicated their willingness to serve on the IETF90 registration form, and
whose eligibility has been confirmed.  54 people were confirmed to be
eligible, and 70 people were not confirmed based upon the email they have
used to register.   Those 124 people have been contacted directly.

If you have heard from me, but are not on the list, then there is some
problem, and you should have gotten a query from me to determine your
eligibility.

If you have volunteered and not heard from him, then please resend;
it got lost.

Ten voting members for the nomcom are selected in a verifiably random
way from a pool of volunteers. The more volunteers, the better chance we have
of choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!
We are at 123 volunteers so far, and WE NEED TO HAVE 200!!!

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
         86(Orlando),       \
         87(Berlin),         *** ANY THREE!
         88(Vancouver),     /
         89(London)        /

If you qualify, please volunteer.   However, much as we want this, before you
decide to volunteer, please be sure you are willing to forgo appointment
to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
There will be activities to collect requirements from the community, review
candidate questionnaires, review feedback from community members about
candidates, and talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is also
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct interviews.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following 4 lines the email body (it is simplest
if you just include the info);

Your Full Name
Emails used to register
Telephone
Current Primary Affiliation

You should expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive this response,
please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider
that nomcom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
    https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details
of the randomness seeds to be used for the RFC 3797 selection process,
within the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in alphabetical order by first name
ANM Zaheduzzaman Sarker
Adam Montville
Ari Ker?nen
Benson Schliesser
Bhumip Khasnabish
Bill VerSteeg
Carl Williams
Carlos Martinez
Charles Eckel
Charles Perkins
Christer Holmberg
Craig White
DHRUV DHODY
Dacheng Zhang
Damien Saucez
Dapeng Liu
Dean Bogdanovic
Dimitri Papadimitriou
Donald Eastlake
Edward Crabbe
Emil Ivov
Eric Rescorla
Eric VYNCKE
Fangwei Hu
Fatai Zhang
Fernando Gont
Fred Baker
Giles Heron
Gonzalo Salgueiro
Gregory Mirsky
Hannes Gredler
Hongyu Li
Hosnieh Rafiee
Hugo Salgado
Hui Deng
Iuniana Oprescu
Jeff Tantsura
John Drake
John Jason Brzozowski
John Levine
John Scudder
Jon Hudson
Jon Mitchell
Karen O'Donoghue
Karen Seo
Kaveh Ranjbar
Klaas Wierenga
Larry Masinter
Lars Eggert
Lee Howard
Lei Zhu
Li Xue
Linda Dunbar
Lingli Deng
Louis (Lou) Berger
Luca Martini
Lucy Lynch
Lucy Yong
Luigi Iannone
Mach Chen
Marcelo Bagnulo
Mark Townsley
Matt Lepinski
Matthew Bocci
Mehmet Ersue
Melinda Shore
Michael Jones
Min Ye
Mingui Zhang
Ning Zong
Ole Troan
Pascal Thubert
Paul Hoffman
Peter Lothberg
Peter Yee
QIN WU
Ralph Droms
Ron Bonica
Ross Callon
Ross Finlayson
Russ White
Sam K. Aldrin
Samuel Weiler
Sandeep Kumar
Sanjay Mishra
Scott Mansfield
Sheng JIANG
Shucheng Liu
Simon Pietro Romano
Stan Ratliff
Stephan Friedl
Stephan Wenger
Stephen Kent
Stewart Bryant
Stig Venaas
Suhas Nandakumar
Suresh Krishnan
Susan Hares
Thomas Walsh
Tim Wicinski
Tissa Senevirathne
Toerless Eckert
Tony Hansen
Ulrich Herberg
Varun Singh
Wassim Haddad
Xiaohu XU
Yi Zhao
Yizhou Li
Yong Cui
Yuanlong Jiang
Yunfei Zhang
Zhaohui Zhang
Zhen Cao
iuniana oprescu


--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU5tCJYCLcPvd0N1lAQIZ6Qf+PzxfY9N/wqNSk9XreMXJr6Km3K5OC4M4
faPA7vMRKQoe/V8eItwX8xMOVRt9LXUXGF0tJOkvJrR9Wdd24p9l0cj9U8dTXwGz
UmvGJH5nDZD5E+PMTAQwuyHO+zXdnzZIE7BskwbStMvO6MIFGEy31v1ML8V7Luk7
xD0Nm+xrg3w9HXbEP8ljpFJyVF0GRZFOUByi+wPhNvMoLAwiwF6mm4i3IlnRIJ/d
dRBEtefdf+9sCe2gRZqeZhOkBVOYzxt4Mqcr+0p8snPVq2RqG9Pg7wsx9cxJsbMV
Rp9iU9g4+uIgXx8YiyT+F6+UemQwIxgcEqQOU8HAiAErpOgfmboG/g==
=VUot
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun 13 11:49:41 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 982671B29F4 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level: 
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_62=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 0KSF6TfT3FZt for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:49:36 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CBA01B29F1 for <ietf@ietf.org>; Fri, 13 Jun 2014 11:49:36 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1EA772002B for <ietf@ietf.org>; Fri, 13 Jun 2014 14:53:17 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 79B9463B0E; Fri, 13 Jun 2014 14:49:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5A65F63B0B for <ietf@ietf.org>; Fri, 13 Jun 2014 14:49:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: third call: NomCom 2014-2015 Call for Volunteers (version 2.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 13 Jun 2014 14:49:31 -0400
Message-ID: <27940.1402685371@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/R82wq6vCd1r2TrnkD_qnBA5_he8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mcr+nomcom@sandelman.ca
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 18:49:39 -0000

<#secure method=pgpmime mode=sign>

This is the third call for volunteers.
(appologies for duplication: there are unresolved
datatracker<->lists.ietf.org issues with the automatic tool)

This message also differs in that the list of volunteers has grown
slightly since attempts to post earlier today, and some duplicates removed.

VOLUNTEER NOW: we need to make 200.
The DEADLINE is June 26 to volunteer.

The IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

If your name is on the below, then you have volunteered and are qualified.
In addition to those who volunteered by email, it also includes those who
indicated their willingness to serve on the IETF90 registration form, and
whose eligibility has been confirmed.
The total is up to 118 people confirmed.

An additional 60 people who volunteered on the registration form have
yet to confirmed as eligible, and have been contacted directly.

If you have heard from me, but are not on the list, then there is some
problem, and you should have gotten a query from me to determine your
eligibility.

If you have volunteered and not heard from me, then please resend;it got lost.

Ten voting members for the nomcom are selected in a verifiably random
way from a pool of volunteers. The more volunteers, the better chance we have
of choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!
We are at 118 volunteers so far, and WE NEED TO HAVE 200!!!

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
         86(Orlando),       \
         87(Berlin),         *** ANY THREE!
         88(Vancouver),     /
         89(London)        /

If you qualify, please volunteer.   However, much as we want this, before you
decide to volunteer, please be sure you are willing to forgo appointment
to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
There will be activities to collect requirements from the community, review
candidate questionnaires, review feedback from community members about
candidates, and talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is also
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct interviews.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following 4 lines the email body (it is simplest
if you just include the info);

Your Full Name
Emails used to register
Telephone
Current Primary Affiliation

You should expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive this response,
please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider
that nomcom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
    https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details
of the randomness seeds to be used for the RFC 3797 selection process,
within the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in alphabetical order by first name
ANM Zaheduzzaman Sarker
Adam Montville
Ari Ker?nen
Benson Schliesser
Bhumip Khasnabish
Bill VerSteeg
Carl Williams
Carlos Martinez
Charles Eckel
Charles Perkins
Christer Holmberg
Craig White
DHRUV DHODY
Dacheng Zhang
Damien Saucez
Dapeng Liu
Dean Bogdanovic
Dimitri Papadimitriou
Donald Eastlake
Edward Crabbe
Emil Ivov
Eric Rescorla
Eric VYNCKE
Fangwei Hu
Fatai Zhang
Fernando Gont
Fred Baker
Giles Heron
Gonzalo Salgueiro
Gregory Mirsky
Hannes Gredler
Hongyu Li
Hosnieh Rafiee
Hugo Salgado
Hui Deng
Iuniana Oprescu
Jeff Tantsura
John E Drake
John Jason Brzozowski
John Levine
John Scudder
Jon Hudson
Jon Mitchell
Joseph Abley
Karen O'Donoghue
Karen Seo
Kaveh Ranjbar
Klaas Wierenga
Kostas Pentikousis
Larry Masinter
Lars Eggert
Lee Howard
Lei Zhu
Li Xue
Linda Dunbar
Lingli Deng
Louis (Lou) Berger
Luca Martini
Lucy Lynch -900
Lucy Yong
Luigi Iannone
Mach Chen
Mahesh Jethanandani
Marcelo Bagnulo
Mark Townsley
Matt Lepinski
Matthew Bocci
Mehmet Ersue
Melinda Shore
Michael Jones
Min Ye
Mingui Zhang
Ning Zong
Ole Troan
Pascal Thubert
Paul Hoffman
Peter Lothberg
Peter Yee
QIN WU
Ralph Droms
Ron Bonica
Ross Callon
Ross Finlayson
Russ White
Sam K. Aldrin
Samuel Weiler
Sandeep Kumar
Sanjay Mishra
Scott Mansfield
Sheng JIANG
Shucheng Liu
Simon Pietro Romano
Stan Ratliff
Stephan Friedl
Stephan Wenger
Stephen Kent
Stewart Bryant
Stig Venaas
Suhas Nandakumar
Suresh Krishnan
Susan Hares
Thomas Walsh
Tim Wicinski
Tissa Senevirathne
Toerless Eckert
Tony Hansen
Ulrich Herberg
Varun Singh
Wassim Haddad
Xiaohu XU
Yi Zhao
Yizhou Li
Yong Cui
Yuanlong Jiang
Yunfei Zhang
Zhaohui Zhang
Zhen Cao
iuniana oprescu


From nobody Fri Jun 13 17:02:21 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A561B2A5A for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 17:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, SPF_PASS=-0.001] autolearn=unavailable
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 QB6rsF-OenG0 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 17:02:17 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E4541B2993 for <ietf@ietf.org>; Fri, 13 Jun 2014 17:02:17 -0700 (PDT)
Received: by mail-ig0-f169.google.com with SMTP id a13so2099776igq.4 for <ietf@ietf.org>; Fri, 13 Jun 2014 17:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HKWIP61bonfWmUhLRG1Rn/8MtARy0rY+nJ7+z7f85xg=; b=kvYBO7Aey5INDKLmMobFLZ0e5hKvtaCq7elYGUXf26IwrhAp52m7veMusKINHzcOvm i2vujEvEH1KNJsXCAcaYAl4/iqcPYrkPCAD1YkU+8u8xWFikZCN68tA3zpG45zsMRF2O J9Ijftt1GDEeeWf/YTNfMDOkKgmS+HfIDoZcY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=HKWIP61bonfWmUhLRG1Rn/8MtARy0rY+nJ7+z7f85xg=; b=mQXU1cGyzLx4f8wohIdDr9f3CgeEpdA5IYWNWIIh/VIGA0A8Qi5jY8chuh4lUhTV1Y 4ZgmstBX4yrp8sdmKzYwAm3SM4LwWOt7icvi06JD7o0wA7NDUUfOMQeb4tX9gRgIV2FF nD02tTzPnKCNuber09/RmezZimZdX2TNc+IAndF6kyQcEkKq8cbqS4vlgo2+FRWhTgtW 1DL1EfwJLcWgTe5VOYfFmx8zc/+3k7Qu4HMFbD/OnVrQt9Lp9V/81TLos7iQvGcEQSbo vJnvQdefFwzqexglmqZtYfQ3PgEeKXyDUt8KK2rnL9s9h843A/MeiE6XsBJmjZJx5ETF QUGQ==
X-Gm-Message-State: ALoCoQlqKftyLzku5vzBG+weCHwmPuB18X9pQnHoRYiueGzRWBUw7/esa7cELD+8O3pctrov0B7m
X-Received: by 10.42.68.204 with SMTP id y12mr6678812ici.16.1402704136661; Fri, 13 Jun 2014 17:02:16 -0700 (PDT)
Received: from [199.212.90.59] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id m1sm6886681ige.22.2014.06.13.17.02.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 17:02:15 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <539AE6AD.9090601@meetinghouse.net>
Date: Fri, 13 Jun 2014 20:02:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1747C4BD-F9E3-4D91-981D-27F38F86E672@hopcount.ca>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp> <539AE6AD.9090601@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OE7Jl_1Gs3dbxhPBs0xnCsWckpc
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 00:02:18 -0000

On 13 Jun 2014, at 7:55, Miles Fidelman <mfidelman@meetinghouse.net> =
wrote:

> Just a quick reminder here:  Postal mail is still going strong, after =
100s of years.

I don't know what it's like where you live, but here the only thing that =
is keeping the post office afloat is being paid by advertisers to =
deliver unsolicited junk.

"Canada Post has hiked postal rates for regular mail and plans to cut up =
to 8,000 jobs as it phases out urban mail delivery over the next five =
years -- all in a bid to reverse the tide of red ink at the money-losing =
Crown corporation."

"The Crown Corporation predicted this year that Canada Post and its =
subsidiaries would lose $274 million before tax in 2014."

"Still going strong" is not a phrase that resonates with me.


Joe


From nobody Fri Jun 13 23:48:57 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6F111B2B84 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 23:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 R3_vxzUjzEhZ for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 23:48:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF9C01B28CA for <ietf@ietf.org>; Fri, 13 Jun 2014 23:48:53 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Wvhjg-000GoT-HY; Sat, 14 Jun 2014 02:46:44 -0400
Date: Sat, 14 Jun 2014 02:48:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Change the mailing list protocol, not DMARC.
Message-ID: <F906336DD15388D3498C471F@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk> <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com> <CAMm+Lwi0hzy1AWRccqP0LR7L2E3raFAb0YjShHLfvMPc9dHLcg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XWQb6PudopKZrYQGPv5n6qQoTU4
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 06:48:55 -0000

--On Friday, June 13, 2014 10:59 -0400 Phillip Hallam-Baker
<phill@hallambaker.com> wrote:

>...
> What really needs to happen is that the external body
> mechanism needs to be integrated into the virus scanning
> mechanism and both have to support use of digital signatures
> so that senders can be appropriately whitelisted.

And what property of external bodies do you believe would
prohibit implementing external bodies so that incoming material
is buffered and scanned for viruses (and whatever else one wants
to scan things for) the same way any local body part/ attachment
scanned?  Or extending the external body mechanism to support
signatures -- either in the form of verifying that a signature
or hash in the message matches one taken over the external body
or an option and check on a signature attached to the external
body.

Seems to me that, at worst, all either would take would be
defining of a new access type (see Section 5.2.3 of RFC 2046)
that would make some material in the phantom body mandatory to
pay attention to if present.

Not exactly the sort of radical, earthshaking, change that
justifies a claim that the mail system needs to be replaced.

    john


From nobody Sat Jun 14 00:16:44 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943D71A00E2 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 00:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 6RruwP6GB_yv for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 00:16:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A4591A0496 for <ietf@ietf.org>; Sat, 14 Jun 2014 00:16:41 -0700 (PDT)
Received: from [192.168.1.45] (134.194-136-217.adsl-dyn.isp.belgacom.be [217.136.194.134]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s5E7Ftu2004284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 14 Jun 2014 00:16:23 -0700
Message-ID: <539BF66B.3020404@bbiw.net>
Date: Sat, 14 Jun 2014 09:14:51 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Webmail is implementation, not Internet architecture  (was Re: Change the mailing list protocol, not DMARC.)
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com>
In-Reply-To: <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Sat, 14 Jun 2014 00:16:38 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/es2EVW3eah8b17Tm6nhwokpyRe8
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 07:16:42 -0000

On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
> On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin <john-ietf@jck.com
...
>     (2) One of those changes --support for remote body parts-- was
>     incorporated into MIME in its very first version and contains
>     most of the mechanism needed to support what I understand PHB is
>     recommending for PUSH-PULL-PULL.  It has been implemented in
>     several places but has gotten very little traction in the mail
>     sending and receiving community.  IMO, it ought to be incumbent
>     on anyone proposing a different "get notification, then retrieve
>     mail from server" model explain why their ideas will be more
>     successful than that 20-odd-year-old MIME mechanism.
> 
> In a word - WebMail.

This is a classic confusion between software implementation and
operation, vesus networking architecture.

Webmail is nothing more than a particular style of user interface,
integrated into the operations of a particular service.  25-30 years
ago, Einar Stefferud labeled this a "split UI" mode, since part of the
mail user interface runs on the user's platform and part runs on the
server's.  It uses whatever homegrown UI-to-UI protocol the local
operator chooses, but otherwise is nothing but classic Internet Mail
architecture.

It's a useful operating mode, within its limits, which typically
includes requiring full-time connectivity.  As good as user access to
the Internet often is, requiring it all the time, for doing email, is a
pretty serious limitation.

More importantly, it isn't interoperable, in the sense we use the term
in the IETF, since it locks the user into the service provider for
literally everything.

There's no user ability to have a different MUA, different email
storage, different address book, different anything.   By having things
locked into the recipient's own email service provider, there is no way
to distribute out enhancements.

So, for example, there is no way for the /author/ to declare an
attachment as being located somewhere else.


> Updating mail clients is a long and tedious process so it is not
> surprising that updates take a lot of time to percolate through. It was
> 5 years after the initial deployment of MIME before mail clients to
> support it became common. And the first of those that did were actually
> combined mail/NNTP readers.

Truly distributed networking architecture certainly does carry costs,
including costs and delays of making changes.

But we've had a highly siloed world before the Internet and we didn't
much like sticking to it.  That we've moved back to it for many services
is convenient for providers to control their market (and, yes, quickly
provide new features) but it has made the user's world notably more
complex and often less interoperable.

Consider the issue, the next time you want to send someone an instant
message.  Do you send it via SMS, google, facebook, yahoo, skype or --
oh yeah -- aol?  That's a really prime example of the derivative effects
of excessive integration witha provider: combinatorial explosion rather
than seamless Internet integration.

And the view that it is sufficient to have a client which integrates all
the heterogeneous services into a single user interface misses the
operational complexities and lack of interoperability they are living with.


> I don't read all my mail in Webmail, 

Why not.  If it's so wonderful, then why isn't it being used for all
your email?


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sat Jun 14 07:01:41 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152CA1B2882 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 zhCiWRImhOzs for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:01:36 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78FA11B286C for <ietf@ietf.org>; Sat, 14 Jun 2014 07:01:35 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id k14so3860041wgh.30 for <ietf@ietf.org>; Sat, 14 Jun 2014 07:01:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cXrOgSUKC6/4jyk8WxZxWEPOksRizv4ziKiyL6iYHGM=; b=V0kyOQndyjwWNvqaFBIBQQnQaXaEcc3ed2++8AuzIPnhgQ0ta2f6xYd8OpdvWsUMXY RVCvSyKhubuV9BzGuZIPShvPaW3nz64TSdYRFfEJCzCpqRmtb9jhodLI2HbDg7J7gXSI ZUUYE/Eqq++7TR82gka1bfrs/xr8WSgVmjdU2SMUydiko7BpDK1dt14U3TXeRXZNE8Zx iEcOEOHNkGHN38JxtSOZT9bsbKU0h1o2vhvb3B0jK8W+7qIKfedLVMxz0SlPr+MrHr+K LjLZ7S8a3/ZTFvtmM95ozxjdcwXxjyp8fvMOpj/3ympVzP+2GPTCtO7yksT4KMLWpkvx T5IA==
MIME-Version: 1.0
X-Received: by 10.194.24.36 with SMTP id r4mr13097588wjf.39.1402754492479; Sat, 14 Jun 2014 07:01:32 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Sat, 14 Jun 2014 07:01:32 -0700 (PDT)
In-Reply-To: <539BF66B.3020404@bbiw.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net>
Date: Sat, 14 Jun 2014 10:01:32 -0400
X-Google-Sender-Auth: 5CvLPIPX0F8XAyE69ueKxHJJbBU
Message-ID: <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b5d2dea3b422a04fbcc3bd9
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iKV1hjy_HCdujbDTOL91YrXkfvg
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 14:01:38 -0000

--047d7b5d2dea3b422a04fbcc3bd9
Content-Type: text/plain; charset=UTF-8

On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <dcrocker@bbiw.net> wrote:

> On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
> > On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin <john-ietf@jck.com
> ...
> >     (2) One of those changes --support for remote body parts-- was
> >     incorporated into MIME in its very first version and contains
> >     most of the mechanism needed to support what I understand PHB is
> >     recommending for PUSH-PULL-PULL.  It has been implemented in
> >     several places but has gotten very little traction in the mail
> >     sending and receiving community.  IMO, it ought to be incumbent
> >     on anyone proposing a different "get notification, then retrieve
> >     mail from server" model explain why their ideas will be more
> >     successful than that 20-odd-year-old MIME mechanism.
> >
> > In a word - WebMail.
>
> This is a classic confusion between software implementation and
> operation, vesus networking architecture.
>
> Webmail is nothing more than a particular style of user interface,
> integrated into the operations of a particular service.


It is the mode used by the majority of mail users today. Which makes it
rather more than just technology from a deployment point of view.

Of course WebMail is simple, I implemented a version of Webmail in 1993. It
took me less than a week to get it running. Would have taken me a day if
not for the fact that I found the POST method was broken. So it was the
first version of WebMail to be able to send mail.

And yes I am aware of the patent lawsuit. That is why we got into the whole
history bit.


It's a useful operating mode, within its limits, which typically
> includes requiring full-time connectivity.  As good as user access to
> the Internet often is, requiring it all the time, for doing email, is a
> pretty serious limitation.
>

Yes, I invented it and I didn't use it until Gmail launched. WebMail is
only useful with high bandwidth links.

But if you are looking to change the mail system those limits are
irrelevant as they don't stop people using it.




> More importantly, it isn't interoperable, in the sense we use the term
> in the IETF, since it locks the user into the service provider for
> literally everything.
>

Umm, how do you work this one out? I am using gmail right now with my
phill@hallambaker.com address.




> There's no user ability to have a different MUA, different email
> storage, different address book, different anything.


Perhaps you should look at something before you speak about it. You are
completely wrong about all of those. In fact most MUA these days have
specific handling to integrate with gmail, yahoo, etc.




> By having things
> locked into the recipient's own email service provider, there is no way
> to distribute out enhancements.
>
> So, for example, there is no way for the /author/ to declare an
> attachment as being located somewhere else.
>

Software authors have been declaring IETF approved features junk and
refusing to implement them for years.

The fact that the mail providers don't snap to attention and implement a
feature because it is agreed by an IETF committee does not mean that they
will never implement it. Who proposes the feature and what they do to get
it deployed makes the difference.

Another thing that makes the difference is time and situation. I invented
WebMail in 1993 but Gmail didn't launch till 2004. And it was the
combination of high bandwidth, generous storage allowances and the fact
Javascript no longer crashed after three seconds that made modern WebMail
possible.


Consider the issue, the next time you want to send someone an instant
> message.  Do you send it via SMS, google, facebook, yahoo, skype or --
> oh yeah -- aol?  That's a really prime example of the derivative effects
> of excessive integration witha provider: combinatorial explosion rather
> than seamless Internet integration.
>

Well maybe the reason that problem hasn't been addressed is that too many
people take notice of the people whose only function is to tell them that
something can't be done, won't work, etc.

It was thirty years from the start of project Xanadu to the birth of the
web. Plenty of people thought it impossible




> And the view that it is sufficient to have a client which integrates all
> the heterogeneous services into a single user interface misses the
> operational complexities and lack of interoperability they are living with.
>
>
> > I don't read all my mail in Webmail,
>
> Why not.  If it's so wonderful, then why isn't it being used for all
> your email?


Same reason that I use Linux, Windows and Mac every single day. Same reason
I have three different home automation systems in my house. Same reason I
just bought a 3D mill kit despite the fact that there is a CNC Mill and
Lathe in the basement already.

I don't want to become a technological fossil who is clinging to some
obsolete tool that the market passed by long ago. This is a technology
business, if you want to contribute you have see what is happening in every
part of it.

--047d7b5d2dea3b422a04fbcc3bd9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <span dir=3D"ltr">&lt=
;<a href=3D"mailto:dcrocker@bbiw.net" target=3D"_blank">dcrocker@bbiw.net</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 6/12/2014 6:33 PM, Phillip Hallam-Baker w=
rote:<br>
&gt; On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin &lt;<a href=3D"mailto=
:john-ietf@jck.com">john-ietf@jck.com</a><br>
...<br>
&gt; =C2=A0 =C2=A0 (2) One of those changes --support for remote body parts=
-- was<br>
&gt; =C2=A0 =C2=A0 incorporated into MIME in its very first version and con=
tains<br>
&gt; =C2=A0 =C2=A0 most of the mechanism needed to support what I understan=
d PHB is<br>
&gt; =C2=A0 =C2=A0 recommending for PUSH-PULL-PULL. =C2=A0It has been imple=
mented in<br>
&gt; =C2=A0 =C2=A0 several places but has gotten very little traction in th=
e mail<br>
&gt; =C2=A0 =C2=A0 sending and receiving community. =C2=A0IMO, it ought to =
be incumbent<br>
&gt; =C2=A0 =C2=A0 on anyone proposing a different &quot;get notification, =
then retrieve<br>
&gt; =C2=A0 =C2=A0 mail from server&quot; model explain why their ideas wil=
l be more<br>
&gt; =C2=A0 =C2=A0 successful than that 20-odd-year-old MIME mechanism.<br>
&gt;<br>
&gt; In a word - WebMail.<br>
<br>
This is a classic confusion between software implementation and<br>
operation, vesus networking architecture.<br>
<br>
Webmail is nothing more than a particular style of user interface,<br>
integrated into the operations of a particular service. =C2=A0</blockquote>=
<div><br></div><div>It is the mode used by the majority of mail users today=
. Which makes it rather more than just technology from a deployment point o=
f view.</div>
<div><br></div><div>Of course WebMail is simple, I implemented a version of=
 Webmail in 1993. It took me less than a week to get it running. Would have=
 taken me a day if not for the fact that I found the POST method was broken=
. So it was the first version of WebMail to be able to send mail.</div>
<div><br></div><div>And yes I am aware of the patent lawsuit. That is why w=
e got into the whole history bit.</div><div><br></div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
It&#39;s a useful operating mode, within its limits, which typically<br>
includes requiring full-time connectivity. =C2=A0As good as user access to<=
br>
the Internet often is, requiring it all the time, for doing email, is a<br>
pretty serious limitation.<br></blockquote><div><br></div><div>Yes, I inven=
ted it and I didn&#39;t use it until Gmail launched. WebMail is only useful=
 with high bandwidth links.</div><div><br></div><div>But if you are looking=
 to change the mail system those limits are irrelevant as they don&#39;t st=
op people using it.</div>
<div><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
More importantly, it isn&#39;t interoperable, in the sense we use the term<=
br>
in the IETF, since it locks the user into the service provider for<br>
literally everything.<br></blockquote><div><br></div><div>Umm, how do you w=
ork this one out? I am using gmail right now with my <a href=3D"mailto:phil=
l@hallambaker.com">phill@hallambaker.com</a> address.=C2=A0</div><div><br><=
/div>
<div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There&#39;s no user ability to have a different MUA, different email<br>
storage, different address book, different anything. =C2=A0 </blockquote><d=
iv><br></div><div>Perhaps you should look at something before you speak abo=
ut it. You are completely wrong about all of those. In fact most MUA these =
days have specific handling to integrate with gmail, yahoo, etc.</div>
<div><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">By having things<br>
locked into the recipient&#39;s own email service provider, there is no way=
<br>
to distribute out enhancements.<br>
<br>
So, for example, there is no way for the /author/ to declare an<br>
attachment as being located somewhere else.<br></blockquote><div><br></div>=
<div>Software authors have been declaring IETF approved features junk and r=
efusing to implement them for years.</div><div><br></div><div>The fact that=
 the mail providers don&#39;t snap to attention and implement a feature bec=
ause it is agreed by an IETF committee does not mean that they will never i=
mplement it. Who proposes the feature and what they do to get it deployed m=
akes the difference.=C2=A0</div>
<div><br></div><div>Another thing that makes the difference is time and sit=
uation. I invented WebMail in 1993 but Gmail didn&#39;t launch till 2004. A=
nd it was the combination of high bandwidth, generous storage allowances an=
d the fact Javascript no longer crashed after three seconds that made moder=
n WebMail possible.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Consider the i=
ssue, the next time you want to send someone an instant<br>
message. =C2=A0Do you send it via SMS, google, facebook, yahoo, skype or --=
<br>
oh yeah -- aol? =C2=A0That&#39;s a really prime example of the derivative e=
ffects<br>
of excessive integration witha provider: combinatorial explosion rather<br>
than seamless Internet integration.<br></blockquote><div><br></div><div>Wel=
l maybe the reason that problem hasn&#39;t been addressed is that too many =
people take notice of the people whose only function is to tell them that s=
omething can&#39;t be done, won&#39;t work, etc.</div>
<div><br></div><div>It was thirty years from the start of project Xanadu to=
 the birth of the web. Plenty of people thought it impossible</div><div><br=
></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

And the view that it is sufficient to have a client which integrates all<br=
>
the heterogeneous services into a single user interface misses the<br>
operational complexities and lack of interoperability they are living with.=
<br>
<br>
<br>
&gt; I don&#39;t read all my mail in Webmail,<br>
<br>
Why not. =C2=A0If it&#39;s so wonderful, then why isn&#39;t it being used f=
or all<br>
your email?</blockquote><div><br></div><div>Same reason that I use Linux, W=
indows and Mac every single day. Same reason I have three different home au=
tomation systems in my house. Same reason I just bought a 3D mill kit despi=
te the fact that there is a CNC Mill and Lathe in the basement already.</di=
v>
<div><br></div><div>I don&#39;t want to become a technological fossil who i=
s clinging to some obsolete tool that the market passed by long ago. This i=
s a technology business, if you want to contribute you have see what is hap=
pening in every part of it.</div>
</div></div></div>

--047d7b5d2dea3b422a04fbcc3bd9--


From nobody Sat Jun 14 07:40:37 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6E61B2914 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 hXIRYO7iTAQJ for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:40:33 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 608E51B2911 for <ietf@ietf.org>; Sat, 14 Jun 2014 07:40:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 72DD0CC082 for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:32 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KFun6M-txNpR for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:23 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A91E2CC07F for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:23 -0400 (EDT)
Message-ID: <539C5ED6.7080708@meetinghouse.net>
Date: Sat, 14 Jun 2014 10:40:22 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
CC: IETF <ietf@ietf.org>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
In-Reply-To: <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TE-2fhx8_5G_lYxB9IV8HAOQ4D0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 14:40:35 -0000

Phillip Hallam-Baker wrote:
>
> On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <dcrocker@bbiw.net 
> <mailto:dcrocker@bbiw.net>> wrote:
>
>     On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
>     > On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin
>     <john-ietf@jck.com <mailto:john-ietf@jck.com>
>     ...
>     >     (2) One of those changes --support for remote body parts-- was
>     >     incorporated into MIME in its very first version and contains
>     >     most of the mechanism needed to support what I understand PHB is
>     >     recommending for PUSH-PULL-PULL.  It has been implemented in
>     >     several places but has gotten very little traction in the mail
>     >     sending and receiving community.  IMO, it ought to be incumbent
>     >     on anyone proposing a different "get notification, then retrieve
>     >     mail from server" model explain why their ideas will be more
>     >     successful than that 20-odd-year-old MIME mechanism.
>     >
>     > In a word - WebMail.
>
>     This is a classic confusion between software implementation and
>     operation, vesus networking architecture.
>
>     Webmail is nothing more than a particular style of user interface,
>     integrated into the operations of a particular service. 
>
>
> It is the mode used by the majority of mail users today. Which makes 
> it rather more than just technology from a deployment point of view.

That's almost certainly not true, or it's certainly highly questionable.

Two words:
1. Outlook
2. Smartphones


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sat Jun 14 07:49:43 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC25F1B2878 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 rg0jC6MJ7iOn for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:49:38 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBCB1B291E for <ietf@ietf.org>; Sat, 14 Jun 2014 07:49:38 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P8ZV7R8GZK004ZZI@mauve.mrochek.com> for ietf@ietf.org; Sat, 14 Jun 2014 07:44:31 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P8UD4AOU8W0049PU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 14 Jun 2014 07:44:23 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P8ZV7PHO8M0049PU@mauve.mrochek.com>
Date: Sat, 14 Jun 2014 07:42:09 -0700 (PDT)
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
In-reply-to: "Your message dated Sat, 14 Jun 2014 10:40:22 -0400" <539C5ED6.7080708@meetinghouse.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fcvTkQUhhKoy3QUvinWQT8dv6Yw
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 14:49:40 -0000

> Phillip Hallam-Baker wrote:
> >
> > On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <dcrocker@bbiw.net
> > <mailto:dcrocker@bbiw.net>> wrote:
> >
> >     On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
> >     > On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin
> >     <john-ietf@jck.com <mailto:john-ietf@jck.com>
> >     ...
> >     >     (2) One of those changes --support for remote body parts-- was
> >     >     incorporated into MIME in its very first version and contains
> >     >     most of the mechanism needed to support what I understand PHB is
> >     >     recommending for PUSH-PULL-PULL.  It has been implemented in
> >     >     several places but has gotten very little traction in the mail
> >     >     sending and receiving community.  IMO, it ought to be incumbent
> >     >     on anyone proposing a different "get notification, then retrieve
> >     >     mail from server" model explain why their ideas will be more
> >     >     successful than that 20-odd-year-old MIME mechanism.
> >     >
> >     > In a word - WebMail.
> >
> >     This is a classic confusion between software implementation and
> >     operation, vesus networking architecture.
> >
> >     Webmail is nothing more than a particular style of user interface,
> >     integrated into the operations of a particular service.
> >
> >
> > It is the mode used by the majority of mail users today. Which makes
> > it rather more than just technology from a deployment point of view.

> That's almost certainly not true, or it's certainly highly questionable.

> Two words:
> 1. Outlook
> 2. Smartphones

Some data to support this conclusion:

   http://emailclientmarketshare.com/

				Ned


From nobody Sat Jun 14 08:26:39 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B761B293B for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 MZWI7w9yvzCO for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:26:37 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0F291A038B for <ietf@ietf.org>; Sat, 14 Jun 2014 08:26:37 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so3777547wgh.26 for <ietf@ietf.org>; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PbilKTiYCKcY6JFrjoP7O9h83HQsK5pH2vmvfuMmmzA=; b=Hz/mGLBEzN7ziH5EP787zxXxX9TFXRgVY8+8Jy8Ucoys+USnF9UpxtVOqiIbsn49ca NXtDO6T7BF/pm+Hh+9SjBZ6WxEVWKQpd4sWzURxzqZxCWoIDfCnXrgVJP3ogMRFVgkew oL5bEoq91ZsjNYHi3UOC4+6DNBc3UtCgBU9PZQSIgnOthxAHSPWvsPDvtEQWrN1HOuXd K7q2j9uo6g57jmP2vlNAeLzSEJGJ24TVQFXYjjGu7d2za3y97MYjP0OmiVQM0PE+D3pj geazDQrH6D4cNP+zcAex5V10s4MJrE+7nT6spaY+3MJNvulITo8jsljs7/NXlI4BTOki Y+jA==
MIME-Version: 1.0
X-Received: by 10.180.207.9 with SMTP id ls9mr13307465wic.32.1402759596084; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
In-Reply-To: <539C5ED6.7080708@meetinghouse.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net>
Date: Sat, 14 Jun 2014 11:26:36 -0400
X-Google-Sender-Auth: Zu-itkNO9giTL_QusF1fVqNSNWk
Message-ID: <CAMm+LwhTtwfFtfXQjha95gY-tp6DQbuwudMg1ZXOBuGuJ7zirA@mail.gmail.com>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a11c3cdc06e15a404fbcd6bea
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pF5jxc55PbCu3k_2LRaer2bShks
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 15:26:39 -0000

--001a11c3cdc06e15a404fbcd6bea
Content-Type: text/plain; charset=UTF-8

On Sat, Jun 14, 2014 at 10:40 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Phillip Hallam-Baker wrote:
>
>>
>> It is the mode used by the majority of mail users today. Which makes it
>> rather more than just technology from a deployment point of view.
>>
>
> That's almost certainly not true, or it's certainly highly questionable.
>
> Two words:
> 1. Outlook
> 2. Smartphones


Well it all depends on whether you measure users or uses. People who use
mail a lot are more likely to use a dedicated client.

But from a deployment point of view smartphones are and always will be
limited lifetime devices because of their mode of use. If Apple adds a new
feature today, 90% of the Apple smartphones in regular use will support it
in three years. Because even if development of phones stops, any device you
carry with you every day is going to see a lot of wear and tear.


But even taking this as a given, it seems that every time that I go to a
blog with a comments form on using my iPhone the provider is trying to push
a 'stream reader' app at me. It might be that these people will only push a
proprietary app but I think it likely that they would be interested in an
open standard if one was on offer.


You may be right of course that change is impossible, it is certainly
difficult. But it does have a better chance of achieving the desired goal
of a decent discussion mechanism that supports the desired capabilities,
access modes, etc. than sitting in the sea and bidding the DMARC tide turn.

--001a11c3cdc06e15a404fbcd6bea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Jun 14, 2014 at 10:40 AM, Miles Fidelman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelman@meetingh=
ouse.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br></div><div class=3D"">
It is the mode used by the majority of mail users today. Which makes it rat=
her more than just technology from a deployment point of view.<br>
</div></blockquote>
<br>
That&#39;s almost certainly not true, or it&#39;s certainly highly question=
able.<br>
<br>
Two words:<br>
1. Outlook<br>
2. Smartphones</blockquote><div><br></div><div>Well it all depends on wheth=
er you measure users or uses. People who use mail a lot are more likely to =
use a dedicated client.</div><div><br></div><div>But from a deployment poin=
t of view smartphones are and always will be limited lifetime devices becau=
se of their mode of use. If Apple adds a new feature today, 90% of the Appl=
e smartphones in regular use will support it in three years. Because even i=
f development of phones stops, any device you carry with you every day is g=
oing to see a lot of wear and tear.</div>
<div><br></div><div><br></div><div>But even taking this as a given, it seem=
s that every time that I go to a blog with a comments form on using my iPho=
ne the provider is trying to push a &#39;stream reader&#39; app at me. It m=
ight be that these people will only push a proprietary app but I think it l=
ikely that they would be interested in an open standard if one was on offer=
.</div>
<div><br></div><div><br></div><div>You may be right of course that change i=
s impossible, it is certainly difficult. But it does have a better chance o=
f achieving the desired goal of a decent discussion mechanism that supports=
 the desired capabilities, access modes, etc. than sitting in the sea and b=
idding the DMARC tide turn.</div>
<div><br></div></div></div></div>

--001a11c3cdc06e15a404fbcd6bea--


From nobody Sat Jun 14 08:30:42 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52981B2943 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ODa5LmaMOwbJ for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:30:39 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C893E1A038B for <ietf@ietf.org>; Sat, 14 Jun 2014 08:30:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1402759836; bh=5bOCB3h8/GkjBsBRLAAnFFtY93m0EXATu89iysXYjYo=; l=3863; h=Date:From:To:References:In-Reply-To; b=byfOpjD7+JzzwVrfjhk6o1sJth8zvxQi/XH9lOeCRl8yi1FbqwWBtRct/9LS+yEYX yID/bNlJt5sGGI2H9xGNyflr3Nh41Rkb5EV4dH+tE6FZIbDZ/oYo0PKN3SYiIqyfkT gdyr/qDfc9hx1wJsZGHDLupDB2rFnJQnMjRTcyzo=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Sat, 14 Jun 2014 17:30:36 +0200 id 00000000005DC033.00000000539C6A9C.000067EE
Message-ID: <539C6A9C.6010707@tana.it>
Date: Sat, 14 Jun 2014 17:30:36 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Webmail is implementation, not Internet architecture  (was Re: Change the mailing list protocol, not DMARC.)
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net>
In-Reply-To: <539BF66B.3020404@bbiw.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/87igoSyajRtA9iphJ7TD4M2LApw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 15:30:40 -0000

On Sat 14/Jun/2014 09:14:51 +0200 Dave Crocker wrote:
> On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
>> On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin <john-ietf@jck.com
> ...
>>     (2) One of those changes --support for remote body parts-- was
>>     incorporated into MIME in its very first version and contains
>>     most of the mechanism needed to support what I understand PHB is
>>     recommending for PUSH-PULL-PULL.  It has been implemented in
>>     several places but has gotten very little traction in the mail
>>     sending and receiving community.  IMO, it ought to be incumbent
>>     on anyone proposing a different "get notification, then retrieve
>>     mail from server" model explain why their ideas will be more
>>     successful than that 20-odd-year-old MIME mechanism.
>> 
>> In a word - WebMail.
> 
> This is a classic confusion between software implementation and
> operation, vesus networking architecture.
> 
> Webmail is nothing more than a particular style of user interface,
> integrated into the operations of a particular service.  25-30 years
> ago, Einar Stefferud labeled this a "split UI" mode, since part of the
> mail user interface runs on the user's platform and part runs on the
> server's.  It uses whatever homegrown UI-to-UI protocol the local
> operator chooses, but otherwise is nothing but classic Internet Mail
> architecture.
> 
> It's a useful operating mode, within its limits, which typically
> includes requiring full-time connectivity.  As good as user access to
> the Internet often is, requiring it all the time, for doing email, is a
> pretty serious limitation.
> 
> More importantly, it isn't interoperable, in the sense we use the term
> in the IETF, since it locks the user into the service provider for
> literally everything.
> 
> There's no user ability to have a different MUA, different email
> storage, different address book, different anything.   By having things
> locked into the recipient's own email service provider, there is no way
> to distribute out enhancements.

I agree with Dave on this point.  His note is especially meaningful
in this thread, because Phillip started it noting that:

On Sat 07/Jun/2014 14:40:50 +0200 Phillip Hallam-baker wrote:
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kvU9-WN7AASUAUpfUCpc__LpLGE
>>>> That is what folk complaining don't get: you don't have the right to
>>>> use your employers email or a public email provider's email any way
>>>> you want. The domain name owner makes the rules.
>>>> 
>>>> As Craster insists: My domain, my rules.

That is the sort of reasoning which is often heard about social
networks, sometimes culminating with someone observing that we should
devise a protocol for generic social sites, so as to avoid being at
the mercy of the provider of the day...

Specifying a protocol is only useful inasmuch as it allows to swap
the underlying implementation.  Webmail, for example, can be
implemented locally using an IMAP backend (e.g. Mailpile).

The issue at hand originates from the fact that protocols, by
definition[1], cover the mechanics rather than the semantics.  DMARC
attempts to ensure the authenticity of an identifier, whose semantics
should provide for accountability.  So, while its enforcement depends
on the ability of receivers to reject (with "considerable care"[2])
its impact and semantics are still left to the community.  Some sort
of training is appropriate, but IETF's voice doesn't seem to be much
heard outside of a restricted circle, which is one of the reasons why
I proposed an online demonstration.

Ale

[1] thread starting in:
 http://www.ietf.org/mail-archive/web/ietf/current/msg71257.html
my observation on semantics was in:
 http://www.ietf.org/mail-archive/web/ietf/current/msg73752.html

[2] http://tools.ietf.org/html/rfc5321#section-7.9


From nobody Sat Jun 14 11:09:06 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AE61A0646 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 11:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 Ork5dH7QfcbF for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 11:09:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B146D1A05CB for <ietf@ietf.org>; Sat, 14 Jun 2014 11:09:01 -0700 (PDT)
Received: from [192.168.1.45] (134.194-136-217.adsl-dyn.isp.belgacom.be [217.136.194.134]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s5EI7nFh021891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 14 Jun 2014 11:08:08 -0700
Message-ID: <539C8F24.9060503@dcrocker.net>
Date: Sat, 14 Jun 2014 20:06:28 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
In-Reply-To: <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 14 Jun 2014 11:08:57 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YsxnQGXcrK_kTNfJOB9BRwtc11Q
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 18:09:03 -0000

On 6/14/2014 4:01 PM, Phillip Hallam-Baker wrote:
> On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <dcrocker@bbiw.net
>     > In a word - WebMail.
> 
>     This is a classic confusion between software implementation and
>     operation, vesus networking architecture.
> 
>     Webmail is nothing more than a particular style of user interface,
>     integrated into the operations of a particular service.  
> 
> It is the mode used by the majority of mail users today. Which makes it
> rather more than just technology from a deployment point of view.

This appears to be claiming that popularity alters whether something is
'technology' or 'architecture' or the like.  For the point I was making,
market penetration statistics are irrelevant.

(There seems to be some confusion in the meaning of the term webmail.  I
have a guess about it's basis later in this note.)

What makes a difference to architecture is architecture.

Webmail is merely a classic centralized time-sharing server approach to
email service, the same as we had from the 1960s (for standalone email
service) and early 1970s (for networked email).  It's prettier and
faster, and perhaps a bit more functional, but architecturally it is
identical.

At base, the term is for marketing siloed email operations that are
accessed through a browser.  Marketing terms can be useful, as can the
services they reference, of course, but they don't have much to do with
technical architecture.


> Of course WebMail is simple, I implemented a version of Webmail in 1993.

I made no comment about technical complexity or its absence.

Siloed operation certainly permits simpler decision-making for the
operator and often permits simpler development for the software folk,
and especially faster cycling of enhancements -- though one would be
hard-pressed to call any of the current, major providers' internal
systems simple...

Change requiring multi-administration coordination is inherently slow
and expensive, but it's the only choice when a service truly is global
and, therefore, subject to the consensus (or lack of it) by many
independent organizations.


>     It's a useful operating mode, within its limits, which typically
>     includes requiring full-time connectivity.  
...
> But if you are looking to change the mail system those limits are
> irrelevant as they don't stop people using it.

The changes are limited to that operator.  Sometimes operators do
wonderful things within their siloed environments.

However if you are creating an interoperable change, it no longer has
anything to do with the term 'webmail', since it has to do with open
protocol standards, whereas 'webmail' has to do with accessing a
centralized service, and either with a raw browser or with a proprietary
active agent downloaded as session start.

See RFC 5598, Figure 5.  If there are architectural/technical
characteristics about 'webmail' that are different from an
implementation approach to the MUA then please provide a technical
description.


>     More importantly, it isn't interoperable, in the sense we use the term
>     in the IETF, since it locks the user into the service provider for
>     literally everything.
> 
> Umm, how do you work this one out? I am using gmail right now with my
> phill@hallambaker.com <mailto:phill@hallambaker.com> address. 

The protocol between the user-side and server-side of the MUA is
proprietary.  The mechanisms for access the message store are (or can
be) proprietary. Same for local access to the MTA.  And best of all: The
user is locked into the operators MUA (as I said before and you missed
responding to.)

My point was not that a proprietary webmail service is unable to
exchange mail with other Internet Mail users, but that the environment
/within/ the webmail service is entirely siloed.  The world of email
evolved to permit quite a bit of choice of operational components, and
webmail services essentially eliminate those choices.

That a user's world is made simpler by having a fully-integrated
operator that downloads the MUA to the browser in real-time is an
obvious and significant benefit for some/many users.  But again, that's
irrelevant to a discussion about email architecture.


>     There's no user ability to have a different MUA, different email
>     storage, different address book, different anything.   
> 
> Perhaps you should look at something before you speak about it. You are
> completely wrong about all of those. In fact most MUA these days have
> specific handling to integrate with gmail, yahoo, etc.

After 40 years of doing email software, servers and standards, its
richness as a playground for technical innovation and human use remain
impressive to me.  I still find some wonder at what there is to learn
about it.

Or perhaps...

What your note confuses is the difference between being an email
operator that might offer web-based access, versus accessing such a
service through other means.

That is, from what I can tell the confusion here is between "webmail" as
a term referring to an access method for service -- where that term does
have some technical merit, given the split UA -- versus use of the term
to cover all aspects of an operator that offers such web-based access,
which moves the use into purely marketing purposes.  Hence it would
imply that all gmail users are webmail users, which of course they aren't.

Restated:  It's possible that you are using the term to refer to any
tightly-integrated operation of MUA, MS, MSA/MDA, and at least one MTA,
where some users gain access through a web browser.  That's certainly
popular way to use the term amongst non-technical folk.

I'm assuming rather more knowledge and care for technical discussion on
an IETF list.  Here, the term webmail only makes sense when referring to
the web-related portion of some users' access, namely through a browser.

Yes, gmail offers web-based access.  And yes, I access my gmail account
through IMAP and Thunderbird.

But the first fact is irrelevant to the second.  There is nothing about
my access that is "webmail" anymore than it is webmail when I use a
different setting in Thunderbird to access my bbiw.net account -- which
I've been lazy about and haven't added web-based access to -- and get
exactly the same type of service as I get from gmail.  IMAP defines the
service semantics and the nature of the window into the remote email store.


>     By having things
>     locked into the recipient's own email service provider, there is no way
>     to distribute out enhancements.
> 
>     So, for example, there is no way for the /author/ to declare an
>     attachment as being located somewhere else.
> 
> Software authors have been declaring IETF approved features junk and
> refusing to implement them for years.

'author' was used in juxtaposition with 'recipient'.  I was/am referring
to message authors, not programmers.


>     Consider the issue, the next time you want to send someone an instant
>     message.  Do you send it via SMS, google, facebook, yahoo, skype or --
>     oh yeah -- aol?  That's a really prime example of the derivative effects
>     of excessive integration witha provider: combinatorial explosion rather
>     than seamless Internet integration.
> 
> Well maybe the reason that problem hasn't been addressed is that too
> many people take notice of the people whose only function is to tell
> them that something can't be done, won't work, etc.

Fascinating.  It would be educational to see the documentation
supporting that claim, especially since I thought the driving forces
were customer capture by the operator and a lack of user demand for
integration.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sat Jun 14 13:14:51 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9441B29BF for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 13:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 CEcrlkiE4E_4 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 13:14:47 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6D9F1B29BD for <ietf@ietf.org>; Sat, 14 Jun 2014 13:14:47 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id g10so537859pdj.28 for <ietf@ietf.org>; Sat, 14 Jun 2014 13:14:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=S42f9B2NJ4mkdxtV5WHoebQkIVf5L/2j2i0W83aIWXo=; b=TRDnoFoIDOYqLh4ymuQE/j53tG/hRrG/iQP3EYU7xVgYSlOw2oqwnwXxhrUUFQ0PeB SMOGhDZQyg7RTf/4hXFNxmAFyw7HBx+jbQwfvQUbHdhhkZQFW3ET9HX3b4z1dpG39io5 +Fn5w2fBgzPtvvOOYIUmXqJiFutdvPltd6vt5DZQgSndnf/WOvVdUZBg0Ns85IJFeTNQ RnlhQW5MjLncW9tbg87szYriwgnvXbyxTN4ttaD0wAj8wYFwwHKtBrt8MI1qbn6rEZ9z tJV1uIP3a7stX2w5lKkSYky6TTp67UmTem+nYBhcHJzW4trweVDu72sc7rjHVF7pzKDf 84WQ==
X-Received: by 10.66.100.200 with SMTP id fa8mr12695067pab.23.1402776887398; Sat, 14 Jun 2014 13:14:47 -0700 (PDT)
Received: from [192.168.178.23] (76.197.69.111.dynamic.snap.net.nz. [111.69.197.76]) by mx.google.com with ESMTPSA id ee5sm10275643pbc.47.2014.06.14.13.14.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 14 Jun 2014 13:14:46 -0700 (PDT)
Message-ID: <539CAD2E.6030805@gmail.com>
Date: Sun, 15 Jun 2014 08:14:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com>
In-Reply-To: <01P8ZV7PHO8M0049PU@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_JWwyLqBg1CrAJh6OpETCwNcvE4
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 20:14:49 -0000

Ned,

On 15/06/2014 02:42, ned+ietf@mauve.mrochek.com wrote:
...
> Some data to support this conclusion:
[that webmail is not dominant]
> 
>   http://emailclientmarketshare.com/

Hmm. I was curious about what those numbers really measure.
Judging by http://litmus.com/email-analytics, it seems that
they refer to a sample of emails that (a) contained a specific
HTML snippet and were (b) opened as HTML by the clients and
(c) by implication, had been sent via a mailing list. It seems
very likely to me that the sample consisted of spam. I'm
not sure that the numbers reflect unbiased statistics, unless
you're a spammer. In any case they don't indicate how many
people open email in plain text mode (which I alway do if
possible, precisely to avoid embedded code).

That said, they certainly show that one size doesn't fit all.

Does anyone have statistics of POP3 vs IMAP vs split-UI?

    Brian




From nobody Sat Jun 14 13:40:04 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 009F21B27FC for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 13:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 0bQ8jKGqSbKW for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 13:39:58 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 12A671A0241 for <ietf@ietf.org>; Sat, 14 Jun 2014 13:39:58 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P907G639EO005DEZ@mauve.mrochek.com> for ietf@ietf.org; Sat, 14 Jun 2014 13:34:50 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P8UD4AOU8W0049PU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 14 Jun 2014 13:34:41 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P907G00ESM0049PU@mauve.mrochek.com>
Date: Sat, 14 Jun 2014 13:21:24 -0700 (PDT)
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
In-reply-to: "Your message dated Sun, 15 Jun 2014 08:14:38 +1200" <539CAD2E.6030805@gmail.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AvVNJlc4sOFR8vmxpDQ5XnsSHUA
Cc: ned+ietf@mauve.mrochek.com, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jun 2014 20:40:03 -0000

> Ned,

> On 15/06/2014 02:42, ned+ietf@mauve.mrochek.com wrote:
> ...
> > Some data to support this conclusion:
> [that webmail is not dominant]
> >
> >   http://emailclientmarketshare.com/

> Hmm. I was curious about what those numbers really measure.
> Judging by http://litmus.com/email-analytics, it seems that
> they refer to a sample of emails that (a) contained a specific
> HTML snippet and were (b) opened as HTML by the clients and
> (c) by implication, had been sent via a mailing list.

Litmus is a service for people who send out bulk mail and want to track
whether or not it's seen, and when it's seen what client is used to see it.

> It seems
> very likely to me that the sample consisted of spam.

Actually, it's unlikely in the extreme. Spammers are into volume, they don't
care about tracking analytics and aren't going to pay a company like Litmus to
perform such a service. But there are a hell of a lot of legitimate bulk email
senders out there who do care about the effectiveness of their mail, and have
the money to pay for such things.

> I'm
> not sure that the numbers reflect unbiased statistics, unless
> you're a spammer. In any case they don't indicate how many
> people open email in plain text mode (which I alway do if
> possible, precisely to avoid embedded code).

Well, I think it's up to you to show that a significant fraction of the
email-reading public prefers to read HTML mail without resolving any of the
links, and that missing out on that fraction significantly biases such data.

> That said, they certainly show that one size doesn't fit all.

Which was the main point.

				Ned



From nobody Sat Jun 14 19:57:27 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F1641B2A85; Sat, 14 Jun 2014 19:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.847
X-Spam-Level: 
X-Spam-Status: No, score=0.847 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 TTp_c70Hgjtj; Sat, 14 Jun 2014 19:57:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1C21B2886; Sat, 14 Jun 2014 19:57:06 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5F2v0YE028756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Jun 2014 22:57:00 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s5F2v0YE028756
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1402801020; bh=z2zGtkehDOoPF3PQcQ/NDTatVTI=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=UpmfkpTneu2+WBMGDevEWaaR+875ANNrKPTRqn//cNubptGwSupmsJorLlFKKNWMO vFxWkaim0xCyIjjrItqxTXXJBJ8utIS4Z24EsJaRJE8cHqkq6qLGYAQIdNloFozPqb RSuHt9ksbN0FMN2gdwGdiGhkWx7Yq3n3MRSv4vzY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s5F2v0YE028756
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd02.lss.emc.com (RSA Interceptor); Sat, 14 Jun 2014 22:56:45 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5F2uj0R022962 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 14 Jun 2014 22:56:45 -0400
Received: from mx15a.corp.emc.com ([169.254.1.248]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Sat, 14 Jun 2014 22:56:45 -0400
From: "Black, David" <david.black@emc.com>
To: "Magnus Westerlund (magnus.westerlund@ericsson.com)" <magnus.westerlund@ericsson.com>, "thomas.zeng@gmail.com" <thomas.zeng@gmail.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Date: Sat, 14 Jun 2014 22:56:43 -0400
Subject: Gen-ART and OPS-Dir review of draft-ietf-mmusic-rtsp-nat-evaluation-14
Thread-Topic: Gen-ART and OPS-Dir review of draft-ietf-mmusic-rtsp-nat-evaluation-14
Thread-Index: Ac+IRWFz4ahMkmbER52S8zyZHBzAJg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076FF268CF@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5hp-R2rG6ARqLK8JBKMfWqZsVwc
Cc: "Black, David" <david.black@emc.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jun 2014 02:57:11 -0000

This is a combined Gen-ART and OPS-DIR review.
Boilerplate for both follows ...

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

I have reviewed this document as part of the Operational directorate's ongo=
ing
effort to review all IETF documents being processed by the IESG.  These com=
ments
were written primarily for the benefit of the operational area directors.
Document editors and WG chairs should treat these comments just like any ot=
her
last call comments.

Document: draft-ietf-mmusic-rtsp-nat-evaluation-14
Reviewer: David L. Black
Review Date: June 14, 2014
IETF LC End Date: June 13, 2014

Summary: This draft is on the right track, but has open issues
                described in the review.

This draft describes and evaluates a number of proposed NAT traversal
mechanisms for RTSP.  The draft covers a lot of detailed material
about the proposed mechanisms, and necessarily assumes that the reader
has some reasonable familiarity with NAT and RTP concepts.

Major issues:

[1] The abstract characterizes this draft as the evaluation that lead to
the mmusic WG's choice of the NAT traversal technique for RTSP, but
the evaluation in this draft did not drive that choice, as indicated
in Section 6:

   Looking at Figure 1 one would draw the conclusion that using TCP
   Tunneling or Three-Way Latching is the solutions that best fulfill
   the requirements.  The different techniques were discussed in the
   MMUSIC WG.  It was established that the WG would pursue an ICE based
   solution due to its generality and capability of handling also
   servers delivering media from behind NATs.

OTOH, there appears to be a lot  of useful material in this draft that
should be published in an informational RFC, not only the comparison, of
NAT traversal techniques, but also documentation of some of those
techniques, as indicated in Section 4:

   This section includes NAT traversal techniques that
   have not been formally specified anywhere else.  The overview section
   of this document may be the only publicly available specification of
   some of the NAT traversal techniques.

This may be fairly simple to address, as the last sentence in the
abstract and the Section 6 text quoted above are the primary sources
of this issue.  It may also help to change the title of this draft
from "The Evaluation of ..." to "Comparison of ..." and do something
analogous to other occurrences of the word "evaluation" in this draft.

Also in the text quoted from section 4 above "overview section" is
misleading, as the documentation is in Section 4 - I suggest deleting
"The overview section of". [Editorial]

[2] Section 4 says:

   Some other techniques have been recommended against or are no longer
   possible due to standardization works' outcome or their failure to
   progress within IETF after the initial evaluation in this document,
   e.g.  RTP No-Op [I-D.ietf-avt-rtp-no-op].

That's too vague, an explicit list should be provided of techniques in
Section 4 that should not or cannot currently be used, starting with RTP
No-Op including an explanation of why that is the case for each technique.
There's also an important editorial clarification needed - these
"other techniques" are not NAT traversal techniques; they are possible
elements of some NAT traversal techniques.

This text is 4.1.1 is part of this issue:

   The first version of STUN [RFC3489] included categorization and
   parameterization of NATs.  This was abandoned in the updated version
   [RFC5389] due to it being unreliable and brittle.  Some of the below
   discussed methods are based on RFC3489 functionality which will be
   called out and the downside of that will be part of the
   characterization.

Minor issues:

[A] Firewall paragraph in Introduction confuses ALG implementation with
firewall configuration (presumably UDP pinholes).  It needs to clearly
separate those two concepts, as the current text implies that punching
a UDP (pin)hole is part of the firewall implementation, whereas it's
actually part of the operational configuration of the firewall.

[B] Still in the Introduction (Section 1):

   At the time when the bulk of work on this document was done, a single
   level of NAT was the dominant deployment for NATs, and multiple level
   of NATs, including Carrier Grade NATs (CGNs) has been only partially
   considered.

That's vague - please provide a clear statement of what is out of scope for
this draft.  It looks like everything other than Basic NAT techniques is
out of scope.

-- Section 1.2
[C]
   Many organizations
   use firewalls to prevent privacy intrusions and malicious attacks to
   corporate computing resources in the private intranet [RFC2588].

Please remove the word "privacy" - I don't believe it's correct in this
context, as many of the intrusions are intended to compromise far more than
privacy. I would also change "to prevent" -> "to counter" as many current
attacks are not prevented by firewalls.

This needs more explanation:

   2.  NAT does not in itself provide security, although some access
       control policies can be implemented using address translation
       schemes.  The inherent filtering behaviours are commonly mistaken
       for real security policies.

At a minimum, explain what sort of "security" is not provided.  In addition=
,
I suggest noting that a NAT can provide some privacy by concealing address/=
port
usage on the private side of the NAT.

[D] Still in Section 1.2:

   In the rest of this memo we use the phrase "NAT traversal"
   interchangeably with "firewall traversal", and "NAT/firewall
   traversal".

No, don't do that, please.  This is a NAT traversal document that considers
the effects of NAT traversal techniques on firewalls, so the term "NAT
traversal" should be the primary term.

-- Section 2, last paragraph.
[E]
   Note that if neither RTCP packets nor RTSP
   messages are received by the RTSP server for a while, the RTSP server
   has the option to delete the corresponding RTP session, SSRC and RTSP
   session ID, because either the client can not get through a middle
   box NAT/firewall, or the client is mal-functioning.

Is there any delay recommended before RTSP server reuse of that set of
identifying information (RTP session, SSRC and RTSP session ID)?

-- Section 3
[F]
   3.  Should have minimal impact on clients not behind NATs and which
       are not dual-hosted.  RTSP dual-hosting means that the RTSP
       signalling protocol and the media protocol (e.g.  RTP) are
       implemented on different computers with different IP addresses.

       *  For instance, no extra delay from RTSP connection till arrival
          of media

By comparison to requirement R3 in Section 6, the above text is too broad.
The R3 requirement considered in this draft is specifically about additiona=
l
protocol round trips; "extra delay" could be introduced for other reasons.

[G] Still in Section 3

   4.  Should be simple to use/implement/administer so people actually
       turn them on

       *  Otherwise people will resort to TCP tunneling through NATs

Not so fast ... TCP tunneling is one of the evaluated techniques (see
Section 4.8), so that text isn't right.  Deletion of the
"* Otherwise ..." sub-bullet should suffice to deal with this.

[H] Still in Section 3

   5.  Should authenticate dual-hosted client transport handler to
       prevent DDoS attacks.

What's a "dual-hosted client transport handler" ???  I suggest adding
this term and dual-hosting/dual-hosted to the Glossary in Section 1.3.

[I] Still in Section 3

   Note a simple preventative measure commonly
   deployed is for the RTSP server to disallow the cases where the
   client's RTP receiver has a different IP address than that of the
   RTSP client.  With the increased deployment of NAT middleboxes by
   operators, i.e. carrier grade NAT (CGN), the reuse of an IP address
   on the NAT's external side by many customers reduces the protection
   provided.  Also in some applications (e.g., centralized
   conferencing), dual-hosted RTSP/RTP clients have valid use cases.
   The key is how to authenticate the messages exchanged during the NAT
   traversal process.

Is that "measure commonly deployed" recommended?  The above text chunk
feels like Security Considerations text, and this text could usefully
be moved to Section 8.

[J] Section 4.1.1 relies on STUN's abandoned NAT type classification
functionality to determine where to send the hole-punching UDP packets.
What's wrong with always sending those packets to the "server's source
address/port"?  That should work for both types of NATs, thereby removing
the dependency on STUN classification of NAT types.

[K] Why are ALG considerations only applicable to STUN-based techniques?

-- Section 4.3.4 Disadvantages list
[L]
   o  Assumes that it is possible to de-multiplex between the packets of
      the media protocol and STUN packets.

That is actually possible, although the demux technique is not exactly
elegant Add a pointer to Section 5.1.2 of RFC 5764 for information on
how this can be done.

-- Section 4.4.1
[M]
   Latching [I-D.ietf-mmusic-latching] is a NAT traversal solution that
   is based on requiring RTSP clients to send UDP packets to the
   server's media output ports.

Well, draft-ietf-mmusic-latching is about to be approved for publication
as an RFC, but it does not apply to RTSP.  Additional RTSP extension work
would be required, as specified in section 4.4.2. Please make that clear
at the start of this section, and include a forward pointer to section 4.4.=
2.

[N] Section 4.6 - Where are the security considerations for 3-way Latching?

-- Section 4.8.4
[O]
   It is not possible to
   get any amplification effect for denial of service attacks due to
   TCP's flow control.

That's not correct or at least not a complete discussion of denial of servi=
ce
possibilities - if an attacker can cause a lot of TCP SYNs to be sent to a
target/victim, the result can be a DDoS attack.  The text quoted above need=
s
to be rewritten to address this possibility.

Nits/editorial comments:

There are additional editorial cleanups that I'll leave to the RFC Editor,
but I noted a few things that seem to deserve mention here:

- Section 1, 1st paragraph

   Today there is a proliferate deployment of different flavors of

"proliferate" -> "proliferating", "flavors" -> "types"

-- Section 1.1:

   "This document uses the term "address and port mapping" as the
   translation between an external address and port and an internal
   address and port.  Note that this is not the same as an "address
   binding" as defined in RFC 2663."

      Note: In the above it would be more correct to use external
      instead of public in the above text.  The external IP address is
      commonly a public one, but might be of other type if the NAT's
      external side is in a private address domain.

That's confusing - I think this can be improved by using more precise
terms in the first sentence (including adding quotes):
         external instead of public ->
                 "external IP address" instead of "public IP address"

-- Section 2

   The loss of a
   RTP mapping can only be detected when expected traffic does not
   arrive.  If a client does not receive data within a few seconds after
   having received the "200 OK" response to a PLAY request, it may be
   the result of a middlebox blocking the traffic.

Are "200 OK" and "PLAY request" sent via RTP?  I don't think so ...
please clarify.

-- Section 4

Add an explanation of what the "Transition:" text discusses for each
mechanism are about - transition from what to what?  I believe that
these chunks of text concern transitioning to a (hypothetical, IMHO)
world in which NATs don't exist.

-- Section 4.3.4 Disadvantages list

   o  Assumes that it is possible to de-multiplex between the packets of
      the media protocol and STUN packets.

It is possible, although not elegant.  Add a pointer to Section 5.1.2
of RFC 5764 for this.

-- Section 5

   DDoS attacks occur if
   the attacker fakes the messages in the NAT traversal mechanism to
   trick the RTSP server into believing that the client's RTP receiver
   is located on a separate host.

"a separate host" -> "the host to be attacked".

-- Section 8

The second paragraph in this section summarizes the security considerations
from Section 4.  It ought to be followed by a paragraph that compares/
contrasts the degree of security risks of the various NAT traversal mechani=
sms
to draw some conclusions - e.g., are some of the proposed mechanisms simply
infeasible/implausible because the security risks are too high?

idnits 2.13.01 found a few minor concerns with the references:

  =3D=3D Outdated reference: A later version (-07) exists of
     draft-ietf-mmusic-latching-05

  =3D=3D Outdated reference: A later version (-21) exists of
     draft-ietf-mmusic-rtsp-nat-20

  -- Obsolete informational reference (is this intentional?): RFC 3489
     (Obsoleted by RFC 5389)

The final concern deserves attention - it would be a good thing if the
need to reference to RFC 3489 could be eliminated.  See [J] above for
one suggested step towards that end.

--- Selected RFC 5706 Appendix A Q&A for OPS-Dir review ---

In general, there is a lot of operational considerations material
(applicable to A.1 questions) in this draft.  Beyond that, management
considerations (A.2 questions) are generally inapplicable.

A.1.1.  Has deployment been discussed?

        Yes, there is significant good material on deployment consideration=
s.

A.1.3.  Has the migration path been discussed?

        Not much, but discussion of migration is mostly deferrable to the
        documentation of the selected NAT traversal mechanism and its
        components.  Ease/difficulty of adding the NAT traversal support
        could have been an evaluation consideration, but was not used.
        On balance, this seems ok.

A.1.4.  Have the Requirements on other protocols and functional
       components been discussed?

        Yes, the discussion of each NAT traversal mechanism indicates what,
        if any changes would be needed to protocols used by that mechanism.

        But ... see major issue [2] above on the need for clarification
        of the discussion of obsolete/unusable protocol changes/features.

A.1.9 Is configuration discussed?

        Yes, as part of the deployment considerations discussion, and
        the desire to avoid complexity of configuration is one of the
        evaluation criteria (R4).

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Mon Jun 16 02:56:24 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A53761B2A87; Mon, 16 Jun 2014 02:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 yll72t8qtW5X; Mon, 16 Jun 2014 02:56:19 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4A01B29B5; Mon, 16 Jun 2014 02:56:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8256; q=dns/txt; s=iport; t=1402912579; x=1404122179; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rdFhC5nvJi8t6OU+4vNkZfwBA8aozrqE1IjwOrlWLfg=; b=jyman3SpVB/Ni5+ckhrR8qQLvKjjUHfavf9gFLAeZKb36+/a3o/S/R1s FnEAGk0tyva2ffW9WvaMCldTMHbcDD6gB4dORPuI80PlOknl6aI7HdAvY mkHvmepP73YqQrSxN2u1NUisoKtg5N7rMESACMT1Mkg8fb3g/N4P4fdz0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFAMC+nlOtJssW/2dsb2JhbABag1+qNgwBAQEBAQEFAZkkAYEodYQDAQEBBDIBBUABDAQLEQMBAQEBCRYIBwkDAgECATQJCAYBDAEFAgEBF4gnDc8IF4VjhxaBJVgHBoQ9AQOWNIQPgUOFN4xeg0I7L4EC
X-IronPort-AV: E=Sophos;i="5.01,485,1400025600"; d="scan'208";a="83348231"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 16 Jun 2014 09:56:16 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s5G9uG8L023862; Mon, 16 Jun 2014 09:56:16 GMT
Message-ID: <539EBF3F.4060906@cisco.com>
Date: Mon, 16 Jun 2014 11:56:15 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>, Brian Trammell <ietf@trammell.ch>
Subject: Re: Gen-ART review of draft-ietf-ipfix-text-adt-05
References: <8D3D17ACE214DC429325B2B98F3AE712076C662F4B@MX15A.corp.emc.com> <63FBCD8F-C028-4AE6-B3CF-F8FDFB98102B@trammell.ch> <8D3D17ACE214DC429325B2B98F3AE712076C6632B4@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C6632B4@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_t0Xblewgk_XYZhuoYxf6lENMso
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>, Juergen Quittek <Quittek@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 09:56:21 -0000

Hi Brian, Juergen,

Do I understand correctly that you plan on submitting a new draft 
version to address David's feedback?

Juergen,
As far as I know, this is the only feedback received during IETF LC.
If that's correct, when this feedback is addressed, I'll put this 
document on the IESG telechat.

Regards, Benoit
> Brian,
>
> Thanks for the response.
>
> Regarding Unicode string normalization and preparation, if those were
> appropriate, they should have been introduced in RFC 7011, and picked
> up here by reference.  If there's an actual problem that requires
> those techniques (unclear), a revision to RFC 7011 would be the right
> place to address that problem, not this draft.
>
> I would note that the sheer volume of monitoring data tends to require
> automatic processing by recipients, and such tools are likely to compare
> strings in monitoring data.
>
> I definitely agree that some text about Enclosing Context rules/requirements
> for Unicode usage would help, e.g., along the lines of:
>
>> We largely presume these to be the responsibility of the Enclosing Context (in
>> this document) and the Metering Process that created the string in the first
>> place. Neither 7011 nor this representation present additional considerations
>> here: we just take the Unicode string we get from whoever wants to send/store
>> it and shovel it out.
> and
>
>>> Lots of mischief is possible with non-printing and control characters -
>>> I would expect that the Enclosing Context contains sufficient restrictions
>>> on use of Unicode to deal with most of this concern, and would state that
>>> expectation.  This comment is definitely specific to this draft.
> So, please do add some text on this topic.
>
>>> A general warning about unreliability of Unicode string comparison
>>> is in order.  This also applies if an identifier that is not limited
>>> to ASCII characters is substituted for an integer as described in
>>> Section 4.2.
>> Good point; is there a good cite for this?
> Try RFC 6885 - Stringprep Revision and Problem Statement
> for the Preparation and Comparison of Internationalized Strings (PRECIS)
>
>>> Section 4.1.5 of the précis framework draft warns against use of mixed-
>>> direction Unicode strings, as "there is currently no widely accepted and
>>> implemented solution for the processing and safe display of mixed-
>>> direction strings."  That warning deserves repetition here.
> Please repeat that warning, probably w/an informative reference to the
> précis framework draft.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Brian Trammell [mailto:ietf@trammell.ch]
>> Sent: Wednesday, May 28, 2014 5:22 AM
>> To: Black, David
>> Cc: General Area Review Team (gen-art@ietf.org); ipfix@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-ipfix-text-adt-05
>>
>> hi David,
>>
>> Many thanks for the review. Comments and questions inline.
>>
>> On 24 May 2014, at 04:10, Black, David <david.black@emc.com> wrote:
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>>
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-ietf-ipfix-text-adt-05
>>> Reviewer: David L. Black
>>> Review Date: May 23, 2014
>>> IETF LC End Date: May 28, 2014
>>>
>>> Summary:  This draft is on the right track, but has open issues
>>> 		described in the review.
>>>
>>> This is a relatively short draft defining textual representations of
>>> IPFIX data elements.  It's clear and easy to read.
>>>
>>> I assume that all the ABNF has been checked.
>> Yep.
>>
>>> The open issues involve use of Unicode.
>> This is unsurprising. :)
>>
>>> Minor issues:
>>>
>>> Section 4.7 string
>>>
>>>    As Information Elements of the string type are simply UTF-8 encoded
>>>    strings, they are represented directly, subject to the escaping and
>>>    encoding rules of the Enclosing Context.
>>>
>>> There's nothing "simply" about use of UTF-8 encoded strings :-).
>> Well, no. But most of the string normalization nightmares with UTF-8 are also
>> problems in the Enclosing Contexts as well, so the assumption here is that if
>> you're already representing strings in, say, UTF-8 encoded JSON, you're
>> already paying the UTF-8 tax, so this document presents no additional
>> considerations.
>>
>> There is an additional point here, though, that the Enclosing Context may
>> prefer or require a different encoding than UTF-8, so we should address that:
>>
>> 	As Information Elements of the string type are simply Unicode
>> 	strings (encoded as UTF-8 when appearing in Data Sets in IPFIX
>> 	Messages [RFC 7011]), they are represented directly, using the
>> 	Unicode encoding rules and quoting and escaping rules of the
>> 	Enclosing Context.
>>
>>> There appear to be no restrictions on Unicode codepoint usage and no
>>> requirements for string normalization or other preparation either in this
>>> draft or RFC 7011.
>> We largely presume these to be the responsibility of the Enclosing Context (in
>> this document) and the Metering Process that created the string in the first
>> place. Neither 7011 nor this representation present additional considerations
>> here: we just take the Unicode string we get from whoever wants to send/store
>> it and shovel it out.
>>
>> I'm not sure it makes sense to enforce normalization in this context.
>>
>>>   This can be a formula for all sorts of mischief, so
>>> some warnings about what's possible should be added somewhere - some of
>>> these comments may be raising Unicode concerns in RFC 7011 that would
>>> be better addressed there.
>> Generally, text-adt is intended to allow the use of the IPFIX Information
>> Model separately from the protocol described in RFC 7011, so any concern there
>> should also be raised here.
>>
>>> A general warning about unreliability of Unicode string comparison
>>> is in order.  This also applies if an identifier that is not limited
>>> to ASCII characters is substituted for an integer as described in
>>> Section 4.2.
>> Good point; is there a good cite for this?
>>
>>>   In addition, the concerns around visually similar
>>> characters discussed in section 10.5 of the précis framework draft
>>> (draft-ietf-précis-framework) apply; a short summary and pointer
>>> to that section of that draft should suffice.
>>>
>>> Section 4.1.5 of the précis framework draft warns against use of mixed-
>>> direction Unicode strings, as "there is currently no widely accepted and
>>> implemented solution for the processing and safe display of mixed-
>>> direction strings."  That warning deserves repetition here.
>>>
>>> Lots of mischief is possible with non-printing and control characters -
>>> I would expect that the Enclosing Context contains sufficient restrictions
>>> on use of Unicode to deal with most of this concern, and would state that
>>> expectation.  This comment is definitely specific to this draft.
>>>
>>> Nits/editorial comments:
>>>
>>> Section 4.4 float32 and float64
>>>
>>>    exponent = ( "e" / "E" ) [sign] 1*3DIGIT
>>>
>>> Please explain why no more than 3 digits are ever required.
>> Will do (i.e., because the maximum ranges on the type range from O(1e-3xx) -
>> O(1e3xx)).
>>
>>> Section 4.8 dateTime*
>>>
>>> The '*' in the section title, dateTime* is clever, but it's meaning is not
>>> obvious.  I suggest "The dateTime Data Types" as a better section title.
>> Yep, thanks.
>>
>>> Section 5 Security Considerations
>>>
>>>    The security considerations for the IPFIX Protocol [RFC7011] apply;
>>>    this document presents no additional security considerations.
>>>
>>> That's ok, although adding a direct mention of the [UTF8-EXPLOIT] TR
>>> cited in RFC 7011 would be helpful.
>> Will do.
>>
>>> idnits 2.13.01 warns that the JSON reference (RFC 4627) is obsolete, and
>>> needs to be replaced with one or two current RFC references.
>> Oops; will replace.
>>
>> Thanks again, cheers,
>>
>> Brian
> .
>


From nobody Mon Jun 16 07:32:39 2014
Return-Path: <blong@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6491B2879 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 12:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.029
X-Spam-Level: 
X-Spam-Status: No, score=-4.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 bTkGccfAozM1 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 12:13:15 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BC951B27BB for <ietf@ietf.org>; Fri, 13 Jun 2014 12:13:14 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id tr6so2882942ieb.29 for <ietf@ietf.org>; Fri, 13 Jun 2014 12:13:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=o2m5DbvBh1vGGHaUYNbLS9gy0ifLc2lBFCIuAjlwTwc=; b=Mh8kxvHy1lPh97Ri8Qq8xJhwJyhdiTWUTqMTabN/jG10r+PJa9N8zAdnQ72//aUM2U w9UM4OtUtja2SVPDjrV2coKMStKTqYJI+ijyR6diECcRhIyRFvbBiT1Oql0VD5AYpmCz QQwxRX2pDAIHtS3zz3RO6TDlR2zFYQX1IyJxG7w2ouUvsmkkH4p7DHUMm4jXMEYVA9XB hdY4R7XfGNxRjWTNuiY6hMUrsOaVn2C72YAYmIm487ZJmzUR1GGc4DNZDILByziAbgHe qpZlKOJkMsBXkuAUsL/+QoZf6U4zS3lQB6G0RqsiLc73mziprMDHJC2jpgfCZmOrxceM IcfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=o2m5DbvBh1vGGHaUYNbLS9gy0ifLc2lBFCIuAjlwTwc=; b=GbIK/ko2oGN9l35RhrvVDXQbpPMzMeaDanQRld5bbrX59QLQFlcmA2hA4PnO8okKB/ gkM2KAfW0IoRNHAGoNIen/9boNSckqKdkc2XsJB7ElqeLml3L2tC/X6HPHqW/5JNAp1Q x7/lLUP3dHrwVCmvvAsBh6M++MPwslH7B64Kpt6COyUMoJHsZOSm9Njwh7Sy/INsFMI7 bRG0pLEbxFBRpMm2RGxT6vSvLYNt9IRFDuZO2kJLaCkQZuZp+BRDsijRiSVOgBOuPkqw +LC9n5gMeM/TTUcmcy6k/OcNEzF96XDFgcrDoYJe2rxitKSYC4k6jvzHISULbu5IlsKW KNHw==
X-Gm-Message-State: ALoCoQm2r17DLFmhYPkfO0R/tjzhUZtdH8ljr+qCrRVZzQjzEXeGLgB0gQ0qIoDesIGzQ+/lYtpD
MIME-Version: 1.0
X-Received: by 10.42.212.18 with SMTP id gq18mr5428000icb.48.1402686794412; Fri, 13 Jun 2014 12:13:14 -0700 (PDT)
Received: by 10.64.136.202 with HTTP; Fri, 13 Jun 2014 12:13:14 -0700 (PDT)
In-Reply-To: <539B3D9A.7040104@meetinghouse.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <87sin9oegr.fsf@uwakimon.sk.tsukuba.ac.jp> <539AE6AD.9090601@meetinghouse.net> <CAMm+Lwhi+7o-GYa7Y4U-iZ=jyWX+rE4nWHrV83csO-qQOCxTVw@mail.gmail.com> <539B3D9A.7040104@meetinghouse.net>
Date: Fri, 13 Jun 2014 12:13:14 -0700
Message-ID: <CABa8R6sLToBn0vcdd4Y8fEhVzdXiT0J40UST5OK1Vjh87SEcEA@mail.gmail.com>
Subject: Re: [dmarc-ietf] Change the mailing list protocol, not DMARC.
From: Brandon Long <blong@google.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=20cf303e9d821cea1804fbbc7812
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FDBOngQwXVr7z3Blz_sQOKlspX4
X-Mailman-Approved-At: Mon, 16 Jun 2014 07:32:37 -0700
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 19:13:16 -0000

--20cf303e9d821cea1804fbbc7812
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 13, 2014 at 11:06 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Phillip Hallam-Baker wrote:
>
>
>>
>>
>> On Fri, Jun 13, 2014 at 7:55 AM, Miles Fidelman <
>> mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>>
>>     Stephen J. Turnbull wrote:
>>
>>         Phillip Hallam-Baker writes:
>>
>>           > My point is that mail is an old protocol and people who
>>         expect that
>>           > it can be kept going unaltered in its original form
>>         serving all the
>>           > purposes that it was never designed for but have emerged
>>         over time
>>           > are going to be upset no matter what.
>>
>>         True, as far as it goes.  However, there is need for a push
>>         protocol
>>         that allows you to receive contacts from authors you don't
>>         know yet,
>>         in other words, a medium that is designed to be flexible enough to
>>         accomodate new modes of communication.
>>
>>         It's not obvious to me that this need can be satisfied while
>>         at the
>>         same time denying spam.  If it is indeed impossible, I don't
>>         see why
>>         that purpose can't continue to be served by email, while most mail
>>         (which is correspondence among acquaintances) gets redirected into
>>         authenticated channels.
>>
>>     Just a quick reminder here:  Postal mail is still going strong,
>>     after 100s of years.
>>
>>
>> Only because we haven't got email security properly sorted.
>>
>> I can't remember the last time I received a real letter. All I get is
>> junk mail and bills. And the bills arrive because we haven't got the
>> standards for doing it electronically established yet.
>>
>
> Bills are "real" - they're transactional.  So are checks.  Some of us
> actually do things like send proposals, signed contracts, and so forth.
>  And, of course, packages.  And the higher the value, the more likely that
> they'll be sent via physical mail.  It ain't going away anytime soon.


If I had spam filtering on postal mail that was as good as I've got on
email, regular postal mail would already be gone.

That isn't to say that high value postal mail at FedEx/UPS/etc prices would
be gone, just that current first class mail and daily deliveries would be.

In the US, the USPS is already on rough ground (which isn't entirely due to
failing rates of mail, granted), so "going strong" would not be what I'd
use.  Holding out for another 100 years in some form... maybe.

Brandon

--20cf303e9d821cea1804fbbc7812
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jun 13, 2014 at 11:06 AM, Miles Fidelman <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelm=
an@meetinghouse.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Phillip Hallam-Baker wrote:<div><div class=
=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
<br>
On Fri, Jun 13, 2014 at 7:55 AM, Miles Fidelman &lt;<a href=3D"mailto:mfide=
lman@meetinghouse.net" target=3D"_blank">mfidelman@meetinghouse.net</a> &lt=
;mailto:<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfi=
delman@<u></u>meetinghouse.net</a>&gt;&gt; wrote:<br>

<br>
=C2=A0 =C2=A0 Stephen J. Turnbull wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phillip Hallam-Baker writes:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; My point is that mail is an old pro=
tocol and people who<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 expect that<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; it can be kept going unaltered in i=
ts original form<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 serving all the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; purposes that it was never designed=
 for but have emerged<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 over time<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; are going to be upset no matter wha=
t.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 True, as far as it goes. =C2=A0However, there i=
s need for a push<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 protocol<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that allows you to receive contacts from author=
s you don&#39;t<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 know yet,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 in other words, a medium that is designed to be=
 flexible enough to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 accomodate new modes of communication.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 It&#39;s not obvious to me that this need can b=
e satisfied while<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 at the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 same time denying spam. =C2=A0If it is indeed i=
mpossible, I don&#39;t<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 see why<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that purpose can&#39;t continue to be served by=
 email, while most mail<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (which is correspondence among acquaintances) g=
ets redirected into<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 authenticated channels.<br>
<br>
=C2=A0 =C2=A0 Just a quick reminder here: =C2=A0Postal mail is still going =
strong,<br>
=C2=A0 =C2=A0 after 100s of years.<br>
<br>
<br>
Only because we haven&#39;t got email security properly sorted.<br>
<br>
I can&#39;t remember the last time I received a real letter. All I get is j=
unk mail and bills. And the bills arrive because we haven&#39;t got the sta=
ndards for doing it electronically established yet.<br>
</blockquote>
<br></div></div>
Bills are &quot;real&quot; - they&#39;re transactional. =C2=A0So are checks=
. =C2=A0Some of us actually do things like send proposals, signed contracts=
, and so forth. =C2=A0And, of course, packages. =C2=A0And the higher the va=
lue, the more likely that they&#39;ll be sent via physical mail. =C2=A0It a=
in&#39;t going away anytime soon.</blockquote>
<div><br></div><div>If I had spam filtering on postal mail that was as good=
 as I&#39;ve got on email, regular postal mail would already be gone.</div>=
<div><br></div><div>That isn&#39;t to say that high value postal mail at Fe=
dEx/UPS/etc prices would be gone, just that current first class mail and da=
ily deliveries would be.</div>
<div><br></div><div>In the US, the USPS is already on rough ground (which i=
sn&#39;t entirely due to failing rates of mail, granted), so &quot;going st=
rong&quot; would not be what I&#39;d use. =C2=A0Holding out for another 100=
 years in some form... maybe.</div>
<div><br></div><div>Brandon=C2=A0</div></div><br></div></div>

--20cf303e9d821cea1804fbbc7812--


From nobody Mon Jun 16 07:32:57 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6031A01E7 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 woUQ53SrMTiG for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 11:08:36 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75F4A1B293F for <ietf@ietf.org>; Fri, 13 Jun 2014 11:08:36 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BDFA220028 for <ietf@ietf.org>; Fri, 13 Jun 2014 14:12:17 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 42EA863B0E; Fri, 13 Jun 2014 14:08:32 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2C2FE63B0B for <ietf@ietf.org>; Fri, 13 Jun 2014 14:08:32 -0400 (EDT)
From: Michael Richardson <mcr+nomcom@sandelman.ca>
To: ietf@ietf.org
Subject: third call: NomCom 2014-2015 Call for Volunteers
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 13 Jun 2014 14:08:32 -0400
Message-ID: <18924.1402682912@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zv3woLzYf7wAM49S6WxGxceabbY
X-Mailman-Approved-At: Mon, 16 Jun 2014 07:32:54 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 18:08:39 -0000

--=-=-=


This is the third call for volunteers.
VOLUNTEER NOW: we need to make 200.
The DEADLINE is June 26 to volunteer.

The IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

If your name is on the below, then you have volunteered and are qualified.
In addition to those who volunteered by email, it also includes those who
indicated their willingness to serve on the IETF90 registration form, and
whose eligibility has been confirmed.  54 people were confirmed to be
eligible, and 70 people were not confirmed based upon the email they have
used to register.   Those 124 people have been contacted directly.

If you have heard from me, but are not on the list, then there is some
problem, and you should have gotten a query from me to determine your
eligibility.

If you have volunteered and not heard from him, then please resend;
it got lost.

Ten voting members for the nomcom are selected in a verifiably random
way from a pool of volunteers. The more volunteers, the better chance we have
of choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!
We are at 123 volunteers so far, and WE NEED TO HAVE 200!!!

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
         86(Orlando),       \
         87(Berlin),         *** ANY THREE!
         88(Vancouver),     /
         89(London)        /

If you qualify, please volunteer.   However, much as we want this, before you
decide to volunteer, please be sure you are willing to forgo appointment
to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
There will be activities to collect requirements from the community, review
candidate questionnaires, review feedback from community members about
candidates, and talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is also
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct interviews.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following 4 lines the email body (it is simplest
if you just include the info);

Your Full Name
Emails used to register
Telephone
Current Primary Affiliation

You should expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive this response,
please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider
that nomcom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
    https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details
of the randomness seeds to be used for the RFC 3797 selection process,
within the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in alphabetical order by first name
ANM Zaheduzzaman Sarker
Adam Montville
Ari Ker?nen
Benson Schliesser
Bhumip Khasnabish
Bill VerSteeg
Carl Williams
Carlos Martinez
Charles Eckel
Charles Perkins
Christer Holmberg
Craig White
DHRUV DHODY
Dacheng Zhang
Damien Saucez
Dapeng Liu
Dean Bogdanovic
Dimitri Papadimitriou
Donald Eastlake
Edward Crabbe
Emil Ivov
Eric Rescorla
Eric VYNCKE
Fangwei Hu
Fatai Zhang
Fernando Gont
Fred Baker
Giles Heron
Gonzalo Salgueiro
Gregory Mirsky
Hannes Gredler
Hongyu Li
Hosnieh Rafiee
Hugo Salgado
Hui Deng
Iuniana Oprescu
Jeff Tantsura
John Drake
John Jason Brzozowski
John Levine
John Scudder
Jon Hudson
Jon Mitchell
Karen O'Donoghue
Karen Seo
Kaveh Ranjbar
Klaas Wierenga
Larry Masinter
Lars Eggert
Lee Howard
Lei Zhu
Li Xue
Linda Dunbar
Lingli Deng
Louis (Lou) Berger
Luca Martini
Lucy Lynch
Lucy Yong
Luigi Iannone
Mach Chen
Marcelo Bagnulo
Mark Townsley
Matt Lepinski
Matthew Bocci
Mehmet Ersue
Melinda Shore
Michael Jones
Min Ye
Mingui Zhang
Ning Zong
Ole Troan
Pascal Thubert
Paul Hoffman
Peter Lothberg
Peter Yee
QIN WU
Ralph Droms
Ron Bonica
Ross Callon
Ross Finlayson
Russ White
Sam K. Aldrin
Samuel Weiler
Sandeep Kumar
Sanjay Mishra
Scott Mansfield
Sheng JIANG
Shucheng Liu
Simon Pietro Romano
Stan Ratliff
Stephan Friedl
Stephan Wenger
Stephen Kent
Stewart Bryant
Stig Venaas
Suhas Nandakumar
Suresh Krishnan
Susan Hares
Thomas Walsh
Tim Wicinski
Tissa Senevirathne
Toerless Eckert
Tony Hansen
Ulrich Herberg
Varun Singh
Wassim Haddad
Xiaohu XU
Yi Zhao
Yizhou Li
Yong Cui
Yuanlong Jiang
Yunfei Zhang
Zhaohui Zhang
Zhen Cao
iuniana oprescu


--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU5s+HYCLcPvd0N1lAQISyggAljiPfZ/itCl23WAkMoir9XKFd9TAHSxs
hb2Be5k7feR5A+3LEk/rgH+BsTjnuX8ccAmniVjM88/14/YlM9q6HeNzYrCedW0w
X0FyshN01UpHylwhgxweS1L2rQ1MywsJkWrx+TNslF2M6tHs/R9qWccC0+obEd+A
cR6jkgzXbiAlNysGimWqpzxlrtaukQkwG3/liVj45LFlMfiEV1UWKu5KRFyx4WRN
Az/91IFE69KfNFJmLbx1RLglYy+x94PjYmzkXTW7SItwaWTu/CojRoZq9qq6U+4F
9DhwM1U0P539d2xN0FtYAN5J8Vk6/3bfTJQnR8MHMGmE8AST455KAw==
=/0WO
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jun 16 08:35:06 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1A61A007C; Mon, 16 Jun 2014 08:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 juIHhwWizBd8; Mon, 16 Jun 2014 08:35:01 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3273F1A007B; Mon, 16 Jun 2014 08:35:01 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s5GFYtOX007500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 16 Jun 2014 17:34:55 +0200 (MEST)
Subject: Re: [TLS] Last Call: <draft-ietf-tls-encrypt-then-mac-02.txt> (Encrypt-then-MAC for TLS and DTLS) to Proposed Standard
In-Reply-To: <CADi0yUN+A7QGZLeSDDXMLhK6mr4O09rGr0ZJy6AafPVSQJX1tA@mail.gmail.com>
To: Hugo Krawczyk <hugo@ee.technion.ac.il>
Date: Mon, 16 Jun 2014 17:34:55 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140616153455.977B21AD52@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dfmr87r-tQX5YsCUEdC_e_gwkYk
Cc: "ietf\\@ietf.org" <ietf@ietf.org>, TLS Mailing List <tls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 15:35:03 -0000

Hugo Krawczyk wrote:
>
> The technical results in my 2001 paper are correct but the conclusion
> regarding SSL/TLS is wrong. I assumed that TLS was using fresh IVs and that
> the MAC was computed on the encoded plaintext, i.e. Encode-Mac-Encrypt
> while TLS is doing Mac-Encode-Encrypt which is exactly what my theoretical
> example shows is insecure. The later padding attacks showed that the
> theoretical example of insecurity had a very practical instantiation in
> TLS.  While the paper shows correctly that MAC-then-Encrypt can be secure
> with both CBC and stream ciphers, it also shows that it requires a LOT of
> care about encoding - it turned out that TLS/SSL was not doing that. So if
> you want to keep Mac-then-Encrypt then you must change the encoding as well
> as how you apply the MAC. Changing to Encrypt-then-MAC is a much safer
> solution.

I agree with you that your paper demonstrates problem with
mac-extend-encrypt schemes.  And that it fails to notice that
TLS applies CBC padding after computing the MAC and before encryption,
and is therefore an mac-extend-encrypt scheme that can be susceptible to
decryption oracles.

But I strongly disagree to the assertion that "Encrypt-then-MAC" would
be a much safer scheme than *TRUE* MAC-then-Encrypt _withou_ any
extension inserted before the encryption such as CBC-padding.

In fact, the pad-mac-encrypt scheme for TLS-CBC-ciphersuites, as suggested
by Serge Vaudenay, is provably safer than the currently favoured
encrypt-then-MAC scheme.


-Martin


From nobody Mon Jun 16 11:13:37 2014
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC43C1A0033 for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 11:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 KKrnuoL9vKOr for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 11:13:30 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.246.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B31581A00B8 for <ietf@ietf.org>; Mon, 16 Jun 2014 11:13:28 -0700 (PDT)
Received: from [141.161.133.90] (port=49564 helo=[10.129.226.108]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <eburger-l@standardstrack.com>) id 1WwbPH-0002xJ-F4 for ietf@ietf.org; Mon, 16 Jun 2014 11:13:27 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <01P907G00ESM0049PU@mauve.mrochek.com>
Date: Mon, 16 Jun 2014 14:13:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2653BAE2-E5EC-4A6C-A611-3CA88F6AD09C@standardstrack.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.2)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger-l+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RwZcSivmDit1IwP3a4QIO3do9Lc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 18:13:33 -0000

I also wonder about the accuracy of the numbers. They say Apple=92s MUAs =
command 44% of the email MUA market (iPhone+iPad+MacOS). That seems just =
a tiny bit high, considering Apple commands 40% of all smartphones, 33% =
of all tablets, and under 8% of desktops.

On Jun 14, 2014, at 4:21 PM, ned+ietf@mauve.mrochek.com wrote:

>> Ned,
>=20
>> On 15/06/2014 02:42, ned+ietf@mauve.mrochek.com wrote:
>> ...
>>> Some data to support this conclusion:
>> [that webmail is not dominant]
>>>=20
>>>  http://emailclientmarketshare.com/
>=20
>> Hmm. I was curious about what those numbers really measure.
>> Judging by http://litmus.com/email-analytics, it seems that
>> they refer to a sample of emails that (a) contained a specific
>> HTML snippet and were (b) opened as HTML by the clients and
>> (c) by implication, had been sent via a mailing list.
>=20
> Litmus is a service for people who send out bulk mail and want to =
track
> whether or not it's seen, and when it's seen what client is used to =
see it.
>=20
>> It seems
>> very likely to me that the sample consisted of spam.
>=20
> Actually, it's unlikely in the extreme. Spammers are into volume, they =
don't
> care about tracking analytics and aren't going to pay a company like =
Litmus to
> perform such a service. But there are a hell of a lot of legitimate =
bulk email
> senders out there who do care about the effectiveness of their mail, =
and have
> the money to pay for such things.
>=20
>> I'm
>> not sure that the numbers reflect unbiased statistics, unless
>> you're a spammer. In any case they don't indicate how many
>> people open email in plain text mode (which I alway do if
>> possible, precisely to avoid embedded code).
>=20
> Well, I think it's up to you to show that a significant fraction of =
the
> email-reading public prefers to read HTML mail without resolving any =
of the
> links, and that missing out on that fraction significantly biases such =
data.
>=20
>> That said, they certainly show that one size doesn't fit all.
>=20
> Which was the main point.
>=20
> 				Ned
>=20
>=20


From nobody Mon Jun 16 11:40:40 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3DC1A015D for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 11:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 MV_WDCqhf0zF for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 11:40:37 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8AC1A014E for <ietf@ietf.org>; Mon, 16 Jun 2014 11:40:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P92VUQCWB40054FV@mauve.mrochek.com> for ietf@ietf.org; Mon, 16 Jun 2014 11:35:21 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=windows-1252
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P8UD4AOU8W0049PU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 16 Jun 2014 11:35:18 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P92VUP3SB40049PU@mauve.mrochek.com>
Date: Mon, 16 Jun 2014 11:22:19 -0700 (PDT)
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
In-reply-to: "Your message dated Mon, 16 Jun 2014 14:13:24 -0400" <2653BAE2-E5EC-4A6C-A611-3CA88F6AD09C@standardstrack.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <2653BAE2-E5EC-4A6C-A611-3CA88F6AD09C@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mJmZ94_-BBpB9Z4lzAwyJbZRmzg
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 18:40:39 -0000

> I also wonder about the accuracy of the numbers. They say Apple’s MUAs
> command 44% of the email MUA market (iPhone+iPad+MacOS).

> That seems just a tiny bit high, considering Apple commands 40% of all
> smartphones, 33% of all tablets, and under 8% of desktops.

All they are saying that those are the email clients they see accessing the
messages sent by the folks who use their service. This has very little to do
with the phone/laptop  market overall. A lot of people never access their email
from their smart phone or tablet; indeed, there are a fair number who never do
anything "smart" with their phone at all.

Assuming the numbers are actually representative of mobile email use on a
broader scale, at most what they are telling you is that the percentage of
people who actually make use of their phone's capabilities for email may be
higher for iPhones/iPads.

				Ned

> On Jun 14, 2014, at 4:21 PM, ned+ietf@mauve.mrochek.com wrote:

> >> Ned,
> >
> >> On 15/06/2014 02:42, ned+ietf@mauve.mrochek.com wrote:
> >> ...
> >>> Some data to support this conclusion:
> >> [that webmail is not dominant]
> >>>
> >>>  http://emailclientmarketshare.com/
> >
> >> Hmm. I was curious about what those numbers really measure.
> >> Judging by http://litmus.com/email-analytics, it seems that
> >> they refer to a sample of emails that (a) contained a specific
> >> HTML snippet and were (b) opened as HTML by the clients and
> >> (c) by implication, had been sent via a mailing list.
> >
> > Litmus is a service for people who send out bulk mail and want to track
> > whether or not it's seen, and when it's seen what client is used to see it.
> >
> >> It seems
> >> very likely to me that the sample consisted of spam.
> >
> > Actually, it's unlikely in the extreme. Spammers are into volume, they don't
> > care about tracking analytics and aren't going to pay a company like Litmus to
> > perform such a service. But there are a hell of a lot of legitimate bulk email
> > senders out there who do care about the effectiveness of their mail, and have
> > the money to pay for such things.
> >
> >> I'm
> >> not sure that the numbers reflect unbiased statistics, unless
> >> you're a spammer. In any case they don't indicate how many
> >> people open email in plain text mode (which I alway do if
> >> possible, precisely to avoid embedded code).
> >
> > Well, I think it's up to you to show that a significant fraction of the
> > email-reading public prefers to read HTML mail without resolving any of the
> > links, and that missing out on that fraction significantly biases such data.
> >
> >> That said, they certainly show that one size doesn't fit all.
> >
> > Which was the main point.
> >
> > 				Ned
> >
> >


From nobody Mon Jun 16 13:49:20 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FA01A0212 for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 13:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 BTI7PLKcZgxH for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 13:48:54 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C210F1A0218 for <ietf@ietf.org>; Mon, 16 Jun 2014 13:48:43 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id uo5so4604529pbc.12 for <ietf@ietf.org>; Mon, 16 Jun 2014 13:48:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BUGM06oaPyu0l4NkctnGXQMkeRr8JOTv3FQbbP8CixE=; b=gay+FdRfOjp7pK5WHml8LDwSuV1UnCYU4W+1EulHaxX0ZWipkL0sirhff5yWCyKn3a ehTH37MBrWet8scMgz38J6H2FaUw65Q8NeFOn6fwguefs53f+udN6p024tvNkcOULkvu OWuX/RMkxzh3e+29uLBZBRaOggbfIAB2aIsmgZ/q1xDWf47wms2z+BcEHp912Vm0CrgB xL/vml+tHSidfiwjcT7lCnFRbshOgJ/vXTVZ1KkTcHvN2rMXDSsWQbFQ7YGDId4oTDwN sLs//VCUOnH/W5ysD3NtMNhCaoig+3a6vlHPd+FuMSGPKe4YGulwzng/ZkwqK9wSWy0g b8Sw==
X-Received: by 10.66.192.104 with SMTP id hf8mr27379044pac.13.1402951723445; Mon, 16 Jun 2014 13:48:43 -0700 (PDT)
Received: from [192.168.178.23] (10.192.69.111.dynamic.snap.net.nz. [111.69.192.10]) by mx.google.com with ESMTPSA id g6sm73867862pat.2.2014.06.16.13.48.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 13:48:42 -0700 (PDT)
Message-ID: <539F5828.60403@gmail.com>
Date: Tue, 17 Jun 2014 08:48:40 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com>
In-Reply-To: <01P907G00ESM0049PU@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Dt4TxbBCYWAGJ1Qg5RpABOphckY
Cc: ned+ietf@mauve.mrochek.com, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 20:49:08 -0000

Ned,

On 15/06/2014 08:21, Ned Freed wrote:
>> Ned,
> 
>> On 15/06/2014 02:42, ned+ietf@mauve.mrochek.com wrote:
>> ...
>>> Some data to support this conclusion:
>> [that webmail is not dominant]
>>>   http://emailclientmarketshare.com/
> 
>> Hmm. I was curious about what those numbers really measure.
>> Judging by http://litmus.com/email-analytics, it seems that
>> they refer to a sample of emails that (a) contained a specific
>> HTML snippet and were (b) opened as HTML by the clients and
>> (c) by implication, had been sent via a mailing list.
> 
> Litmus is a service for people who send out bulk mail and want to track
> whether or not it's seen, and when it's seen what client is used to see it.
> 
>> It seems
>> very likely to me that the sample consisted of spam.
> 
> Actually, it's unlikely in the extreme. Spammers are into volume, they don't
> care about tracking analytics and aren't going to pay a company like Litmus to
> perform such a service. But there are a hell of a lot of legitimate bulk email
> senders out there who do care about the effectiveness of their mail, and have
> the money to pay for such things.

I think I'll avoid stating an opinion about the boundary between
legitimate bulk email and spam, because that would lead to far
too much dissent, pretty much regardless of what I said ;-)

>> I'm
>> not sure that the numbers reflect unbiased statistics, unless
>> you're a spammer. In any case they don't indicate how many
>> people open email in plain text mode (which I alway do if
>> possible, precisely to avoid embedded code).
> 
> Well, I think it's up to you to show that a significant fraction of the
> email-reading public prefers to read HTML mail without resolving any of the
> links, and that missing out on that fraction significantly biases such data.

I believe I am in a tiny, tiny minority by running my email
client in 'plain text' mode unless I receive a message that is
incomprehensible without setting 'original html' mode.

>> That said, they certainly show that one size doesn't fit all.
> 
> Which was the main point.

Indeed.

    Brian


From nobody Mon Jun 16 14:33:15 2014
Return-Path: <casner@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3873B1A022B for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 14:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 36X2oT15qocX for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 14:33:12 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 0919E1A0266 for <ietf@ietf.org>; Mon, 16 Jun 2014 14:33:12 -0700 (PDT)
Received: from auge (75-25-120-141.lightspeed.snvaca.sbcglobal.net [75.25.120.141]) (authenticated bits=0) by c.mail.sonic.net (8.14.4/8.14.4) with ESMTP id s5GLX9tP020678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Jun 2014 14:33:09 -0700
Date: Mon, 16 Jun 2014 14:33:09 -0700 (PDT)
From: Stephen Casner <casner@acm.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
In-Reply-To: <539F5828.60403@gmail.com>
Message-ID: <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com>
User-Agent: Alpine 2.19.9991 (OSX 64 2014-05-31)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Sonic-ID: C;6BXSz5314xG21rdcoNQ8UQ== M;LKLyz5314xG21rdcoNQ8UQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JnFk4o8r-j9uyWAPe2ouNwHgYPI
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 21:33:13 -0000

On Tue, 17 Jun 2014, Brian E Carpenter wrote:

> I believe I am in a tiny, tiny minority by running my email
> client in 'plain text' mode unless I receive a message that is
> incomprehensible without setting 'original html' mode.

I'm with you there.

                                                        -- Steve


From nobody Mon Jun 16 16:55:49 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 772911A02D3 for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 16:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 QCPxyz8Yo4y3 for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 16:55:43 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A8881A02D2 for <ietf@ietf.org>; Mon, 16 Jun 2014 16:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=zg3RUOslp2YUSPFyscbC7sRKmd6Y90FUD9piy0hCqPE=;  b=orN8CymxaLixASdgcxJKpwKiRMSVJc9n/Psxw0aMRRU8R2Oq8EaSCP4+lvtWONEHdpSkBc0apm7vPRipTbq+U8BPMCIBzsQft8BN7UogjDKpckFOmYSSirgmWddpreiRmAiy0ga3jr1M52iKGGmvQmNeOkiS6MGZoAr0rSPEZ6M=;
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WwgkX-0008Ad-Be; Mon, 16 Jun 2014 23:55:41 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id C93795802F6; Mon, 16 Jun 2014 19:55:40 -0400 (EDT)
Date: Mon, 16 Jun 2014 19:55:40 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Stephen Casner <casner@acm.org>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Message-ID: <20140616235540.GC2214@thunk.org>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ECYxmLclNeuUBGj4V6R4xFKsQ6w
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 23:55:46 -0000

On Mon, Jun 16, 2014 at 02:33:09PM -0700, Stephen Casner wrote:
> On Tue, 17 Jun 2014, Brian E Carpenter wrote:
> 
> > I believe I am in a tiny, tiny minority by running my email
> > client in 'plain text' mode unless I receive a message that is
> > incomprehensible without setting 'original html' mode.
> 
> I'm with you there.

Ditto.  But whenver these sorts of discussions come up, it's always
pointed out that engineers don't count when product managers are
making their decisions.  :-(

			- Ted (who is using "mutt" and "offlineimap")


From nobody Mon Jun 16 18:39:19 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB5BF1A008F for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 18:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.677
X-Spam-Level: 
X-Spam-Status: No, score=-0.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 3VLYqAKlLZVh for <ietf@ietfa.amsl.com>; Mon, 16 Jun 2014 18:39:15 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96EBB1A0084 for <ietf@ietf.org>; Mon, 16 Jun 2014 18:39:15 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id u57so6379178wes.5 for <ietf@ietf.org>; Mon, 16 Jun 2014 18:39:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=FFkVd/Rm3YghP6EbE3BV7XKiROk9XyrXZ3YJZJmDz1o=; b=z9TKd89NexSxYWWJy5D/aeshD1m+5sFMpGzsRANlwhkTlsXTZ6nwNNfZjfdNaCtPVY LKX06XGqjBHgdTuPUPSSufIILx3XLnc2Ja8nDFhMfzmplO7H70FgkTuY0KekESBX5NDT qbYxMV0eAjMATZyKp5YLVB7VhxMrXjUpc4r0Af8sEfplFsYgdYj7RPEfuliQsAA9CI9y HiITjfuAET5tHsN2MW0zWq1Z+9XL75g6Sp4IOyxPh6M6a651dXBsnYH3Vnxg7piFsfwz T67r0f2Qf78mu6vonnFKMd2zNmjAgiV08QNF1eSEI6MJjG92GaCgbLL3wdLLzM+fyhgc mhoQ==
MIME-Version: 1.0
X-Received: by 10.180.82.199 with SMTP id k7mr10371974wiy.34.1402969154116; Mon, 16 Jun 2014 18:39:14 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Mon, 16 Jun 2014 18:39:14 -0700 (PDT)
In-Reply-To: <20140616235540.GC2214@thunk.org>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org>
Date: Mon, 16 Jun 2014 21:39:14 -0400
X-Google-Sender-Auth: lFmgUwmhu6ng0RuQ7xBKPDZXX8w
Message-ID: <CAMm+LwgkHRymJVuRNV7PqcF8xjTH9o8zR_5qm5eHpfc2ZkGX7g@mail.gmail.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=f46d043bd7aa0fe5f804fbfe3679
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y1anq6ioOGyTQhKrT9aXx6LtQTE
Cc: Stephen Casner <casner@acm.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 01:39:17 -0000

--f46d043bd7aa0fe5f804fbfe3679
Content-Type: text/plain; charset=UTF-8

On Mon, Jun 16, 2014 at 7:55 PM, Theodore Ts'o <tytso@mit.edu> wrote:

> On Mon, Jun 16, 2014 at 02:33:09PM -0700, Stephen Casner wrote:
> > On Tue, 17 Jun 2014, Brian E Carpenter wrote:
> >
> > > I believe I am in a tiny, tiny minority by running my email
> > > client in 'plain text' mode unless I receive a message that is
> > > incomprehensible without setting 'original html' mode.
> >
> > I'm with you there.
>
> Ditto.  But whenver these sorts of discussions come up, it's always
> pointed out that engineers don't count when product managers are
> making their decisions.  :-(
>
>                         - Ted (who is using "mutt" and "offlineimap")
>
>
That behavior might be unusual but the default for Gmail is to not open
embedded images unless a particular sender has been whitelisted for that.

So not at all surprising that Webmail would rank lower on that mode of
measurement.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jun 16, 2014 at 7:55 PM, Theodore Ts&#39;o <span dir=3D"ltr=
">&lt;<a href=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit.edu</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On M=
on, Jun 16, 2014 at 02:33:09PM -0700, Stephen Casner wrote:<br>
&gt; On Tue, 17 Jun 2014, Brian E Carpenter wrote:<br>
&gt;<br>
&gt; &gt; I believe I am in a tiny, tiny minority by running my email<br>
&gt; &gt; client in &#39;plain text&#39; mode unless I receive a message th=
at is<br>
&gt; &gt; incomprehensible without setting &#39;original html&#39; mode.<br=
>
&gt;<br>
&gt; I&#39;m with you there.<br>
<br>
</div></div>Ditto. =C2=A0But whenver these sorts of discussions come up, it=
&#39;s always<br>
pointed out that engineers don&#39;t count when product managers are<br>
making their decisions. =C2=A0:-(<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 - Ted (who is using &quot;mutt&quot; and &quot;offlineimap&quot;=
)<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">That behavior might=
 be unusual but the default for Gmail is to not open embedded images unless=
 a particular sender has been whitelisted for that.</div><div class=3D"gmai=
l_extra">
<br></div><div class=3D"gmail_extra">So not at all surprising that Webmail =
would rank lower on that mode of measurement.</div></div>

--f46d043bd7aa0fe5f804fbfe3679--


From nobody Tue Jun 17 06:27:06 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4501A0383 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 06:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 zD9_A1aUC_u9 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 06:27:03 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5331D1A0382 for <ietf@ietf.org>; Tue, 17 Jun 2014 06:27:03 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WwtNX-000OON-J4; Tue, 17 Jun 2014 09:24:47 -0400
Date: Tue, 17 Jun 2014 09:26:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Message-ID: <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com>
In-Reply-To: <20140616235540.GC2214@thunk.org>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/k5ZxMxfiftb2fGO5FsrZRA_lAag
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 13:27:05 -0000

--On Monday, June 16, 2014 19:55 -0400 Theodore Ts'o
<tytso@mit.edu> wrote:

> On Mon, Jun 16, 2014 at 02:33:09PM -0700, Stephen Casner wrote:
>> On Tue, 17 Jun 2014, Brian E Carpenter wrote:
>> 
>> > I believe I am in a tiny, tiny minority by running my email
>> > client in 'plain text' mode unless I receive a message that
>> > is incomprehensible without setting 'original html' mode.
>> 
>> I'm with you there.
> 
> Ditto.  But whenver these sorts of discussions come up, it's
> always pointed out that engineers don't count when product
> managers are making their decisions.  :-(

To state that differently and perhaps more relevantly, many,
perhaps most, of the decisions about what to offer and support
are not made by product managers but by marketing product
designers who are more interested in whether something
demonstrates well and looks sexy than by, e.g., long-term
usability.   When criteria of those types are used, plain-text
email preferences will always lose, no matter how many of us (or
even non-engineers) prefer them for performance, security,
efficiency, or other reasons.

    john
 




From nobody Tue Jun 17 06:31:25 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E81A1A038A for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 06:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 hmCbTSHkNXLB for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 06:31:20 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 916371A0380 for <ietf@ietf.org>; Tue, 17 Jun 2014 06:31:20 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 744B71B8034 for <ietf@ietf.org>; Tue, 17 Jun 2014 06:31:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6971019005C; Tue, 17 Jun 2014 06:31:20 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Jun 2014 06:31:20 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com>
Date: Tue, 17 Jun 2014 09:31:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EpladVwN3lUwrbpswJP86ie4QKs
Cc: Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 13:31:24 -0000

On Jun 17, 2014, at 9:26 AM, John C Klensin <john-ietf@jck.com> wrote:
> When criteria of those types are used, plain-text
> email preferences will always lose, no matter how many of us (or
> even non-engineers) prefer them for performance, security,
> efficiency, or other reasons.

FWIW, non-flowing, non-indentable plain text is a royal PITA for me when =
I'm doing document reviews, so I have a lot of sympathy for those =
product managers.   The idea that indentation and flowable text can have =
security impacts is kind of sad.


From nobody Tue Jun 17 07:12:50 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED521A015A for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 07:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 UmARyPdMGgI2 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 07:12:40 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f41]) (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 EF8201A0037 for <ietf@ietf.org>; Tue, 17 Jun 2014 07:12:39 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:56023) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1Wwu7m-00017w-Po (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 17 Jun 2014 15:12:34 +0100
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1Wwu7l-0007fk-Qi (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 17 Jun 2014 15:12:33 +0100
Date: Tue, 17 Jun 2014 15:12:33 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
In-Reply-To: <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com>
Message-ID: <alpine.LSU.2.00.1406171510380.3035@hermes-1.csi.cam.ac.uk>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zGPA9dvevqBlaBpqHr9E1gTn2Jo
Cc: John C Klensin <john-ietf@jck.com>, Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 14:12:45 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:

> FWIW, non-flowing, non-indentable plain text is a royal PITA for me when
> I'm doing document reviews, so I have a lot of sympathy for those
> product managers.

It is a pity that Microsoft's refusal to implement RFC 2646 means that the
spec is pretty much unusable. Apple Mail used to support it but has
backed off to formatting each paragraph on one extremely long line.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Hebrides, Bailey: Westerly or southwesterly 4 or 5, occasionally 6 in Bailey.
Slight or moderate. Fog patches at first. Moderate or good, occasionally very
poor at first.


From nobody Tue Jun 17 08:05:18 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99E11A02D9; Mon, 16 Jun 2014 17:20:43 -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] autolearn=ham
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 ITTps2-HY1tx; Mon, 16 Jun 2014 17:20:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50BA91A02DB; Mon, 16 Jun 2014 17:20:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP: IETF Website Revamp
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140617002035.1959.10710.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jun 2014 17:20:35 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/86fPyWK-en8PMtlIah0mCp3yNro
X-Mailman-Approved-At: Tue, 17 Jun 2014 08:05:12 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: tmc@ietf-bids.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 00:20:45 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF, announces this 
Request for Proposals for a revamp of the IETF website, www.ietf.org.  The successful bidder 
will enter into a contract with the Internet Society.

The Internet Engineering Task Force (IETF) desires a revamp of its website to update the IETF's
 public-facing website, providing a "front door" for the IETF, including access to all the information 
that IETF participants need to accomplish their work.  Intended audiences include active participants, 
new or potential participants, and those looking to learn more about the IETF.  Goals include improving 
ease of navigation, accessibility by mobile devices, and content maintenance.

The RFP can be found at: <https://iaoc.ietf.org/rfps.html>.

Proposals must be received via email at tmc@ietf-bids.org no later than July 7, 2012.  All questions,
inquiries must be submitted by June 23, 2014.  Responses to questions and inquiries shall be posted 
online at:  <https://iaoc.ietf.org/rfps.html> by June 27, 2014. 

The point of contact regarding this RFP is the IETF Administrative Director, Ray Pelletier, iad@ietf.org.

Ray Pelletier
IAD


From nobody Tue Jun 17 08:05:20 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E8B1A00BD; Mon, 16 Jun 2014 17:27:21 -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] autolearn=ham
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 2a49eID5tHEV; Mon, 16 Jun 2014 17:27:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6689A1A0090; Mon, 16 Jun 2014 17:27:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP: IMAP Server
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140617002720.3827.63599.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jun 2014 17:27:20 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XFVEGOEcIiwDeRpDV9Rv_yHUyJo
X-Mailman-Approved-At: Tue, 17 Jun 2014 08:05:12 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: tmc@ietf-bids.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 00:27:22 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF, announces this 
Request for Proposals to develop the capability for IMAP browse and search of the IETF mail 
archives.  The successful bidder will enter into a contract with the Internet Society.

The IETF makes heavy use of email lists to conduct its work.  This often involves accessing the 
archived history of those email lists. Participants would like to have the ability to browse and search 
those archives using standard IMAP clients. The principal requirements for this access are captured 
in RFC 7017.  The service will use the set of archived messages maintained by the web-based 
browsing and archiving tool. That is the set that is being maintained for spam removal.

The RFP can be found at: <https://iaoc.ietf.org/rfps.html>.

Proposals must be received via email at tmc@ietf-bids.org no later than July 7, 2012.  All questions,
inquiries must be submitted by June 23, 2014.  Responses to questions and inquiries shall be posted 
online at:  <https://iaoc.ietf.org/rfps.html> by June 27, 2014. 

The point of contact regarding this RFP is the IETF Administrative Director, Ray Pelletier, iad@ietf.org.

Ray Pelletier
IAD


From nobody Tue Jun 17 08:24:42 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3C11A0066 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 08:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 0UJcJ7hN-4Gs for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 08:24:27 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE32D1A0391 for <ietf@ietf.org>; Tue, 17 Jun 2014 08:24:23 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5E2111B81CC for <ietf@ietf.org>; Tue, 17 Jun 2014 08:24:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 512CA19005C; Tue, 17 Jun 2014 08:24:23 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Jun 2014 08:24:23 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <alpine.LSU.2.00.1406171510380.3035@hermes-1.csi.cam.ac.uk>
Date: Tue, 17 Jun 2014 11:24:17 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <39608E69-2027-48F1-A1DC-9175C7A4C0E3@nominum.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <alpine.LSU.2.00.1406171510380.3035@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kMd8_fO9OHBZuDyrJ2ve9f6MgAA
Cc: John C Klensin <john-ietf@jck.com>, Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 15:24:33 -0000

On Jun 17, 2014, at 10:12 AM, Tony Finch <dot@dotat.at> wrote:
> It is a pity that Microsoft's refusal to implement RFC 2646 means that the
> spec is pretty much unusable. Apple Mail used to support it but has
> backed off to formatting each paragraph on one extremely long line.

Yup.


From nobody Tue Jun 17 08:51:56 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318691A0369 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 08:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 f73vi9-Ey3wz for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 08:51:50 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98AFE1A0340 for <ietf@ietf.org>; Tue, 17 Jun 2014 08:51:50 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Wwvdf-000OXg-4M; Tue, 17 Jun 2014 11:49:35 -0400
Date: Tue, 17 Jun 2014 11:51:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Message-ID: <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com>
In-Reply-To: <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dUKp0QqZYj-0D-USlKt__WQaQyE
Cc: Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 15:51:55 -0000

--On Tuesday, June 17, 2014 09:31 -0400 Ted Lemon
<ted.lemon@nominum.com> wrote:

> On Jun 17, 2014, at 9:26 AM, John C Klensin
> <john-ietf@jck.com> wrote:
>> When criteria of those types are used, plain-text
>> email preferences will always lose, no matter how many of us
>> (or even non-engineers) prefer them for performance, security,
>> efficiency, or other reasons.
> 
> FWIW, non-flowing, non-indentable plain text is a royal PITA
> for me when I'm doing document reviews, so I have a lot of
> sympathy for those product managers.   The idea that
> indentation and flowable text can have security impacts is
> kind of sad.

Red herring, I think.  As Tony pointed out, RFC 2646 is out
there, does work, and few if any of us who prefer plain text
mail to HTML have any problems with it.  When it is necessary,
I'm also willing to give up some convenience for enhanced
security and privacy.

The things that I think have security (or significant
operational) impacts include tracking beacons embedded in
messages to tell the sender (at least) when or if they were read
(privacy problem), embedded large images or text that is
automagically downloaded when the message is opened or earlier
(potential DoS attack), embedded malware and scripts of multiple
flavors even if not intentionally hostile, and so on.

It is probably too bad that Rich Text didn't get and keep
traction for those who want the ability to, e.g., color for
format text without exposing themselves to the risks above (and
others).  It is equally unfortunate that there are not more MUAs
around that can provide a reasonable interpretation of HTML
without following external links (either pull or push) or doing
anything else questionable without significant control by the
user.  But those things didn't happen.  I'd like to believe that
is because there isn't sufficient marketplace demand, but the
"sexy demo" and "designed for people who don't want to have to
either learn or think about their tools" issues at best distort
whatever demand might otherwise exist.

    john




From nobody Tue Jun 17 09:15:54 2014
Return-Path: <eckert@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD95F1A0085; Tue, 17 Jun 2014 09:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 4JReYTuwMVPj; Tue, 17 Jun 2014 09:15:49 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 630711A0079; Tue, 17 Jun 2014 09:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2802; q=dns/txt; s=iport; t=1403021747; x=1404231347; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=qubgx02B49Fdcim0gPOakeJCJSmDnFI2Ef17W47Koho=; b=SVPW/j6mGsubrn9IP1fcVjNNhajAaT+7otH0yZNAafXi0ZSIqUU+x+CP 21bUJS3sD1TUjxmbQbn5wBE3Rff6auVPDbadgjYbNXhgO8diMdsbSF0x8 Y3qLxyu4WD10o6aNnNHJUmpZs5cjT9lNoz+Ts9kk3nBdgw67M7JJANgSx 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuMGANhooFOtJV2U/2dsb2JhbABagw1Sql4BAQEBAQEFAZkmAYENFnWEAwEBAQQ6DzAQCxIGCSUPBTUVEohCyg4XhWOIJgsRAVAHgy2BFgSKP5ADAZNYg2AdL4EL
X-IronPort-AV: E=Sophos;i="5.01,494,1400025600"; d="scan'208";a="333533856"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-1.cisco.com with ESMTP; 17 Jun 2014 16:15:46 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s5HGFjXO002840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Jun 2014 16:15:45 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id s5HGFils016576; Tue, 17 Jun 2014 09:15:44 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s5HGFi3A016575; Tue, 17 Jun 2014 09:15:44 -0700
Date: Tue, 17 Jun 2014 09:15:44 -0700
From: Toerless Eckert <eckert@cisco.com>
To: ietf@ietf.org, tmc@ietf-bids.org
Subject: Re: RFP: IETF Website Revamp
Message-ID: <20140617161544.GD11315@cisco.com>
References: <20140617002035.1959.10710.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140617002035.1959.10710.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hOxlLny3dQgUW-P-hiZROad0a8Q
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 16:15:50 -0000

Oh whow...

Almost every time in the last few years that i have seen web pages
of other companies/organizations being "revamped", it ended up
being worse in before. I caution you to refine the requirements
to consider the following problems:

 - Loading must not be slower than now, especially not because of
   a lot of use of graphical elements. Consider large RTT performance
   testing results as a factor.
 - The ability to translate ietf pages via web based translate services
   must be equal or better than now. This btw also mean that
   graphical elements are NOT helpfull in general..
 - The quality of representation in lynx must be equal or better than now.
 - The ability to correctly view the content when zooming in/out in
   a browser must be equal or better than now. Some graphical
   SDKs start cutting of visible text when zooming in. Really bad.
 - The ability to print out web pages must be equal or better than now.
 - The version for mobile devices must not be just a subset of information,
   unless it is very easy to also get to the full set of information.

Btw: I think the current IETF pages are for me as a user compared
to all the other graphicrap out there pretty darn good to get real
work done. Which makes me especially nervuous when i hear revamp...

Cheers
    Toerless
   

On Mon, Jun 16, 2014 at 05:20:35PM -0700, IETF Administrative Director wrote:
> The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF, announces this 
> Request for Proposals for a revamp of the IETF website, www.ietf.org.  The successful bidder 
> will enter into a contract with the Internet Society.
> 
> The Internet Engineering Task Force (IETF) desires a revamp of its website to update the IETF's
>  public-facing website, providing a "front door" for the IETF, including access to all the information 
> that IETF participants need to accomplish their work.  Intended audiences include active participants, 
> new or potential participants, and those looking to learn more about the IETF.  Goals include improving 
> ease of navigation, accessibility by mobile devices, and content maintenance.
> 
> The RFP can be found at: <https://iaoc.ietf.org/rfps.html>.
> 
> Proposals must be received via email at tmc@ietf-bids.org no later than July 7, 2012.  All questions,
> inquiries must be submitted by June 23, 2014.  Responses to questions and inquiries shall be posted 
> online at:  <https://iaoc.ietf.org/rfps.html> by June 27, 2014. 
> 
> The point of contact regarding this RFP is the IETF Administrative Director, Ray Pelletier, iad@ietf.org.
> 
> Ray Pelletier
> IAD

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From nobody Tue Jun 17 09:39:10 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 148DB1A0066 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 09:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 uB27mQk0fiC5 for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 09:39:06 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A341A00A3 for <ietf@ietf.org>; Tue, 17 Jun 2014 09:39:06 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id j17so9046457oag.11 for <ietf@ietf.org>; Tue, 17 Jun 2014 09:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=NflIjrmqsZGh2IIJo5ZYLyjlXJZ7Q4MyqXvEf5IIP5E=; b=sb4Av9tDjsNT+uppJwTxM5w3yq1RF5+Aa9r/jct6Ih+U84xqzxJTHJBXw0w8ah3Kov DfzQiIqnfKoDf88yWSXhvskym9QjX3FvBfnYuM0qGBmsN2o7qlX76BvZf8q126uAl5+n Ne6SLyE+2WfErF8fHsqnpgYv0Y2ccBmgM/igFL38grRRjO0/VQ7dqpQAavt4dTC8LKNY ic+4OpMajMkVESG2S+2EmublMqdrSo5MiQCv3zWi1V/zMAmEh54CRBUZpoTEyhmECGxs Sx+quvhCpvc8dhOu5MkaF9Z3XcOQKYLHkoOgj/pzXzunXyCyjbSxJiBueYTFmlfZcqi3 +Usw==
X-Received: by 10.60.73.97 with SMTP id k1mr15866293oev.54.1403023145816; Tue, 17 Jun 2014 09:39:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.98.70 with HTTP; Tue, 17 Jun 2014 09:38:45 -0700 (PDT)
In-Reply-To: <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 17 Jun 2014 12:38:45 -0400
Message-ID: <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DrqGdz-wZ1jcYoXNsdnWxuoyWEQ
Cc: IETF <ietf@ietf.org>, Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 16:39:09 -0000

On Tue, Jun 17, 2014 at 11:51 AM, John C Klensin <john-ietf@jck.com> wrote:
> The things that I think have security (or significant
> operational) impacts include tracking beacons embedded in
> messages to tell the sender (at least) when or if they were read
> (privacy problem), embedded large images or text that is
> automagically downloaded when the message is opened or earlier
> (potential DoS attack), embedded malware and scripts of multiple
> flavors even if not intentionally hostile, and so on.

Yes, there are many traps for the average user on a MUA that tries
very hard to look spiffy. I like mutt ... but an alternative is to use
a GUI MUA that where you can keep its behavior conservative.
Thunderbird is not bad at that.


From nobody Tue Jun 17 09:58:04 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822191A00ED for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 09:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 kJMS2coNzMhM for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 09:57:59 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2301A00E7 for <ietf@ietf.org>; Tue, 17 Jun 2014 09:57:59 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 4C83BF3C01E; Tue, 17 Jun 2014 12:57:49 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id yM8KvAFoBOUa; Tue, 17 Jun 2014 12:57:24 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-144-77.washdc.fios.verizon.net [96.255.144.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7DBEEF2C0D1; Tue, 17 Jun 2014 12:57:24 -0400 (EDT)
Subject: Re: RFP: IETF Website Revamp
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20140617161544.GD11315@cisco.com>
Date: Tue, 17 Jun 2014 12:57:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <809BFD82-C80B-4E38-BFD6-896953809783@vigilsec.com>
References: <20140617002035.1959.10710.idtracker@ietfa.amsl.com> <20140617161544.GD11315@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V8GaWai6M6luHbU27PvDc66KTVg
Cc: IAOC Tools Mgmt Committee <tmc@ietf-bids.org>, IETF <ietf@ietf.org>, Chris Griffiths <cgriffiths@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 16:58:01 -0000

Toerless:

You know that the statement of work was sent out twice for review and =
comment.

=
https://mailarchive.ietf.org/arch/msg/ietf-announce/4hL91GT5za24PTS-LZ1M-z=
tAA6s
=
https://mailarchive.ietf.org/arch/msg/ietf-announce/o9csPR_gabYYiXBb-0kMQZ=
vM98c

These comments would have been much more useful at either of those =
times.

Russ


On Jun 17, 2014, at 12:15 PM, Toerless Eckert wrote:

> Oh whow...
>=20
> Almost every time in the last few years that i have seen web pages
> of other companies/organizations being "revamped", it ended up
> being worse in before. I caution you to refine the requirements
> to consider the following problems:
>=20
> - Loading must not be slower than now, especially not because of
>   a lot of use of graphical elements. Consider large RTT performance
>   testing results as a factor.
> - The ability to translate ietf pages via web based translate services
>   must be equal or better than now. This btw also mean that
>   graphical elements are NOT helpfull in general..
> - The quality of representation in lynx must be equal or better than =
now.
> - The ability to correctly view the content when zooming in/out in
>   a browser must be equal or better than now. Some graphical
>   SDKs start cutting of visible text when zooming in. Really bad.
> - The ability to print out web pages must be equal or better than now.
> - The version for mobile devices must not be just a subset of =
information,
>   unless it is very easy to also get to the full set of information.
>=20
> Btw: I think the current IETF pages are for me as a user compared
> to all the other graphicrap out there pretty darn good to get real
> work done. Which makes me especially nervuous when i hear revamp...
>=20
> Cheers
>    Toerless
>=20
>=20
> On Mon, Jun 16, 2014 at 05:20:35PM -0700, IETF Administrative Director =
wrote:
>> The IETF Administrative Oversight Committee (IAOC), on behalf of the =
IETF, announces this=20
>> Request for Proposals for a revamp of the IETF website, www.ietf.org. =
 The successful bidder=20
>> will enter into a contract with the Internet Society.
>>=20
>> The Internet Engineering Task Force (IETF) desires a revamp of its =
website to update the IETF's
>> public-facing website, providing a "front door" for the IETF, =
including access to all the information=20
>> that IETF participants need to accomplish their work.  Intended =
audiences include active participants,=20
>> new or potential participants, and those looking to learn more about =
the IETF.  Goals include improving=20
>> ease of navigation, accessibility by mobile devices, and content =
maintenance.
>>=20
>> The RFP can be found at: <https://iaoc.ietf.org/rfps.html>.
>>=20
>> Proposals must be received via email at tmc@ietf-bids.org no later =
than July 7, 2012.  All questions,
>> inquiries must be submitted by June 23, 2014.  Responses to questions =
and inquiries shall be posted=20
>> online at:  <https://iaoc.ietf.org/rfps.html> by June 27, 2014.=20
>>=20
>> The point of contact regarding this RFP is the IETF Administrative =
Director, Ray Pelletier, iad@ietf.org.
>>=20
>> Ray Pelletier
>> IAD
>=20
> --=20
> ---
> Toerless Eckert, eckert@cisco.com
> Cisco NSSTG Systems & Technology Architecture
> SDN: Let me play with the network, mommy!
>=20


From nobody Tue Jun 17 09:59:16 2014
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08BFC1A0340; Tue, 17 Jun 2014 09:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 C45F_rrn8Fv0; Tue, 17 Jun 2014 09:59:08 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 5738B1A00A7; Tue, 17 Jun 2014 09:58:58 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=gC+XdRVn1uG6hROqItW+p8BI0VkmJRYWYEERsnz6CKvhZqVeaXQ+Le35QDqMtrUF; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.46] (helo=elwamui-royal.atl.sa.earthlink.net) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Wwwin-0006S2-8g; Tue, 17 Jun 2014 12:58:57 -0400
Received: from 99.187.238.160 by webmail.earthlink.net with HTTP; Tue, 17 Jun 2014 12:58:56 -0400
Message-ID: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
Date: Tue, 17 Jun 2014 09:58:56 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Toerless Eckert <eckert@cisco.com>, ietf@ietf.org, tmc@ietf-bids.org
Subject: Re: RFP: IETF Website Revamp
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88864c4c3a38ce6fd8143f73def57a05c094d70610c3ef1cb32350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.46
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EVnylSuVA9lwvw3IVIlAvsokELs
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 16:59:11 -0000

Hi -

>From: Toerless Eckert <eckert@cisco.com>
>Sent: Jun 17, 2014 9:15 AM
>To: ietf@ietf.org, tmc@ietf-bids.org
>Cc: IETF Announcement List <ietf-announce@ietf.org>
>Subject: Re: RFP: IETF Website Revamp
>
>Oh whow...
>
>Almost every time in the last few years that i have seen web pages
>of other companies/organizations being "revamped", it ended up
>being worse in before.

Yes.

>I caution you to refine the requirements
>to consider the following problems:
>
> - Loading must not be slower than now, especially not because of
>   a lot of use of graphical elements. Consider large RTT performance
>   testing results as a factor.

Yes.

> - The ability to translate ietf pages via web based translate services
>   must be equal or better than now. This btw also mean that
>   graphical elements are NOT helpfull in general..

Yes.

> - The quality of representation in lynx must be equal or better than now.

Ok.  I wouldn't just single Lynx out...

> - The ability to correctly view the content when zooming in/out in
>   a browser must be equal or better than now. Some graphical
>   SDKs start cutting of visible text when zooming in. Really bad.

Yes.  In particular, it should not be necessary to zoom under
normal circumstances.  Using the "text size" setting of browsers
having such a feature should just work.

> - The ability to print out web pages must be equal or better than now.

Yes.

> - The version for mobile devices must not be just a subset of information,
>   unless it is very easy to also get to the full set of information.

Ok.

>Btw: I think the current IETF pages are for me as a user compared
>to all the other graphicrap out there pretty darn good to get real
>work done. Which makes me especially nervuous when i hear revamp...

Amen.  Though I'd still prefer the *previous* version of the
IETF website.  Much less cluttered.

Randy


From nobody Tue Jun 17 13:13:49 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 324CD1A0123; Tue, 17 Jun 2014 13:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 gRaS2KuyQ2SR; Tue, 17 Jun 2014 13:13:45 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9CAE1A011C; Tue, 17 Jun 2014 13:13:45 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id uo5so5785286pbc.40 for <multiple recipients>; Tue, 17 Jun 2014 13:13:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m9HrjuonYmOwCV2s2pG5XABSFHihHa3hOVcSE35EmkM=; b=OWPYTvORhV/trdkuXlmyEvWttkyTPifMov5O9toVHqSpqGKxNReuEfwhJSQMBhzV+W qLgYTBv4ocAwl0EUouwOnoQzRIADuM1JdjqxHfk67s2bI1lT8ioK+sWTmw0FnJiJVDCq s7RxVJWtiy+th3ns9/23nH+UlbMcBKUwpH1JbbY0+QN0yczOSnDKOyUaxy7GTWDaW8K1 OYP2fiFRiuvheX7iBym6irNtRA7ZX/QlY7cPFVaEZRoPKdyo5bDq/AXEEBvUx2We1mEX PLRkvHcT4cTfAt7dHoDUvfdolAyjhzdYoXmyfyaBjtDofsjszm3Nd+0qw++BNIrrP2qr lsxQ==
X-Received: by 10.68.139.36 with SMTP id qv4mr35793164pbb.82.1403036025364; Tue, 17 Jun 2014 13:13:45 -0700 (PDT)
Received: from [192.168.178.23] (171.198.69.111.dynamic.snap.net.nz. [111.69.198.171]) by mx.google.com with ESMTPSA id su8sm25388473pbc.72.2014.06.17.13.13.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Jun 2014 13:13:44 -0700 (PDT)
Message-ID: <53A0A17A.4000802@gmail.com>
Date: Wed, 18 Jun 2014 08:13:46 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: RFP: IETF Website Revamp
References: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
In-Reply-To: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wCtMcYTJnBC86MkkuYyru0yjuPU
Cc: tmc@ietf-bids.org, ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 20:13:47 -0000

On 18/06/2014 04:58, Randy Presuhn wrote:
...
>> Btw: I think the current IETF pages are for me as a user compared
>> to all the other graphicrap out there pretty darn good to get real
>> work done. Which makes me especially nervuous when i hear revamp...
> 
> Amen.  Though I'd still prefer the *previous* version of the
> IETF website.  Much less cluttered.

Why I use http://www.ietf.org/content.html

  Brian


From nobody Tue Jun 17 13:55:47 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED8CB1A015F for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 13:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 6CAALL5XFSyU for <ietf@ietfa.amsl.com>; Tue, 17 Jun 2014 13:55:41 -0700 (PDT)
Received: from listserv.winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 837C91A0154 for <ietf@ietf.org>; Tue, 17 Jun 2014 13:55:41 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2645; t=1403038535; h=Received:Received: Message-Id:From:Subject:Date:To:Organization:List-ID; bh=a8Xk7Mr CURunm/CDbFsl3CHEnJw=; b=KBvKScImIufzc1fBy1480+cMbfjmdWWu+/57CWm Vwqav2qKZFg2Ab6bzqArnWHPi2h25FHgtIUsYBx7rLP4Skd5mnO5cNPyO1E1W5Iu 0H7OZsxDRv5m2GL/BfaA9NWla65Zal//8Yvdy1J3DXvHSRq2v3IeJ7OpnzjDRYiL fizk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 17 Jun 2014 16:55:35 -0400
Received: from [192.168.1.67] (99-121-4-27.lightspeed.miamfl.sbcglobal.net [99.121.4.27]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2518650415.33238.2480; Tue, 17 Jun 2014 16:55:34 -0400
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E53ED61-5771-40ED-B6C4-EE3A8CD665C2@isdg.net>
X-Mailer: iPad Mail (11B651)
From: Hector Santos <hsantos@isdg.net>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Date: Tue, 17 Jun 2014 16:55:33 -0400
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iGjstSKFff5vI17r7JrJryEXX2Y
Cc: IETF <ietf@ietf.org>, Theodore Ts'o <tytso@mit.edu>, Stephen Casner <casner@acm.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 20:55:46 -0000

John,=20

We have a multi-portal framework where we all started as text only systems a=
nd it's been a moving target as a function of the evolution of the client de=
vices, and it continues to be a moving target.  There is no IETF "webmail" p=
rotocol, like we have for SMTP,  POP3, IMAP and NNTP.  If you want more cont=
rol, you offer online or native frontend/apps, otherwise you only have 822/2=
822/5322 has a common ground for independent 3rd party hosting client tools.=


When internet mail came, a Preserve MIME option was added. It was default of=
f and the sysop had control. Not the user.  All mail was transformed into th=
e native mail storage format, attachment separated. The web ui portal was gi=
ven view HTML/text only click if the mail was save in preserve mime mode.

When users began to roam using pop3, the pop3 server recreated the RFC x822 m=
ail for the pop3 download.  No WYSIWYG complaints for many years. Operators s=
et the Preserve Mime option on a case by case basis. Some operators with a h=
igher movement of roaming users, wrote scripts to set the option to true.=20=


As HTML, storage issues declined, more online viewing stripping of harmful H=
TML or images stuff was added, the Preserve Mime option was eventually provi=
ded as a user option. But today, it is still off by default.  That can chang=
e in a future ever evolving update.=20

We also have Preserve Mime options at the conference, mail, network type sto=
rage level. So for some NNTP gated emails or list storage areas,  it's prese=
rved and in others it's clean up as plain text.=20

Now today, if you had to do this over all again, what will be done?  Well, i=
t depends. There is good strategy that simple is better, just do it, no user=
 options, or save it for the future, forget about the stuff that was just ca=
ndy and never used, etc.  Some of the native Mail apps for these smart devic=
es are pretty primitive compared to their PC counterparts. Just look at twit=
ter and these other small footprint, 5% of what you already had reinventions=
, that are successful.

Nothing hasn't really change but the vendor need to single source these mult=
iple portals. It also depends on how performance is needed. Offloading speed=
s things up. Web based is stil a lot of overhead. HTML5 and web sockets will=
 give us more feel of a native client.

=46rom an IETF standpoint, probably an I-D for an web-based Mail I/O API, th=
en we can properly call it WebMail.


--
Hector Santos
http://www.santronics.com

> On Jun 17, 2014, at 11:51 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> work,


From nobody Wed Jun 18 00:05:48 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F88B1A001A; Wed, 18 Jun 2014 00:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 B6RWDtrZrOD6; Wed, 18 Jun 2014 00:05:41 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 331851A000F; Wed, 18 Jun 2014 00:05:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 545C21E5E76; Wed, 18 Jun 2014 00:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X8HGvKCr1gwa; Wed, 18 Jun 2014 00:05:02 -0700 (PDT)
Received: from [10.30.0.130] (unknown [83.150.71.93]) by c8a.amsl.com (Postfix) with ESMTPSA id 23F751E5E74; Wed, 18 Jun 2014 00:05:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: IETF-90 BoFs
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: IETF Chair <chair@ietf.org>
Date: Wed, 18 Jun 2014 10:05:36 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <532789EB-9C19-43EC-BBB3-682E90A868AD@ietf.org>
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DWuuQGGSshvYFFOTrW_TqJsg1aE
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF discussion list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 07:05:43 -0000

Once again we will have a long list of proposals for new working groups =
in Toronto. This article discusses those BoFs. Pointers to the relevant =
mailing lists are also included.

The success of any IETF effort, and new proposals in particular, depends =
on all of our ability to join and provide constructive feedback. So =
please join the efforts and contribute!

http://www.ietf.org/blog/2014/06/ietf-90-bofs/

Jari Arkko
IETF Chair


From nobody Wed Jun 18 06:12:17 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE0C1A01F6 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 06:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 D48sHa8PtdGU for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 06:12:10 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE0E1A0247 for <ietf@ietf.org>; Wed, 18 Jun 2014 06:12:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WxFce-0001Rj-9K for ietf@ietf.org; Wed, 18 Jun 2014 09:09:52 -0400
Date: Wed, 18 Jun 2014 09:12:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF <ietf@ietf.org>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Message-ID: <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com>
In-Reply-To: <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com> <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bXcN1vGgbn9YIMOYGMi7FgA60EA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 13:12:14 -0000

--On Tuesday, June 17, 2014 12:38 -0400 Scott Brim
<scott.brim@gmail.com> wrote:

> On Tue, Jun 17, 2014 at 11:51 AM, John C Klensin
> <john-ietf@jck.com> wrote:
>> The things that I think have security (or significant
>> operational) impacts include tracking beacons embedded in
>> messages to tell the sender (at least) when or if they were
>> read (privacy problem), embedded large images or text that is
>> automagically downloaded when the message is opened or earlier
>> (potential DoS attack), embedded malware and scripts of
>> multiple flavors even if not intentionally hostile, and so on.
> 
> Yes, there are many traps for the average user on a MUA that
> tries very hard to look spiffy. I like mutt ... but an
> alternative is to use a GUI MUA that where you can keep its
> behavior conservative. Thunderbird is not bad at that.

But not so good at some other things.

<mini-rant>

I use email heavily enough that I'd happily pay a hundred or two
USD a year for something that was optimized for IMAP desktop and
laptop use, that has good MIME support (not just patches on an
earlier approach), that was well-supported and whose design
enhanced or preserved my productivity. Wrt the latter, note that
I'm heavily dependent on IMAP disconnected mode and, like many
others here, have strong opinions about the importance of
controlled handling of HTML messages, controlled handling of
certs, S/MIME and PGP (both OpenPGP and legacy), and support for
other email and IMAP functionality that seems critical.   Now
that it is the middle of 2014, an MUA that didn't have full i18n
(aka "EAI") support wouldn't be worth the cost of conversion.
Perhaps unlike others, I'm a lot less concerned about close
calendar integration or inline support of a wide variety of
media types as long as I can quickly and easily extract body
parts to the local file system, get to them, and open them with
external programs.   Probably some other IETF users are in
similar situations.   But the evidence is that those who are
making product decisions don't believe we constitute a market on
which they can get adequate ROIs, so we periodically end up in
these almost-pointless "where is the action" discussions that
lead nowhere... except back to the conclusions that some people
are more or less happy with whatever they are using and that a
lot of people (who presumably don't deal with the combination of
very high mail volume and the periodic need to work offline) use
some flavor of "webmail".

Sad situation, IMO.
</rant>

     john





From nobody Wed Jun 18 07:12:13 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DCDA1A026E for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 07:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 qPaF5kbIld5b for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 07:12:08 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01001A0279 for <ietf@ietf.org>; Wed, 18 Jun 2014 07:12:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WxGYY-0001iR-3G; Wed, 18 Jun 2014 10:09:42 -0400
Date: Wed, 18 Jun 2014 10:11:51 -0400
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, Toerless Eckert <eckert@cisco.com>
Subject: Re: RFP: IETF Website Revamp
Message-ID: <67A24FDAE52544AB3BAEF9F4@JcK-HP8200.jck.com>
In-Reply-To: <809BFD82-C80B-4E38-BFD6-896953809783@vigilsec.com>
References: <20140617002035.1959.10710.idtracker@ietfa.amsl.com> <20140617161544.GD11315@cisco.com> <809BFD82-C80B-4E38-BFD6-896953809783@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FzfW4Cs5cXHF7ZDup8ee3I-I_Ac
Cc: IAOC Tools Mgmt Committee <tmc@ietf-bids.org>, IETF <ietf@ietf.org>, Chris Griffiths <cgriffiths@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 14:12:11 -0000

--On Tuesday, June 17, 2014 12:57 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> Toerless:
> 
> You know that the statement of work was sent out twice for
> review and comment.
> 
> https://mailarchive.ietf.org/arch/msg/ietf-announce/4hL91GT5za
> 24PTS-LZ1M-ztAA6s
> https://mailarchive.ietf.org/arch/msg/ietf-announce/o9csPR_gab
> YYiXBb-0kMQZvM98c
> 
> These comments would have been much more useful at either of
> those times.

Russ,

(1) Yes

(2) I believe that, other than reinforcing prior messages, there
is little or nothing in Torless's message that is actually new,
i.e., that did not appear in those prior rounds or that was
implied by comments that did appear then.

(3) It would have been really helpful had the IAOC or IAD chosen
to summarize what is different about the request/ SOW this time
relative to its predecessors.  As an equivalent, a summary by
the IAOC of its responses to comments on the prior draft SOWs
would have been helpful.  Either would have led, I believe, to a
much more focused discussion this time around.

best,
    john





From nobody Wed Jun 18 07:13:31 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2B41A0280 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 07:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 wZOoGqPYp1Hp for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 07:13:23 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11E2E1A026D for <ietf@ietf.org>; Wed, 18 Jun 2014 07:13:22 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so900011wgh.11 for <ietf@ietf.org>; Wed, 18 Jun 2014 07:13:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=C7Gc3fPGzPNdISrKa3TQDsRwvAncVYb5AsRhQ5FLyGc=; b=gKrd8Z2UJNlQRr062PlFB8lMHjFkICDPqBHg254Y3Xx9qlT4vzUI2Z14asPgaOST3D vTMr/4FAlPsEWX4lFOLVWKYtKu9t7bDqgcZBG5tuRsQpwcVlyGc2b/R5rrTuztg9LWEc ffYy7hNsn2azS/wiMtxAt0I1Cy+4WHuy5mHhrxcNleM10g6HqDQw/k5cr9kBRvJ8lUO9 plUcjTjUC0ATeMcL5unKIjSTD/dCymLAaE9ZHAWXfZqly9oB9iviEKFWB2FeUKpPWZay MdxGyVi1VbUOPsPhkC75/wVVsza4lOri1dibcewKEIS7CGp7IiH1BaRFJtIN8mBmT7Z+ 6YfQ==
MIME-Version: 1.0
X-Received: by 10.180.38.107 with SMTP id f11mr5591034wik.59.1403100801455; Wed, 18 Jun 2014 07:13:21 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Wed, 18 Jun 2014 07:13:21 -0700 (PDT)
In-Reply-To: <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com>
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com> <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com> <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com>
Date: Wed, 18 Jun 2014 10:13:21 -0400
X-Google-Sender-Auth: 42p3adNHsiqcfk9lIrFzGrNqPqM
Message-ID: <CAMm+LwhGMEkF=EgjsS_b0AVZUvkB3ueA=LCG+drr9xfH-jjv5A@mail.gmail.com>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=e89a8f643354dd1a0a04fc1cdc3f
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZWv1vrKlKpgynRIQfO1HeicHaqQ
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 14:13:25 -0000

--e89a8f643354dd1a0a04fc1cdc3f
Content-Type: text/plain; charset=UTF-8

On Wed, Jun 18, 2014 at 9:12 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, June 17, 2014 12:38 -0400 Scott Brim
> <scott.brim@gmail.com> wrote:
>
> > On Tue, Jun 17, 2014 at 11:51 AM, John C Klensin
> > <john-ietf@jck.com> wrote:
> >> The things that I think have security (or significant
> >> operational) impacts include tracking beacons embedded in
> >> messages to tell the sender (at least) when or if they were
> >> read (privacy problem), embedded large images or text that is
> >> automagically downloaded when the message is opened or earlier
> >> (potential DoS attack), embedded malware and scripts of
> >> multiple flavors even if not intentionally hostile, and so on.
> >
> > Yes, there are many traps for the average user on a MUA that
> > tries very hard to look spiffy. I like mutt ... but an
> > alternative is to use a GUI MUA that where you can keep its
> > behavior conservative. Thunderbird is not bad at that.
>
> But not so good at some other things.
>
> <mini-rant>
>
> I use email heavily enough that I'd happily pay a hundred or two
> USD a year for something that was optimized for IMAP desktop and
> laptop use, that has good MIME support (not just patches on an
> earlier approach),

..

> . except back to the conclusions that some people
> are more or less happy with whatever they are using and that a
> lot of people (who presumably don't deal with the combination of
> very high mail volume and the periodic need to work offline) use
> some flavor of "webmail".
>
> Sad situation, IMO.
> </rant>
>

I am still looking for a calendar program written by someone who
understands that there are multiple time zones and that when I travel from
one time zone to another I probably want to get up at different times etc
without having the change affect appointments when I return.

Seriously, is it so difficult for someone to understand that when setting a
recurring appointment it is necessary to be able to specify the time zone
so that the correct daylight savings adjustments are made?

I gave up waiting for those features in Outlook after waiting ten years.
But they do indicate just how 'STUCK' software gets.

I don't know why such obviously necessary features don't get into product
but I am pretty sure the 'security' and 'usability' are the reasons we are
stuck with insecure and hard to use products. Whenever a product group has
a requirement that they aren't up to hacking they will squawk 'security' or
'usability' as the reason.

It is the same here, someone will suggest ending some feature and someone
will pop up saying that it is absolutely essential to keep it going because
it is necessary to support the mail system in Timbuktu which still runs on
DEC10s talking UUCP. And of course the guy who actually lives in Timbuktu
is protesting that they are pretty sure they never had any DEC 10s to start
with and they mostly run Ubuntu.


As for being a low volume mail user, I am currently using 10Gb of my 15Gb
free Gmail allowance. The reason I use Gmail to do my IETF mail is that I
can't wait half an hour for IMAP or POP to sync each time I want to read
mail.

I don't give my work email out nearly as often as my gmail account which
means that I get my corporate email in an acceptable length of time.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Jun 18, 2014 at 9:12 AM, John C Klensin <span dir=3D"ltr">&=
lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><br>
<br>
--On Tuesday, June 17, 2014 12:38 -0400 Scott Brim<br>
<div><div class=3D"h5">&lt;<a href=3D"mailto:scott.brim@gmail.com">scott.br=
im@gmail.com</a>&gt; wrote:<br>
<br>
&gt; On Tue, Jun 17, 2014 at 11:51 AM, John C Klensin<br>
&gt; &lt;<a href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; wro=
te:<br>
&gt;&gt; The things that I think have security (or significant<br>
&gt;&gt; operational) impacts include tracking beacons embedded in<br>
&gt;&gt; messages to tell the sender (at least) when or if they were<br>
&gt;&gt; read (privacy problem), embedded large images or text that is<br>
&gt;&gt; automagically downloaded when the message is opened or earlier<br>
&gt;&gt; (potential DoS attack), embedded malware and scripts of<br>
&gt;&gt; multiple flavors even if not intentionally hostile, and so on.<br>
&gt;<br>
&gt; Yes, there are many traps for the average user on a MUA that<br>
&gt; tries very hard to look spiffy. I like mutt ... but an<br>
&gt; alternative is to use a GUI MUA that where you can keep its<br>
&gt; behavior conservative. Thunderbird is not bad at that.<br>
<br>
</div></div>But not so good at some other things.<br>
<br>
&lt;mini-rant&gt;<br>
<br>
I use email heavily enough that I&#39;d happily pay a hundred or two<br>
USD a year for something that was optimized for IMAP desktop and<br>
laptop use, that has good MIME support (not just patches on an<br>
earlier approach), </blockquote><div>..=C2=A0<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">. e=
xcept back to the conclusions that some people<br>

are more or less happy with whatever they are using and that a<br>
lot of people (who presumably don&#39;t deal with the combination of<br>
very high mail volume and the periodic need to work offline) use<br>
some flavor of &quot;webmail&quot;.<br>
<br>
Sad situation, IMO.<br>
&lt;/rant&gt;<br></blockquote><div><br></div><div>I am still looking for a =
calendar program written by someone who understands that there are multiple=
 time zones and that when I travel from one time zone to another I probably=
 want to get up at different times etc without having the change affect app=
ointments when I return.</div>
<div><br></div><div>Seriously, is it so difficult for someone to understand=
 that when setting a recurring appointment it is necessary to be able to sp=
ecify the time zone so that the correct daylight savings adjustments are ma=
de?</div>
<div><br></div><div>I gave up waiting for those features in Outlook after w=
aiting ten years. But they do indicate just how &#39;STUCK&#39; software ge=
ts.</div><div><br></div><div>I don&#39;t know why such obviously necessary =
features don&#39;t get into product but I am pretty sure the &#39;security&=
#39; and &#39;usability&#39; are the reasons we are stuck with insecure and=
 hard to use products. Whenever a product group has a requirement that they=
 aren&#39;t up to hacking they will squawk &#39;security&#39; or &#39;usabi=
lity&#39; as the reason.</div>
<div><br></div><div>It is the same here, someone will suggest ending some f=
eature and someone will pop up saying that it is absolutely essential to ke=
ep it going because it is necessary to support the mail system in Timbuktu =
which still runs on DEC10s talking UUCP. And of course the guy who actually=
 lives in Timbuktu is protesting that they are pretty sure they never had a=
ny DEC 10s to start with and they mostly run Ubuntu.</div>
<div><br></div><div><br></div><div>As for being a low volume mail user, I a=
m currently using 10Gb of my 15Gb free Gmail allowance. The reason I use Gm=
ail to do my IETF mail is that I can&#39;t wait half an hour for IMAP or PO=
P to sync each time I want to read mail.</div>
<div><br></div><div>I don&#39;t give my work email out nearly as often as m=
y gmail account which means that I get my corporate email in an acceptable =
length of time.</div></div></div></div>

--e89a8f643354dd1a0a04fc1cdc3f--


From nobody Wed Jun 18 08:30:00 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3081A0263 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 08:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 5-36z1dH-I6w for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 08:29:44 -0700 (PDT)
Received: from secure.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 97E401A025C for <ietf@ietf.org>; Wed, 18 Jun 2014 08:29:43 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2690; t=1403105377; h=Received:Received: Message-Id:From:Subject:Date:To:Organization:List-ID; bh=oJ636oj MkDSs3WRmTzTSwvE4eaQ=; b=Np2WjLV3LE5lCyzTBquDrjUhw2FM4erwBVhvxfl cNqB9+E5Bc6SQAL5gIOuvCOG08V3qmPGSWDcRe6FPSlCPMqsrG+yTfWd89bgyKz/ 5+Ydv13KkjCEcoLa3DWeWruK9hnEXnITi1eN5xkM4lSw6xc+0vA7VSDOOZb5Hd8o FKbc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 18 Jun 2014 11:29:37 -0400
Received: from [192.168.1.162] (99-72-160-212.lightspeed.miamfl.sbcglobal.net [99.72.160.212]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2585492507.34700.4912; Wed, 18 Jun 2014 11:29:36 -0400
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com> <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com> <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <60A8D6B4-4456-41B9-8DBB-33D586F7F7FD@isdg.net>
X-Mailer: iPad Mail (11B651)
From: Hector Santos <hsantos@isdg.net>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Date: Wed, 18 Jun 2014 11:29:33 -0400
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/p-sOPpmLS2teHyndjUSNAsFF3hQ
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 15:29:51 -0000

> On Jun 18, 2014, at 9:12 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> --On Tuesday, June 17, 2014 12:38 -0400 Scott Brim
>>=20
>> Yes, there are many traps for the average user on a MUA that
>> tries very hard to look spiffy. I like mutt ... but an
>> alternative is to use a GUI MUA that where you can keep its
>> behavior conservative. Thunderbird is not bad at that.
>=20
> But not so good at some other things.
>=20
> <mini-rant>
> ........ But the evidence is that those who are
> making product decisions don't believe we constitute a market on
> which they can get adequate ROIs, so we periodically end up in
> these almost-pointless "where is the action" discussions that
> lead nowhere... except back to the conclusions that some people
> are more or less happy with whatever they are using and that a
> lot of people (who presumably don't deal with the combination of
> very high mail volume and the periodic need to work offline) use
> some flavor of "webmail".
>=20
> Sad situation, IMO.
> </rant>
>=20

+1,  it is a very expensive integrated, moving target design issue, especial=
ly for smaller operations.  It pays to picky and choose, be conservative wit=
h incremental changes, when you already have an established base of differ m=
ulti-portal needs.  Honestly, we haven't really had another good top notch i=
ntegrated IETF technologies RFC that puts it all together ala what RFC1123 (=
STD3) did for integrated internet protocols application hosting systems.  At=
 that point, the applications developers will have a better handle of what n=
eeds to be done.  The mail related RFCs these days written mostly by same us=
ual folks, tend to be overly verbally complex, confusing, ambiguous, too ope=
n ended, and if I may say, not always "protocol complete" from an integratio=
n standpoint.=20

Personally, I use a mix of MUAs, and it's changes depending on what's going o=
n. Right now, relaxing at a pool, with my new iPad mail app. It has absolute=
ly no display rending options that it can see and the other day I wanted to s=
ee a message in fix font mode, so I switched over to the web interface with s=
afari, a 1996 web ui design that still works but needs to be streamlined for=
 the new smaller, keyboard less device environments, with lesser real estate=
 to display, less needs to over do it with display options.=20

With the INTL stuff,  I'm still catching up to this, but overall, adding fun=
ctional UTF wrappers around the field displays, etc and this is only being d=
one at the web ui. With the other legacy views, you see the UTF prefixes, et=
c.

--
Hector Santos
http://www.santronics.com



From nobody Wed Jun 18 08:45:38 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 514691A0297 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 08:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 WupL6ovyeulj for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 08:45:35 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED471A0087 for <ietf@ietf.org>; Wed, 18 Jun 2014 08:45:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 7891ECC097 for <ietf@ietf.org>; Wed, 18 Jun 2014 11:45:34 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ikczav-hTbD0 for <ietf@ietf.org>; Wed, 18 Jun 2014 11:45:25 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 9B49CCC09D for <ietf@ietf.org>; Wed, 18 Jun 2014 11:45:25 -0400 (EDT)
Message-ID: <53A1B414.7090503@meetinghouse.net>
Date: Wed, 18 Jun 2014 11:45:24 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1
MIME-Version: 1.0
CC: IETF <ietf@ietf.org>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com> <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com> <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com> <CAMm+LwhGMEkF=EgjsS_b0AVZUvkB3ueA=LCG+drr9xfH-jjv5A@mail.gmail.com>
In-Reply-To: <CAMm+LwhGMEkF=EgjsS_b0AVZUvkB3ueA=LCG+drr9xfH-jjv5A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qxoNnCvM-ZdRSJ1Qtrbf5MXaZcw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 15:45:36 -0000

Phillip Hallam-Baker wrote:
>
> I am still looking for a calendar program written by someone who 
> understands that there are multiple time zones and that when I travel 
> from one time zone to another I probably want to get up at different 
> times etc without having the change affect appointments when I return.
>
> Seriously, is it so difficult for someone to understand that when 
> setting a recurring appointment it is necessary to be able to specify 
> the time zone so that the correct daylight savings adjustments are made?
>
> I gave up waiting for those features in Outlook after waiting ten 
> years. But they do indicate just how 'STUCK' software gets.

That's odd - time zones and daylight savings time just seem to work in 
all the calendars that I use -  (including Outlook and my out-of-the-box 
Android smartphone)

>
> As for being a low volume mail user, I am currently using 10Gb of my 
> 15Gb free Gmail allowance. The reason I use Gmail to do my IETF mail 
> is that I can't wait half an hour for IMAP or POP to sync each time I 
> want to read mail.
>
> I don't give my work email out nearly as often as my gmail account 
> which means that I get my corporate email in an acceptable length of time.

Hmmm.... my mailbox alone gets maybe 5000 emails a day - a lot of it 
spam of course, but a lot of list traffic and admin messages (I'm 
postmaster for our system as well as admin for a bunch of email 
lists).   The mail on my laptop client (SeaMonkey) and my smartphone are 
pretty much always up to date, and if I boot my laptop cold, a few 
thousand messages will update within a minute or so.  If it takes you 
half an hour to sync IMAP then you're doing something very wrong.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Jun 18 10:24:51 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D7C1A0051 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 10:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 Ugy1XjNTpUfW for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 10:24:46 -0700 (PDT)
Received: from ntbbs.santronics.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 59A101A004A for <ietf@ietf.org>; Wed, 18 Jun 2014 10:24:46 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=841; t=1403112277; h=Received:Received: Message-Id:From:Subject:Date:To:Organization:List-ID; bh=Z1kYZwj Iw/SP7EZIbHX/Zkq3H74=; b=Lsve1MgBRv76G9m8HP8ZtKYy67uIYBX+6/w0cGX h2sYHYTVaeZ0c1BpED/sOXzlsesxqhwUXRoEoMLDwp+mEeYZj/AgDkIXYidSFoSm L/eJP0Nta14YiQTa4OqKFEKIofXM32A22moHrPoPvmbA0n9x8X3egJRUzEK8Qgx/ VGzE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 18 Jun 2014 13:24:37 -0400
Received: from [192.168.1.162] (99-72-160-212.lightspeed.miamfl.sbcglobal.net [99.72.160.212]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2592392587.34700.328; Wed, 18 Jun 2014 13:24:37 -0400
References: <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <01P8ZV7PHO8M0049PU@mauve.mrochek.com> <539CAD2E.6030805@gmail.com> <01P907G00ESM0049PU@mauve.mrochek.com> <539F5828.60403@gmail.com> <alpine.OSX.2.19.9991.1406161432260.11755@auge.gateway.2wire.net> <20140616235540.GC2214@thunk.org> <6C327290EAFAB2FEE15F5FA9@JcK-HP8200.jck.com> <2FC96FA4-5EF0-4F0A-9E3E-5DD42BEA8A25@nominum.com> <62BB2DC3A8B0A3A93833E5C5@JcK-HP8200.jck.com> <CAPv4CP_M0O0vhGRJm9NF+1G1RYPtPG_L86Oz2x=0nUa=ANymkA@mail.gmail.com> <568D757BC9C61D83B86AA45D@JcK-HP8200.jck.com> <CAMm+LwhGMEkF=EgjsS_b0AVZUvkB3ueA=LCG+drr9xfH-jjv5A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAMm+LwhGMEkF=EgjsS_b0AVZUvkB3ueA=LCG+drr9xfH-jjv5A@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <28917025-969E-45EA-9261-40E9BB85EAA9@isdg.net>
X-Mailer: iPad Mail (11B651)
From: Hector Santos <hsantos@isdg.net>
Subject: Re: email client popularity [was Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)]
Date: Wed, 18 Jun 2014 13:24:34 -0400
To: Phillip Hallam-Baker <phill@hallambaker.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6fuuDYaRvXmkW8HcpTSfgiGPHXg
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 17:24:49 -0000

> On Jun 18, 2014, at 10:13 AM, Phillip Hallam-Baker <phill@hallambaker.com>=
 wrote:
>=20
> As for being a low volume mail user, I am currently using 10Gb of my 15Gb f=
ree Gmail allowance. The reason I use Gmail to do my IETF mail is that I can=
't wait half an hour for IMAP or POP to sync each time I want to read mail.
>=20

That should only be an issue the first time.  And the only thing that I can s=
ee off-hand with pop3 is if the client is not issuing the server update comm=
and with is QUIT.  In other words, your device mail app and/or connectivity i=
s dropping rather than gracefully closing then session.  The explicitly issu=
ed  QUIT command is the only way the server to know you successful got your m=
ail and can begin some backend marking of reception.  =20

--
Hector Santos
http://www.santronics.com=


From nobody Wed Jun 18 13:25:13 2014
Return-Path: <markr@signal100.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8001A0307 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 13:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.589
X-Spam-Level: **
X-Spam-Status: No, score=2.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, HOST_EQ_BROADBND=1.118, HOST_MISMATCH_COM=0.311, RCVD_IN_BRBL_LASTEXT=1.449, TVD_FROM_1=1] autolearn=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 ly6H5Mz9Jjfl for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 13:25:09 -0700 (PDT)
Received: from mail.signal100.net (5751e297.skybroadband.com [87.81.226.151]) by ietfa.amsl.com (Postfix) with ESMTP id 459281A0306 for <ietf@ietf.org>; Wed, 18 Jun 2014 13:25:08 -0700 (PDT)
Received: from [192.168.1.7] ([87.81.226.151]) by mail.signal100.net with MailEnable ESMTP; Wed, 18 Jun 2014 21:25:05 +0100
Message-ID: <53A1F5AD.1020500@signal100.com>
Date: Wed, 18 Jun 2014 21:25:17 +0100
From: Mark Rousell <markr@signal100.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net> <CAMm+LwhTtwfFtfXQjha95gY-tp6DQbuwudMg1ZXOBuGuJ7zirA@mail.gmail.com>
In-Reply-To: <CAMm+LwhTtwfFtfXQjha95gY-tp6DQbuwudMg1ZXOBuGuJ7zirA@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=C9C5C162; url=pool.sks-keyservers.net
X-TagToolbar-Keys: D20140618212517206
X-Face: $zr)h.c^+kI[-MYu+^_?xDRQ9E)8LKzRjKW76[lp$}`FEOs&DG-YCaQ_(Itx~w1tWa8:~)d[EOaxV8puV&Faq, .e{1{81"OD"9] 5nfHo<`n3Hguzpw}7%8__`Zi^~"jowiAw(duc(c3BCv']#@Fd6~g@; e[*,i`9L; $ZfR8EShV%%W'B; ]
X-MailList-Post: Yes
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3cNkRglBxcU1K9N4-QcqxpK0kQY
Cc: Phillip Hallam-Baker <phill@hallambaker.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 20:25:11 -0000

On 14/06/2014 16:26, Phillip Hallam-Baker wrote:
> But even taking this as a given, it seems that every time that I go to a
> blog with a comments form on using my iPhone the provider is trying to
> push a 'stream reader' app at me. It might be that these people will
> only push a proprietary app but I think it likely that they would be
> interested in an open standard if one was on offer.

I suspect that for the most part they'd only be interested in an open
standard if it could reliably push adverts as part of the content and
generate reliably trackable page views from the adverts.

It seems to me that the re-siloisation of data has been driven by
commercial interests predicated on the hope of profit from
reader/customer lock-in and advertising revenue.

Open standards seem to me to tend in general to be incompatible with
advertising-based commercialisation in this context.



-- 
Mark Rousell

PGP public key: http://www.signal100.com/markr/pgp
Key ID: C9C5C162
 
 
 


From nobody Wed Jun 18 17:39:22 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 729B41A033E for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 17:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
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 vCCOjQYlj-E7 for <ietf@ietfa.amsl.com>; Wed, 18 Jun 2014 17:39:14 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24AE21A033B for <ietf@ietf.org>; Wed, 18 Jun 2014 17:39:14 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id hw13so1361118qab.20 for <ietf@ietf.org>; Wed, 18 Jun 2014 17:39:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XF+9DbdZIJ00V1uQipbpwakkqiQT8EYkAiEuY8gte4A=; b=MxxSzfRBwWMo/3zMlxykzwLzroGiut+Xoy/1f67S5Gy+1gI3TivutwhVeGF2EMeON/ thshtTpFv0JFy6C/ZS7yLTgvzCzvkwsGcKRcxGX4ZQMkb1Uqzf1ecg4SfsMU62PtFJZo 2RSD/Et9rP167maPDXGfl1b5dOqusMHfGFhhrWwzv7KAvL85ZBTMPHjDcfmaVLx9ktsr HMNTVlf4dhvPgwMd9bZyVp/J9ibQ1ltqAzbOoLaDQdcVV5FD0R3gJc8FKtMYgXFRYpNe pFxuLPnPervMXwjo9SKC7OQdgeW2R+bWapY15Y4BUlNJ3eI5GVuBNr+iPqRmKTC61O6G retQ==
X-Gm-Message-State: ALoCoQkH62VYU7BcxeB/NwgzsPH0c8681LQEwhYkrssJNO2SyHJwz9BroETm7FAQeX2wQ0du9ZXX
MIME-Version: 1.0
X-Received: by 10.140.41.113 with SMTP id y104mr2218687qgy.34.1403138353250; Wed, 18 Jun 2014 17:39:13 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Wed, 18 Jun 2014 17:39:13 -0700 (PDT)
In-Reply-To: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
References: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
Date: Wed, 18 Jun 2014 17:39:13 -0700
Message-ID: <CABCOCHQeP69F-3pJBhX58rDN9oQ3x40zOYQ=0uGNkvWPw7zGgQ@mail.gmail.com>
Subject: Re: RFP: IETF Website Revamp
From: Andy Bierman <andy@yumaworks.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=001a11c121b01dec4804fc259b6b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/r8WTbQTLLbz-Hr-z5Y6f_BkgnZU
Cc: tmc@ietf-bids.org, IETF discussion list <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2014 00:39:16 -0000

--001a11c121b01dec4804fc259b6b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 17, 2014 at 9:58 AM, Randy Presuhn <randy_presuhn@mindspring.com
> wrote:

> Hi -
>
> >From: Toerless Eckert <eckert@cisco.com>
> >Sent: Jun 17, 2014 9:15 AM
> >To: ietf@ietf.org, tmc@ietf-bids.org
> >Cc: IETF Announcement List <ietf-announce@ietf.org>
> >Subject: Re: RFP: IETF Website Revamp
> >
> >Oh whow...
> >
> >Almost every time in the last few years that i have seen web pages
> >of other companies/organizations being "revamped", it ended up
> >being worse in before.
>
> Yes.
>


I think the IETF WEB site is getting better over time, especially wrt/
auto-generated links to tools on various pages. (Thank you tools team! :-)



> >I caution you to refine the requirements
> >to consider the following problems:
> >
> > - Loading must not be slower than now, especially not because of
> >   a lot of use of graphical elements. Consider large RTT performance
> >   testing results as a factor.
>
> Yes.
>
>

Sure, but if there are better auto-generated navigation links, perhaps you
find the right content in 2 clicks instead of 3 and save a page load.
Faster user experience is more than individual RTT.



Andy



> - The ability to translate ietf pages via web based translate services
> >   must be equal or better than now. This btw also mean that
> >   graphical elements are NOT helpfull in general..
>
> Yes.


> > - The quality of representation in lynx must be equal or better than now.
>
> Ok.  I wouldn't just single Lynx out...
>
> > - The ability to correctly view the content when zooming in/out in
> >   a browser must be equal or better than now. Some graphical
> >   SDKs start cutting of visible text when zooming in. Really bad.
>
> Yes.  In particular, it should not be necessary to zoom under
> normal circumstances.  Using the "text size" setting of browsers
> having such a feature should just work.
>
> > - The ability to print out web pages must be equal or better than now.
>
> Yes.
>
> > - The version for mobile devices must not be just a subset of
> information,
> >   unless it is very easy to also get to the full set of information.
>
> Ok.
>
> >Btw: I think the current IETF pages are for me as a user compared
> >to all the other graphicrap out there pretty darn good to get real
> >work done. Which makes me especially nervuous when i hear revamp...
>
> Amen.  Though I'd still prefer the *previous* version of the
> IETF website.  Much less cluttered.
>
> Randy
>
>

--001a11c121b01dec4804fc259b6b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 17, 2014 at 9:58 AM, Randy Presuhn <span dir=3D"ltr">&l=
t;<a href=3D"mailto:randy_presuhn@mindspring.com" target=3D"_blank">randy_p=
resuhn@mindspring.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi -<br>
<br>
&gt;From: Toerless Eckert &lt;<a href=3D"mailto:eckert@cisco.com">eckert@ci=
sco.com</a>&gt;<br>
&gt;Sent: Jun 17, 2014 9:15 AM<br>
&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>, <a href=3D"mail=
to:tmc@ietf-bids.org">tmc@ietf-bids.org</a><br>
&gt;Cc: IETF Announcement List &lt;<a href=3D"mailto:ietf-announce@ietf.org=
">ietf-announce@ietf.org</a>&gt;<br>
&gt;Subject: Re: RFP: IETF Website Revamp<br>
&gt;<br>
&gt;Oh whow...<br>
&gt;<br>
&gt;Almost every time in the last few years that i have seen web pages<br>
&gt;of other companies/organizations being &quot;revamped&quot;, it ended u=
p<br>
&gt;being worse in before.<br>
<br>
Yes.<br></blockquote><div><br></div><div><br></div><div>I think the IETF WE=
B site is getting better over time, especially wrt/</div><div>auto-generate=
d links to tools on various pages. (Thank you tools team! :-)</div><div>
<br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;I caution you to refine the requirements<br>
&gt;to consider the following problems:<br>
&gt;<br>
&gt; - Loading must not be slower than now, especially not because of<br>
&gt; =A0 a lot of use of graphical elements. Consider large RTT performance=
<br>
&gt; =A0 testing results as a factor.<br>
<br>
Yes.<br>
<br></blockquote><div><br></div><div><br></div><div>Sure, but if there are =
better auto-generated navigation links, perhaps you</div><div>find the righ=
t content in 2 clicks instead of 3 and save a page load.</div><div>Faster u=
ser experience is more than individual RTT.</div>
<div><br></div><div><br></div><div><br></div><div>Andy</div><div><br></div>=
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt; - The ability to translate ietf pages via web based translate services=
<br>
&gt; =A0 must be equal or better than now. This btw also mean that<br>
&gt; =A0 graphical elements are NOT helpfull in general..<br>
<br>
Yes.</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; - The quality of representation in lynx must be equal or better than n=
ow.<br>
<br>
Ok. =A0I wouldn&#39;t just single Lynx out...<br>
<br>
&gt; - The ability to correctly view the content when zooming in/out in<br>
&gt; =A0 a browser must be equal or better than now. Some graphical<br>
&gt; =A0 SDKs start cutting of visible text when zooming in. Really bad.<br=
>
<br>
Yes. =A0In particular, it should not be necessary to zoom under<br>
normal circumstances. =A0Using the &quot;text size&quot; setting of browser=
s<br>
having such a feature should just work.<br>
<br>
&gt; - The ability to print out web pages must be equal or better than now.=
<br>
<br>
Yes.<br>
<br>
&gt; - The version for mobile devices must not be just a subset of informat=
ion,<br>
&gt; =A0 unless it is very easy to also get to the full set of information.=
<br>
<br>
Ok.<br>
<br>
&gt;Btw: I think the current IETF pages are for me as a user compared<br>
&gt;to all the other graphicrap out there pretty darn good to get real<br>
&gt;work done. Which makes me especially nervuous when i hear revamp...<br>
<br>
Amen. =A0Though I&#39;d still prefer the *previous* version of the<br>
IETF website. =A0Much less cluttered.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Randy<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a11c121b01dec4804fc259b6b--


From nobody Thu Jun 19 11:03:06 2014
Return-Path: <Valdis.Kletnieks@vt.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBC71A0249; Thu, 19 Jun 2014 11:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 P3lU1eT1IkrX; Thu, 19 Jun 2014 11:03:03 -0700 (PDT)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D95A1A00B1; Thu, 19 Jun 2014 11:03:03 -0700 (PDT)
Received: from mr6.cc.vt.edu (mr6.cc.vt.edu [198.82.141.20]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id s5JI2UnV024514; Thu, 19 Jun 2014 14:02:30 -0400
Received: from auth1.smtp.vt.edu (auth1.smtp.vt.edu [198.82.161.152] (may be forged)) by mr6.cc.vt.edu (8.14.4/8.14.4) with ESMTP id s5JI2Ou4012156; Thu, 19 Jun 2014 14:02:29 -0400
Received: from turing-police.cc.vt.edu ([IPv6:2001:468:c80:2103:75f6:ae54:501e:7a57]) (authenticated bits=0) by auth1.smtp.vt.edu (8.14.4/8.14.4) with ESMTP id s5JI2OqU025440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 19 Jun 2014 14:02:24 -0400
X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6+dev
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: RFP: IETF Website Revamp
In-Reply-To: Your message of "Wed, 18 Jun 2014 17:39:13 -0700." <CABCOCHQeP69F-3pJBhX58rDN9oQ3x40zOYQ=0uGNkvWPw7zGgQ@mail.gmail.com>
From: Valdis.Kletnieks@vt.edu
References: <5100818.1403024337262.JavaMail.root@elwamui-royal.atl.sa.earthlink.net> <CABCOCHQeP69F-3pJBhX58rDN9oQ3x40zOYQ=0uGNkvWPw7zGgQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1403200944_7016P"; micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Jun 2014 14:02:24 -0400
Message-ID: <10312.1403200944@turing-police.cc.vt.edu>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LqyMwKIMVMgCn91-b1WNH5zu-Zg
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, tmc@ietf-bids.org, IETF discussion list <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2014 18:03:04 -0000

--==_Exmh_1403200944_7016P
Content-Type: text/plain; charset=us-ascii

On Wed, 18 Jun 2014 17:39:13 -0700, Andy Bierman said:

> Sure, but if there are better auto-generated navigation links, perhaps you
> find the right content in 2 clicks instead of 3 and save a page load.
> Faster user experience is more than individual RTT.

It's not even about clicks anymore.

For grins, hit www.google.com, and use tcpdump or similar to watch how many
network interactions happen for auto-complete suggestions as you type a query.


--==_Exmh_1403200944_7016P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001

iQIVAwUBU6MlsAdmEQWDXROgAQJXUA//UNMr7BAyzbHrPos4Vzpw3jilXwmfROZQ
tVUiqITu3AE7GjLFh2vynh8JtIO6tC9wXo7S8hdGvr7InfrLJGY1Zaj0de4Y+7hf
+piErB/FhTuxpNLCeMtOH/Dmym1nBgfCcu5MkMLu3clNLJiKHdD+QX3O1jWHmBGi
pzCf5cGMBy/yIv5qcRxzGBMniEphjjtACu2fQQrauqwTr12UdqJsCIKA87ro0UdG
JUKqt/FFxqbsuj8SRpTqkB5M9Tu/FM8ZBF0rSsY+Y49SPLzuIpaUnuzPIiGIaBi8
xBKCMpfZERTc/iz1mYs/Wq+SY7BX20EqnC4AUItDgWr3gWTz/F6vyYUQsnwnLAwz
7G9N/BXE3f4mp8TdMOBOgBxa4H8KecHtcb8PFKkGD9bWgAH4YWbNfyPCzvwDcVXO
isIi1KASg5q3k8o9Y4uiZs4Il45ch9xSLHPX9K5BWhBvcTHxmUPbjszWEsRmSb6r
FpdjCvMScHbHkBxPcqSZI6EMxZI1xgUgQAt/cVEk7pUaSvsvi/2I+d89/VMpjhLg
HISA1rr/Om75PSbbCS3BJzPLAw9IpO9NuL9yB6O06UwYKw/LBEzazuEBAz03bmna
1Eyo0yEPYf8b1awiluiFTh4yZxfurvfeD0sJVp11iUsAgtGGiFVxIMUmxuNFiSnY
Xa9XkShLxT4=
=S2kt
-----END PGP SIGNATURE-----

--==_Exmh_1403200944_7016P--


From nobody Thu Jun 19 21:54:09 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06FA01A0505 for <ietf@ietfa.amsl.com>; Thu, 19 Jun 2014 21:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.653
X-Spam-Level: 
X-Spam-Status: No, score=-5.653 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 a0GMjRcqYHhm for <ietf@ietfa.amsl.com>; Thu, 19 Jun 2014 21:54:04 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00DC51A0401 for <ietf@ietf.org>; Thu, 19 Jun 2014 21:54:03 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 20 Jun 2014 00:54:02 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 20 Jun 2014 00:54:01 -0400
Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id F10E338C8027 for <ietf@ietf.org>; Fri, 20 Jun 2014 00:54:00 -0400 (EDT)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s5K4rqlF61800484 for <ietf@ietf.org>; Fri, 20 Jun 2014 04:54:00 GMT
Received: from d01av05.pok.ibm.com (localhost [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s5K4rSej014031 for <ietf@ietf.org>; Fri, 20 Jun 2014 00:53:28 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s5K4rRNu013867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 20 Jun 2014 00:53:28 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s5K4r2iu008954 for <ietf@ietf.org>; Fri, 20 Jun 2014 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s5K4r29d008910 for ietf@ietf.org; Fri, 20 Jun 2014 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201406200453.s5K4r29d008910@rotala.raleigh.ibm.com>
Date: Fri, 20 Jun 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14062004-7182-0000-0000-00000AF06432
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SNE0tUEwvc95maeeME6x9SnuV6I
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 04:54:07 -0000

Total of 57 messages in the last 7 days.
 
script run at: Fri Jun 20 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.28% |    7 | 16.43% |    81975 | phill@hallambaker.com
  8.77% |    5 |  7.26% |    36236 | john-ietf@jck.com
  7.02% |    4 |  5.99% |    29884 | mfidelman@meetinghouse.net
  5.26% |    3 |  4.92% |    24558 | hsantos@isdg.net
  5.26% |    3 |  4.65% |    23201 | ned+ietf@mauve.mrochek.com
  5.26% |    3 |  4.45% |    22220 | brian.e.carpenter@gmail.com
  5.26% |    3 |  4.08% |    20343 | dot@dotat.at
  5.26% |    3 |  3.98% |    19868 | ted.lemon@nominum.com
  3.51% |    2 |  4.69% |    23421 | mcr+ietf@sandelman.ca
  1.75% |    1 |  4.33% |    21621 | david.black@emc.com
  3.51% |    2 |  2.28% |    11393 | iad@ietf.org
  1.75% |    1 |  2.88% |    14389 | bclaise@cisco.com
  1.75% |    1 |  2.74% |    13649 | blong@google.com
  1.75% |    1 |  2.66% |    13268 | dhc@dcrocker.net
  1.75% |    1 |  2.51% |    12536 | andy@yumaworks.com
  1.75% |    1 |  2.41% |    12040 | mcr+nomcom@sandelman.ca
  1.75% |    1 |  1.95% |     9743 | vesely@tana.it
  1.75% |    1 |  1.78% |     8901 | dcrocker@bbiw.net
  1.75% |    1 |  1.78% |     8900 | eckert@cisco.com
  1.75% |    1 |  1.71% |     8536 | narten@us.ibm.com
  1.75% |    1 |  1.71% |     8522 | housley@vigilsec.com
  1.75% |    1 |  1.62% |     8087 | eburger-l@standardstrack.com
  1.75% |    1 |  1.54% |     7665 | jabley@hopcount.ca
  1.75% |    1 |  1.47% |     7338 | randy_presuhn@mindspring.com
  1.75% |    1 |  1.43% |     7134 | scott.brim@gmail.com
  1.75% |    1 |  1.39% |     6924 | valdis.kletnieks@vt.edu
  1.75% |    1 |  1.35% |     6726 | tytso@mit.edu
  1.75% |    1 |  1.31% |     6548 | markr@signal100.com
  1.75% |    1 |  1.27% |     6323 | mrex@sap.com
  1.75% |    1 |  1.17% |     5840 | casner@acm.org
  1.75% |    1 |  1.17% |     5824 | stephen@xemacs.org
  1.75% |    1 |  1.06% |     5268 | chair@ietf.org
--------+------+--------+----------+------------------------
100.00% |   57 |100.00% |   498881 | Total


From nobody Fri Jun 20 09:06:56 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A93D1B2852; Fri, 20 Jun 2014 09:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 nqwp1jRrLjGp; Fri, 20 Jun 2014 09:06:47 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC291B2843; Fri, 20 Jun 2014 09:06:47 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 62F62F9C015; Fri, 20 Jun 2014 12:06:37 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id XdK2b1PAJ4T0; Fri, 20 Jun 2014 12:06:14 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-144-77.washdc.fios.verizon.net [96.255.144.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CC04CF9C01A; Fri, 20 Jun 2014 12:06:12 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART Review of draft-ietf-ppsp-survey-08
Date: Fri, 20 Jun 2014 11:15:25 -0400
Message-Id: <58EC4CB6-6867-4110-B961-D76876503239@vigilsec.com>
To: draft-ietf-ppsp-survey.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dnUnNI6bZaZHnDFbG54-_kdgoTs
Cc: IETF Gen-ART <gen-art@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 16:06:51 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-ppsp-survey-08
Reviewer: Russ Housley
Review Date: 2014-06-20
IETF LC End Date: 2014-06-30
IESG Telechat date: unknown

Summary:  Almost Ready

Major Concerns:  None

Minor Concerns:

- Section 4.5 talks about differences between Tribler and BitTorrent;
  however, BitTorrent has not been described.  The authors need to
  describe BitTorrent before this section, or this section needs to be
  written without comparison to BitTorrent.  At a minimum, a reference
  to a description of BitTorrent is needed here.

- Section 4.6: Please include references for CDN and STUN.

- Section 7: I cannot figure out the sentence that is trying to justify
  the selection of ECC over RSA.  The sentence needs to be rewritten to
  be comprehensible.

- Section 7: Please include a reference for ISO/IEC 9798-3.

Other Comments:

- Section 1 (near bottom of page 3): This is awkward: "... which join
  dynamically the system ..."  I suggest: "... which join the system
  dynamically ..."

- Section 1 (near the top of page 4): I encourage you to avoid the use
  of "regulates".  I suggest:

  - the "tracker protocol" for interaction between trackers and peers;
  - the "peer protocol" for interaction between peers.

  The use of "regulates" appears elsewhere too, and in each case it
  caused to to ask what the authors are really trying to say.  In my
  opinion, the reader will be served by rewording in every one of these
  sentences.

- Section 4.1: s/living streaming content/live streaming content/

- Figure 2: s/Peer3/Peer 3/

- Section 4.2: This is awkward: "PPLive website reached 50 millions of
  visitors for the opening ceremony of Beijing 2008 Olympics, ..."  I
  suggest: "The PPLive website served 50 million visitors during the
  Beijing 2008 Olympics opening ceremony, ..."
  
- Section 4.2: s/PPLIVE/PPLive/

- Section 4.3: s/As it can be seen also in Figure 4, there/
                /Figure 4 also shows that there/


From nobody Fri Jun 20 14:01:54 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 993741B2915; Fri, 20 Jun 2014 14:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.151
X-Spam-Level: 
X-Spam-Status: No, score=-1.151 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 QU2jkfNIZi4w; Fri, 20 Jun 2014 14:01:52 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F51C1B2912; Fri, 20 Jun 2014 14:01:52 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1Wy5wQ-0005uj-QR; Fri, 20 Jun 2014 21:01:48 +0000
Date: Sat, 21 Jun 2014 06:01:46 +0900
Message-ID: <m2wqcbb8hx.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: NomCom Chair 2014 <nomcom-chair-2014@ietf.org>
Subject: Re: NOMCOM 2014 random seed selection
In-Reply-To: <20140620182028.14256.57198.idtracker@ietfa.amsl.com>
References: <20140620182028.14256.57198.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_2lD8tXdbnDHxTbLccOmEZcFnZQ
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 21:01:53 -0000

> Canadian Lottery Lotto 649                                                      
> US National debt ("Debt Held by the Public"), published by the                  
> US National debt ("Intragovernmental Holdings"), published by the               
> Euromillions Lottery                                                            

you gotta love the equivalence class


From nobody Sat Jun 21 11:06:41 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5ED91A03C3; Sat, 21 Jun 2014 11:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 8Oq2w-vLSNbI; Sat, 21 Jun 2014 11:06:24 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6A641A03AB; Sat, 21 Jun 2014 11:06:23 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5LI6LN5028107; Sat, 21 Jun 2014 19:06:21 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5LI6KeI028099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 21 Jun 2014 19:06:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <internetgovtech@iab.org>, <ietf@ietf.org>
Subject: Status of selection of IANA NTIA transition representatives by the IESG
Date: Sat, 21 Jun 2014 19:06:20 +0100
Message-ID: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+Ne3+nXJOcUIiRT4WbtQKz3xCqFw==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20772.001
X-TM-AS-Result: No--4.772-10.0-31-10
X-imss-scan-details: No--4.772-10.0-31-10
X-TMASE-MatchedRID: uPdbYrSxZsbAz7IGs/2dj1YIkrFDFO7mEtdrY/Wb3fM7nO9p37Uqk7Yz /RR6JZDspVdMiW33wf/NRKl8tXQsm9UX4QqLU49f04Rmz/agfdzxyOUBQvAZnlVMJlS9HCuzmvF PPubhMtlsSWbHX76Tc5C1FYwsuHudxGtpMtFxybLTzWmGCXkX+RQK/sD1nu4x63iNMMu8u6ujxY yRBa/qJX3mXSdV7KK4OubYLCVnBVFYF3qW3Je6+47xASrNIrdALsQoIsBdX/fHBvR4AHjgehRyq X5kt3ioph9VJDgt7M9vFWy0tXYd+Ea+nxL6lktN9Gy4O62y53UovwM4Byhjduh6vUQky8b7LLR5 nF3ltXgVUhluC41uNBWJz0qF3xvHjd00uZU7WfJ+3BndfXUhXQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hl9PzpBxLc3Fo4bpk2S18EB7DEU
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jun 2014 18:06:26 -0000

The IESG (minus any ADs who have put their names in as candidates) continues to
consider the appointment of two IETF representatives to the ICANN consultative
process on the transition of IANA from NTIA stewardship and thanks all of the
people who have put their names forward.

Alissa Cooper has been selected as one of the two representatives, and the IESG
is still considering all of the other candidates to select a second person. We
want to stress that our failure to select a second representative does not
reflect badly on the quality of the candidates, but rather results from the care
that the IESG is taking over the decision. 

There is an initial ICANN meeting on this topic in London next week and the IESG
will not have made its selection of the second representative in time for the
meeting. Therefore, the IESG is delegating Alissa Cooper as the representative
of the IETF's interests at that meeting. Jari Arkko will also be in attendance
in his role as the IETF Chair and can, of course, speak to IETF concerns as they
arise.

The IESG plans to resume consideration after the London meeting and make its
selection of the second IETF representative before the July 2nd deadline.

Thanks,
Adrian Farrel for the IESG


From nobody Sun Jun 22 12:17:52 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA29B1A0308; Sun, 22 Jun 2014 12:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.551
X-Spam-Level: 
X-Spam-Status: No, score=-0.551 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 UVmt-HBVU1z7; Sun, 22 Jun 2014 12:17:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1F8B1A00CD; Sun, 22 Jun 2014 12:17:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WynEI-000BXn-NE; Sun, 22 Jun 2014 15:15:06 -0400
Date: Sun, 22 Jun 2014 15:17:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jefsey <jefsey@jefsey.com>, adrian@olddog.co.uk, internetgovtech@iab.org,  ietf@ietf.org
Subject: Re: [Internetgovtech] Status of selection of IANA NTIA transition representatives by the IESG
Message-ID: <0FDAFBF46666EB91ED76F7A7@JcK-HP8200.jck.com>
In-Reply-To: <20140622182235.41BC41B27C5@ietfa.amsl.com>
References: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk> <20140622182235.41BC41B27C5@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/S0H9oSM4swzgDsNDzwDIl1CAdA0
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jun 2014 19:17:46 -0000

--On Sunday, June 22, 2014 20:22 +0200 Jefsey
<jefsey@jefsey.com> wrote:

> Dear Adrian,
> 
> this is an embarassing situation as no one knows who are the
> candidates, their positions, and the criteria of their
> selection. Nor, by the way, what the IESG agenda may be
> concerning the IETF position regarding the ICANN process. IMHO
> the most appropriate solution for a technical body should be
> to consider the best and the worst cases and make sure that
> the technology can cope with both of them, most probably with
> a delegate being specialized in each extreme case?

Jefsey,

I find many things with which I disagree and about which to be
concerned in the various pieces of this process.  But I don't
think Adrian's note identifies a situation about which the IESG
or IETF should be embarrassed in any way.  I believe that the
overall schedule would be very difficult even if ICANN had
presented a starting-point plan to the community for tuning and
ratification, but they didn't and, as far as I can tell, no one
wants that.  That leaves the community with an even more
difficult schedule and, while I can understand some impatience
with delays, I think there are ultimately only two possibilities:

(1) This whole initiative isn't going anywhere and, if there is
eventually an IANA transition away from the current NTIA
oversight model, it will not result from this process and, in
particular, from the Coordination Group's efforts.  If that is
the case, it doesn't make any difference what the IESG does and
no one should be concerned about whether or not they do it
(except, possibly, about the time they spend discussing it that
could be spent in other ways).

(2) The initiative is important.  In that case, I would much
rather have the IESG think carefully about what they want, who
they want to do it, and any details they want to work out about
relationships, discussing that with each other and, if needed,
with possible candidates, rather than do anything hasty in order
to get a second person appointed quickly ... especially since I
note that several other constituencies haven't announced
selections either.  And I think we should be pleased, and not
embarrassed at all, that they are taking that level of care.

> Otherwise, along RFC 6852, this is encouraging users and
> operators considering contingency situations where solutions
> could be asked for, proposed and implemented,  "regardless of
> their formal status". 

I don't see any way in which that would follow, even if I were
more confident I understood what you were talking about.

> This is exactly the situation where I
> put myself as a Libre non-profit ISP having to protect the
> best symetric (inbound/outbound) access to my members.

It is not clear to me why you think --as I assume from the above
that you do-- protecting "best symmetric ... access to your
members" has anything to do with IANA, how it is overseen, or
any other aspect of this process.    Even if it did, it would
not be clear to me why you should be seeking representation in
the process via the IESG or otherwise feeling that you have
standing to complain about what the IESG is or is not doing.

> I do not worry too much due to the actual flexibility of the
> technology but I am definitly sure that the solutions I will
> implement in case of difficulty will not be those advocated by
> the ICANNTIA project, as they would be the source of that
> difficulty. Since many of other operators and users will
> proceed the same in their own unknown way, some by local
> regulations or national law, without prior MSist coordination,
> the result may turn out to be technically operational but
> politically confuse, and difficult or even impossible to
> globally concert again. This would then be the end of the IETF
> as a global body or even worse if the situation degenerated.
>...

And now I'm sure I don't understand what you are talking about.
Nothing in the NTIA-ICANN-IANA relationship has ever had an
influence on IETF protocol decisions (other than as comments
from the community).  If something causes difficulties in the
design or implementation of what you decide to do, it will
either be administrative or policy decisions involving your
providers or French, EU, or possibly RIPE, but not NTIA or IANA
in any direct way.  IETF protocol decisions may make it easier
or harder to do whatever you intend to do (and, in particular,
may influence what you can easily obtain as Common,
Off-the-Shelf, hardware or software, but NTIA and IANA don't
have much influence over those decisions either... and it has
hard to blame the IETF for not facilitating whatever
non-conforming things you want to do.

And, again, I don't see how you classify or name some aspect of
what is going on changes anything.  You may have disagreements
with decisions the IETF makes and/or the patterns of IETF
protocol work.  You may want to go off in other directions and
may even consider some of those directions to be more true to
the spirit of the Internet model than what you see the IETF
doing.  Whether you would be, by some measure, right or wrong,
it still seems to me to have no interaction at all with this
NTIA-IANA transition proposal.

    john



From nobody Sun Jun 22 14:20:42 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19C311A02BA; Sun, 22 Jun 2014 14:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 J45D9liqLxes; Sun, 22 Jun 2014 14:20:31 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D30F11A0295; Sun, 22 Jun 2014 14:20:29 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5MLKRJ0000310; Sun, 22 Jun 2014 22:20:27 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5MLKQwh032760 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 22 Jun 2014 22:20:27 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Jefsey'" <jefsey@jefsey.com>, <internetgovtech@iab.org>, <ietf@ietf.org>
References: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk> <201406221822.s5MIMUW0010375@mta1.iomartmail.com>
In-Reply-To: <201406221822.s5MIMUW0010375@mta1.iomartmail.com>
Subject: RE: [Internetgovtech] Status of selection of IANA NTIA transition representatives by the IESG
Date: Sun, 22 Jun 2014 22:20:25 +0100
Message-ID: <00b401cf8e5f$c8ea7680$5abf6380$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG6iqpsDMWT8ffEtzBNvKw7amLnugJ5UM1fm5PaJOA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20774.002
X-TM-AS-Result: No--11.992-10.0-31-10
X-imss-scan-details: No--11.992-10.0-31-10
X-TMASE-MatchedRID: C/snMIRQLS192uPSQ/uy2GrRghnYv51qC3HuWcgyQCZ9Q5/gynnG1uAm ImeMynMEGuN6OYqG1L8Z5+/CBY4PWdaSgJLPelTmVZ54ioe2EwsL8TGleseLPBsizOQuDf4xr+g 7JvNQo+9ozlC4ypuEFVyQkoWMY0gvy+mf3q0dxCZHcypzEXqVgVxIyn/X4Smnq4c1/8j5pHqkwF TCCpbFRzSiGtn3dqFDg0ba6jw+n/ig0d6GNBKQUO8rvrpD1cllBhfhOps3jagtfh4sRUyg+gEGq FryhDT/1dzFSrJgGNVqT2omj58OwE1fsoLovwOe5VdEYJwEhsDSv+oK79xjnQ8x3RwK3jjFBf7f 3ILP2qoEDX0Lfnqcqo7SOhp1bxAa0RCs70uuPqHcWo5Vvs8MQpWr6iSXWtgP7ynGrUv2DpQzBHK sDHLon5kzCXQMauGmQ1KdtEmw6Jk84uNt4Z+7XZ4CIKY/Hg3AlfGwpNSPVn6+qryzYw2E8M8943 oc3p3sq7rFUcuGp/EgBwKKRHe+rzjjxtyzlw2j8emFrFRJEvJMSta06qk2FK8aAqJcMWstHlfuy zRdC+k=
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HHK4SjEPhxv_B69Cfw-f077hYk4
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jun 2014 21:20:34 -0000

Hello JFC,

I speak only for myself in my answer.

The IETF community was invited to volunteer for these positions. I view the
positions as akin to the liaison manage roles usually appointed to by the IAB,
and it does not seem to me that the IESG is doing anything unusual in the way it
is choosing these representatives.

There are email lists on which the subject matter can be discussed in order to
get a good view of the concerns and possibly of consensus within the IETF. The
representatives being appointed by the IESG are intended to represent the IETF.

Adrian


> Dear Adrian,
> 
> this is an embarassing situation as no one knows who are the
> candidates, their positions, and the criteria of their selection.
> Nor, by the way, what the IESG agenda may be concerning the IETF
> position regarding the ICANN process. IMHO the most appropriate
> solution for a technical body should be to consider the best and the
> worst cases and make sure that the technology can cope with both of
> them, most probably with a delegate being specialized in each extreme case?
> 
> Otherwise, along RFC 6852, this is encouraging users and operators
> considering contingency situations where solutions could be asked
> for, proposed and implemented,  "regardless of their formal status".
> This is exactly the situation where I put myself as a Libre
> non-profit ISP having to protect the best symetric (inbound/outbound)
> access to my members.
> 
> I do not worry too much due to the actual flexibility of the
> technology but I am definitly sure that the solutions I will
> implement in case of difficulty will not be those advocated by the
> ICANNTIA project, as they would be the source of that difficulty.
> Since many of other operators and users will proceed the same in
> their own unknown way, some by local regulations or national law,
> without prior MSist coordination, the result may turn out to be
> technically operational but politically confuse, and difficult or
> even impossible to globally concert again. This would then be the end
> of the IETF as a global body or even worse if the situation degenerated.
> 
> This kind of situation is scientifically known as "SOC",
> self-organizing criticality. This is the way nature and history
> usually work, by way of catastrophes. I think this is a point worth
> considering, more over than most of the people who will actually take
> these decisions are not (like me, but this is its own decision) on
> the IETF list.
> 
> jfc
> 
> PS. for your information most of the positions I will take in an a
> difficult situation will be documented in the French language for my
> French fellow users. I suppose that other ISPs will proceed in the
> same manner. Not to consider an ICANNTIA failure and train us in
> advance may lead to contradict RFC 3935 which states that "The IETF
> uses the English language for its work is because of its utility for
> working in a global context."



From nobody Mon Jun 23 00:56:57 2014
Return-Path: <ietf@trammell.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86221B29E7; Mon, 23 Jun 2014 00:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ccUqAhD8rv74; Mon, 23 Jun 2014 00:56:50 -0700 (PDT)
Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9141B287E; Mon, 23 Jun 2014 00:56:50 -0700 (PDT)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) by trammell.ch (Postfix) with ESMTPSA id 4ADFB1A13F1; Mon, 23 Jun 2014 09:56:48 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_72FCE113-833C-4C01-AEC7-92B2C80B1A83"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Gen-ART review of draft-ietf-ipfix-text-adt-05
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <539EBF3F.4060906@cisco.com>
Date: Mon, 23 Jun 2014 09:56:49 +0200
Message-Id: <9C4A391D-163B-48AB-9884-9FF311EDE026@trammell.ch>
References: <8D3D17ACE214DC429325B2B98F3AE712076C662F4B@MX15A.corp.emc.com> <63FBCD8F-C028-4AE6-B3CF-F8FDFB98102B@trammell.ch> <8D3D17ACE214DC429325B2B98F3AE712076C6632B4@MX15A.corp.emc.com> <539EBF3F.4060906@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/04pNZfjCw9wuuoPPdqEmP_gs8J0
Cc: "Black, David" <david.black@emc.com>, Juergen Quittek <Quittek@neclab.eu>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 07:56:54 -0000

--Apple-Mail=_72FCE113-833C-4C01-AEC7-92B2C80B1A83
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

hi Benoit,

Yep, that's my plan. Just back from vacation but should be able to =
finally get to this this week.

Cheers,

Brian

On 16 Jun 2014, at 11:56, Benoit Claise <bclaise@cisco.com> wrote:

> Hi Brian, Juergen,
>=20
> Do I understand correctly that you plan on submitting a new draft =
version to address David's feedback?
>=20
> Juergen,
> As far as I know, this is the only feedback received during IETF LC.
> If that's correct, when this feedback is addressed, I'll put this =
document on the IESG telechat.
>=20
> Regards, Benoit
>> Brian,
>>=20
>> Thanks for the response.
>>=20
>> Regarding Unicode string normalization and preparation, if those were
>> appropriate, they should have been introduced in RFC 7011, and picked
>> up here by reference.  If there's an actual problem that requires
>> those techniques (unclear), a revision to RFC 7011 would be the right
>> place to address that problem, not this draft.
>>=20
>> I would note that the sheer volume of monitoring data tends to =
require
>> automatic processing by recipients, and such tools are likely to =
compare
>> strings in monitoring data.
>>=20
>> I definitely agree that some text about Enclosing Context =
rules/requirements
>> for Unicode usage would help, e.g., along the lines of:
>>=20
>>> We largely presume these to be the responsibility of the Enclosing =
Context (in
>>> this document) and the Metering Process that created the string in =
the first
>>> place. Neither 7011 nor this representation present additional =
considerations
>>> here: we just take the Unicode string we get from whoever wants to =
send/store
>>> it and shovel it out.
>> and
>>=20
>>>> Lots of mischief is possible with non-printing and control =
characters -
>>>> I would expect that the Enclosing Context contains sufficient =
restrictions
>>>> on use of Unicode to deal with most of this concern, and would =
state that
>>>> expectation.  This comment is definitely specific to this draft.
>> So, please do add some text on this topic.
>>=20
>>>> A general warning about unreliability of Unicode string comparison
>>>> is in order.  This also applies if an identifier that is not =
limited
>>>> to ASCII characters is substituted for an integer as described in
>>>> Section 4.2.
>>> Good point; is there a good cite for this?
>> Try RFC 6885 - Stringprep Revision and Problem Statement
>> for the Preparation and Comparison of Internationalized Strings =
(PRECIS)
>>=20
>>>> Section 4.1.5 of the pr=E9cis framework draft warns against use of =
mixed-
>>>> direction Unicode strings, as "there is currently no widely =
accepted and
>>>> implemented solution for the processing and safe display of mixed-
>>>> direction strings."  That warning deserves repetition here.
>> Please repeat that warning, probably w/an informative reference to =
the
>> pr=E9cis framework draft.
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: Brian Trammell [mailto:ietf@trammell.ch]
>>> Sent: Wednesday, May 28, 2014 5:22 AM
>>> To: Black, David
>>> Cc: General Area Review Team (gen-art@ietf.org); ipfix@ietf.org; =
ietf@ietf.org
>>> Subject: Re: Gen-ART review of draft-ietf-ipfix-text-adt-05
>>>=20
>>> hi David,
>>>=20
>>> Many thanks for the review. Comments and questions inline.
>>>=20
>>> On 24 May 2014, at 04:10, Black, David <david.black@emc.com> wrote:
>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>> Gen-ART, please see the FAQ at
>>>>=20
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>=20
>>>> Please resolve these comments along with any other Last Call =
comments
>>>> you may receive.
>>>>=20
>>>> Document: draft-ietf-ipfix-text-adt-05
>>>> Reviewer: David L. Black
>>>> Review Date: May 23, 2014
>>>> IETF LC End Date: May 28, 2014
>>>>=20
>>>> Summary:  This draft is on the right track, but has open issues
>>>> 		described in the review.
>>>>=20
>>>> This is a relatively short draft defining textual representations =
of
>>>> IPFIX data elements.  It's clear and easy to read.
>>>>=20
>>>> I assume that all the ABNF has been checked.
>>> Yep.
>>>=20
>>>> The open issues involve use of Unicode.
>>> This is unsurprising. :)
>>>=20
>>>> Minor issues:
>>>>=20
>>>> Section 4.7 string
>>>>=20
>>>>   As Information Elements of the string type are simply UTF-8 =
encoded
>>>>   strings, they are represented directly, subject to the escaping =
and
>>>>   encoding rules of the Enclosing Context.
>>>>=20
>>>> There's nothing "simply" about use of UTF-8 encoded strings :-).
>>> Well, no. But most of the string normalization nightmares with UTF-8 =
are also
>>> problems in the Enclosing Contexts as well, so the assumption here =
is that if
>>> you're already representing strings in, say, UTF-8 encoded JSON, =
you're
>>> already paying the UTF-8 tax, so this document presents no =
additional
>>> considerations.
>>>=20
>>> There is an additional point here, though, that the Enclosing =
Context may
>>> prefer or require a different encoding than UTF-8, so we should =
address that:
>>>=20
>>> 	As Information Elements of the string type are simply Unicode
>>> 	strings (encoded as UTF-8 when appearing in Data Sets in IPFIX
>>> 	Messages [RFC 7011]), they are represented directly, using the
>>> 	Unicode encoding rules and quoting and escaping rules of the
>>> 	Enclosing Context.
>>>=20
>>>> There appear to be no restrictions on Unicode codepoint usage and =
no
>>>> requirements for string normalization or other preparation either =
in this
>>>> draft or RFC 7011.
>>> We largely presume these to be the responsibility of the Enclosing =
Context (in
>>> this document) and the Metering Process that created the string in =
the first
>>> place. Neither 7011 nor this representation present additional =
considerations
>>> here: we just take the Unicode string we get from whoever wants to =
send/store
>>> it and shovel it out.
>>>=20
>>> I'm not sure it makes sense to enforce normalization in this =
context.
>>>=20
>>>>  This can be a formula for all sorts of mischief, so
>>>> some warnings about what's possible should be added somewhere - =
some of
>>>> these comments may be raising Unicode concerns in RFC 7011 that =
would
>>>> be better addressed there.
>>> Generally, text-adt is intended to allow the use of the IPFIX =
Information
>>> Model separately from the protocol described in RFC 7011, so any =
concern there
>>> should also be raised here.
>>>=20
>>>> A general warning about unreliability of Unicode string comparison
>>>> is in order.  This also applies if an identifier that is not =
limited
>>>> to ASCII characters is substituted for an integer as described in
>>>> Section 4.2.
>>> Good point; is there a good cite for this?
>>>=20
>>>>  In addition, the concerns around visually similar
>>>> characters discussed in section 10.5 of the pr=E9cis framework =
draft
>>>> (draft-ietf-pr=E9cis-framework) apply; a short summary and pointer
>>>> to that section of that draft should suffice.
>>>>=20
>>>> Section 4.1.5 of the pr=E9cis framework draft warns against use of =
mixed-
>>>> direction Unicode strings, as "there is currently no widely =
accepted and
>>>> implemented solution for the processing and safe display of mixed-
>>>> direction strings."  That warning deserves repetition here.
>>>>=20
>>>> Lots of mischief is possible with non-printing and control =
characters -
>>>> I would expect that the Enclosing Context contains sufficient =
restrictions
>>>> on use of Unicode to deal with most of this concern, and would =
state that
>>>> expectation.  This comment is definitely specific to this draft.
>>>>=20
>>>> Nits/editorial comments:
>>>>=20
>>>> Section 4.4 float32 and float64
>>>>=20
>>>>   exponent =3D ( "e" / "E" ) [sign] 1*3DIGIT
>>>>=20
>>>> Please explain why no more than 3 digits are ever required.
>>> Will do (i.e., because the maximum ranges on the type range from =
O(1e-3xx) -
>>> O(1e3xx)).
>>>=20
>>>> Section 4.8 dateTime*
>>>>=20
>>>> The '*' in the section title, dateTime* is clever, but it's meaning =
is not
>>>> obvious.  I suggest "The dateTime Data Types" as a better section =
title.
>>> Yep, thanks.
>>>=20
>>>> Section 5 Security Considerations
>>>>=20
>>>>   The security considerations for the IPFIX Protocol [RFC7011] =
apply;
>>>>   this document presents no additional security considerations.
>>>>=20
>>>> That's ok, although adding a direct mention of the [UTF8-EXPLOIT] =
TR
>>>> cited in RFC 7011 would be helpful.
>>> Will do.
>>>=20
>>>> idnits 2.13.01 warns that the JSON reference (RFC 4627) is =
obsolete, and
>>>> needs to be replaced with one or two current RFC references.
>>> Oops; will replace.
>>>=20
>>> Thanks again, cheers,
>>>=20
>>> Brian
>> .
>>=20
>=20


--Apple-Mail=_72FCE113-833C-4C01-AEC7-92B2C80B1A83
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJTp93BAAoJENt3nsOmbNJcgjgH/2nv6gf4stg3bCaJCaSmhbyS
b4iSpDmIlig0gnSKuGmh4H0JbWzkulpKvki9U8wViUojWdRG6y/3/5+c+0b3ss/m
G5HW5n8Lh1aFkjXeOGpLpE/cDsXvp85PcOu+tGxtRlrnvn5gShwhnNtOwGrfxDcw
c/IAgYhRRW/TqEZbwR0cuarVbzJ63cxrihdYRFbrkKJnCVOuGNSu5rlhaB+z6Sqd
WCTjG1aLSph9w2q1a9hRl7fZYlF5N7w07eV2eBMsMSI50WLobmfuZeaMJXPLvx2g
uO3kbVb1xfjlhKxRlq69ygxk3xQcrzlV2Omz8ERDOnXuSDDdGNcCHlhkwijxZdA=
=UmcN
-----END PGP SIGNATURE-----

--Apple-Mail=_72FCE113-833C-4C01-AEC7-92B2C80B1A83--


From nobody Mon Jun 23 06:29:09 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1C91B2956; Mon, 23 Jun 2014 06:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.171
X-Spam-Level: 
X-Spam-Status: No, score=0.171 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=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 bc7192bTP3RN; Mon, 23 Jun 2014 06:29:03 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6638A1B2955; Mon, 23 Jun 2014 06:29:02 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so6364857wgh.35 for <multiple recipients>; Mon, 23 Jun 2014 06:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=nNZrrFTEoAgHNOOdnnwg527v2kbN8fmq8kHsvvrWzNI=; b=pEqdhNoSOfhDTJ2hTYyPUaHKl9daCeewZ9xHmvuPvdIfoY/e+cfo7VMvxyhKNRDyxr i70DM4NsDYTBWRlsEXcIOUZR8U2nh59V4oveHCAfHvxA0ktOKDNFoFE4raG/1NaDKBXb mNaFnsCVXkozfiaqIg2+a9XZES0+Iwc0TKpJe3Moivbdfs9vNZ1K8T5rOn/tv0P2xNYx 1QVfehEuFFP+aJtTqpyAfN4lvHWzCUGk2XuIvORt2zO/3ltiuyfuPZLTANLTC6cP5I7e ApG94eDvpmIuToGQASOZXHNKo02+2nGDB9QXCRwH9zaQvL7EYIhnyaWXBS7KQL69C3Rq P5jA==
X-Received: by 10.194.120.72 with SMTP id la8mr19183581wjb.24.1403530137946; Mon, 23 Jun 2014 06:28:57 -0700 (PDT)
Received: from RoniE (bzq-79-179-98-253.red.bezeqint.net. [79.179.98.253]) by mx.google.com with ESMTPSA id i3sm33440940wiz.13.2014.06.23.06.28.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 23 Jun 2014 06:28:57 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-tram-stun-dtls.all@tools.ietf.org>, <gen-art@ietf.org>, <ietf@ietf.org>
Subject: Gen-ART LC review of draft-ietf-tram-stun-dtls-03
Date: Mon, 23 Jun 2014 16:28:51 +0300
Message-ID: <03df01cf8ee7$15b3fae0$411bf0a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03E0_01CF8F00.3B021D40"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac+O5v0nAdpox5xnTVGptA1vivCFMA==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zPpR5FSqjfSGrP6szj_6SgIRGOU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 13:29:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03E0_01CF8F00.3B021D40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-tram-stun-dtls-03

Reviewer: Roni Even

Review Date:2014-6-23

IETF LC End Date: 2014-6-25

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as an Standard track
RFC.

 

 

Major issues:

 

Minor issues:

 

I am not sure I understand section 4.3. When talking about "media keep-alive
packets" is it for the STUN Binding Indication usage or for all the options
in section 10 of RFC 5245.  Maybe you meant that you should prefer DTLS/SRTP
keep-alive like RTP no-op in this case. I had problem understanding this
section. Please clarify.

 

 

 

Nits/editorial comments:

 

 

 


------=_NextPart_000_03E0_01CF8F00.3B021D40
Content-Type: text/html;
	charset="us-ascii"
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document:&n=
bsp; </span>draft-ietf-tram-stun-dtls-03<span =
style=3D'color:black'><o:p></o:p></span></pre><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;6-23<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2014&#8211;6-25<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as an Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am not =
sure I understand section 4.3. When talking about &#8220;media =
keep-alive packets&#8221; is it for the STUN Binding Indication usage or =
for all the options in section 10 of RFC 5245.&nbsp; Maybe you meant =
that you should prefer DTLS/SRTP keep-alive like RTP no-op in this case. =
I had problem understanding this section. Please =
clarify.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_03E0_01CF8F00.3B021D40--


From nobody Mon Jun 23 10:04:43 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B32FC1A03A9; Mon, 23 Jun 2014 10:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level: 
X-Spam-Status: No, score=-1.23 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_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=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 GRF4Fbo5Grde; Mon, 23 Jun 2014 10:04:38 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A253A1B2B66; Mon, 23 Jun 2014 09:56:19 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id bs8so4752361wib.15 for <multiple recipients>; Mon, 23 Jun 2014 09:56:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=HGH7ogygezeArtUNOKpP2CzSjuPKJCihv2/PlXPOTZk=; b=g/GW+ONQa4TO29xfSkrDIRZ5X5gXsNdOG/wPOkha2Ad+HuHHB0d8av+oapzVSC28Rf vI3WOIRJ8rJLMZcy/Yh6r6myNCRHnhMpD442nMexzMTyAxbDCfxc3eCKLZKGLAvoJhcn 5Zfzsg/O2LkBVXiWPE0eSuc9y30eKfA+5dr1sp6gj3o4ErTl3dORZIlP7+4O8/rHIfWP qxMlgF2Eo1xpt9aNaM8A0kvXvV7JNtkPqBw82c+qo46Lpe42tbK+OjhfXr+lpfiDqaa5 eBaKL3qLUZUgMyc5KlWlLSU1ldHGnkEsZFHMQQIFVsMdVDqxYlciMoIMVufvATVXVVGV VTcA==
X-Received: by 10.194.157.68 with SMTP id wk4mr29387902wjb.42.1403542577994; Mon, 23 Jun 2014 09:56:17 -0700 (PDT)
Received: from RoniE (bzq-79-179-98-253.red.bezeqint.net. [79.179.98.253]) by mx.google.com with ESMTPSA id f6sm34966243wiy.19.2014.06.23.09.56.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 23 Jun 2014 09:56:16 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Marc Petit-Huguenin'" <marcph@getjive.com>, <draft-ietf-tram-stun-dtls.all@tools.ietf.org>, <gen-art@ietf.org>, <ietf@ietf.org>
References: <03df01cf8ee7$15b3fae0$411bf0a0$@gmail.com> <53A83B03.4050101@getjive.com>
In-Reply-To: <53A83B03.4050101@getjive.com>
Subject: RE: Gen-ART LC review of draft-ietf-tram-stun-dtls-03
Date: Mon, 23 Jun 2014 19:56:13 +0300
Message-ID: <040901cf8f04$0c54f810$24fee830$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQItEtHPoFRvTbSnGpwRAJN1yq2O/AD2Dw0Cmrww9CA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XOjsLKhfbsyULE0tih0H44FchR4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 17:04:39 -0000

Hi Marc,
So maybe emphasis that it is about STUN Binding Indications suggest

" When STUN Binding Indications are being used for media keep-alive
(described in Section
   10 of [RFC5245]), it runs alongside an RTP or RTCP session.  It is
   possible to send these media keep-alive packets inside a separately
   negotiated non-SRTP DTLS session if DTLS-SRTP [RFC5764] is used, but
   that would add overhead, with minimal security benefit."
Roni

> -----Original Message-----
> From: Marc Petit-Huguenin [mailto:marcph@getjive.com]
> Sent: 23 June, 2014 5:35 PM
> To: Roni Even; draft-ietf-tram-stun-dtls.all@tools.ietf.org;
gen-art@ietf.org;
> ietf@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-tram-stun-dtls-03
> 
> Hi Roni,
> 
> See my answers below.
> 
> On 6/23/14, 7:28 AM, Roni Even wrote:
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document:  draft-ietf-tram-stun-dtls-03
> >
> > Reviewer: Roni Even
> >
> > Review Date:2014-6-23
> >
> > IETF LC End Date: 2014-6-25
> >
> > IESG Telechat date:
> >
> >
> >
> > Summary: This draft is almost ready for publication as an Standard
> > track RFC.
> >
> >
> >
> >
> >
> > Major issues:
> >
> >
> >
> > Minor issues:
> >
> >
> >
> > I am not sure I understand section 4.3. When talking about "media
> > keep-alive packets" is it for the STUN Binding Indication usage or for
> > all the options in section 10 of RFC 5245.
> 
> Yes, only the STUN Binding Indication usage.  You are right this is not
clear.
> 
> > Maybe you meant that you should prefer DTLS/SRTP keep-alive like RTP
> > no-op in this case. I had problem understanding this section. Please
> > clarify.
> >
> 
> No the text did not meant to choose one over the other, just to explain
the pros
> and cons of running the STUN Binding Indication usage over DTLS.
> 
> I propose this new text:
> 
> "  When STUN is being used for media keep-alive (described in Section
>    10 of [RFC5245]), it runs alongside an RTP or RTCP session.  It is
>    possible to send the media keep-alive packets inside a separately
>    negotiated non-SRTP DTLS session if DTLS-SRTP [RFC5764] is used, but
>    that would add overhead, with minimal security benefit."
> 
> Thanks.
> 
> --
> Marc Petit-Huguenin
> Developer  |  Jive Communications, Inc.
> Jive.com  |  marcph@getjive.com



From nobody Mon Jun 23 10:38:04 2014
Return-Path: <jefsey@jefsey.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 820791B27C7; Sun, 22 Jun 2014 11:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.631
X-Spam-Level: *
X-Spam-Status: No, score=1.631 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] autolearn=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 zaj7hXqla6QI; Sun, 22 Jun 2014 11:22:30 -0700 (PDT)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (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 45A411B27C4; Sun, 22 Jun 2014 11:22:30 -0700 (PDT)
Received: from 231.74.14.81.rev.sfr.net ([81.14.74.231]:7405 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1WymPL-0007s6-Ti; Sun, 22 Jun 2014 11:22:28 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 22 Jun 2014 20:22:00 +0200
To: adrian@olddog.co.uk,<internetgovtech@iab.org>,<ietf@ietf.org>
From: Jefsey <jefsey@jefsey.com>
Subject: Re: [Internetgovtech] Status of selection of IANA NTIA transition representatives by the IESG
In-Reply-To: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk>
References: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: jefsey+jefsey.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Lc53KiGFqt02RCWPGc4QqSbK0ns
X-Mailman-Approved-At: Mon, 23 Jun 2014 10:38:02 -0700
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jun 2014 18:22:31 -0000

Dear Adrian,

this is an embarassing situation as no one knows who are the 
candidates, their positions, and the criteria of their selection. 
Nor, by the way, what the IESG agenda may be concerning the IETF 
position regarding the ICANN process. IMHO the most appropriate 
solution for a technical body should be to consider the best and the 
worst cases and make sure that the technology can cope with both of 
them, most probably with a delegate being specialized in each extreme case?

Otherwise, along RFC 6852, this is encouraging users and operators 
considering contingency situations where solutions could be asked 
for, proposed and implemented,  "regardless of their formal status". 
This is exactly the situation where I put myself as a Libre 
non-profit ISP having to protect the best symetric (inbound/outbound) 
access to my members.

I do not worry too much due to the actual flexibility of the 
technology but I am definitly sure that the solutions I will 
implement in case of difficulty will not be those advocated by the 
ICANNTIA project, as they would be the source of that difficulty. 
Since many of other operators and users will proceed the same in 
their own unknown way, some by local regulations or national law, 
without prior MSist coordination, the result may turn out to be 
technically operational but politically confuse, and difficult or 
even impossible to globally concert again. This would then be the end 
of the IETF as a global body or even worse if the situation degenerated.

This kind of situation is scientifically known as "SOC", 
self-organizing criticality. This is the way nature and history 
usually work, by way of catastrophes. I think this is a point worth 
considering, more over than most of the people who will actually take 
these decisions are not (like me, but this is its own decision) on 
the IETF list.

jfc

PS. for your information most of the positions I will take in an a 
difficult situation will be documented in the French language for my 
French fellow users. I suppose that other ISPs will proceed in the 
same manner. Not to consider an ICANNTIA failure and train us in 
advance may lead to contradict RFC 3935 which states that "The IETF 
uses the English language for its work is because of its utility for 
working in a global context."





At 20:06 21/06/2014, Adrian Farrel wrote:
>The IESG (minus any ADs who have put their names in as candidates) 
>continues to
>consider the appointment of two IETF representatives to the ICANN consultative
>process on the transition of IANA from NTIA stewardship and thanks all of the
>people who have put their names forward.
>
>Alissa Cooper has been selected as one of the two representatives, 
>and the IESG
>is still considering all of the other candidates to select a second person. We
>want to stress that our failure to select a second representative does not
>reflect badly on the quality of the candidates, but rather results 
>from the care
>that the IESG is taking over the decision.
>
>There is an initial ICANN meeting on this topic in London next week 
>and the IESG
>will not have made its selection of the second representative in time for the
>meeting. Therefore, the IESG is delegating Alissa Cooper as the representative
>of the IETF's interests at that meeting. Jari Arkko will also be in attendance
>in his role as the IETF Chair and can, of course, speak to IETF 
>concerns as they
>arise.
>
>The IESG plans to resume consideration after the London meeting and make its
>selection of the second IETF representative before the July 2nd deadline.
>
>Thanks,
>Adrian Farrel for the IESG
>
>_______________________________________________
>Internetgovtech mailing list
>Internetgovtech@iab.org
>https://www.iab.org/mailman/listinfo/internetgovtech


From nobody Mon Jun 23 10:38:07 2014
Return-Path: <jefsey@jefsey.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7661B2B46; Mon, 23 Jun 2014 08:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.632
X-Spam-Level: *
X-Spam-Status: No, score=1.632 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] autolearn=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 0mUAGB4tiayi; Mon, 23 Jun 2014 08:45:28 -0700 (PDT)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (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 CC91F1B2B4A; Mon, 23 Jun 2014 08:45:28 -0700 (PDT)
Received: from 231.74.14.81.rev.sfr.net ([81.14.74.231]:21523 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1Wz6Qv-0006PQ-8l; Mon, 23 Jun 2014 08:45:27 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Jun 2014 17:44:54 +0200
To: <adrian@olddog.co.uk>,<internetgovtech@iab.org>,<ietf@ietf.org>
From: Jefsey <jefsey@jefsey.com>
Subject: RE: [Internetgovtech] Status of selection of IANA NTIA  transition representatives by the IESG
In-Reply-To: <00b401cf8e5f$c8ea7680$5abf6380$@olddog.co.uk>
References: <0ba001cf8d7b$81c1f6a0$8545e3e0$@olddog.co.uk> <201406221822.s5MIMUW0010375@mta1.iomartmail.com> <00b401cf8e5f$c8ea7680$5abf6380$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_1001550536==.ALT"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: jefsey+jefsey.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PAFOOVVQPKU6DpU5fOKdF4srlRE
X-Mailman-Approved-At: Mon, 23 Jun 2014 10:38:03 -0700
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 15:45:31 -0000

--=====================_1001550536==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

John, Adrian,

I am afraid we misunderstand. In a nutshell, I consider that the July 
1978 IEN 48 internetting project:

- first motivation phase is ending. The proof of the catenet concept 
under TCP/IP is completed. President Giscard d'Estain has closed the 
Cyclades project that ARPA has paid for and completed, and the 
alternative RCP project has led to Transpac and X.25 and has also 
closed. The French and US government executive direct/indirect 
influences on hardware and software, bandwidth and code are over. 
NTIA ends it.
- second motivation phase is eventually engaged. It is to provide 
what Tymnet had engaged in June 1978 while new govermental influences 
(Europe, Russia, China) are emerging in a different form (no more 
budgets to pay for the code but laws to influence the code). 
Brainware/collective use is taking preeminance while economy and 
strategies are shifting from information and communications focus to 
intellition, i.e. what makes sense out of received/collected 
communicated information (publicity, press, PRISM, big data, content).

In this process fair competition replacing regulation not possible 
due to cross-subsidization from brainware (edge providers) and 
inbound/outbound dissymetry, laws and public investement must restore 
a fair situation. This will have most probably an important impact on 
the fringe to fringe and edge systems architecture.

The question I raise is who is going to make sure that the kind of 
ubiquity that intellition systems brainware calls for is going to be 
technically documented?
- either in recalling the current technologies limits, possibilities, 
costs, options to other and new stakeholders who will sponsor a new 
tech community?
- or in coordinating a collective documentation, experimentation, 
validation and deployment in the multi-global-community context 
acknowledged but not organized by RFC 6852?

As a result there are two possibilities for the IETF:
- either to help documenting what is existing and what it can do but 
never did yet (transition).
- or to work on the architectural extensions the new 
geo-political-use will call for (evolution).

In front of this there are two possibilities for the NTIA/ICANN process:
- either they listen to the IETF and OpenStand allies and cooperate.
- or they do not.

This will impact the position of Governments, as I see in the current 
".wine", ".vin" issue, and in turn my capacity of access to the 
hardware, software and brainware current reality (i.e; what I cannot 
change by mu own).


1. I need to know my options and decide my road-map. This is why I 
wish to know (I am not interested  in discussing it: I am banned) the 
IETF project, and it to be efficiently  defended (for stability 
reasons). This is why I need the IETF to delegate two people 
specialized, one for the political cooperation scenario and the other 
for the political change scenaroi.

Question 1. What is the architectonical project of the IETF? To 
remain at the software protocol strtatum, or to extend in the virtual 
hardware, layer six and the low brainware layers?
Question 2. How is this coordinated within the OpenStand partners?
Question 3. The NTIA transfers authority. The liaisons are not to be 
experts but leaders with a target and powers. What is the target, 
what are the powers?


2. I need to survive and develop with what is available to me now. I 
am in the same situation as many others, with the difference that (1) 
I have been in charge of the early years of what is to be deployed, 
this was before the industry's status-quo strategy took over (2) I 
planned and tested ahead how the internet technology could support it.

I have two options:

- either I use the solutions that the IETF will quickly and credibly 
document for my type of use and accomodate the positive or negative 
outcome of the NTIA/ICANN transition.
- or I adapt the existing solutions by myself, alone or in 
coordinating with allies, something everyone may have to do in hurry, 
to best accomodate the positive or negative aspects of the NTIA/ICANN 
transition. My feeling is that the best interest of Virtual Glocal 
Networks is that solution proposers coordinate.

I have nothing more to say. I will attentively listen to you. And we 
will proceed by our own for the best of our members.

jfc


At 23:20 22/06/2014, Adrian Farrel wrote:
>Hello JFC,
>
>I speak only for myself in my answer.
>
>The IETF community was invited to volunteer for these positions. I view the
>positions as akin to the liaison manage roles usually appointed to by the IAB,
>and it does not seem to me that the IESG is doing anything unusual 
>in the way it
>is choosing these representatives.
>
>There are email lists on which the subject matter can be discussed in order to
>get a good view of the concerns and possibly of consensus within the IETF. The
>representatives being appointed by the IESG are intended to 
>represent the IETF.
>
>Adrian
>
>
> > Dear Adrian,
> >
> > this is an embarassing situation as no one knows who are the
> > candidates, their positions, and the criteria of their selection.
> > Nor, by the way, what the IESG agenda may be concerning the IETF
> > position regarding the ICANN process. IMHO the most appropriate
> > solution for a technical body should be to consider the best and the
> > worst cases and make sure that the technology can cope with both of
> > them, most probably with a delegate being specialized in each extreme case?
> >
> > Otherwise, along RFC 6852, this is encouraging users and operators
> > considering contingency situations where solutions could be asked
> > for, proposed and implemented,  "regardless of their formal status".
> > This is exactly the situation where I put myself as a Libre
> > non-profit ISP having to protect the best symetric (inbound/outbound)
> > access to my members.
> >
> > I do not worry too much due to the actual flexibility of the
> > technology but I am definitly sure that the solutions I will
> > implement in case of difficulty will not be those advocated by the
> > ICANNTIA project, as they would be the source of that difficulty.
> > Since many of other operators and users will proceed the same in
> > their own unknown way, some by local regulations or national law,
> > without prior MSist coordination, the result may turn out to be
> > technically operational but politically confuse, and difficult or
> > even impossible to globally concert again. This would then be the end
> > of the IETF as a global body or even worse if the situation degenerated.
> >
> > This kind of situation is scientifically known as "SOC",
> > self-organizing criticality. This is the way nature and history
> > usually work, by way of catastrophes. I think this is a point worth
> > considering, more over than most of the people who will actually take
> > these decisions are not (like me, but this is its own decision) on
> > the IETF list.
> >
> > jfc
> >
> > PS. for your information most of the positions I will take in an a
> > difficult situation will be documented in the French language for my
> > French fellow users. I suppose that other ISPs will proceed in the
> > same manner. Not to consider an ICANNTIA failure and train us in
> > advance may lead to contradict RFC 3935 which states that "The IETF
> > uses the English language for its work is because of its utility for
> > working in a global context."

--=====================_1001550536==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
John, Adrian,<br><br>
I am afraid we misunderstand. In a nutshell, I consider that the July
1978 IEN 48 internetting project: <br><br>
- first motivation phase is ending. The proof of the catenet concept
under TCP/IP is completed. President Giscard d'Estain has closed the
Cyclades project that ARPA has paid for and completed, and the
alternative RCP project has led to Transpac and X.25 and has also closed.
The French and US government executive direct/indirect influences on
hardware and software, bandwidth and code are over. NTIA ends it. <br>
- second motivation phase is eventually engaged. It is to provide what
Tymnet had engaged in June 1978 while new govermental influences (Europe,
Russia, China) are emerging in a different form (no more budgets to pay
for the code but laws to influence the code). Brainware/collective use is
taking preeminance while economy and strategies are shifting from
information and communications focus to intellition, i.e. what makes
sense out of received/collected communicated information (publicity,
press, PRISM, big data, content). <br><br>
In this process fair competition replacing regulation not possible due to
cross-subsidization from brainware (edge providers) and inbound/outbound
dissymetry, laws and public investement must restore a fair situation.
This will have most probably an important impact on the fringe to fringe
and edge systems architecture.<br><br>
The question I raise is who is going to make sure that the kind of
ubiquity that intellition systems brainware calls for is going to be
technically documented?<br>
- either in recalling the current technologies limits, possibilities,
costs, options to other and new stakeholders who will sponsor a new tech
community?<br>
- or in coordinating a collective documentation, experimentation,
validation and deployment in the multi-global-community context
acknowledged <u>but not organized </u>by RFC 6852?<br><br>
As a result there are two possibilities for the IETF: <br>
- either to help documenting what is existing and what it can do but
never did yet (transition).<br>
- or to work on the architectural extensions the new geo-political-use
will call for (evolution).<br><br>
In front of this there are two possibilities for the NTIA/ICANN
process:<br>
- either they listen to the IETF and OpenStand allies and cooperate.
<br>
- or they do not. <br><br>
This will impact the position of Governments, as I see in the current
&quot;.wine&quot;, &quot;.vin&quot; issue, and in turn my capacity of
access to the hardware, software and brainware current reality (i.e; what
I cannot change by mu own).<br><br>
<br>
1. I need to know my options and decide my road-map. This is why I wish
to know (I am not interested&nbsp; in discussing it: I am banned) the
IETF project, and it to be efficiently&nbsp; defended (for stability
reasons). This is why I need the IETF to delegate two people specialized,
one for the political cooperation scenario and the other for the
political change scenaroi.<br><br>
Question 1. What is the architectonical project of the IETF? To remain at
the software protocol strtatum, or to extend in the virtual hardware,
layer six and the low brainware layers?<br>
Question 2. How is this coordinated within the OpenStand partners? <br>
Question 3. The NTIA transfers authority. The liaisons are not to be
experts but leaders with a target and powers. What is the target, what
are the powers?<br><br>
<br>
2. I need to survive and develop with what is available to me now. I am
in the same situation as many others, with the difference that (1) I have
been in charge of the early years of what is to be deployed, this was
before the industry's status-quo strategy took over (2) I planned and
tested ahead how the internet technology could support it.<br><br>
I have two options:<br><br>
- either I use the solutions that the IETF will quickly and credibly
document for my type of use and accomodate the positive or negative
outcome of the NTIA/ICANN transition.<br>
- or I adapt the existing solutions by myself, alone or in coordinating
with allies, something everyone may have to do in hurry, to best
accomodate the positive or negative aspects of the NTIA/ICANN transition.
My feeling is that the best interest of Virtual Glocal Networks is that
solution proposers coordinate.<br><br>
I have nothing more to say. I will attentively listen to you. And we will
proceed by our own for the best of our members.<br><br>
jfc<br><br>
<br>
At 23:20 22/06/2014, Adrian Farrel wrote:<br>
<blockquote type=cite class=cite cite="">Hello JFC,<br><br>
I speak only for myself in my answer.<br><br>
The IETF community was invited to volunteer for these positions. I view
the<br>
positions as akin to the liaison manage roles usually appointed to by the
IAB,<br>
and it does not seem to me that the IESG is doing anything unusual in the
way it<br>
is choosing these representatives.<br><br>
There are email lists on which the subject matter can be discussed in
order to<br>
get a good view of the concerns and possibly of consensus within the
IETF. The<br>
representatives being appointed by the IESG are intended to represent the
IETF.<br><br>
Adrian<br><br>
<br>
&gt; Dear Adrian,<br>
&gt; <br>
&gt; this is an embarassing situation as no one knows who are the<br>
&gt; candidates, their positions, and the criteria of their
selection.<br>
&gt; Nor, by the way, what the IESG agenda may be concerning the
IETF<br>
&gt; position regarding the ICANN process. IMHO the most appropriate<br>
&gt; solution for a technical body should be to consider the best and
the<br>
&gt; worst cases and make sure that the technology can cope with both
of<br>
&gt; them, most probably with a delegate being specialized in each
extreme case?<br>
&gt; <br>
&gt; Otherwise, along RFC 6852, this is encouraging users and
operators<br>
&gt; considering contingency situations where solutions could be
asked<br>
&gt; for, proposed and implemented,&nbsp; &quot;regardless of their
formal status&quot;.<br>
&gt; This is exactly the situation where I put myself as a Libre<br>
&gt; non-profit ISP having to protect the best symetric
(inbound/outbound)<br>
&gt; access to my members.<br>
&gt; <br>
&gt; I do not worry too much due to the actual flexibility of the<br>
&gt; technology but I am definitly sure that the solutions I will<br>
&gt; implement in case of difficulty will not be those advocated by
the<br>
&gt; ICANNTIA project, as they would be the source of that
difficulty.<br>
&gt; Since many of other operators and users will proceed the same
in<br>
&gt; their own unknown way, some by local regulations or national
law,<br>
&gt; without prior MSist coordination, the result may turn out to be<br>
&gt; technically operational but politically confuse, and difficult
or<br>
&gt; even impossible to globally concert again. This would then be the
end<br>
&gt; of the IETF as a global body or even worse if the situation
degenerated.<br>
&gt; <br>
&gt; This kind of situation is scientifically known as
&quot;SOC&quot;,<br>
&gt; self-organizing criticality. This is the way nature and history<br>
&gt; usually work, by way of catastrophes. I think this is a point
worth<br>
&gt; considering, more over than most of the people who will actually
take<br>
&gt; these decisions are not (like me, but this is its own decision)
on<br>
&gt; the IETF list.<br>
&gt; <br>
&gt; jfc<br>
&gt; <br>
&gt; PS. for your information most of the positions I will take in an
a<br>
&gt; difficult situation will be documented in the French language for
my<br>
&gt; French fellow users. I suppose that other ISPs will proceed in
the<br>
&gt; same manner. Not to consider an ICANNTIA failure and train us
in<br>
&gt; advance may lead to contradict RFC 3935 which states that &quot;The
IETF<br>
&gt; uses the English language for its work is because of its utility
for<br>
&gt; working in a global context.&quot;</blockquote></body>
</html>

--=====================_1001550536==.ALT--


From nobody Mon Jun 23 10:39:08 2014
Return-Path: <marcph@getjive.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7101B2AB9 for <ietf@ietfa.amsl.com>; Mon, 23 Jun 2014 07:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=unavailable
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 f2nnCBZcu0WA for <ietf@ietfa.amsl.com>; Mon, 23 Jun 2014 07:34:52 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F8D1B2965 for <ietf@ietf.org>; Mon, 23 Jun 2014 07:34:51 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id rd18so5845775iec.35 for <ietf@ietf.org>; Mon, 23 Jun 2014 07:34:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getjive.com; s=mail; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=2ns69stHSALUnxQG90M84g/Ph0xz72q7G/VQBEMh/dA=; b=itvJPS1xTIqcKUsMUm9kOUj6f4V3YurCny3vU4veJconevsXP+I3HmzcJVmYh/O+py 6GtC7ZHN05geZ/UF6jqjE3eZ1Fn7yhvXZd24hZAWg6bxf4d2CoowZMhW/mQnT/3GFtnm 0KHtp3DGPxtaNMI2ZNryc4tjc2EXpVch8qjLA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=2ns69stHSALUnxQG90M84g/Ph0xz72q7G/VQBEMh/dA=; b=kZ57Ig/YP+I+uIue6w3Xt8KTFdox89K6JFGZPOMhoG6h4tEAdLUdWxnFPnhZiR+dGZ Qf4FpPHiLdoGkBuYJg/Uyi3PO3t56XoDDd3OjLCQ1WjCx8E2T8mtNN6X0U/V32JKkajG D+WgJNvOlX+JnJCIqH9qVlfYhIBznWpophoTJzEfvNNIkvd2ebyvW4UWEV8PQ3CQXs2K HoH7xKelYHd7Ac2m7JPrdORobD5JSfwASSIBmZIdm0v71lfhb3FK5/11tEPUdW9oqKLr aSgBLmik7AqZX5laLKYTJU36mWkPypXC1l53n5nhTpVNPguZfE8LcF6vyles1Q6IhWiD U5DQ==
X-Gm-Message-State: ALoCoQm4DGm6eIVUir5FRlL6ndUr8cGd2XQmQ4MOOIabYK1mtpNbs5Ixjm/AXJItefa4HHCUMmM/
X-Received: by 10.43.39.137 with SMTP id tm9mr887253icb.41.1403534090369; Mon, 23 Jun 2014 07:34:50 -0700 (PDT)
Received: from jivecommunications.com ([199.87.120.126]) by mx.google.com with ESMTPSA id h13sm33070596igq.6.2014.06.23.07.34.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Jun 2014 07:34:49 -0700 (PDT)
Message-ID: <53A83B03.4050101@getjive.com>
Date: Mon, 23 Jun 2014 08:34:43 -0600
From: Marc Petit-Huguenin <marcph@getjive.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>,  draft-ietf-tram-stun-dtls.all@tools.ietf.org, gen-art@ietf.org,  ietf@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-tram-stun-dtls-03
References: <03df01cf8ee7$15b3fae0$411bf0a0$@gmail.com>
In-Reply-To: <03df01cf8ee7$15b3fae0$411bf0a0$@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="msiLotwfcNFUm5B0EPXeq3dj88FxfULaH"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eKYVHQ-mSv6MuVpiharjI9lewKg
X-Mailman-Approved-At: Mon, 23 Jun 2014 10:38:56 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 14:34:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--msiLotwfcNFUm5B0EPXeq3dj88FxfULaH
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Roni,

See my answers below.

On 6/23/14, 7:28 AM, Roni Even wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments y=
ou
> may receive.
>=20
> Document:  draft-ietf-tram-stun-dtls-03
>=20
> Reviewer: Roni Even
>=20
> Review Date:2014-6-23
>=20
> IETF LC End Date: 2014-6-25
>=20
> IESG Telechat date:=20
>=20
> =20
>=20
> Summary: This draft is almost ready for publication as an Standard trac=
k
> RFC.
>=20
> =20
>=20
> =20
>=20
> Major issues:
>=20
> =20
>=20
> Minor issues:
>=20
> =20
>=20
> I am not sure I understand section 4.3. When talking about "media keep-=
alive
> packets" is it for the STUN Binding Indication usage or for all the opt=
ions
> in section 10 of RFC 5245. =20

Yes, only the STUN Binding Indication usage.  You are right this is not
clear.

> Maybe you meant that you should prefer DTLS/SRTP
> keep-alive like RTP no-op in this case. I had problem understanding thi=
s
> section. Please clarify.
>=20

No the text did not meant to choose one over the other, just to explain
the pros and cons of running the STUN Binding Indication usage over DTLS.=


I propose this new text:

"  When STUN is being used for media keep-alive (described in Section
   10 of [RFC5245]), it runs alongside an RTP or RTCP session.  It is
   possible to send the media keep-alive packets inside a separately
   negotiated non-SRTP DTLS session if DTLS-SRTP [RFC5764] is used, but
   that would add overhead, with minimal security benefit."

Thanks.

--=20
Marc Petit-Huguenin
Developer  |  Jive Communications, Inc.
Jive.com  |  marcph@getjive.com


--msiLotwfcNFUm5B0EPXeq3dj88FxfULaH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqDsIAAoJEMUNRP98lsiXzDoH/0QkeOfbidh0ww68p0K5RprC
xrrHMQ51j/worwet8m3IQL4EWoHjCctPlofbRJIBqE22ea6u0BzlwMomPW3JlZHq
DVvq4Qwo3ZKvVYiBXyUGd2iv0O2Kmg/pUZGsdQbAzRmQl0tYdOqL5lx4RSVnhXL6
ohMDEDd1UggNgW/sqB1nWNXRiT/Yf82xnu3/IoC3izFAbqUKLydoTVOGjjuQKsnE
POIbrCUbszYqyNDrWLIojsOQMFo4s6EGhmbQz+ZKN8cj2v9JGr+RapZTw4yjz8ML
w2el9dGtkQzNMmE6MN3Vvot34pnmgSxQBtHZeNMxq2KzAG96j/fhf3avXFhS94g=
=dXDi
-----END PGP SIGNATURE-----

--msiLotwfcNFUm5B0EPXeq3dj88FxfULaH--


From nobody Mon Jun 23 10:39:55 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AC21B2929 for <ietf@ietfa.amsl.com>; Mon, 23 Jun 2014 06:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.158
X-Spam-Level: 
X-Spam-Status: No, score=0.158 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 meA628_x8EB1 for <ietf@ietfa.amsl.com>; Mon, 23 Jun 2014 06:44:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96B471B2925 for <ietf@ietf.org>; Mon, 23 Jun 2014 06:44:58 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 029B72002A; Mon, 23 Jun 2014 09:49:13 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B37E363B0F; Mon, 23 Jun 2014 09:44:56 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A4B6563AED; Mon, 23 Jun 2014 09:44:56 -0400 (EDT)
From: Michael Richardson <mcr+nomcom@sandelman.ca>
To: ietf@ietf.org
Subject: Re: second call: NomCom 2014-2015 Call for Volunteers
In-Reply-To: <C1B30304-B69A-4156-8D36-6C9C20792C88@mnot.net>
References: <15721.1401823067@sandelman.ca> <C1B30304-B69A-4156-8D36-6C9C20792C88@mnot.net>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 23 Jun 2014 09:44:56 -0400
Message-ID: <27243.1403531096@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Zo3LBxnMwXTG8fKqJFXqVEMy6jo
X-Mailman-Approved-At: Mon, 23 Jun 2014 10:39:53 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 13:45:01 -0000

--=-=-=


I had feed back that:

> I'd suggest that you'd get better participation from .au, .nz and perhaps
> parts of Asia as well if there was more transparency about how often the
> calls are, when they'll be scheduled, etc.

and I wanted to explain.

1) the first thing the newly seated nomcom usually does is adopt some
   proceedures, including a voting process.  On non-selection decisions,
   all members of the nomcom vote, including liasons; but most nomcoms
   have tried to work consensus on non-selection decisions.
   One important non-selection decision is when to have conference calls.

2) I've been on three nomcoms, and while I can't really recall 2003/2004,
   for 2012/2013 we had a regular thursday 12:00 UTC call (2hr before the
   IESG call).
   For the 2013/2014 we had a regular Tuesday 12:00 UTC, and later added
   a 04:00 UTC Thursday call.
   (I think we adjusted to daylight savings though)

12:00 UTC translates to:
          5am PDT
          8am EDT
          2pm EET
          8pm China
          9pm Tokyo
          10pm Sydney
          11pm Auckland

In 2013/2014 we picked 04:00 for the second call to reverse the night pain:
04:00 UTC translates to:
          9pm   PDT    (the night before)
          00:00 EDT    (midnight to 2am)
          6am EET
          12:00 China
          1pm   Tokyo
          2pm   Sydney
          3pm   Auckland

As many of the calls were done with G+ and included video, one could see who
was falling asleep.  There also some cats who participated in many calls.

In the list, there are people from nearly every time zone, and previous
nomcoms have been well represented around the globe, so it doesn't have to
always be painful for every call.

--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU6gvWICLcPvd0N1lAQLXEgf/S8DYhEd9XHUfy3+qeu9lZNLgXCaJpZAj
Bu7H+uMpBTvPHUY5odP9Pg1c1x8v6LcR7+WXWQzcuALVGowGpJlF8cjUwyr+D3SQ
qGX6O/tn9blwIkM208RDa4s5AN1bVJXff772vfg8V6K2+W149V1IaQ2vkz4d76ii
So0at/e5MZ933CUBGcmpOxwCC3AQBA1mOiA/tVbCL45GsJ21BUEvF5qUxAYvJFWs
p4zL2uNIvlqCIFNklLTM9U355O6F40nqxf928zi1aFmg0B3rXsf1Kkr9mPxJk+x9
0AyT4neYtwBb1fFaXTQJMaY/8mNb0EhFVpmRc2RnyaTnaD63jFfMMQ==
=mDvZ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jun 23 12:16:27 2014
Return-Path: <agenda@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93521B2CA1; Mon, 23 Jun 2014 12:16:23 -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] autolearn=ham
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 tMhrgcQp1jZC; Mon, 23 Jun 2014 12:16:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 84ACF1B2CA6; Mon, 23 Jun 2014 12:16:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Agenda <agenda@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 90 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140623191620.22420.52623.idtracker@ietfa.amsl.com>
Date: Mon, 23 Jun 2014 12:16:20 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mqIthLDJYVimlcNIXo1GpaI8ojA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 19:16:24 -0000

The IETF 90 Preliminary Agenda has been posted. The final agenda will be published on Friday, June 27th, 2014. Currently Registration and Breaks are not displaying. This will be remedied on the final agenda.

https://datatracker.ietf.org/meeting/90/agenda.html 
https://datatracker.ietf.org/meeting/90/agenda.txt 

More information regarding IETF 90 in Toronto, ON, Canada is located here: https://www.ietf.org/meeting/90/index.html 

Thank you! 

IETF Secretariat


From nobody Mon Jun 23 12:32:05 2014
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D6F1B2C01; Mon, 23 Jun 2014 12:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 zY47w-qFMnZL; Mon, 23 Jun 2014 12:32:01 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 EB0201A02BB; Mon, 23 Jun 2014 12:32:00 -0700 (PDT)
Received: from [10.0.1.23] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s5NJVvET045250 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 23 Jun 2014 14:31:59 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.23]
Content-Type: text/plain; charset=us-ascii
Subject: Gen-ART Telechat Review of draft-kelsey-intarea-mesh-link-establishment-06
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ben Campbell <ben@nostrum.com>
Date: Mon, 23 Jun 2014 14:31:56 -0500
X-Mao-Original-Outgoing-Id: 425244716.831463-1fec653ef45d0dd71fdcf494d6380acc
Content-Transfer-Encoding: quoted-printable
Message-Id: <F94B5A66-70E1-47D2-8525-7BFC41020809@nostrum.com>
To: draft-kelsey-intarea-mesh-link-establishment.all@tools.ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uiI16gLbHVWnwQ0F4oNO3PzPzSw
Cc: Private Gen-ART Mailing List <gen-art-private@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 19:32:02 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-kelsey-intarea-mesh-link-establishment-06
Reviewer: Ben Campbell
Review Date:  2014-06-23
IESG Telechat date: 2014-06-26

Summary: This draft is ready for publication as a proposed standard. My =
comments on version 05 at IETF last call have been addressed to my =
satisfaction.


Major issues:

None.

Minor issues:

None.

Nits/editorial comments:

None.=


From nobody Tue Jun 24 08:41:02 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A621B2D98 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 08:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Wa2osGkrS4ui for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 08:40:56 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA5C1B2D92 for <ietf@ietf.org>; Tue, 24 Jun 2014 08:38:49 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id x13so531619wgg.3 for <ietf@ietf.org>; Tue, 24 Jun 2014 08:38:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=hY8yNP1lJo5KAUkjRMfzxcF1QSmhTJcI07tXf2AHnnU=; b=AMOfi+t8y2TI+EMqxRaLmnoYLtF3FqwYggpp0mCWbga9rsPr0n4sb7GiPk1BI77izK UZ7v+7C1T07pp18OiSrk8pagtmNM8GPvQSXNJhPqTllpWxzDkUaYMT3pcUf8GgE1LlLs AJHl6iaOp8Olnhsziheuz2ihJi3rIutCaaouESobADoZYIlgWooKTC6jFJPyA5Rwg81G by3Y4M+vG7a+N/Xs2ZX6XOUpkpWhHHriTRCF0WZrlokLfHt61TgoZgkRAJZIqeyhK0ZC n1lpFGeFii8nrzcub/kmEopvGMGPNNd6L9mYFzYen+LWOlW2skirDoygjmWrC3NT49tr NHKA==
MIME-Version: 1.0
X-Received: by 10.180.184.198 with SMTP id ew6mr35570602wic.13.1403624325320;  Tue, 24 Jun 2014 08:38:45 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Tue, 24 Jun 2014 08:38:45 -0700 (PDT)
Date: Tue, 24 Jun 2014 11:38:45 -0400
X-Google-Sender-Auth: rI3mdpiqGjxG2wbDDthFpn0R4Nc
Message-ID: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
Subject: Time to move beyond the 32 bit Internet.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3348c4f15ea04fc96c12d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yB-VcudTvZlCpfCbZvcfTXMuuWo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 15:40:57 -0000

--001a11c3348c4f15ea04fc96c12d
Content-Type: text/plain; charset=UTF-8

This might be a random thought, but one of the main problems we have as an
organization is getting people to take deployment of IETF specs seriously.
Particularly when they are enhancements of existing specs that work 'well
enough' for existing users.

While going through the Windows API calls and thinking how old fashioned
and lame all those 'Win32' classes look now, a sudden thought:

Ordinary users don't understand the importance of going from IPv4 to IPv6.

But Ordinary users do understand that 32 bits is bad and old and obsolete
and rubbish and 64 bits is better.


So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is your
Internet service 32 bit or 128'?


This might sound a trivial matter but I can assure you its not. Banging on
about how the wealthy Wall Street types got a bailout during Bush's fiscal
crisis got nowhere. "The wealth of the 1% or the welfare of the 99%" had
real effect.

--001a11c3348c4f15ea04fc96c12d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This might be a random thought, but one of the main proble=
ms we have as an organization is getting people to take deployment of IETF =
specs seriously. Particularly when they are enhancements of existing specs =
that work &#39;well enough&#39; for existing users.<div>
<br></div><div>While going through the Windows API calls and thinking how o=
ld fashioned and lame all those &#39;Win32&#39; classes look now, a sudden =
thought:</div><div><br></div><div>Ordinary users don&#39;t understand the i=
mportance of going from IPv4 to IPv6.=C2=A0</div>
<div><br></div><div>But Ordinary users do understand that 32 bits is bad an=
d old and obsolete and rubbish and 64 bits is better.</div><div><br></div><=
div><br></div><div>So lets stop asking ISPs &#39;do you support IPv6&#39; a=
nd instead ask &#39;Is your Internet service 32 bit or 128&#39;?</div>
<div><br></div><div><br></div><div>This might sound a trivial matter but I =
can assure you its not. Banging on about how the wealthy Wall Street types =
got a bailout during Bush&#39;s fiscal crisis got nowhere. &quot;The wealth=
 of the 1% or the welfare of the 99%&quot; had real effect.<br>
</div></div>

--001a11c3348c4f15ea04fc96c12d--


From nobody Tue Jun 24 12:28:11 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D45F1B2BD1 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 12:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 J378VqSW7ReH for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 12:28:07 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtp001.mac.com [17.158.236.236]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54E831B2B09 for <ietf@ietf.org>; Tue, 24 Jun 2014 12:28:07 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.19] (unknown [90.155.50.12]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0N7O006CSU25W780@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Tue, 24 Jun 2014 19:27:43 +0000 (GMT)
Subject: Re: Time to move beyond the 32 bit Internet.
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
Date: Tue, 24 Jun 2014 20:27:30 +0100
Content-transfer-encoding: quoted-printable
Message-id: <30710E7F-9185-4DC3-9E7D-BE93ED56C30F@me.com>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.1878.6)
X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaGxEKTEMXGx0EGx8SBBscHwQdGRAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbGRpiTk0bdRhEdRl4c wcfZRsTGB1CaBEKRUMXFhkaHRsabx1sBxMbEh8HHm5pGQcTbx1uB2hvExlvbh8caRkabGpHTwR JRUcUEQpYXBcZBBoEGx4HTU4cExoaHRMFGx0EGx8SBBscHwQdGRAbHhofGxEKXlkXYRkZcmERC kxGF2xraxEKQ1oXExoEGx8fBB8aBBsYEQpEWBcYEQpESRcbEQpCRRdmUH1dH21kGgVIYxEKQk4 XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXaAFkeE5jH G54YhkRCnBoF2BeAXBPQ0VlG0YYEQpwaBdtbm56f1gdZF1BHBEKcGgXYhN6SWAbeWtCXx8RCnB oF2NeX0IabGJvY0FFEQpwaBdiTxwTU0gYYX4dQREKcGwXa2ZOa0FlX2ZTZwERCnBMF25dTHl+H X5kRXhZEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.14,0.0.0000 definitions=2014-06-24_10:2014-06-24,2014-06-24,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406240221
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7PHZ2kTSZY60SqWZomDbYNHcarA
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 19:28:09 -0000

On 24 Jun 2014, at 16:38, Phillip Hallam-Baker <phill@hallambaker.com> =
wrote:
> This might be a random thought, but one of the main problems we have =
as an organization is getting people to take deployment of IETF specs =
seriously. Particularly when they are enhancements of existing specs =
that work 'well enough' for existing users.

Having fielded yet another =93IPv6 is moronic! I can explain =
IPv4+DHCP+NAT in five seconds, but IPv6 is just sooooooooo complicated!=94=
 exchange, which ended (as usual) with the admin both not deploying the =
protocol and accusing the IETF of =93Rolling over=94 when the end-user =
CPE makers can=92t pull their fingers out, I do wonder whether we =
shouldn=92t be shouting ever-so-slightly louder from the rooftops?

I do my best, honest, but I think it=92s just possible that we should be =
trying to make =93UX=94 some sort of priority.

Of course we all know that IPv6 is *supposed* to work out of the box, =
but it seems to me that we do not even attract *market* power, and we=92re=
 essentially going by social response alone.  People who can will =
continue to use kludges, because honestly, they actually do work.  And =
the end-user is driving that apathy.

> While going through the Windows API calls and thinking how old =
fashioned and lame all those 'Win32' classes look now, a sudden thought:
>=20
> Ordinary users don't understand the importance of going from IPv4 to =
IPv6.=20
>=20
> But Ordinary users do understand that 32 bits is bad and old and =
obsolete and rubbish and 64 bits is better.
>=20
>=20
> So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is =
your Internet service 32 bit or 128'?
>=20
>=20
> This might sound a trivial matter but I can assure you its not. =
Banging on about how the wealthy Wall Street types got a bailout during =
Bush's fiscal crisis got nowhere. "The wealth of the 1% or the welfare =
of the 99%" had real effect.

Mmm.  I like the way you think. :)

Cheers,
Sabahattin


From nobody Tue Jun 24 13:06:56 2014
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A74E21ACD01 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 13:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.348
X-Spam-Level: 
X-Spam-Status: No, score=0.348 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 taJxEnhY6KQH for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 13:06:53 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 953F81A0657 for <ietf@ietf.org>; Tue, 24 Jun 2014 13:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s5OK6iOE001302; Tue, 24 Jun 2014 22:06:44 +0200 (CEST)
Received: from [192.168.217.106] (p54891224.dip0.t-ipconnect.de [84.137.18.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4C43B1BF9; Tue, 24 Jun 2014 22:06:43 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
Date: Tue, 24 Jun 2014 22:06:41 +0200
X-Mao-Original-Outgoing-Id: 425333201.810942-aa9b3e94d9b88347218ec5d2b857b708
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B067502-29BD-4330-B627-A09898BAEB1D@tzi.org>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MF_DBWCc2gQlgBJ9JzScv9QkExw
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 20:06:55 -0000

On 24 Jun 2014, at 17:38, Phillip Hallam-Baker <phill@hallambaker.com> =
wrote:

> 'Is your Internet service 32 bit or 128'?

Yeah, I googled =93128-bit Internet=94 and found this article which =
shows everything you need to do.

http://www.errorfixes.net/128-bit-internet-explorer.php
(including a link "click here to download the 128 Bit Internet Explorer =
repair program.=94)

Gr=FC=DFe, Carsten


(For the humor-impaired: This appears to be an adware site, one of many =
you find with Google under the search term =93128-bit Internet=94.)


From nobody Tue Jun 24 14:23:32 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 677421B2823; Tue, 24 Jun 2014 14:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level: 
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 JSxG5zYwWow9; Tue, 24 Jun 2014 14:23:25 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67E8A1B28AC; Tue, 24 Jun 2014 14:14:35 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5OLEYFf029926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Jun 2014 17:14:34 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s5OLEYFf029926
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1403644474; bh=Ppwy6ashI5Jrm5Nj/bzDEyLmplo=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ED85yU5C1GJ0AOME65AyDnz6S66VqMli7LX3OMwSgOVRalb0wjHulSnUADzSSPcGW 2hQdHxizHZN0wyFEMZWfe6yHXnYJDH3TdVAui7iX/fyMV4Bt1vBqg1PjjKaSj29hUh Ykdr/hrKH3kqD57aTC88uEcnewX7BWplOINqt9Fc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s5OLEYFf029926
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 24 Jun 2014 17:14:16 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5OLEFlq006000 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Jun 2014 17:14:16 -0400
Received: from mx15a.corp.emc.com ([169.254.1.248]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Tue, 24 Jun 2014 17:14:15 -0400
From: "Black, David" <david.black@emc.com>
To: "ietf@trammell.ch" <ietf@trammell.ch>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Tue, 24 Jun 2014 17:14:14 -0400
Subject: RE: Gen-ART review of draft-ietf-ipfix-text-adt-05
Thread-Topic: Gen-ART review of draft-ietf-ipfix-text-adt-05
Thread-Index: Ac929V7zhjIWDi0GQXixOzBRCQWkcQY+uSkA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712077005024C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C662F4B@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C662F4B@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public, Resumes
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AORrUZbfBYVflshsCe39oQ2DpBI
Cc: "ietf@ietf.org" <ietf@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 21:23:28 -0000

The -06 version of this draft addresses all of the comments in the
Gen-ART review of the -05 version.

Nit: I suggest one minor clarification in the added text (insertion
of the word "comparing" is the primary purpose of this change, feel
free to edit to taste):

OLD
   See
   [RFC6885] and [I-D.ietf-precis-framework] for more on the dangers of
   Unicode strings..
NEW
   See
   [RFC6885] and [I-D.ietf-precis-framework] for more on possible
   unexpected results and related risks in comparing Unicode strings.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Friday, May 23, 2014 10:11 PM
> To: ietf@trammell.ch; General Area Review Team (gen-art@ietf.org)
> Cc: ipfix@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-ipfix-text-adt-05
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-ipfix-text-adt-05
> Reviewer: David L. Black
> Review Date: May 23, 2014
> IETF LC End Date: May 28, 2014
>=20
> Summary:  This draft is on the right track, but has open issues
> 		described in the review.
>=20
> This is a relatively short draft defining textual representations of
> IPFIX data elements.  It's clear and easy to read.
>=20
> I assume that all the ABNF has been checked.  The open issues involve
> use of Unicode.
>=20
> Minor issues:
>=20
> Section 4.7 string
>=20
>    As Information Elements of the string type are simply UTF-8 encoded
>    strings, they are represented directly, subject to the escaping and
>    encoding rules of the Enclosing Context.
>=20
> There's nothing "simply" about use of UTF-8 encoded strings :-).
>=20
> There appear to be no restrictions on Unicode codepoint usage and no
> requirements for string normalization or other preparation either in this
> draft or RFC 7011.  This can be a formula for all sorts of mischief, so
> some warnings about what's possible should be added somewhere - some of
> these comments may be raising Unicode concerns in RFC 7011 that would
> be better addressed there.
>=20
> A general warning about unreliability of Unicode string comparison
> is in order.  This also applies if an identifier that is not limited
> to ASCII characters is substituted for an integer as described in
> Section 4.2.  In addition, the concerns around visually similar
> characters discussed in section 10.5 of the pr=E9cis framework draft
> (draft-ietf-pr=E9cis-framework) apply; a short summary and pointer
> to that section of that draft should suffice.
>=20
> Section 4.1.5 of the pr=E9cis framework draft warns against use of mixed-
> direction Unicode strings, as "there is currently no widely accepted and
> implemented solution for the processing and safe display of mixed-
> direction strings."  That warning deserves repetition here.
>=20
> Lots of mischief is possible with non-printing and control characters -
> I would expect that the Enclosing Context contains sufficient restriction=
s
> on use of Unicode to deal with most of this concern, and would state that
> expectation.  This comment is definitely specific to this draft.
>=20
> Nits/editorial comments:
>=20
> Section 4.4 float32 and float64
>=20
>    exponent =3D ( "e" / "E" ) [sign] 1*3DIGIT
>=20
> Please explain why no more than 3 digits are ever required.
>=20
> Section 4.8 dateTime*
>=20
> The '*' in the section title, dateTime* is clever, but it's meaning is no=
t
> obvious.  I suggest "The dateTime Data Types" as a better section title.
>=20
> Section 5 Security Considerations
>=20
>    The security considerations for the IPFIX Protocol [RFC7011] apply;
>    this document presents no additional security considerations.
>=20
> That's ok, although adding a direct mention of the [UTF8-EXPLOIT] TR
> cited in RFC 7011 would be helpful.
>=20
> idnits 2.13.01 warns that the JSON reference (RFC 4627) is obsolete, and
> needs to be replaced with one or two current RFC references.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From nobody Tue Jun 24 14:26:15 2014
Return-Path: <flyingkiwiguy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87001AD62A for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 14:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 GKmieqz4hHjC for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 14:26:11 -0700 (PDT)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8E5B1B28F4 for <ietf@ietf.org>; Tue, 24 Jun 2014 14:21:30 -0700 (PDT)
Received: by mail-ve0-f178.google.com with SMTP id oy12so1024682veb.37 for <ietf@ietf.org>; Tue, 24 Jun 2014 14:21:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2n3rZstnDi15NGnql7MXGffpKcgqN15Gf42QZISq9KA=; b=UyxvR0qnH2bSLvZwWCPhVcgiIjHGO3gITMR/qjhHYrth38ea8Ocl5jrA/YLAukJ5k+ 9IOmTG8vZpeEfvPGvBEBdYEBEAnfANSMH05XvvSRZPcGSj6zROTGTCq/PyS7fXwxcJUI Klzic5f7c3JuGn5ZnSmj3GXE6m/xssbAnCO/+bTBFNFh8D6UfEr7YEcTNe6YNxwoez19 j7PczW/jshIpujduP10UtqyJ8KQmiNmZgGZTvB0plV/P9ro7ZGQS2ocP98hujeabT5sO QTLd/5RPnqG9RrIZ8QAInvm5EuNxF8VnGKnmyy6oMyt9PIXBDCj2rdqjBB1rN5vnM1VQ DOMA==
X-Received: by 10.52.25.228 with SMTP id f4mr2361963vdg.62.1403644890065; Tue, 24 Jun 2014 14:21:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.40.13 with HTTP; Tue, 24 Jun 2014 14:20:49 -0700 (PDT)
In-Reply-To: <5B067502-29BD-4330-B627-A09898BAEB1D@tzi.org>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <5B067502-29BD-4330-B627-A09898BAEB1D@tzi.org>
From: Gary Mulder <flyingkiwiguy@gmail.com>
Date: Tue, 24 Jun 2014 22:20:49 +0100
Message-ID: <CAKy9zTDkWgDDA_Meks4qFjfKBZijvWk7zm-LTbEu2QycUkE7eQ@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a1136976410305404fc9b8b2c
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1rSscOoJA77NiFGXLU7IDM5k7z4
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 21:26:13 -0000

--001a1136976410305404fc9b8b2c
Content-Type: text/plain; charset=UTF-8

People, ISPs, etc. will move to the 128-bit Internet when they're forced to
and no sooner. The fact that there is a workable solution to a known
problem both proposed and implemented means that the transition will be
less painful that it would be if there was no alternative and people are
forced to "go digital or else".

It is a credit to the IETF that a multi-decadal design still functions
amazingly well and no dictatorial edict requires that all unilaterally
relinquish all the perceived advantages of IPv4 until there is consensus
and need to do so. Survival of the fittest!

Regards,
Gary (sent from an IPv4 IP, sorry...)

--001a1136976410305404fc9b8b2c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">People, ISPs, etc. will move to the 128-bit Internet when =
they&#39;re forced to and no sooner. The fact that there is a workable solu=
tion to a known problem both proposed and implemented means that the transi=
tion will be less painful that it would be if there was no alternative and =
people are forced to &quot;go digital or else&quot;.<div>

<br></div><div>It is a credit to the IETF that a multi-decadal design still=
 functions amazingly well and no dictatorial edict requires that all unilat=
erally relinquish all the perceived advantages of IPv4 until there is conse=
nsus and need to do so. Survival of the fittest!</div>

<div><br></div><div>Regards,</div><div>Gary (sent from an IPv4 IP, sorry...=
)</div></div>

--001a1136976410305404fc9b8b2c--


From nobody Tue Jun 24 14:41:41 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 496B81B2893; Tue, 24 Jun 2014 14:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 uryY-o9SGqUi; Tue, 24 Jun 2014 14:41:37 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F365A1A039C; Tue, 24 Jun 2014 14:41:36 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5OLfXLs025887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Jun 2014 17:41:34 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s5OLfXLs025887
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1403646094; bh=zGeTiLfSfkdI9CR4/kXbAaJQ5bM=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=PE5fmMuxLLDSs6HisbMQWXIsZ0ldK87G1LKSM/dpicSdHEWbpN79OjVenZWGCv6WT +KAjHndBSBODYjNRNjmtOaoqzNaq+pSGD1rCGw6JX6yOl25VQ9VbOgc3Lq/HMITKlG eyRM8tOYyZDgkT6/0ZQpZauKITHIf60eUqpMsiV8=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s5OLfXLs025887
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd03.lss.emc.com (RSA Interceptor); Tue, 24 Jun 2014 17:41:26 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s5OLfP9m029162 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Jun 2014 17:41:26 -0400
Received: from mx15a.corp.emc.com ([169.254.1.248]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Tue, 24 Jun 2014 17:41:26 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "ietf@trammell.ch" <ietf@trammell.ch>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Tue, 24 Jun 2014 17:41:24 -0400
Subject: Gen-ART review of draft-ietf-ipfix-text-adt-06
Thread-Topic: Gen-ART review of draft-ietf-ipfix-text-adt-06
Thread-Index: Ac+P9QvTQoRjqJt7QiGkc8Ukj7DjIQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120770050255@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public, Resumes
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/249AIDVtVGzntRAlJzzK5NJmj6A
Cc: "ietf@ietf.org" <ietf@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 21:41:39 -0000

With correct subject line this time ...

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Black, David
> Sent: Tuesday, June 24, 2014 5:14 PM
> To: ietf@trammell.ch; General Area Review Team (gen-art@ietf.org)
> Cc: ietf@ietf.org; ipfix@ietf.org
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ipfix-text-adt-05
>=20
> The -06 version of this draft addresses all of the comments in the
> Gen-ART review of the -05 version.
>=20
> Nit: I suggest one minor clarification in the added text (insertion
> of the word "comparing" is the primary purpose of this change, feel
> free to edit to taste):
>=20
> OLD
>    See
>    [RFC6885] and [I-D.ietf-precis-framework] for more on the dangers of
>    Unicode strings..
> NEW
>    See
>    [RFC6885] and [I-D.ietf-precis-framework] for more on possible
>    unexpected results and related risks in comparing Unicode strings.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Friday, May 23, 2014 10:11 PM
> > To: ietf@trammell.ch; General Area Review Team (gen-art@ietf.org)
> > Cc: ipfix@ietf.org; ietf@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-ipfix-text-adt-05
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-ipfix-text-adt-05
> > Reviewer: David L. Black
> > Review Date: May 23, 2014
> > IETF LC End Date: May 28, 2014
> >
> > Summary:  This draft is on the right track, but has open issues
> > 		described in the review.
> >
> > This is a relatively short draft defining textual representations of
> > IPFIX data elements.  It's clear and easy to read.
> >
> > I assume that all the ABNF has been checked.  The open issues involve
> > use of Unicode.
> >
> > Minor issues:
> >
> > Section 4.7 string
> >
> >    As Information Elements of the string type are simply UTF-8 encoded
> >    strings, they are represented directly, subject to the escaping and
> >    encoding rules of the Enclosing Context.
> >
> > There's nothing "simply" about use of UTF-8 encoded strings :-).
> >
> > There appear to be no restrictions on Unicode codepoint usage and no
> > requirements for string normalization or other preparation either in th=
is
> > draft or RFC 7011.  This can be a formula for all sorts of mischief, so
> > some warnings about what's possible should be added somewhere - some of
> > these comments may be raising Unicode concerns in RFC 7011 that would
> > be better addressed there.
> >
> > A general warning about unreliability of Unicode string comparison
> > is in order.  This also applies if an identifier that is not limited
> > to ASCII characters is substituted for an integer as described in
> > Section 4.2.  In addition, the concerns around visually similar
> > characters discussed in section 10.5 of the pr=E9cis framework draft
> > (draft-ietf-pr=E9cis-framework) apply; a short summary and pointer
> > to that section of that draft should suffice.
> >
> > Section 4.1.5 of the pr=E9cis framework draft warns against use of mixe=
d-
> > direction Unicode strings, as "there is currently no widely accepted an=
d
> > implemented solution for the processing and safe display of mixed-
> > direction strings."  That warning deserves repetition here.
> >
> > Lots of mischief is possible with non-printing and control characters -
> > I would expect that the Enclosing Context contains sufficient restricti=
ons
> > on use of Unicode to deal with most of this concern, and would state th=
at
> > expectation.  This comment is definitely specific to this draft.
> >
> > Nits/editorial comments:
> >
> > Section 4.4 float32 and float64
> >
> >    exponent =3D ( "e" / "E" ) [sign] 1*3DIGIT
> >
> > Please explain why no more than 3 digits are ever required.
> >
> > Section 4.8 dateTime*
> >
> > The '*' in the section title, dateTime* is clever, but it's meaning is =
not
> > obvious.  I suggest "The dateTime Data Types" as a better section title=
.
> >
> > Section 5 Security Considerations
> >
> >    The security considerations for the IPFIX Protocol [RFC7011] apply;
> >    this document presents no additional security considerations.
> >
> > That's ok, although adding a direct mention of the [UTF8-EXPLOIT] TR
> > cited in RFC 7011 would be helpful.
> >
> > idnits 2.13.01 warns that the JSON reference (RFC 4627) is obsolete, an=
d
> > needs to be replaced with one or two current RFC references.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Jun 24 15:05:23 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2601B28E4 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 15:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.852
X-Spam-Level: 
X-Spam-Status: No, score=-3.852 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 jaBaSEHLHxjd for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 15:05:19 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10AF71B28CF for <ietf@ietf.org>; Tue, 24 Jun 2014 15:05:18 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s5OM5DBH026851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 00:05:13 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 25 Jun 2014 00:05:13 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yV9fzPUijjlK4w2sksPEtjpbymQ
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 22:05:21 -0000

Phillip Hallam-Baker wrote:
> 
> While going through the Windows API calls and thinking how old fashioned
> and lame all those 'Win32' classes look now, a sudden thought:
> 
> Ordinary users don't understand the importance of going from IPv4 to IPv6.
> 
> But Ordinary users do understand that 32 bits is bad and old and obsolete
> and rubbish and 64 bits is better.

Experienced users know painfully well just how smooth and painless
32-bit (windows) and 32-bit IPv4 is, whereas newer 64-bit (windows)
and newer 128-bit IPv6 is just many painful problems and ZERO benefit.

A lot of the equipment that me and my family is using is not IPv6 capable,
and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
***MUCH*** better when configured with IPv4-only anyway, so why bother.

If someone needs to be pushed, then it is *VENDORS*, not users,
that they ship their equipment in a fashion that it will work with IPv6,
should this ever become available.  Then maybe in 10 years from now,
this might become interesting to end users.


-Martin


From nobody Tue Jun 24 15:50:10 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D754D1B2969 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 15:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 m93N8otF4UWl for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 15:50:07 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05F4C1B2967 for <ietf@ietf.org>; Tue, 24 Jun 2014 15:50:06 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id wp4so1156960obc.40 for <ietf@ietf.org>; Tue, 24 Jun 2014 15:50:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X7k6WycFqPXbgxBeltfLViY8GejSbtKFzZ9/swwrsWY=; b=XeQEvaI3RK/og1TP+F5gsWEFrnwyKq8YVTYN0yltov4JvWBTk5MRMzEnQv3PT3hMNW 3NDk7BcbY8JyPm70+rTlyVktSlTL9oPhwmRzmjev4ugMaJxdI9ElBuq/v/OpWhckJ6nS HO62LMQk7UtLqqemD2u6ryLFiKHXRHEfVE2jU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=X7k6WycFqPXbgxBeltfLViY8GejSbtKFzZ9/swwrsWY=; b=MJSPKQ28/N2PxjrsnnY76iSbBlksz+Gi6Af4DmI8vAr7w6cjPGRBoy8vY5HEd5+Xoi 27MrRcXnITTPZlGLBb2cTuyk2bTlqDXhQIaB79RTePcH9+fLceJk38ZBscBUC1ZdoPbB kZrnxKQu304dwfzPY6p73irTgJnfyFa6NeKHQL7w290OCoScJGW2OKsBfbMCU5TuO/2g N84Jt+CBpgwsCgPAEjCN4sRRbfiLSNFzm/lXyI5NSxPrQIA2No3zdbamYvVsJ8drWEEU 8O6PEYqUtn5Al2+VFhZdH9A4Ae3oxRWDc9mm/cQ379U+zH6KiOKw5Aq3UZb3+ytmCWHZ /kJA==
X-Gm-Message-State: ALoCoQlH7jWzU/hAJV4dudlb2icXaFvj3jWn1D+48m8We+B/ZppwBv6lqcUfkXKaM6I0T0YZsEPC
MIME-Version: 1.0
X-Received: by 10.182.60.65 with SMTP id f1mr4176145obr.78.1403650206469; Tue, 24 Jun 2014 15:50:06 -0700 (PDT)
Received: by 10.60.60.100 with HTTP; Tue, 24 Jun 2014 15:50:06 -0700 (PDT)
In-Reply-To: <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
Date: Tue, 24 Jun 2014 23:50:06 +0100
Message-ID: <CAKHUCzy6=_VtwQJGSaSEgB2TEm13FKCP0=UiE-KpwwDupi8miQ@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Dave Cridland <dave@cridland.net>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=089e01538ad8f2268804fc9cc7b0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/veqnDyFvMGk_qgQJaDFZLLLzZcc
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 22:50:08 -0000

--089e01538ad8f2268804fc9cc7b0
Content-Type: text/plain; charset=UTF-8

On 24 June 2014 23:05, Martin Rex <mrex@sap.com> wrote:
>
> If someone needs to be pushed, then it is *VENDORS*, not users,
>

No - user demand creates the market that'll get the vendors moving. Phillip
is spot-on, here.

--089e01538ad8f2268804fc9cc7b0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
4 June 2014 23:05, Martin Rex <span dir=3D"ltr">&lt;<a href=3D"mailto:mrex@=
sap.com" target=3D"_blank">mrex@sap.com</a>&gt;</span> wrote:<blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">

If someone needs to be pushed, then it is *VENDORS*, not users,<br></blockq=
uote><div>=C2=A0</div><div>No - user demand creates the market that&#39;ll =
get the vendors moving. Phillip is spot-on, here.</div></div></div></div>

--089e01538ad8f2268804fc9cc7b0--


From nobody Tue Jun 24 16:44:53 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8A21B29B6 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 16:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 Zkl_yVun8TRF for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 16:44:49 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC0061B29CB for <ietf@ietf.org>; Tue, 24 Jun 2014 16:44:49 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 6B2E334942C; Tue, 24 Jun 2014 23:44:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 73B0716005B; Tue, 24 Jun 2014 23:51:59 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 432E4160059; Tue, 24 Jun 2014 23:51:59 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 77AB6193C5DD; Wed, 25 Jun 2014 09:44:44 +1000 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
Subject: Re: Time to move beyond the 32 bit Internet.
In-reply-to: Your message of "Wed, 25 Jun 2014 00:05:13 +0200." <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 09:44:44 +1000
Message-Id: <20140624234444.77AB6193C5DD@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OGcD8iiU5J1HWEhY7_8MN_ALOLE
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 23:44:51 -0000

In message <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>, Martin Rex writes:
> Phillip Hallam-Baker wrote:
> > 
> > While going through the Windows API calls and thinking how old fashioned
> > and lame all those 'Win32' classes look now, a sudden thought:
> > 
> > Ordinary users don't understand the importance of going from IPv4 to IPv6.
> > 
> > But Ordinary users do understand that 32 bits is bad and old and obsolete
> > and rubbish and 64 bits is better.
> 
> Experienced users know painfully well just how smooth and painless
> 32-bit (windows) and 32-bit IPv4 is, whereas newer 64-bit (windows)
> and newer 128-bit IPv6 is just many painful problems and ZERO benefit.
> 
> A lot of the equipment that me and my family is using is not IPv6 capable,
> and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
> ***MUCH*** better when configured with IPv4-only anyway, so why bother.
> 
> If someone needs to be pushed, then it is *VENDORS*, not users,
> that they ship their equipment in a fashion that it will work with IPv6,
> should this ever become available.  Then maybe in 10 years from now,
> this might become interesting to end users.

Given there are ISP delivering IPv6 + DS-Lite today over fibre
because they have run out of addresses it is time that *everybody*
starts complaining to every supplier that doesn't ship equipement
/ services with IPv6 enabled by default.

> -Martin
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Jun 24 16:55:52 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86DE71B29DA for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 16:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 4XdkVd3Enzub for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 16:55:48 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B69A1B29B6 for <ietf@ietf.org>; Tue, 24 Jun 2014 16:55:48 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s5ONthnE028828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 01:55:43 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <20140624234444.77AB6193C5DD@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
Date: Wed, 25 Jun 2014 01:55:43 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/21jGUi10veSJlwcHL6XikXEB080
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 23:55:50 -0000

Mark Andrews wrote:
> 
> Martin Rex writes:
> >
> > Phillip Hallam-Baker wrote:
> > > 
> > > While going through the Windows API calls and thinking how old fashioned
> > > and lame all those 'Win32' classes look now, a sudden thought:
> > > 
> > > Ordinary users don't understand the importance of going from IPv4 to IPv6.
> > > 
> > > But Ordinary users do understand that 32 bits is bad and old and obsolete
> > > and rubbish and 64 bits is better.
> > 
> > Experienced users know painfully well just how smooth and painless
> > 32-bit (windows) and 32-bit IPv4 is, whereas newer 64-bit (windows)
> > and newer 128-bit IPv6 is just many painful problems and ZERO benefit.
> > 
> > A lot of the equipment that me and my family is using is not IPv6 capable,
> > and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
> > ***MUCH*** better when configured with IPv4-only anyway, so why bother.
> > 
> > If someone needs to be pushed, then it is *VENDORS*, not users,
> > that they ship their equipment in a fashion that it will work with IPv6,
> > should this ever become available.  Then maybe in 10 years from now,
> > this might become interesting to end users.
> 
> Given there are ISP delivering IPv6 + DS-Lite today over fibre
> because they have run out of addresses it is time that *everybody*
> starts complaining to every supplier that doesn't ship equipement
> / services with IPv6 enabled by default.


Why would any private individual want to get an IPv6 address?
With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
you may have at least a vague chance that your ID doesn't stick out
of every IP datagram like a sore thumb.  With IPv6, you're stripped
naked for traffic analysis by every governmental agency worldwide, no matter
how strong you encrypt your traffic.

The end-2-end principle is equivalent to a fairly complete loss of privacy.
Really, I'm glad that I can use IPv4 and get a new IPv4 address assigned
several times a day.

-Martin


From nobody Tue Jun 24 17:16:41 2014
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501A51B29DA for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.952
X-Spam-Level: 
X-Spam-Status: No, score=-2.952 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 SyBD-ahUJgU9 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:16:37 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.135.88]) by ietfa.amsl.com (Postfix) with ESMTP id 3915A1B29D9 for <ietf@ietf.org>; Tue, 24 Jun 2014 17:16:37 -0700 (PDT)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Tue, 24 Jun 2014 19:16:30 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f174.google.com [209.85.223.174] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ie0-f174.google.com with SMTP id lx4so998500iec.33 for <ietf@ietf.org>; Tue, 24 Jun 2014 17:16:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Qtoc0mGYVG0PUPznSEyq1FdyyTTi1nOdTetTE0hYSFE=; b=N1Jx+OU+tMvsA2ys0eIxnj6CsZW3wPUVp5Mu00/2pBHrK/Y650/agoNn+T5N/DsG9m BhQzv9G7flKYS3cKsk6M7rpKRUwSeP9np1tiT7/iBOaWb402on/BbERDN/gL+aJ3Y3Hb HcnqWsfinz9RZ8f0JruJkBW0QpErh9l+/5x9/H3MY4Gbz0CpUEMEIY+FXYIjhyZypo/k Kd6HuIkdhE+8Zbq3INpmnG3ZzRgN1zp+phm5cMeJ+8CQiwBiu5MJkRaggCY7FAjWHesI 3/hi6uXZXG05k3M+rcPGSmZQiXltTpCOawiINXHl0TZciZgJFKZD1ErURzi6BwYLT0gc IigA==
X-Gm-Message-State: ALoCoQm9MqLrkyGX8tA+WaQjIA78yRp3EMbi2+Pk6HujOJY6nQiHyM2KpuxW98iALsSMVDiVMiK1JEHZ1S/zl+c2nMkT9aAzMhmBsIZGRE+nEzU1txAm6jg=
X-Received: by 10.42.25.19 with SMTP id y19mr3974208icb.45.1403655390460; Tue, 24 Jun 2014 17:16:30 -0700 (PDT)
X-Received: by 10.42.25.19 with SMTP id y19mr3974196icb.45.1403655390238; Tue, 24 Jun 2014 17:16:30 -0700 (PDT)
Received: from x-134-84-88-66.nts.umn.edu (x-134-84-88-66.nts.umn.edu. [134.84.88.66]) by mx.google.com with ESMTPSA id dz3sm1858959igb.3.2014.06.24.17.16.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Jun 2014 17:16:29 -0700 (PDT)
Message-ID: <53AA14DA.6080504@umn.edu>
Date: Tue, 24 Jun 2014 19:16:26 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: mrex@sap.com, Mark Andrews <marka@isc.org>
Subject: Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
In-Reply-To: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Xp4E808jgh2nwm6GHSfHjneuixs
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 00:16:39 -0000

On 6/24/14, 18:55 , Martin Rex wrote:

> Why would any private individual want to get an IPv6 address?
> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
> you may have at least a vague chance that your ID doesn't stick out
> of every IP datagram like a sore thumb.  With IPv6, you're stripped
> naked for traffic analysis by every governmental agency worldwide, no matter
> how strong you encrypt your traffic.
>
> The end-2-end principle is equivalent to a fairly complete loss of privacy.
> Really, I'm glad that I can use IPv4 and get a new IPv4 address assigned
> several times a day.

But do you really get a different IPv4 address?  In the situation you 
discuss that is completely up to your provider, not really up to you. 
With IPv6 my laptop, iPhone, and iPad are continually changing their 
IPv6 address and my devices are in control of the address selected not 
my providers.  For IPv4 my address for my home NAT changes only every 6 
months or so at best.

No if you mean you IPv4 address changes as you go from home to work to 
the mall, etc...  But, the same thing is true for IPv4.  Change in the 
world is inevitable, get over it.

I recommend you read the Why64 draft, it talks about both security and 
privacy provided by 64 bit host addresses.

http://tools.ietf.org/html/draft-ietf-6man-why64

As for 32bit vs. 128bit Internet, nice spin, doesn't hut, but not a new 
idea, just not a silver bullet either.


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Tue Jun 24 17:26:45 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2DFA1B29D9 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 xUq9rU8AtVOh for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:26:41 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 919311B29CD for <ietf@ietf.org>; Tue, 24 Jun 2014 17:26:41 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id x12so1199664wgg.10 for <ietf@ietf.org>; Tue, 24 Jun 2014 17:26:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wICy7voQNn9MCOfYdfvURKUAe989lQZFIXKEyziczDs=; b=zLEaJKKSGmNqQt+YeieQtggCHZccH+5X3e1P+iH93xnG0YRlFLk+lwVnHQ734AXGb+ Ens0DzRzjqk3x7HYeB+tlMYU6C9naVSF0MEl1gclTTA2x2PH2j/DbSmY9IA/PhPNF7V1 MTED417xAblcJNp0IhvsZqPYeZZckh+ty9DhDD9e3RNDuAOvdlHjZ4VzUZ05XO3t39+x Se7AEmt5c1ZkOtmu+Sw1j1R1n6NQ6on11UboBwqsY4VVtZj9HUXsvl3uFEI66AaQMKom WBtFzko4gdNsTjkYlp+7xWh/0ZCHse17+UUTNzC7oGrcumCfRioHkqjMSJV/c0AkNkSc zT5A==
MIME-Version: 1.0
X-Received: by 10.194.200.67 with SMTP id jq3mr5561927wjc.114.1403656000012; Tue, 24 Jun 2014 17:26:40 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Tue, 24 Jun 2014 17:26:39 -0700 (PDT)
In-Reply-To: <CAKy9zTDkWgDDA_Meks4qFjfKBZijvWk7zm-LTbEu2QycUkE7eQ@mail.gmail.com>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <5B067502-29BD-4330-B627-A09898BAEB1D@tzi.org> <CAKy9zTDkWgDDA_Meks4qFjfKBZijvWk7zm-LTbEu2QycUkE7eQ@mail.gmail.com>
Date: Tue, 24 Jun 2014 20:26:39 -0400
X-Google-Sender-Auth: 8Jf-bv5AnElh8qyScuVnQMUJMBw
Message-ID: <CAMm+LwiDkFFk-d5hvAff+KwNWM3=bWVeQqav0ntx=q0fCgb5og@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Gary Mulder <flyingkiwiguy@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b8737ca4486de04fc9e2166
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/A1ukoiZX5-bN6qFJ5Q8fp997St8
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 00:26:43 -0000

--047d7b8737ca4486de04fc9e2166
Content-Type: text/plain; charset=UTF-8

On Tue, Jun 24, 2014 at 5:20 PM, Gary Mulder <flyingkiwiguy@gmail.com>
wrote:

> People, ISPs, etc. will move to the 128-bit Internet when they're forced
> to and no sooner. The fact that there is a workable solution to a known
> problem both proposed and implemented means that the transition will be
> less painful that it would be if there was no alternative and people are
> forced to "go digital or else".
>
>
Actually IPv6 is a 64 bit Internet, not 128 bits.

Only 64 bits of an IPv6 address are routable. It is the Inter-network after
all. Another 64 bits are reserved for the local network. One of the biggest
changes since the ARPANET days is that sites typically have local networks
with tens of machines. This house has 64 IPv4 addresses with static DHCP
allocations and I expect that to grow by at least an order of magnitude.

So we are really going from a 32 bit Internetwork+Network routing space to
64 bits of Internet and 64 bits of Network.

--047d7b8737ca4486de04fc9e2166
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Jun 24, 2014 at 5:20 PM, Gary Mulder <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:flyingkiwiguy@gmail.com" target=3D"_blank">flyingkiwiguy@gmail.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">People, ISPs, etc. will mov=
e to the 128-bit Internet when they&#39;re forced to and no sooner. The fac=
t that there is a workable solution to a known problem both proposed and im=
plemented means that the transition will be less painful that it would be i=
f there was no alternative and people are forced to &quot;go digital or els=
e&quot;.<div>
<br></div></div></blockquote><div><br></div><div>Actually IPv6 is a 64 bit =
Internet, not 128 bits.</div><div><br></div><div>Only 64 bits of an IPv6 ad=
dress are routable. It is the Inter-network after all. Another 64 bits are =
reserved for the local network. One of the biggest changes since the ARPANE=
T days is that sites typically have local networks with tens of machines. T=
his house has 64 IPv4 addresses with static DHCP allocations and I expect t=
hat to grow by at least an order of magnitude.=C2=A0</div>
<div><br></div><div>So we are really going from a 32 bit Internetwork+Netwo=
rk routing space to 64 bits of Internet and 64 bits of Network.</div></div>=
</div></div>

--047d7b8737ca4486de04fc9e2166--


From nobody Tue Jun 24 17:57:08 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C353B1B291A for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 yKUfq49uYWLJ for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 17:57:01 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2017C1B2A01 for <ietf@ietf.org>; Tue, 24 Jun 2014 17:57:01 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 41EC134944A; Wed, 25 Jun 2014 00:57:00 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 76B4216005B; Wed, 25 Jun 2014 01:03:41 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 0DFBB160059; Wed, 25 Jun 2014 01:03:41 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2DCAC19400A7; Wed, 25 Jun 2014 10:56:27 +1000 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
Subject: Re: Time to move beyond the 32 bit Internet.
In-reply-to: Your message of "Wed, 25 Jun 2014 01:55:43 +0200." <20140624235543.332511AD64@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 10:56:27 +1000
Message-Id: <20140625005627.2DCAC19400A7@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/677T33j8jbVKdsVipRjzQYLTsn4
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 00:57:07 -0000

In message <20140624235543.332511AD64@ld9781.wdf.sap.corp>, Martin Rex writes:
> Mark Andrews wrote:
> > 
> > Martin Rex writes:
> > >
> > > Phillip Hallam-Baker wrote:
> > > > 
> > > > While going through the Windows API calls and thinking how old fashione
> d
> > > > and lame all those 'Win32' classes look now, a sudden thought:
> > > > 
> > > > Ordinary users don't understand the importance of going from IPv4 to IP
> v6.
> > > > 
> > > > But Ordinary users do understand that 32 bits is bad and old and obsole
> te
> > > > and rubbish and 64 bits is better.
> > > 
> > > Experienced users know painfully well just how smooth and painless
> > > 32-bit (windows) and 32-bit IPv4 is, whereas newer 64-bit (windows)
> > > and newer 128-bit IPv6 is just many painful problems and ZERO benefit.
> > > 
> > > A lot of the equipment that me and my family is using is not IPv6 capable
> ,
> > > and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
> > > ***MUCH*** better when configured with IPv4-only anyway, so why bother.
> > > 
> > > If someone needs to be pushed, then it is *VENDORS*, not users,
> > > that they ship their equipment in a fashion that it will work with IPv6,
> > > should this ever become available.  Then maybe in 10 years from now,
> > > this might become interesting to end users.
> > 
> > Given there are ISP delivering IPv6 + DS-Lite today over fibre
> > because they have run out of addresses it is time that *everybody*
> > starts complaining to every supplier that doesn't ship equipement
> > / services with IPv6 enabled by default.
> 
> 
> Why would any private individual want to get an IPv6 address?
> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
> you may have at least a vague chance that your ID doesn't stick out
> of every IP datagram like a sore thumb.  With IPv6, you're stripped
> naked for traffic analysis by every governmental agency worldwide, no matter
> how strong you encrypt your traffic.

Because with CGN, DS-Lite and NAT64 you have a third class IPv4
internet.  You can't run any services what so ever.  You cannot do
anything that requires anything other than UDP or TCP over IPv4.
Try running IPv4 in IPv4 or IPv6 in IPv4 tunnels over CGN, DS-Lite
and NAT64.  They do not work due to the addresses sharing.  Try
running a NAS from behind them, it does not work.

With one level of NAT that you control (second class internet) you
can kludge around some of the issues cause by not having global
addresses ability of every machine.  UPNP helps here.

As for you ID sticking out, IPv6 is no worse that IPv4 is for all
practical purposes with currently shipping IPv6 stacks.  They have
privacy addresses and they are turned on by default.

Now with IPv6 you have a choice of whether to offer a service or
not and you don't have configure port forwarding etc.  You can have
both stable and temporary addresses at the same time for the same
box.  You can choose which to use on a service and/or role basis.

But hey a third class internet is "good enough" for the plebes at
home.  They don't deserve to be able to run servers from home.  They
don't deserve to have a first class internet.

Mark

> The end-2-end principle is equivalent to a fairly complete loss of privacy.
> Really, I'm glad that I can use IPv4 and get a new IPv4 address assigned
> several times a day.
> 
> -Martin
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Jun 24 18:08:08 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8491B2A0C for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 18:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 DHvABVTgg8rt for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 18:08:03 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FB721B2A04 for <ietf@ietf.org>; Tue, 24 Jun 2014 18:08:03 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id w10so932956pde.3 for <ietf@ietf.org>; Tue, 24 Jun 2014 18:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XEKYsRIp5lhF4CUJBlBSC+0ehN4EnNpN8E+TXbWfa7c=; b=ONZixeoGVK9YFBOLnGNWHuKOCC8wpuImGk2s425rP4T4JeH7fAYd6ijF0+fqM+1uZs 1tQuhLvKxRSAEWEtKTdArUeR7URTFFi5oi2AwqmWii/IFI+w4Iu1b7Y6n//erESxSHuE ixkWYbbVDVTy9Id5qUjpvyoj08fpinqR/W6IYw6rW+smyYNpLYvQOxHRuZDdY6WOUA6+ iacKT5jRrGjz8ROUMiMAnezk6eeHA4+v5EGI/Ll2Z8MDCLGg6Y4nzdRU9JDkKzce2a7T /yIVOXWDMmdI2/5kSOum0OHz2fikfmjW5VPMoJF6EEmlliQinkucBPnyqL1IG1qfI9DO Bhjg==
X-Received: by 10.67.22.33 with SMTP id hp1mr6473127pad.134.1403658483013; Tue, 24 Jun 2014 18:08:03 -0700 (PDT)
Received: from [172.24.60.8] (wireless-nat-21.auckland.ac.nz. [130.216.30.132]) by mx.google.com with ESMTPSA id gw8sm2352490pbc.28.2014.06.24.18.08.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Jun 2014 18:08:02 -0700 (PDT)
Message-ID: <53AA20F7.4070808@gmail.com>
Date: Wed, 25 Jun 2014 13:08:07 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
In-Reply-To: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lqTzCxrTTe58O02ubdUlO-PYkPI
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 01:08:06 -0000

> Why would any private individual want to get an IPv6 address?
> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
> you may have at least a vague chance that your ID doesn't stick out
> of every IP datagram like a sore thumb.  With IPv6, you're stripped
> naked for traffic analysis by every governmental agency worldwide, no matter
> how strong you encrypt your traffic.

Er, your ISP-based IPv4 address often sticks out plenty even if your
host is behind a NAT. Just look at the headers for gmail SMTP users,
for example. As far as having the Bundespolizei at your door
goes, that is sufficient.

Most private individuals simply don't care, anyway. They do care
if they can't get connected at all, which is why we need to move
beyond 32 bits in the first place.

   Brian


From nobody Tue Jun 24 20:02:57 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E20921B2A5E for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 3ZnmgU2yPXgm for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:02:53 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 400151B2A45 for <ietf@ietf.org>; Tue, 24 Jun 2014 20:02:53 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C9B021B81C7 for <ietf@ietf.org>; Tue, 24 Jun 2014 20:02:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 83462190071; Tue, 24 Jun 2014 20:02:52 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 20:02:52 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <53AA20F7.4070808@gmail.com>
Date: Tue, 24 Jun 2014 23:02:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <53AA20F7.4070808@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q7u_V3xvqKHyFjMIJGVUr0gVNKQ
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 03:02:55 -0000

I wonder if this will be the big debate about whether or not IPv6 will =
get deployed that actually comes to a conclusion everybody can accept.   =
It's got to happen one of these days...

;)


From nobody Tue Jun 24 20:20:23 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6F21B2A80 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Jhl3q9GJzdfH for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:20:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391B91B2A7A for <ietf@ietf.org>; Tue, 24 Jun 2014 20:20:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1Wzdks-0002lb-OB; Wed, 25 Jun 2014 03:20:15 +0000
Date: Wed, 25 Jun 2014 12:20:13 +0900
Message-ID: <m2tx79hdzm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <53AA20F7.4070808@gmail.com> <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YqClWkvO8rZd7NJ1gY9-wkhKWic
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 03:20:21 -0000

> I wonder if this will be the big debate about whether or not IPv6 will
> get deployed that actually comes to a conclusion everybody can accept.
> It's got to happen one of these days...

i am always impressed by optimism in the face of reality

maybe if we scream at the evil {vendors,backbones,content,lastmile,.*}
some more and tell them that the sky will fall on them and that they
will be struck by falling frogs ...

or maybe if we put more cologne on the mis-designed incompatible botch?

randy


From nobody Tue Jun 24 20:26:19 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653331B2A80 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 viv2c_eL5yCu for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:26:13 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 104161B2A82 for <ietf@ietf.org>; Tue, 24 Jun 2014 20:26:13 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E34AD1B81C7 for <ietf@ietf.org>; Tue, 24 Jun 2014 20:26:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D1768190071; Tue, 24 Jun 2014 20:26:12 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 20:26:12 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <m2tx79hdzm.wl%randy@psg.com>
Date: Tue, 24 Jun 2014 23:26:09 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <78656965-FE53-4307-ABF4-4ED6386EC518@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <53AA20F7.4070808@gmail.com> <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com> <m2tx79hdzm.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8xrKwYytrnCa0VruViGEx-Gcu9g
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 03:26:15 -0000

On Jun 24, 2014, at 11:20 PM, Randy Bush <randy@psg.com> wrote:
> or maybe if we put more cologne on the mis-designed incompatible botch?

Or maybe we should stop arguing about it, since it's not in our hands anyway.


From nobody Tue Jun 24 20:36:08 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA691B2A8F for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 G9PHkD6sf5Nf for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:36:05 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A9D1B2A8E for <ietf@ietf.org>; Tue, 24 Jun 2014 20:36:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1Wze0A-0002oo-9X; Wed, 25 Jun 2014 03:36:02 +0000
Date: Wed, 25 Jun 2014 12:36:01 +0900
Message-ID: <m2simthd9a.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <78656965-FE53-4307-ABF4-4ED6386EC518@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <53AA20F7.4070808@gmail.com> <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com> <m2tx79hdzm.wl%randy@psg.com> <78656965-FE53-4307-ABF4-4ED6386EC518@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nyp_OEcxyhYajD0ioly_Ah1S75Y
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 03:36:06 -0000

>> or maybe if we put more cologne on the mis-designed incompatible
>> botch?
> Or maybe we should stop arguing about it, since it's not in our hands
> anyway.

depends.  some of us here actually operate networks, make cpe, ...  iij
deployed v6 pretty early, like the last century.  and we make the cpe.
so our money is where our mouth is.  but it was religion, not profit
driven.  i fear that ipv6 makes no money for anybody except the rirs.

randy


From nobody Tue Jun 24 20:43:54 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 835FA1B2A97 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 smmVQLMIo48I for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 20:43:52 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 952D41B2A9D for <ietf@ietf.org>; Tue, 24 Jun 2014 20:43:52 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5CBD61B81D5 for <ietf@ietf.org>; Tue, 24 Jun 2014 20:43:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 11E89190071; Tue, 24 Jun 2014 20:43:52 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 20:43:51 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <m2simthd9a.wl%randy@psg.com>
Date: Tue, 24 Jun 2014 23:43:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <72B92470-404A-4855-8263-F41C91949576@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <53AA20F7.4070808@gmail.com> <13032996-55D3-46E0-96A0-90DFCC5BD976@nominum.com> <m2tx79hdzm.wl%randy@psg.com> <78656965-FE53-4307-ABF4-4ED6386EC518@nominum.com> <m2simthd9a.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EnNvnVfOt3GBlfD1RIzzkxFctHo
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 03:43:53 -0000

On Jun 24, 2014, at 11:36 PM, Randy Bush <randy@psg.com> wrote:
> some of us here actually operate networks, make cpe

Sigh, and now I am prolonging the conversation.   Sorry.   But my point =
was not that we have nothing to do about it.   Just that we aren't going =
to have a discussion where we all agree about what the outcome will be, =
because no matter what we do or try to do, it's not really in our hands. =
  Doesn't mean we can't (or shouldn't) try!


From nobody Tue Jun 24 21:28:32 2014
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB671B2AAD for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 21:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.147
X-Spam-Level: 
X-Spam-Status: No, score=0.147 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 9PuBOAkmiFfm for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 21:28:26 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9171B2AAE for <ietf@ietf.org>; Tue, 24 Jun 2014 21:28:26 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Time to move beyond the 32 bit Internet.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Tue, 24 Jun 2014 21:28:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <69B9BA3779753A49865BB9010D560EBB7020@newserver.arneill-py.local>
In-Reply-To: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Time to move beyond the 32 bit Internet.
Thread-Index: Ac+PwrRXB7Bf8kWLQ0yV88/NS9WNhwAZgAPA
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>, "Ted Lemon" <ted.lemon@nominum.com>, "IETF Discussion Mailing List" <ietf@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XHM4uxgbQsoCpNhpcZmF53T99ws
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 04:28:28 -0000

PiBQaGlsbGlwIEhhbGxhbS1CYWtlciB3cm90ZSA6DQo+IFNvIGxldHMgc3RvcCBhc2tpbmcgSVNQ
cyAnZG8geW91IHN1cHBvcnQgSVB2NicgYW5kIGluc3RlYWQgYXNrICdJcyB5b3VyIEludGVybmV0
IHNlcnZpY2UgMzIgYml0IG9yIDEyOCc/DQoNCkNyZWF0aXZlLiBTaW5jZSBmcmVlSVB2NnBvcm4u
Y29tIHRoaXMgaXMgdGhlIGRlZmluaXRlbHkgb25lIG9mIHRoZSBiZXN0IG1hcmtldGluZyBhdHRl
bXB0cyB0aGF0IEkgY2FuIHJlbWVtYmVyLg0KDQpIb3dldmVyLCBJIHdvdWxkIGJlIGNvbmNlcm5l
ZCB0aGF0IGRlY2lkZXJzIHdobyB3b3VsZCBiZSB0ZW1wdGVkIGJ5IHRoYXQgcGljay11cCBsaW5l
IGhhZCBiZWVuIGVhcmxpZXIgYWRvcHRlcnMgb2YgNjQtYml0IE9TIGFuZCBmb3VuZCA2NC1iaXQg
ZHJpdmVycyBmb3IgdGhlaXIgZXhpc3RpbmcgcGVyaXBoZXJhbHMgKG9yIHRoZSBsYWNrLCB0aGVy
ZW9mKSBkaXN0dXJiaW5nLg0KDQpPUyB1cGdyYWRlcyBmcm9tIDggdG8gMTYgYml0LCAxNiB0byAz
MiBhbmQgMzIgdG8gNjQgdmVyc2lvbnMgaGF2ZSBhbGwgYmVlbiBwYWluZnVsOyBhbGwgb2YgdGhl
bSBsZWZ0IHNvbWUgc2NhcnMuIEknbSBhZnJhaWQgdGhhdCB0aGUgY3VycmVudCBtaW5kc2V0IGlz
IHRoYXQgaXQgaXMgdXJnZW50IHRvIHdhaXQsIGJvdGggdG8gbGV0IHRoZSBvdGhlciBndXkgc3dl
YXQgdGhlIHVuYXZvaWRhYmxlIGJ1Z3Mgb3V0LCBhbmQgdG8gc2VlIGlmIHRoZSB1cGdyYWRlIGlz
IHdvcnRoIHRoZSBtb25leS4NCg0KRGFuZ2Vyb3VzIG1vdmUsIGJ1dCB3b3J0aCBhIHNob3QgYXQg
aXQuIElQdjYgZG9lcyBub3QgaGF2ZSBtYW55IHNob3RzIGxlZnQuDQoNCg0KPiBBY3R1YWxseSBJ
UHY2IGlzIGEgNjQgYml0IEludGVybmV0LCBub3QgMTI4IGJpdHMuDQoNCkJldHRlciB0byBmb3Jn
ZXQgdGhhdCBhbmQgdHJ5IHRvIHNlbGwgaXQgYXMgMTI4IGJpdHMsIGFzIG5vYm9keSBlbHNlIGhh
cyBiZWVuIGJ1cm5lZCBidXQgdGhhdCBudW1iZXIgeWV0Lg0KDQoNCj4gVGVkIExlbW9uIHdyb3Rl
IDoNCj4gSSB3b25kZXIgaWYgdGhpcyB3aWxsIGJlIHRoZSBiaWcgZGViYXRlIGFib3V0IHdoZXRo
ZXIgb3Igbm90IElQdjYNCj4gd2lsbCBnZXQgZGVwbG95ZWQgdGhhdCBhY3R1YWxseSBjb21lcyB0
byBhIGNvbmNsdXNpb24gZXZlcnlib2R5IGNhbiBhY2NlcHQuDQo+IEl0J3MgZ290IHRvIGhhcHBl
biBvbmUgb2YgdGhlc2UgZGF5cy4uLiA7KQ0KDQpJIGhhdmUgYmVlbiB3YWl0aW5nIG9uIHRoZSBz
aWRlbGluZXMgZm9yIHRoYXQgZGF5IGZvciBhIGxvbmcgdGltZS4gSG93ZXZlciwgb25lIHR3byBv
ciB0aHJlZSBtb3JlIHllYXJzIG1vcmUgd29uJ3QgbWFrZSBhIGRpZmZlcmVuY2U7IHBsZWFzZSBj
b25zaWRlciBoYXZpbmcgYSBuaWNlICJQbGFuIEIiIHJlYWR5IHdoZW4gdGhhdCBkYXkgZG9lcyBj
b21lOyBtYWtpbmcgaXQgY29tZSBlYXJsaWVyIHRoYW4gdGhlIG1hcmtldCBpcyByaXBlIGZvciBp
cyBhIHdhc3RlIG9mIGVuZXJneS4NCg0KTWljaGVsLg0KDQo=


From nobody Tue Jun 24 22:55:28 2014
Return-Path: <ietf@trammell.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14DF51B2AD5 for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 22:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 u8VNxYcKZfDl for <ietf@ietfa.amsl.com>; Tue, 24 Jun 2014 22:55:25 -0700 (PDT)
Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id A90211B2AD0 for <ietf@ietf.org>; Tue, 24 Jun 2014 22:55:24 -0700 (PDT)
Received: from [IPv6:2001:470:26:9c2::2] (unknown [IPv6:2001:470:26:9c2::2]) by trammell.ch (Postfix) with ESMTPSA id 292B31A0036; Wed, 25 Jun 2014 07:55:22 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_53BA7524-DE9B-4756-B14F-70DCB5085FC5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 07:55:22 +0200
Message-Id: <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LFGXefatE-8T_RQYfbu1QDalQVI
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 05:55:27 -0000

--Apple-Mail=_53BA7524-DE9B-4756-B14F-70DCB5085FC5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Martin, all,

On 25 Jun 2014, at 01:55, Martin Rex <mrex@sap.com> wrote:

> Why would any private individual want to get an IPv6 address?
> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
> you may have at least a vague chance that your ID doesn't stick out
> of every IP datagram like a sore thumb.  With IPv6, you're stripped
> naked for traffic analysis by every governmental agency worldwide, no =
matter
> how strong you encrypt your traffic.

There is an incredibly dubious assumption hidden in this statement that =
it's hard to map NATted addresses to user and session identifiers. Not =
only is it not particularly hard, it's actually _required_ in certain =
jurisdictions for ISPs to keep this mapping information to respond to LE =
requests.=20

Even if you're _not_ the ISP or (quasi-)legally empowered to compel it =
to give you this information, there's enough information radiated by =
application layer protocols that you can tease session identifiers back =
out of traces even without payload and with addressing information =
*purposefully* destroyed, as opposed to merely tweaked for operational =
expediency. See e.g. Coull et al "Playing Devil's Advocate: Inferring =
Sensitive Information from Anonymized Network Traces" NDSS 2007; Wright =
et al "On Inferring Application Protocol Behaviors in Encrypted Network =
Traffic" Journal of Machine Learning Research 2006; and the citation =
trees rooted at those two papers.

Network address translation is simply an expedient technique to tease a =
few more bits out of the address space by hiding those bits in transient =
state kept along the path. The assumption that it is somehow hard to =
store or reconstruct that transient state is simply incorrect.=20

As a method for protecting privacy, NAT is privacy theater, full stop.

> The end-2-end principle is equivalent to a fairly complete loss of =
privacy.
> Really, I'm glad that I can use IPv4 and get a new IPv4 address =
assigned
> several times a day.

I'm pretty sure I read somewhere that we're out of "new" IPv4 addresses. =
:) So those addresses aren't new, they're reused. So the important =
metric here isn't the frequency of change, but (1) the size of the set =
of addresses and (2) the predictability of that set. Unless you're =
changing your ISP several times a day, NAT serves only to "hide" you in =
a pool of a very small number of bits of address entropy.

Regards,

Brian

--Apple-Mail=_53BA7524-DE9B-4756-B14F-70DCB5085FC5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJTqmRKAAoJENt3nsOmbNJcNk0IAMhmOyASUEgC6tJmCsNKPtpa
HBSs8qcI0WdzFQEhzTadKiad6sIyTa7/pbKyM0uIuG+rOQEcTWf99dtXoFgIzaks
4jAhQX7zIZ77fyapFLSGEsXDowmNOovhLKf03MjUSjyGn1AQsBW4ZfrdKbLXGIPq
jI8TdZofcqL0DiYEdsE8toSduNHXedoizyFQnSr2rrUBVYSrSZtB2mBWf0oZk9oL
Nd1E87ZrW0zduW8Z8p77zbgQhFpC3+6iQMQavnKt91M4Ht8+Xa94MyLwxwljn3Mo
wd19f+rtvvx3GGf1d9awshDuePjfHr3UZjPLOKW/JBWpppr7yYhRFY0f7NLjBJc=
=0Jab
-----END PGP SIGNATURE-----

--Apple-Mail=_53BA7524-DE9B-4756-B14F-70DCB5085FC5--


From nobody Tue Jun 24 23:16:20 2014
Return-Path: <ietf@trammell.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B463F1B2AE0; Tue, 24 Jun 2014 23:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 B6zd8du6snQV; Tue, 24 Jun 2014 23:16:12 -0700 (PDT)
Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id F18BB1B2ADB; Tue, 24 Jun 2014 23:16:11 -0700 (PDT)
Received: from [IPv6:2001:470:26:9c2::2] (unknown [IPv6:2001:470:26:9c2::2]) by trammell.ch (Postfix) with ESMTPSA id E81451A0158; Wed, 25 Jun 2014 08:16:09 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_6838806A-2549-465C-93C7-F7B14A15758C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Gen-ART review of draft-ietf-ipfix-text-adt-06
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120770050255@MX15A.corp.emc.com>
Date: Wed, 25 Jun 2014 08:16:09 +0200
Message-Id: <5D72BEB3-1038-48EE-AD8C-2BABD53B85B9@trammell.ch>
References: <8D3D17ACE214DC429325B2B98F3AE7120770050255@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/z44pT1sd4ahNSfMeumj-fDabq7s
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 06:16:14 -0000

--Apple-Mail=_6838806A-2549-465C-93C7-F7B14A15758C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

hi David,

On 24 Jun 2014, at 23:41, Black, David <david.black@emc.com> wrote:

> With correct subject line this time ...
>=20
>> -----Original Message-----
>> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Black, =
David
>> Sent: Tuesday, June 24, 2014 5:14 PM
>> To: ietf@trammell.ch; General Area Review Team (gen-art@ietf.org)
>> Cc: ietf@ietf.org; ipfix@ietf.org
>> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ipfix-text-adt-05
>>=20
>> The -06 version of this draft addresses all of the comments in the
>> Gen-ART review of the -05 version.
>>=20
>> Nit: I suggest one minor clarification in the added text (insertion
>> of the word "comparing" is the primary purpose of this change, feel
>> free to edit to taste):
>>=20
>> OLD
>>   See
>>   [RFC6885] and [I-D.ietf-precis-framework] for more on the dangers =
of
>>   Unicode strings..
>> NEW
>>   See
>>   [RFC6885] and [I-D.ietf-precis-framework] for more on possible
>>   unexpected results and related risks in comparing Unicode strings.

Yep, that's better. I'll hold this for a -07 post-next-review-round.

Many thanks, best regards,

Brian

>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: Black, David
>>> Sent: Friday, May 23, 2014 10:11 PM
>>> To: ietf@trammell.ch; General Area Review Team (gen-art@ietf.org)
>>> Cc: ipfix@ietf.org; ietf@ietf.org; Black, David
>>> Subject: Gen-ART review of draft-ietf-ipfix-text-adt-05
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>>=20
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-ietf-ipfix-text-adt-05
>>> Reviewer: David L. Black
>>> Review Date: May 23, 2014
>>> IETF LC End Date: May 28, 2014
>>>=20
>>> Summary:  This draft is on the right track, but has open issues
>>> 		described in the review.
>>>=20
>>> This is a relatively short draft defining textual representations of
>>> IPFIX data elements.  It's clear and easy to read.
>>>=20
>>> I assume that all the ABNF has been checked.  The open issues =
involve
>>> use of Unicode.
>>>=20
>>> Minor issues:
>>>=20
>>> Section 4.7 string
>>>=20
>>>   As Information Elements of the string type are simply UTF-8 =
encoded
>>>   strings, they are represented directly, subject to the escaping =
and
>>>   encoding rules of the Enclosing Context.
>>>=20
>>> There's nothing "simply" about use of UTF-8 encoded strings :-).
>>>=20
>>> There appear to be no restrictions on Unicode codepoint usage and no
>>> requirements for string normalization or other preparation either in =
this
>>> draft or RFC 7011.  This can be a formula for all sorts of mischief, =
so
>>> some warnings about what's possible should be added somewhere - some =
of
>>> these comments may be raising Unicode concerns in RFC 7011 that =
would
>>> be better addressed there.
>>>=20
>>> A general warning about unreliability of Unicode string comparison
>>> is in order.  This also applies if an identifier that is not limited
>>> to ASCII characters is substituted for an integer as described in
>>> Section 4.2.  In addition, the concerns around visually similar
>>> characters discussed in section 10.5 of the pr=E9cis framework draft
>>> (draft-ietf-pr=E9cis-framework) apply; a short summary and pointer
>>> to that section of that draft should suffice.
>>>=20
>>> Section 4.1.5 of the pr=E9cis framework draft warns against use of =
mixed-
>>> direction Unicode strings, as "there is currently no widely accepted =
and
>>> implemented solution for the processing and safe display of mixed-
>>> direction strings."  That warning deserves repetition here.
>>>=20
>>> Lots of mischief is possible with non-printing and control =
characters -
>>> I would expect that the Enclosing Context contains sufficient =
restrictions
>>> on use of Unicode to deal with most of this concern, and would state =
that
>>> expectation.  This comment is definitely specific to this draft.
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> Section 4.4 float32 and float64
>>>=20
>>>   exponent =3D ( "e" / "E" ) [sign] 1*3DIGIT
>>>=20
>>> Please explain why no more than 3 digits are ever required.
>>>=20
>>> Section 4.8 dateTime*
>>>=20
>>> The '*' in the section title, dateTime* is clever, but it's meaning =
is not
>>> obvious.  I suggest "The dateTime Data Types" as a better section =
title.
>>>=20
>>> Section 5 Security Considerations
>>>=20
>>>   The security considerations for the IPFIX Protocol [RFC7011] =
apply;
>>>   this document presents no additional security considerations.
>>>=20
>>> That's ok, although adding a direct mention of the [UTF8-EXPLOIT] TR
>>> cited in RFC 7011 would be helpful.
>>>=20
>>> idnits 2.13.01 warns that the JSON reference (RFC 4627) is obsolete, =
and
>>> needs to be replaced with one or two current RFC references.
>>>=20
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_6838806A-2549-465C-93C7-F7B14A15758C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJTqmkpAAoJENt3nsOmbNJc4ccH/j/NSZnKacb3CnA+KmcWyvJr
cU1WQz0PCHMPY5vl8RRhMxrSVgyHK90f79+WkrdPxkEq+FVwWdPe3F2oS5J/iBGb
sIC6EGdy/2sOMhcxC/E3Oz38u4YewPsySUwBM6XQcsFs7KK8OAXTn1hM+gWlPM6H
ibtyIOV3aW/bF/Ww9PoqrzSJMjFh9FETYThdH8KYV9dKfGNisBz551xOiTCB17uX
9Ytz6NDqlz/OOEY+bKfEAYUhesb2D3xnwPVcNTnuoeeYJfbrFHPIfa9k5Wg0S0So
LVK/RGlRJ4/fotpZ8t7d6cuEDBaRrcog/e0T4xgr2JYK4jSY5Kg4ws1WxA+1avQ=
=DOM9
-----END PGP SIGNATURE-----

--Apple-Mail=_6838806A-2549-465C-93C7-F7B14A15758C--


From nobody Wed Jun 25 00:10:26 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A58571B2AEF; Wed, 25 Jun 2014 00:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.1
X-Spam-Level: ***
X-Spam-Status: No, score=3.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  MANGLED_LIST=2.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 2vlzzzPuNd0s; Wed, 25 Jun 2014 00:10:21 -0700 (PDT)
Received: from p3plsmtpa08-05.prod.phx3.secureserver.net (p3plsmtpa08-05.prod.phx3.secureserver.net [173.201.193.106]) by ietfa.amsl.com (Postfix) with ESMTP id CD48E1B2AE9; Wed, 25 Jun 2014 00:10:20 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-05.prod.phx3.secureserver.net with  id JXAC1o0051huGat01XACp1; Wed, 25 Jun 2014 00:10:20 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-netext-wifi-epc-eap-attributes.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-netext-wifi-epc-eap-attributes-08
Date: Wed, 25 Jun 2014 00:10:16 -0700
Message-ID: <08eb01cf9044$893c73d0$9bb55b70$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+QO5sTsbQV2OmnSEa9W+i3m4dC9Q==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5GA9dGDLCn43MUw3oiok3sYuZyQ
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 07:10:22 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-netext-wifi-epc-eap-attributes-08
Reviewer: Peter Yee
Review Date: June-24-2014
IETF LC End Date: June-24-2014
IESG Telechat date: TBD

Summary: This draft is basically ready for publication as an Informational
RFC, but has some nits that should be fixed before publication. [Ready with
nits.]

The draft could do with some language cleanup, but otherwise appears fine
for publication.

Questions:

Page 8, Section 5.2, 2nd paragraph, last sentence: by "present" do you mean
the presence of the Type field itself or the presence of a Type field value?
I believe you mean the latter, in which case you may wish to add "value"
after "Type field".

Page 11, Section 5.5, diagram: the session ID would seem to run longer than
32 bits in some cases.  For example, I understand a GUTI to be 62 bits (30
bits of GUMMEI plus 32 bits of M-TMSI).  Should the diagram be modified to
reflect the variable length?

General:

Replace "WiFi" with "Wi-Fi" throughout the document to align with the
preferred usage of the name as given by the Wi-Fi Alliance.

Expand acronyms on first use unless they are blazingly obvious in this
context.  Consider citing their references for clarity.

Replace "a MN" with "an MN" throughout the document.

Determine if RFC 2119 language is really necessary in this document and then
use it (or not) consistently.  There are SHOULDs and shalls (lower case).

Leave URLs out of RFC references; they aren't included in the current
reference format.

Not all the attributes defined in Section 5 are discussed in Section 4.  Is
this expected or desirable?

Nits:

Page 1, Abstract, 1st paragraph, 2nd sentence: append a comma after
"connections".

Page 2, Introduction, 1st paragraph, 3rd sentence: change "the functions" to
"these functions".

Page 2, Introduction, 1st paragraph, 5th sentence: change "indicates" to
"requests", unless this 3GPP's terminology for a requesting a new IP
session.

Page 3, paragraph after the bullet points, 1st sentence: replace "and"
before "EAP-SIM" with a comma.

Page 3, paragraph after the bullet points, last sentence: append a comma
after "4G".

Page 3, Section 1.1, 1st paragraph, 2nd sentence: change "it's" to "its".

Page 3, Section 1.1, 1st paragraph, 4th sentence: change "internet" to
"Internet" unless you really mean lower case "internet".

Page 3, Section 1.1., 1st paragraph, 4th sentence: insert "a" before "user".

Page 3, Section 1.1, 2nd paragraph, 2nd sentence: change "attributes" to
"attribute".

Page 3, Section 1.2, 2nd sentence: replace "Additional" with "additional" in
both places to match 3GPP usage. 

Page 4, Section 1.3, 1st sentence: replace "it's" with "its".

Page 4, Section 1.3, 1st sentence: insert "network" between "access" and
"to".

Page 4, Section 1.3, 2nd sentence: insert "a" before "3GPP".

Page 4, Section 1.3, 3rd sentence: change "from" to "using" and delete the
subsequent "the".

Page 4, Section 1.3, last sentence: expand the acronym "RAN".  Note that
3GPP and IEEE 802 usage of the acronym differs.

Page 5, Section 3.2, 2nd paragraph, 2nd sentence: change "it's" to "its".

Page 5, Section 3.2, 2nd paragraph, 2nd sentence: insert "an" before the
first occurrence of "MN".

Page 5, Section 3.2, 2nd paragraph, 2nd sentence: insert "the" before the
second occurrence of "MN" and replace the following "credentials" with
"identity".  The credentials are used to prove the identity that was
communicated.

Page 6, first bullet item, last sentence: insert "the" before "MAG".

Page 6, "Call Flow Description": a whole host of definite and indefinite
articles is missing.  They're simply too numerous for me to what to list
them individually.  Review the section and insert articles as appropriate to
aid readability.

Page 6, "Call Flow Description", item 1: end the sentence with a period.

Page 6, "Call Flow Description", item 2: append a period to the sentence.

Page 6, "Call Flow Description", item 6:  replace "it's" with "its".

Page 6, "Call Flow Description", item 7:  replace "it's" with "its".  Come
to think of it, just do a global search-and-replace for "it's".

Page 6, "Call Flow Description", item 10: move the comma after "etc." to
before it.

Page 7, Section 4.1, 1st paragraph: insert "the" before
"AT_VIRTUAL_NETWORK_ID"; insert "the" before "EAP-Response/AKA-Challenge".

Page 7, Section 4.1, 2nd paragraph, 1st sentence: insert "the" before
"AT_VIRTUAL_NETWORK_ID"; insert "the" before "EAP-Response/AKA-Challenge".

Page 7, Section 4.2, 1st paragraph: insert "the" before "MN".

Page 7, Section 4.2, 1st bullet item: eliminate the space before the colon.

Page 7, Section 4.2, 1st bullet item, 1st sentence: insert "the" before
"MN".

Page 7, Section 4.2, 1st bullet item, 2nd sentence: insert "the" before
"network".

Page 7, Section 4.2, 2nd bullet item, 1st sentence: insert "The" before
"MN".

Page 7, Section 4.3, 1st paragraph, 1st sentence: consider replacing "A
Mobile Node" with "An MN".

Page 7, Section 4.3, 1st paragraph, 2nd sentence: insert "the" before
"so-called".

Page 8, Section 5: insert "the" before "first".

Page 8, Section 5.1, Virtual Network Id definition, 1st sentence: insert
"the" before "MN".

Page 8, Section 5.2, 1st paragraph, 1st sentence: insert "an" before the
first occurrent of "MN"; insert "the" before the second.

Page 8, Section 5.2, 2nd paragraph, 3rd sentence: insert "the" before
"MN's".

Page 9, Virt-Net-Req Type, 3rd bullet item: insert "the" before
"Connectivity".

Page 9, Section 5.3: consider moving this section to after Section 5.5 to
mirror the order found in Section 4.

Page 9, Section 5.3, 1st paragraph: consider changing "A Mobile Node" to "An
MN".

Page 10, Section 5.4, diagram: it's not apparent to me why the attribute
length value is equal to 1 plus the session ID length.

Page 10, Section 5.4, both bullet items: insert "The" or "the" before "MN"
in all cases, as appropriate.

Page 11, Section 5.5, 1st paragraph, 1st sentence: insert "an" before the
first occurrence of "MN"; insert "a session" before "identity"; insert "the"
before the second occurrence of "MN".

Page 11, Section 5.5, 1st paragraph, 2nd sentence: insert "The" before "MN";
replace "a" with "an" before "E-UTRAN".

Page 11, Section 5.5, 1st paragraph, 3rd sentence: insert "the" before "MN".

Page 11, last paragraph, 2nd sentence: replace "begining" with "beginning".

Page 11, last paragraph, last sentence: insert spaces before this sentence
to separate it from the previous one.

Page 12, Section 6, 1st sentence: insert "the" before "EAP-AKA".  Delete
"RFC 4187".  The reference should suffice.

Page 12, Section 6,  2nd sentence: consider noting that some attributes are
passed from the network to the MN.

Page 14, EPC reference: delete the semicolon. Delete the superfluous quote
and comma following the date.

Page 14, GPRS reference: insert a closing quote after "Stage 2". Delete the
superfluous quote and comma following the date.


From nobody Wed Jun 25 01:45:24 2014
Return-Path: <floris.vandenabeele@intec.ugent.be>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4D681B2B0F for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 01:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 36Kw818kjsPe for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 01:45:19 -0700 (PDT)
Received: from smtp1.ugent.be (smtp1.ugent.be [157.193.71.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8547F1B2AF6 for <ietf@ietf.org>; Wed, 25 Jun 2014 01:45:18 -0700 (PDT)
Received: from localhost (mcheck3.ugent.be [157.193.71.89]) by smtp1.ugent.be (Postfix) with ESMTP id 461DF884E; Wed, 25 Jun 2014 10:45:17 +0200 (CEST)
X-Virus-Scanned: by UGent DICT
Received: from smtp1.ugent.be ([IPv6:::ffff:157.193.71.182]) by localhost (mcheck3.UGent.be [::ffff:157.193.43.11]) (amavisd-new, port 10024) with ESMTP id V5XuQU_dCozJ; Wed, 25 Jun 2014 10:45:11 +0200 (CEST)
Received: from mail2.intec.ugent.be (mail2.intec.ugent.be [157.193.214.245]) by smtp1.ugent.be (Postfix) with ESMTP id 843BB883C; Wed, 25 Jun 2014 10:45:12 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.intec.ugent.be (Postfix) with ESMTP id 9DB0224; Wed, 25 Jun 2014 10:45:12 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at intec.ugent.be
Received: from mail2.intec.ugent.be ([127.0.0.1]) by localhost (mail2.intec.ugent.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWnKROAbVsVJ; Wed, 25 Jun 2014 10:45:12 +0200 (CEST)
Received: from [157.193.135.213] (dhcp-zdpt-213.intec.ugent.be [157.193.135.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fvdabeele) by mail2.intec.ugent.be (Postfix) with ESMTPSA id F201221; Wed, 25 Jun 2014 10:45:11 +0200 (CEST)
Message-ID: <53AA8C0E.3020708@intec.ugent.be>
Date: Wed, 25 Jun 2014 10:45:02 +0200
From: Floris Van den Abeele <floris.vandenabeele@intec.ugent.be>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brian Trammell <ietf@trammell.ch>
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch>
In-Reply-To: <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LDti8HsKhrsNLqRLNTXei76agPInV6Oel"
X-Miltered: at jchkm3 with ID 53AA8C18.001 by Joe's j-chkmail (http://helpdesk.ugent.be/email/)!
X-j-chkmail-Enveloppe: 53AA8C18.001 from mail2.intec.ugent.be/mail2.intec.ugent.be/157.193.214.245/mail2.intec.ugent.be/<floris.vandenabeele@intec.ugent.be>
X-j-chkmail-Score: MSGID : 53AA8C18.001 on smtp1.ugent.be : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/w4g0yuUU3ByJZctjG28ehB0wKHg
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 08:45:22 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--LDti8HsKhrsNLqRLNTXei76agPInV6Oel
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

FWIW, in Flanders (Northern region of Belgium) the two largest ISPs
(Telenet and Belgacom) have been enabling IPv6 for their customers for
the last year or so. Unfortunately, this only includes residential
customers that got the latest CPE model (though luck if you're stuck
with an older model). In the case of Telenet (monopoly ISP on HFC
network) every customer gets a /56 subnet.

This is just to say that (some) ISPs are actually rolling out IPv6. I
would imagine the situation to be similar in other regions of the world.

Floris

On wo 25 jun 2014 07:55:22 CEST, Brian Trammell wrote:
>
> hi Martin, all,
>
> On 25 Jun 2014, at 01:55, Martin Rex <mrex@sap.com> wrote:
>
>>
>> Why would any private individual want to get an IPv6 address?
>> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
>> you may have at least a vague chance that your ID doesn't stick out
>> of every IP datagram like a sore thumb. With IPv6, you're stripped
>> naked for traffic analysis by every governmental agency worldwide, no
>> matter
>> how strong you encrypt your traffic.
>
>
> There is an incredibly dubious assumption hidden in this statement
> that it's hard to map NATted addresses to user and session
> identifiers. Not only is it not particularly hard, it's actually
> _required_ in certain jurisdictions for ISPs to keep this mapping
> information to respond to LE requests.
>
> Even if you're _not_ the ISP or (quasi-)legally empowered to compel it
> to give you this information, there's enough information radiated by
> application layer protocols that you can tease session identifiers
> back out of traces even without payload and with addressing
> information *purposefully* destroyed, as opposed to merely tweaked for
> operational expediency. See e.g. Coull et al "Playing Devil's
> Advocate: Inferring Sensitive Information from Anonymized Network
> Traces" NDSS 2007; Wright et al "On Inferring Application Protocol
> Behaviors in Encrypted Network Traffic" Journal of Machine Learning
> Research 2006; and the citation trees rooted at those two papers.
>
> Network address translation is simply an expedient technique to tease
> a few more bits out of the address space by hiding those bits in
> transient state kept along the path. The assumption that it is somehow
> hard to store or reconstruct that transient state is simply incorrect.
>
> As a method for protecting privacy, NAT is privacy theater, full stop.
>
>>
>> The end-2-end principle is equivalent to a fairly complete loss of
>> privacy.
>> Really, I'm glad that I can use IPv4 and get a new IPv4 address assign=
ed
>> several times a day.
>
>
> I'm pretty sure I read somewhere that we're out of "new" IPv4
> addresses. :) So those addresses aren't new, they're reused. So the
> important metric here isn't the frequency of change, but (1) the size
> of the set of addresses and (2) the predictability of that set. Unless
> you're changing your ISP several times a day, NAT serves only to
> "hide" you in a pool of a very small number of bits of address entropy.=

>
> Regards,
>
> Brian
>


--LDti8HsKhrsNLqRLNTXei76agPInV6Oel
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJTqowXAAoJEB7YeVptYoaUrv4H/iSAKgEMOX/kUdsBgT85mw1V
KDESvSLYupvpXTc5D9P7d6v72jbEaia4dkNsi62ZZr9O2ZR3VhWX1bk5cu89zzVv
VNqnbyLqvWv8uh3ttxYUbcjJyfGCq54V4krLQbFaU+kyoWlggjrv9J1U3AzSSp0Q
2r3XgkoDxfjvIb4OAQs4kXY5H7dKnvQxpEqaa0PF9sxLvBqzwVNmgUFPD0Y8XhRr
tGSQBIlWcZ9Eosqn+LTIR4Jgmm+byX0zlSz6v1QXBjJ+10YjcB7/NrQhA2Y1+WGn
zYJlGiKB/QSLwvxL5BVKRd9knJQU0MORKbA0yNVSIw5oJ8hxpFusuKKioKcUg60=
=vFFL
-----END PGP SIGNATURE-----

--LDti8HsKhrsNLqRLNTXei76agPInV6Oel--


From nobody Wed Jun 25 02:50:53 2014
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 157F81B2B1A for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 02:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.042
X-Spam-Level: 
X-Spam-Status: No, score=-0.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651] autolearn=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 PlRIohcYM7_n for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 02:50:50 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id A702D1B2B16 for <ietf@ietf.org>; Wed, 25 Jun 2014 02:50:49 -0700 (PDT)
Received: (qmail 4375 invoked from network); 25 Jun 2014 09:42:11 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 25 Jun 2014 09:42:11 -0000
Message-ID: <53AA9B75.9070409@necom830.hpcl.titech.ac.jp>
Date: Wed, 25 Jun 2014 18:50:45 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Time to move beyond the 32 bit Internet.
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
In-Reply-To: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/578kg0x-Jp2nI8GICj0VhrUVzbY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 09:50:51 -0000

Phillip Hallam-Baker wrote:

> So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is your
> Internet service 32 bit or 128'?

FYI, NAT means 48 bit Internet, which is large enough for
all the practical purposes.

You can enjoy the 48 bit space even with the end to end transparency
with RSIP (rfc3130), A+P (rfc6346), E2ENAT (draft-ohta-e2e-nat) or
PE-ARP (NANOG47), though A+P is written as if it can't.

						Masataka Ohta


From nobody Wed Jun 25 02:58:02 2014
Return-Path: <Jelte.Jansen@sidn.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A47831B2B35 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 02:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.557
X-Spam-Level: 
X-Spam-Status: No, score=-0.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 LlQFvQ-SxY3Y for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 02:57:58 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BE8A1B2B38 for <ietf@ietf.org>; Wed, 25 Jun 2014 02:57:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=DNkC3hQ+tpgUjeelabrZMnU0g0ihqC/nDkTaAbUg8es=; b=RZAGKIGDW7Qv/MMlVrlnsBDom2EtaRGPhUfVDF0eg+KAChoEofMTUoTIiby+PdZ/fE456wVGJaPBkcOFSlPjukezlmhZR2QE4DdUf9NrXxCeulocj6t6d9dyZa+Hj2cj9cjDpsrTKW5YyGpnzjahdu8PfOOZddx1L3TxCXEoPjs=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by arn2-kamx.sidn.nl  with ESMTP id s5P9vsWv025370-s5P9vsWx025370 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL) for <ietf@ietf.org>; Wed, 25 Jun 2014 11:57:54 +0200
Received: from zen.sidnlabs.nl (94.198.152.214) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 25 Jun 2014 11:57:51 +0200
Message-ID: <53AA9D1F.8000007@sidn.nl>
Date: Wed, 25 Jun 2014 11:57:51 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch>
In-Reply-To: <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mZhxY_-jhjRULs8_ZSVfrFGhBC0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 09:57:59 -0000

On 06/25/2014 07:55 AM, Brian Trammell wrote:
> 
> Network address translation is simply an expedient technique to
> tease a few more bits out of the address space by hiding those bits
> in transient state kept along the path. The assumption that it is
> somehow hard to store or reconstruct that transient state is simply
> incorrect.
> 
> As a method for protecting privacy, NAT is privacy theater, full
> stop.
> 

I'd go a step further. Given that address translation needs things like
CGN, STUN, uPnP and portforwarding to get the most basic of things
working, I think the whole picture gives you less privacy and security
than a completely untranslated end-to-end world does.

BTW, now that Microsoft is finally feeling some actual pain due to a
lack of new addresses in their azure cloud, perhaps there is some hope
that some big parties are finally starting to move.

BTW2, tbh i think calling it 32 vs 64/128 bits 'internet' will make it
even more confusing. I'd prefer something like 'ye olde obsolete
adressing'.

Jelte


From nobody Wed Jun 25 04:09:55 2014
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817151B2BAE for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 04:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.042
X-Spam-Level: 
X-Spam-Status: No, score=-0.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651] autolearn=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 PwtVWChrycSX for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 04:09:51 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id D310C1B2C6F for <ietf@ietf.org>; Wed, 25 Jun 2014 04:06:19 -0700 (PDT)
Received: (qmail 5498 invoked from network); 25 Jun 2014 10:57:41 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 25 Jun 2014 10:57:41 -0000
Message-ID: <53AAAD28.8030401@necom830.hpcl.titech.ac.jp>
Date: Wed, 25 Jun 2014 20:06:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch> <53AA9D1F.8000007@sidn.nl>
In-Reply-To: <53AA9D1F.8000007@sidn.nl>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zCEYgpyskgTZHqCLnT6_1Mdx50g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 11:09:52 -0000

Jelte Jansen wrote:

> Given that address translation needs things like
> CGN, STUN, uPnP and portforwarding to get the most basic of things
> working,

Wrong.

While uPnP involves end systems a little, they hide address
translation from the end systems, which is why they destroy
the end to end transparency (with uPnP, there can be the end
to end transparency for applications over TCP or UDP).

> I think the whole picture gives you less privacy and security
> than a completely untranslated end-to-end world does.

The amount of privacy is same. It is merely that ISPs must have
more log, as long as they assign address/port dynamically on
demand.

But, if ISPs assign one of their customer an address and a range
of port numbers, the amount of log is same.

That is, assigning a customer 192.0.2.1 is not very different
from assigning the customer port 1024 to 1279 of 192.0.2.1.

						Masataka Ohta


> 
> BTW, now that Microsoft is finally feeling some actual pain due to a
> lack of new addresses in their azure cloud, perhaps there is some hope
> that some big parties are finally starting to move.
> 
> BTW2, tbh i think calling it 32 vs 64/128 bits 'internet' will make it
> even more confusing. I'd prefer something like 'ye olde obsolete
> adressing'.
> 
> Jelte
> 
> 
> 


From nobody Wed Jun 25 04:32:40 2014
Return-Path: <Jelte.Jansen@sidn.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8661B2B90 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 04:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.557
X-Spam-Level: 
X-Spam-Status: No, score=-0.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 6hV62ug5CiqX for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 04:32:36 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64BE21B2B8D for <ietf@ietf.org>; Wed, 25 Jun 2014 04:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=864gY2Uaq/ATfonJ5yQsYc3Hltg9/Q47umdJShpF5xI=; b=c6iNX7tZVMLBQuWyl/T4WAlGcGQh2UA1DUjErJdPYs1B+FtccMR/540JKDuluHzg6ISfb2FSq92zea89TCQ+a7P5wE+MFWRMuxqdzFd+OXvgcSW9nwaiv2/+Xibtui01Cd/3TEc1P9P+SPnxLQcAu2gcPFan5EYfM3aTN+Hs204=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by arn2-kamx.sidn.nl  with ESMTP id s5PBWYx3000661-s5PBWYx5000661 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL); Wed, 25 Jun 2014 13:32:34 +0200
Received: from zen.sidnlabs.nl (94.198.152.214) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 25 Jun 2014 13:32:30 +0200
Message-ID: <53AAB34F.5020808@sidn.nl>
Date: Wed, 25 Jun 2014 13:32:31 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, <ietf@ietf.org>
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch> <53AA9D1F.8000007@sidn.nl> <53AAAD28.8030401@necom830.hpcl.titech.ac.jp>
In-Reply-To: <53AAAD28.8030401@necom830.hpcl.titech.ac.jp>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NkLdz2pFvydiEHJ_lg3XHgMg7UI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 11:32:38 -0000

On 06/25/2014 01:06 PM, Masataka Ohta wrote:
>> Given that address translation needs things like
>> CGN, STUN, uPnP and portforwarding to get the most basic of things
>> working,
> 
> Wrong.
> 
> While uPnP involves end systems a little, they hide address
> translation from the end systems, which is why they destroy
> the end to end transparency (with uPnP, there can be the end
> to end transparency for applications over TCP or UDP).
> 

and upnp has been a security nightmare. It may hide your internal
addresses but who cares about that if it creates an attack surface that
can open up your entire network?

Other NAT-workarounds include (sometimes unpredictable) third parties
that should be unnecessary (stun, skype, and probably any number of
game-related solutions). Or force people on a fixed internal address
while they could be switching it around (portforwarding).


>> I think the whole picture gives you less privacy and security
>> than a completely untranslated end-to-end world does.
> 
> The amount of privacy is same. It is merely that ISPs must have
> more log, as long as they assign address/port dynamically on
> demand.
> 
> But, if ISPs assign one of their customer an address and a range
> of port numbers, the amount of log is same.
> 
> That is, assigning a customer 192.0.2.1 is not very different
> from assigning the customer port 1024 to 1279 of 192.0.2.1.
> 

yeah, from an ISP point of view it's the same.

Jelte


From nobody Wed Jun 25 05:26:31 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28161B2BE7 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 05:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 ztpHt9Dl-QRZ for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 05:26:23 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C5551B2AF3 for <ietf@ietf.org>; Wed, 25 Jun 2014 05:26:23 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so1985464wgh.16 for <ietf@ietf.org>; Wed, 25 Jun 2014 05:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=924/OTatXLdUo45XYhrKmNmaO50H3Z6K5qr3ADjosyQ=; b=vhrHaya/hb7o9BX98N0SS0KZs7A6gE7ehkbJTZqefpbL8n3JEX0DoOQHH//AMHmacB 0IRsWzy5NFg1A9RK/jrGOfNx5QPziK5NjoM+xx0H28XH6oK4NUEkMqOlfoF2s/61y1uX 1TyF520LKcqlmbXp9StPC0Bpjge+ds4293Dz9fEksHeSyEHp3S4O/JExoNOEI7SYlGjK cdQGncSBE2aC0f70uv0fpBFery7igVv3rn27xfEq9Tir2mps1KKVvr49V8szjl9kgkHz DzhXIzH/1uDDAP3WTO0JDpKhJ/kADoHqwQORw7WkZgQWVmhXbQNjCsFqMF3WqjNyNJi2 W9ww==
MIME-Version: 1.0
X-Received: by 10.180.73.70 with SMTP id j6mr5279719wiv.64.1403699178329; Wed, 25 Jun 2014 05:26:18 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Wed, 25 Jun 2014 05:26:18 -0700 (PDT)
In-Reply-To: <69B9BA3779753A49865BB9010D560EBB7020@newserver.arneill-py.local>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <69B9BA3779753A49865BB9010D560EBB7020@newserver.arneill-py.local>
Date: Wed, 25 Jun 2014 08:26:18 -0400
X-Google-Sender-Auth: GmWXZV8C0q2F2MFZ_mc7cFRZT7g
Message-ID: <CAMm+LwhLbvZoR1L=R3XR6kCvqnWp2OpdTFhdXSi-D9zyuv_CFA@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=f46d04389085e55ec104fca82ecd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2wcieEb051uM1sHB1Tw0Hoji6cs
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 12:26:29 -0000

--f46d04389085e55ec104fca82ecd
Content-Type: text/plain; charset=UTF-8

On Wed, Jun 25, 2014 at 12:28 AM, Michel Py <
michel@arneill-py.sacramento.ca.us> wrote:

> > Phillip Hallam-Baker wrote :
> > So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is your
> Internet service 32 bit or 128'?
>
> Creative. Since freeIPv6porn.com this is the definitely one of the best
> marketing attempts that I can remember.
>
> However, I would be concerned that deciders who would be tempted by that
> pick-up line had been earlier adopters of 64-bit OS and found 64-bit
> drivers for their existing peripherals (or the lack, thereof) disturbing.
>

Actually, that is part of the message.

Going to IPv6 is not easy or inexpensive. And one of the reasons that is
the case is that there has been an assumption that it will 'just happen'
and that there is no need to consider bridge technologies.

People literally laughed at me when I said that we needed to embrace NAT to
deploy IPv6. Today there are very few people who don't get the reasons why.
But if you look at the efforts O/S vendors had to go through to get to 64
bits, NAT is a minor carbuncle in comparison. The way a 64 bit O/S runs a
32 bit program is not pretty.



> > Actually IPv6 is a 64 bit Internet, not 128 bits.
>
> Better to forget that and try to sell it as 128 bits, as nobody else has
> been burned but that number yet.
>

I think it would sound like twice the pain.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jun 25, 2014 at 12:28 AM, Michel Py <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:michel@arneill-py.sacramento.ca.us" target=3D"_blank">michel@arneill-p=
y.sacramento.ca.us</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; Phillip Hallam-Baker wrote :<br>
<div class=3D"">&gt; So lets stop asking ISPs &#39;do you support IPv6&#39;=
 and instead ask &#39;Is your Internet service 32 bit or 128&#39;?<br>
<br>
</div>Creative. Since freeIPv6porn.com this is the definitely one of the be=
st marketing attempts that I can remember.<br>
<br>
However, I would be concerned that deciders who would be tempted by that pi=
ck-up line had been earlier adopters of 64-bit OS and found 64-bit drivers =
for their existing peripherals (or the lack, thereof) disturbing.<br></bloc=
kquote>
<div><br></div><div>Actually, that is part of the message.</div><div><br></=
div><div>Going to IPv6 is not easy or inexpensive. And one of the reasons t=
hat is the case is that there has been an assumption that it will &#39;just=
 happen&#39; and that there is no need to consider bridge technologies.</di=
v>
<div><br></div><div>People literally laughed at me when I said that we need=
ed to embrace NAT to deploy IPv6. Today there are very few people who don&#=
39;t get the reasons why. But if you look at the efforts O/S vendors had to=
 go through to get to 64 bits, NAT is a minor carbuncle in comparison. The =
way a 64 bit O/S runs a 32 bit program is not pretty.=C2=A0</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"=
"><br>
&gt; Actually IPv6 is a 64 bit Internet, not 128 bits.<br>
<br>
</div>Better to forget that and try to sell it as 128 bits, as nobody else =
has been burned but that number yet.<br></blockquote><div><br></div><div>I =
think it would sound like twice the pain.</div><div><br></div><div><br>
</div></div></div></div>

--f46d04389085e55ec104fca82ecd--


From nobody Wed Jun 25 08:39:59 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61971B2D1E for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 08:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ZEFOgWIrcyP4 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 08:39:56 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D00281B2D0A for <ietf@ietf.org>; Wed, 25 Jun 2014 08:39:55 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s5PFdpHC004195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 17:39:51 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <53AA14DA.6080504@umn.edu>
To: David Farmer <farmer@umn.edu>
Date: Wed, 25 Jun 2014 17:39:51 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140625153951.053FF1AD66@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Cl_O8hEZOC5X9zyK39jeJAg09e0
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 15:39:57 -0000

David Farmer wrote:
> On 6/24/14, 18:55 , Martin Rex wrote:
> 
> > Why would any private individual want to get an IPv6 address?
> > With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
> > you may have at least a vague chance that your ID doesn't stick out
> > of every IP datagram like a sore thumb.  With IPv6, you're stripped
> > naked for traffic analysis by every governmental agency worldwide, no matter
> > how strong you encrypt your traffic.
> >
> > The end-2-end principle is equivalent to a fairly complete loss of privacy.
> > Really, I'm glad that I can use IPv4 and get a new IPv4 address assigned
> > several times a day.
> 
> But do you really get a different IPv4 address?

Yes, definitely.


>
> In the situation you discuss that is completely up to your provider,
> not really up to you. 

Agreed.  But the national regulator&legislator can help.


>
> With IPv6 my laptop, iPhone, and iPad are continually changing their 
> IPv6 address

Do you really get a new _prefix_ (One than is randomly drawn from
a pool of ISP customers)?


-Martin


From nobody Wed Jun 25 09:16:59 2014
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8D61B2D6C for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.147
X-Spam-Level: 
X-Spam-Status: No, score=0.147 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 DW4C_onxCmkz for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:16:53 -0700 (PDT)
Received: from mail.connotech.com (connotech.com [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 73F061B2D47 for <ietf@ietf.org>; Wed, 25 Jun 2014 09:16:53 -0700 (PDT)
Received: from [192.168.1.204] (DODECA1ER.CONNOTECH-INTERNAL.COM [192.168.1.204]) by mail.connotech.com (Postfix) with ESMTPA id C3D7C319F9 for <ietf@ietf.org>; Wed, 25 Jun 2014 12:28:55 -0400 (EDT)
Message-ID: <53AAF719.7000003@connotech.com>
Date: Wed, 25 Jun 2014 16:21:45 +0000
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Time to move beyond the 32 bit Internet.
References: <20140625153951.053FF1AD66@ld9781.wdf.sap.corp>
In-Reply-To: <20140625153951.053FF1AD66@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/anBAJ6YBO1Um5gFDaBtlkUNOA-c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 16:16:55 -0000

On 2014-06-25 15:39, Martin Rex wrote:
> David Farmer wrote:
>> On 6/24/14, 18:55 , Martin Rex wrote:
>>
>>> Why would any private individual want to get an IPv6 address?
>>> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
>>> you may have at least a vague chance that your ID doesn't stick out
>>> of every IP datagram like a sore thumb.  With IPv6, you're stripped
>>> naked for traffic analysis by every governmental agency worldwide, no matter
>>> how strong you encrypt your traffic.
>>>
>>> The end-2-end principle is equivalent to a fairly complete loss of privacy.
>>> Really, I'm glad that I can use IPv4 and get a new IPv4 address assigned
>>> several times a day.
>>
>> But do you really get a different IPv4 address?
>
> Yes, definitely.
>
>
>>
>> In the situation you discuss that is completely up to your provider,
>> not really up to you.
>
> Agreed.  But the national regulator&legislator can help.
>

In here, the legislator helps law enforcement agencies by mandating the 
ISPs to keep records of dynamic IP address assignments for some minimal 
duration, notably. (At least this is my understanding of legislative 
amendments pushed in our parliament.)

Privacy enhanced with IPv4? Maybe a false sense of privacy.

- Thierry


From nobody Wed Jun 25 09:29:18 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82711B29F1 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.152
X-Spam-Level: 
X-Spam-Status: No, score=-115.152 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_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 aStMeiOn3LSZ for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:29:13 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0249E1B29EB for <ietf@ietf.org>; Wed, 25 Jun 2014 09:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2332; q=dns/txt; s=iport; t=1403713753; x=1404923353; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=4iA/BCWQ18EHs4lH4viSU0JjeJB41gWtJfLrooYIOjw=; b=mZZsmbTI4UB18vO0Kf2NKkeZjelYqXt9wyckEemmxby9rjvR2X5pCE7O Jz1uxC0reQ/64NstDKdcARwbt0P9luEUJxkmvuFU7D2k5XUfsi1XqqOVM xlIvEPf3wkpM6HgSzSb4ywLOg/nqLVMzxh7hbcKBiAloQdjHtwep1HOAu Q=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAK73qlOtJV2c/2dsb2JhbAA/GoMNUlrDSwGBDhZ1hAMBAQEDAXkFCwIBCEYyJQIEDgUOiCwIDTanCJpqEwSOfAeDLYEWBYRjAo0jgUGHCI1shX+DQmyBRA
X-IronPort-AV: E=Sophos;i="5.01,546,1400025600";  d="asc'?scan'208";a="332495659"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 25 Jun 2014 16:29:12 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s5PGTB1b015850 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Jun 2014 16:29:11 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.143]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Wed, 25 Jun 2014 11:29:11 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Floris Van den Abeele <floris.vandenabeele@intec.ugent.be>
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
Thread-Topic: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
Thread-Index: AQHPj8LAjHuEvda2lU2S80toG+4BrZuBJQqA///IImaAAFa+gIAAZHwAgAAvZwCAAIGrAA==
Date: Wed, 25 Jun 2014 16:29:10 +0000
Message-ID: <612C9C9E-4E99-4B32-96BC-314D1F87F55F@cisco.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch> <53AA8C0E.3020708@intec.ugent.be>
In-Reply-To: <53AA8C0E.3020708@intec.ugent.be>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_CF6DAA96-0EF5-495F-A5B2-B91A01F44873"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Q5yKSDxsld85OD5GHeCnnI7baa0
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 16:29:14 -0000

--Apple-Mail=_CF6DAA96-0EF5-495F-A5B2-B91A01F44873
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jun 25, 2014, at 1:45 AM, Floris Van den Abeele =
<floris.vandenabeele@intec.ugent.be> wrote:

> FWIW, in Flanders (Northern region of Belgium) the two largest ISPs
> (Telenet and Belgacom) have been enabling IPv6 for their customers for
> the last year or so. Unfortunately, this only includes residential
> customers that got the latest CPE model (though luck if you're stuck
> with an older model). In the case of Telenet (monopoly ISP on HFC
> network) every customer gets a /56 subnet.

We also see measurable growth in traffic and deployment.

Eric put together some graphs of Ipv6 growth, using Google data. It =
attempts to project traffic level a year hence, with obvious dependency =
on the regression model. You may find it interesting to poke around in. =
An =93IPv6-enabled web browser=94 is a web browser that exchanges data =
with Google using IPv6, and implies not only the browser and laptop, but =
intervening network.

An interesting comparison regarding =93a year hence=94 is the range =
between the logistic curve prediction and the quadratic projection; =
where it=92s actually going to be is probably bracketed by those =
numbers. Take some time poking around.

=
https://www.vyncke.org/ipv6status/project.php?metric=3Dp&timeforward=3D&ti=
mebackward=3D&country=3Dbe
=
https://www.vyncke.org/ipv6status/project.php?metric=3Dp&timeforward=3D&ti=
mebackward=3D&country=3Dus
=
https://www.vyncke.org/ipv6status/project.php?metric=3Dp&timeforward=3D&ti=
mebackward=3D&country=3Dde
=
https://www.vyncke.org/ipv6status/project.php?metric=3Dp&timeforward=3D&ti=
mebackward=3D&country=3Dww



--Apple-Mail=_CF6DAA96-0EF5-495F-A5B2-B91A01F44873
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFTqvjUbjEdbHIsm0MRAh53AKDB2Ay+OE47aNQ6Blc3Eq45X6jRqwCgjCsq
DaCKBcAtGspTI56K4DyG+uU=
=L13h
-----END PGP SIGNATURE-----

--Apple-Mail=_CF6DAA96-0EF5-495F-A5B2-B91A01F44873--


From nobody Wed Jun 25 09:37:27 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 450441B2A4F for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 wTljRCDO0wSa for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 09:37:22 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8ED71B2A8A for <ietf@ietf.org>; Wed, 25 Jun 2014 09:37:22 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8A0061B806B for <ietf@ietf.org>; Wed, 25 Jun 2014 09:37:22 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 7F5A7190071; Wed, 25 Jun 2014 09:37:22 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 25 Jun 2014 09:37:22 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: The P in NAPT != Privacy was Re: Time to move beyond the 32 bit Internet.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <612C9C9E-4E99-4B32-96BC-314D1F87F55F@cisco.com>
Date: Wed, 25 Jun 2014 12:37:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <4E6FEA6B-14C7-4FE8-9270-AB97BFFECD87@nominum.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <C7352F08-B5DE-418E-AF91-8F9EB4C04125@trammell.ch> <53AA8C0E.3020708@intec.ugent.be> <612C9C9E-4E99-4B32-96BC-314D1F87F55F@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bbS0gZzDbV3ij9vwF7K_xtM-nAc
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 16:37:24 -0000

On Jun 25, 2014, at 12:29 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> Eric put together some graphs of Ipv6 growth, using Google data. It =
attempts to project traffic level a year hence, with obvious dependency =
on the regression model. You may find it interesting to poke around in. =
An =93IPv6-enabled web browser=94 is a web browser that exchanges data =
with Google using IPv6, and implies not only the browser and laptop, but =
intervening network.

What's that weird blip in December 2013?   Also, the numbers for France =
look pretty grim!


From nobody Wed Jun 25 10:09:01 2014
Return-Path: <dwing@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26FF61B2B37 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 iop5DeAzTjj6 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:08:55 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB1C1B2A8B for <ietf@ietf.org>; Wed, 25 Jun 2014 10:08:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4140; q=dns/txt; s=iport; t=1403716134; x=1404925734; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=szZrYAjk3LY+ge+neAww+qedu4C8HD2iNQW/n9dJe5U=; b=iLNwzrc+QEW5o0bYtSdRhWyCAKxsCOEsVmLRRhvwXwCutoXbk++uA4cg ZzbrzIXVKtlPdYF+SmHYHl8OuY1ByFHh7dudLtaoDg/Hpgj4/fiPBPmkb 0nRMn3Wpe4tLN4mr5+GNpPmxS5ha9o0SSsENyS31H4aDXz4WXpGA5ag4O Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFANwAq1OtJA2D/2dsb2JhbABZgw2rNwUBmToBgQ4WdYQDAQEBAwE6PwUJAgsYLhsuAQ0GE4g6CMJVFwSFX4hmMweDLYEWBYpEkA2LYIgLg2IdgTEk
X-IronPort-AV: E=Sophos;i="5.01,547,1400025600"; d="scan'208";a="335402328"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-1.cisco.com with ESMTP; 25 Jun 2014 17:08:52 +0000
Received: from sjc-vpn4-975.cisco.com (sjc-vpn4-975.cisco.com [10.21.83.206]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s5PH8o9N002950 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 25 Jun 2014 17:08:51 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <20140625005627.2DCAC19400A7@rock.dv.isc.org>
Date: Wed, 25 Jun 2014 10:08:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <20C4472E-C736-4620-B7BD-ACFCF826D327@cisco.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <20140625005627.2DCAC19400A7@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zeoCvyKhHYwp65sx9Qtoevi1rYM
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:08:58 -0000

On Jun 24, 2014, at 5:56 PM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <20140624235543.332511AD64@ld9781.wdf.sap.corp>, Martin Rex =
writes:
>> Mark Andrews wrote:
>>>=20
>>> Martin Rex writes:
>>>>=20
>>>> Phillip Hallam-Baker wrote:
>>>>>=20
>>>>> While going through the Windows API calls and thinking how old =
fashione
>> d
>>>>> and lame all those 'Win32' classes look now, a sudden thought:
>>>>>=20
>>>>> Ordinary users don't understand the importance of going from IPv4 =
to IP
>> v6.
>>>>>=20
>>>>> But Ordinary users do understand that 32 bits is bad and old and =
obsole
>> te
>>>>> and rubbish and 64 bits is better.
>>>>=20
>>>> Experienced users know painfully well just how smooth and painless
>>>> 32-bit (windows) and 32-bit IPv4 is, whereas newer 64-bit (windows)
>>>> and newer 128-bit IPv6 is just many painful problems and ZERO =
benefit.
>>>>=20
>>>> A lot of the equipment that me and my family is using is not IPv6 =
capable
>> ,
>>>> and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
>>>> ***MUCH*** better when configured with IPv4-only anyway, so why =
bother.
>>>>=20
>>>> If someone needs to be pushed, then it is *VENDORS*, not users,
>>>> that they ship their equipment in a fashion that it will work with =
IPv6,
>>>> should this ever become available.  Then maybe in 10 years from =
now,
>>>> this might become interesting to end users.
>>>=20
>>> Given there are ISP delivering IPv6 + DS-Lite today over fibre
>>> because they have run out of addresses it is time that *everybody*
>>> starts complaining to every supplier that doesn't ship equipement
>>> / services with IPv6 enabled by default.
>>=20
>>=20
>> Why would any private individual want to get an IPv6 address?
>> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
>> you may have at least a vague chance that your ID doesn't stick out
>> of every IP datagram like a sore thumb.  With IPv6, you're stripped
>> naked for traffic analysis by every governmental agency worldwide, no =
matter
>> how strong you encrypt your traffic.
>=20
> Because with CGN, DS-Lite and NAT64 you have a third class IPv4
> internet.  You can't run any services what so ever.  You cannot do
> anything that requires anything other than UDP or TCP over IPv4.
> Try running IPv4 in IPv4 or IPv6 in IPv4 tunnels over CGN, DS-Lite
> and NAT64.  They do not work due to the addresses sharing.  Try
> running a NAS from behind them, it does not work.
>=20
> With one level of NAT that you control (second class internet) you
> can kludge around some of the issues cause by not having global
> addresses ability of every machine.  UPNP helps here.
>=20
> As for you ID sticking out, IPv6 is no worse that IPv4 is for all
> practical purposes with currently shipping IPv6 stacks.  They have
> privacy addresses and they are turned on by default.

IPv6 privacy addresses aren't changed very frequently -- I see them =
change only every 24 hours.  Can they change more frequently with sysctl =
or application encouragement?  I know NAPT assigns a new port for every =
connection, which is how often we need a new IPv6 privacy address to =
provide NAPT-equvilence host obfuscation.

-d


> Now with IPv6 you have a choice of whether to offer a service or
> not and you don't have configure port forwarding etc.  You can have
> both stable and temporary addresses at the same time for the same
> box.  You can choose which to use on a service and/or role basis.
>=20
> But hey a third class internet is "good enough" for the plebes at
> home.  They don't deserve to be able to run servers from home.  They
> don't deserve to have a first class internet.
>=20
> Mark
>=20
>> The end-2-end principle is equivalent to a fairly complete loss of =
privacy.
>> Really, I'm glad that I can use IPv4 and get a new IPv4 address =
assigned
>> several times a day.
>>=20
>> -Martin
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>=20


From nobody Wed Jun 25 10:16:57 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE2C1B2A95 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 nnNvM_mdCSPs for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:16:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FB851B2A75 for <ietf@ietf.org>; Wed, 25 Jun 2014 10:16:53 -0700 (PDT)
Received: from mbp.local (31.66.208.web-pass.com [208.66.31.202] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s5PHGi9x032880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 25 Jun 2014 17:16:44 GMT (envelope-from joelja@bogus.com)
Message-ID: <53AB03F7.9080709@bogus.com>
Date: Wed, 25 Jun 2014 10:16:39 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>, Mark Andrews <marka@isc.org>
Subject: Re: Time to move beyond the 32 bit Internet.
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <20140625005627.2DCAC19400A7@rock.dv.isc.org> <20C4472E-C736-4620-B7BD-ACFCF826D327@cisco.com>
In-Reply-To: <20C4472E-C736-4620-B7BD-ACFCF826D327@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8XDdCtCLU1SXNrQfmeELNIJI2XL6rb13h"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Wed, 25 Jun 2014 17:16:44 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ztx13TREybUZE6bXG6ipbL_ptlE
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:16:55 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8XDdCtCLU1SXNrQfmeELNIJI2XL6rb13h
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 6/25/14 10:08 AM, Dan Wing wrote:
>=20
<snip>
>=20
> IPv6 privacy addresses aren't changed very frequently -- I see them
> change only every 24 hours.  Can they change more frequently with
> sysctl or application encouragement?  I know NAPT assigns a new port
> for every connection, which is how often we need a new IPv6 privacy
> address to provide NAPT-equvilence host obfuscation.

you pay the price for that in the size of your ND cache. which unlike
that napt connection table doesn't get expired when the connection
terminates. having thousands of l3 nexthops for each device isn't a
great way to scale ethernet switches.






--8XDdCtCLU1SXNrQfmeELNIJI2XL6rb13h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOrA/cACgkQ8AA1q7Z/VrIjCQCeOvwzZioiKteg+DtQqcw/vE1B
0roAmgJW0iT0B6qnaTsTAZ8iBn9YC8Tr
=SRlc
-----END PGP SIGNATURE-----

--8XDdCtCLU1SXNrQfmeELNIJI2XL6rb13h--


From nobody Wed Jun 25 10:23:57 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A801B2CCC for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 SVkezr8dN-_h for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:23:50 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27D951B29EF for <ietf@ietf.org>; Wed, 25 Jun 2014 10:23:49 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s5PHNicn007204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 19:23:44 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <20140625005627.2DCAC19400A7@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
Date: Wed, 25 Jun 2014 19:23:44 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EUU503D9O5QZW60uvVJWv8pY3NA
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:23:54 -0000

Mark Andrews wrote:
>> 
>> Why would any private individual want to get an IPv6 address?
>> With DHCP IPv4 + NAT (on your Home router) and even more so with CGN,
>> you may have at least a vague chance that your ID doesn't stick out
>> of every IP datagram like a sore thumb.  With IPv6, you're stripped
>> naked for traffic analysis by every governmental agency worldwide, no matter
>> how strong you encrypt your traffic.
> 
> Because with CGN, DS-Lite and NAT64 you have a third class IPv4
> internet.  You can't run any services what so ever.

The majority of home users actually do not want and do not need to
run any service in the first place.

And the majority of home users who do run services on their home
network today (Bots; trojaned PC) would probably rather not to do so.


>
> You cannot do anything that requires anything other than
> UDP or TCP over IPv4.

There is nothing any members of my family or any of my equipment
needs that doesn't fit here.


>
> Try running IPv4 in IPv4 or IPv6 in IPv4 tunnels over CGN, DS-Lite
> and NAT64.  They do not work due to the addresses sharing.  Try
> running a NAS from behind them, it does not work.

I do *NOT* use IPv6 anywhere, and of the few equipment that I have
that is IPv6 capable at all, I have IPv6 removed or disabled, because
that makes it run smoother and safer.


> 
> With one level of NAT that you control (second class internet) you
> can kludge around some of the issues cause by not having global
> addresses ability of every machine.  UPNP helps here.


There is a difference between using a random changing DHCP-assigned
IPv4 address that is NATed on your home gateway by default, and not
being able to get a static IPv4 or static IPv6 address assigned (and used)
for _very_limited_and_very_specific_ services.


> 
> As for you ID sticking out, IPv6 is no worse that IPv4 is for all
> practical purposes with currently shipping IPv6 stacks.  They have
> privacy addresses and they are turned on by default.

IPv6 privacy addresses are security theater when the network prefix
is constant and the number of users sharing the prefix is tiny.


> 
> Now with IPv6 you have a choice of whether to offer a service or
> not and you don't have configure port forwarding etc.  You can have
> both stable and temporary addresses at the same time for the same
> box.  You can choose which to use on a service and/or role basis.


*NOT* having to configure port forwarding is a real security issue,
that you really can not seriously want to be the default for home users.


> 
> But hey a third class internet is "good enough" for the plebes at home.

Given the small bandwith that many home DSL subscribers face, there simply
is no use case for "offering services" from home in the first place.


-Martin


From nobody Wed Jun 25 10:25:30 2014
Return-Path: <dwing@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE2B1B2D7C for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 99G9hQULha0E for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:25:24 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F95B1B2D4B for <ietf@ietf.org>; Wed, 25 Jun 2014 10:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=776; q=dns/txt; s=iport; t=1403717126; x=1404926726; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=igKxIfm4ZUDNdUl9ywQ+Ej0U8OvCRHfnumnnNz7N9wc=; b=YFUGWK7aVfhPYWOpGqa/JPAr8OMy1HAqRdPtOxKlcI4KYZlPtdk6OzYs tgexxwIzJ7DumFH1z8thlpxQ/iPoSCPdfb0o/2z6dfZHnKhmBnltM6S1w VS5Qf/NuBvbDutPvasioz+luFYWqnah17p9a/GfIYTOhjc2ovJcpiJijS c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAHwFq1OtJV2Q/2dsb2JhbABZgw2rNwUBmToBgQ4WdYQDAQEBAwF5BQsLGC5XBhOIOgjCeBeFY4NjhTYHgy2BFgEEikSQDZNrg2Id
X-IronPort-AV: E=Sophos;i="5.01,547,1400025600"; d="scan'208";a="335406503"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP; 25 Jun 2014 17:25:25 +0000
Received: from sjc-vpn4-975.cisco.com (sjc-vpn4-975.cisco.com [10.21.83.206]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s5PHPLaK019837 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 25 Jun 2014 17:25:23 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <53AB03F7.9080709@bogus.com>
Date: Wed, 25 Jun 2014 10:25:21 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <0FE13F23-4DA9-4B6A-BBE5-60DF269D6A86@cisco.com>
References: <20140624235543.332511AD64@ld9781.wdf.sap.corp> <20140625005627.2DCAC19400A7@rock.dv.isc.org> <20C4472E-C736-4620-B7BD-ACFCF826D327@cisco.com> <53AB03F7.9080709@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6RKlAw0xjiLy5gZKzHOef4wOWdk
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:25:26 -0000

On Jun 25, 2014, at 10:16 AM, joel jaeggli <joelja@bogus.com> wrote:

> On 6/25/14 10:08 AM, Dan Wing wrote:
>> 
> <snip>
>> 
>> IPv6 privacy addresses aren't changed very frequently -- I see them
>> change only every 24 hours.  Can they change more frequently with
>> sysctl or application encouragement?  I know NAPT assigns a new port
>> for every connection, which is how often we need a new IPv6 privacy
>> address to provide NAPT-equvilence host obfuscation.
> 
> you pay the price for that in the size of your ND cache. which unlike
> that napt connection table doesn't get expired when the connection
> terminates. having thousands of l3 nexthops for each device isn't a
> great way to scale ethernet switches.

Yep, we've seen that problem.

-d


From nobody Wed Jun 25 10:26:20 2014
Return-Path: <Lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A0D1B2CCC for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.769
X-Spam-Level: 
X-Spam-Status: No, score=0.769 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_SORBS_WEB=0.77] autolearn=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 5hGI6LHwEs6d for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:26:08 -0700 (PDT)
Received: from atl4mhob16.myregisteredsite.com (atl4mhob16.myregisteredsite.com [209.17.115.109]) by ietfa.amsl.com (Postfix) with ESMTP id 85F911B2D89 for <ietf@ietf.org>; Wed, 25 Jun 2014 10:26:07 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob16.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s5PHQ5cg029505 for <ietf@ietf.org>; Wed, 25 Jun 2014 13:26:05 -0400
Received: (qmail 18163 invoked by uid 0); 25 Jun 2014 17:26:05 -0000
X-TCPREMOTEIP: 204.235.115.163
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?10.71.36.51?) (lee@asgard.org@204.235.115.163) by 0 with ESMTPA; 25 Jun 2014 17:26:04 -0000
User-Agent: Microsoft-MacOutlook/14.4.2.140509
Date: Wed, 25 Jun 2014 13:26:05 -0400
Subject: Re: Time to move beyond the 32 bit Internet.
From: Lee Howard <Lee@asgard.org>
To: <mrex@sap.com>, Phillip Hallam-Baker <phill@hallambaker.com>
Message-ID: <CFD07B52.6054E%Lee@asgard.org>
Thread-Topic: Time to move beyond the 32 bit Internet.
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
In-Reply-To: <20140624220513.4F8CB1AD64@ld9781.wdf.sap.corp>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pD3gX6BfEf8NYF2Tpxre9m1ojzU
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:26:09 -0000

Venue question: Is this the right place to discuss marketing techniques?

On 6/24/14 6:05 PM, "Martin Rex" <mrex@sap.com> wrote:

>
>A lot of the equipment that me and my family is using is not IPv6 capable,
>and *ALL* Software that I've used so far (Linux, WinXP, Win7) runs
>***MUCH*** better when configured with IPv4-only anyway, so why bother.

You know that WinXP is end of support, right?
I haven't seen data showing dual-stack to be in any way inferior to
IPv4-only.
If you have some, please forward.
I have seen data showing IPv6 latency is lower.

>
>If someone needs to be pushed, then it is *VENDORS*, not users,
>that they ship their equipment in a fashion that it will work with IPv6,
>should this ever become available.  Then maybe in 10 years from now,
>this might become interesting to end users.

I believe it was Joe St. Sauver who said:
	Consumers don't care about plumbing, they want water.

	Whether the water comes over cast iron, copper, or PVC only matters to
	the plumbers.



In my humble opinion, it is too late to argue about whether IPv6 will be
deployed.  It is.
We can argue about where there are gaps, and whether IPv6 will be
universal enough (and "enough for what?", and how to sunset IPv4 (q.v.),
and how to avoid or improve NATs.  We could argue about whether IETF
should keep updating IPv4 and working around NAT
(draft-george-ipv6-support).

And of course, we each 2119-SHOULD deploy IPv6 as universally as possible.


Lee



From nobody Wed Jun 25 10:43:26 2014
Return-Path: <nd@syndicat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2D01B2A10 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.953
X-Spam-Level: 
X-Spam-Status: No, score=-2.953 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 A4X8u94fpTqb for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 10:43:19 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 02F411B2D8A for <ietf@ietf.org>; Wed, 25 Jun 2014 10:43:19 -0700 (PDT)
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 10.04_1-PostHamster) (envelope-from <nd@syndicat.com>) id 1WzrE4-0000iY-8r; Wed, 25 Jun 2014 19:43:16 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yVSgwpZBNg7; Wed, 25 Jun 2014 19:43:16 +0200 (CEST)
Received: from p5dc3f26e.dip0.t-ipconnect.de ([93.195.242.110] helo=gongo.localnet) by mail.syndicat.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Syndicat.com PostHamster 10.04_1-PostHamster) (envelope-from <nd@syndicat.com>) id 1WzrE3-0003IB-Sx; Wed, 25 Jun 2014 19:43:15 +0200
From: Niels Dettenbach <nd@syndicat.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Time to move beyond the 32 bit Internet.
Date: Wed, 25 Jun 2014 19:43:08 +0200
Message-ID: <1938577.jO2gyWluhM@gongo>
Organization: Syndicat IT&Internet
User-Agent: KMail/4.12.2 (Linux/3.13.3-gentoo; KDE/4.12.2; x86_64; ; )
In-Reply-To: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1889930.nJHUrQgvAQ"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QfMkbM0L4F3cO1Gog48Woe3MCpY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 17:43:22 -0000

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

Am Mittwoch, 25. Juni 2014, 19:23:44 schrieb Martin Rex:
> IPv6 privacy addresses are security theater when the network prefix
> is constant and the number of users sharing the prefix is tiny.
...ahh,
which is 'not' the case with (much) shorter IPv4 network prefixes and (=
much)=20
smaller address pools?!...

Seeing NAT as any kind of "network security" or "anonymity" feature is =
a major=20
reason for the major security and abuse problems within the internet to=
day=20
(incl. bots and similiar you mentioned).

The fact that most users are not providing services on the net is not t=
rue at=20
all.

Alone all that "nice" stuff from Skype to TeamViewer whose major point =
is that=20
they "trick out" typical, non managed stateful inspection firewalls on =
NAT and=20
the fact that even most typical IT service providers are using and=20
recommending that crap for high risky scenarios shows that it is time t=
o bring=20
up pressure to think about.=20

And if IPv6 will bring up this too - plus one point from me...

On the other hand - i have a lot of new internet app scenarios in mind =
which=20
are not practical today without a more flexible - access network transp=
arent -=20
end user access to IP.



cheerioh,


Niels.
=2D-=20
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
=20




--nextPart1889930.nJHUrQgvAQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABCAAGBQJTqwowAAoJEM78prARigUnY1IQAJ5u0lzbmZ9up/Qsyj0cuxvL
trTXZ2SzC/4c/dSXAzmj65K57i+81w/MCuaum0TpZrPHtUkxQ7wDtjm4/CIU62me
oozQkdfsmRQC5lA9Lnvt9pPMQ6f2gIQaLfT5wYN6MvYv8lKlyjN3AkUrJlCjCJGo
f6KuYD9D/1HHQEkFqpyvCj/qBugyA0YRNs4CDJRJGdYDyd2pFJ2eZADR+Ltl/rTg
SUNAyu3m0dHRM6scPsT+Dp7Cy8O9nXVeyU5dNns4fo0s2w3W9/Ln+/DYIy5LsIVV
K7wkgSf6cLmgeUc0/7qJ9HCEvbqcDomSoCbNTA6l6XGnv9rFEMuBz3rUX3hLVlP7
0UbZRfFEz0TZA5St8WSYr7g4FoRrQfofZzOGJoDVdpaScKEVmsrvGzBH9wGH+fLY
8azcThTRaSqOYtA1FfNhkojI31kR32V2IaLWvVieJj8J2EYEs5FJkq7TDVDvpxjf
Wnqkh3Enw41JQadzpG8Z1DPje4vdAJa3fc0jH1L0yy3ovQ4YtjdMg6HCJRRLPGbz
xRNcIT0jItHvGaZK1z+opaPggNL/5jWAzwAf8n7QcHJnxuj1Mt/QBAxpdJSgn1eT
0hN/WLjYpMhk6jy0qty8dfuWODB32BdYHBlnwmeQC/w83ZQb5BZQxCGE0N7dnVcU
ejwIvuedo1yYmfplAxAU
=/Qjl
-----END PGP SIGNATURE-----

--nextPart1889930.nJHUrQgvAQ--


From nobody Wed Jun 25 11:43:38 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676861B2E12 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 11:43:36 -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, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_44=0.6, SPF_PASS=-0.001] autolearn=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 YqT31CGXB-jE for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 11:43:35 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED6EE1B2E0A for <ietf@ietf.org>; Wed, 25 Jun 2014 11:43:34 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id k48so2495102wev.34 for <ietf@ietf.org>; Wed, 25 Jun 2014 11:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jaYi8PD5IUMVtqQZ/U/rbAoU6muPM7862SFeHrX7gY8=; b=T5SlpXGD51NLgSXeJhYlzIcc+TcmtURxFvyHhROkapxPKverMaKNj+PIU78JVM57/t goCaEz7zs/KnN6i3Rk70HRZwPA9sNpP16CkzbasBtDolWeEW+pm+w6a9nstkzZ7Ao0iv 9h6wa5zx1oDXQM3U6cMl038sWSF6VyydmLOHz+FLRMf71UnfIJBSWlfqUCdMpOPgzfYb v/OX5xkii8gaYDOhvQtHiUdnQ36oaH+ym2UgD91+8pSedUVsrynsgfdtsS+BkiBb7+Se 0vZoNTYT5GgguIF/3ACY2rZpXGXfsd6266h0079vti3UP5UtLwNwEPNx9IcJhbyI6DWj ywtw==
X-Received: by 10.194.157.195 with SMTP id wo3mr5279885wjb.130.1403721813076;  Wed, 25 Jun 2014 11:43:33 -0700 (PDT)
Received: from [192.168.1.104] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id cz8sm9117055wjc.11.2014.06.25.11.43.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Jun 2014 11:43:32 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 21:43:28 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A7B7FA2-51C1-4D90-8AA0-2D9AB11CD787@gmail.com>
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/djXeh-d9nsuIvuILyxkdAVOUn18
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 18:43:36 -0000

On Jun 25, 2014, at 8:23 PM, Martin Rex <mrex@sap.com> wrote:

> Mark Andrews wrote:
>>>=20
>>> Why would any private individual want to get an IPv6 address?
>>> With DHCP IPv4 + NAT (on your Home router) and even more so with =
CGN,
>>> you may have at least a vague chance that your ID doesn't stick out
>>> of every IP datagram like a sore thumb.  With IPv6, you're stripped
>>> naked for traffic analysis by every governmental agency worldwide, =
no matter
>>> how strong you encrypt your traffic.
>>=20
>> Because with CGN, DS-Lite and NAT64 you have a third class IPv4
>> internet.  You can't run any services what so ever.
>=20
> The majority of home users actually do not want and do not need to
> run any service in the first place.

I think it=92s more correct to say that the majority of home users have =
learned to make do without running services.

I have a desktop computer at home with about a terabyte of free disk =
space and a connected printer. That computer can easily run services =
with protocols such as SMTP+IMAP, NFS, IPP and VoIP. In fact, OS vendors =
like Apple and Microsoft could include these services very easily and =
with little need to configure anything.=20

And yet these home users use cloud services for all of these things. =
Why?  Because getting to those home servers is such a hassle when =
they=92re behind NAT. Sure, there are ways to print on my home printer. =
But those ways always boil down to printing to a cloud service, with the =
hope printer occasionally pulling print jobs from the cloud. That=92s an =
awkward way to get around the limitation.

So we=92ve been using Gmail and Gdrive and iCloud and DropBox and a =
bunch or others for so long, that we feel as though that=92s the right =
way for things. It sure is convenient, but it=92s not the only way.

We can speculate about whether cloud services for consumers would have =
taken off if IPv6 had taken off in =9298 and NATs quietly died. I tend =
to think that the risk of losing everything would have led to where we =
are today anyway, at least for mail and file storage. Usable backups =
have only been in mainstream operating system for the last few years. =
It=92s all speculation, but we shouldn=92t assume that consumers would =
not do something else if it was technically feasible.

Yoav


From nobody Wed Jun 25 11:48:59 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D75C1B2E1E for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 11:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level: 
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 WFQjdD4q-mrS for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 11:48:53 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 854BD1B2E1B for <ietf@ietf.org>; Wed, 25 Jun 2014 11:48:53 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s5PImo6Q025078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 20:48:50 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <1938577.jO2gyWluhM@gongo>
To: Niels Dettenbach <nd@syndicat.com>
Date: Wed, 25 Jun 2014 20:48:50 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140625184850.14B901AD68@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pawKh4K9b9jNaPxMvOgs-ntaL9Y
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 18:48:55 -0000

Niels Dettenbach wrote:
>
> Martin Rex:
>>
>> IPv6 privacy addresses are security theater when the network prefix
>> is constant and the number of users sharing the prefix is tiny.
> ...ahh,
> which is 'not' the case with (much) shorter IPv4 network prefixes and (much) 
> smaller address pools?!...

Correct.

AFAIK, to change an IPv6 network prefix in a "fully transparent" home
network, you would have to renumber every machine&device on that network.
So for a DSL subscriber, the network prefix is the size of that
subscriber household, which often is a family or just one single person.


With NAT and a regularly reassigned randomly chosen IPv4-Address on
the WAN interface of your home gateway, you not only get rid of the
entire renumbering crap for the inside of your (home) network,
but you also get blended with many other subscribers of the same ISP
in the perception of everyone else on the internet other than your ISP.

I've just glanced over the IPv4 addresses assigned over the past 4 days.

The "lowest" IP address  was  a.b.4.x
The "highest" IP address was  a.b.118.x

and the other addresses look fairly well distributed between these.


Looking at the past ~50 addresses, I see 3 addresses twice, the other
addresses are unique.


Absolute anonymity doesn't exist.  In the real world, anonymity
means always some form of "blending in a group".  And the larger
that group, the better.


Randomly dynamic DHCP-assigned IPv4 addresses do not _provide_ anonymity,
but static IPv6 network prefixes completely preclude anonymity, and 
therefore completely preclude privacy when the groups size is ~10 or less,
or in the extreme, just a single subscriber/customer.


To get a decent level of privacy, you really want to blend with
1000+ plus other ISP customers, preferably 10000+ or more.


-Martin


From nobody Wed Jun 25 12:04:01 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663781B2E5F for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -112.452
X-Spam-Level: 
X-Spam-Status: No, score=-112.452 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 4NdlvZNWFY58 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:03:54 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146881B2E2A for <ietf@ietf.org>; Wed, 25 Jun 2014 12:03:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5343; q=dns/txt; s=iport; t=1403723034; x=1404932634; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=RgkQO4KwxOVhjtxKSlrarX3nZa1at3ffWUcq1GM6R/A=; b=hrv10cD6FMMEF9xV0Ar0HaRbLdbEtfRs2KCnEvmczdUizUpyl75YwdPm JUUrUL6jK1ZLvKrH6y++bCu0mKQyEn0dMinhZaZPfKwqxc83/J76CdHgI FALHD6BJSrn1J6Sf5Mp8ZtTbOKKWeKZr7RV6cUrDidNiDXJ65VYZ5ymbR k=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAHccq1OtJA2K/2dsb2JhbABZgw1SWsNNAYEOFnWEAwEBAQMBeQULAgEIDjgyJQIEDgUOiCwIDcMjEwSOM0kHgy2BFgWEYwKNI4FBhwiTa4NCgW9B
X-IronPort-AV: E=Sophos;i="5.01,547,1400025600";  d="asc'?scan'208";a="335641647"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-8.cisco.com with ESMTP; 25 Jun 2014 19:03:53 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s5PJ3r55017154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Jun 2014 19:03:53 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.143]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Wed, 25 Jun 2014 14:03:52 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Niels Dettenbach <nd@syndicat.com>
Subject: Re: Time to move beyond the 32 bit Internet.
Thread-Topic: Time to move beyond the 32 bit Internet.
Thread-Index: AQHPj8LAjHuEvda2lU2S80toG+4BrZuBJQqA///IImaAAFa+gP//vXWjgAFnWwCAAAVrAIAAFowA
Date: Wed, 25 Jun 2014 19:03:52 +0000
Message-ID: <13B29AD0-5A69-43D0-BC46-59A7092BD5E4@cisco.com>
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp> <1938577.jO2gyWluhM@gongo>
In-Reply-To: <1938577.jO2gyWluhM@gongo>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_7246DC09-B59E-4D2A-A26A-740652C1FD21"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/m9GqNVQ7zyAhvQ4ZpO1Ge34xpLs
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 19:03:59 -0000

--Apple-Mail=_7246DC09-B59E-4D2A-A26A-740652C1FD21
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jun 25, 2014, at 10:43 AM, Niels Dettenbach <nd@syndicat.com> wrote:

> The fact that most users are not providing services on the net is not =
true at all.

Agreed.

I suppose part of this is the definition of a =93service=94. I think =
it=92s fair to say that your average residential user doesn=92t have the =
kind of service infrastructure in his or her home that an ISP would =
provide. But I think that=92s actually a pretty restrictive definition =
of a "service=94.

To me, networked applications fall into two broad categories: those that =
need an address before a application session opens, and those that have =
no need of an address until the instant an application session opens. =
The latter are obviously clients - the fact that I can readily connect =
from a web browser to a web server through an arbitrarily long sequence =
of NATs says to me that the client=92s address is mostly-irrelevant from =
its perspective, and it could be supplied with an address at the instant =
it decided to create the connection. That=92s not a service, that=92s =
the client of a service.

However, if I need an address to connect to an application on some =
remote device, that remote application is in some sense a service.

Let=92s talk about services that people often do operate from their =
homes.

My daughter has had a couple o break-ins, and lives in a neighborhood =
that has had trouble with that. It=92s not a =93bad=94 neighborhood, but =
police cruisers seem to spend their time in more upscale neighborhoods =
or the business parts of her town, so her neighborhood has had trouble. =
I installed a surveillance system for her. One of the really nice things =
is that the computer in her home can use Dynamic DNS to enable and =
application on her phone or laptop to access the current camera or =
stored footage from somewhere else. There are several systems that allow =
that. https://www.google.com/search?q=3Dsurveillance+dynamic+dns. It =
works through a NAT by configuring the NAT appropriately. In her case, =
however, she has the NAT in her router and a NAT somewhere upstream (in =
her modem, probably, or perhaps CGN if the provider is using that), so =
that the service doesn=92t actually WORK. IPv6 would solve that issue =
cold, although it would perhaps highlight security issues (so who is =
looking at her surveillance footage?).

And then there are things on one=92s phone or notebook. Think Skype, =
FaceTime, Voice/Video in general, gaming, photo exchange, p2p-anything. =
These services today have large infrastructure =93in the cloud=94, =
because NATs pretty much force the thing in the home to be a client of =
something somewhere else. However, that has some direct impacts - if =
every user has the option of sending at mumble kbps or mbps, the cloud =
infrastructure has to be able to receive at that rate and retransmit to =
one or more other users at that rate. Count noses, and then say =93MBPS=94=
.=20

Now, imagine a different model. Your membership in, say, =
Skype-or-whatever gives you the opportunity to ask a server somewhere =
=93what address is my buddy at right now=94, or perhaps =93buddies". The =
infrastructure cost drops like a rock, and connections between users of =
the service become direct. Did you say that, maybe, privacy was =
important and you wanted to =93go dark=94? OK, encrypt the session and =
give only your buddy the key. Skype wants to deploy a service in which a =
client can share with an arbitrary number of buddies simultaneously? =
Hey, if you have the bandwidth, whatever, Skype simply gives you the =
addresses of several buddies. So these things in which a system in a =
house has to be a client of some kind of expensive infrastructure =
suddenly become SERVICES in the sense that they have an address when =
someone needs to connect to them, and one connection goes end to end.

A classic example of that is Free=92s IPv6 video service. I don=92t live =
in France and I haven=92t used it, so I=92m propagating hear-say here. =
But as I understand it, it is a lot like youtube, but the rotating =
storage is provided by the Free subscribers that share videos using it, =
at no cost to Free.

If the defining characteristic of a service is that someone ELSE =
connects to IT when THEY decide to do so, I think you will find that the =
typical residential user runs services all the time, and they would work =
at least as well and probably better without the middleware. They just =
don=92t know it, and they depend on some pretty heavy-duty stuff =93in =
the cloud=94 to make it possible.

--Apple-Mail=_7246DC09-B59E-4D2A-A26A-740652C1FD21
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFTqx0WbjEdbHIsm0MRAipdAJ44a4NVoNYIuwN1ZyLPbVTQD0kOVwCfQLVT
znLQBYCgG5hCLSMVppTqDxY=
=/PsW
-----END PGP SIGNATURE-----

--Apple-Mail=_7246DC09-B59E-4D2A-A26A-740652C1FD21--


From nobody Wed Jun 25 12:26:57 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D8E1B2E49 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level: 
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 YNDAWFoaw7qh for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:26:53 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E440F1B2E46 for <ietf@ietf.org>; Wed, 25 Jun 2014 12:26:52 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id nu7so2681873obb.16 for <ietf@ietf.org>; Wed, 25 Jun 2014 12:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bBy1QqXH43nvGsLtw6nKp+siFcOnqbezkWs366BJjy4=; b=Jmog6xhCnPwam6tAPXtgGiA+/ZwBDBxZWb4Ha/N3sF07IWHkV+55i1gN66t/v4pgub MjLQZtmjOPEhdu5qENS24MMjvhC1+pixuntFMgmPIqKWPAdoKBfrOwEZ7BYoAar/x85f PpXAqqO05b9GtxB95nhdlrSvdf0D55wPlGUpQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bBy1QqXH43nvGsLtw6nKp+siFcOnqbezkWs366BJjy4=; b=jAeTKopXylgKNCFUtefC9uOrEI7lcah8hanhycFtSZNTRrySOKZQBPiMPzytIJTKfC 5EoJUmy4T25lvTFPcweD9v6H7f0/OGWFhPdCJvplBClbYdaHEPVKcFZqpxqyg7zz8NGo dPgs9cymj66K8rsb69MGkZOUCy6kuLMAHt4kfj6xmMLPkKKNMzUGD0e73DyVB+URo1zL IAVuue5k5oKwNYdzval/p+DvVUKGO804mlvM4xnC7/5sEHxNz0g8SUbp/6DoZ2s00TxL 8dPQwl3sJxHSoTzD6iORfqnDd2Yu2Wd08+qD+0ruw/hrCKE+aUSsK7qGw6PRbt6QHgni 4lMA==
X-Gm-Message-State: ALoCoQl1rRsQ5wqJqoLZQbqpIp3ONhpMTM0Uw1bBE+3yw5J8dZa8q8jzthlV3MFz4DM0/j1qL2MG
MIME-Version: 1.0
X-Received: by 10.60.146.167 with SMTP id td7mr10426894oeb.6.1403724412134; Wed, 25 Jun 2014 12:26:52 -0700 (PDT)
Received: by 10.60.60.100 with HTTP; Wed, 25 Jun 2014 12:26:52 -0700 (PDT)
In-Reply-To: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
References: <20140625005627.2DCAC19400A7@rock.dv.isc.org> <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 20:26:52 +0100
Message-ID: <CAKHUCzyxwhakE0cEFi9q54eSKGNZ2kr6tBeg2dA2PBUCc6kaVw@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Dave Cridland <dave@cridland.net>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=047d7b5d376cf2eefe04fcae0e39
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xqgYpzdcEhew2Y62A9XvXryusGc
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 19:26:54 -0000

--047d7b5d376cf2eefe04fcae0e39
Content-Type: text/plain; charset=UTF-8

On 25 June 2014 18:23, Martin Rex <mrex@sap.com> wrote:

> The majority of home users actually do not want and do not need to
> run any service in the first place.
>

You're surely joking?

Let's assume that by "service" you actually meant "service accessible to
anywhere on the internet", because it's just silly to assume you might have
meant internal services.

There's a fairly large number of devices sold with the explicit feature
that they have a [horrendously complex] mechanism by which they're
reachable from the outside world.

The Western Digital NAS I have sitting on a bookshelf in my office is one
such, as is the HP printer behind me. There are various digital TV set-top
boxes that are able to be programmed to record from outside the consumer's
network, too.

These aren't obscure undocumented features; these are headline USPs.

They're not *public* services, of course, but they're certainly services in
every meaningful technical sense, and they're all reliant on weird hacks,
proxy services, and so on. IPv6 instantly makes these simpler for
developers and users.

Dave.

--047d7b5d376cf2eefe04fcae0e39
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
5 June 2014 18:23, Martin Rex <span dir=3D"ltr">&lt;<a href=3D"mailto:mrex@=
sap.com" target=3D"_blank">mrex@sap.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<div class=3D"">The majority of home users actually do not want and do not =
need to<br></div>
run any service in the first place.<br></blockquote><div><br></div><div>You=
&#39;re surely joking?</div><div><br></div><div>Let&#39;s assume that by &q=
uot;service&quot; you actually meant &quot;service accessible to anywhere o=
n the internet&quot;, because it&#39;s just silly to assume you might have =
meant internal services.</div>
<div><br></div><div>There&#39;s a fairly large number of devices sold with =
the explicit feature that they have a [horrendously complex] mechanism by w=
hich they&#39;re reachable from the outside world.</div><div><br></div>
<div>The Western Digital NAS I have sitting on a bookshelf in my office is =
one such, as is the HP printer behind me. There are various digital TV set-=
top boxes that are able to be programmed to record from outside the consume=
r&#39;s network, too.<br>
</div><div><br></div><div>These aren&#39;t obscure undocumented features; t=
hese are headline USPs.</div><div><br></div><div>They&#39;re not *public* s=
ervices, of course, but they&#39;re certainly services in every meaningful =
technical sense, and they&#39;re all reliant on weird hacks, proxy services=
, and so on. IPv6 instantly makes these simpler for developers and users.</=
div>
<div><br></div><div>Dave.</div></div></div></div>

--047d7b5d376cf2eefe04fcae0e39--


From nobody Wed Jun 25 12:52:46 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9DB1B2E7D for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.299
X-Spam-Level: 
X-Spam-Status: No, score=-99.299 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 iDAW2h6eqKaw for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 12:52:26 -0700 (PDT)
Received: from ntbbs.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1B5301B2E7A for <ietf@ietf.org>; Wed, 25 Jun 2014 12:52:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6955; t=1403725938; h=Received:Received: Message-Id:From:Subject:Date:To:Organization:List-ID; bh=rGeyR2o 4L4xTC7cYO3OvthCSIL0=; b=j9Cfcb0U/Rix2YgIZ34VskqUZGJMFmXnRrtOnTR c/9voeqpK0nJPwf4DmN3fz0B0ENDH/E6LIINa2DBzs2j2bDpCCBKaLzHH5xMR1d8 3i+J9GPJd95RM0+HjZ+GNYYNJGyYXYHAoR9sK39+qsRaqeerQcmDwFTHTOTeFf55 I9r0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 25 Jun 2014 15:52:18 -0400
Received: from [192.168.1.221] (99-72-160-212.lightspeed.miamfl.sbcglobal.net [99.72.160.212]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3206045811.1.3628; Wed, 25 Jun 2014 15:52:17 -0400
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <69B9BA3779753A49865BB9010D560EBB7020@newserver.arneill-py.local> <CAMm+LwhLbvZoR1L=R3XR6kCvqnWp2OpdTFhdXSi-D9zyuv_CFA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAMm+LwhLbvZoR1L=R3XR6kCvqnWp2OpdTFhdXSi-D9zyuv_CFA@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-6EE4ED0D-8231-4248-8D34-06485AA039DF
Content-Transfer-Encoding: 7bit
Message-Id: <280F3993-F4DD-43FA-A14A-D44DFD0EEDFD@isdg.net>
X-Mailer: iPad Mail (11B651)
From: Hector Santos <hsantos@isdg.net>
Subject: Re: Time to move beyond the 32 bit Internet.
Date: Wed, 25 Jun 2014 15:52:14 -0400
To: Phillip Hallam-Baker <phill@hallambaker.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Xb1gKY8GG1d3QUXGWF_-HVjLbGU
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 19:52:33 -0000

--Apple-Mail-6EE4ED0D-8231-4248-8D34-06485AA039DF
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Phillip, I still deal in a RS232 dial up market that is "mission critical" a=
t every segment of the market place; from the hobbyist to mom&pop, to small t=
o large commercial and government, level operational communications needs.  =
 Change is slow and as long as it remains cost effective and automatic with l=
ow support needs, etc, it's going to take a long time to dismantle the long t=
ime established infrastructure.

I do feel there needs to be better education, not for the end-user, but for t=
he communications market engineers, people like myself, those that develop a=
nd maintain the unified virtual communications applications.  We also need f=
unding and grants to assist with the migration.  But in all honesty, their r=
eally hasn't been any market pressure to change and I doubt the ISP is going=
 to take a chance with tortious interference lawsuits by long time well esta=
blishment businesses.

I do agree the NAT should of been used as a carrot toward ipv6 in the same w=
ay i feel author domain policy should be used as a DKIM carrot to help estab=
lish a non-existing 3rd party trust market.  =20

--
Hector Santos
http://www.santronics.com

> On Jun 25, 2014, at 8:26 AM, Phillip Hallam-Baker <phill@hallambaker.com> w=
rote:
>=20
>> On Wed, Jun 25, 2014 at 12:28 AM, Michel Py <michel@arneill-py.sacramento=
.ca.us> wrote:
>> > Phillip Hallam-Baker wrote :
>> > So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is your=
 Internet service 32 bit or 128'?
>>=20
>> Creative. Since freeIPv6porn.com this is the definitely one of the best m=
arketing attempts that I can remember.
>>=20
>> However, I would be concerned that deciders who would be tempted by that p=
ick-up line had been earlier adopters of 64-bit OS and found 64-bit drivers f=
or their existing peripherals (or the lack, thereof) disturbing.
>=20
> Actually, that is part of the message.
>=20
> Going to IPv6 is not easy or inexpensive. And one of the reasons that is t=
he case is that there has been an assumption that it will 'just happen' and t=
hat there is no need to consider bridge technologies.
>=20
> People literally laughed at me when I said that we needed to embrace NAT t=
o deploy IPv6. Today there are very few people who don't get the reasons why=
. But if you look at the efforts O/S vendors had to go through to get to 64 b=
its, NAT is a minor carbuncle in comparison. The way a 64 bit O/S runs a 32 b=
it program is not pretty.=20
>=20
>=20
>>=20
>> > Actually IPv6 is a 64 bit Internet, not 128 bits.
>>=20
>> Better to forget that and try to sell it as 128 bits, as nobody else has b=
een burned but that number yet.
>=20
> I think it would sound like twice the pain.
>=20
>=20

--Apple-Mail-6EE4ED0D-8231-4248-8D34-06485AA039DF
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Phillip, I still deal in a RS232 dial u=
p market that is "mission critical" at every segment of the market place; fr=
om the hobbyist to mom&amp;pop, to small to large commercial and government,=
 level operational communications needs. &nbsp; Change is slow and as long a=
s it remains cost effective and automatic with low support needs, etc, it's g=
oing to take a long time to dismantle the long time established infrastructu=
re.</div><div><br></div><div>I do feel there needs to be better education, n=
ot for the end-user, but for the communications market engineers, people lik=
e myself, those that develop and maintain the unified virtual communications=
 applications. &nbsp;We also need funding and grants to assist with the migr=
ation. &nbsp;But in all honesty, their really hasn't been any market pressur=
e to change and I doubt the ISP is going to take a chance with tortious inte=
rference lawsuits by long time well establishment businesses.</div><div><br>=
</div><div>I do agree the NAT should of been used as a carrot toward ipv6 in=
 the same way i feel author domain policy should be used as a DKIM carrot to=
 help establish a non-existing 3rd party trust market. &nbsp;&nbsp;</div><di=
v><br>--<div>Hector Santos</div><div><a href=3D"http://www.santronics.com">h=
ttp://www.santronics.com</a></div></div><div><br>On Jun 25, 2014, at 8:26 AM=
, Phillip Hallam-Baker &lt;<a href=3D"mailto:phill@hallambaker.com">phill@ha=
llambaker.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><di=
v dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Wed, J=
un 25, 2014 at 12:28 AM, Michel Py <span dir=3D"ltr">&lt;<a href=3D"mailto:m=
ichel@arneill-py.sacramento.ca.us" target=3D"_blank">michel@arneill-py.sacra=
mento.ca.us</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">&gt; Phillip Hallam-Baker wrote :<br>
<div class=3D"">&gt; So lets stop asking ISPs 'do you support IPv6' and inst=
ead ask 'Is your Internet service 32 bit or 128'?<br>
<br>
</div>Creative. Since <a href=3D"http://freeIPv6porn.com">freeIPv6porn.com</=
a> this is the definitely one of the best marketing attempts that I can reme=
mber.<br>
<br>
However, I would be concerned that deciders who would be tempted by that pic=
k-up line had been earlier adopters of 64-bit OS and found 64-bit drivers fo=
r their existing peripherals (or the lack, thereof) disturbing.<br></blockqu=
ote>
<div><br></div><div>Actually, that is part of the message.</div><div><br></d=
iv><div>Going to IPv6 is not easy or inexpensive. And one of the reasons tha=
t is the case is that there has been an assumption that it will 'just happen=
' and that there is no need to consider bridge technologies.</div>
<div><br></div><div>People literally laughed at me when I said that we neede=
d to embrace NAT to deploy IPv6. Today there are very few people who don't g=
et the reasons why. But if you look at the efforts O/S vendors had to go thr=
ough to get to 64 bits, NAT is a minor carbuncle in comparison. The way a 64=
 bit O/S runs a 32 bit program is not pretty.&nbsp;</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"">=
<br>
&gt; Actually IPv6 is a 64 bit Internet, not 128 bits.<br>
<br>
</div>Better to forget that and try to sell it as 128 bits, as nobody else h=
as been burned but that number yet.<br></blockquote><div><br></div><div>I th=
ink it would sound like twice the pain.</div><div><br></div><div><br>
</div></div></div></div>
</div></blockquote></body></html>=

--Apple-Mail-6EE4ED0D-8231-4248-8D34-06485AA039DF--


From nobody Wed Jun 25 13:50:51 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D05471A03C2 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 vPUcii7Nqol5 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:50:45 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F4FB1A03BC for <ietf@ietf.org>; Wed, 25 Jun 2014 13:50:45 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s5PKocOM007710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Jun 2014 22:50:39 +0200 (MEST)
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <CAKHUCzyxwhakE0cEFi9q54eSKGNZ2kr6tBeg2dA2PBUCc6kaVw@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Date: Wed, 25 Jun 2014 22:50:38 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140625205038.D0A0E1AD69@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MK3nXtnpzQh4cjmXegnUayI2NWY
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 20:50:48 -0000

Dave Cridland wrote:
> Martin Rex <mrex@sap.com> wrote:
> 
>> The majority of home users actually do not want and do not need to
>> run any service in the first place.
> 
> You're surely joking?

Nope, I'm dead serious.


> 
> Let's assume that by "service" you actually meant "service accessible to
> anywhere on the internet", because it's just silly to assume you might have
> meant internal services.

Correct.  "Services" attached to the home network and accessed from
within the home network don't care about the IPv4 address on the
WAN interface of your home gateway.

They would have to care about changing network prefixes of a home gateway
that provided end-to-end transparent IPv6, on the other hand, and that
would be a real nightmare.


> 
> There's a fairly large number of devices sold with the explicit feature
> that they have a [horrendously complex] mechanism by which they're
> reachable from the outside world.
> 
> The Western Digital NAS I have sitting on a bookshelf in my office is one
> such, as is the HP printer behind me. There are various digital TV set-top
> boxes that are able to be programmed to record from outside the consumer's
> network, too.

While that might be true, the security of most of these devices is
so ridiculously lame (read _not_ there), that *EVERYONE* is better
off when few to none of these ever become transparently accessible
from the internet.  And for those devices that aren't huge gaping
security problem as shipped, they *ALL* turn into one within a few months.


> 
> These aren't obscure undocumented features; these are headline USPs.

Pretty much all of them are irresponsible features from a product safety
perspective, and NAT is probably the best (and by far most important) thing
that happened to the internet after the invention of the World Wide Web.


> 
> They're not *public* services, of course, but they're certainly services in
> every meaningful technical sense, and they're all reliant on weird hacks,
> proxy services, and so on. IPv6 instantly makes these simpler for
> developers and users.

If the equipment running these services were transparently accessible
from the internet by default, then the vast majority of them would also
be publicly accessible without the owners consent and probably without
the owners knowlegde.


-Martin


From nobody Wed Jun 25 13:55:17 2014
Return-Path: <nd@syndicat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E38501A03E8 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 V7mrHoUXpl61 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:55:05 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 282981A037D for <ietf@ietf.org>; Wed, 25 Jun 2014 13:55:05 -0700 (PDT)
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 10.04_1-PostHamster) (envelope-from <nd@syndicat.com>) id 1WzuDf-00006X-LS for ietf@ietf.org; Wed, 25 Jun 2014 22:55:03 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2pdjwy10eKq for <ietf@ietf.org>; Wed, 25 Jun 2014 22:55:03 +0200 (CEST)
Received: from p5dc3e27f.dip0.t-ipconnect.de ([93.195.226.127] helo=[10.1.1.18]) by mail.syndicat.com with esmtpsa (TLSv1:AES128-SHA:128) (Syndicat.com PostHamster 10.04_1-PostHamster) (envelope-from <nd@syndicat.com>) id 1WzuDf-0002Cm-9C for ietf@ietf.org; Wed, 25 Jun 2014 22:55:03 +0200
From: "Niels Dettenbach (Syndicat.com)" <nd@syndicat.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6C64C54E-7B53-48F5-BBDF-FB39AE65842C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <B7CC4E9B-6C24-4991-A0B9-D4AB7EF0F000@syndicat.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Time to move beyond the 32 bit Internet.
Date: Wed, 25 Jun 2014 22:55:00 +0200
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp> <1938577.jO2gyWluhM@gongo> <13B29AD0-5A69-43D0-BC46-59A7092BD5E4@cisco.com>
To: ietf@ietf.org
In-Reply-To: <13B29AD0-5A69-43D0-BC46-59A7092BD5E4@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NvujH3UGndWS8s0Dlk9JB2rPkxM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 20:55:08 -0000

--Apple-Mail=_6C64C54E-7B53-48F5-BBDF-FB39AE65842C
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E5291889-03BC-4190-9D9C-FA1268F18BC1"


--Apple-Mail=_E5291889-03BC-4190-9D9C-FA1268F18BC1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


Am 25.06.2014 um 21:03 schrieb Fred Baker (fred) <fred@cisco.com>:

> I suppose part of this is the definition of a =93service=94. I think =
it=92s fair to say that your average residential user doesn=92t have the =
kind of service infrastructure in his or her home that an ISP would =
provide. But I think that=92s actually a pretty restrictive definition =
of a "service=94.

You=92re thinking in that old fashion i described.

As i wrote i.e. Skype and TeamViewer ARE products who show that even =
many (or most?) end users STILL want to provide IP services to the =
public network in any way.=20

By fact, these =84i want to offer IP services from home sometimes =
solutions=93 are much more insecure by structure and principle than =
anything i can imagine today - they require a perforated =84Firewall=93 =
and full access of a third party as super user into their own networks.=20=


NAT is no workaround for a bad configured firewall or similar.


cheerioh,


Niels.
=97
Syndicat IT & Internet
Gosslerstr. 34, Goettingen, DE
http://www.syndicat.com

--Apple-Mail=_E5291889-03BC-4190-9D9C-FA1268F18BC1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>Am 25.06.2014 um 21:03 schrieb Fred =
Baker (fred) &lt;<a =
href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&gt;:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;">I suppose part of this is the definition of a =93service=94. =
I think it=92s fair to say that your average residential user doesn=92t =
have the kind of service infrastructure in his or her home that an ISP =
would provide. But I think that=92s actually a pretty restrictive =
definition of a "service=94.</span></blockquote></div><br><div>You=92re =
thinking in that old fashion i described.</div><div><br></div><div>As i =
wrote i.e. Skype and TeamViewer ARE products who show that even many (or =
most?) end users STILL want to provide IP services to the public network =
in any way.&nbsp;</div><div><br></div><div>By fact, these =84i want to =
offer IP services from home sometimes solutions=93 are much more =
insecure by structure and principle than anything i can imagine today - =
they require a perforated =84Firewall=93 and full access of a third =
party as super user into their own =
networks.&nbsp;</div><div><br></div><div>NAT is no workaround for a bad =
configured firewall or =
similar.</div><div><br></div><div><br></div><div>cheerioh,</div><div><br><=
/div><div><br></div><div>Niels.</div><div>=97</div><div>Syndicat IT =
&amp; Internet</div><div>Gosslerstr. 34, Goettingen, DE</div><div><a =
href=3D"http://www.syndicat.com">http://www.syndicat.com</a></div></body><=
/html>=

--Apple-Mail=_E5291889-03BC-4190-9D9C-FA1268F18BC1--

--Apple-Mail=_6C64C54E-7B53-48F5-BBDF-FB39AE65842C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJTqzckAAoJEM78prARigUnyfcQAJ4aG/yvYXfjmaKRC0dpNtdm
H0XHaSTQG5Jky4e1t+PfNssjSbEVJ6T5SVD0lpOlr8lMLk99j3eEOXompt8WrxL9
WcM+R9mzlYUeEnsaRUH54UHPMu9+BbYpM4fdHlgMKDcndFb/gowe1M5qUbzMfCYf
A8eMsrg1Kl2T9tEDmMGy/lp7wrAkKrNc83p/MZdrrHKCOem0YdfRJSSSWfelRfz9
fHZ8n10zPPiJ/679Zdcy8rOWu+rrAXXiKZ2kD/3vn56/AQyrCpmLKgHZKD6smGNr
e1OzTaAwhzgrSOeCaMUYxzVAeXbZnY9FUn4EGfdw+J5GJkRTgsM1MG0Q2wHdc+Aj
I1YxTJYo+q72S0LMcV4jaYC3oQI06goCN3YONq0bXR5T9Wv/1cNrtAshFP5O6Z03
S3N3PCR1vrnKe8+/iplunIK3NnmV7WE8WiI9zYADPJgVnZIKc8ZutxA21l4MKGxh
n97idGPZNYMfSCWGPC6I+indK/d2qVZutrT4QFFBVZQmDvUkAPzy+d1sqToQtptQ
kXJkf6hYvZV4mrNYYF4iRfe5ZAz9EPPdZ4PaJgB4RONmV3zawjURWLWkY5FT5CV0
f6AFkraFRdOxWmT0QD0IYFCVcPaRfazdn/QNeKiODZV55DhWKbSWVZUXTEv2dfUO
Skwpdyn0Q6dZAYM0ft2A
=UzVc
-----END PGP SIGNATURE-----

--Apple-Mail=_6C64C54E-7B53-48F5-BBDF-FB39AE65842C--


From nobody Wed Jun 25 13:56:49 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104D21A037D for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 BJpgk8wWUhXx for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 13:56:46 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2108F1A03C5 for <ietf@ietf.org>; Wed, 25 Jun 2014 13:56:46 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id n16so2794368oag.23 for <ietf@ietf.org>; Wed, 25 Jun 2014 13:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vmy9fB5IXTMhgtBW0cCnbi3jn79Ax5kWXrZKAZ+pJFw=; b=E8z5JzFlEtmb1in5Cscx8Empg0AVQUliEQXiJJMyu8aVEOFTHx9QC2LG1uvs2O8b9j 58e7coZEhVXOvH5m+lxCmX+j1fXJjSmUZ/y/PXAUx2VL90UDDmQbihndP2ve42F2MURl hDK6px2pLeKOPec19B2eUv+z59GWd48CHv/2k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vmy9fB5IXTMhgtBW0cCnbi3jn79Ax5kWXrZKAZ+pJFw=; b=ILc/4N+801Jc5Moci5Fnenyw5JWFFmzv+lvR0TxNzWxMx1wLZJo0+O9SM4x/YxZPFs ylyi3QjSuj4iiL7AziIjuBW5RxiAoosrVojXphP0K6D4mbrlk0pHz4vX6EraObcVmC+h KIOq02u/2L7GWKBPGF89QcuynErUR4rbHoGnT3qeXp9/IDPoO3zt2LPReFrLtB1CuM4p 91xiq3cUdlaZc7s28UH5efbhfv0sjGpu/+tOwjQGZFxYZ5lEekF8pbGCxiECJ1TMrPEt PVI3g/56tTakurSLlN0nYGUg7sSjzMKI8oUjGpJ3o0Gb3W+ON42alnIhyPZmI4UkCtNv 6Pig==
X-Gm-Message-State: ALoCoQmz7lMzQmT5/KS3L88a01Q8be9G3eqTs/XfFt1Qe3RKw8YDmj6cs05ORLFM5+4g5vc+B9xs
MIME-Version: 1.0
X-Received: by 10.182.211.99 with SMTP id nb3mr10981836obc.40.1403729805487; Wed, 25 Jun 2014 13:56:45 -0700 (PDT)
Received: by 10.60.60.100 with HTTP; Wed, 25 Jun 2014 13:56:45 -0700 (PDT)
In-Reply-To: <20140625205038.D0A0E1AD69@ld9781.wdf.sap.corp>
References: <CAKHUCzyxwhakE0cEFi9q54eSKGNZ2kr6tBeg2dA2PBUCc6kaVw@mail.gmail.com> <20140625205038.D0A0E1AD69@ld9781.wdf.sap.corp>
Date: Wed, 25 Jun 2014 21:56:45 +0100
Message-ID: <CAKHUCzwBVww6Rv7wmcCfCSTsHiNiOd6acwLHhwXpYmpYZ7WXbA@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Dave Cridland <dave@cridland.net>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=e89a8f503b826af41f04fcaf50c5
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wCm1oqIbQz29Vp5cmxrZwZGQHsc
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 20:56:47 -0000

--e89a8f503b826af41f04fcaf50c5
Content-Type: text/plain; charset=UTF-8

On 25 June 2014 21:50, Martin Rex <mrex@sap.com> wrote:

> Dave Cridland wrote:
> > Martin Rex <mrex@sap.com> wrote:
> >
> >> The majority of home users actually do not want and do not need to
> >> run any service in the first place.
> >
> > You're surely joking?
>
> Nope, I'm dead serious.
>
>
Well, you prove yourself wrong in your own email. These things exist, and
are sold, and are run, all of which you agree with. You should have opted
to claim a failed joke while you had the chance.

You might think users shouldn't be allowed to run such things, but the fact
is they do want to, and they certainly think they need to.

Your opinion of whether this is acceptable behaviour on behalf of the
proletariat is entirely irrelevant.

Dave.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
5 June 2014 21:50, Martin Rex <span dir=3D"ltr">&lt;<a href=3D"mailto:mrex@=
sap.com" target=3D"_blank">mrex@sap.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<div class=3D"">Dave Cridland wrote:<br>
&gt; Martin Rex &lt;<a href=3D"mailto:mrex@sap.com">mrex@sap.com</a>&gt; wr=
ote:<br>
&gt;<br>
&gt;&gt; The majority of home users actually do not want and do not need to=
<br>
&gt;&gt; run any service in the first place.<br>
&gt;<br>
&gt; You&#39;re surely joking?<br>
<br>
</div>Nope, I&#39;m dead serious.<br>
<div class=3D""><br></div></blockquote><div><br></div><div>Well, you prove =
yourself wrong in your own email. These things exist, and are sold, and are=
 run, all of which you agree with. You should have opted to claim a failed =
joke while you had the chance.</div>
<div><br></div><div>You might think users shouldn&#39;t be allowed to run s=
uch things, but the fact is they do want to, and they certainly think they =
need to.</div><div><br></div><div>Your opinion of whether this is acceptabl=
e behaviour on behalf of the proletariat is entirely irrelevant.</div>
<div><br></div><div>Dave.</div></div></div></div>

--e89a8f503b826af41f04fcaf50c5--


From nobody Wed Jun 25 14:42:34 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3FD1A0054 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 14:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.151
X-Spam-Level: 
X-Spam-Status: No, score=-1.151 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Owg4pYaeQxqm for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 14:42:31 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEECA1A0384 for <ietf@ietf.org>; Wed, 25 Jun 2014 14:42:30 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WzuxY-0006O9-Fy; Wed, 25 Jun 2014 21:42:29 +0000
Date: Thu, 26 Jun 2014 06:42:28 +0900
Message-ID: <m2pphwfyyj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Niels Dettenbach <nd@syndicat.com>
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <1938577.jO2gyWluhM@gongo>
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp> <1938577.jO2gyWluhM@gongo>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Rc2jTzUkaJkpjNOZS71uLL9EsyE
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 21:42:32 -0000

> The fact that most users are not providing services on the net is not
> true at all.

making it difficult for the end user to provide services is a dangerous
disfunction, the consumer-only couch potato intertnet.  we should strive
for a world where the user can control and publish their own data, not
be forced by isp edge policies and technologues into being owned by the
googles.

[ my edge router in hawi is an openwrt, and time warner will not even
  let me https or ssh to maintain it from the outside, e.g. to install
  security updates.  this is badly broken. ]

in the IoT, this will force the home user to be owned by the IoT device
providers with schemes where the devices have to 'call' their original
manufacturers to rendezvous.

randy


From nobody Wed Jun 25 15:08:53 2014
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A8AB1A0641 for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 15:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.658
X-Spam-Level: **
X-Spam-Status: No, score=2.658 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651] autolearn=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 TILgZa_I4rJq for <ietf@ietfa.amsl.com>; Wed, 25 Jun 2014 15:08:47 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E11261B27A0 for <ietf@ietf.org>; Wed, 25 Jun 2014 15:08:44 -0700 (PDT)
Received: (qmail 10457 invoked from network); 25 Jun 2014 22:00:05 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 25 Jun 2014 22:00:05 -0000
Message-ID: <53AB4868.1060307@necom830.hpcl.titech.ac.jp>
Date: Thu, 26 Jun 2014 07:08:40 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Time to move beyond the 32 bit Internet.
References: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
In-Reply-To: <20140625172344.C91BD1AD68@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/caPz4HqomP1cmJ_mvJmqPGTVFOY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 22:08:51 -0000

Martin Rex wrote:

> The majority of home users actually do not want and do not need to
> run any service in the first place.

Joining peer to peer service means simultaneously acting as a
server and a client of the service.

						Masataka Ohta


From nobody Thu Jun 26 09:04:23 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1ACA1B2D4A; Thu, 26 Jun 2014 09:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 4GN69Mzk1FaP; Thu, 26 Jun 2014 09:04:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC261B2D94; Thu, 26 Jun 2014 08:08:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A157C2CEE0; Thu, 26 Jun 2014 18:08:42 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
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 1VJ30_nJKkji; Thu, 26 Jun 2014 18:08:38 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D79F12CEDE; Thu, 26 Jun 2014 18:08:37 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: [v6ops] Gen-art LC review: draft-ietf-v6ops-enterprise-incremental-ipv6-05
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5390BE61.4050407@nostrum.com>
Date: Thu, 26 Jun 2014 16:08:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8AF3C2D9-22C3-4FE1-9EBE-40BB8F9A6628@piuha.net>
References: <5390BE61.4050407@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WzTmmBMmSMtS2rBtl5PEHeRs9p4
Cc: v6ops@ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-v6ops-enterprise-incremental-v6@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 16:04:16 -0000

Thank you Robert for your (once again) in-depth review. But I have a =
question - was there a response to the comments? My e-mail system does =
not show one, but maybe I missed it.

Jari

On 05 Jun 2014, at 20:00, Robert Sparks <rjsparks@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-v6ops-enterprise-incremental-ipv6-05
> Reviewer: Robert Sparks
> Review Date: 5 June 2014
> IETF LC End Date: 9 June 2014
> IESG Telechat date: not yet scheduled
>=20
> Summary: This draft is basically ready for publication as an =
Informational RFC,
> but has nits that should be considered before publication.
>=20
> I had a mixed overall impression after my first read-through of this =
draft.
>=20
> Overall, the list of issues to consider, and the compendium of =
references is very useful, but there are large stretches of text that =
really aren't helping the reader, and they make the good stuff harder to =
see.
>=20
> I encourage the group to take one more editorial pass, focusing on =
removing as much text as possible without losing the message.
>=20
> Please help the IESG and the RFC-Editor out: the shepherd's writeup =
should say something about why deviating from the style guide's =
restriction on number of authors is is appropriate for this document.
>=20
> Here are specific nits to consider in document order:
>=20
> The first paragraph of section 1.3 starts talking about phases as if =
they've already been described. As written, it says that beginning with =
the External Phase is recommended in RFC5211. But the words "External =
Phase" do not appear in 5211, and its not clear on a quick read exactly =
what in 5211 you were hoping to point out here.  Please introduce the =
phases before this point, and change the callout to 5211 to make it more =
clear how what 5211 is saying ties into this document.
>=20
> Why is "Other Phases" capitalized in 2.1? The number of phases defined =
in this document is small - I suspect this text is older and left room =
for the group to decide to define more phases. Consider just listing =
what you ended up with explicitly.
>=20
> Section 2.1 contains sentences like "The project manager will need to =
spend some time on planning." That is obvious, and you've already =
established that planning needs to happen. This paragraph (perhaps much =
of this section) would be improved by removing as much text as you can. =
It already speaks mostly in terms of the benefits of planning. Making =
that a more explicit goal in the writing structure would help identify =
what can be taken away without losing the message. Overall, trying to =
describe what good project management entails is a bit out of place. =
Perhaps you should just say "This requires good project management =
skills"?
>=20
> In 2.2.2 you say "Applications should be made to use APIs". That seems =
an odd construct for an IETF document. Perhaps you could observe, rather =
than command, here? Would saying something like "Applications that use =
APIs to hide the specifics ... will be easier to take through the =
migration" make the point?
>=20
> In 2.3, why do you need the hyperbole in "IPv6 adoption will be a =
multifacted undertaking that will touch everyone in the organization =
unlike almost any other project."? How does the "unlike almost any other =
project" help the reader?
>=20
> In 2.4.1, please rephrase "pretty much like". Are there any =
differences in the use of IPSec dependent on the address family that are =
important to call out? If not, why doesn't this say "the same as in"?
>=20
> Section 2.4.2: As written, this says Etc. is an attack. Please change =
the introduction to the list to say "for example" or "in particular" and =
remove the Etc. If the point was to cause the reader to think about =
attacks beyond these listed, say that explicitly.
>=20
> The 6th paragraph of 2.6 states the problem is "how to get host DNS =
records updated." The text in the rest of the paragraph only addresses =
this by implication. It looks more like the general discussion of SLAAC =
vs DHCPv6 instead of straightforwardly noting that a DHCPv6 server can =
be made to update DNS records.
>=20
> The reference to RFC6866 in paragraph 7 of section 2.6 is unclear - =
what was it trying to point out?  I think the last sentence was trying =
to say 'static address assignment (even if achieved with DHCP) is =
usually used' where it currently says 'SLAAC is rarely used'?
>=20
> Section 3: The second paragraph doesn't add anything to the document.
>=20
> Section 3.1 paragraph 2: I don't understand why the paragraph ends =
with "which is an important consideration". Can you delete the phrase =
without losing the message? If not, say why an enterprise would care =
whether or not _other_ enterprises had already deployed using BGP on =
their own.
>=20
> Section 3.1 paragraph 4 : "will prefer to use" is out of place. =
Perhaps this should be stated as "will likely get better results using"?
>=20
> Section 3.1 paragraph 5: Can you add a reference to a discussion of =
how keeping the MTU congruent simplifies operations?
>=20
> In section 3.2 consider using the names from 4890 in the list ('Packet =
Too Big' rather than 'Unreachable packet-to-big')
>=20
> Please check whether the sentence "To be fully compliant with =
[RFC5095], all packets containing the routing extension header type 0 =
must be dropped." is perhaps too simple a description of 5095? Does =
context keep you out of the "Segments left is zero" branch of that RFCs =
requirement?
>=20
> In section 3.4, please remove "this may seem too time-consuming and =
too risky" or restate it with details. How is this observation supposed =
to help the reader?
>=20
> In section 4.1 paragraph 3 "But the major issue is probably linked to =
all threats" would read better as "One major issue is threats"
>=20
> In section 5 paragraph 3, please provide a reference to where these =
significant implications are discussed, or add some discussion. =
(Otherwise, what is the reader supposed to do with this observation?)
>=20
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Thu Jun 26 09:09:42 2014
Return-Path: <nomcom-chair-2014@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7EB11B2E0A; Thu, 26 Jun 2014 09:09:39 -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_50=0.8,  J_CHICKENPOX_21=0.6] autolearn=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 kNLpQNmnQvTg; Thu, 26 Jun 2014 09:09:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD461B2E9A; Thu, 26 Jun 2014 08:16:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2014 <nomcom-chair-2014@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: draft list of qualified volunteers for 2014-2015 nomcom
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140626151615.10019.86428.idtracker@ietfa.amsl.com>
Date: Thu, 26 Jun 2014 08:16:15 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Uqxdb-luHXiP7fm12QQwoCBCMds
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: mcr+nomcom@sandelman.ca
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 16:09:40 -0000

This is the draft list of volunteers.

I am pleased to announce that we have 118 qualified individuals who
have generously volunteered to serve as voting members of this year's
Nomcom.

Please take a look and get in touch before July 3 if you think your
name should be here and it isn't (or possibly I've mis-typed it...), or
if you have any other questions or concerns with the list.

The first number is the place in the list.  The number in () is
the spot on my master list (which includes ineligible people).

My apologies if my any UTF-8/Latin-1 confusion broke an accent in
your name; it's my MUA's fault.

As published in the schedule, back in April, and visible at:
     https://datatracker.ietf.org/nomcom/2014/
and  http://goo.gl/D3q2CY

We are at step 06.  The random selection will occur on Sunday July 6.

01. 2014-Mar-28 Nomcom Chair Announcement made.
02. 2014-May-15 FIRST message volunteers
03. 2014-May-29 SECOND message volunteers
04. 2014-Jun-12 THIRD message volunteers
05. 2014-Jun-19 Timeline and Seeds for Random Selection
06. 2014-Jun-26 Final Announcement of Qualified Volunteers
    *HERE*

07. 2014-Jul-03 Raise issues on qualified volunteers by 23:59 EDT.
08. 2014-Jul-06 Seed values available from seed sources
09. 2014-Jul-06 Run random selection algorithm and publish results
10. 2014-Jul-07 challenge process begins
11. 2014-Jul-14 challenge process ends
12. 2014-Jul-15 Results of Random Selection


Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in list order, no sorting
001 (1) Tim Wicinski , Salesforce
002 (2) Paul Hoffman , VPN Consortium
003 (3) John Scudder , Juniper
004 (4) Toerless Eckert , Cisco Systems
005 (5) Gonzalo Salgueiro , Cisco Systems
006 (6) Stephan Wenger , Vidyo
007 (7) Louis (Lou) Berger , LabN Consulting, L.L.C.
008 (8) Fred Baker , Cisco Systems
009 (9) Ross Callon , Juniper
010 (10) Carlos Martinez , LACNIC
011 (11) DHRUV DHODY , Huawei Technologies
012 (12) Suhas Nandakumar , Cisco Systems
013 (13) Ron Bonica , Juniper
014 (14) Sanjay Mishra , Verizon Communications
015 (15) John Levine , Taughannock Networks
016 (16) Melinda Shore , No Mountain Software
017 (17) Wassim Haddad , Ericsson
018 (18) Hosnieh Rafiee , Huawei Technologies
019 (19) Sam K. Aldrin , Huawei Technologies
020 (20) Lucy Yong , Huawei Technologies
021 (21) Ross Finlayson , Live Networks, Inc.
022 (22) Mehmet Ersue , Nokia
023 (23) Carl Williams , MCSR Labs
024 (24) Min Ye , Huawei Technologies
025 (25) Fernando Gont , UTN/FRH
026 (26) Ole Troan , Cisco Systems
027 (27) Luca Martini , Cisco Systems
028 (28) Bill VerSteeg , Cisco Systems
029 (29) Linda Dunbar , Huawei technologies
030 (30) Charles Eckel , Cisco Systems
031 (31) Pascal Thubert , Cisco systems
032 (32) Hugo Salgado , NIC Chile
033 (33) Peter Yee , AKAYLA
034 (34) Stephen Kent , BBN Technologies
035 (35) Xiaohu XU , Huawei Technologies
036 (36) John E Drake , Juniper Networks
037 (37) Donald Eastlake , Huawei Technologies
038 (38) Yuanlong Jiang , Huawei Technologies
039 (39) Ning Zong , Huawei technologies
040 (40) Hongyu Li , Huawei Technologies
041 (41) Shucheng Liu , Huawei Technologies
042 (42) Ralph Droms , Cisco Systems
043 (43) Tissa Senevirathne , Cisco Systems
044 (44) Lingli Deng , China Mobile
045 (45) Dapeng Liu , China Mobile
046 (46) Mach Chen , Huawei technologies
047 (47) Dacheng Zhang , Huawei technologies
048 (48) Adam Montville , Tripwire, Inc.
049 (49) Mark Townsley , Cisco Systems
050 (50) Sheng JIANG , Huawei Technologies
051 (51) Matt Lepinski , BBN Technologies
052 (52) Stephan Friedl , Cisco Systems
053 (53) Eric VYNCKE , Cisco Systems
054 (54) ANM Zaheduzzaman Sarker , Ericsson
055 (55) Stan Ratliff , Cisco
056 (56) Edward Crabbe , Google
057 (57) Karen Seo , BBN Technology
058 (58) Hannes Gredler , Juniper Networks
059 (59) Susan Hares , Hickory Hill Consulting
060 (60) Iuniana Oprescu , Orange
061 (61) Varun Singh , Aalto University
062 (62) Jon Mitchell , Jon Mitchell
063 (63) Zhaohui Zhang , Juniper Networks
064 (64) Ari Ker?nen , Ari Ker?nen
065 (65) Mingui Zhang , Huawei
066 (66) Dean Bogdanovic , Juniper Networks
067 (67) Suresh Krishnan , Ericsson
068 (68) Craig White , Alcatel-Lucent
069 (69) Fangwei Hu , ZTE Corporation
070 (70) Samuel Weiler , Parsons
071 (82) Benson Schliesser, Brocade Communications
072 (83) Bhumip Khasnabish, ZTE (TX) Inc.
073 (84) QIN WU, Shenzhen Huawei Technologies Software Co.,Ltd
074 (88) Charles Perkins, Futurewei
075 (92) Christer Holmberg, Ericsson
076 (95) Yong Cui, Tsinghua Univ.
077 (98) Damien Saucez , Inria
078 (100) Hui Deng, China Mobile
079 (102) Dimitri Papadimitriou,
080 (110) Emil Ivov, jitsi.org
081 (119) Luigi Iannone, Telecom ParisTech
082 (120) Giles Heron, Cisco Systems
083 (123) Gregory Mirsky, Ericsson
084 (126) Yunfei Zhang, Coolpad
085 (133) iuniana oprescu, Orange
086 (134) Joseph Abley, Dyn, Inc.
087 (136) Jeff Tantsura, Ericsson
088 (140) John Jason Brzozowski, Comcast
089 (142) Jon Hudson, Brocade
090 (143) Jouni Korhonen,
091 (144) Kostas Pentikousis, EICT GmbH
092 (147) Klaas Wierenga, Cisco
093 (148) Kaveh Ranjbar, RIPE NCC
094 (153) Lee Howard, Time Warner Cable
095 (155) Lei Zhu, Huawei
096 (159) Yizhou Li, Huawei Technologies
097 (160) Lucy Lynch, Internet Society
098 (165) Marcelo Bagnulo, UC3M
099 (166) Larry Masinter, Adobe
100 (167) Matthew Bocci, Alcatel-Lucent
101 (170) Michael Jones, Microsoft
102 (171) Mahesh Jethanandani, Ciena Corporation
103 (173) Karen O'Donoghue, Internet Society
104 (179) P?l-Erik Martinsen, Cisco
105 (187) Peter Lothberg, STUPI LLC
106 (189) Russ White, Ericsson
107 (190) Sandeep Kumar, Philips Research
108 (192) Scott Mansfield, Ericsson
109 (196) Simon Pietro Romano, Meetecho/University of Napoli
110 (198) Stewart Bryant, Cisco Systems
111 (201) Stig Venaas, cisco
112 (206) Tony Hansen, AT&T Labs
113 (208) Thomas Walsh, Juniper Networks
114 (209) Ulrich Herberg, Fujitsu Laboratories of America
115 (216) Li Xue, Shenzhen Huawei Technologies Software Co., Ltd
116 (218) Zhen Cao, China Mobile
117 (220) Fatai Zhang, Shenzhen Huawei Technologies Software Co., Ltd.
118 (221) Yi Zhao, Huawei USA


From nobody Thu Jun 26 09:14:24 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBC2C1B2F11; Thu, 26 Jun 2014 09:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 ehRi1hXH7VV5; Thu, 26 Jun 2014 09:14:14 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 608F81B2FF3; Thu, 26 Jun 2014 08:22:37 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-89-168.dllstx.fios.verizon.net [173.57.89.168]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s5QFMYiW041704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 26 Jun 2014 10:22:35 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-89-168.dllstx.fios.verizon.net [173.57.89.168] claimed to be unnumerable.local
Message-ID: <53AC3ABA.8010204@nostrum.com>
Date: Thu, 26 Jun 2014 10:22:34 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [v6ops] Gen-art LC review: draft-ietf-v6ops-enterprise-incremental-ipv6-05
References: <5390BE61.4050407@nostrum.com> <8AF3C2D9-22C3-4FE1-9EBE-40BB8F9A6628@piuha.net>
In-Reply-To: <8AF3C2D9-22C3-4FE1-9EBE-40BB8F9A6628@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NrSV4QOsuPIxG5a2YBwzlyOaVNE
Cc: v6ops@ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-v6ops-enterprise-incremental-v6@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 16:14:19 -0000

No, I don't think I've seen a response.

RjS

On 6/26/14, 10:08 AM, Jari Arkko wrote:
> Thank you Robert for your (once again) in-depth review. But I have a question - was there a response to the comments? My e-mail system does not show one, but maybe I missed it.
>
> Jari
>
> On 05 Jun 2014, at 20:00, Robert Sparks <rjsparks@nostrum.com> wrote:
>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-v6ops-enterprise-incremental-ipv6-05
>> Reviewer: Robert Sparks
>> Review Date: 5 June 2014
>> IETF LC End Date: 9 June 2014
>> IESG Telechat date: not yet scheduled
>>
>> Summary: This draft is basically ready for publication as an Informational RFC,
>> but has nits that should be considered before publication.
>>
>> I had a mixed overall impression after my first read-through of this draft.
>>
>> Overall, the list of issues to consider, and the compendium of references is very useful, but there are large stretches of text that really aren't helping the reader, and they make the good stuff harder to see.
>>
>> I encourage the group to take one more editorial pass, focusing on removing as much text as possible without losing the message.
>>
>> Please help the IESG and the RFC-Editor out: the shepherd's writeup should say something about why deviating from the style guide's restriction on number of authors is is appropriate for this document.
>>
>> Here are specific nits to consider in document order:
>>
>> The first paragraph of section 1.3 starts talking about phases as if they've already been described. As written, it says that beginning with the External Phase is recommended in RFC5211. But the words "External Phase" do not appear in 5211, and its not clear on a quick read exactly what in 5211 you were hoping to point out here.  Please introduce the phases before this point, and change the callout to 5211 to make it more clear how what 5211 is saying ties into this document.
>>
>> Why is "Other Phases" capitalized in 2.1? The number of phases defined in this document is small - I suspect this text is older and left room for the group to decide to define more phases. Consider just listing what you ended up with explicitly.
>>
>> Section 2.1 contains sentences like "The project manager will need to spend some time on planning." That is obvious, and you've already established that planning needs to happen. This paragraph (perhaps much of this section) would be improved by removing as much text as you can. It already speaks mostly in terms of the benefits of planning. Making that a more explicit goal in the writing structure would help identify what can be taken away without losing the message. Overall, trying to describe what good project management entails is a bit out of place. Perhaps you should just say "This requires good project management skills"?
>>
>> In 2.2.2 you say "Applications should be made to use APIs". That seems an odd construct for an IETF document. Perhaps you could observe, rather than command, here? Would saying something like "Applications that use APIs to hide the specifics ... will be easier to take through the migration" make the point?
>>
>> In 2.3, why do you need the hyperbole in "IPv6 adoption will be a multifacted undertaking that will touch everyone in the organization unlike almost any other project."? How does the "unlike almost any other project" help the reader?
>>
>> In 2.4.1, please rephrase "pretty much like". Are there any differences in the use of IPSec dependent on the address family that are important to call out? If not, why doesn't this say "the same as in"?
>>
>> Section 2.4.2: As written, this says Etc. is an attack. Please change the introduction to the list to say "for example" or "in particular" and remove the Etc. If the point was to cause the reader to think about attacks beyond these listed, say that explicitly.
>>
>> The 6th paragraph of 2.6 states the problem is "how to get host DNS records updated." The text in the rest of the paragraph only addresses this by implication. It looks more like the general discussion of SLAAC vs DHCPv6 instead of straightforwardly noting that a DHCPv6 server can be made to update DNS records.
>>
>> The reference to RFC6866 in paragraph 7 of section 2.6 is unclear - what was it trying to point out?  I think the last sentence was trying to say 'static address assignment (even if achieved with DHCP) is usually used' where it currently says 'SLAAC is rarely used'?
>>
>> Section 3: The second paragraph doesn't add anything to the document.
>>
>> Section 3.1 paragraph 2: I don't understand why the paragraph ends with "which is an important consideration". Can you delete the phrase without losing the message? If not, say why an enterprise would care whether or not _other_ enterprises had already deployed using BGP on their own.
>>
>> Section 3.1 paragraph 4 : "will prefer to use" is out of place. Perhaps this should be stated as "will likely get better results using"?
>>
>> Section 3.1 paragraph 5: Can you add a reference to a discussion of how keeping the MTU congruent simplifies operations?
>>
>> In section 3.2 consider using the names from 4890 in the list ('Packet Too Big' rather than 'Unreachable packet-to-big')
>>
>> Please check whether the sentence "To be fully compliant with [RFC5095], all packets containing the routing extension header type 0 must be dropped." is perhaps too simple a description of 5095? Does context keep you out of the "Segments left is zero" branch of that RFCs requirement?
>>
>> In section 3.4, please remove "this may seem too time-consuming and too risky" or restate it with details. How is this observation supposed to help the reader?
>>
>> In section 4.1 paragraph 3 "But the major issue is probably linked to all threats" would read better as "One major issue is threats"
>>
>> In section 5 paragraph 3, please provide a reference to where these significant implications are discussed, or add some discussion. (Otherwise, what is the reader supposed to do with this observation?)
>>
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Thu Jun 26 09:43:18 2014
Return-Path: <nomcom-chair-2014@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B411B2BDB; Thu, 26 Jun 2014 09:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6] autolearn=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 ckvRbsmxhVHM; Thu, 26 Jun 2014 09:43:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAD21B30CF; Thu, 26 Jun 2014 09:20:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2014 <nomcom-chair-2014@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: econd draft list of qualified volunteers for 2014-2015 nomcom
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140626162038.18995.71697.idtracker@ietfa.amsl.com>
Date: Thu, 26 Jun 2014 09:20:38 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Yq-oyDC8nkvIUbPaQueTrGsodt4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: nomcom-chair-2014@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 16:43:17 -0000

This is the draft (2) list of volunteers.
21 names that I confirmed were eligible this morning did not
make it into the list.

I am pleased to announce that we have 139 qualified individuals who
have generously volunteered to serve as voting members of this year's
Nomcom.

Please take a look and get in touch before July 3 if you think your
name should be here and it isn't (or possibly I've mis-typed it...), or
if you have any other questions or concerns with the list.

The first number is the place in the list.  The number in () is
the spot on my master list (which includes ineligible people).

My appologies if my any UTF-8/Latin-1 confusion broke an accent in
your name; it's my MUA's fault.

As published in the schedule, back in April, and visible at:
     https://datatracker.ietf.org/nomcom/2014/
and  http://goo.gl/D3q2CY

We are at step 06.  The random selection will occur on Sunday July 6.

01. 2014-Mar-28 Nomcom Chair Announcement made.
02. 2014-May-15 FIRST message volunteers
03. 2014-May-29 SECOND message volunteers
04. 2014-Jun-12 THIRD message volunteers
05. 2014-Jun-19 Timeline and Seeds for Random Selection
06. 2014-Jun-26 Final Announcement of Qualified Volunteers
    *HERE*

07. 2014-Jul-03 Raise issues on qualified volunteers by 23:59 EDT.
08. 2014-Jul-06 Seed values available from seed sources
09. 2014-Jul-06 Run random selection algorithm and publish results
10. 2014-Jul-07 challenge process begins
11. 2014-Jul-14 challenge process ends
12. 2014-Jul-15 Results of Random Selection


Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in list order, no sorting
001 (1) Tim Wicinski , Salesforce
002 (2) Paul Hoffman , VPN Consortium
003 (3) John Scudder , Juniper
004 (4) Toerless Eckert , Cisco Systems
005 (5) Gonzalo Salgueiro , Cisco Systems
006 (6) Stephan Wenger , Vidyo
007 (7) Louis (Lou) Berger , LabN Consulting, L.L.C.
008 (8) Fred Baker , Cisco Systems
009 (9) Ross Callon , Juniper
010 (10) Carlos Martinez , LACNIC
011 (11) DHRUV DHODY , Huawei Technologies
012 (12) Suhas Nandakumar , Cisco Systems
013 (13) Ron Bonica , Juniper
014 (14) Sanjay Mishra , Verizon Communications
015 (15) John Levine , Taughannock Networks
016 (16) Melinda Shore , No Mountain Software
017 (17) Wassim Haddad , Ericsson
018 (18) Hosnieh Rafiee , Huawei Technologies
019 (19) Sam K. Aldrin , Huawei Technologies
020 (20) Lucy Yong , Huawei Technologies
021 (21) Ross Finlayson , Live Networks, Inc.
022 (22) Mehmet Ersue , Nokia
023 (23) Carl Williams , MCSR Labs
024 (24) Min Ye , Huawei Technologies
025 (25) Fernando Gont , UTN/FRH
026 (26) Ole Troan , Cisco Systems
027 (27) Luca Martini , Cisco Systems
028 (28) Bill VerSteeg , Cisco Systems
029 (29) Linda Dunbar , Huawei technologies
030 (30) Charles Eckel , Cisco Systems
031 (31) Pascal Thubert , Cisco systems
032 (32) Hugo Salgado , NIC Chile
033 (33) Peter Yee , AKAYLA
034 (34) Stephen Kent , BBN Technologies
035 (35) Xiaohu XU , Huawei Technologies
036 (36) John E Drake , Juniper Networks
037 (37) Donald Eastlake , Huawei Technologies
038 (38) Yuanlong Jiang , Huawei Technologies
039 (39) Ning Zong , Huawei technologies
040 (40) Hongyu Li , Huawei Technologies
041 (41) Shucheng Liu , Huawei Technologies
042 (42) Ralph Droms , Cisco Systems
043 (43) Tissa Senevirathne , Cisco Systems
044 (44) Lingli Deng , China Mobile
045 (45) Dapeng Liu , China Mobile
046 (46) Mach Chen , Huawei technologies
047 (47) Dacheng Zhang , Huawei technologies
048 (48) Adam Montville , Tripwire, Inc.
049 (49) Mark Townsley , Cisco Systems
050 (50) Sheng JIANG , Huawei Technologies
051 (51) Matt Lepinski , BBN Technologies
052 (52) Stephan Friedl , Cisco Systems
053 (53) Eric VYNCKE , Cisco Systems
054 (54) ANM Zaheduzzaman Sarker , Ericsson
055 (55) Stan Ratliff , Cisco
056 (56) Edward Crabbe , Google
057 (57) Karen Seo , BBN Technology
058 (58) Hannes Gredler , Juniper Networks
059 (59) Susan Hares , Hickory Hill Consulting
060 (60) Iuniana Oprescu , Orange
061 (61) Varun Singh , Aalto University
062 (62) Jon Mitchell , Jon Mitchell
063 (63) Zhaohui Zhang , Juniper Networks
064 (64) Ari Ker?nen , Ari Ker?nen
065 (65) Mingui Zhang , Huawei
066 (66) Dean Bogdanovic , Juniper Networks
067 (67) Suresh Krishnan , Ericsson
068 (68) Craig White , Alcatel-Lucent
069 (69) Fangwei Hu , ZTE Corporation
070 (70) Samuel Weiler , Parsons
071 (82) Benson Schliesser, Brocade Communications
072 (83) Bhumip Khasnabish, ZTE (TX) Inc.
073 (84) QIN WU, Shenzhen Huawei Technologies Software Co.,Ltd
074 (88) Charles Perkins, Futurewei
075 (92) Christer Holmberg, Ericsson
076 (95) Yong Cui, Tsinghua Univ.
077 (98) Damien Saucez , Inria
078 (100) Hui Deng, China Mobile
079 (102) Dimitri Papadimitriou, 
080 (110) Emil Ivov, jitsi.org
081 (119) Luigi Iannone, Telecom ParisTech
082 (120) Giles Heron, Cisco Systems
083 (123) Gregory Mirsky, Ericsson
084 (124) Gunter Van de Velde, 
085 (126) Yunfei Zhang, Coolpad
086 (133) iuniana oprescu, Orange
087 (134) Joseph Abley, Dyn, Inc.
088 (136) Jeff Tantsura, Ericsson
089 (140) John Jason Brzozowski, Comcast
090 (142) Jon Hudson, Brocade
091 (143) Jouni Korhonen, 
092 (144) Kostas Pentikousis, EICT GmbH
093 (147) Klaas Wierenga, Cisco
094 (148) Kaveh Ranjbar, RIPE NCC
095 (153) Lee Howard, Time Warner Cable
096 (155) Lei Zhu, Huawei
097 (159) Yizhou Li, Huawei Technologies
098 (160) Lucy Lynch -900, Internet Society
099 (165) Marcelo Bagnulo, UC3M
100 (166) Larry Masinter, Adobe
101 (167) Matthew Bocci, Alcatel-Lucent
102 (170) Michael Jones, Microsoft
103 (171) Mahesh Jethanandani, Ciena Corporation
104 (173) Karen O'Donoghue, Internet Society
105 (179) P?l-Erik Martinsen, Cisco
106 (187) Peter Lothberg, STUPI LLC
107 (189) Russ White, Ericsson
108 (190) Sandeep Kumar, Philips Research
109 (192) Scott Mansfield, Ericsson
110 (196) Simon Pietro Romano, Meetecho/University of Napoli
111 (198) Stewart Bryant, Cisco Systems
112 (201) Stig Venaas, cisco
113 (206) Tony Hansen, AT&T Labs
114 (208) Thomas Walsh, Juniper Networks
115 (209) Ulrich Herberg, Fujitsu Laboratories of America
116 (216) Li Xue, Shenzhen Huawei Technologies Software Co., Ltd
117 (218) Zhen Cao, China Mobile
118 (220) Fatai Zhang, Shenzhen Huawei Technologies Software Co., Ltd.
119 (221) Yi Zhao, Huawei USA
120 (222) Hannes Tschofenig , 
121 (223) Paul Ebersman , Comcast 
122 (224) Andrew Yourtchenko , Cisco
123 (225) Salvatore Loreto , Ericsson
124 (226) Stig Venaas , Cisco
125 (227) Peter Koch  , DENIC eG
126 (228) Paul Wouters , Red Hat
127 (230) Vic Liu (Zhiheng Liu) , ChinaMobile
128 (231) Andy Bierman , YumaWorks, Inc.
129 (232) Simon Perreault , Jive Communications 
130 (234) Franck Martin , Linkedin
131 (235) Tom Walsh , Juniper Networks
132 (236) Ning Kong , CNNIC
133 (237) Russ White , Ericsson
134 (238) Konda Tirumaleswar Reddy , Cisco
135 (239) Lixia Zhang , UCLA
136 (240) Ignas Bagdonas , Routing System Ltd
137 (241) Brian Weis , Cisco Systems
138 (242) David Mandelberg , BBN Technologies
139 (244) Warren Kumari  , 


From nobody Thu Jun 26 11:03:19 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA80E1B305A; Thu, 26 Jun 2014 11:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100] autolearn=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 WpGRNnvskfGp; Thu, 26 Jun 2014 11:03:07 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id ED6241B2D42; Thu, 26 Jun 2014 10:49:53 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 9AC20F9C012; Thu, 26 Jun 2014 13:49:43 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id rUAwGHtpvrAc; Thu, 26 Jun 2014 13:49:19 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-144-77.washdc.fios.verizon.net [96.255.144.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6CBB8F9C014; Thu, 26 Jun 2014 13:49:19 -0400 (EDT)
Subject: Re: econd draft list of qualified volunteers for 2014-2015 nomcom
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20140626162038.18995.71697.idtracker@ietfa.amsl.com>
Date: Thu, 26 Jun 2014 13:49:07 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <156BCC28-3BEA-4BAB-92CF-C96500450B40@vigilsec.com>
References: <20140626162038.18995.71697.idtracker@ietfa.amsl.com>
To: nomcom-chair-2014@ietf.org
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/svEi9MkTLbVIzAsGgs7Tjaqjx2I
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 18:03:11 -0000

A couple of people seem to appear on the list more than once...

Iuniana Oprescu: number 60 and 86.
Russ White: number 107 and 133.
Stig Venaas: number 112 and 124.
Thomas (Tom) Walsh: 114 and 131.

Russ


On Jun 26, 2014, at 12:20 PM, NomCom Chair 2014 wrote:

> This is the draft (2) list of volunteers.
> 21 names that I confirmed were eligible this morning did not
> make it into the list.
> 
> I am pleased to announce that we have 139 qualified individuals who
> have generously volunteered to serve as voting members of this year's
> Nomcom.
> 
> Please take a look and get in touch before July 3 if you think your
> name should be here and it isn't (or possibly I've mis-typed it...), or
> if you have any other questions or concerns with the list.
> 
> The first number is the place in the list.  The number in () is
> the spot on my master list (which includes ineligible people).
> 
> My appologies if my any UTF-8/Latin-1 confusion broke an accent in
> your name; it's my MUA's fault.
> 
> As published in the schedule, back in April, and visible at:
>     https://datatracker.ietf.org/nomcom/2014/
> and  http://goo.gl/D3q2CY
> 
> We are at step 06.  The random selection will occur on Sunday July 6.
> 
> 01. 2014-Mar-28 Nomcom Chair Announcement made.
> 02. 2014-May-15 FIRST message volunteers
> 03. 2014-May-29 SECOND message volunteers
> 04. 2014-Jun-12 THIRD message volunteers
> 05. 2014-Jun-19 Timeline and Seeds for Random Selection
> 06. 2014-Jun-26 Final Announcement of Qualified Volunteers
>    *HERE*
> 
> 07. 2014-Jul-03 Raise issues on qualified volunteers by 23:59 EDT.
> 08. 2014-Jul-06 Seed values available from seed sources
> 09. 2014-Jul-06 Run random selection algorithm and publish results
> 10. 2014-Jul-07 challenge process begins
> 11. 2014-Jul-14 challenge process ends
> 12. 2014-Jul-15 Results of Random Selection
> 
> 
> Michael Richardson
> mcr+nomcom@sandelman.ca
> nomcom-chair-2014@ietf.org
> 
> =====  qualified volunteers so far, in list order, no sorting
> 001 (1) Tim Wicinski , Salesforce
> 002 (2) Paul Hoffman , VPN Consortium
> 003 (3) John Scudder , Juniper
> 004 (4) Toerless Eckert , Cisco Systems
> 005 (5) Gonzalo Salgueiro , Cisco Systems
> 006 (6) Stephan Wenger , Vidyo
> 007 (7) Louis (Lou) Berger , LabN Consulting, L.L.C.
> 008 (8) Fred Baker , Cisco Systems
> 009 (9) Ross Callon , Juniper
> 010 (10) Carlos Martinez , LACNIC
> 011 (11) DHRUV DHODY , Huawei Technologies
> 012 (12) Suhas Nandakumar , Cisco Systems
> 013 (13) Ron Bonica , Juniper
> 014 (14) Sanjay Mishra , Verizon Communications
> 015 (15) John Levine , Taughannock Networks
> 016 (16) Melinda Shore , No Mountain Software
> 017 (17) Wassim Haddad , Ericsson
> 018 (18) Hosnieh Rafiee , Huawei Technologies
> 019 (19) Sam K. Aldrin , Huawei Technologies
> 020 (20) Lucy Yong , Huawei Technologies
> 021 (21) Ross Finlayson , Live Networks, Inc.
> 022 (22) Mehmet Ersue , Nokia
> 023 (23) Carl Williams , MCSR Labs
> 024 (24) Min Ye , Huawei Technologies
> 025 (25) Fernando Gont , UTN/FRH
> 026 (26) Ole Troan , Cisco Systems
> 027 (27) Luca Martini , Cisco Systems
> 028 (28) Bill VerSteeg , Cisco Systems
> 029 (29) Linda Dunbar , Huawei technologies
> 030 (30) Charles Eckel , Cisco Systems
> 031 (31) Pascal Thubert , Cisco systems
> 032 (32) Hugo Salgado , NIC Chile
> 033 (33) Peter Yee , AKAYLA
> 034 (34) Stephen Kent , BBN Technologies
> 035 (35) Xiaohu XU , Huawei Technologies
> 036 (36) John E Drake , Juniper Networks
> 037 (37) Donald Eastlake , Huawei Technologies
> 038 (38) Yuanlong Jiang , Huawei Technologies
> 039 (39) Ning Zong , Huawei technologies
> 040 (40) Hongyu Li , Huawei Technologies
> 041 (41) Shucheng Liu , Huawei Technologies
> 042 (42) Ralph Droms , Cisco Systems
> 043 (43) Tissa Senevirathne , Cisco Systems
> 044 (44) Lingli Deng , China Mobile
> 045 (45) Dapeng Liu , China Mobile
> 046 (46) Mach Chen , Huawei technologies
> 047 (47) Dacheng Zhang , Huawei technologies
> 048 (48) Adam Montville , Tripwire, Inc.
> 049 (49) Mark Townsley , Cisco Systems
> 050 (50) Sheng JIANG , Huawei Technologies
> 051 (51) Matt Lepinski , BBN Technologies
> 052 (52) Stephan Friedl , Cisco Systems
> 053 (53) Eric VYNCKE , Cisco Systems
> 054 (54) ANM Zaheduzzaman Sarker , Ericsson
> 055 (55) Stan Ratliff , Cisco
> 056 (56) Edward Crabbe , Google
> 057 (57) Karen Seo , BBN Technology
> 058 (58) Hannes Gredler , Juniper Networks
> 059 (59) Susan Hares , Hickory Hill Consulting
> 060 (60) Iuniana Oprescu , Orange
> 061 (61) Varun Singh , Aalto University
> 062 (62) Jon Mitchell , Jon Mitchell
> 063 (63) Zhaohui Zhang , Juniper Networks
> 064 (64) Ari Ker?nen , Ari Ker?nen
> 065 (65) Mingui Zhang , Huawei
> 066 (66) Dean Bogdanovic , Juniper Networks
> 067 (67) Suresh Krishnan , Ericsson
> 068 (68) Craig White , Alcatel-Lucent
> 069 (69) Fangwei Hu , ZTE Corporation
> 070 (70) Samuel Weiler , Parsons
> 071 (82) Benson Schliesser, Brocade Communications
> 072 (83) Bhumip Khasnabish, ZTE (TX) Inc.
> 073 (84) QIN WU, Shenzhen Huawei Technologies Software Co.,Ltd
> 074 (88) Charles Perkins, Futurewei
> 075 (92) Christer Holmberg, Ericsson
> 076 (95) Yong Cui, Tsinghua Univ.
> 077 (98) Damien Saucez , Inria
> 078 (100) Hui Deng, China Mobile
> 079 (102) Dimitri Papadimitriou, 
> 080 (110) Emil Ivov, jitsi.org
> 081 (119) Luigi Iannone, Telecom ParisTech
> 082 (120) Giles Heron, Cisco Systems
> 083 (123) Gregory Mirsky, Ericsson
> 084 (124) Gunter Van de Velde, 
> 085 (126) Yunfei Zhang, Coolpad
> 086 (133) iuniana oprescu, Orange
> 087 (134) Joseph Abley, Dyn, Inc.
> 088 (136) Jeff Tantsura, Ericsson
> 089 (140) John Jason Brzozowski, Comcast
> 090 (142) Jon Hudson, Brocade
> 091 (143) Jouni Korhonen, 
> 092 (144) Kostas Pentikousis, EICT GmbH
> 093 (147) Klaas Wierenga, Cisco
> 094 (148) Kaveh Ranjbar, RIPE NCC
> 095 (153) Lee Howard, Time Warner Cable
> 096 (155) Lei Zhu, Huawei
> 097 (159) Yizhou Li, Huawei Technologies
> 098 (160) Lucy Lynch -900, Internet Society
> 099 (165) Marcelo Bagnulo, UC3M
> 100 (166) Larry Masinter, Adobe
> 101 (167) Matthew Bocci, Alcatel-Lucent
> 102 (170) Michael Jones, Microsoft
> 103 (171) Mahesh Jethanandani, Ciena Corporation
> 104 (173) Karen O'Donoghue, Internet Society
> 105 (179) P?l-Erik Martinsen, Cisco
> 106 (187) Peter Lothberg, STUPI LLC
> 107 (189) Russ White, Ericsson
> 108 (190) Sandeep Kumar, Philips Research
> 109 (192) Scott Mansfield, Ericsson
> 110 (196) Simon Pietro Romano, Meetecho/University of Napoli
> 111 (198) Stewart Bryant, Cisco Systems
> 112 (201) Stig Venaas, cisco
> 113 (206) Tony Hansen, AT&T Labs
> 114 (208) Thomas Walsh, Juniper Networks
> 115 (209) Ulrich Herberg, Fujitsu Laboratories of America
> 116 (216) Li Xue, Shenzhen Huawei Technologies Software Co., Ltd
> 117 (218) Zhen Cao, China Mobile
> 118 (220) Fatai Zhang, Shenzhen Huawei Technologies Software Co., Ltd.
> 119 (221) Yi Zhao, Huawei USA
> 120 (222) Hannes Tschofenig , 
> 121 (223) Paul Ebersman , Comcast 
> 122 (224) Andrew Yourtchenko , Cisco
> 123 (225) Salvatore Loreto , Ericsson
> 124 (226) Stig Venaas , Cisco
> 125 (227) Peter Koch  , DENIC eG
> 126 (228) Paul Wouters , Red Hat
> 127 (230) Vic Liu (Zhiheng Liu) , ChinaMobile
> 128 (231) Andy Bierman , YumaWorks, Inc.
> 129 (232) Simon Perreault , Jive Communications 
> 130 (234) Franck Martin , Linkedin
> 131 (235) Tom Walsh , Juniper Networks
> 132 (236) Ning Kong , CNNIC
> 133 (237) Russ White , Ericsson
> 134 (238) Konda Tirumaleswar Reddy , Cisco
> 135 (239) Lixia Zhang , UCLA
> 136 (240) Ignas Bagdonas , Routing System Ltd
> 137 (241) Brian Weis , Cisco Systems
> 138 (242) David Mandelberg , BBN Technologies
> 139 (244) Warren Kumari  , 
> 


From nobody Thu Jun 26 11:54:27 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B41E11A0308; Thu, 26 Jun 2014 11:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Jhc9TDN7MCUN; Thu, 26 Jun 2014 11:54:22 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 00F171B2F4B; Thu, 26 Jun 2014 11:47:42 -0700 (PDT)
Received: from [192.168.1.110] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 6289227F9478; Thu, 26 Jun 2014 14:47:41 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_1965C44B-C6FE-4B56-B7C8-90ECCDE52A12"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: econd draft list of qualified volunteers for 2014-2015 nomcom
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <156BCC28-3BEA-4BAB-92CF-C96500450B40@vigilsec.com>
Date: Thu, 26 Jun 2014 14:47:14 -0400
Message-Id: <966C9628-C75F-4DA0-84ED-703AF4FB8976@lucidvision.com>
References: <20140626162038.18995.71697.idtracker@ietfa.amsl.com> <156BCC28-3BEA-4BAB-92CF-C96500450B40@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jFzLHhLtLGTLSegQyaHGNbhRD5A
Cc: nomcom-chair-2014@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 18:54:25 -0000

--Apple-Mail=_1965C44B-C6FE-4B56-B7C8-90ECCDE52A12
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	At least those folks are on the list. I definitely attended the =
last 3 meetings and I do not appear=20
on the list at all!=20

	--Tom


On Jun 26, 2014:1:49 PM, at 1:49 PM, Russ Housley <housley@vigilsec.com> =
wrote:

> A couple of people seem to appear on the list more than once...
>=20
> Iuniana Oprescu: number 60 and 86.
> Russ White: number 107 and 133.
> Stig Venaas: number 112 and 124.
> Thomas (Tom) Walsh: 114 and 131.
>=20
> Russ
>=20
>=20
> On Jun 26, 2014, at 12:20 PM, NomCom Chair 2014 wrote:
>=20
>> This is the draft (2) list of volunteers.
>> 21 names that I confirmed were eligible this morning did not
>> make it into the list.
>>=20
>> I am pleased to announce that we have 139 qualified individuals who
>> have generously volunteered to serve as voting members of this year's
>> Nomcom.
>>=20
>> Please take a look and get in touch before July 3 if you think your
>> name should be here and it isn't (or possibly I've mis-typed it...), =
or
>> if you have any other questions or concerns with the list.
>>=20
>> The first number is the place in the list.  The number in () is
>> the spot on my master list (which includes ineligible people).
>>=20
>> My appologies if my any UTF-8/Latin-1 confusion broke an accent in
>> your name; it's my MUA's fault.
>>=20
>> As published in the schedule, back in April, and visible at:
>>    https://datatracker.ietf.org/nomcom/2014/
>> and  http://goo.gl/D3q2CY
>>=20
>> We are at step 06.  The random selection will occur on Sunday July 6.
>>=20
>> 01. 2014-Mar-28 Nomcom Chair Announcement made.
>> 02. 2014-May-15 FIRST message volunteers
>> 03. 2014-May-29 SECOND message volunteers
>> 04. 2014-Jun-12 THIRD message volunteers
>> 05. 2014-Jun-19 Timeline and Seeds for Random Selection
>> 06. 2014-Jun-26 Final Announcement of Qualified Volunteers
>>   *HERE*
>>=20
>> 07. 2014-Jul-03 Raise issues on qualified volunteers by 23:59 EDT.
>> 08. 2014-Jul-06 Seed values available from seed sources
>> 09. 2014-Jul-06 Run random selection algorithm and publish results
>> 10. 2014-Jul-07 challenge process begins
>> 11. 2014-Jul-14 challenge process ends
>> 12. 2014-Jul-15 Results of Random Selection
>>=20
>>=20
>> Michael Richardson
>> mcr+nomcom@sandelman.ca
>> nomcom-chair-2014@ietf.org
>>=20
>> =3D=3D=3D=3D=3D  qualified volunteers so far, in list order, no =
sorting
>> 001 (1) Tim Wicinski , Salesforce
>> 002 (2) Paul Hoffman , VPN Consortium
>> 003 (3) John Scudder , Juniper
>> 004 (4) Toerless Eckert , Cisco Systems
>> 005 (5) Gonzalo Salgueiro , Cisco Systems
>> 006 (6) Stephan Wenger , Vidyo
>> 007 (7) Louis (Lou) Berger , LabN Consulting, L.L.C.
>> 008 (8) Fred Baker , Cisco Systems
>> 009 (9) Ross Callon , Juniper
>> 010 (10) Carlos Martinez , LACNIC
>> 011 (11) DHRUV DHODY , Huawei Technologies
>> 012 (12) Suhas Nandakumar , Cisco Systems
>> 013 (13) Ron Bonica , Juniper
>> 014 (14) Sanjay Mishra , Verizon Communications
>> 015 (15) John Levine , Taughannock Networks
>> 016 (16) Melinda Shore , No Mountain Software
>> 017 (17) Wassim Haddad , Ericsson
>> 018 (18) Hosnieh Rafiee , Huawei Technologies
>> 019 (19) Sam K. Aldrin , Huawei Technologies
>> 020 (20) Lucy Yong , Huawei Technologies
>> 021 (21) Ross Finlayson , Live Networks, Inc.
>> 022 (22) Mehmet Ersue , Nokia
>> 023 (23) Carl Williams , MCSR Labs
>> 024 (24) Min Ye , Huawei Technologies
>> 025 (25) Fernando Gont , UTN/FRH
>> 026 (26) Ole Troan , Cisco Systems
>> 027 (27) Luca Martini , Cisco Systems
>> 028 (28) Bill VerSteeg , Cisco Systems
>> 029 (29) Linda Dunbar , Huawei technologies
>> 030 (30) Charles Eckel , Cisco Systems
>> 031 (31) Pascal Thubert , Cisco systems
>> 032 (32) Hugo Salgado , NIC Chile
>> 033 (33) Peter Yee , AKAYLA
>> 034 (34) Stephen Kent , BBN Technologies
>> 035 (35) Xiaohu XU , Huawei Technologies
>> 036 (36) John E Drake , Juniper Networks
>> 037 (37) Donald Eastlake , Huawei Technologies
>> 038 (38) Yuanlong Jiang , Huawei Technologies
>> 039 (39) Ning Zong , Huawei technologies
>> 040 (40) Hongyu Li , Huawei Technologies
>> 041 (41) Shucheng Liu , Huawei Technologies
>> 042 (42) Ralph Droms , Cisco Systems
>> 043 (43) Tissa Senevirathne , Cisco Systems
>> 044 (44) Lingli Deng , China Mobile
>> 045 (45) Dapeng Liu , China Mobile
>> 046 (46) Mach Chen , Huawei technologies
>> 047 (47) Dacheng Zhang , Huawei technologies
>> 048 (48) Adam Montville , Tripwire, Inc.
>> 049 (49) Mark Townsley , Cisco Systems
>> 050 (50) Sheng JIANG , Huawei Technologies
>> 051 (51) Matt Lepinski , BBN Technologies
>> 052 (52) Stephan Friedl , Cisco Systems
>> 053 (53) Eric VYNCKE , Cisco Systems
>> 054 (54) ANM Zaheduzzaman Sarker , Ericsson
>> 055 (55) Stan Ratliff , Cisco
>> 056 (56) Edward Crabbe , Google
>> 057 (57) Karen Seo , BBN Technology
>> 058 (58) Hannes Gredler , Juniper Networks
>> 059 (59) Susan Hares , Hickory Hill Consulting
>> 060 (60) Iuniana Oprescu , Orange
>> 061 (61) Varun Singh , Aalto University
>> 062 (62) Jon Mitchell , Jon Mitchell
>> 063 (63) Zhaohui Zhang , Juniper Networks
>> 064 (64) Ari Ker?nen , Ari Ker?nen
>> 065 (65) Mingui Zhang , Huawei
>> 066 (66) Dean Bogdanovic , Juniper Networks
>> 067 (67) Suresh Krishnan , Ericsson
>> 068 (68) Craig White , Alcatel-Lucent
>> 069 (69) Fangwei Hu , ZTE Corporation
>> 070 (70) Samuel Weiler , Parsons
>> 071 (82) Benson Schliesser, Brocade Communications
>> 072 (83) Bhumip Khasnabish, ZTE (TX) Inc.
>> 073 (84) QIN WU, Shenzhen Huawei Technologies Software Co.,Ltd
>> 074 (88) Charles Perkins, Futurewei
>> 075 (92) Christer Holmberg, Ericsson
>> 076 (95) Yong Cui, Tsinghua Univ.
>> 077 (98) Damien Saucez , Inria
>> 078 (100) Hui Deng, China Mobile
>> 079 (102) Dimitri Papadimitriou,=20
>> 080 (110) Emil Ivov, jitsi.org
>> 081 (119) Luigi Iannone, Telecom ParisTech
>> 082 (120) Giles Heron, Cisco Systems
>> 083 (123) Gregory Mirsky, Ericsson
>> 084 (124) Gunter Van de Velde,=20
>> 085 (126) Yunfei Zhang, Coolpad
>> 086 (133) iuniana oprescu, Orange
>> 087 (134) Joseph Abley, Dyn, Inc.
>> 088 (136) Jeff Tantsura, Ericsson
>> 089 (140) John Jason Brzozowski, Comcast
>> 090 (142) Jon Hudson, Brocade
>> 091 (143) Jouni Korhonen,=20
>> 092 (144) Kostas Pentikousis, EICT GmbH
>> 093 (147) Klaas Wierenga, Cisco
>> 094 (148) Kaveh Ranjbar, RIPE NCC
>> 095 (153) Lee Howard, Time Warner Cable
>> 096 (155) Lei Zhu, Huawei
>> 097 (159) Yizhou Li, Huawei Technologies
>> 098 (160) Lucy Lynch -900, Internet Society
>> 099 (165) Marcelo Bagnulo, UC3M
>> 100 (166) Larry Masinter, Adobe
>> 101 (167) Matthew Bocci, Alcatel-Lucent
>> 102 (170) Michael Jones, Microsoft
>> 103 (171) Mahesh Jethanandani, Ciena Corporation
>> 104 (173) Karen O'Donoghue, Internet Society
>> 105 (179) P?l-Erik Martinsen, Cisco
>> 106 (187) Peter Lothberg, STUPI LLC
>> 107 (189) Russ White, Ericsson
>> 108 (190) Sandeep Kumar, Philips Research
>> 109 (192) Scott Mansfield, Ericsson
>> 110 (196) Simon Pietro Romano, Meetecho/University of Napoli
>> 111 (198) Stewart Bryant, Cisco Systems
>> 112 (201) Stig Venaas, cisco
>> 113 (206) Tony Hansen, AT&T Labs
>> 114 (208) Thomas Walsh, Juniper Networks
>> 115 (209) Ulrich Herberg, Fujitsu Laboratories of America
>> 116 (216) Li Xue, Shenzhen Huawei Technologies Software Co., Ltd
>> 117 (218) Zhen Cao, China Mobile
>> 118 (220) Fatai Zhang, Shenzhen Huawei Technologies Software Co., =
Ltd.
>> 119 (221) Yi Zhao, Huawei USA
>> 120 (222) Hannes Tschofenig ,=20
>> 121 (223) Paul Ebersman , Comcast=20
>> 122 (224) Andrew Yourtchenko , Cisco
>> 123 (225) Salvatore Loreto , Ericsson
>> 124 (226) Stig Venaas , Cisco
>> 125 (227) Peter Koch  , DENIC eG
>> 126 (228) Paul Wouters , Red Hat
>> 127 (230) Vic Liu (Zhiheng Liu) , ChinaMobile
>> 128 (231) Andy Bierman , YumaWorks, Inc.
>> 129 (232) Simon Perreault , Jive Communications=20
>> 130 (234) Franck Martin , Linkedin
>> 131 (235) Tom Walsh , Juniper Networks
>> 132 (236) Ning Kong , CNNIC
>> 133 (237) Russ White , Ericsson
>> 134 (238) Konda Tirumaleswar Reddy , Cisco
>> 135 (239) Lixia Zhang , UCLA
>> 136 (240) Ignas Bagdonas , Routing System Ltd
>> 137 (241) Brian Weis , Cisco Systems
>> 138 (242) David Mandelberg , BBN Technologies
>> 139 (244) Warren Kumari  ,=20
>>=20
>=20
>=20


--Apple-Mail=_1965C44B-C6FE-4B56-B7C8-90ECCDE52A12
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJTrGqyAAoJEPcO+I7eiUJZoY8P/1VPk1xUpqzo89+J7IcAN8I6
BGhoI0Ai9XHEtTdTthshZz4l9/RsBpIXUxaUe0PMIC+l/bDK8FeUzutQlWYAPHUb
BvQkR1DAgZEnhZKwRq3bl9kyWc0fQjYSqAomkm9jhmkgXFCYo3oJMcoQATsspUrt
snzXrIZpcRW9KPQAdHC9sUTDsUkG1gJpdng6mpu5rD8h1mA/A/VCfqzynuN/Zp26
IaEAwwmELTWUjrpHgyCH2jSl4zRgKQ3DYPSOljFY5Ma05GL8Da+2y9wgzTYc3rvV
0ay7kaFMjUQSJLHElDYtDeS+rPKKk0nanvxoKCvUbX8VB+wV6pyBX/9UGhUgzB+N
cUFtmblzOplxIzAigjLDKVZirEHkgQtM3XdZ79x6zsKVM0PIu23yCFFH6aQr+j15
8ljKCJHzQt9ptKYGUirnnlx5M3PNSBLwfLxOMzNfklLHEFhXi4i2FiBM/9YeXlTo
ysDvcjrgH707ky2PinjCUxwyQSa5Pjnx2z9nD/v/SzVkDksTNKVJjUT8uusntidb
jBBypgP3v8uf2bQOD/t1nsZu86RrQytIXP1vFsOTUfElh9mukP+4Wp5AA2pzmIGA
lwe6k610/wRbrPT2F/LIcZubqRmBwNT45zL009/UiDuQXfBP5MwHlj1KNDf2Vdj2
ojF9cdtIMH4ZuCquldiE
=B1Id
-----END PGP SIGNATURE-----

--Apple-Mail=_1965C44B-C6FE-4B56-B7C8-90ECCDE52A12--


From nobody Thu Jun 26 21:53:16 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F66B1B3148 for <ietf@ietfa.amsl.com>; Thu, 26 Jun 2014 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 gXzYZjpHxcdp for <ietf@ietfa.amsl.com>; Thu, 26 Jun 2014 21:53:09 -0700 (PDT)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACCDE1B2A92 for <ietf@ietf.org>; Thu, 26 Jun 2014 21:53:08 -0700 (PDT)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 26 Jun 2014 22:53:07 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 26 Jun 2014 22:53:05 -0600
Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id EACE319D8026 for <ietf@ietf.org>; Thu, 26 Jun 2014 22:52:55 -0600 (MDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by b03cxnp07028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s5R4pfJI2163052 for <ietf@ietf.org>; Fri, 27 Jun 2014 06:51:41 +0200
Received: from d03av03.boulder.ibm.com (localhost [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s5R4r44n032557 for <ietf@ietf.org>; Thu, 26 Jun 2014 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d03av03.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s5R4r3cl032533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 26 Jun 2014 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s5R4r3bK023642 for <ietf@ietf.org>; Fri, 27 Jun 2014 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s5R4r3K3023588 for ietf@ietf.org; Fri, 27 Jun 2014 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201406270453.s5R4r3K3023588@rotala.raleigh.ibm.com>
Date: Fri, 27 Jun 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14062704-8236-0000-0000-0000036B799F
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yo87M5kACEu1TlvsmHhA8PzAI5c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 04:53:15 -0000

Total of 70 messages in the last 7 days.
 
script run at: Fri Jun 27 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.57% |    6 |  6.94% |    41167 | mrex@sap.com
  4.29% |    3 |  5.75% |    34141 | ietf@trammell.ch
  5.71% |    4 |  4.09% |    24265 | ted.lemon@nominum.com
  5.71% |    4 |  3.64% |    21577 | randy@psg.com
  4.29% |    3 |  4.38% |    25986 | phill@hallambaker.com
  4.29% |    3 |  4.15% |    24647 | dave@cridland.net
  2.86% |    2 |  5.15% |    30559 | jefsey@jefsey.com
  4.29% |    3 |  2.81% |    16688 | mohta@necom830.hpcl.titech.ac.jp
  2.86% |    2 |  3.81% |    22638 | david.black@emc.com
  2.86% |    2 |  3.66% |    21746 | nomcom-chair-2014@ietf.org
  2.86% |    2 |  3.60% |    21348 | ron.even.tlv@gmail.com
  2.86% |    2 |  3.39% |    20106 | housley@vigilsec.com
  2.86% |    2 |  3.38% |    20064 | fred@cisco.com
  2.86% |    2 |  3.15% |    18710 | nd@syndicat.com
  2.86% |    2 |  2.88% |    17080 | dwing@cisco.com
  2.86% |    2 |  2.67% |    15827 | marka@isc.org
  2.86% |    2 |  2.45% |    14568 | adrian@olddog.co.uk
  2.86% |    2 |  2.33% |    13846 | jelte.jansen@sidn.nl
  1.43% |    1 |  2.40% |    14261 | tnadeau@lucidvision.com
  1.43% |    1 |  2.13% |    12646 | hsantos@isdg.net
  1.43% |    1 |  1.97% |    11666 | peter@akayla.com
  1.43% |    1 |  1.96% |    11623 | jari.arkko@piuha.net
  1.43% |    1 |  1.95% |    11557 | rjsparks@nostrum.com
  1.43% |    1 |  1.79% |    10639 | floris.vandenabeele@intec.ugent.be
  1.43% |    1 |  1.76% |    10447 | john-ietf@jck.com
  1.43% |    1 |  1.54% |     9129 | marcph@getjive.com
  1.43% |    1 |  1.42% |     8451 | ynir.ietf@gmail.com
  1.43% |    1 |  1.42% |     8440 | narten@us.ibm.com
  1.43% |    1 |  1.38% |     8177 | listsebby@me.com
  1.43% |    1 |  1.37% |     8161 | farmer@umn.edu
  1.43% |    1 |  1.26% |     7484 | mcr+nomcom@sandelman.ca
  1.43% |    1 |  1.25% |     7444 | flyingkiwiguy@gmail.com
  1.43% |    1 |  1.16% |     6878 | brian.e.carpenter@gmail.com
  1.43% |    1 |  1.11% |     6581 | joelja@bogus.com
  1.43% |    1 |  1.09% |     6481 | lee@asgard.org
  1.43% |    1 |  1.08% |     6384 | michel@arneill-py.sacramento.ca.us
  1.43% |    1 |  1.00% |     5932 | thierry.moreau@connotech.com
  1.43% |    1 |  0.99% |     5887 | cabo@tzi.org
  1.43% |    1 |  0.96% |     5698 | ben@nostrum.com
  1.43% |    1 |  0.78% |     4650 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |   70 |100.00% |   593579 | Total


From nobody Fri Jun 27 03:50:43 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 265D51B2AB1 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 03:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
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 IKiNEwJAbAi3 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 03:50:40 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA1D21B2A83 for <ietf@ietf.org>; Fri, 27 Jun 2014 03:50:39 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 117423B7DA; Fri, 27 Jun 2014 12:50:38 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id EDA5FF008D1; Fri, 27 Jun 2014 12:50:28 +0200 (CEST)
Date: Fri, 27 Jun 2014 12:50:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: ietf.org now DNSSEC-bogus :-(
Message-ID: <20140627105028.GA30447@laperouse.bortzmeyer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Transport: UUCP rules
X-Operating-System: Ubuntu 14.04 (trusty)
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SG4w5zxoZQLd1odrnHkV-eXau6c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 10:50:42 -0000

[Sent by using a mail server with a non-validating resolver...]

The delegation at .org still indicates the old name servers but the
zone contains the new ones, at Cloudflare.

% dig @ns0.amsl.com. NS ietf.org

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @ns0.amsl.com. NS ietf.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51586
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;ietf.org.		IN NS

;; ANSWER SECTION:
ietf.org.		1800 IN	NS jack.ns.cloudflare.com.
ietf.org.		1800 IN	NS dora.ns.cloudflare.com.
ietf.org.		1800 IN	RRSIG NS 5 2 1800 20150627101542 (
				20140627091717 40452 ietf.org.
				cGLMaGJyWGuBsUJ43Ot5c1N8A0pe0DYpML2qhnCdvWAv
				SAiuyejFv0yjSXT2dAA4gM/lRMw6Ii07wus1S7GKAcS3
				df2Rr2ltVxl3NWvo7cKXVAQN59QL2Er2G0J71zEBwMZu
				dx6UznWSBWf9IrNvDn6VHZkUzKOxcExtnOgV9iwk3Pef
				UfJpvHelQXo4DgYI5a2wCpuLcljLfb62GYu/N4vLYOLB
				hGxyygvDnCriYSGFlVO7bhqA6bFbZWK/g8G26zEqE+ix
				+XjkiV9hBR1xSadgiqPi28sBAFy+zyvVrrkracgzFGzC
				5Jz2dAE+c6Haw8Es74sizo3VZ7M5tnKU+w== )

;; Query time: 75 msec
;; SERVER: 64.170.98.2#53(64.170.98.2)
;; WHEN: Fri Jun 27 12:46:31 2014
;; MSG SIZE  rcvd: 388

The cloudflare name servers does not server RRSIG or DNSKEY :-(

% dig @jack.ns.cloudflare.com. DNSKEY ietf.org

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @jack.ns.cloudflare.com. DNSKEY ietf.org
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29097
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;ietf.org.		IN DNSKEY

;; AUTHORITY SECTION:
ietf.org.		86400 IN SOA dora.ns.cloudflare.com. dns.cloudflare.com. (
				2015553176 ; serial
				10000      ; refresh (2 hours 46 minutes 40 seconds)
				2400       ; retry (40 minutes)
				604800     ; expire (1 week)
				3600       ; minimum (1 hour)
				)

;; Query time: 8 msec
;; SERVER: 2400:cb00:2049:1::adf5:3b79#53(2400:cb00:2049:1::adf5:3b79)
;; WHEN: Fri Jun 27 12:49:46 2014
;; MSG SIZE  rcvd: 99


From nobody Fri Jun 27 03:52:43 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5732A1B2CCA for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 03:52:41 -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] autolearn=ham
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 gxm3_yZ2rr92 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 03:52:39 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DBE71B2A83 for <ietf@ietf.org>; Fri, 27 Jun 2014 03:52:39 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id A11013B7DA; Fri, 27 Jun 2014 12:52:37 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id 55481F008D1; Fri, 27 Jun 2014 12:52:28 +0200 (CEST)
Date: Fri, 27 Jun 2014 12:52:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: ietf.org now DNSSEC-bogus :-(
Message-ID: <20140627105228.GA30699@laperouse.bortzmeyer.org>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140627105028.GA30447@laperouse.bortzmeyer.org>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 14.04 (trusty)
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/C_q6Ua2fbgdDmVbiwet6BLjnIF0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 10:52:41 -0000

On Fri, Jun 27, 2014 at 12:50:28PM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 69 lines which said:

> [Sent by using a mail server with a non-validating resolver...]
> 
> The delegation at .org still indicates the old name servers but the
> zone contains the new ones, at Cloudflare.

http://dnsviz.net/d/ietf.org/U61LsA/dnssec/


From nobody Fri Jun 27 04:02:27 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 829A91B2B4B for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 04:02:26 -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] autolearn=ham
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 lwJnJvnPM59B for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 04:02:24 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 107FD1B2B29 for <ietf@ietf.org>; Fri, 27 Jun 2014 04:02:04 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id BB2A63B7DA; Fri, 27 Jun 2014 13:02:02 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id B89EBF008D1; Fri, 27 Jun 2014 12:56:02 +0200 (CEST)
Date: Fri, 27 Jun 2014 12:56:02 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: ietf.org now DNSSEC-bogus :-(
Message-ID: <20140627105602.GA31049@laperouse.bortzmeyer.org>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140627105028.GA30447@laperouse.bortzmeyer.org>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 14.04 (trusty)
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0yCRV6zaUwXftNItv0IqAnQ08Kk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 11:02:26 -0000

On Fri, Jun 27, 2014 at 12:50:28PM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 69 lines which said:

> [Sent by using a mail server with a non-validating resolver...]
> 
> The delegation at .org still indicates the old name servers but the
> zone contains the new ones, at Cloudflare.

Ticket [www.ietf.org/rt #66469] by the way.


From nobody Fri Jun 27 07:51:27 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA911B31A3 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 07:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 2cim-TwXWhIJ for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 07:51:22 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 379761B2D2A for <ietf@ietf.org>; Fri, 27 Jun 2014 07:51:21 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hy4so5180035vcb.20 for <ietf@ietf.org>; Fri, 27 Jun 2014 07:51:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=u7shCuO5BzS/20S+pPA/4YequlkbWqB3D4aMQhog60U=; b=tNvU9ndU570XPfYd97SeAQ4eCbOF3UkfMPzVvljH/UZJ5xlFFwh4hk44YSKkkHnQGh upTmyxLoA8qlaRHilS/BmIEyJWZMW7ijNGzu9H8cfsDqzqwMahyex8VSknoXBV+KmENc Pvr7i5/5S6vZdm+gDN3J711CxwOtK0flEu8D0u7IsV4BpCZw8dflhca6a6xm+CG3eMyB IhpjdUCSiONy7wtjoMlOpEmuegxn1wCmiKE9GVALgm3CyCTCdA8nlVdpfYwQDbAgN/dp Lld/kEkz3pp7zacSMKKfUYqhv8Ib7b5xkOZiuGuzroniTC1JR5Chuxd3WUmSs9ovAG6x t/rA==
MIME-Version: 1.0
X-Received: by 10.52.248.146 with SMTP id ym18mr17129094vdc.8.1403880680330; Fri, 27 Jun 2014 07:51:20 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.58.106.202 with HTTP; Fri, 27 Jun 2014 07:51:20 -0700 (PDT)
In-Reply-To: <20140627105602.GA31049@laperouse.bortzmeyer.org>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org> <20140627105602.GA31049@laperouse.bortzmeyer.org>
Date: Fri, 27 Jun 2014 10:51:20 -0400
X-Google-Sender-Auth: N5xLh2nZCl5EqBJRU6yTLGbpzfY
Message-ID: <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com>
Subject: Re: ietf.org now DNSSEC-bogus :-(
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jm3hU-r-PdO06HIjiT5HSc6hhpk
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 14:51:24 -0000

;; QUESTION SECTION:
;ietf.org.                      IN      NS

;; ANSWER SECTION:
ietf.org.               1773    IN      NS      ns1.mia1.afilias-nst.info.
ietf.org.               1773    IN      NS      ns1.hkg1.afilias-nst.info.
ietf.org.               1773    IN      NS      ns1.yyz1.afilias-nst.info.
ietf.org.               1773    IN      NS      ns1.ams1.afilias-nst.info.
ietf.org.               1773    IN      NS      ns1.sea1.afilias-nst.info.
ietf.org.               1773    IN      NS      ns0.amsl.com.

maybe fixed now?

http://dnsviz.net/d/ietf.org/dnssec/

seems to also indicate fix action has taken place.

On Fri, Jun 27, 2014 at 6:56 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> On Fri, Jun 27, 2014 at 12:50:28PM +0200,
>  Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote
>  a message of 69 lines which said:
>
>> [Sent by using a mail server with a non-validating resolver...]
>>
>> The delegation at .org still indicates the old name servers but the
>> zone contains the new ones, at Cloudflare.
>
> Ticket [www.ietf.org/rt #66469] by the way.
>


From nobody Fri Jun 27 07:57:44 2014
Return-Path: <shuque@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7DF1B2B5F for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 07:57:43 -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, SPF_PASS=-0.001] autolearn=ham
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 prXuvCwZlIUm for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 07:57:41 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFA11B2DD7 for <ietf@ietf.org>; Fri, 27 Jun 2014 07:57:29 -0700 (PDT)
Received: by mail-ig0-f177.google.com with SMTP id c1so2031887igq.10 for <ietf@ietf.org>; Fri, 27 Jun 2014 07:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=TZ+VUflzxtszlRQZsuJsH7a+ZvG+/v5cV7nCxut/A0U=; b=JjlSdsE5/8i6MmIjNZQvdAEnjid9GXXmuhcx2c2vvcgQk20lLHNBv7vG+8fVHvxKKN em3nSBE0Ht1N95YA8dQj9hI4+ddVsQJeF2ar4VMTG8MBRqRRDNnvDmPh+LtFyk6GHh0f p73jKcy1LTsCI564Z6OvP0flWfXLhCf+W6TW7nEXU/UyPDHW9ak99/vRv2kt9gxb+EMk 5S4ug60d0X1mqgXPekoqEoH/qmvWw712RCzD6IWlZ17oKOs3l8vuT8YSDPEm0ePTHllo 7MZJmmpZjL/R7ovqdvA+VZFVVihk7yTjY7+HsRiMEVQTJzQaQ92eFZUJjEgZBpqe6xGK 2pww==
MIME-Version: 1.0
X-Received: by 10.50.39.45 with SMTP id m13mr13154148igk.1.1403881049090; Fri, 27 Jun 2014 07:57:29 -0700 (PDT)
Received: by 10.64.13.193 with HTTP; Fri, 27 Jun 2014 07:57:29 -0700 (PDT)
In-Reply-To: <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org> <20140627105602.GA31049@laperouse.bortzmeyer.org> <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com>
Date: Fri, 27 Jun 2014 10:57:29 -0400
Message-ID: <CAHPuVdXxLrDoOKpr8NWQ+av6fKVYzSkK4RAqkX-scZdKTCXAdA@mail.gmail.com>
Subject: Re: ietf.org now DNSSEC-bogus :-(
From: Shumon Huque <shuque@gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc131e3cf27d04fcd287fd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bYqGxn_Ujcwlo7nKTtzmxAK4mDo
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: shuque@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 14:57:43 -0000

--047d7bdc131e3cf27d04fcd287fd
Content-Type: text/plain; charset=UTF-8

There is still another problem that arguably needs to be addressed.

The IETF website (www.ietf.org) is now aliased to Cloudflare zones that
don't do DNSSEC. So
validating resolvers querying the IETF website, www.ietf.org will not be
able to authenticate the result. The AD bit won't be set because the answer
section includes A/AAAA records without signatures.

--Shumon.



On Fri, Jun 27, 2014 at 10:51 AM, Christopher Morrow <
morrowc.lists@gmail.com> wrote:

> ;; QUESTION SECTION:
> ;ietf.org.                      IN      NS
>
> ;; ANSWER SECTION:
> ietf.org.               1773    IN      NS      ns1.mia1.afilias-nst.info.
> ietf.org.               1773    IN      NS      ns1.hkg1.afilias-nst.info.
> ietf.org.               1773    IN      NS      ns1.yyz1.afilias-nst.info.
> ietf.org.               1773    IN      NS      ns1.ams1.afilias-nst.info.
> ietf.org.               1773    IN      NS      ns1.sea1.afilias-nst.info.
> ietf.org.               1773    IN      NS      ns0.amsl.com.
>
> maybe fixed now?
>
> http://dnsviz.net/d/ietf.org/dnssec/
>
> seems to also indicate fix action has taken place.
>
> On Fri, Jun 27, 2014 at 6:56 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
> wrote:
> > On Fri, Jun 27, 2014 at 12:50:28PM +0200,
> >  Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote
> >  a message of 69 lines which said:
> >
> >> [Sent by using a mail server with a non-validating resolver...]
> >>
> >> The delegation at .org still indicates the old name servers but the
> >> zone contains the new ones, at Cloudflare.
> >
> > Ticket [www.ietf.org/rt #66469] by the way.
> >
>
>

--047d7bdc131e3cf27d04fcd287fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>There is still another problem that arguably nee=
ds to be addressed.<br><br></div><div>The IETF website (<a href=3D"http://w=
ww.ietf.org">www.ietf.org</a>) is now aliased to Cloudflare zones that don&=
#39;t do DNSSEC. So <br>
</div>validating resolvers querying the IETF website, <a href=3D"http://www=
.ietf.org">www.ietf.org</a> will not be able to authenticate the result. Th=
e AD bit won&#39;t be set because the answer section includes A/AAAA record=
s without signatures.<br>
<br></div>--Shumon.<br><br></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Jun 27, 2014 at 10:51 AM, Christopher Morrow <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:morrowc.lists@gmail.com" target=3D"_b=
lank">morrowc.lists@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">;; QUESTION SECTION:<br>
;<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IN =C2=A0 =C2=
=A0 =C2=A0NS<br>
<br>
;; ANSWER SECTION:<br>
</div><a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=
=A0 =C2=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns1.mia1.afilias-nst.inf=
o" target=3D"_blank">ns1.mia1.afilias-nst.info</a>.<br>
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=A0 =C2=
=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns1.hkg1.afilias-nst.info" targ=
et=3D"_blank">ns1.hkg1.afilias-nst.info</a>.<br>
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=A0 =C2=
=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns1.yyz1.afilias-nst.info" targ=
et=3D"_blank">ns1.yyz1.afilias-nst.info</a>.<br>
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=A0 =C2=
=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns1.ams1.afilias-nst.info" targ=
et=3D"_blank">ns1.ams1.afilias-nst.info</a>.<br>
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=A0 =C2=
=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns1.sea1.afilias-nst.info" targ=
et=3D"_blank">ns1.sea1.afilias-nst.info</a>.<br>
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>. =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1773 =C2=A0 =C2=A0IN =C2=A0 =C2=A0 =C2=
=A0NS =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ns0.amsl.com" target=3D"_blank"=
>ns0.amsl.com</a>.<br>
<br>
maybe fixed now?<br>
<br>
<a href=3D"http://dnsviz.net/d/ietf.org/dnssec/" target=3D"_blank">http://d=
nsviz.net/d/ietf.org/dnssec/</a><br>
<br>
seems to also indicate fix action has taken place.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Fri, Jun 27, 2014 at 6:56 AM, Stephane Bortzmeyer &lt;<a href=3D"mailto:=
bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt; wrote:<br>
&gt; On Fri, Jun 27, 2014 at 12:50:28PM +0200,<br>
&gt; =C2=A0Stephane Bortzmeyer &lt;<a href=3D"mailto:bortzmeyer@nic.fr">bor=
tzmeyer@nic.fr</a>&gt; wrote<br>
&gt; =C2=A0a message of 69 lines which said:<br>
&gt;<br>
&gt;&gt; [Sent by using a mail server with a non-validating resolver...]<br=
>
&gt;&gt;<br>
&gt;&gt; The delegation at .org still indicates the old name servers but th=
e<br>
&gt;&gt; zone contains the new ones, at Cloudflare.<br>
&gt;<br>
&gt; Ticket [<a href=3D"http://www.ietf.org/rt" target=3D"_blank">www.ietf.=
org/rt</a> #66469] by the way.<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--047d7bdc131e3cf27d04fcd287fd--


From nobody Fri Jun 27 09:22:42 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5E01B3211 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 09:22:40 -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] autolearn=ham
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 6lZo50pvrEw4 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 09:22:39 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D984E1B2B44 for <ietf@ietf.org>; Fri, 27 Jun 2014 09:22:38 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 0613E3B8AD; Fri, 27 Jun 2014 18:22:35 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id 95369F008BE; Fri, 27 Jun 2014 18:22:24 +0200 (CEST)
Date: Fri, 27 Jun 2014 18:22:24 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: ietf.org now DNSSEC-bogus :-(
Message-ID: <20140627162224.GA6759@laperouse.bortzmeyer.org>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org> <20140627105602.GA31049@laperouse.bortzmeyer.org> <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 14.04 (trusty)
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EYfcr65Q7E7An-GJ3xNQCftcG3M
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 16:22:40 -0000

On Fri, Jun 27, 2014 at 10:51:20AM -0400,
 Christopher Morrow <morrowc.lists@gmail.com> wrote 
 a message of 29 lines which said:

> maybe fixed now?

Yes, back to the correct name servers. See what happened during the problem:

http://dnsviz.net/d/ietf.org/U61S3A/dnssec/


From nobody Fri Jun 27 10:10:24 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0043E1B28E6 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 10:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 WV_pNcF-UVrN for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 10:10:19 -0700 (PDT)
Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FBC61B28B9 for <ietf@ietf.org>; Fri, 27 Jun 2014 10:10:19 -0700 (PDT)
Received: by mail-yk0-f181.google.com with SMTP id 9so3046152ykp.12 for <ietf@ietf.org>; Fri, 27 Jun 2014 10:10:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=hRXn5q1Yw37AXRXaTVwmZy0yRtwlIJYOI79znemmX5o=; b=buX8pWrtd/KJn4s9AwRbhGfWxVWPkEC2g8UOu7+w8KF/fxyndvf/63cJtr285uJIXS hdqfKXhA10yFTMvyzE65mBb8jE0VccDTTd4tfAIdx/YHcW4+4EaV8BY58Ji2tLs6yJaS 6Fqyhxob5WHKT2ypoYAuQ3aCOWSq4djXRzObfwXXp96bxbOXInu/3Ch4I1YErNdK/MlI 3yGahfxB0lkJlHVk+wC7ZJha0apERYCudXz3XgCTwK/R4ynLCLxrfLIHirj/Ardiu3CM vLpVCbnkS4X3VQ6DccrVWtUPvN7jZJSEXAMCgS1DGiXJ+Szo4znwgi4hatnkuGXnmpQ9 e2Cg==
X-Received: by 10.236.66.70 with SMTP id g46mr4462251yhd.159.1403889018540; Fri, 27 Jun 2014 10:10:18 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.139.215 with HTTP; Fri, 27 Jun 2014 10:09:38 -0700 (PDT)
In-Reply-To: <20140627162224.GA6759@laperouse.bortzmeyer.org>
References: <20140627105028.GA30447@laperouse.bortzmeyer.org> <20140627105602.GA31049@laperouse.bortzmeyer.org> <CAL9jLaaMVk+gzT9+4UKCiRm8XyfaFvpgtPdhzZ=eHJw=Rf4-pQ@mail.gmail.com> <20140627162224.GA6759@laperouse.bortzmeyer.org>
From: Dick Franks <rwfranks@acm.org>
Date: Fri, 27 Jun 2014 18:09:38 +0100
X-Google-Sender-Auth: I5mUAX2D6GX4iMF2MRPJOm7nRTo
Message-ID: <CAKW6Ri6gUh8NMYLje6d6EJggZ=E4hJ5uHrx3ZJM4g7KTK5dWAQ@mail.gmail.com>
Subject: Re: ietf.org now DNSSEC-bogus :-(
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=089e013a160e4117bb04fcd46233
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/89m_uwFb-igjKKRd3u3ER1FpfnU
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 17:10:21 -0000

--089e013a160e4117bb04fcd46233
Content-Type: text/plain; charset=UTF-8

Possibly an IPv6 routing issue here too.
Both nameservers affected, and have common address prefix, so it is all or
nothing.


cloudflare.net.    86259    IN    SOA    fred.ns.cloudflare.com.
dns.cloudflare.com. (
                    2014904817    ;serial
                    10000        ;refresh
                    2400        ;retry
                    604800        ;expire
                    3600    )    ;minimum
www.ietf.org.    1658    IN    RRSIG    CNAME 5 3 1800 (
    20150627140549 20140627130739 40452 ietf.org.
    Oggxi8gGJxwg0n+ ...
www.ietf.org.    1658    IN    CNAME    www.ietf.org.cdn.cloudflare.net.
----

[1]*    fred.ns.cloudflare.com  [173.245.59.113]
            zone serial    2014904817

[1]*    fred.ns.cloudflare.com  [2400:cb00:2049:1:0:0:adf5:3b71]
### no response

[2]    jean.ns.cloudflare.com  [173.245.58.121]
            zone serial    2014904817

[2]    jean.ns.cloudflare.com  [2400:cb00:2049:1:0:0:adf5:3a79]
### no response

Unsatisfactory response from 2 nameservers

________________________



On 27 June 2014 17:22, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> On Fri, Jun 27, 2014 at 10:51:20AM -0400,
>  Christopher Morrow <morrowc.lists@gmail.com> wrote
>  a message of 29 lines which said:
>
> > maybe fixed now?
>
> Yes, back to the correct name servers. See what happened during the
> problem:
>
> http://dnsviz.net/d/ietf.org/U61S3A/dnssec/
>
>

--089e013a160e4117bb04fcd46233
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Possibly an IPv6 routing issue here too.<br></div>Bot=
h nameservers affected, and have common address prefix, so it is all or not=
hing.<br><div><div><br><br></div></div><div class=3D"gmail_extra"><a href=
=3D"http://cloudflare.net">cloudflare.net</a>.=C2=A0=C2=A0=C2=A0 86259=C2=
=A0=C2=A0=C2=A0 IN=C2=A0=C2=A0=C2=A0 SOA=C2=A0=C2=A0=C2=A0 <a href=3D"http:=
//fred.ns.cloudflare.com">fred.ns.cloudflare.com</a>. <a href=3D"http://dns=
.cloudflare.com">dns.cloudflare.com</a>. (<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 2014904817=C2=A0=C2=A0=C2=A0 ;serial<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 10000=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 ;refresh<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 2400=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 ;retry<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 604800=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 ;expire<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 3600=C2=A0=C2=A0=C2=A0 )=C2=A0=C2=A0=C2=A0 ;minimum<br>

<a href=3D"http://www.ietf.org">www.ietf.org</a>.=C2=A0=C2=A0=C2=A0 1658=C2=
=A0=C2=A0=C2=A0 IN=C2=A0=C2=A0=C2=A0 RRSIG=C2=A0=C2=A0=C2=A0 CNAME 5 3 1800=
 (<br>=C2=A0=C2=A0=C2=A0 20150627140549 20140627130739 40452 <a href=3D"htt=
p://ietf.org">ietf.org</a>.<br>=C2=A0=C2=A0=C2=A0 Oggxi8gGJxwg0n+ ...<br><a=
 href=3D"http://www.ietf.org">www.ietf.org</a>.=C2=A0=C2=A0=C2=A0 1658=C2=
=A0=C2=A0=C2=A0 IN=C2=A0=C2=A0=C2=A0 CNAME=C2=A0=C2=A0=C2=A0 <a href=3D"htt=
p://www.ietf.org.cdn.cloudflare.net">www.ietf.org.cdn.cloudflare.net</a>.<b=
r>

----<br><br>[1]*=C2=A0=C2=A0=C2=A0 <a href=3D"http://fred.ns.cloudflare.com=
">fred.ns.cloudflare.com</a>=C2=A0 [173.245.59.113]<br>=C2=A0=C2=A0=C2=A0 =
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 zone serial=C2=A0=C2=A0=C2=A0 2014904=
817<br><br>[1]*=C2=A0=C2=A0=C2=A0 <a href=3D"http://fred.ns.cloudflare.com"=
>fred.ns.cloudflare.com</a>=C2=A0 [2400:cb00:2049:1:0:0:adf5:3b71]<br>

### no response<br><br>[2]=C2=A0=C2=A0=C2=A0 <a href=3D"http://jean.ns.clou=
dflare.com">jean.ns.cloudflare.com</a>=C2=A0 [173.245.58.121]<br>=C2=A0=C2=
=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 zone serial=C2=A0=C2=A0=C2=
=A0 2014904817<br><br>[2]=C2=A0=C2=A0=C2=A0 <a href=3D"http://jean.ns.cloud=
flare.com">jean.ns.cloudflare.com</a>=C2=A0 [2400:cb00:2049:1:0:0:adf5:3a79=
]<br>

### no response<br><br>Unsatisfactory response from 2 nameservers<br><div><=
br><div><div dir=3D"ltr"><span><font color=3D"#888888">____________________=
____<br>
</font></span><br></div></div>
</div>
<br><br><div class=3D"gmail_quote">On 27 June 2014 17:22, Stephane Bortzmey=
er <span dir=3D"ltr">&lt;<a href=3D"mailto:bortzmeyer@nic.fr" target=3D"_bl=
ank">bortzmeyer@nic.fr</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

On Fri, Jun 27, 2014 at 10:51:20AM -0400,<br>
=C2=A0Christopher Morrow &lt;<a href=3D"mailto:morrowc.lists@gmail.com">mor=
rowc.lists@gmail.com</a>&gt; wrote<br>
=C2=A0a message of 29 lines which said:<br>
<br>
&gt; maybe fixed now?<br>
<br>
Yes, back to the correct name servers. See what happened during the problem=
:<br>
<br>
<a href=3D"http://dnsviz.net/d/ietf.org/U61S3A/dnssec/" target=3D"_blank">h=
ttp://dnsviz.net/d/ietf.org/U61S3A/dnssec/</a><br>
<br>
</blockquote></div><br></div></div>

--089e013a160e4117bb04fcd46233--


From nobody Fri Jun 27 11:12:44 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830FE1A041C for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 P-ghs2Cypc11 for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:12:41 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44E971B27ED for <ietf@ietf.org>; Fri, 27 Jun 2014 11:12:39 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 22450200E9; Fri, 27 Jun 2014 13:56:52 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id ACA2163B24; Tue, 24 Jun 2014 13:23:06 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9A0E263AED; Tue, 24 Jun 2014 13:23:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Time to move beyond the 32 bit Internet.
In-Reply-To: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 24 Jun 2014 13:23:06 -0400
Message-ID: <23312.1403630586@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cUd0_CS5lWVqe5zfYmCdbvxEHpQ
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 18:12:42 -0000

--=-=-=


Phillip Hallam-Baker <phill@hallambaker.com> wrote:
    > So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is your
    > Internet service 32 bit or 128'?

Good idea.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU6mz+oCLcPvd0N1lAQJgjwf/RZ7qaqOFVYiJE6P/hXgccdZdiUfX3Lwa
5oO67ReKrKJYeSd8XNEU9YFtbF12m1Z+m2S2wDnHcaG1S/ao1GtDLli+cP/eFv8y
TvfccpdVw9lnXz94qO4xhX8+V5N/xqDX5ZVyT6c9qrlUSvZnhtMKjaju8GNooWeK
kIxMZXKNZUnTWUrqrodXAeGGgUoJB0rmRA44iqE3CH+MSggpRGUD8EhkZgyTQFPp
fTWSBsF++TbOk7L/HehI022iA2y1bcuBCPlLwsqyBPClHJDQrT7ZrGEi+v6MADIb
RmVvq7w6NTx2myEVpvU/c7x9NIOjK5t7/oQw1FO+5Zqu0HfoHy0T1Q==
=rsa6
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun 27 13:42:33 2014
Return-Path: <rajeev.koodli@intel.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2D621B29DB; Fri, 27 Jun 2014 10:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.252
X-Spam-Level: 
X-Spam-Status: No, score=-5.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 tq5gsgqVzLW9; Fri, 27 Jun 2014 10:33:26 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id CF4411B29A0; Fri, 27 Jun 2014 10:33:24 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 27 Jun 2014 10:33:24 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.01,561,1400050800"; d="scan'208";a="450839665"
Received: from fmsmsx108.amr.corp.intel.com ([10.19.9.228]) by azsmga001.ch.intel.com with ESMTP; 27 Jun 2014 10:33:14 -0700
Received: from fmsmsx102.amr.corp.intel.com (10.19.9.53) by FMSMSX108.amr.corp.intel.com (10.19.9.228) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 27 Jun 2014 10:33:12 -0700
Received: from fmsmsx105.amr.corp.intel.com ([169.254.5.225]) by FMSMSX102.amr.corp.intel.com ([169.254.2.147]) with mapi id 14.03.0123.003; Fri, 27 Jun 2014 10:33:12 -0700
From: "Koodli, Rajeev" <rajeev.koodli@intel.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-netext-wifi-epc-eap-attributes.all@tools.ietf.org" <draft-ietf-netext-wifi-epc-eap-attributes.all@tools.ietf.org>
Subject: Re: Gen-ART LC review of draft-ietf-netext-wifi-epc-eap-attributes-08
Thread-Topic: Gen-ART LC review of draft-ietf-netext-wifi-epc-eap-attributes-08
Thread-Index: Ac+QO5sTsbQV2OmnSEa9W+i3m4dC9QB8kSMA
Date: Fri, 27 Jun 2014 17:33:11 +0000
Message-ID: <CFD2F17F.14A6%rajeev.koodli@intel.com>
References: <08eb01cf9044$893c73d0$9bb55b70$@akayla.com>
In-Reply-To: <08eb01cf9044$893c73d0$9bb55b70$@akayla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.254.45.52]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <926D1E2B39DD244C80616ECF9800D532@intel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mJwk5PVlHGPWyi5SS0kCdZv6_Og
X-Mailman-Approved-At: Fri, 27 Jun 2014 13:42:31 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 17:33:29 -0000

Hi Peter,

Thanks for the review.

Please see inline:


On 6/25/14, 12:10 AM, "Peter Yee" <peter@akayla.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
>Please resolve these comments along with any other Last Call comments you
>may receive.
>
>Document: draft-ietf-netext-wifi-epc-eap-attributes-08
>Reviewer: Peter Yee
>Review Date: June-24-2014
>IETF LC End Date: June-24-2014
>IESG Telechat date: TBD
>
>Summary: This draft is basically ready for publication as an Informational
>RFC, but has some nits that should be fixed before publication. [Ready
>with
>nits.]

Okay.

>
>The draft could do with some language cleanup, but otherwise appears fine
>for publication.
>
>Questions:
>
>Page 8, Section 5.2, 2nd paragraph, last sentence: by "present" do you
>mean
>the presence of the Type field itself or the presence of a Type field
>value?
>I believe you mean the latter, in which case you may wish to add "value"
>after "Type field".

Right, Type value. Will revise.

>
>Page 11, Section 5.5, diagram: the session ID would seem to run longer
>than
>32 bits in some cases.  For example, I understand a GUTI to be 62 bits (30
>bits of GUMMEI plus 32 bits of M-TMSI).  Should the diagram be modified to
>reflect the variable length?

Fair enough.


>
>General:
>
>Replace "WiFi" with "Wi-Fi" throughout the document to align with the
>preferred usage of the name as given by the Wi-Fi Alliance.

Ok.

>
>Expand acronyms on first use unless they are blazingly obvious in this
>context.  Consider citing their references for clarity.
>
>Replace "a MN" with "an MN" throughout the document.
>
>Determine if RFC 2119 language is really necessary in this document and
>then
>use it (or not) consistently.  There are SHOULDs and shalls (lower case).
>
>Leave URLs out of RFC references; they aren't included in the current
>reference format.
>
>Not all the attributes defined in Section 5 are discussed in Section 4.
>Is
>this expected or desirable?

Will add some description in Section 4.

Thanks for the thorough review below. It=B9s helpful. Will revise, and let
you know if I disagree on anything.

Regards,

-Rajeev



>
>Nits:
>
>Page 1, Abstract, 1st paragraph, 2nd sentence: append a comma after
>"connections".
>
>Page 2, Introduction, 1st paragraph, 3rd sentence: change "the functions"
>to
>"these functions".
>
>Page 2, Introduction, 1st paragraph, 5th sentence: change "indicates" to
>"requests", unless this 3GPP's terminology for a requesting a new IP
>session.
>
>Page 3, paragraph after the bullet points, 1st sentence: replace "and"
>before "EAP-SIM" with a comma.
>
>Page 3, paragraph after the bullet points, last sentence: append a comma
>after "4G".
>
>Page 3, Section 1.1, 1st paragraph, 2nd sentence: change "it's" to "its".
>
>Page 3, Section 1.1, 1st paragraph, 4th sentence: change "internet" to
>"Internet" unless you really mean lower case "internet".
>
>Page 3, Section 1.1., 1st paragraph, 4th sentence: insert "a" before
>"user".
>
>Page 3, Section 1.1, 2nd paragraph, 2nd sentence: change "attributes" to
>"attribute".
>
>Page 3, Section 1.2, 2nd sentence: replace "Additional" with "additional"
>in
>both places to match 3GPP usage.
>
>Page 4, Section 1.3, 1st sentence: replace "it's" with "its".
>
>Page 4, Section 1.3, 1st sentence: insert "network" between "access" and
>"to".
>
>Page 4, Section 1.3, 2nd sentence: insert "a" before "3GPP".
>
>Page 4, Section 1.3, 3rd sentence: change "from" to "using" and delete the
>subsequent "the".
>
>Page 4, Section 1.3, last sentence: expand the acronym "RAN".  Note that
>3GPP and IEEE 802 usage of the acronym differs.
>
>Page 5, Section 3.2, 2nd paragraph, 2nd sentence: change "it's" to "its".
>
>Page 5, Section 3.2, 2nd paragraph, 2nd sentence: insert "an" before the
>first occurrence of "MN".
>
>Page 5, Section 3.2, 2nd paragraph, 2nd sentence: insert "the" before the
>second occurrence of "MN" and replace the following "credentials" with
>"identity".  The credentials are used to prove the identity that was
>communicated.
>
>Page 6, first bullet item, last sentence: insert "the" before "MAG".
>
>Page 6, "Call Flow Description": a whole host of definite and indefinite
>articles is missing.  They're simply too numerous for me to what to list
>them individually.  Review the section and insert articles as appropriate
>to
>aid readability.
>
>Page 6, "Call Flow Description", item 1: end the sentence with a period.
>
>Page 6, "Call Flow Description", item 2: append a period to the sentence.
>
>Page 6, "Call Flow Description", item 6:  replace "it's" with "its".
>
>Page 6, "Call Flow Description", item 7:  replace "it's" with "its".  Come
>to think of it, just do a global search-and-replace for "it's".
>
>Page 6, "Call Flow Description", item 10: move the comma after "etc." to
>before it.
>
>Page 7, Section 4.1, 1st paragraph: insert "the" before
>"AT_VIRTUAL_NETWORK_ID"; insert "the" before "EAP-Response/AKA-Challenge".
>
>Page 7, Section 4.1, 2nd paragraph, 1st sentence: insert "the" before
>"AT_VIRTUAL_NETWORK_ID"; insert "the" before "EAP-Response/AKA-Challenge".
>
>Page 7, Section 4.2, 1st paragraph: insert "the" before "MN".
>
>Page 7, Section 4.2, 1st bullet item: eliminate the space before the
>colon.
>
>Page 7, Section 4.2, 1st bullet item, 1st sentence: insert "the" before
>"MN".
>
>Page 7, Section 4.2, 1st bullet item, 2nd sentence: insert "the" before
>"network".
>
>Page 7, Section 4.2, 2nd bullet item, 1st sentence: insert "The" before
>"MN".
>
>Page 7, Section 4.3, 1st paragraph, 1st sentence: consider replacing "A
>Mobile Node" with "An MN".
>
>Page 7, Section 4.3, 1st paragraph, 2nd sentence: insert "the" before
>"so-called".
>
>Page 8, Section 5: insert "the" before "first".
>
>Page 8, Section 5.1, Virtual Network Id definition, 1st sentence: insert
>"the" before "MN".
>
>Page 8, Section 5.2, 1st paragraph, 1st sentence: insert "an" before the
>first occurrent of "MN"; insert "the" before the second.
>
>Page 8, Section 5.2, 2nd paragraph, 3rd sentence: insert "the" before
>"MN's".
>
>Page 9, Virt-Net-Req Type, 3rd bullet item: insert "the" before
>"Connectivity".
>
>Page 9, Section 5.3: consider moving this section to after Section 5.5 to
>mirror the order found in Section 4.
>
>Page 9, Section 5.3, 1st paragraph: consider changing "A Mobile Node" to
>"An
>MN".
>
>Page 10, Section 5.4, diagram: it's not apparent to me why the attribute
>length value is equal to 1 plus the session ID length.
>
>Page 10, Section 5.4, both bullet items: insert "The" or "the" before "MN"
>in all cases, as appropriate.
>
>Page 11, Section 5.5, 1st paragraph, 1st sentence: insert "an" before the
>first occurrence of "MN"; insert "a session" before "identity"; insert
>"the"
>before the second occurrence of "MN".
>
>Page 11, Section 5.5, 1st paragraph, 2nd sentence: insert "The" before
>"MN";
>replace "a" with "an" before "E-UTRAN".
>
>Page 11, Section 5.5, 1st paragraph, 3rd sentence: insert "the" before
>"MN".
>
>Page 11, last paragraph, 2nd sentence: replace "begining" with
>"beginning".
>
>Page 11, last paragraph, last sentence: insert spaces before this sentence
>to separate it from the previous one.
>
>Page 12, Section 6, 1st sentence: insert "the" before "EAP-AKA".  Delete
>"RFC 4187".  The reference should suffice.
>
>Page 12, Section 6,  2nd sentence: consider noting that some attributes
>are
>passed from the network to the MN.
>
>Page 14, EPC reference: delete the semicolon. Delete the superfluous quote
>and comma following the date.
>
>Page 14, GPRS reference: insert a closing quote after "Stage 2". Delete
>the
>superfluous quote and comma following the date.
>


From nobody Fri Jun 27 13:43:27 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F711A041C for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.733
X-Spam-Level: 
X-Spam-Status: No, score=-0.733 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_SUBJECT=1.799, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=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 BA4Qvn8dFu-r for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:01:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6762E1A03B4 for <ietf@ietf.org>; Fri, 27 Jun 2014 11:01:15 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4CBD52002A; Fri, 27 Jun 2014 14:01:28 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B164663AED; Fri, 27 Jun 2014 14:01:14 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9BBDB637FE; Fri, 27 Jun 2014 14:01:14 -0400 (EDT)
From: Michael Richardson <mcr+nomcom@sandelman.ca>
To: ietf@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 27 Jun 2014 14:01:14 -0400
Message-ID: <27170.1403892074@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Uuv04P1VMlINDeqgOCnmjlffeFQ
X-Mailman-Approved-At: Fri, 27 Jun 2014 13:43:23 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 18:01:16 -0000

--=-=-=


A number of you wrote to me over the past few days asking why I was not
acknowledging your email.  Finally, I found the problem with a stuck
DNS(sec) server.  I think it affected people who had only IPv4 NS records,
as my IPv4 network was renumbered on Monday as I returned a /25. The IPv6 was
unaffected.

My appologies for confusion created.

A number of people were marked eligible yesterday afternoon and I did
see the multiple emails about the 4 remaining duplicates.
I said that I'd post an updated list today (Friday), but I'm going to
let the various emails that got stuck filter out and see if there is
some additional tweaks that I need to make to the list.


--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU62xZ4CLcPvd0N1lAQI7dQf+IE/4JdBHYZgsbkAv1/GPB7RHm+eqZuXq
WKmM/tAQmiCLju1J+Emd4cBr1Tmls68Wpgn0//dXKg7wtiHDfZi5P9e5lkK4sYZJ
SEs1JxsWQyZOEebgGSmx39LldHEMkX3xURBLbL6AM5o2bh1/ExfDK/9QKtpzBSOa
ojuw8JUcb5OgeB2KHbofTFiPb56QhW0FsZdGxSyAqLmaZoA43EX0di5ZiCM+3EuQ
OchTkmbpgNuMLAJrP22h/n7E2G/kmoWh91MxC7Wjv7wfvTwvhWpGTPSjCXNnNx1+
267vWqgyF0qdjauwDRCLKXVlA9NpJan16WYAI/fkhUKPnbGbUswEjw==
=m7jN
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun 27 13:43:29 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE6D01AD62A for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 5OHjKQreiTBP for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:02:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A442A1A03B4 for <ietf@ietf.org>; Fri, 27 Jun 2014 11:02:39 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 08BCD200D6; Fri, 27 Jun 2014 13:56:52 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 84FC36466E; Thu, 26 Jun 2014 14:22:52 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6C2B263AED; Thu, 26 Jun 2014 14:22:52 -0400 (EDT)
From: Michael Richardson <mcr+nomcom@sandelman.ca>
To: Robert Sparks <rjsparks@nostrum.com>, ietf@ietf.org
Subject: Re: Fwd: econd draft list of qualified volunteers for 2014-2015 nomcom
In-Reply-To: <53AC52BF.5040202@nostrum.com>
References: <20140626162038.18995.71697.idtracker@ietfa.amsl.com> <53AC52BF.5040202@nostrum.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 26 Jun 2014 14:22:52 -0400
Message-ID: <5733.1403806972@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cFPCLsSGa9X_dRG58g1xbBG5YkY
X-Mailman-Approved-At: Fri, 27 Jun 2014 13:43:26 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 18:02:40 -0000

--=-=-=


Robert Sparks <rjsparks@nostrum.com> wrote:
    > I think you have the same person at 114 and 131

thank you.  Tom vs Thomas.

--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU6xk+YCLcPvd0N1lAQLZOQf/bUoEbd+hLzlNgXMgUG8iRNLuzWzj+7QV
BnK4t1DjusbMKeRWUFYAFy+MmYl37eITwzSZV/JUfMm5r/f/4Dq+PUjkM6BcWtLf
IbL0AHtVCDUJwx4pgCY+vLZnwVlCZpTY33Ps7ZUwu7mBLcRlnfCrU8PsyV1hyf22
PfOnfGmxvtr1hSinUPWOupAS3fRN1Er9N+DIvJMTgoySjXAp9s2GwsEBskh0galS
+YxVixCoR6ADgZQPgaK5ccDh/U4YpxA4Hjj5//liAm7Tji2VxD0JhMJUVL1rfDeP
xIR394A+4ZIigKx2k5wXypXtHZlTp9BxYmtep59f2ZASoPkcn8LtxA==
=3NiX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun 27 13:43:31 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26EE31B279A for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 MWGpuSXp5upz for <ietf@ietfa.amsl.com>; Fri, 27 Jun 2014 11:07:50 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DB211AD972 for <ietf@ietf.org>; Fri, 27 Jun 2014 11:07:50 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 33F06E08C; Fri, 27 Jun 2014 13:56:53 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6AEF56466C; Thu, 26 Jun 2014 14:21:04 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 56D8563AED; Thu, 26 Jun 2014 14:21:04 -0400 (EDT)
From: Michael Richardson <mcr+nomcom@sandelman.ca>
To: "Gonzalo Salgueiro \(gsalguei\)" <gsalguei@cisco.com>, ietf@ietf.org
Subject: Re: econd draft list of qualified volunteers for 2014-2015 nomcom
In-Reply-To: <92F74347-4472-42A3-BC42-82217EDF40EF@cisco.com>
References: <20140626162038.18995.71697.idtracker@ietfa.amsl.com> <92F74347-4472-42A3-BC42-82217EDF40EF@cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 26 Jun 2014 14:21:04 -0400
Message-ID: <5329.1403806864@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OEERrV_w_OMyBU7WEQ7tHDhlyws
X-Mailman-Approved-At: Fri, 27 Jun 2014 13:43:25 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 18:07:53 -0000

--=-=-=


Gonzalo Salgueiro (gsalguei) <gsalguei@cisco.com> wrote:
    > Minor note: It appears you have Russ White (Ericsson) appearing twice.

Thanks. It's pretty important to remove duplicates.
One copy came from the IETF90 form, the other directly.
I tried hard to remove the duplicates, but I guess I missed one.


--
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU6xkjYCLcPvd0N1lAQJSMQgAvI3qiYB9IVrPfsOPXgMPK6RGQiR0Oekg
Tt15DyNwcadpPnD7jDESMY0LFwE8D0DjIP7mbcVF31uXYzWmeyrwutdUjTDZh/KN
SPKof2hLNFngijjjZC52FypZQvDBW9z00XkcRUoyT/Zgu08cNYJCw6lL/umQ4XBj
ZEo2F39OYK10a6T2DFysQMKlCMsevAjQWt7sFhlKVrlDyQjv1GZyDm/dtkLJng0q
VvZks/0M153jd0l3sPdZowpHREZtN6LU74VTqayFc3Nc64uy04CqgRwf6SwVWEn1
3lGmhe7RX/s2FZd0UdT/4WJmjRL0GVA4OlRbg6eBTd9xhIG1cCzLxg==
=LaWG
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun 27 13:44:04 2014
Return-Path: <list-ietf@dragon.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 084111B2D17; Thu, 26 Jun 2014 09:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 rPUULng3nPiv; Thu, 26 Jun 2014 09:38:46 -0700 (PDT)
Received: from mail.dragon.net (mail.dragon.net [IPv6:2001:4f8:3:36::235]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24B851B2C1A; Thu, 26 Jun 2014 09:17:45 -0700 (PDT)
Received: from fafnir.remote.dragon.net (localhost [127.0.0.1]) by mail.dragon.net (Postfix) with ESMTP id DE8A537403BB; Thu, 26 Jun 2014 09:17:44 -0700 (PDT)
Received: by fafnir.remote.dragon.net (Postfix, from userid 501) id 830A43A4F30D; Thu, 26 Jun 2014 10:17:44 -0600 (MDT)
Received: from fafnir.remote.dragon.net (localhost [127.0.0.1]) by fafnir.remote.dragon.net (Postfix) with ESMTP id 821D43A4F30C; Thu, 26 Jun 2014 10:17:44 -0600 (MDT)
To: ietf@ietf.org, mcr+nomcom@sandelman.ca, NomCom Chair 2014 <nomcom-chair-2014@ietf.org>
From: Paul Ebersman <list-ietf@dragon.net>
Subject: Re: draft list of qualified volunteers for 2014-2015 nomcom
In-reply-to: <20140626151615.10019.86428.idtracker@ietfa.amsl.com>
References: <20140626151615.10019.86428.idtracker@ietfa.amsl.com>
Comments: In-reply-to NomCom Chair 2014 <nomcom-chair-2014@ietf.org> message dated "Thu, 26 Jun 2014 08:16:15 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.3; XEmacs 21.4 (patch 22)
Date: Thu, 26 Jun 2014 10:17:44 -0600
Message-Id: <20140626161744.830A43A4F30D@fafnir.remote.dragon.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gICEPdoo80_s4ZajuOxx3QSRF-M
X-Mailman-Approved-At: Fri, 27 Jun 2014 13:44:03 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 16:38:48 -0000

nc-chair> Please take a look and get in touch before July 3 if you think
nc-chair> your name should be here and it isn't (or possibly I've
nc-chair> mis-typed it...), or if you have any other questions or
nc-chair> concerns with the list.

I'd gotten an email back that I was on the list but don't seem to be
in the list included in this email.


From nobody Sun Jun 29 19:19:43 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7C01A00C2 for <ietf@ietfa.amsl.com>; Sun, 29 Jun 2014 19:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 BJgPfPLzFSLH for <ietf@ietfa.amsl.com>; Sun, 29 Jun 2014 19:19:39 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.166]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA6AE1A00BD for <ietf@ietf.org>; Sun, 29 Jun 2014 19:19:38 -0700 (PDT)
Received: from [195.245.230.131:43665] by server-6.bemta-3.messagelabs.com id 31/D6-15862-839C0B35; Mon, 30 Jun 2014 02:19:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1404094776!31949652!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22138 invoked from network); 30 Jun 2014 02:19:36 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 30 Jun 2014 02:19:36 -0000
Received: from EXHY011V.surrey.ac.uk (131.227.200.103) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 30 Jun 2014 03:19:36 +0100
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.200.4) by email365.surrey.ac.uk (131.227.200.103) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 30 Jun 2014 03:19:35 +0100
Received: from AM3PR06MB434.eurprd06.prod.outlook.com (10.242.112.17) by AM3PR06MB434.eurprd06.prod.outlook.com (10.242.112.17) with Microsoft SMTP Server (TLS) id 15.0.974.11; Mon, 30 Jun 2014 02:19:34 +0000
Received: from AM3PR06MB434.eurprd06.prod.outlook.com ([10.242.112.17]) by AM3PR06MB434.eurprd06.prod.outlook.com ([10.242.112.17]) with mapi id 15.00.0974.002; Mon, 30 Jun 2014 02:19:34 +0000
From: <l.wood@surrey.ac.uk>
To: <mcr+ietf@sandelman.ca>, <phill@hallambaker.com>
Subject: RE: Time to move beyond the 32 bit Internet.
Thread-Topic: Time to move beyond the 32 bit Internet.
Thread-Index: AQHPj8LPKDWoeHlghEiJPqzarqkrN5uAgmYAgAhwyo8=
Date: Mon, 30 Jun 2014 02:19:34 +0000
Message-ID: <1404094773482.42250@surrey.ac.uk>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com>,  <23312.1403630586@sandelman.ca>
In-Reply-To: <23312.1403630586@sandelman.ca>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [122.200.59.30]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 0258E7CCD4
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(199002)(189002)(24454002)(377454003)(105586002)(107046002)(106356001)(20776003)(50986999)(99396002)(101416001)(106116001)(76176999)(54356999)(64706001)(83322001)(19580405001)(19580395003)(21056001)(2656002)(85852003)(36756003)(87936001)(15975445006)(15202345003)(83072002)(92566001)(86362001)(81342001)(92726001)(74502001)(74482001)(74662001)(81542001)(31966008)(85306003)(95666004)(66066001)(15395725005)(80022001)(46102001)(4396001)(15198665003)(77982001)(79102001)(76482001); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR06MB434; H:AM3PR06MB434.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: AM3PR06MB434.eurprd06.prod.outlook.com
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY011v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY011v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ChnxgWOF4tBMTgt-1lfmMhRXRnk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 02:19:41 -0000

So NAPT (32bit IPv4 address + necessary 16-bit send/receive ports) must be =
64 bit?=0A=
=0A=
Lloyd Wood=0A=
http://about.me/lloydwood=0A=
________________________________________=0A=
From: ietf <ietf-bounces@ietf.org> on behalf of Michael Richardson <mcr+iet=
f@sandelman.ca>=0A=
Sent: Wednesday, 25 June 2014 3:23 AM=0A=
To: Phillip Hallam-Baker=0A=
Cc: IETF Discussion Mailing List=0A=
Subject: Re: Time to move beyond the 32 bit Internet.=0A=
=0A=
Phillip Hallam-Baker <phill@hallambaker.com> wrote:=0A=
    > So lets stop asking ISPs 'do you support IPv6' and instead ask 'Is yo=
ur=0A=
    > Internet service 32 bit or 128'?=0A=
=0A=
Good idea.=0A=
=0A=
--=0A=
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=0A=
 -=3D IPv6 IoT consulting =3D-=0A=
=0A=
=0A=
=0A=


From nobody Mon Jun 30 05:41:05 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A56CE1A02C1 for <ietf@ietfa.amsl.com>; Mon, 30 Jun 2014 05:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 PGTK7uiAmZjr for <ietf@ietfa.amsl.com>; Mon, 30 Jun 2014 05:41:02 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 444C91A02BE for <ietf@ietf.org>; Mon, 30 Jun 2014 05:40:59 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id bs8so5918643wib.15 for <ietf@ietf.org>; Mon, 30 Jun 2014 05:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZpkwfLhxRyoGNqHA5VxKJmzDjJ52raXTEtQwldlwbtc=; b=C77J2udAqh6TWpxUIpFJiukX1yeuMtJJhBLV+H1SCb+GtWRDfAZSVIxsiEfJ0pWBIq EfsUhmTLNU1oQdGWsdWbp9lrPYVwuYpTMzAhG+8F8VWpQpfrJlRkU3BWmZ2XvEQ6lbnb W2CVuAEMyn1T4cBoQ5E7bGXMQ3doXtygL7JMSbWMYoNGzYMMBOCjR5jJ3RLWRfqiRsIp dEz4+8NCkd+DvRattzL5ZJCJrElECe2qmxstY3TFYEy4/c5BCVXnvKZ4OEvHNjcUy6I4 YOWNmrderz7vp0MvwAT9xDwgYC51OOkTmjfBIQxlaM97498iatwiruWU/CBU0EPfKl3X e9kw==
MIME-Version: 1.0
X-Received: by 10.194.189.81 with SMTP id gg17mr3068816wjc.107.1404132057634;  Mon, 30 Jun 2014 05:40:57 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Mon, 30 Jun 2014 05:40:57 -0700 (PDT)
In-Reply-To: <1404094773482.42250@surrey.ac.uk>
References: <CAMm+LwgR_foFD5Cy6ZnkwDCjL_E0APdko26eMf90cEgtjVSU4g@mail.gmail.com> <23312.1403630586@sandelman.ca> <1404094773482.42250@surrey.ac.uk>
Date: Mon, 30 Jun 2014 08:40:57 -0400
X-Google-Sender-Auth: 5i3-2ee4prx1lwKHa7esgoV47qA
Message-ID: <CAMm+LwjkgvFLC2o4KrSTrEwMW7tNSApnsDFc-ivQmMz92Lf2Gw@mail.gmail.com>
Subject: Re: Time to move beyond the 32 bit Internet.
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=047d7bb03a548370b004fd0cf8ce
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LlY0T2yFON4ouhObWQJVN8t4uqo
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 12:41:03 -0000

--047d7bb03a548370b004fd0cf8ce
Content-Type: text/plain; charset=UTF-8

On Sun, Jun 29, 2014 at 10:19 PM, <l.wood@surrey.ac.uk> wrote:

> So NAPT (32bit IPv4 address + necessary 16-bit send/receive ports) must be
> 64 bit?
>
> Its 64 bits the same way that paged memory gave you a 32 bit address space
on 16 bit chips.

--047d7bb03a548370b004fd0cf8ce
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 29, 2014 at 10:19 PM,  <span dir="ltr">&lt;<a href="mailto:l.wood@surrey.ac.uk" target="_blank">l.wood@surrey.ac.uk</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So NAPT (32bit IPv4 address + necessary 16-bit send/receive ports) must be 64 bit?<br>
<br></blockquote><div>Its 64 bits the same way that paged memory gave you a 32 bit address space on 16 bit chips.</div></div></div></div>

--047d7bb03a548370b004fd0cf8ce--


From nobody Mon Jun 30 09:47:33 2014
Return-Path: <nomcom-chair-2014@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 735D91A03B5; Mon, 30 Jun 2014 09:47:29 -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_50=0.8,  J_CHICKENPOX_21=0.6] autolearn=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 cMsDjRXdcgMq; Mon, 30 Jun 2014 09:47:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5C21A03A4; Mon, 30 Jun 2014 09:47:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2014 <nomcom-chair-2014@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: third draft list of qualified volunteers for 2014-2015 nomcom
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140630164728.6326.53628.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jun 2014 09:47:28 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pLU2xr2rN8KkU1kO4Ir7vdJ5g-0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: nomcom-chair-2014@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 16:47:29 -0000

This is the draft (3) list of volunteers.

Four duplicates were removed from the list.
Affiliations which were blank were confirmed.
Eligibility of three people: Alvaro, Christian, Murray was confirmed

I am pleased to announce that we have 140 qualified individuals who
have generously volunteered to serve as voting members of this year's
Nomcom.

Please take a look and get in touch before July 3 if you think your
name should be here and it isn't (or possibly I've mis-typed it...), or
if you have any other questions or concerns with the list.

The first number is the place in the list.  The number in () is
the spot on my master list (which includes ineligible people).

My apologies if my any UTF-8/Latin-1 confusion broke an accent in
your name; it's my MUA's fault.

As published in the schedule, back in April, and visible at:
     https://datatracker.ietf.org/nomcom/2014/
and  http://goo.gl/D3q2CY

We are at step 06.  The random selection will occur on Sunday July 6.

01. 2014-Mar-28 Nomcom Chair Announcement made.
02. 2014-May-15 FIRST message volunteers
03. 2014-May-29 SECOND message volunteers
04. 2014-Jun-12 THIRD message volunteers
05. 2014-Jun-19 Timeline and Seeds for Random Selection
06. 2014-Jun-26 Final Announcement of Qualified Volunteers
    *HERE*

07. 2014-Jul-03 Raise issues on qualified volunteers by 23:59 EDT.
08. 2014-Jul-06 Seed values available from seed sources
09. 2014-Jul-06 Run random selection algorithm and publish results
10. 2014-Jul-07 challenge process begins
11. 2014-Jul-14 challenge process ends
12. 2014-Jul-15 Results of Random Selection

ps: if your copy of my GPG key says it expired, pull from pgp.mit.edu,
    use finger mcr@sandelman.ca

Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org

=====  qualified volunteers so far, in list order, no sorting
001 (1) Tim Wicinski , Salesforce
002 (2) Paul Hoffman , VPN Consortium
003 (3) John Scudder , Juniper
004 (4) Toerless Eckert , Cisco Systems
005 (5) Gonzalo Salgueiro , Cisco Systems
006 (6) Stephan Wenger , Vidyo
007 (7) Louis (Lou) Berger , LabN Consulting, L.L.C.
008 (8) Fred Baker , Cisco Systems
009 (9) Ross Callon , Juniper
010 (10) Carlos Martinez , LACNIC
011 (11) DHRUV DHODY , Huawei Technologies
012 (12) Suhas Nandakumar , Cisco Systems
013 (13) Ron Bonica , Juniper
014 (14) Sanjay Mishra , Verizon Communications
015 (15) John Levine , Taughannock Networks
016 (16) Melinda Shore , No Mountain Software
017 (17) Wassim Haddad , Ericsson
018 (18) Hosnieh Rafiee , Huawei Technologies
019 (19) Sam K. Aldrin , Huawei Technologies
020 (20) Lucy Yong , Huawei Technologies
021 (21) Ross Finlayson , Live Networks, Inc.
022 (22) Mehmet Ersue , Nokia
023 (23) Carl Williams , MCSR Labs
024 (24) Min Ye , Huawei Technologies
025 (25) Fernando Gont , UTN/FRH
026 (26) Ole Troan , Cisco Systems
027 (27) Luca Martini , Cisco Systems
028 (28) Bill VerSteeg , Cisco Systems
029 (29) Linda Dunbar , Huawei technologies
030 (30) Charles Eckel , Cisco Systems
031 (31) Pascal Thubert , Cisco systems
032 (32) Hugo Salgado , NIC Chile
033 (33) Peter Yee , AKAYLA
034 (34) Stephen Kent , BBN Technologies
035 (35) Xiaohu XU , Huawei Technologies
036 (36) John E Drake , Juniper Networks
037 (37) Donald Eastlake , Huawei Technologies
038 (38) Yuanlong Jiang , Huawei Technologies
039 (39) Ning Zong , Huawei technologies
040 (40) Hongyu Li , Huawei Technologies
041 (41) Shucheng Liu , Huawei Technologies
042 (42) Ralph Droms , Cisco Systems
043 (43) Tissa Senevirathne , Cisco Systems
044 (44) Lingli Deng , China Mobile
045 (45) Dapeng Liu , China Mobile
046 (46) Mach Chen , Huawei technologies
047 (47) Dacheng Zhang , Huawei technologies
048 (48) Adam Montville , Tripwire, Inc.
049 (49) Mark Townsley , Cisco Systems
050 (50) Sheng JIANG , Huawei Technologies
051 (51) Matt Lepinski , BBN Technologies
052 (52) Stephan Friedl , Cisco Systems
053 (53) Eric VYNCKE , Cisco Systems
054 (54) ANM Zaheduzzaman Sarker , Ericsson
055 (55) Stan Ratliff , Cisco
056 (56) Edward Crabbe , Google
057 (57) Karen Seo , BBN Technology
058 (58) Hannes Gredler , Juniper Networks
059 (59) Susan Hares , Hickory Hill Consulting
060 (60) Iuniana Oprescu , Orange
061 (61) Varun Singh , Aalto University
062 (62) Jon Mitchell , Microsoft
063 (63) Zhaohui Zhang , Juniper Networks
064 (64) Ari Ker?nen , Ari Ker?nen
065 (65) Mingui Zhang , Huawei
066 (66) Dean Bogdanovic , Juniper Networks
067 (67) Suresh Krishnan , Ericsson
068 (68) Craig White , Alcatel-Lucent
069 (69) Fangwei Hu , ZTE Corporation
070 (70) Samuel Weiler , Parsons
071 (77) Alvaro Retana, Cisco Systems, Inc.
072 (82) Benson Schliesser, Brocade Communications
073 (83) Bhumip Khasnabish, ZTE (TX) Inc.
074 (84) QIN WU, Shenzhen Huawei Technologies Software Co.,Ltd
075 (88) Charles Perkins, Futurewei
076 (92) Christer Holmberg, Ericsson
077 (95) Yong Cui, Tsinghua Univ.
078 (98) Damien Saucez , Inria
079 (100) Hui Deng, China Mobile
080 (102) Dimitri Papadimitriou, Alcatel
081 (110) Emil Ivov, jitsi.org
082 (119) Luigi Iannone, Telecom ParisTech
083 (120) Giles Heron, Cisco Systems
084 (123) Gregory Mirsky, Ericsson
085 (124) Gunter Van de Velde, Cisco Systems
086 (126) Yunfei Zhang, Coolpad
087 (134) Joseph Abley, Dyn, Inc.
088 (136) Jeff Tantsura, Ericsson
089 (140) John Jason Brzozowski, Comcast
090 (142) Jon Hudson, Brocade
091 (143) Jouni Korhonen, Broadcom
092 (144) Kostas Pentikousis, EICT GmbH
093 (147) Klaas Wierenga, Cisco
094 (148) Kaveh Ranjbar, RIPE NCC
095 (153) Lee Howard, Time Warner Cable
096 (155) Lei Zhu, Huawei
097 (159) Yizhou Li, Huawei Technologies
098 (160) Lucy Lynch -900, Internet Society
099 (165) Marcelo Bagnulo, UC3M
100 (166) Larry Masinter, Adobe
101 (167) Matthew Bocci, Alcatel-Lucent
102 (170) Michael Jones, Microsoft
103 (171) Mahesh Jethanandani, Ciena Corporation
104 (173) Karen O'Donoghue, Internet Society
105 (174) Christian O'Flaherty, Internet Society
106 (179) P?l-Erik Martinsen, Cisco
107 (187) Peter Lothberg, STUPI LLC
108 (190) Sandeep Kumar, Philips Research
109 (192) Scott Mansfield, Ericsson
110 (196) Simon Pietro Romano, Meetecho/University of Napoli
111 (198) Stewart Bryant, Cisco Systems
112 (204) Thomas Nadeau, Brocade
113 (206) Tony Hansen, AT&T Labs
114 (209) Ulrich Herberg, Fujitsu Laboratories of America
115 (216) Li Xue, Shenzhen Huawei Technologies Software Co., Ltd
116 (218) Zhen Cao, China Mobile
117 (220) Fatai Zhang, Shenzhen Huawei Technologies Software Co., Ltd.
118 (221) Yi Zhao, Huawei USA
119 (222) Hannes Tschofenig , ARM
120 (223) Paul Ebersman , Comcast
121 (224) Andrew Yourtchenko , Cisco
122 (225) Salvatore Loreto , Ericsson
123 (226) Stig Venaas , Cisco
124 (227) Peter Koch  , DENIC eG
125 (228) Paul Wouters , Red Hat
126 (230) Vic Liu (Zhiheng Liu) , ChinaMobile
127 (231) Andy Bierman , YumaWorks, Inc.
128 (232) Simon Perreault , Jive Communications
129 (234) Franck Martin , Linkedin
130 (235) Tom Walsh , Juniper Networks
131 (236) Ning Kong , CNNIC
132 (237) Russ White , Ericsson
133 (238) Konda Tirumaleswar Reddy , Cisco
134 (239) Lixia Zhang , UCLA
135 (240) Ignas Bagdonas , Routing System Ltd
136 (241) Brian Weis , Cisco Systems
137 (242) David Mandelberg , BBN Technologies
138 (243) Dorothy Gellert , Silver Spring Networks.
139 (244) Warren Kumari  , Google
140 (245) Murray Kucherawy , Facebook

